[AVTCORE] Re: Gunter Van de Velde's Discuss on draft-ietf-avtcore-rtp-payload-registry-04: (with DISCUSS and COMMENT)

Magnus Westerlund <magnus.westerlund@ericsson.com> Wed, 09 October 2024 11:53 UTC

Return-Path: <magnus.westerlund@ericsson.com>
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 5F426C151080; Wed, 9 Oct 2024 04:53:50 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.155
X-Spam-Level:
X-Spam-Status: No, score=-2.155 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIMWL_WL_HIGH=-0.148, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, HTML_MESSAGE=0.001, HTTPS_HTTP_MISMATCH=0.1, RCVD_IN_DNSWL_BLOCKED=0.001, RCVD_IN_MSPIKE_H2=-0.001, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_PASS=-0.001, 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=ericsson.com
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 GW02gA5etB-z; Wed, 9 Oct 2024 04:53:46 -0700 (PDT)
Received: from EUR02-DB5-obe.outbound.protection.outlook.com (mail-db5eur02on2058.outbound.protection.outlook.com [40.107.249.58]) (using TLSv1.2 with cipher ECDHE-ECDSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 84E0FC14F701; Wed, 9 Oct 2024 04:53:45 -0700 (PDT)
ARC-Seal: i=1; a=rsa-sha256; s=arcselector10001; d=microsoft.com; cv=none; b=cuveSu0OE4guPzdzT65zZThLdLuDWEIZVUmP7xm6FqdWGWuXDsY+VWcVfRcoY20UhgMEEgMDTysbMc+jgqblpkdwqXDXYWzfwWUrznP0O/cVxU1MGlFEfkiuX2jralld5I0Ow/0iZ0TNtAgo1WIpPia2wQ2XmqyMqtEC2oCTfPa2Bhvl9FcFHb4RuhG6BFTsGkiuAGe8avTNtByaSTM3WD56CDjMZoBmTNslJ9fBPxbvxK5SQ7b8GoLZwgo4YMquEZ8o06GDUUtCKy0nVaCr/zSWT4aHUbgg2WlNQzkcGIaLOpD/pGShg3W5l7RFkWsCrniHlcyBfQJ0GDGQ69P2Bg==
ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=microsoft.com; s=arcselector10001; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-AntiSpam-MessageData-ChunkCount:X-MS-Exchange-AntiSpam-MessageData-0:X-MS-Exchange-AntiSpam-MessageData-1; bh=dSsMZr/2q64dlzk1pTDRrHlvNbzjUeeNQR0F/AnpWRU=; b=bt0MgBz4clqi0LrAp3QkEwky6T7FrX9hB8cO9l8H+KsWzuoHF6VtV7JQ6hFA41+uyq6SfmFHEBmwyZtZILEIXyNQOKJllJwBsn62+opN6DR/PX1+Qctb/oFZZoXvYKnXNgKluiHSNuUAiW259UsWJ+Qg5urRy32bV60RDMS0UP548bCktxyfLWeL+YY4+5xYkXDBJ2THCBEt5ssjB9IcTwXs0olfWgkV/qOiDVsx9mf6tVT7ustOe+qnGIuQu4UkLEwPte7sa6MUQJfVBOjWvTVSjRbmVIJmsrKdlejevyJ6DILiklkPvNAdZFQMFCwDowy4Y4afv4+P5588oIVCRA==
ARC-Authentication-Results: i=1; mx.microsoft.com 1; spf=pass smtp.mailfrom=ericsson.com; dmarc=pass action=none header.from=ericsson.com; dkim=pass header.d=ericsson.com; arc=none
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=ericsson.com; s=selector1; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-SenderADCheck; bh=dSsMZr/2q64dlzk1pTDRrHlvNbzjUeeNQR0F/AnpWRU=; b=KBnPOV/A4U6hykz6Jx25aJz745hpeF6BeE4PH31FyOuQCsd0vubOpV3LUpfh/8EfSzVGOPht821nAOW74qkYcyWEZT+gD/CvD+m+q17eqHFIk7IOtQPOhZddMVwFOdmOEYYc9QKMzuls6Dc2zBg6g7HokQM88Op6jJVbsUVGMR1/MxI+e4q9nYR8FgqfK0O8u8P9sPWZOqD4lK2sl2mgSm9b4BiRCYXlHuqCbgQuGw/V77a+J7i3j+iqaaAkvn1q51LGZRER8KTutKmvIBgyFx6Lim/hsiNkKq6k/2tI/5s0ettgDiADqjKllRmqLFcB+ypa6bNAFXhsEbWnBK+PUg==
Received: from AS4PR07MB8874.eurprd07.prod.outlook.com (2603:10a6:20b:4f5::6) by PR3PR07MB8183.eurprd07.prod.outlook.com (2603:10a6:102:176::14) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.8026.23; Wed, 9 Oct 2024 11:53:42 +0000
Received: from AS4PR07MB8874.eurprd07.prod.outlook.com ([fe80::5dc8:3768:1f55:6b14]) by AS4PR07MB8874.eurprd07.prod.outlook.com ([fe80::5dc8:3768:1f55:6b14%4]) with mapi id 15.20.8026.020; Wed, 9 Oct 2024 11:53:42 +0000
From: Magnus Westerlund <magnus.westerlund@ericsson.com>
To: Gunter Van de Velde <gunter.van_de_velde@nokia.com>, The IESG <iesg@ietf.org>
Thread-Topic: Gunter Van de Velde's Discuss on draft-ietf-avtcore-rtp-payload-registry-04: (with DISCUSS and COMMENT)
Thread-Index: AQHbGjjsWqfuuQv0j0KhRpCF6qkk1LJ+Sati
Date: Wed, 09 Oct 2024 11:53:42 +0000
Message-ID: <AS4PR07MB887405AC50E17C9880BAE786957F2@AS4PR07MB8874.eurprd07.prod.outlook.com>
References: <172847096504.101201.755252130745554400@dt-datatracker-78dc5ccf94-w8wgc>
In-Reply-To: <172847096504.101201.755252130745554400@dt-datatracker-78dc5ccf94-w8wgc>
Accept-Language: en-US, sv-SE
Content-Language: en-GB
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
authentication-results: dkim=none (message not signed) header.d=none;dmarc=none action=none header.from=ericsson.com;
x-ms-publictraffictype: Email
x-ms-traffictypediagnostic: AS4PR07MB8874:EE_|PR3PR07MB8183:EE_
x-ms-office365-filtering-correlation-id: 6b9cc6ba-e935-4898-6fa8-08dce85905c1
x-ms-exchange-senderadcheck: 1
x-ms-exchange-antispam-relay: 0
x-microsoft-antispam: BCL:0;ARA:13230040|366016|376014|1800799024|38070700018;
x-microsoft-antispam-message-info: oUqfaLiyisfzER3fK2BVlU9bCMzw9sex15fpu+mwuN0pK9DH25WD3XOm6ghAeQbTHRotRzbO0ymFraPC7Qen/UKjK+Rvb1Zx12+d7BIe6ETVBdlG1SMOscJdkPqPPpQCrlJJhUwQHKQOCB4kABMDxtbuv7SNJPQ+g55D+Lg6V5/B6HpCTtpodtRkAIJgifhVWuie9VViR2htqz45+YyxoyADi2MflMA+nygNzf6JJ4RKX8vmCaJsa2smfOaPQ39+iZuKikAA9ywME3rY5bJdgBuYdEZopdj69Pb1FvkVKSQUCuaNvGF9TbKdZHzsKLcC/7gl/XHZVcDcj89BNvD5kVMZeTc8zv8kRxtnYK9Xti+K9jXsboePduWkXLI2UsO2ak17WYP5NYph7l4ud9YM4GL6Ytr9n3zzwFVG1etAr57FX5V++5P4Ddwc+4M9s4QVtMzlcF747d3NSTDvFgBYygyuWagj9a+zVBD9x5jBX91wXkl7uFGp6Up94xEG7ZrLsM+1pF+QXeYFvMwWINjshkv4wdFEOAaoLA85pna1yR5v1emssMwdmyn/iUYCUfwVBrY+eER/DDENZ/AYqctNfzNbtgbjaAxvrk7+cHNLsWbqKR7c3PfrXp0NnKF/uwi094YIFb6h1o9XdLrlRNT2fe+wQhEIDYX+br+A8yktxbZDwFnalHxThJ2U5upcSGq2MS16oC1ZMJnp/QTEF24OHcO+BD6x0c7Re216c9B5CMcnYNGARsjDxJz5tkDWG+GIXy1qv4vl4RC1YGTxywSF0iXfFBnAsKiQBXuN06z3N+WwAYg6ADdC25Ta7z37UCjyrA1Mv1vvo2idgDFVbQSs+0lHorEnj9x3aqEVzxDbu7/mSBTHma350yV1xq/fWDmW6to0RTdVXrm+j0L0D+4dEBxGSpb7By3ojcIPb6zfneMFTN6/I1kOPflCS2QaZGnUeXfewj+9CibSlCJNPCsE0xls26bsmx/53Pa6WyLzn4n81R+bSxGY/N+YsOtZSYJ5eZ13yybA8vSpBnDNBhY4sHmcVwZ3hqcN23Etfbc1sWTcr3hrJ/cj0LGAE1dSJW9vgdV1nTzkXe+dHDCBMC3w/9xsxck3+YJ3krPC2b0Ty5zpX55s18BQaYjECKQTtYDozvxkAHNFr5WUoO9Rc/lylRN71ONlPvy+ulP2ELEpQekDp7xJGHf8rvvHD37l69kLQ3gdEE3S/98KkaBxW6sKJR89p+fmN7czAPLH5FSWO8Rl1yVO0ILmclFZL8eBdGHGmzKYDSUv8eEG7g2w2T/W9g==
x-forefront-antispam-report: CIP:255.255.255.255;CTRY:;LANG:en;SCL:1;SRV:;IPV:NLI;SFV:NSPM;H:AS4PR07MB8874.eurprd07.prod.outlook.com;PTR:;CAT:NONE;SFS:(13230040)(366016)(376014)(1800799024)(38070700018);DIR:OUT;SFP:1101;
x-ms-exchange-antispam-messagedata-chunkcount: 1
x-ms-exchange-antispam-messagedata-0: 0zNMrdKJdTxQCQ1UotvPqHzlyyy3AYQ6F/mnkmN5zmLDLL/pKzt2+7PN1GTvkBqbm73ptr4uksuBA1frmpZjqlbErCnOtPSSTp45Boriz86NHVIsmvluH6TUKcmCcl3hLMs2YzDIsQsQ9FozOYbZBDMH9Zj73a1aaT91Gw0oIURox2JKPLIxwfbc5vLEzluD9VV6/hHT+Jv1gT0A3/9FPyYIChvsidG1gBGc81bBtafamFs895+Xqj5qVANgPM+9g02gPUFdIOt3Apo2ofYLe2rub/nAI3uW1cejk7XKBW6U9ENikRoZDx+ZBlD4X34L63IPqVQWDt4mjpvEM9Q3ahZfBhkETkGeEsAU9ORCgAm7QuyNhNd21ffvZWAc0XTlSbsp7SWAeYdWw3NGmjFXfUWhbIV13Es3ZsiZdRXkrdTRjgRGGD7GJYSNWqTWzWj2tujIbQwii2eWQA3M7lAXBMI3dGpE2jZoLvdk79Fm5dRxhF8HbpyZ1IJ+J3cbJozvnTOM2rMSshF6AxNwCvwLubyue/lpN0dJ416cZtmuRE4JZF0Y523iurYTr4GaeZw7JDLv5BWQz/g44JLLFd5ED6zH8M7SWY+3bodR5W2QkUIugKVJo/pok9M70SXLFEFvbOUDVwTciUoVtQmT7PT/pCFiJH0fHI+oCn4fCfE6V2DzZd+WOjE3M/WqyrX2oXf7d4IM3Y5byOEs0orx6QP9phNuq8KROtkQun0Tu32XcwXb9x4gqFxq+V2hJ88105ok+1LrA5JtYJWFFxcjCmeEIg0TC5F5LGNafUBk7Fo9alSoKPI/vR2PQQ7fGPkMNxpHA4LS34kdpSgGwSbTI7Qif1Y24b/eguYpe4Dh3MeVImNghBe1O/m8yMDgkJO9hEmU0s2RsVl9c13LulZYZG2bsw+MkU/EbewzsXeT/DXXtz0cCh/8GuiLc5TQhZULWJGVzAuAN4GPWq0FWLyp8tCn5u4YCcq4fRCXrLnwmZbtwqdBy8WFTtUs02BQ9kfgvvfu5foE258K1MsiSRSnj0bxkyrHkDfkQ9DSG4rYNddq9csCdU/5TlXF1rxDgCcCzW3ybN2gf6kevhnRAGQKHcdclwapSOkC+yqNeSca5uCD7QEkQbziX2n4AGC+j3ZyZ8hGAvT+KHI5hAQIobzt/jlPelrv2u5VobSk61HkTkZD7W9ptfbKk82cjlpFCMoGUjSE+Esz5P5D9njqfTVKKPlX+v2wVbbVkLgdx0fhEgszKib8260ySPQO0wzypYCwQLcpVhcXP9LyPCuE0vGuwdetUb5SDUZbfjIE2+Vj1YpFX0+uHYTZkymEmb3Ra9OoYsISdY766n15mERKS4af4UqFVUQHlulGhor4+l9uWmc9GaBFa+5psbIY58bHUGe+wl2FBlEU0bQIi6yFvvTnn8v9X5U9d+vCYmSLaMCzdbfZETdndYby/zwF/cVV8ZZE2343WgyzbhUgYYqKUQIK6Kr1mN9nyQncU6xIZAElyYEQ70ImHovruDfko5AwhnWqRnptDYN2gsaVONjcBSi2/Gk/qI+8NF4IxfLm07NQjmn8jYFZbFOsUrtBtjcYyMcnICIRDMEE1WRlJ+vvkOEbXhhf4noVR0DgLUHUpujVhGTAkis=
Content-Type: multipart/alternative; boundary="_000_AS4PR07MB887405AC50E17C9880BAE786957F2AS4PR07MB8874eurp_"
MIME-Version: 1.0
X-OriginatorOrg: ericsson.com
X-MS-Exchange-CrossTenant-AuthAs: Internal
X-MS-Exchange-CrossTenant-AuthSource: AS4PR07MB8874.eurprd07.prod.outlook.com
X-MS-Exchange-CrossTenant-Network-Message-Id: 6b9cc6ba-e935-4898-6fa8-08dce85905c1
X-MS-Exchange-CrossTenant-originalarrivaltime: 09 Oct 2024 11:53:42.5727 (UTC)
X-MS-Exchange-CrossTenant-fromentityheader: Hosted
X-MS-Exchange-CrossTenant-id: 92e84ceb-fbfd-47ab-be52-080c6b87953f
X-MS-Exchange-CrossTenant-mailboxtype: HOSTED
X-MS-Exchange-CrossTenant-userprincipalname: XMAtKUVcJouSMMYZ7bRkS0FspenNafKICK6fQNsgnjxj8uPqDgF5yh0KoXNvN7dMYzCYvk62CWlt5O1TpP61qH/lLsFXRefKwL3g5njBMBg=
X-MS-Exchange-Transport-CrossTenantHeadersStamped: PR3PR07MB8183
Message-ID-Hash: VD2774AMRLSGUGQX7TCDXWRKRPHWXMCM
X-Message-ID-Hash: VD2774AMRLSGUGQX7TCDXWRKRPHWXMCM
X-MailFrom: magnus.westerlund@ericsson.com
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: "draft-ietf-avtcore-rtp-payload-registry@ietf.org" <draft-ietf-avtcore-rtp-payload-registry@ietf.org>, "avtcore-chairs@ietf.org" <avtcore-chairs@ietf.org>, "avt@ietf.org" <avt@ietf.org>
X-Mailman-Version: 3.3.9rc5
Precedence: list
Subject: [AVTCORE] Re: Gunter Van de Velde's Discuss on draft-ietf-avtcore-rtp-payload-registry-04: (with DISCUSS and COMMENT)
List-Id: Audio/Video Transport Core Maintenance <avt.ietf.org>
Archived-At: <https://mailarchive.ietf.org/arch/msg/avt/hC_7YKCMpBFBv8iTUM4U_XvLFAA>
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>

Hi Gunther,


----------------------------------------------------------------------
DISCUSS:
----------------------------------------------------------------------

# Gunter Van de Velde, RTG AD, comments for
draft-ietf-avtcore-rtp-payload-registry-04

# line numbers are derived with the idnits tool
https://eur02.safelinks.protection.outlook.com/?url=https%3A%2F%2Fauthor-tools.ietf.org%2Fapi%2Fidnits%3Furl%3Dhttps%3A%2F%2Fwww.ietf.org%2Farchive%2Fid%2Fdraft-ietf-avtcore-rtp-payload-registry-04.txt&data=05%7C02%7Cmagnus.westerlund%40ericsson.com%7Ca78bb63a11be4f73309008dce8500c12%7C92e84cebfbfd47abbe52080c6b87953f%7C0%7C0%7C638640677724667128%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C0%7C%7C%7C&sdata=2hoL78EcWvEZLZef5Azr47pPvEWnO0O9Y6XXrCILo10%3D&reserved=0<https://author-tools.ietf.org/api/idnits?url=https://www.ietf.org/archive/id/draft-ietf-avtcore-rtp-payload-registry-04.txt>

# After reviewing the document, I did not identify any significant
typographical errors. The document is short and to the point.

# idnits gives some warnings about the references

# You will find a blocking DISCUSS requesting to clarify why IETF stream
"proposed standard" was selected and 2 non-blocking comments.

#DISCUSS COMMENTS
#================

# The shepherd writeup indicates that the document is proposed Standards Track,
representing an upgrade from Informational status, driven by its impact on RFC
8008. However, a search within the document reveals no references to RFC 8008.
Additionally, the document does not define any formal procedures, nor does it
specify a protocol. Including text that explains the reasoning behind
classifying this document as a Proposed Standard instead of Informational would
enhance understanding for documentation purposes.

MW: So the level of standards track was chosen to ensure that no-one could question that this formal change to the IANA registry was reviewed at a sufficient formality level, i.e. the one of standards track. Especially as the current IANA registry claims that this was created as result of the publication of RFC 4855  (A standards track document), even if there are no instructions in this RFC for the creation. I think this registry might have been a result of some email discussion even prior to RFC 4855 (Likely around the publication RFC 3555 in 2003. Which is also a standards track document) and then been updated informally 17 years ago.

In regard to the RFC 8088 (not RFC 8008), the substituted text in this document is not intended to elevate any text in RFC 8088 or its replacement text to a higher status than Informational. If that needs to be made clear in the surrounding text to the change we can add such text.


----------------------------------------------------------------------
COMMENT:
----------------------------------------------------------------------

#DETAILED COMMENTS
#=================
## classified as [minor] and [major]

11      Abstract

13         It has been observed that specifications of new Real-time Transport
14         Protocol (RTP) payload formats often forget to specify registration
15         of the format's media type in the IANA registry "RTP Payload Formats
16         Media Types" as recommended by RFC 8088.  In practice this has no
17         real impact.  One reason is that the Media Types registry is the
18         crucial registry to register any Media Type to establish the media
19         type used to identified the format in various signaling usage.

21         This document resolves the situation by first updating the RTP
22         Payload Format Media Type registry to include all the known RTP
23         payload formats at the time of writing, then it closes this IANA
24         Registry for any future registration.  Beyond instructing IANA to
25         close this registry, the instructions to authors in RFC 8088 are
26         updated to reflect this.

[minor]

GV> What about the following rewrite making the abstract higher level
explaining the intent of the document. The valuable first paragraph seems more
at its place within an introduction section. A possible derived shortened
abstract proposal:

"
This document specifies the procedures for registering media types for
Real-time Transport Protocol (RTP) payload formats with the Internet Assigned
Numbers Authority (IANA). It updates and clarifies the guidelines for authors
defining new RTP payload formats (rfc8088), ensuring consistent and
well-documented registrations. By standardizing the registration process and
media type specifications, this document facilitates interoperability and
efficient implementation of RTP-based multimedia applications across diverse
platforms and systems. "

MW: This abstract does not represent what this document is, so not suitable as a replacement.
I can attempt a rewrite of the abstract but I think it is mostly useless extra work as people will arrive at this document using the reference in the relevant registry or from the modified document through the indication of the changes.


111        It is unclear how the "RTP Payload formats Media Types" [RTP-FORMATS]
112        registry came into existence.  The registry references [RFC4855] as
113        the instructions for this registry.  However, reviewing that RFC we
114        have been unable to find any text that defines its purpose and rules.
115        Further attempts to find how the registry was created have failed to
116        find any reference to its creation.  It is likely this was created
117        based on email or AD request.  Thus, there is no known existing
118        specification for this registry that needs to be updated when closing
119        the registry.

[minor] A small rewrite proposal to make the text more formal sounding:

"
The origins of the "RTP Payload Formats 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 or at the request of an Area Director (AD).
Consequently, there is no known existing specification for this registry that
requires updating upon its closure. "
MW: That is quite good, and can be substituted.
Cheers
Magnus Westerlund