IETF Logo Mail Archive

Re: [AVTCORE] Missing RTP payload format media type registrations

worley@ariadne.com Thu, 31 August 2023 02:17 UTC

Return-Path: <worley@alum.mit.edu>
X-Original-To: avt@ietfa.amsl.com
Delivered-To: avt@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id AD3A0C14CE4F for <avt@ietfa.amsl.com>; Wed, 30 Aug 2023 19:17:04 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.992
X-Spam-Level:
X-Spam-Status: No, score=-5.992 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, HEADER_FROM_DIFFERENT_DOMAINS=0.249, PP_MIME_FAKE_ASCII_TEXT=0.001, RCVD_IN_DNSWL_HI=-5, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_SOFTFAIL=0.665, T_SCC_BODY_TEXT_LINE=-0.01, URIBL_DBL_BLOCKED_OPENDNS=0.001, URIBL_ZEN_BLOCKED_OPENDNS=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=comcastmailservice.net
Received: from mail.ietf.org ([50.223.129.194]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id TPm0rid5d7jM for <avt@ietfa.amsl.com>; Wed, 30 Aug 2023 19:17:00 -0700 (PDT)
Received: from resqmta-h1p-028589.sys.comcast.net (resqmta-h1p-028589.sys.comcast.net [96.102.200.6]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id A9756C14CE24 for <avt@ietf.org>; Wed, 30 Aug 2023 19:17:00 -0700 (PDT)
Received: from resomta-h1p-027914.sys.comcast.net ([96.102.179.199]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 256/256 bits) (Client did not present a certificate) by resqmta-h1p-028589.sys.comcast.net with ESMTP id bWzXqMUl6m8PjbXD1qvekx; Thu, 31 Aug 2023 02:14:59 +0000
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=comcastmailservice.net; s=20211018a; t=1693448099; bh=JBMUikRJdJFr+ixKSCWLHTdWAd+GX58aLhCm8iGhi+Y=; h=Received:Received:Received:Received:From:To:Subject:Date: Message-ID:Xfinity-Spam-Result; b=dfZJy3o9o35Wgug/0DNkvZrxXKfeMK0lS7QqiuVjqWiaxX7Z8v0Pyk3/ql7LH/U5u ApSmWTD/thoet5e7UuqbLFhOm+m2a/Ut0V1w/vfdKZWArywJpp35hCbWqHsxIvFGv+ ir84aahv+pDm0Z0XWK19HwR75+jsodYD2SNMQTZeOUd8Q2lyRGmnJM8zTnZ/JVDAJS IiTTtCAK11g7wZyNyejIF5YByhOLjQchh9Fw7AB+8EadrBJ4Fyt71XCOukYCATe8qV SiAlpuLkJzwbku1KalnBTqP0pBNgHsoKRzz5ijFJ1vu6aAuFShNPtYndpM9u5wx0qO Z8tNitGPcOANg==
Received: from hobgoblin.ariadne.com ([IPv6:2601:192:4a00:430::3788]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 256/256 bits) (Client did not present a certificate) by resomta-h1p-027914.sys.comcast.net with ESMTPA id bXCcqA8OcEnnMbXCeqsBps; Thu, 31 Aug 2023 02:14:37 +0000
X-Xfinity-VAAS: gggruggvucftvghtrhhoucdtuddrgedviedrudefledgheehucetufdoteggodetrfdotffvucfrrhhofhhilhgvmecuvehomhgtrghsthdqtfgvshhipdfqfgfvpdfpqffurfetoffkrfenuceurghilhhouhhtmecufedtudenucesvcftvggtihhpihgvnhhtshculddquddttddmnecujfgurhephffvvefujghssedttddttddttddtnecuhfhrohhmpeifohhrlhgvhiesrghrihgrughnvgdrtghomhculdffrghlvgcutfdrucghohhrlhgvhidmnecuggftrfgrthhtvghrnhepteevtdeuhfeuhfehleejhfduieduvddtfeejveejffetgfeuleeiudehvdfgudefnecuffhomhgrihhnpehirghnrgdrohhrghenucfkphepvdeitddumeduledvmeegrgdttdemgeeftdemmeefjeekkeenucevlhhushhtvghrufhiiigvpedtnecurfgrrhgrmhephhgvlhhopehhohgsghhosghlihhnrdgrrhhirggunhgvrdgtohhmpdhinhgvthepvdeitddumeduledvmeegrgdttdemgeeftdemmeefjeekkedpmhgrihhlfhhrohhmpeifohhrlhgvhiesrghluhhmrdhmihhtrdgvughupdhnsggprhgtphhtthhopeegpdhrtghpthhtohepjhhonhgrthhhrghnrdhlvghnnhhogieskeigkedrtghomhdprhgtphhtthhopehphhhilhhiphhprdhhrghntghkvgesghhmrghilhdrtghomhdprhgtphhtthhopegrvhhtsehivghtfhdrohhrghdprhgtphhtthhopegsvghrnhgrrhgurdgrsghosggrsehgmhgrihhlrdgtohhm
X-Xfinity-VMeta: sc=-100.00;st=legit
Received: from hobgoblin.ariadne.com (localhost [127.0.0.1]) by hobgoblin.ariadne.com (8.16.1/8.16.1) with ESMTPS id 37V2EXiD2169875 (version=TLSv1.3 cipher=TLS_AES_256_GCM_SHA384 bits=256 verify=NOT); Wed, 30 Aug 2023 22:14:33 -0400
Received: (from worley@localhost) by hobgoblin.ariadne.com (8.16.1/8.16.1/Submit) id 37V2EXFv2169872; Wed, 30 Aug 2023 22:14:33 -0400
X-Authentication-Warning: hobgoblin.ariadne.com: worley set sender to worley@alum.mit.edu using -f
From: worley@ariadne.com
To: Jonathan Lennox <jonathan.lennox@8x8.com>
Cc: bernard.aboba@gmail.com, avt@ietf.org, philipp.hancke@gmail.com
In-Reply-To: <5F9677DC-1631-4588-A2A4-2673B8E82042@8x8.com> (jonathan.lennox@8x8.com)
Sender: worley@ariadne.com
Date: Wed, 30 Aug 2023 22:14:33 -0400
Message-ID: <87v8cw9cvq.fsf@hobgoblin.ariadne.com>
Archived-At: <https://mailarchive.ietf.org/arch/msg/avt/ZVGdbiEtEA0J4CeaD3fMIJFSQHQ>
Subject: Re: [AVTCORE] Missing RTP payload format media type registrations
X-BeenThere: avt@ietf.org
X-Mailman-Version: 2.1.39
Precedence: list
List-Id: Audio/Video Transport Core Maintenance <avt.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/avt>, <mailto:avt-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/avt/>
List-Post: <mailto:avt@ietf.org>
List-Help: <mailto:avt-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/avt>, <mailto:avt-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 31 Aug 2023 02:17:04 -0000

>> On Aug 29, 2023, at 5:34 PM, Bernard Aboba <bernard.aboba@gmail.com> wrote:
>> Apparently, the AV1, VP8, HEVC and VVC codecs are not included in the IANA list of RTP payload media types: 
>> https://www.iana.org/assignments/rtp-parameters/rtp-parameters.xhtml#rtp-parameters-2
>> 
>> However, they are registered in the mime-types registry under video: 
>> https://www.iana.org/assignments/media-types/media-types.xhtml

Actually, HEVC and VVC are *not* in
https://www.iana.org/assignments/media-types/media-types.xhtml (as of
Thu Aug 31 02:09:08 AM UTC 2023).

Jonathan Lennox <jonathan.lennox@8x8.com> writes:
> I guess the first question would be, is the “RTP Payload Format Media
> Types” table actually useful to anyone?  If not, I’d suggest retiring
> it, rather than fixing it. 
>
> I imagine there are more than just those four well-known codecs
> missing from it, and doing a full audit of all relevant payload types
> would be a pretty large amount of work.

If the only question is to align rtp-parameters with media-types, both
of those tables are available as CSV and a join between them should
reveal any missing registrations.

In principle, rtp-parameters specifies how to specify the codec in SDP,
which is not required in the definition of a media type per se.  The SDP
rtpmap "encoding name" is always the same as the media subtype, but SDP
also requires documenting how the encoding parameters are to be
specified in the rtpmap attribute.

Dale

v2.46.0 | Report a Bug | By Email | System Status