RFC 3984: RTP Payload Format for H.264 Video
This RFC has been replaced. Do not implement against it for new work — it was formally obsoleted by RFC 6184.
Current version: 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. 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 bit-rate conversational usage, to Internet video streaming with interleaved transmission, to high bit-rate video-on-demand. [STANDARDS-TRACK]
Document record
- Document ID
- RFC3984
- Published
- February 2005
- Authors
- S. Wenger; M.M. Hannuksela; T. Stockhammer; M. Westerlund; D. Singer
- Status
- PROPOSED STANDARD
- Stream
- IETF
- Area
- rai
- Pages
- 83
- Also known as
- —
- Obsoleted by:
- RFC 6184
Topics
Referenced by
One later RFC formally updates or obsoletes part of this document.
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 3994Indication of Message Composition for Instant MessagingCurrent
February 2005
- RFC 3969The Internet Assigned Number Authority (IANA) Uniform Resource Identifier (URI) Parameter Registry for the Session Initiation Protocol (SIP)Updated
December 2004
- RFC 3968The Internet Assigned Number Authority (IANA) Header Field Parameter Registry for the Session Initiation Protocol (SIP)Current
December 2004
- RFC 4002IANA Registration for Enumservice 'web' and 'ft'Updated
February 2005
- RFC 3966The tel URI for Telephone NumbersUpdated
December 2004
- RFC 3960Early Media and Ringing Tone Generation in the Session Initiation Protocol (SIP)Current
December 2004
- RFC 3959The Early Session Disposition Type for the Session Initiation Protocol (SIP)Current
December 2004
- RFC 3953Telephone Number Mapping (ENUM) Service Registration for Presence ServicesUpdated
January 2005
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?