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

Ted Lemon <Ted.Lemon@nominum.com> Sat, 21 December 2002 00:47 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 TAA17026 for <dhcwg-archive@odin.ietf.org>; Fri, 20 Dec 2002 19:47:56 -0500 (EST)
Received: (from mailnull@localhost) by www1.ietf.org (8.11.6/8.11.6) id gBL0ovN21362 for dhcwg-archive@odin.ietf.org; Fri, 20 Dec 2002 19:50:57 -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 gBL0ouv21359 for <dhcwg-web-archive@optimus.ietf.org>; Fri, 20 Dec 2002 19:50:56 -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 TAA16942 for <dhcwg-web-archive@ietf.org>; Fri, 20 Dec 2002 19:47:25 -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 gBL0mRv21296; Fri, 20 Dec 2002 19:48:27 -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 gBL0lnv21272 for <dhcwg@optimus.ietf.org>; Fri, 20 Dec 2002 19:47:49 -0500
Received: from toccata.fugue.com (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA16891 for <dhcwg@ietf.org>; Fri, 20 Dec 2002 19:44:18 -0500 (EST)
Received: from nominum.com (dsl081-147-128.chi1.dsl.speakeasy.net [64.81.147.128]) by toccata.fugue.com (8.11.6/8.6.11) with ESMTP id gBL0hPq10240; Fri, 20 Dec 2002 18:43:25 -0600 (CST)
Date: Fri, 20 Dec 2002 18:47:19 -0600
Subject: Re: [dhcwg] draft-ietf-dhc-packetcable-04.txt
Content-Type: text/plain; charset="US-ASCII"; format="flowed"
Mime-Version: 1.0 (Apple Message framework v551)
Cc: dhcwg@ietf.org, Paul Duffy <paduffy@cisco.com>, 'Thomas Narten' <narten@us.ibm.com>
To: "Woundy, Richard" <Richard_Woundy@cable.comcast.com>
From: Ted Lemon <Ted.Lemon@nominum.com>
In-Reply-To: <6732623D2548D61193C90002A5C88DCC01EBD009@entmaexch02.broadband.att.com>
Message-Id: <C23F0518-147D-11D7-8657-00039317663C@nominum.com>
Content-Transfer-Encoding: 7bit
X-Mailer: Apple Mail (2.551)
Content-Transfer-Encoding: 7bit
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>
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit

I was under the impression that allocation for DHCP relay agent 
suboptions was not predicated on getting a draft through last call.   
The rules you're quoting are for mainline DHCP options, which are in 
short supply.   No such problem exists for relay agent suboptions.

I can't claim to speak for the WG, but if there is no conflict in the 
options that were allocated in the CableLabs draft, I don't see any 
reason why we'd want to change the numbers.

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