IETF Logo Mail Archive

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

Ted Lemon <Ted.Lemon@nominum.com> Mon, 23 December 2002 20:17 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 PAA14387 for <dhcwg-archive@odin.ietf.org>; Mon, 23 Dec 2002 15:17:18 -0500 (EST)
Received: (from mailnull@localhost) by www1.ietf.org (8.11.6/8.11.6) id gBNKKpZ01565 for dhcwg-archive@odin.ietf.org; Mon, 23 Dec 2002 15:20:51 -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 gBNKKpv01562 for <dhcwg-web-archive@optimus.ietf.org>; Mon, 23 Dec 2002 15:20:51 -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 PAA14384 for <dhcwg-web-archive@ietf.org>; Mon, 23 Dec 2002 15:16:47 -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 gBNKIOv01490; Mon, 23 Dec 2002 15:18:24 -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 gBNKHfv01474 for <dhcwg@optimus.ietf.org>; Mon, 23 Dec 2002 15:17:41 -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 PAA14318 for <dhcwg@ietf.org>; Mon, 23 Dec 2002 15:13:36 -0500 (EST)
Received: from nominum.com (dialup-64.158.80.160.Dial1.Buffalo1.Level3.net [64.158.80.160]) by toccata.fugue.com (8.11.6/8.6.11) with ESMTP id gBNKCBq19430; Mon, 23 Dec 2002 14:12:11 -0600 (CST)
Date: Mon, 23 Dec 2002 14:16:40 -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: 'Thomas Narten' <narten@us.ibm.com>, Paul Duffy <paduffy@cisco.com>, dhcwg@ietf.org
To: "Woundy, Richard" <Richard_Woundy@cable.comcast.com>
From: Ted Lemon <Ted.Lemon@nominum.com>
In-Reply-To: <6732623D2548D61193C90002A5C88DCC01EBD010@entmaexch02.broadband.att.com>
Message-Id: <72A2F8AD-16B3-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 thought we were talking about the CCC sub-option numbering space, 
> not the
> relay information option sub-option numbering space.

D'oh, sorry.   The point is still the same - we do not need as 
draconian a standard as we have for DHCP options.   WG consensus that 
the suboption is okay should be enough to allow assignment of a code - 
that is, we don't have to agree on the exact final wording of the RFC 
before you get a code.

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

v2.23.0 | Report a Bug | By Email