Protocol Action: 'Vendor-Identifying Vendor Options for DHCPv4' to Proposed Standard

The IESG <iesg-secretary@ietf.org> Mon, 12 July 2004 19:56 UTC

Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA06690 for <ietf-announce-archive@ietf.org>; Mon, 12 Jul 2004 15:56:44 -0400 (EDT)
Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx) by ietf-mx with esmtp (Exim 4.32) id 1Bk6ur-0003bY-TJ for ietf-announce-archive@ietf.org; Mon, 12 Jul 2004 15:56:45 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12) id 1Bk6sj-0002wL-00 for ietf-announce-archive@ietf.org; Mon, 12 Jul 2004 15:54:34 -0400
Received: from [65.246.255.50] (helo=mx2.foretec.com) by ietf-mx with esmtp (Exim 4.12) id 1Bk6qU-0002OZ-00; Mon, 12 Jul 2004 15:52:14 -0400
Received: from megatron.ietf.org ([132.151.6.71]) by mx2.foretec.com with esmtp (Exim 4.24) id 1Bk6ZD-00048d-D3; Mon, 12 Jul 2004 15:34:23 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1Bk69a-0004Kr-OH; Mon, 12 Jul 2004 15:07:54 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1Bk5vp-00052f-7w for ietf-announce@megatron.ietf.org; Mon, 12 Jul 2004 14:53:41 -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 OAA00861 for <ietf-announce@ietf.org>; Mon, 12 Jul 2004 14:53:39 -0400 (EDT)
Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx) by ietf-mx with esmtp (Exim 4.32) id 1Bk5vo-0002w8-4m for ietf-announce@ietf.org; Mon, 12 Jul 2004 14:53:40 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12) id 1Bk5up-0002fq-00 for ietf-announce@ietf.org; Mon, 12 Jul 2004 14:52:39 -0400
Received: from megatron.ietf.org ([132.151.6.71]) by ietf-mx with esmtp (Exim 4.12) id 1Bk5tt-0002Cg-00; Mon, 12 Jul 2004 14:51:41 -0400
Received: from apache by megatron.ietf.org with local (Exim 4.32) id 1Bk5ZA-0001Uo-Sh; Mon, 12 Jul 2004 14:30:16 -0400
X-test-idtracker: no
From: The IESG <iesg-secretary@ietf.org>
To: IETF-Announce <ietf-announce@ietf.org>
Message-Id: <E1Bk5ZA-0001Uo-Sh@megatron.ietf.org>
Date: Mon, 12 Jul 2004 14:30:16 -0400
Cc: dhc mailing list <dhcwg@ietf.org>, dhc chair <rdroms@cisco.com>, Internet Architecture Board <iab@iab.org>, RFC Editor <rfc-editor@rfc-editor.org>
Subject: Protocol Action: 'Vendor-Identifying Vendor Options for DHCPv4' to Proposed Standard
X-BeenThere: ietf-announce@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: ietf-announce.ietf.org
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ietf-announce>, <mailto:ietf-announce-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ietf-announce@ietf.org>
List-Help: <mailto:ietf-announce-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ietf-announce>, <mailto:ietf-announce-request@ietf.org?subject=subscribe>
Sender: ietf-announce-bounces@ietf.org
Errors-To: ietf-announce-bounces@ietf.org
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on ietf-mx.ietf.org
X-Spam-Status: No, hits=0.2 required=5.0 tests=AWL autolearn=no version=2.60

The IESG has approved the following document:

- 'Vendor-Identifying Vendor Options for DHCPv4 '
   <draft-ietf-dhc-vendor-03.txt> as a Proposed Standard

This document is the product of the Dynamic Host Configuration Working Group. 

The IESG contact persons are Margaret Wasserman and Thomas Narten.

Technical Summary

The DHCP options for Vendor Class and Vendor-Specific Information can
be limiting or ambiguous when a DHCP client represents multiple
vendors.  This document defines two new options, modeled on the IPv6
options for vendor class and vendor-specific information, which
contain Enterprise Numbers to remove ambiguity.

Working Group Summary

The WG agrees that these options are a useful extension to DHCPv4.
The corresponding options in DHCPv6 were based on deployment
experience with the vendor type (option 60) and vendor-specific
information (option 43) options.

Protocol Quality

The protocol in this standard is not currently implemented.  We expect
implementation in new DHCP clients, especially in dedicated devices
like DOCSIS modems and RFID readers, which may require class and
option information based on both the type of device and the vendor of
the device.  We don't have any specific information about
implementation plans.  

This document was reviewed for the IESG by Margaret Wasserman.


_______________________________________________
IETF-Announce mailing list
IETF-Announce@ietf.org
https://www1.ietf.org/mailman/listinfo/ietf-announce