IETF Logo Mail Archive

Re: [dhcwg] dhc WG last call on draft-ietf-dhc-vendor-01

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 UAA13148 for <dhcwg-archive@odin.ietf.org>; Thu, 8 Apr 2004 20:04:36 -0400 (EDT)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1BBjV9-0000q1-Et for dhcwg-archive@odin.ietf.org; Thu, 08 Apr 2004 20:04:07 -0400
Received: (from exim@localhost) by www1.ietf.org (8.12.8/8.12.8/Submit) id i39047dI003217 for dhcwg-archive@odin.ietf.org; Thu, 8 Apr 2004 20:04:07 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1BBjV9-0000po-BR for dhcwg-web-archive@optimus.ietf.org; Thu, 08 Apr 2004 20:04:07 -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 UAA12940 for <dhcwg-web-archive@ietf.org>; Thu, 8 Apr 2004 20:04:05 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 1BBjV7-0000Yg-00 for dhcwg-web-archive@ietf.org; Thu, 08 Apr 2004 20:04:05 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12) id 1BBie1-0001tJ-00 for dhcwg-web-archive@ietf.org; Thu, 08 Apr 2004 19:09:14 -0400
Received: from optimus.ietf.org ([132.151.1.19]) by ietf-mx with esmtp (Exim 4.12) id 1BBhma-0003hx-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 1BBhma-0003Kj-Pk; Thu, 08 Apr 2004 18:14:00 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1BBhlu-0003Ab-Gv for dhcwg@optimus.ietf.org; Thu, 08 Apr 2004 18:13:18 -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 SAA01065 for <dhcwg@ietf.org>; Thu, 8 Apr 2004 18:13:14 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 1BBhlr-0003aa-00 for dhcwg@ietf.org; Thu, 08 Apr 2004 18:13:15 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12) id 1BBfiI-0002a6-00 for dhcwg@ietf.org; Thu, 08 Apr 2004 16:01:29 -0400
Received: from sj-iport-3-in.cisco.com ([171.71.176.72] helo=sj-iport-3.cisco.com) by ietf-mx with esmtp (Exim 4.12) id 1BBYgp-0001tg-00 for dhcwg@ietf.org; Thu, 08 Apr 2004 08:31:27 -0400
Received: from sj-core-1.cisco.com (171.71.177.237) by sj-iport-3.cisco.com with ESMTP; 08 Apr 2004 04:40:06 +0000
Received: from flask.cisco.com (IDENT:mirapoint@flask.cisco.com [161.44.122.62]) by sj-core-1.cisco.com (8.12.10/8.12.6) with ESMTP id i38CUsGF012097 for <dhcwg@ietf.org>; Thu, 8 Apr 2004 05:30:55 -0700 (PDT)
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 AHL46356; Thu, 8 Apr 2004 08:30:53 -0400 (EDT)
Message-Id: <4.3.2.7.2.20040408082319.01f3e948@flask.cisco.com>
X-Sender: rdroms@flask.cisco.com
X-Mailer: QUALCOMM Windows Eudora Version 4.3.2
Date: Thu, 08 Apr 2004 08:30:51 -0400
To: dhcwg@ietf.org
From: Ralph Droms <rdroms@cisco.com>
Subject: Re: [dhcwg] dhc WG last call on draft-ietf-dhc-vendor-01
In-Reply-To: <4.3.2.7.2.20040403072717.029b01f8@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.0 required=5.0 tests=AWL autolearn=no version=2.60

This specification provides a useful extension to the vendor class and
vendor specific options capabilities in DHCP.  The requirements for these
capabilities are based on experience with competing uses for the existing
vendor class and vendor specific options in DHCP deployments.

I agree with the decision to define these two capabilities as separate
options for simplicity and to minimize the requirement for RFC 3396 option
concatenation.  While the current DHCP option code space is nearing
exhaustion, draft-ietf-dhc-reclassify-options (currently in WG last call)
will increase the available option codes, reducing the need for option code
conservation.

The specification should separate the references into Normative and
Informative, and should be updated to include the boilerplate from RFC 3667.

Note to draft authors using xml2rfc: you can include the appropriate
boilerplate in your docs by moving to version 1.22 and setting the ipr tag
to "full3667".

- Ralph


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

v2.23.0 | Report a Bug | By Email