RFC 9751 on Closing the RTP Payload Format Media Types Registry
rfc-editor@rfc-editor.org Wed, 19 March 2025 06:52 UTC
Return-Path: <wwwrun@rfcpa.rfc-editor.org>
X-Original-To: ietf-announce@ietf.org
Delivered-To: ietf-announce@mail2.ietf.org
Received: from rfcpa.rfc-editor.org (unknown [167.172.21.234]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature ECDSA (P-256) server-digest SHA256) (No client certificate requested) by mail2.ietf.org (Postfix) with ESMTPS id 72C73E71117; Tue, 18 Mar 2025 23:52:07 -0700 (PDT)
Received: by rfcpa.rfc-editor.org (Postfix, from userid 461) id 3061B1EEEB9; Tue, 18 Mar 2025 23:52:07 -0700 (PDT)
To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org
Subject: RFC 9751 on Closing the RTP Payload Format Media Types Registry
From: rfc-editor@rfc-editor.org
Content-type: text/plain; charset="UTF-8"
Message-Id: <20250319065207.3061B1EEEB9@rfcpa.rfc-editor.org>
Date: Tue, 18 Mar 2025 23:52:07 -0700
Message-ID-Hash: NCZUR2NGDJFKGYLYCIXAUPIF6PY4MJYL
X-Message-ID-Hash: NCZUR2NGDJFKGYLYCIXAUPIF6PY4MJYL
X-MailFrom: wwwrun@rfcpa.rfc-editor.org
X-Mailman-Rule-Misses: dmarc-mitigation; no-senders; approved; emergency; loop; banned-address; member-moderation; header-match-ietf-announce.ietf.org-0; nonmember-moderation; administrivia; implicit-dest; max-recipients; max-size; news-moderation; no-subject; digests; suspicious-header
CC: rfc-editor@rfc-editor.org, drafts-update-ref@iana.org, avt@ietf.org
X-Mailman-Version: 3.3.9rc6
Precedence: list
List-Id: "IETF announcement list. No discussions." <ietf-announce.ietf.org>
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf-announce/U9ESRwmKWDnrkeXQ23keB9zSvAI>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf-announce>
List-Help: <mailto:ietf-announce-request@ietf.org?subject=help>
List-Owner: <mailto:ietf-announce-owner@ietf.org>
List-Post: <mailto:ietf-announce@ietf.org>
List-Subscribe: <mailto:ietf-announce-join@ietf.org>
List-Unsubscribe: <mailto:ietf-announce-leave@ietf.org>
A new Request for Comments is now available in online RFC libraries.
RFC 9751
Title: Closing the RTP Payload Format Media Types Registry
Author: M. Westerlund
Status: Standards Track
Stream: IETF
Date: March 2025
Mailbox: magnus.westerlund@ericsson.com
Pages: 6
Updates: RFC 8088
I-D Tag: draft-ietf-avtcore-rtp-payload-registry-05.txt
URL: https://www.rfc-editor.org/info/rfc9751
DOI: 10.17487/RFC9751
The working group process and the authors of RTP payload formats have
sometimes failed to ensure that the media types are registered in the
IANA "RTP Payload Format Media Types" registry as recommended by RFC
8088. To simplify the process and rely only on the "Media Types"
registry, this document closes the RTP payload- specific registry. In
addition, it updates the instruction in RFC 8088 to reflect this
change.
This document is a product of the Audio/Video Transport Core Maintenance Working Group of the IETF.
This is now a Proposed Standard.
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 Official
Internet Protocol Standards (https://www.rfc-editor.org/standards) for the
standardization state and status of this protocol. Distribution of this
memo is unlimited.
This announcement is sent to the IETF-Announce and rfc-dist lists.
To subscribe or unsubscribe, see
https://www.ietf.org/mailman/listinfo/ietf-announce
https://mailman.rfc-editor.org/mailman/listinfo/rfc-dist
For searching the RFC series, see https://www.rfc-editor.org/search
For downloading RFCs, see https://www.rfc-editor.org/retrieve/bulk
Requests for special distribution should be addressed to either the
author of the RFC in question, or to rfc-editor@rfc-editor.org. Unless
specifically noted otherwise on the RFC itself, all RFCs are for
unlimited distribution.
The RFC Editor Team