[dhcwg] I-D ACTION:draft-ietf-dhc-agent-subnet-selection-04.txt

Internet-Drafts@ietf.org Tue, 29 October 2002 11:21 UTC

Received: from www1.ietf.org (ietf.org [] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id GAA28448 for <dhcwg-archive@odin.ietf.org>; Tue, 29 Oct 2002 06:21:04 -0500 (EST)
Received: (from mailnull@localhost) by www1.ietf.org (8.11.6/8.11.6) id g9TBMuw05212 for dhcwg-archive@odin.ietf.org; Tue, 29 Oct 2002 06:22:56 -0500
Received: from ietf.org (odin.ietf.org []) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g9TBMuv05209 for <dhcwg-web-archive@optimus.ietf.org>; Tue, 29 Oct 2002 06:22:56 -0500
Received: from www1.ietf.org (ietf-mx.ietf.org []) by ietf.org (8.9.1a/8.9.1a) with ESMTP id GAA28404 for <dhcwg-web-archive@ietf.org>; Tue, 29 Oct 2002 06:20:33 -0500 (EST)
Received: from www1.ietf.org (localhost.localdomain []) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g9TBKmv05022; Tue, 29 Oct 2002 06:20:48 -0500
Received: from ietf.org (odin.ietf.org []) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g9TBIqv04873 for <dhcwg@optimus.ietf.org>; Tue, 29 Oct 2002 06:18:52 -0500
Received: from CNRI.Reston.VA.US (localhost []) by ietf.org (8.9.1a/8.9.1a) with ESMTP id GAA27549; Tue, 29 Oct 2002 06:16:28 -0500 (EST)
Message-Id: <200210291116.GAA27549@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: Tue, 29 Oct 2002 06:16:28 -0500
Subject: [dhcwg] I-D ACTION:draft-ietf-dhc-agent-subnet-selection-04.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		: Link Selection sub-option for the Relay Agent 
                          Information Option for DHCPv4
	Author(s)	: K. Kinnear, M. Stapp, R. Johnson, J. Kumarasamy
	Filename	: draft-ietf-dhc-agent-subnet-selection-04.txt
	Pages		: 8
	Date		: 2002-10-28
In RFC 2131, the giaddr specifies an IP address which determines both
a subnet and thereby a link on which a DHCP client resides as well as
an IP address which can be used to communicate with the relay agent.
The subnet-selection option [RFC 3011] allows these functions of the
giaddr to be split so that when one entity is performing as a DHCP
proxy, it can specify the subnet/link from which to allocate an IP
address which is different from the IP address with which it desires
to communicate with the DHCP server.  Analgous situations exist where
the relay agent needs to specify the subnet/link on which a DHCP
client resides which is different from an IP address which can be
used to communicate with the relay agent.  The link-selection sub-
option (specified here) of the relay-agent-information option allows
a relay agent to do this.

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-agent-subnet-selection-04.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-agent-subnet-selection-04.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