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

[Bernard Aboba <[e-mail]>]

Dale said:

"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)."

[BA] They are included in a table on that page with a sub-heading of
"Video".  The table that generates that part of the registry is here:
video.csv (iana.org)
<https://www.iana.org/assignments/media-types/video.csv>



On Wed, Aug 30, 2023 at 7:15 PM Dale R. Worley <[e-mail]> wrote:

> >> On Aug 29, 2023, at 5:34 PM, Bernard Aboba <[e-mail]>
> 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 <[e-mail]> 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
>