Media Type Registration of Payload Formats in the RTP Profile for Audio and Video Conferences
draft-ietf-avt-rfc3555bis-part2-02

Approval announcement
Draft of message to be sent after approval:

Announcement

From: The IESG <iesg-secretary@ietf.org>
To: IETF-Announce <ietf-announce@ietf.org>
Cc: Internet Architecture Board <iab@iab.org>,
    RFC Editor <rfc-editor@rfc-editor.org>, 
    avt mailing list <avt@ietf.org>, 
    avt chair <avt-chairs@tools.ietf.org>
Subject: Protocol Action: 'Media Type Registration of RTP 
         Payload Formats' to Proposed Standard 

The IESG has approved the following documents:

- 'Media Type Registration of RTP Payload Formats '
   <draft-ietf-avt-rfc3555bis-06.txt> as a Proposed Standard
- 'Media Type Registration of Payload Formats in the RTP Profile for 
   Audio and Video Conferences '
   <draft-ietf-avt-rfc3555bis-part2-03.txt> as a Proposed Standard

These documents are products of the Audio/Video Transport Working Group. 

The IESG contact persons are Cullen Jennings and Jon Peterson.

A URL of this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-ietf-avt-rfc3555bis-06.txt

Ballot Text

Technical Summary

These drafts specify the procedure to register RTP payload formats
as audio, video or other media subtype names. This is useful in a
text-based format description or control protocol to identify the
type of an RTP transmission. Media type registrations for the RTP
payload formats defined in the RTP Profile for Audio and Video
Conferences are also included. Some of these may also be used for
transfer modes other than RTP.

Working Group Summary

These drafts update RFC 3555 to document existing practice with
media type registration for RTP payload formats, as has evolved
in the time since RFC 3555 was published, and taking account of
the updated media type registration rules defined in RFC 4288.
They also update a number of media type registrations, to match
the current template.

Protocol Quality

These drafts were reviewed for the IESG by Magnus Westerlund and
Colin Perkins, and update RFC 3555 to match existing practice.
Review on the ietf-types list was solicited in May 2006, and there
were no objections.

Note to RFC Editor
 
 Replace "RFC XXXX" with the RFC number for draft-ietf-avt-rfc3555bis

RFC Editor Note