[rfc-dist] RFC 5104 on Codec Control Messages in the RTP Audio-Visual Profile with Feedback (AVPF)

rfc-editor@rfc-editor.org rfc-editor at rfc-editor.org
Fri Feb 22 17:11:25 PST 2008

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

        RFC 5104

        Title:      Codec Control Messages in the 
                    RTP Audio-Visual Profile with Feedback (AVPF) 
        Author:     S. Wenger, U. Chandra,
                    M. Westerlund, B. Burman
        Status:     Standards Track
        Date:       February 2008
        Mailbox:    stewe at stewe.org, 
                    Umesh.1.Chandra at nokia.com, 
                    magnus.westerlund at ericsson.com, 
                    bo.burman at ericsson.com
        Pages:      64
        Characters: 158098
        Updates/Obsoletes/SeeAlso:   None

        I-D Tag:    draft-ietf-avt-avpf-ccm-10.txt

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

This document specifies a few extensions to the messages defined in
the Audio-Visual Profile with Feedback (AVPF).  They are helpful
primarily in conversational multimedia scenarios where centralized
multipoint functionalities are in use.  However, some are also
usable in smaller multicast environments and point-to-point calls.

The extensions discussed are messages related to the ITU-T Rec. H.271
Video Back Channel, Full Intra Request, Temporary Maximum Media
Stream Bit Rate, and Temporal-Spatial Trade-off.  [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 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.

The RFC Editor Team
USC/Information Sciences Institute


IETF-Announce mailing list
IETF-Announce at ietf.org

More information about the rfc-dist mailing list