Re: [Iptel] Re: draft-ietf-iptel-tel-reg-00 submitted

Jonathan Rosenberg <jdrosen@cisco.com> Sun, 12 February 2006 14:59 UTC

Received: from localhost.cnri.reston.va.us ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1F8Ign-0001JN-NR; Sun, 12 Feb 2006 09:59:01 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1F8Igl-0001Ii-S6 for iptel@megatron.ietf.org; Sun, 12 Feb 2006 09:58:59 -0500
Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA21386 for <iptel@ietf.org>; Sun, 12 Feb 2006 09:57:15 -0500 (EST)
Received: from rtp-iport-2.cisco.com ([64.102.122.149]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1F8IuC-0004oL-LP for iptel@ietf.org; Sun, 12 Feb 2006 10:12:52 -0500
Received: from rtp-core-2.cisco.com ([64.102.124.13]) by rtp-iport-2.cisco.com with ESMTP; 12 Feb 2006 09:58:51 -0500
X-IronPort-AV: i="4.02,105,1139202000"; d="scan'208"; a="82223972:sNHT32237348"
Received: from xbh-rtp-201.amer.cisco.com (xbh-rtp-201.cisco.com [64.102.31.12]) by rtp-core-2.cisco.com (8.12.10/8.12.6) with ESMTP id k1CEwm6H003985; Sun, 12 Feb 2006 09:58:48 -0500 (EST)
Received: from xfe-rtp-202.amer.cisco.com ([64.102.31.21]) by xbh-rtp-201.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.211); Sun, 12 Feb 2006 09:58:48 -0500
Received: from [192.168.1.101] ([10.86.242.244]) by xfe-rtp-202.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.211); Sun, 12 Feb 2006 09:58:47 -0500
Message-ID: <43EF4D27.4040209@cisco.com>
Date: Sun, 12 Feb 2006 09:58:47 -0500
From: Jonathan Rosenberg <jdrosen@cisco.com>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.7.8) Gecko/20050511
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: Cullen Jennings <fluffy@cisco.com>
Subject: Re: [Iptel] Re: draft-ietf-iptel-tel-reg-00 submitted
References: <C0127F07.709DE%fluffy@cisco.com>
In-Reply-To: <C0127F07.709DE%fluffy@cisco.com>
Content-Type: text/plain; charset="us-ascii"; format="flowed"
Content-Transfer-Encoding: 7bit
X-OriginalArrivalTime: 12 Feb 2006 14:58:47.0659 (UTC) FILETIME=[D3A67BB0:01C62FE4]
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 52f7a77164458f8c7b36b66787c853da
Content-Transfer-Encoding: 7bit
Cc: "iptel@ietf.org" <iptel@ietf.org>, "Vijay K. Gurbani" <vkg@lucent.com>, Michael P Hammer <mhammer@cisco.com>
X-BeenThere: iptel@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: IP Telephony <iptel.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/iptel>, <mailto:iptel-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www1.ietf.org/pipermail/iptel>
List-Post: <mailto:iptel@ietf.org>
List-Help: <mailto:iptel-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/iptel>, <mailto:iptel-request@ietf.org?subject=subscribe>
Sender: iptel-bounces@ietf.org
Errors-To: iptel-bounces@ietf.org

I agree that there should just be a single table in the IANA registry. 
My point in the comment is that the guidelines for people who submit an 
update to the table depends on whether they are creating a new 'row' - 
i.e., a new parameter, or just a new RFC reference for an existing 
value. In the former case, the instructions to RFC authors needs to say 
that they have to provide the parameter name, whether it has predefined 
values, and a set of RFCs. For folks adding a value to an existing 
parameter, you provide only the param name and reference to the RFC 
providing new values. IANA would be instructed to add those RFC 
references to the row in the existing table.

-Jonathan R.

Cullen Jennings wrote:

> I think I prefer one table because it would ensure that table 1 and 2 never
> conflicted. 
> 
> 
> On 2/9/06 7:44 AM, "Michael Hammer (mhammer)" <mhammer@cisco.com> wrote:
> 
> 
>>This overly bureaucratic and redundant, adding work to the IANA person
>>and adding clutter for the IANA reader.  I would suggest a single table.
>>
>>Mike 
>>
>>
>>>-----Original Message-----
>>>From: Vijay K. Gurbani [mailto:vkg@lucent.com]
>>>Sent: Thursday, February 09, 2006 10:24 AM
>>>To: Michael Hammer (mhammer)
>>>Cc: Jonathan Rosenberg (jdrosen); IETF IPTEL WG; Cullen
>>>Jennings (fluffy)
>>>Subject: Re: [Iptel] Re: draft-ietf-iptel-tel-reg-00 submitted
>>>
>>>Michael Hammer (mhammer) wrote:
>>>
>>>>Maybe I don't understand.  What is the difference between
>>>
>>>Table 1 and 2?
>>>
>>>>Table 2 appears to be a subset.  Why not just a single table?
>>>
>>>Mike: Indeed, Table 2 is a subset.  But it provides a quick
>>>visual summary on which tel URI parameters have been updated
>>>to include new values.  Plus, it imposes a cross-check to
>>>IANA registry editor while registering new values for
>>>existing URI parameters (only those parameters can have new
>>>values where the Table 1[param name, predefined value] == "Yes").
>>>
>>>Thanks,
>>>
>>>- vijay
>>>
> 
> 

-- 
Jonathan D. Rosenberg, Ph.D.                   600 Lanidex Plaza
Cisco Fellow                                   Parsippany, NJ 07054-2711
Cisco Systems
jdrosen@cisco.com                              FAX:   (973) 952-5050
http://www.jdrosen.net                         PHONE: (973) 952-5000
http://www.cisco.com

_______________________________________________
Iptel mailing list
Iptel@ietf.org
https://www1.ietf.org/mailman/listinfo/iptel