[rfc-dist] RFC 4629 on RTP Payload Format for ITU-T Rec. H.263 Video

rfc-editor@rfc-editor.org rfc-editor at rfc-editor.org
Wed Jan 31 18:17:35 PST 2007

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

        RFC 4629

        Title:      RTP Payload Format for ITU-T 
                    Rec. H.263 Video 
        Author:     J. Ott, C. Bormann,
                    G. Sullivan, S. Wenger,
                    R. Even, Ed.
        Status:     Standards Track
        Date:       January 2007
        Mailbox:    jo at netlab.tkk.fi, 
                    cabo at tzi.org, 
                    garysull at microsoft.com,  stewe at stewe.org, 
                    roni.even at polycom.co.il
        Pages:      29
        Characters: 67231

        I-D Tag:    draft-ietf-avt-rfc2429-bis-09.txt

        URL:        http://www.rfc-editor.org/rfc/rfc4629.txt

This document describes a scheme to packetize an H.263 video stream
for transport using the Real-time Transport Protocol (RTP) with any
of the underlying protocols that carry RTP.

The document also describes the syntax and semantics of the Session
Description Protocol (SDP) parameters needed to support the H.263 video codec.

The document obsoletes RFC 2429 and updates the H263-1998 and
H263-2000 MIME media type in RFC 3555.  [STANDARDS TRACK]

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

This is now a Proposed Standard Protocol.

STANDARDS TRACK: 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 

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.

The RFC Editor Team
USC/Information Sciences Institute


More information about the rfc-dist mailing list