RFC 6184: RTP Payload Format for H.264 Video
In plain English — editorial summary, not part of the RFC
This memo describes an RTP Payload format for the ITU-T Recommendation H.264 video codec and the technically identical ISO/IEC International Standard 14496-10 video codec, excluding the Scalable Video Coding (SVC) extension and the Multiview Video Coding extension, for which the RTP payload formats are defined elsewhere. The RTP payload format allows for packetization of one or more Network Abstraction Layer Units (NALUs), produced by an H.264 video encoder, in each RTP payload. The payload format has wide applicability, as it supports applications from simple low bitrate conversational usage, to Internet video streaming with interleaved transmission, to high bitrate video-on-demand. This memo obsoletes RFC 3984. Changes from RFC 3984 are summarized in Section 14. Issues on backward compatibility to RFC 3984 are discussed in Section 15. [STANDARDS-TRACK]
Document record
- Document ID
- RFC6184
- Published
- May 2011
- Authors
- Y.-K. Wang; R. Even; T. Kristensen; R. Jesup
- Status
- PROPOSED STANDARD
- Stream
- IETF
- Area
- rai
- Pages
- 101
- Also known as
- —
- Obsoletes:
- RFC 3984
Topics
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 6190RTP Payload Format for Scalable Video CodingCurrent
May 2011
- RFC 6185RTP Payload Format for H.264 Reduced-Complexity Decoding Operation (RCDO) VideoCurrent
May 2011
- RFC 6188The Use of AES-192 and AES-256 in Secure RTPCurrent
March 2011
- RFC 6157IPv6 Transition in the Session Initiation Protocol (SIP)Current
April 2011
- RFC 6155Use of Device Identity in HTTP-Enabled Location Delivery (HELD)Updated
March 2011
- RFC 6222Guidelines for Choosing RTP Control Protocol (RTCP) Canonical Names (CNAMEs)Obsoleted
April 2011
- RFC 6225Dynamic Host Configuration Protocol Options for Coordinate-Based Location Configuration InformationCurrent
July 2011
- RFC 6140Registration for Multiple Phone Numbers in the Session Initiation Protocol (SIP)Current
March 2011
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?