RFC 8851: RTP Payload Format Restrictions
In plain English — editorial summary, not part of the RFC
In this specification, we define a framework for specifying restrictions on RTP streams in the Session Description Protocol (SDP). This framework defines a new "rid" ("restriction identifier") SDP attribute to unambiguously identify the RTP streams within an RTP session and restrict the streams' payload format parameters in a codec-agnostic way beyond what is provided with the regular payload types. This specification updates RFC 4855 to give additional guidance on choice of Format Parameter (fmtp) names and their relation to the restrictions defined by this document.
Document record
- Document ID
- RFC8851
- Published
- January 2021
- Authors
- A.B. Roach
- Status
- PROPOSED STANDARD
- Stream
- IETF
- Area
- art
- Pages
- 26
- Also known as
- —
- Updates:
- RFC 4855
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 8852RTP Stream Identifier Source Description (SDES)Current
January 2021
- RFC 8850Controlling Multiple Streams for Telepresence (CLUE) Protocol Data ChannelCurrent
January 2021
- RFC 8849Mapping RTP Streams to Controlling Multiple Streams for Telepresence (CLUE) Media CapturesCurrent
January 2021
- RFC 8853Using Simulcast in Session Description Protocol (SDP) and RTP SessionsCurrent
January 2021
- RFC 8848Session Signaling for Controlling Multiple Streams for Telepresence (CLUE)Current
January 2021
- RFC 8847Protocol for Controlling Multiple Streams for Telepresence (CLUE)Current
January 2021
- RFC 8855The Binary Floor Control Protocol (BFCP)Current
January 2021
- RFC 8846An XML Schema for the Controlling Multiple Streams for Telepresence (CLUE) Data ModelCurrent
January 2021
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?