Closing the RTP Payload Format Media Types IANA Registry
draft-ietf-avtcore-rtp-payload-registry-04

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: The IESG <iesg@ietf.org>, avt@ietf.org, avtcore-chairs@ietf.org, bernard.aboba@gmail.com, draft-ietf-avtcore-rtp-payload-registry@ietf.org, rfc-editor@rfc-editor.org, zahed.sarker.ietf@gmail.com
Subject: Protocol Action: 'Closing the RTP Payload Format Media Types IANA Registry' to Proposed Standard (draft-ietf-avtcore-rtp-payload-registry-02.txt)

The IESG has approved the following document:
- 'Closing the RTP Payload Format Media Types IANA Registry'
  (draft-ietf-avtcore-rtp-payload-registry-02.txt) as Proposed Standard

This document is the product of the Audio/Video Transport Core Maintenance
Working Group.

The IESG contact persons are Zaheduzzaman Sarker and Francesca Palombini.

A URL of this Internet-Draft is:
https://datatracker.ietf.org/doc/draft-ietf-avtcore-rtp-payload-registry/

Ballot Text

Technical Summary

   It has been observed that specifications of new RTP payload formats
   often forget to register themselves in the IANA registry "RTP Payload
   Formats Media Types".  In practice this has no real impact.  One
   reason is that the Media Types registry is the crucial registry to
   register any Media Type to establish the media type used to
   identified the format in various signaling usage.

   This document resolves the situation by first updating the RTP
   Payload Format Media Type registry to include all the known RTP
   payload formats at the time of writing, then it closes this IANA
   Registry for any future registration.  Beyond instructing IANA to
   close this registry, the instructions to authors in RFC 8088 are
   updated to reflect this.

Working Group Summary

   The consensus represented broad agreement.
WG Last Call summary:
https://mailarchive.ietf.org/arch/msg/avt/Aorv6tEQep128MkGUr_ccPZ00KU/
   The reasoning for a PS is described in the shepherd's writeup.
 

Document Quality

   No protocol implemantation is applicable.

Personnel

   The Document Shepherd for this document is Dr. Bernard D. Aboba. The
   Responsible Area Director is Zaheduzzaman Sarker.

RFC Editor Note