AVTCORE
Internet Engineering Task Force (IETF) M. Westerlund
Internet-Draft
Request for Comments: 9751 Ericsson
Updates: 8088 (if approved) 18 October 2024
Intended status: February 2025
Category: Standards Track
Expires: 21 April 2025
ISSN: 2070-1721
Closing the RTP Payload Format Media Types IANA Registry
draft-ietf-avtcore-rtp-payload-registry-05
Abstract
A number of authors of defining RTP Payload Formats payload formats and the WG Working
Group process have failed to ensure that the media types for RTP payload formats is
registred are
registered in the IANA registry "RTP Payload Formats Format Media Types" registry as
recommended by RFC 8088. To simplify the process and rely only on
the media types registry "Media Types" registry, this document closes the RTP payload payload-
specific registry. In addition addition, it updates the instruction to payload
format authors in RFC
8088 to reflect this change.
About This Document
This note is to be removed before publishing as an RFC.
Status information for this document may be found at
https://datatracker.ietf.org/doc/draft-ietf-avtcore-rtp-payload-
registry/.
Discussion of this document takes place on the AVTCORE Working Group
mailing list (mailto:avt@ietf.org), which is archived at
https://mailarchive.ietf.org/arch/browse/avt/. Subscribe at
https://www.ietf.org/mailman/listinfo/avt/.
Source for this draft and an issue tracker can be found at
https://github.com/gloinul/draft-ietf-avtcore-rtp-payload-registry.
Status of This Memo
This Internet-Draft is submitted in full conformance with the
provisions of BCP 78 and BCP 79.
Internet-Drafts are working documents an Internet Standards Track document.
This document is a product of the Internet Engineering Task Force
(IETF). Note that other groups may also distribute
working documents as Internet-Drafts. The list It represents the consensus of current Internet-
Drafts is at https://datatracker.ietf.org/drafts/current/.
Internet-Drafts are draft documents valid the IETF community. It has
received public review and has been approved for a maximum publication by the
Internet Engineering Steering Group (IESG). Further information on
Internet Standards is available in Section 2 of six months RFC 7841.
Information about the current status of this document, any errata,
and how to provide feedback on it may be updated, replaced, or obsoleted by other documents obtained at any
time. It is inappropriate to use Internet-Drafts as reference
material or to cite them other than as "work in progress."
This Internet-Draft will expire on 21 April 2025.
https://www.rfc-editor.org/info/rfc9751.
Copyright Notice
Copyright (c) 2024 2025 IETF Trust and the persons identified as the
document authors. All rights reserved.
This document is subject to BCP 78 and the IETF Trust's Legal
Provisions Relating to IETF Documents (https://trustee.ietf.org/
license-info)
(https://trustee.ietf.org/license-info) in effect on the date of
publication of this document. Please review these documents
carefully, as they describe your rights and restrictions with respect
to this document. Code Components extracted from this document must
include Revised BSD License text as described in Section 4.e of the
Trust Legal Provisions and are provided without warranty as described
in the Revised BSD License.
Table of Contents
1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 2
2. Update to How To to Write an RTP Payload Format . . . . . . . . 3
3. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 4
4. Security Considerations . . . . . . . . . . . . . . . . . . . 5
5. References . . . . . . . . . . . . . . . . . . . . . . . . . 5
5.1. Normative References . . . . . . . . . . . . . . . . . . 5
5.2. Informative References . . . . . . . . . . . . . . . . . 6
Appendix A.
Acknowledgments . . . . . . . . . . . . . . . . . . 6
Author's Address . . . . . . . . . . . . . . . . . . . . . . . . 6
1. Introduction
It has been observed that specifications of new Real-time Transport
Protocol (RTP) payload formats often forget to specify registration
of the format's media type in the IANA registry "RTP Payload Formats
Media Types" [RTP-FORMATS] as recommended by [RFC8088]. In practice practice,
this has no real impact. This registry is not used for any purpose
other than to track which media types actually have RTP payload
formats. That purpose could be addressed through other means.
The Media Types "Media Types" registry [MEDIA-TYPES] is the crucial registry to
register any Media Type media type to establish the media type used to identify
the format in various signalling usages, to avoid collisions, and to
reference their specifications.
To resolve this situation, this document performs the following
actions. First, it updates the registry to include known RTP payload
formats at the time of writing. Then, it closes the IANA Registry
for RTP "RTP Payload Formats
Format Media Types for Types" registry to future registration. registrations. Beyond
instructing IANA to close this registry, the instructions to authors
in [RFC8088] are updated so that registration in the closed registry
is no longer mentioned.
The origins of the "RTP Payload Formats Format Media Types" registry, as
referenced in [RTP-FORMATS], are unclear. The registry cites
[RFC4855] as providing the instructions for its maintenance.
However, upon reviewing RFC 4855, no text has been found that defines
the registry's purpose and operational rules. Further attempts to
trace the registry's creation have failed to uncover any references
to its establishment. It is likely that the registry was created
based on correspondence via email correspondence or at the request of an Area
Director (AD). Director.
Consequently, there is no known existing specification for this registry that
requires updating upon its closure.
2. Update to How To to Write an RTP Payload Format
How
The IANA Considerations section of "How to write an RTP Payload format [RFC8088] mandates in its section
on IANA Considerations
Format" (Section 7.4) 7.4 of [RFC8088]) mandates that RTP Payload payload formats
shall
register be registered in RTP the "RTP Payload Format media types. Media Types" registry.
This paragraph is changed without affecting its status as part of an informational
Informational RFC. Thus removing the need to register in the "RTP
Payload Format media types".
OLD:
"Since
| Since all RTP payload formats contain a media type specification,
| they also need an IANA Considerations section. The media type
| name must be registered, and this is done by requesting that IANA
| register that media name. When that registration request is
| written, it shall also be requested that the media type is
| included under the "RTP Payload Format media types" sub-registry
| of the RTP registry
(http://www.iana.org/assignments/rtp-parameters)." (http://www.iana.org/assignments/rtp-
| parameters).
NEW:
"Since
| Since all RTP payload formats contain a media type specification,
| they also need an IANA Considerations section. The media type
| name must be registered, and this is done by requesting that IANA
| register that media name in the Media Types "Media Types" registry
(https://www.iana.org/assignments/media-types/media-types.xhtml)."
| (https://www.iana.org/assignments/media-types/).
3. IANA Considerations
IANA is requested to add has added the following missing RTP Payload payload types to the "RTP Payload
Format Media Types" registry [RTP-FORMATS].
+=============+==========+===========+==========+==================+
| Media Type | Sub Type Subtype | Clock | Channels | Reference |
| | | Rate (Hz) | (audio) | |
+=============+==========+===========+==========+==================+
| application | flexfec | | | RFC8627 RFC 8627 |
+-------------+----------+-----------+----------+------------------+
| audio | EVRCNW | 16000 | | RFC6884 RFC 6884 |
+-------------+----------+-----------+----------+------------------+
| audio | EVRCNW0 | 16000 | | RFC6884 RFC 6884 |
+-------------+----------+-----------+----------+------------------+
| audio | EVRCNW1 | 16000 | | RFC6884 RFC 6884 |
+-------------+----------+-----------+----------+------------------+
| audio | aptx | | | RFC7310 RFC 7310 |
+-------------+----------+-----------+----------+------------------+
| audio | opus | 48000 | | RFC7587 RFC 7587 |
+-------------+----------+-----------+----------+------------------+
| audio | G711-0 | | | RFC7650 RFC 7650 |
+-------------+----------+-----------+----------+------------------+
| audio | flexfec | | | RFC8627 RFC 8627 |
+-------------+----------+-----------+----------+------------------+
| text | flexfec | | | RFC8627 RFC 8627 |
+-------------+----------+-----------+----------+------------------+
| text | ttml+xml | | | RFC8759 RFC 8759 |
+-------------+----------+-----------+----------+------------------+
| video | VP8 | 90000 | | RFC7741 RFC 7741 |
+-------------+----------+-----------+----------+------------------+
| video | AV1 | 90000 | | [AV1-Media-Type] |
+-------------+----------+-----------+----------+------------------+
| video | HEVC | 90000 | | RFC7798 RFC 7798 |
+-------------+----------+-----------+----------+------------------+
| video | smpte291 | | | RFC8331 RFC 8331 |
+-------------+----------+-----------+----------+------------------+
| video | VVC | 90000 | | RFC9328 RFC 9328 |
+-------------+----------+-----------+----------+------------------+
| video | EVC | 90000 | | RFC9584 RFC 9584 |
+-------------+----------+-----------+----------+------------------+
| video | flexfec | | | RFC8627 RFC 8627 |
+-------------+----------+-----------+----------+------------------+
Table 1: Payload Types Added to Register in the RTP Payload Format Media
Types Registry
IANA is requested to update has updated the following RTP Payload types entries in the "RTP Payload Format
Media Types" registry [RTP-FORMATS].
+============+===========+=================+==========+===========+
| Media Type | Sub Type Subtype | Clock Rate (Hz) | Channels | Reference |
| | | | (audio) | |
+============+===========+=================+==========+===========+
| audio | MP4A-LATM | | | RFC6416 RFC 6416 |
+------------+-----------+-----------------+----------+-----------+
| video | MP4V-ES | 90000 | | RFC6416 RFC 6416 |
+------------+-----------+-----------------+----------+-----------+
Table 2: Payload Types to update Updated in RTP Payload Format Media
Types Registry
IANA is further requested to close has also closed the "RTP Payload Format Media Types" registry
[RTP-FORMATS] for to any further registrations. IANA
should add added the following
to the existing note for the registry: registry note:
NEW:
"This
| This registry has been closed as closed; it was considered redundant as because
| all RTP Payload payload formats are part of the Media [Media Types registry
(https://www.iana.org/assignments/media-types/media-types.xhtml).
For registry]
| (https://www.iana.org/assignments/media-types). See RFC 9751 for
| further motivation see (RFC-TBD1)." details.
In addition, it is requested that IANA updated the existing note of in the "RTP Payload Format Media
Types" registry [RTP-FORMATS] is changed in the
following way: as follows:
OLD:
| Registration procedures and a registration template can be found
| in [RFC4855].
NEW:
| It was previously stated that registration procedures and a
| registration template can be found in [RFC4855]. This As documented in
| RFC 9751, this is not
actually the case as discussed by [RFC-TBD1].
RFC-Editor Note: Please replace RFC-TBD1 with the RFC number of this
specification and then remove this note. case.
4. Security Considerations
This document has no security considerations as it defines an
administrative rule change.
5. References
5.1. Normative References
[RFC2119] Bradner, S., "Key words for use in RFCs to Indicate
Requirement Levels", BCP 14, RFC 2119,
DOI 10.17487/RFC2119, March 1997,
<https://www.rfc-editor.org/info/rfc2119>.
[AV1-Media-Type]
IANA, "video/AV1",
<https://www.iana.org/assignments/media-types/video/AV1>.
[MEDIA-TYPES]
IANA, "Media Types",
<https://www.iana.org/assignments/media-types>.
[RFC8088] Westerlund, M., "How to Write an RTP Payload Format",
RFC 8088, DOI 10.17487/RFC8088, May 2017,
<https://www.rfc-editor.org/info/rfc8088>.
[RTP-FORMATS]
"IANA's registry for RTP
IANA, "RTP Payload Format Media Types",
November 2023, <https://www.iana.org/assignments/rtp-
parameters/rtp-parameters.xhtml#rtp-parameters-2>.
[MEDIA-TYPES]
"IANA's registry for Media Types", November 2023,
<https://www.iana.org/assignments/media-types/media-
types.xhtml>.
[AV1-Media-Type]
"IANA Media Type Entry for video/AV1", January 2021,
<https://www.iana.org/assignments/media-types/video/AV1>.
<https://www.iana.org/assignments/rtp-parameters>.
5.2. Informative References
[RFC4855] Casner, S., "Media Type Registration of RTP Payload
Formats", RFC 4855, DOI 10.17487/RFC4855, February 2007,
<https://www.rfc-editor.org/info/rfc4855>.
Appendix A.
Acknowledgments
The author likes to thank thanks Jonathan Lennox, Zaheduzzaman Sarker, Bernard
Aboba, Elwyn Davies, Wes Hardaker, Gunter Van de Velde, Éric Vyncke,
Mahesh Jethanandani, and Hyunsik Yang for review their reviews and editorial
fixes.
Author's Address
Magnus Westerlund
Ericsson
Email: magnus.westerlund@ericsson.com