RE: [dhcwg] Last Call: 'Vendor-Identifying Vendor Options for DHCPv4' to Proposed Standard

"Bernie Volz" <volz@cisco.com> Fri, 25 June 2004 12:57 UTC

Received: from megatron.ietf.org (megatron.ietf.org [132.151.6.71]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA27854; Fri, 25 Jun 2004 08:57:48 -0400 (EDT)
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1Bdq5m-0006zl-A0; Fri, 25 Jun 2004 08:46:06 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1Bdq07-0005qK-CG for dhcwg@megatron.ietf.org; Fri, 25 Jun 2004 08:40:15 -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 IAA26896 for <dhcwg@ietf.org>; Fri, 25 Jun 2004 08:40:13 -0400 (EDT)
Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx) by ietf-mx with esmtp (Exim 4.32) id 1Bdq06-0002Is-Od for dhcwg@ietf.org; Fri, 25 Jun 2004 08:40:14 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12) id 1Bdpz7-000208-00 for dhcwg@ietf.org; Fri, 25 Jun 2004 08:39:14 -0400
Received: from sj-iport-1-in.cisco.com ([171.71.176.70] helo=sj-iport-1.cisco.com) by ietf-mx with esmtp (Exim 4.12) id 1Bdpy9-0001QB-00; Fri, 25 Jun 2004 08:38:13 -0400
Received: from sj-core-1.cisco.com (171.71.177.237) by sj-iport-1.cisco.com with ESMTP; 25 Jun 2004 05:41:41 -0700
X-BrightmailFiltered: true
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 i5PCbe4N019237; Fri, 25 Jun 2004 05:37:40 -0700 (PDT)
Received: from volzw2k (che-vpn-cluster-2-2.cisco.com [10.86.242.2]) by flask.cisco.com (MOS 3.4.6-GR) with ESMTP id AJS04543; Fri, 25 Jun 2004 08:37:39 -0400 (EDT)
From: "Bernie Volz" <volz@cisco.com>
To: <iesg@ietf.org>
Subject: RE: [dhcwg] Last Call: 'Vendor-Identifying Vendor Options for DHCPv4' to Proposed Standard
Date: Fri, 25 Jun 2004 08:37:38 -0400
Organization: Cisco
Message-ID: <001101c45ab1$3363b460$6601a8c0@amer.cisco.com>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
X-Priority: 3 (Normal)
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook, Build 10.0.5709
In-Reply-To: <E1BdVJF-0001xP-Ln@megatron.ietf.org>
Importance: Normal
X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4939.300
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
Content-Transfer-Encoding: quoted-printable
Cc: dhcwg@ietf.org
X-BeenThere: dhcwg@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: dhcwg.ietf.org
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/dhcwg>, <mailto:dhcwg-request@ietf.org?subject=unsubscribe>
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>
Sender: dhcwg-bounces@ietf.org
Errors-To: dhcwg-bounces@ietf.org
Content-Transfer-Encoding: quoted-printable

I fully support this document moving forward and hope the IESG will move
this document along quickly. This should greatly reduce the need for vendors
to "hijack" the site-specific options as they have been doing in the past
and which can cause interoperability issues. These new vendor options are
much better than the old ones from RFC 2132.

- Bernie Volz

> -----Original Message-----
> From: dhcwg-bounces@ietf.org [mailto:dhcwg-bounces@ietf.org] 
> On Behalf Of The IESG
> Sent: Thursday, June 24, 2004 10:35 AM
> To: IETF-Announce
> Cc: dhcwg@ietf.org
> Subject: [dhcwg] Last Call: 'Vendor-Identifying Vendor 
> Options for DHCPv4' to Proposed Standard 
> 
> 
> The IESG has received a request from the Dynamic Host 
> Configuration WG to 
> consider the following document:
> 
> - 'Vendor-Identifying Vendor Options for DHCPv4 '
>    <draft-ietf-dhc-vendor-03.txt> as a Proposed Standard
> 
> The IESG plans to make a decision in the next few weeks, and 
> solicits final comments on this action.  Please send any 
> comments to the iesg@ietf.org or ietf@ietf.org mailing lists 
> by 2004-07-08.
> 
> The file can be obtained via 
> http://www.ietf.org/internet-drafts/draft-ietf-dhc-vendor-03.t
xt


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


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