[dhcwg] I-D ACTION:draft-ietf-dhc-vendor-01.txt

Internet-Drafts@ietf.org Thu, 05 February 2004 20:49 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 PAA05811 for <dhcwg-archive@odin.ietf.org>; Thu, 5 Feb 2004 15:49:47 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AoqR4-00078R-UU for dhcwg-archive@odin.ietf.org; Thu, 05 Feb 2004 15:49:18 -0500
Received: (from exim@localhost) by www1.ietf.org (8.12.8/8.12.8/Submit) id i15KnIXb027421 for dhcwg-archive@odin.ietf.org; Thu, 5 Feb 2004 15:49:18 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AoqR4-00078C-PW for dhcwg-web-archive@optimus.ietf.org; Thu, 05 Feb 2004 15:49:18 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA05806 for <dhcwg-web-archive@ietf.org>; Thu, 5 Feb 2004 15:49:16 -0500 (EST)
Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 1AoqR3-0004gi-00 for dhcwg-web-archive@ietf.org; Thu, 05 Feb 2004 15:49:17 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12) id 1AoqQ5-0004bC-00 for dhcwg-web-archive@ietf.org; Thu, 05 Feb 2004 15:48:17 -0500
Received: from optimus.ietf.org ([132.151.1.19]) by ietf-mx with esmtp (Exim 4.12) id 1AoqPs-0004Vg-00 for dhcwg-web-archive@ietf.org; Thu, 05 Feb 2004 15:48:04 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AoqPp-00071O-JF; Thu, 05 Feb 2004 15:48:01 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AoqOs-0006y7-0m for dhcwg@optimus.ietf.org; Thu, 05 Feb 2004 15:47:02 -0500
Received: from CNRI.Reston.VA.US (localhost [127.0.0.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA05618; Thu, 5 Feb 2004 15:46:59 -0500 (EST)
Message-Id: <200402052046.PAA05618@ietf.org>
Mime-Version: 1.0
Content-Type: Multipart/Mixed; Boundary="NextPart"
To: IETF-Announce:;
Cc: dhcwg@ietf.org
From: Internet-Drafts@ietf.org
Reply-to: Internet-Drafts@ietf.org
Date: Thu, 05 Feb 2004 15:46:59 -0500
Subject: [dhcwg] I-D ACTION:draft-ietf-dhc-vendor-01.txt
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.4 required=5.0 tests=AWL,MIME_BOUND_NEXTPART, NO_REAL_NAME autolearn=no version=2.60

A New Internet-Draft is available from the on-line Internet-Drafts directories.
This draft is a work item of the Dynamic Host Configuration Working Group of the IETF.

	Title		: Vendor-Identifying Vendor Options for DHCPv4
	Author(s)	: J. Littlefield
	Filename	: draft-ietf-dhc-vendor-01.txt
	Pages		: 9
	Date		: 2004-2-5
	
The DHCP options for Vendor Class and Vendor-Specific Information can
be 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.

A URL for this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-ietf-dhc-vendor-01.txt

To remove yourself from the IETF Announcement list, send a message to 
ietf-announce-request with the word unsubscribe in the body of the message.

Internet-Drafts are also available by anonymous FTP. Login with the username
"anonymous" and a password of your e-mail address. After logging in,
type "cd internet-drafts" and then
	"get draft-ietf-dhc-vendor-01.txt".

A list of Internet-Drafts directories can be found in
http://www.ietf.org/shadow.html 
or ftp://ftp.ietf.org/ietf/1shadow-sites.txt


Internet-Drafts can also be obtained by e-mail.

Send a message to:
	mailserv@ietf.org.
In the body type:
	"FILE /internet-drafts/draft-ietf-dhc-vendor-01.txt".
	
NOTE:	The mail server at ietf.org can return the document in
	MIME-encoded form by using the "mpack" utility.  To use this
	feature, insert the command "ENCODING mime" before the "FILE"
	command.  To decode the response(s), you will need "munpack" or
	a MIME-compliant mail reader.  Different MIME-compliant mail readers
	exhibit different behavior, especially when dealing with
	"multipart" MIME messages (i.e. documents which have been split
	up into multiple messages), so check your local documentation on
	how to manipulate these messages.
		
		
Below is the data which will enable a MIME compliant mail reader
implementation to automatically retrieve the ASCII version of the
Internet-Draft.
ftp://ftp.ietf.org/internet-drafts/draft-ietf-dhc-vendor-01.txt"><ftp://ftp.ietf.org/internet-drafts/draft-ietf-dhc-vendor-01.txt>