Re: [AVTCORE] New Version Notification for draft-wu-avtcore-dynamic-pt-usage-00.txt

Adam Roach <adam@nostrum.com> Tue, 14 January 2014 20:06 UTC

Return-Path: <adam@nostrum.com>
X-Original-To: avt@ietfa.amsl.com
Delivered-To: avt@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 4AECE1AE1B0 for <avt@ietfa.amsl.com>; Tue, 14 Jan 2014 12:06:48 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.035
X-Spam-Level:
X-Spam-Status: No, score=-1.035 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HELO_MISMATCH_COM=0.553, HOST_MISMATCH_NET=0.311, HTML_MESSAGE=0.001] autolearn=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 291PtVgaRYDM for <avt@ietfa.amsl.com>; Tue, 14 Jan 2014 12:06:47 -0800 (PST)
Received: from shaman.nostrum.com (nostrum-pt.tunnel.tserv2.fmt.ipv6.he.net [IPv6:2001:470:1f03:267::2]) by ietfa.amsl.com (Postfix) with ESMTP id 289041AE1A5 for <avt@ietf.org>; Tue, 14 Jan 2014 12:06:47 -0800 (PST)
Received: from orochi-2.roach.at (99-152-145-110.lightspeed.dllstx.sbcglobal.net [99.152.145.110]) (authenticated bits=0) by shaman.nostrum.com (8.14.3/8.14.3) with ESMTP id s0EK6N8A077025 (version=TLSv1/SSLv3 cipher=DHE-RSA-CAMELLIA256-SHA bits=256 verify=NO); Tue, 14 Jan 2014 14:06:24 -0600 (CST) (envelope-from adam@nostrum.com)
Message-ID: <52D598BA.6050201@nostrum.com>
Date: Tue, 14 Jan 2014 14:06:18 -0600
From: Adam Roach <adam@nostrum.com>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.8; rv:24.0) Gecko/20100101 Thunderbird/24.2.0
MIME-Version: 1.0
To: Colin Perkins <csp@csperkins.org>, Roni Even <ron.even.tlv@gmail.com>
References: <20130830162909.20422.68365.idtracker@ietfa.amsl.com> <008201cea59e$aa9fd3a0$ffdf7ae0$@gmail.com> <5EAB5396-57ED-4B29-9FEF-0CAF92F27052@csperkins.org> <015a01cea7d3$62c3cbe0$284b63a0$@gmail.com> <5C7CBAD2-4340-4A7B-8D55-8E56AB2DE07E@csperkins.org> <031001cea92f$df4ff780$9defe680$@gmail.com> <CC2F3FEA-263D-4754-8D98-E5BA423F5988@csperkins.org>
In-Reply-To: <CC2F3FEA-263D-4754-8D98-E5BA423F5988@csperkins.org>
Content-Type: multipart/alternative; boundary="------------010607060304070309040209"
Received-SPF: pass (shaman.nostrum.com: 99.152.145.110 is authenticated by a trusted mechanism)
Cc: "rai-ads@tools.ietf.org" <rai-ads@tools.ietf.org>, avt@ietf.org
Subject: Re: [AVTCORE] New Version Notification for draft-wu-avtcore-dynamic-pt-usage-00.txt
X-BeenThere: avt@ietf.org
X-Mailman-Version: 2.1.15
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: <http://www.ietf.org/mail-archive/web/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: Tue, 14 Jan 2014 20:06:48 -0000

On 9/4/13 17:13, Colin Perkins wrote:
> I really don't think you need a new draft to update this table. There 
> is an existing RFC that reserves those payload types; just ask IANA to 
> make the correction to the registry.

I agree. I think this is a simple administrative action to update the 
registry to match the facts on the ground as documented by the 
already-published RFC 5761. I think that either the AVT chairs or the 
RAI ADs would be well within process to ask the IANA to fix the registry 
to match currently published RFCs; we do stuff like this all the time 
when oversights in registries are spotted.

If we want to also publish a PT guidance document, great. I think that 
would be useful, too. But we don't need to predicate fixing the registry 
to match the already-published RFCs on having that document finished.

/a