IETF Logo Mail Archive

Re: [AVTCORE] New Version Notification for draft-westerlund-avtcore-rtp-payload-registry-00.txt

Ron Even <ron.even.tlv@gmail.com> Sun, 14 April 2024 15:43 UTC

Return-Path: <ron.even.tlv@gmail.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 70CDCC14F5FF for <avt@ietfa.amsl.com>; Sun, 14 Apr 2024 08:43:49 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.094
X-Spam-Level:
X-Spam-Status: No, score=-2.094 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_NONE=-0.0001, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, 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 8UkysI0diJSx for <avt@ietfa.amsl.com>; Sun, 14 Apr 2024 08:43:44 -0700 (PDT)
Received: from mail-pf1-x434.google.com (mail-pf1-x434.google.com [IPv6:2607:f8b0:4864:20::434]) (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 ED886C14F5F4 for <avt@ietf.org>; Sun, 14 Apr 2024 08:43:44 -0700 (PDT)
Received: by mail-pf1-x434.google.com with SMTP id d2e1a72fcca58-6ed0e9ccca1so2175061b3a.0 for <avt@ietf.org>; Sun, 14 Apr 2024 08:43:44 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20230601; t=1713109424; x=1713714224; 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=434D+K9Ua89/+LDmODI+RmfsqDPVdPqPc+q44tOrr/g=; b=WSYavpu5Juodn6jU5wT5Se1DiztbGJJBDPBTImajOGnrIGGz4STSPljqI3ZeL+lbCk HkWsNRNTn8QQnymmSCYUbtAlRYqDn+k56mNwPfEgYPkDPisjr+kLmPuMFKtyug53Mv0y J99aRwYz/hTHGYjegAUzIfN8zM6RHMTniY9OSDb40aYbtkXV08K0RTVOmLunD2tI1RkV Q0iKC8KU8YRxEj7cc+vbJ/u7rwPFrFGjZP37zB3sSLEHKdfhol9ALow91+/M6LcnzlqQ VZCTNrrijnRyUurq2KdiN+kFVdpO4qm6qo0mXUCL49kxpq7mFoYcst9ILdcMoJWQzc8l AZpg==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1713109424; x=1713714224; 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=434D+K9Ua89/+LDmODI+RmfsqDPVdPqPc+q44tOrr/g=; b=nM+qmzVtmFFeC5rpr5E9E9YVWi7OXeFvA6q91noLbpOm/9SEwipKOyjVQRfNHtKvFj NX3kWNjFzrxb1iV/Cm2EplEx7GLC2wsYs+53UkjG4ntFr8+mQ+c9AL+wOq6GI83mG9NR fF+5sd7EK6IEcOniSIVJLZ/lNrqneoRlXFeyoyFD9bPmp58Iq6ZDk6Qxah0o2EL1IdQj Uhg3rIWNDnlEiGwnBjqOcdbXh2KMA+0yG7OaLlKz3QrOjwwOhfYIPhOMB3I5uPzVScDI GVL+mjJ9ArVXRnGOSIvZAV2QKxj68iq9G1udigy+LChy54HFDkEJkxv9ym5zvU67e73P 1IoA==
X-Gm-Message-State: AOJu0Yw1ByVT1ek6ZHoPZQgascWN4LRTAcKFqctQrrmOakO3WFx0Veoh dB1G6PhJxuXo+htaHMCbZx76jwaJTpWeb8ZKweF5Dpca3Mk0lNpkmtaOPxVwH7mKPA3ZyMntzcp NBTwNdsY7lwIw7V9uTwWPJZYbxbXHqQ==
X-Google-Smtp-Source: AGHT+IGc5/yHsq6JpCWor5vLxVKXslCy17UEmYmhmLAi/xObQr7BjOHyhLQeYCjZhe4FQ9dfIMkSsdFqd1TtWZD8qH8=
X-Received: by 2002:a05:6a20:3250:b0:1a7:6044:88f7 with SMTP id hm16-20020a056a20325000b001a7604488f7mr5996642pzc.30.1713109424013; Sun, 14 Apr 2024 08:43:44 -0700 (PDT)
MIME-Version: 1.0
References: <AS4PR07MB887457CBA232B99AD20E9255953E2@AS4PR07MB8874.eurprd07.prod.outlook.com>
In-Reply-To: <AS4PR07MB887457CBA232B99AD20E9255953E2@AS4PR07MB8874.eurprd07.prod.outlook.com>
From: Ron Even <ron.even.tlv@gmail.com>
Date: Sun, 14 Apr 2024 18:43:32 +0300
Message-ID: <CAHy0fzBUi8CN6aRU+Vt+4x6o13S0txRMVi4-GJrbAd0ERqVUNA@mail.gmail.com>
To: Magnus Westerlund <magnus.westerlund=40ericsson.com@dmarc.ietf.org>
Cc: "avt@ietf.org" <avt@ietf.org>
Content-Type: multipart/alternative; boundary="000000000000ae11680616105e4f"
Archived-At: <https://mailarchive.ietf.org/arch/msg/avt/uBHN7uuhd-VJXRGnOLG9rCakK7Y>
Subject: Re: [AVTCORE] New Version Notification for draft-westerlund-avtcore-rtp-payload-registry-00.txt
X-BeenThere: avt@ietf.org
X-Mailman-Version: 2.1.39
Precedence: list
List-Id: Audio/Video Transport Core Maintenance <avt.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/avt>, <mailto:avt-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/avt/>
List-Post: <mailto:avt@ietf.org>
List-Help: <mailto:avt-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/avt>, <mailto:avt-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sun, 14 Apr 2024 15:43:49 -0000

Hi Magnus,
I agree that it make sense to close the RTP Payload Type registry. The
media type registry has in the notes the following sentence “additional
 procedures for registering media types for transfer via RTP can be found
in [RFC4855]” . This sentence still applies except for the registration in
the RTP payload type registry, for example the need for SDP procedure. This
is for the case when registering RTP payload not via the IETF.
The comment is if the media type registry will be updated based on work in
the Mediaman WG
BR
Roni Even

On Tue, 2 Apr 2024 at 12:07 Magnus Westerlund <magnus.westerlund=
40ericsson.com@dmarc.ietf.org> wrote:

> Hi AVTCORE,
>
>
>
> I have now submitted my very short draft that tries to clean up the
> situation around the RTP Payload Type registry. Please review and I think
> if people agree to this adminstrative action we should go on an adopt this
> as a WG item.
>
>
>
> Cheers
>
>
>
> Magnus  Westerlund
>
>
>
>
>
> A new version of Internet-Draft
> draft-westerlund-avtcore-rtp-payload-registry-00.txt has been successfully
> submitted by Magnus Westerlund and posted to the
> IETF repository.
>
> Name:     draft-westerlund-avtcore-rtp-payload-registry
> Revision: 00
> Title:    Closing the RTP Payload Format Media Types IANA Registry
> Date:     2024-04-02
> Group:    Individual Submission
> Pages:    5
> URL:
> https://www.ietf.org/archive/id/draft-westerlund-avtcore-rtp-payload-registry-00.txt
>
>  Status:
> https://datatracker.ietf.org/doc/draft-westerlund-avtcore-rtp-payload-registry/
> HTML:
> https://www.ietf.org/archive/id/draft-westerlund-avtcore-rtp-payload-registry-00.html
>
> HTMLized:
> https://datatracker.ietf.org/doc/html/draft-westerlund-avtcore-rtp-payload-registry-00
>
> Abstract:
>
>    It has been observed that specifications of new RTP payload formats
>    often forget to register themselves in the IANA regsitry "RTP Payload
>    Formats Media Types".  In practice this has no real impact.  One
>    reason is that the Media Types registry is the crucial regsistry to
>    register any Media Type to establish the media type used to
>    identified the format in various signalling usage.
>
>    To resolve this sitaution this document performs the following.
>    First it updates the registry to include known RTP payload formats at
>    the time of writing.  Then it closes the IANA Registry for RTP
>    Payload formats Media Types for future registration.  Beyond
>    instructing IANA to close this registry the instructions to authors
>    in RFC 8088 are updated that registration is no longer required in
>    the closed registry.
>
>
>
> The IETF Secretariat
> _______________________________________________
> Audio/Video Transport Core Maintenance
> avt@ietf.org
> https://www.ietf.org/mailman/listinfo/avt
>

v2.23.0 | Report a Bug | By Email