Re: [dhcwg] dhc WG last call on draft-ietf-dhc-reclassify-options-00

Ralph Droms <rdroms@cisco.com> Fri, 09 April 2004 00:04 UTC

Received: from optimus.ietf.org (optimus.ietf.org [132.151.1.19]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id UAA13129 for <dhcwg-archive@odin.ietf.org>; Thu, 8 Apr 2004 20:04:32 -0400 (EDT)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1BBjV5-0000pl-5y for dhcwg-archive@odin.ietf.org; Thu, 08 Apr 2004 20:04:03 -0400
Received: (from exim@localhost) by www1.ietf.org (8.12.8/8.12.8/Submit) id i39043So003201 for dhcwg-archive@odin.ietf.org; Thu, 8 Apr 2004 20:04:03 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1BBjV5-0000pY-2l for dhcwg-web-archive@optimus.ietf.org; Thu, 08 Apr 2004 20:04:03 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id UAA12932 for <dhcwg-web-archive@ietf.org>; Thu, 8 Apr 2004 20:04:01 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 1BBjV2-0000YC-00 for dhcwg-web-archive@ietf.org; Thu, 08 Apr 2004 20:04:00 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12) id 1BBie0-0001t8-00 for dhcwg-web-archive@ietf.org; Thu, 08 Apr 2004 19:09:13 -0400
Received: from optimus.ietf.org ([132.151.1.19]) by ietf-mx with esmtp (Exim 4.12) id 1BBhma-0003hw-00 for dhcwg-web-archive@ietf.org; Thu, 08 Apr 2004 18:14:00 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1BBhmb-0003Kr-5r; Thu, 08 Apr 2004 18:14:01 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1BBhlw-0003B7-O1 for dhcwg@optimus.ietf.org; Thu, 08 Apr 2004 18:13:20 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA01070 for <dhcwg@ietf.org>; Thu, 8 Apr 2004 18:13:16 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 1BBhlt-0003ar-00 for dhcwg@ietf.org; Thu, 08 Apr 2004 18:13:17 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12) id 1BBfiM-0002aY-00 for dhcwg@ietf.org; Thu, 08 Apr 2004 16:01:32 -0400
Received: from rtp-iport-1.cisco.com ([64.102.122.148]) by ietf-mx with esmtp (Exim 4.12) id 1BBYnO-0002ci-00 for dhcwg@ietf.org; Thu, 08 Apr 2004 08:38:14 -0400
Received: from rtp-core-2.cisco.com (64.102.124.13) by rtp-iport-1.cisco.com with ESMTP; 08 Apr 2004 05:47:59 -0700
X-BrightmailFiltered: true
Received: from flask.cisco.com (IDENT:mirapoint@flask.cisco.com [161.44.122.62]) by rtp-core-2.cisco.com (8.12.10/8.12.6) with ESMTP id i38CbgCC000084 for <dhcwg@ietf.org>; Thu, 8 Apr 2004 08:37:42 -0400 (EDT)
Received: from rdroms-w2k01.cisco.com ([161.44.65.128]) by flask.cisco.com (Mirapoint Messaging Server MOS 3.3.6-GR) with ESMTP id AHL46683; Thu, 8 Apr 2004 08:37:41 -0400 (EDT)
Message-Id: <4.3.2.7.2.20040408083106.02ade250@flask.cisco.com>
X-Sender: rdroms@flask.cisco.com
X-Mailer: QUALCOMM Windows Eudora Version 4.3.2
Date: Thu, 08 Apr 2004 08:37:39 -0400
To: dhcwg@ietf.org
From: Ralph Droms <rdroms@cisco.com>
Subject: Re: [dhcwg] dhc WG last call on draft-ietf-dhc-reclassify-options-00
In-Reply-To: <4.3.2.7.2.20040403074305.029b19b0@flask.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>
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on ietf-mx.ietf.org
X-Spam-Status: No, hits=0.1 required=5.0 tests=AWL,SUBJ_HAS_UNIQ_ID autolearn=no version=2.60

This document reflects WG consensus on how to make more DHCP option codes
available to avoid exhaustion of the option code space.

Although there are known uses of option codes in the range 128-254 (both
documented and undocumented), the procedure described in this document
provides a way to avoid clashes in the use of reclassified options.

Editorial suggestions and comments:

The references should be listed as Normative and Informative.

Section 3, change the first sentence to: "The DHCP option space (0-255) is
divided into two ranges [RFC2132]:"

Reference [unused-optioncodes] has been published as RFC 3679.

The document should include boilerplate from RFC 3667 when it is revised.


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