[dhcwg] I-D ACTION:draft-ietf-dhc-concat-05.txt

Internet-Drafts@ietf.org Thu, 12 September 2002 12:06 UTC

Received: from www1.ietf.org (ietf.org [] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA20234 for <dhcwg-archive@odin.ietf.org>; Thu, 12 Sep 2002 08:06:14 -0400 (EDT)
Received: (from mailnull@localhost) by www1.ietf.org (8.11.6/8.11.6) id g8CC7QQ01215 for dhcwg-archive@odin.ietf.org; Thu, 12 Sep 2002 08:07:26 -0400
Received: from ietf.org (odin.ietf.org []) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g8CC7Qv01212 for <dhcwg-web-archive@optimus.ietf.org>; Thu, 12 Sep 2002 08:07:26 -0400
Received: from www1.ietf.org (ietf.org [] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA20213 for <dhcwg-web-archive@ietf.org>; Thu, 12 Sep 2002 08:05:44 -0400 (EDT)
Received: from www1.ietf.org (localhost.localdomain []) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g8CBx3v00302; Thu, 12 Sep 2002 07:59:03 -0400
Received: from ietf.org (odin.ietf.org []) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g8CBw4v32712 for <dhcwg@optimus.ietf.org>; Thu, 12 Sep 2002 07:58:04 -0400
Received: from CNRI.Reston.VA.US (localhost []) by ietf.org (8.9.1a/8.9.1a) with ESMTP id HAA19709; Thu, 12 Sep 2002 07:56:20 -0400 (EDT)
Message-Id: <200209121156.HAA19709@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, 12 Sep 2002 07:56:20 -0400
Subject: [dhcwg] I-D ACTION:draft-ietf-dhc-concat-05.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>

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		: Encoding Long Options in DHCPv4
	Author(s)	: T. Lemon, S. Cheshire
	Filename	: draft-ietf-dhc-concat-05.txt
	Pages		: 0
	Date		: 2002-9-11
This document specifies the processing rules for DHCPv4 options
that appear multiple times in the same message.  Multiple
instances of the same option are generated when an option exceeds
255 octets in size (the maximum size of a single option) or when
an option needs to be split apart in order to take advantage of
DHCP option overloading.  When multiple instances of the same
option appear in the options, file and/or sname fields in a DHCP
packet, the contents of these options are concatenated together
to form a single option prior to processing.

A URL for this Internet-Draft is:

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-concat-05.txt".

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

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

Send a message to:
In the body type:
	"FILE /internet-drafts/draft-ietf-dhc-concat-05.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