RFC 8285: A General Mechanism for RTP Header Extensions
In plain English — editorial summary, not part of the RFC
This document provides a general mechanism to use the header extension feature of RTP (the Real-time Transport Protocol). It provides the option to use a small number of small extensions in each RTP packet, where the universe of possible extensions is large and registration is decentralized. The actual extensions in use in a session are signaled in the setup information for that session. This document obsoletes RFC 5285.
Document record
- Document ID
- RFC8285
- Published
- October 2017
- Authors
- D. Singer; H. Desineni; R. Even
- Status
- PROPOSED STANDARD
- Stream
- IETF
- Area
- wit
- Pages
- 25
- Also known as
- —
- Obsoletes:
- RFC 5285
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 8276File System Extended Attributes in NFSv4Current
December 2017
- RFC 8275Allowing Inheritable NFSv4 Access Control Entries to Override the UmaskCurrent
December 2017
- RFC 8297An HTTP Status Code for Indicating HintsCurrent
December 2017
- RFC 8269The ARIA Algorithm and Its Use with the Secure Real-Time Transport Protocol (SRTP)Current
October 2017
- RFC 8267Network File System (NFS) Upper-Layer Binding to RPC-over-RDMA Version 1Current
October 2017
- RFC 8303On the Usage of Transport Features Provided by IETF Transport ProtocolsCurrent
February 2018
- RFC 8304Transport Features of the User Datagram Protocol (UDP) and Lightweight UDP (UDP-Lite)Current
February 2018
- RFC 8261Datagram Transport Layer Security (DTLS) Encapsulation of SCTP PacketsUpdated
November 2017
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?