[rfc-dist] RFC 3984 on RTP Payload Format for H.264 Video

rfc-editor at rfc-editor.org rfc-editor at rfc-editor.org
Fri Feb 4 16:30:14 PST 2005

A new Request for Comments is now available in online RFC libraries.

        RFC 3984

        Title:      RTP Payload Format for H.264 Video
        Author(s):  S. Wenger, M.M. Hannuksela, T. Stockhammer,
                    M. Westerlund, D. Singer
        Status:     Standards Track
        Date:       February 2005
        Mailbox:    stewe at stewe.org, miska.hannuksela at nokia.com,
                    stockhammer at nomor.de,
                    magnus.westerlund at ericsson.com, singer at apple.com
        Pages:      83
        Characters: 205093
        Updates/Obsoletes/SeeAlso:    None

        I-D Tag:    draft-ietf-avt-rtp-h264-11.txt

        URL:        ftp://ftp.rfc-editor.org/in-notes/rfc3984.txt

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.

This document is a product of the Audio/Video Transport Working Group
of the IETF.

This is now a Proposed Standard Protocol.

This document specifies an Internet standards track protocol for
the Internet community, and requests discussion and suggestions
for improvements.  Please refer to the current edition of the
"Internet Official Protocol Standards" (STD 1) for the
standardization state and status of this protocol.  Distribution
of this memo is unlimited.

This announcement is sent to the IETF list and the RFC-DIST list.
Requests to be added to or deleted from the IETF distribution list
should be sent to IETF-REQUEST at IETF.ORG.  Requests to be
added to or deleted from the RFC-DIST distribution list should

Details on obtaining RFCs via FTP or EMAIL may be obtained by sending
an EMAIL message to rfc-info at RFC-EDITOR.ORG with the message body 
help: ways_to_get_rfcs.  For example:

        To: rfc-info at RFC-EDITOR.ORG
        Subject: getting rfcs

        help: ways_to_get_rfcs

Requests for special distribution should be addressed to either the
author of the RFC in question, or to RFC-Manager at RFC-EDITOR.ORG.  Unless
specifically noted otherwise on the RFC itself, all RFCs are for
unlimited distribution.

Submissions for Requests for Comments should be sent to
RFC-EDITOR at RFC-EDITOR.ORG.  Please consult RFC 2223, Instructions to RFC
Authors, for further information.

Joyce K. Reynolds and Sandy Ginoza
USC/Information Sciences Institute


Below is the data which will enable a MIME compliant Mail Reader 
implementation to automatically retrieve the ASCII version
of the RFCs.
-------------- next part --------------
Skipped content of type multipart/alternative

More information about the rfc-dist mailing list