Closing the RTP Payload Format Media Types IANA Registry
draft-westerlund-avtcore-rtp-payload-registry-01
| Document | Type |
Replaced Internet-Draft
(individual)
Expired & archived
|
|
|---|---|---|---|
| Author | Magnus Westerlund | ||
| Last updated | 2024-05-21 | ||
| Replaced by | draft-ietf-avtcore-rtp-payload-registry | ||
| RFC stream | (None) | ||
| Intended RFC status | (None) | ||
| Formats | |||
| Stream | Stream state | (No stream defined) | |
| Consensus boilerplate | Unknown | ||
| RFC Editor Note | (None) | ||
| IESG | IESG state | Replaced by draft-ietf-avtcore-rtp-payload-registry | |
| Telechat date | (None) | ||
| Responsible AD | (None) | ||
| Send notices to | (None) |
This Internet-Draft is no longer active. A copy of the expired Internet-Draft is available in these formats:
Abstract
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. To resolve this situation this document performs the following. First it updates the registry to include known RTP payload formats at the time of writing. Then it closes the IANA Registry for RTP Payload formats Media Types for future registration. Beyond instructing IANA to close this registry the instructions to authors in RFC 8088 are updated that registration is no longer required in the closed registry.
Authors
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)