From nobody Wed Aug 30 20:21:58 2023 Return-Path: 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 6EF61C14CE47 for ; Wed, 30 Aug 2023 20:21:57 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -2.103 X-Spam-Level: X-Spam-Status: No, score=-2.103 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_BLOCKED=0.001, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, T_SCC_BODY_TEXT_LINE=-0.01, URIBL_BLOCKED=0.001, 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=gmail.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 FrZJ4JrL1XjC for ; Wed, 30 Aug 2023 20:21:53 -0700 (PDT) Received: from mail-oa1-x30.google.com (mail-oa1-x30.google.com [IPv6:2001:4860:4864:20::30]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits) server-digest SHA256) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 93F6BC14CE46 for ; Wed, 30 Aug 2023 20:21:53 -0700 (PDT) Received: by mail-oa1-x30.google.com with SMTP id 586e51a60fabf-1cc61f514baso165904fac.1 for ; Wed, 30 Aug 2023 20:21:53 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20221208; t=1693452113; x=1694056913; darn=ietf.org; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:from:to:cc:subject:date:message-id:reply-to; bh=LPFWnX+ILYlXWSvc39zkX18jMRK5c66JWB/Ui0eSCFY=; b=QwIKLElwUmGKrfCqGA4i5WSKpMNh0BtTzeEy7bSMfQZm/nAOJHSWkXn/1DU0EBublB 319l/JPXpdFrvhX7TVXUUy9aOHRzjY+xL7uzy5V2SO15M5lrO8oXg+8EMEAxRWgPcwMQ c4la+eFo+PEI4Jq/f+MPeSYQ3OFLqsL7GwFQD+3aWotMBoehcuclKo05OvMiDG/nPfEY +vf3t1lKoKBvOqhJ7cuBPRX9s2Ke0I0PrvOmMhXfBEQX+EL1M2HXHtBxjCTcvVl+Iusj FfFCfi0fbE49QOblxQ38Kz9sgNM2tFJMPre8sYAxLl/ugxlq10i8R/AnYtVngjh1GuLp XMmg== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20221208; t=1693452113; x=1694056913; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:x-gm-message-state:from:to:cc:subject:date:message-id :reply-to; bh=LPFWnX+ILYlXWSvc39zkX18jMRK5c66JWB/Ui0eSCFY=; b=kgWarPRLTSH6Bpf+o1zqwVmhsCIlQm0DbTEOKIj7Z0owEY9L1XQSuvC2crd1Iu5T+G m/R0x8e6EcJwmxZq80k3fpziIQSEYHyedg3y4EGLI7X9hVaVD7qY4USJ1vGOHeu7gqnX b+70/Sk3HPDktCPhlixBVKFXlbltdlU4w5abDjV8jfA4XzuAEJxFnUfelop1+xeUtfPE 5W+lUIQAsD/a3nO6a1sung/6V9P2qjQBKMj2P3quDMDbS7TclHvr8D3bswiBxxYJ9hm7 9crTaHewjNnRfNR4WSEpKp2+mtFLI8/bgfomB44P0ZZuekRyScDx8AXmrZjps83ocJg2 Ba+g== X-Gm-Message-State: AOJu0YzPMQZrnnrKnpyzaIDl2zQt+ZSL1wCVbsZzdsUxzwq0dEgfvj8z Sp5GTVWGJnrWzL1/T+wxURx/SMC8Vn3AbuEvcNE= X-Google-Smtp-Source: AGHT+IFbANnLwO7vIirOyBnA7IWDJDk/MnpDOMNyjvK7fHEtCscrL8mIhfFXm63fWpJp9JvyCH0CfgJlRB6XnWRJXEY= X-Received: by 2002:a05:6870:c58e:b0:1c0:1424:5e6c with SMTP id ba14-20020a056870c58e00b001c014245e6cmr4696448oab.17.1693452112600; Wed, 30 Aug 2023 20:21:52 -0700 (PDT) MIME-Version: 1.0 References: <5F9677DC-1631-4588-A2A4-2673B8E82042@8x8.com> <87v8cw9cvq.fsf@hobgoblin.ariadne.com> In-Reply-To: <87v8cw9cvq.fsf@hobgoblin.ariadne.com> From: Bernard Aboba Date: Wed, 30 Aug 2023 20:21:41 -0700 Message-ID: To: "Dale R. Worley" Cc: Jonathan Lennox , avt@ietf.org, philipp.hancke@gmail.com Content-Type: multipart/alternative; boundary="0000000000009da50206042f8bb1" Archived-At: 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 List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 31 Aug 2023 03:21:57 -0000 --0000000000009da50206042f8bb1 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable 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) On Wed, Aug 30, 2023 at 7:15=E2=80=AFPM Dale R. Worley = wrote: > >> On Aug 29, 2023, at 5:34 PM, Bernard Aboba > 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 writes: > > I guess the first question would be, is the =E2=80=9CRTP Payload Format= Media > > Types=E2=80=9D table actually useful to anyone? If not, I=E2=80=99d su= ggest 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 > --0000000000009da50206042f8bb1 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
Dale said:=C2=A0

"Actually, HEVC a= nd VVC are *not* in
https://www.i= ana.org/assignments/media-types/media-types.xhtml=C2=A0(as of
T= hu Aug 31 02:09:08 AM UTC 2023)."

[BA] They a= re included in a table on that page with a sub-heading of "Video"= .=C2=A0 The table that generates that part of the registry is here:=C2=A0



=
On Wed, Au= g 30, 2023 at 7:15=E2=80=AFPM Dale R. Worley <worley@ariadne.com> wrote:
>> On Aug 29, 2023, at 5:34 PM, Bernard= Aboba <ber= nard.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-paramete= rs-2
>>
>> However, they are registered in the mime-types registry under vide= o:
>> https://www.iana.org/assignme= nts/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 =E2=80=9CRTP Payload Forma= t Media
> Types=E2=80=9D table actually useful to anyone?=C2=A0 If not, I=E2=80= =99d 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<= br> > 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.=C2=A0 The S= DP
rtpmap "encoding name" is always the same as the media subtype, b= ut SDP
also requires documenting how the encoding parameters are to be
specified in the rtpmap attribute.

Dale
--0000000000009da50206042f8bb1--