[media-types] Re: Conclusion of indication of RTP Payload fo rmats in Media Types registry

Harald Alvestrand <[email protected]>
Newsgroups gmane.ietf.types
Message-ID <[email protected]>
On 7/25/25 10:36, Magnus Westerlund wrote:
> AVTCORE and Mediaman
> 
> In today’s 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 
> <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 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.
> 
> It is important to note that RTP payload formats are still detectable if 
> one look at their Media Types registration as they use both Encoding: 
> framed, as well as Restriction and usages. However, for older RTP 
> payload types this has not be consistently applied.
> 
> Mark Nottingham also asked if AVTCORE could not create a new registry 
> for RTP Payload types to correctly include all that are RTP payload types?
> 
>  From my perspective this is possible. 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 added to the Media Types registry one can avoid mistakes as IANA 
> will follow the rules for the new registry and ensure consistency.

Note: This rule will not prevent the situation where a payload type is 
registered in the media types registry and not in the RTP payload format 
registry. I think we have a few examples of that in the old registry too.

> 
> 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 the following:
> 
> Write new registration rules for RTP payload format that defines a new 
> registry, the registry rules for this registry are:
> 
>   * Request registration in the new registry that list media type and
>     reference
>   * 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
> 
> 
> _______________________________________________
> media-types mailing list -- [email protected]
> To unsubscribe send an email to [email protected]

_______________________________________________
media-types mailing list -- [email protected]
To unsubscribe send an email to [email protected]
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.