[AVTCORE] I-D Action: draft-ietf-avtcore-rtp-payload-registry-04.txt
internet-drafts@ietf.org Mon, 07 October 2024 09:27 UTC
Return-Path: <internet-drafts@ietf.org>
X-Original-To: avt@ietf.org
Delivered-To: avt@ietfa.amsl.com
Received: from [10.244.8.145] (unknown [104.131.183.230]) by ietfa.amsl.com (Postfix) with ESMTP id 64ED2C151533; Mon, 7 Oct 2024 02:27:22 -0700 (PDT)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: internet-drafts@ietf.org
To: i-d-announce@ietf.org
X-Test-IDTracker: no
X-IETF-IDTracker: 12.25.0
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <172829324201.465214.15598954742567420537@dt-datatracker-cb674fff7-jr9km>
Date: Mon, 07 Oct 2024 02:27:22 -0700
Message-ID-Hash: GGUYMFWECNOP37YRCTB74P7TEL7WRTP2
X-Message-ID-Hash: GGUYMFWECNOP37YRCTB74P7TEL7WRTP2
X-MailFrom: internet-drafts@ietf.org
X-Mailman-Rule-Misses: dmarc-mitigation; no-senders; approved; emergency; loop; banned-address; member-moderation; header-match-avt.ietf.org-0; nonmember-moderation; administrivia; implicit-dest; max-recipients; max-size; news-moderation; no-subject; digests; suspicious-header
CC: avt@ietf.org
X-Mailman-Version: 3.3.9rc5
Reply-To: avt@ietf.org
Subject: [AVTCORE] I-D Action: draft-ietf-avtcore-rtp-payload-registry-04.txt
List-Id: Audio/Video Transport Core Maintenance <avt.ietf.org>
Archived-At: <https://mailarchive.ietf.org/arch/msg/avt/bR-LdM0y1SLdyxmWvalyJJTgWuI>
List-Archive: <https://mailarchive.ietf.org/arch/browse/avt>
List-Help: <mailto:avt-request@ietf.org?subject=help>
List-Owner: <mailto:avt-owner@ietf.org>
List-Post: <mailto:avt@ietf.org>
List-Subscribe: <mailto:avt-join@ietf.org>
List-Unsubscribe: <mailto:avt-leave@ietf.org>
Internet-Draft draft-ietf-avtcore-rtp-payload-registry-04.txt is now available. It is a work item of the Audio/Video Transport Core Maintenance (AVTCORE) WG of the IETF. Title: Closing the RTP Payload Format Media Types IANA Registry Author: Magnus Westerlund Name: draft-ietf-avtcore-rtp-payload-registry-04.txt Pages: 7 Dates: 2024-10-07 Abstract: 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" as recommended by RFC 8088. 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. The IETF datatracker status page for this Internet-Draft is: https://datatracker.ietf.org/doc/draft-ietf-avtcore-rtp-payload-registry/ There is also an HTML version available at: https://www.ietf.org/archive/id/draft-ietf-avtcore-rtp-payload-registry-04.html A diff from the previous version is available at: https://author-tools.ietf.org/iddiff?url2=draft-ietf-avtcore-rtp-payload-registry-04 Internet-Drafts are also available by rsync at: rsync.ietf.org::internet-drafts
- [AVTCORE] I-D Action: draft-ietf-avtcore-rtp-payl… internet-drafts
- [AVTCORE] Re: I-D Action: draft-ietf-avtcore-rtp-… Magnus Westerlund