[media-types] Conclusion of indication of RTP Payload formats in Media Types registry
Magnus Westerlund <[email protected]> Fri, 25 Jul 2025 08:36:37 +0000
| Newsgroups | gmane.ietf.types,gmane.ietf.avt |
|---|---|
| Message-ID | <AS4PR07MB8874B363DA944219C38F85A99559A@AS4PR07MB8874.eurprd07.prod.outlook.com> |
--===============7484617216781560943==
Content-Language: en-GB
Content-Type: multipart/alternative;
boundary="_000_AS4PR07MB8874B363DA944219C38F85A99559AAS4PR07MB8874eurp_"
--_000_AS4PR07MB8874B363DA944219C38F85A99559AAS4PR07MB8874eurp_
Content-Type: text/plain; charset="Windows-1252"
Content-Transfer-Encoding: quoted-printable
AVTCORE and Mediaman
In today=92s Mediaman WG meeting the question of indication of RTP payload =
format in the IANA Media Type registry was discussed. The github issue for =
this issue: https://github.com/ietf-wg-mediaman/6838bis/issues/18
The problem with adding an indication in the IANA table is that it creates =
a precedence of having information in the table that is only useful for a p=
articular user set of the media types, and not everyone. I see the issues w=
ith this. The conclusion of the issue was to close it without any further c=
hanges to media types registration rule or the registry.
It is important to note that RTP payload formats are still detectable if on=
e look at their Media Types registration as they use both Encoding: framed,=
as well as Restriction and usages. However, for older RTP payload types th=
is has not be consistently applied.
Mark Nottingham also asked if AVTCORE could not create a new registry for R=
TP Payload types to correctly include all that are RTP payload types?
>From my perspective this is possible. There is a construction that could en=
sure that in the future one do not miss to registration in both registries.=
If the RTP Payload format only register in the new registry and that regis=
try has a rule that any registration in this table MUST be first added to t=
he Media Types registry one can avoid mistakes as IANA will follow the rule=
s for the new registry and ensure consistency.
So the above would be if there are significant value to have a single table=
that contains all RTP payload formats. If that is desirable the actions fo=
r someone in AVTCORE would be the following:
Write new registration rules for RTP payload format that defines a new regi=
stry, the registry rules for this registry are:
* Request registration in the new registry that list media type and ref=
erence
* Registratnts must create a filled in Media Type registry request that=
can complete the Media Types registration process including expert review =
in applicable cases.
* Registaration in this registry require that IANA request Media Types =
registration for the request type
* If the registration is granted IESG or Expert approval then the entry=
is added to the new registry.
I am not volunteering to write this document.
Cheers
Magnus Westerlund
--_000_AS4PR07MB8874B363DA944219C38F85A99559AAS4PR07MB8874eurp_
Content-Type: text/html; charset="Windows-1252"
Content-Transfer-Encoding: quoted-printable
<html xmlns:o=3D"urn:schemas-microsoft-com:office:office" xmlns:w=3D"urn:sc=
hemas-microsoft-com:office:word" xmlns:m=3D"http://schemas.microsoft.com/of=
fice/2004/12/omml" xmlns=3D"http://www.w3.org/TR/REC-html40">
<head>
<meta http-equiv=3D"Content-Type" content=3D"text/html; charset=3DWindows-1=
252">
<meta name=3D"Generator" content=3D"Microsoft Word 15 (filtered medium)">
<style><!--
/* Font Definitions */
@font-face
{font-family:Wingdings;
panose-1:5 0 0 0 0 0 0 0 0 0;}
@font-face
{font-family:"Cambria Math";
panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
{font-family:Aptos;
panose-1:2 11 6 4 2 2 2 2 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0cm;
font-size:11.0pt;
font-family:"Aptos",sans-serif;
mso-ligatures:standardcontextual;
mso-fareast-language:EN-US;}
a:link, span.MsoHyperlink
{mso-style-priority:99;
color:#467886;
text-decoration:underline;}
p.MsoListParagraph, li.MsoListParagraph, div.MsoListParagraph
{mso-style-priority:34;
margin-top:0cm;
margin-right:0cm;
margin-bottom:0cm;
margin-left:36.0pt;
font-size:11.0pt;
font-family:"Aptos",sans-serif;
mso-ligatures:standardcontextual;
mso-fareast-language:EN-US;}
span.EmailStyle17
{mso-style-type:personal-compose;
font-family:"Aptos",sans-serif;
color:windowtext;}
.MsoChpDefault
{mso-style-type:export-only;
font-size:11.0pt;
mso-fareast-language:EN-US;}
@page WordSection1
{size:612.0pt 792.0pt;
margin:72.0pt 72.0pt 72.0pt 72.0pt;}
div.WordSection1
{page:WordSection1;}
/* List Definitions */
@list l0
{mso-list-id:1794590218;
mso-list-type:hybrid;
mso-list-template-ids:-919303204 1326190630 134807555 134807557 134807553 =
134807555 134807557 134807553 134807555 134807557;}
@list l0:level1
{mso-level-start-at:1030;
mso-level-number-format:bullet;
mso-level-text:-;
mso-level-tab-stop:none;
mso-level-number-position:left;
margin-left:18.0pt;
text-indent:-18.0pt;
font-family:"Aptos",sans-serif;
mso-fareast-font-family:Aptos;
mso-bidi-font-family:"Times New Roman";}
@list l0:level2
{mso-level-number-format:bullet;
mso-level-text:o;
mso-level-tab-stop:none;
mso-level-number-position:left;
margin-left:54.0pt;
text-indent:-18.0pt;
font-family:"Courier New";}
@list l0:level3
{mso-level-number-format:bullet;
mso-level-text:\F0A7 ;
mso-level-tab-stop:none;
mso-level-number-position:left;
margin-left:90.0pt;
text-indent:-18.0pt;
font-family:Wingdings;}
@list l0:level4
{mso-level-number-format:bullet;
mso-level-text:\F0B7 ;
mso-level-tab-stop:none;
mso-level-number-position:left;
margin-left:126.0pt;
text-indent:-18.0pt;
font-family:Symbol;}
@list l0:level5
{mso-level-number-format:bullet;
mso-level-text:o;
mso-level-tab-stop:none;
mso-level-number-position:left;
margin-left:162.0pt;
text-indent:-18.0pt;
font-family:"Courier New";}
@list l0:level6
{mso-level-number-format:bullet;
mso-level-text:\F0A7 ;
mso-level-tab-stop:none;
mso-level-number-position:left;
margin-left:198.0pt;
text-indent:-18.0pt;
font-family:Wingdings;}
@list l0:level7
{mso-level-number-format:bullet;
mso-level-text:\F0B7 ;
mso-level-tab-stop:none;
mso-level-number-position:left;
margin-left:234.0pt;
text-indent:-18.0pt;
font-family:Symbol;}
@list l0:level8
{mso-level-number-format:bullet;
mso-level-text:o;
mso-level-tab-stop:none;
mso-level-number-position:left;
margin-left:270.0pt;
text-indent:-18.0pt;
font-family:"Courier New";}
@list l0:level9
{mso-level-number-format:bullet;
mso-level-text:\F0A7 ;
mso-level-tab-stop:none;
mso-level-number-position:left;
margin-left:306.0pt;
text-indent:-18.0pt;
font-family:Wingdings;}
ol
{margin-bottom:0cm;}
ul
{margin-bottom:0cm;}
--></style>
</head>
<body lang=3D"en-SE" link=3D"#467886" vlink=3D"#96607D" style=3D"word-wrap:=
break-word">
<div class=3D"WordSection1">
<p class=3D"MsoNormal"><span lang=3D"EN-GB">AVTCORE and Mediaman<o:p></o:p>=
</span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-GB"><o:p> </o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-GB">In today=92s Mediaman WG meetin=
g the question of indication of RTP payload format in the IANA Media Type r=
egistry was discussed. The github issue for this issue:
<a href=3D"https://github.com/ietf-wg-mediaman/6838bis/issues/18">https://g=
ithub.com/ietf-wg-mediaman/6838bis/issues/18</a><o:p></o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-GB"><o:p> </o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-GB">The problem with adding an indi=
cation in the IANA table is that it creates a precedence of having informat=
ion in the table that is only useful for a particular user set of the media=
types, and not everyone. I see the
issues with this. The conclusion of the issue was to close it without any =
further changes to media types registration rule or the registry.<o:p></o:p=
></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-GB"><o:p> </o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-GB">It is important to note that RT=
P payload formats are still detectable if one look at their Media Types reg=
istration as they use both Encoding: framed, as well as Restriction and usa=
ges. However, for older RTP payload
types this has not be consistently applied. <o:p></o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-GB"><o:p> </o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-GB">Mark Nottingham also asked if A=
VTCORE could not create a new registry for RTP Payload types to correctly i=
nclude all that are RTP payload types?
<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-GB"><o:p> </o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-GB">From my perspective this is pos=
sible. There is a construction that could ensure that in the future one do =
not miss to registration in both registries. If the RTP Payload format only=
register in the new registry and that
registry has a rule that any registration in this table MUST be first adde=
d to the Media Types registry one can avoid mistakes as IANA will follow th=
e rules for the new registry and ensure consistency.
<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-GB"><o:p> </o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-GB">So the above would be if there =
are significant value to have a single table that contains all RTP payload =
formats. If that is desirable the actions for someone in AVTCORE would be t=
he following:<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-GB"><o:p> </o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-GB">Write new registration rules fo=
r RTP payload format that defines a new registry, the registry rules for th=
is registry are:<o:p></o:p></span></p>
<ul style=3D"margin-top:0cm" type=3D"disc">
<li class=3D"MsoListParagraph" style=3D"margin-left:-18.0pt;mso-list:l0 lev=
el1 lfo1">
<span lang=3D"EN-GB">Request registration in the new registry that list med=
ia type and reference<o:p></o:p></span></li><li class=3D"MsoListParagraph" =
style=3D"margin-left:-18.0pt;mso-list:l0 level1 lfo1">
<span lang=3D"EN-GB">Registratnts must create a filled in Media Type regist=
ry request that can complete the Media Types registration process including=
expert review in applicable cases.
<o:p></o:p></span></li><li class=3D"MsoListParagraph" style=3D"margin-left:=
-18.0pt;mso-list:l0 level1 lfo1">
<span lang=3D"EN-GB">Registaration in this registry require that IANA reque=
st Media Types registration for the request type<o:p></o:p></span></li><li =
class=3D"MsoListParagraph" style=3D"margin-left:-18.0pt;mso-list:l0 level1 =
lfo1">
<span lang=3D"EN-GB">If the registration is granted IESG or Expert approval=
then the entry is added to the new registry.<o:p></o:p></span></li></ul>
<p class=3D"MsoNormal"><span lang=3D"EN-GB"><o:p> </o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-GB">I am not volunteering to write =
this document.<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-GB"><o:p> </o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-GB">Cheers<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-GB"><o:p> </o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-GB">Magnus Westerlund <o:p></o:p></=
span></p>
</div>
</body>
</html>
--_000_AS4PR07MB8874B363DA944219C38F85A99559AAS4PR07MB8874eurp_--
--===============7484617216781560943==
Content-Type: text/plain; charset="utf-8"
MIME-Version: 1.0
Content-Transfer-Encoding: base64
Content-Disposition: inline
X19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX18KbWVkaWEtdHlw
ZXMgbWFpbGluZyBsaXN0IC0tIG1lZGlhLXR5cGVzQGlldGYub3JnClRvIHVuc3Vic2NyaWJlIHNl
bmQgYW4gZW1haWwgdG8gbWVkaWEtdHlwZXMtbGVhdmVAaWV0Zi5vcmcK
--===============7484617216781560943==--