Skip to main content

RTP Payload Format for H.264 Video
RFC 6184

Revision differences

Document history

Date By Action
2020-01-21
(System) Received changes through RFC Editor sync (added Verified Errata tag)
2018-12-20
(System)
Received changes through RFC Editor sync (changed abstract to 'This memo describes an RTP Payload format for the ITU-T Recommendation H.264 video codec and the …
Received changes through RFC Editor sync (changed abstract to '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]')
2015-10-14
(System) Notify list changed from avt-chairs@ietf.org, draft-ietf-avt-rtp-rfc3984bis@ietf.org to (None)
2012-12-10
(System) Posted related IPR disclosure: Microsoft Corporation's Statement about IPR related to RFC 6184
2011-05-04
Cindy Morgan State changed to RFC Published from RFC Ed Queue.
2011-05-03
(System) RFC published