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

Cullen Jennings <fluffy@cisco.com> Sat, 11 February 2006 01: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 1F7k2f-00073n-Ax; Fri, 10 Feb 2006 20:59:17 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1F7k2b-00072S-7p for iptel@megatron.ietf.org; Fri, 10 Feb 2006 20:59:15 -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 UAA28917 for <iptel@ietf.org>; Fri, 10 Feb 2006 20:57:22 -0500 (EST)
Received: from sj-iport-4.cisco.com ([171.68.10.86]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1F7kFY-0004RO-Dj for iptel@ietf.org; Fri, 10 Feb 2006 21:12:38 -0500
Received: from sj-core-4.cisco.com ([171.68.223.138]) by sj-iport-4.cisco.com with ESMTP; 10 Feb 2006 17:58:55 -0800
X-IronPort-AV: i="4.02,104,1139212800"; d="scan'208"; a="1775453277:sNHT30323176"
Received: from vtg-um-e2k4.sj21ad.cisco.com (vtg-um-e2k4.cisco.com [171.70.93.57]) by sj-core-4.cisco.com (8.12.10/8.12.6) with ESMTP id k1B1wrQJ013312; Fri, 10 Feb 2006 17:58:53 -0800 (PST)
Received: from 10.21.89.139 ([10.21.89.139]) by vtg-um-e2k4.sj21ad.cisco.com ([171.70.93.57]) with Microsoft Exchange Server HTTP-DAV ; Sat, 11 Feb 2006 01:58:53 +0000
User-Agent: Microsoft-Entourage/11.2.1.051004
Date: Fri, 10 Feb 2006 17:33:59 -0800
Subject: Re: [Iptel] Re: draft-ietf-iptel-tel-reg-00 submitted
From: Cullen Jennings <fluffy@cisco.com>
To: Michael P Hammer <mhammer@cisco.com>, "Vijay K. Gurbani" <vkg@lucent.com>
Message-ID: <C0127F07.709DE%fluffy@cisco.com>
Thread-Topic: [Iptel] Re: draft-ietf-iptel-tel-reg-00 submitted
Thread-Index: AcYtjNdKVETpwT9mTJCsQA9Tr9U2lAAAqXpgAEbvcIQ=
In-Reply-To: <072C5B76F7CEAB488172C6F64B30B5E3010FA25B@xmb-rtp-20b.amer.cisco.com>
Mime-version: 1.0
Content-type: text/plain; charset="US-ASCII"
Content-transfer-encoding: 7bit
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 52e1467c2184c31006318542db5614d5
Content-Transfer-Encoding: 7bit
Cc: "iptel@ietf.org" <iptel@ietf.org>
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 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
>> 

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