Re: [dhcwg] draft-ietf-dhc-packetcable-04.txt

Paul Duffy <paduffy@cisco.com> Fri, 20 December 2002 20:40 UTC

Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA09668 for <dhcwg-archive@odin.ietf.org>; Fri, 20 Dec 2002 15:40:39 -0500 (EST)
Received: (from mailnull@localhost) by www1.ietf.org (8.11.6/8.11.6) id gBKKhcW07651 for dhcwg-archive@odin.ietf.org; Fri, 20 Dec 2002 15:43:38 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gBKKhcv07648 for <dhcwg-web-archive@optimus.ietf.org>; Fri, 20 Dec 2002 15:43:38 -0500
Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA09635 for <dhcwg-web-archive@ietf.org>; Fri, 20 Dec 2002 15:40:08 -0500 (EST)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gBKKfCv07502; Fri, 20 Dec 2002 15:41:12 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gBKKeCv07468 for <dhcwg@optimus.ietf.org>; Fri, 20 Dec 2002 15:40:12 -0500
Received: from rtp-msg-core-1.cisco.com (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA09475 for <dhcwg@ietf.org>; Fri, 20 Dec 2002 15:36:42 -0500 (EST)
Received: from funnel.cisco.com (localhost [127.0.0.1]) by rtp-msg-core-1.cisco.com (8.12.2/8.12.2) with ESMTP id gBKKeHmA009795; Fri, 20 Dec 2002 15:40:17 -0500 (EST)
Received: from paduffy-w2k.cisco.com (dhcp-161-44-149-126.cisco.com [161.44.149.126]) by funnel.cisco.com (8.8.5-Cisco.1/8.6.5) with ESMTP id PAA08486; Fri, 20 Dec 2002 15:39:43 -0500 (EST)
Message-Id: <4.3.2.7.2.20021220151206.02af5130@funnel.cisco.com>
X-Sender: paduffy@funnel.cisco.com
X-Mailer: QUALCOMM Windows Eudora Version 4.3.2
Date: Fri, 20 Dec 2002 15:39:42 -0500
To: Thomas Narten <narten@us.ibm.com>
From: Paul Duffy <paduffy@cisco.com>
Subject: Re: [dhcwg] draft-ietf-dhc-packetcable-04.txt
Cc: dhcwg@ietf.org
In-Reply-To: <200212201828.gBKIS4o02210@rotala.raleigh.ibm.com>
References: <Message from Paul Duffy <paduffy@cisco.com> <4.3.2.7.2.20021220115411.02af9638@funnel.cisco.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
Sender: dhcwg-admin@ietf.org
Errors-To: dhcwg-admin@ietf.org
X-BeenThere: dhcwg@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/dhcwg>, <mailto:dhcwg-request@ietf.org?subject=unsubscribe>
List-Id: <dhcwg.ietf.org>
List-Post: <mailto:dhcwg@ietf.org>
List-Help: <mailto:dhcwg-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/dhcwg>, <mailto:dhcwg-request@ietf.org?subject=subscribe>

...inline....

>Ave you had a chance to look at
>draft-narten-iana-experimental-allocations-02.txt?  Does this address
>any of your concerns? (Or do I still not really understand the
>concerns behind this?)

Not sure this helps...


> > Cablelabs intends to place any new sub-option additions before IETF for
> > approval (witness the recent submission of sub-option 51), but we STRONGLY
> > would prefer to be allowed to assign the sub-option codes.  It will make
> > life a bit easier for the component manufacturers, compliance
> > testing, etc.
>
>In other words, you want the option number for implementations before
>the ID has been reviewed and finallized by the community.  Isn't this
>what led to the situation with the current document having sat around
>for two years before it became urgent to finalize it (and then oops,
>we've already done it this way, now it's painful to change...). I'll
>note that the -00 version of this ID appeared in March of 2000.

Is the intent here that IETF wants to insure the sub-option number DOES 
change (from experimental to official) when a CCC sub-option draft reaches 
RFC?  Forcing a change in the implementations?  If that is the case, then 
this discussion is over and Cablelabs will need to agree to your proposal.

Cheers,








--

Paul Duffy
Cisco Systems, Inc.
paduffy@cisco.com


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