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

Ralph Droms <rdroms@cisco.com> Mon, 05 April 2004 11:36 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 HAA24157 for <dhcwg-archive@odin.ietf.org>; Mon, 5 Apr 2004 07:36:00 -0400 (EDT)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1BASO3-0002mM-Le for dhcwg-archive@odin.ietf.org; Mon, 05 Apr 2004 07:35:31 -0400
Received: (from exim@localhost) by www1.ietf.org (8.12.8/8.12.8/Submit) id i35BZVmf010678 for dhcwg-archive@odin.ietf.org; Mon, 5 Apr 2004 07:35:31 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1BASO3-0002m9-Gv for dhcwg-web-archive@optimus.ietf.org; Mon, 05 Apr 2004 07:35:31 -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 HAA24146 for <dhcwg-web-archive@ietf.org>; Mon, 5 Apr 2004 07:35:29 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 1BASO2-0005Gl-00 for dhcwg-web-archive@ietf.org; Mon, 05 Apr 2004 07:35:31 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12) id 1BASN7-0005AR-00 for dhcwg-web-archive@ietf.org; Mon, 05 Apr 2004 07:34:33 -0400
Received: from optimus.ietf.org ([132.151.1.19]) by ietf-mx with esmtp (Exim 4.12) id 1BASMf-000547-00 for dhcwg-web-archive@ietf.org; Mon, 05 Apr 2004 07:34:05 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1BASMa-0002Nf-U1; Mon, 05 Apr 2004 07:34:00 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1BASM8-0002Ms-JW for dhcwg@optimus.ietf.org; Mon, 05 Apr 2004 07:33:32 -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 HAA24033 for <dhcwg@ietf.org>; Mon, 5 Apr 2004 07:33:31 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 1BASM7-00052S-00 for dhcwg@ietf.org; Mon, 05 Apr 2004 07:33:32 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12) id 1BASLD-0004uC-00 for dhcwg@ietf.org; Mon, 05 Apr 2004 07:32:36 -0400
Received: from sj-iport-4.cisco.com ([171.68.10.86]) by ietf-mx with esmtp (Exim 4.12) id 1BASKF-0004dK-00 for dhcwg@ietf.org; Mon, 05 Apr 2004 07:31:35 -0400
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 i35BV1Ue000257 for <dhcwg@ietf.org>; Mon, 5 Apr 2004 04:31:01 -0700 (PDT)
Received: from rdroms-w2k01.cisco.com (che-vpn-cluster-2-69.cisco.com [10.86.242.69]) by flask.cisco.com (Mirapoint Messaging Server MOS 3.3.6-GR) with ESMTP id AHI90886; Mon, 5 Apr 2004 07:31:00 -0400 (EDT)
Message-Id: <4.3.2.7.2.20040403072717.029b01f8@flask.cisco.com>
X-Sender: rdroms@flask.cisco.com
X-Mailer: QUALCOMM Windows Eudora Version 4.3.2
Date: Mon, 05 Apr 2004 07:31:00 -0500
To: dhcwg@ietf.org
From: Ralph Droms <rdroms@cisco.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format="flowed"
Subject: [dhcwg] dhc WG last call on draft-ietf-dhc-vendor-01
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 message announces a WG last call on "Vendor-Identifying Vendor Options
for DHCPv4" <draft-ietf-dhc-vendor-01>.  The last call will conclude at 5PM
on 4/16/04.

Please respond to this WG last call.  If you support acceptance of the
document without change, respond with a simple acknowledgment, so that
support for the document can be assessed.

Summary: The DHCP options for Vendor Class and Vendor-Specific Information
can be ambiguous when a DHCP client represents multiple vendors.
draft-ietf-dhc-vendor-01 defines two new options, modeled on the IPv6
options for vendor class and vendor-specific information, which contain
Enterprise Numbers to remove ambiguity..  This draft is available as
http://www.ietf.org/internet-drafts/draft-ietf-dhc-vendor-01.txt

- Ralph Droms 


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