RFC 7657: Differentiated Services (Diffserv) and Real-Time Communication
In plain English — editorial summary, not part of the RFC
This memo describes the interaction between Differentiated Services (Diffserv) network quality-of-service (QoS) functionality and real- time network communication, including communication based on the Real-time Transport Protocol (RTP). Diffserv is based on network nodes applying different forwarding treatments to packets whose IP headers are marked with different Diffserv Codepoints (DSCPs). WebRTC applications, as well as some conferencing applications, have begun using the Session Description Protocol (SDP) bundle negotiation mechanism to send multiple traffic streams with different QoS requirements using the same network 5-tuple. The results of using multiple DSCPs to obtain different QoS treatments within a single network 5-tuple have transport protocol interactions, particularly with congestion control functionality (e.g., reordering). In addition, DSCP markings may be changed or removed between the traffic source and destination. This memo covers the implications of these Diffserv aspects for real-time network communication, including WebRTC.
Document record
- Document ID
- RFC7657
- Published
- November 2015
- Authors
- D. Black; P. Jones
- Status
- INFORMATIONAL
- Stream
- IETF
- Area
- rai
- Pages
- 26
- Also known as
- —
Topics
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 8325Mapping Diffserv to IEEE 802.11Updated
February 2018
- RFC 8436Update to IANA Registration Procedures for Pool 3 Values in the Differentiated Services Field Codepoints (DSCP) RegistryCurrent
August 2018
- RFC 6404Session PEERing for Multimedia INTerconnect (SPEERMINT) Security Threats and Suggested CountermeasuresCurrent
November 2011
- RFC 6185RTP Payload Format for H.264 Reduced-Complexity Decoding Operation (RCDO) VideoCurrent
May 2011
- RFC 5691RTP Payload Format for Elementary Streams with MPEG Surround Multi-Channel AudioCurrent
October 2009
- RFC 5584RTP Payload Format for the Adaptive TRansform Acoustic Coding (ATRAC) FamilyCurrent
July 2009
- RFC 5459G.729.1 RTP Payload Format Update: Discontinuous Transmission (DTX) SupportCurrent
January 2009
- RFC 5371RTP Payload Format for JPEG 2000 Video StreamsCurrent
October 2008
Also filed under
About this page
The document record above — title, authors, date, status, stream, area, relationships, DOI and errata — is imported verbatim from the public RFC Editor index. The “in plain English” section is editorial: written by The metasystema editorial team, not part of the RFC. Where the two differ, the RFC text governs.
Last checked against the RFC Editor index on . RFCs are never revised after publication; changes are issued as new documents.
Data sources · Editorial policy · Report a correction · What is an RFC?