RFC 5432: Quality of Service (QoS) Mechanism Selection in the Session Description Protocol (SDP)
In plain English — editorial summary, not part of the RFC
The offer/answer model for the Session Description Protocol (SDP) assumes that endpoints somehow establish the Quality of Service (QoS) required for the media streams they establish. Endpoints in closed environments typically agree out-of-band (e.g., using configuration information) regarding which QoS mechanism to use. However, on the Internet, there is more than one QoS service available. Consequently, there is a need for a mechanism to negotiate which QoS mechanism to use for a particular media stream. This document defines such a mechanism. [STANDARDS-TRACK]
Document record
- Document ID
- RFC5432
- Published
- March 2009
- Authors
- J. Polk; S. Dhesikan; G. Camarillo
- Status
- PROPOSED STANDARD
- Stream
- IETF
- Area
- art
- Pages
- 9
- Also known as
- —
Topics
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 6141Re-INVITE and Target-Refresh Request Handling in the Session Initiation Protocol (SIP)Current
March 2011
- RFC 4574The Session Description Protocol (SDP) Label AttributeCurrent
August 2006
- RFC 5484Associating Time-Codes with RTP StreamsCurrent
March 2009
- RFC 4585Extended RTP Profile for Real-time Transport Control Protocol (RTCP)-Based Feedback (RTP/AVPF)Updated
July 2006
- RFC 5547A Session Description Protocol (SDP) Offer/Answer Mechanism to Enable File TransferCurrent
May 2009
- RFC 5576Source-Specific Media Attributes in the Session Description Protocol (SDP)Current
June 2009
- RFC 5582Location-to-URL Mapping Architecture and FrameworkCurrent
September 2009
- RFC 5583Signaling Media Decoding Dependency in the Session Description Protocol (SDP)Current
July 2009
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?