[dhcwg] I-D ACTION:draft-ietf-dhc-agentopt-radius-02.txt

Internet-Drafts@ietf.org Tue, 05 November 2002 11:19 UTC

Received: from www1.ietf.org (ietf.org [] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id GAA11987 for <dhcwg-archive@odin.ietf.org>; Tue, 5 Nov 2002 06:19:06 -0500 (EST)
Received: (from mailnull@localhost) by www1.ietf.org (8.11.6/8.11.6) id gA5BL5m01814 for dhcwg-archive@odin.ietf.org; Tue, 5 Nov 2002 06:21:05 -0500
Received: from ietf.org (odin.ietf.org []) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gA5BL5v01811 for <dhcwg-web-archive@optimus.ietf.org>; Tue, 5 Nov 2002 06:21:05 -0500
Received: from www1.ietf.org (ietf-mx.ietf.org []) by ietf.org (8.9.1a/8.9.1a) with ESMTP id GAA11967 for <dhcwg-web-archive@ietf.org>; Tue, 5 Nov 2002 06:18:35 -0500 (EST)
Received: from www1.ietf.org (localhost.localdomain []) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gA5BESv01107; Tue, 5 Nov 2002 06:14:28 -0500
Received: from ietf.org (odin.ietf.org []) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gA5B6vv32602 for <dhcwg@optimus.ietf.org>; Tue, 5 Nov 2002 06:06:57 -0500
Received: from CNRI.Reston.VA.US (localhost []) by ietf.org (8.9.1a/8.9.1a) with ESMTP id GAA09954; Tue, 5 Nov 2002 06:04:26 -0500 (EST)
Message-Id: <200211051104.GAA09954@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, 05 Nov 2002 06:04:26 -0500
Subject: [dhcwg] I-D ACTION:draft-ietf-dhc-agentopt-radius-02.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		: RADIUS Attributes Sub-option for the DHCP Relay Agent 
                          Information Option
	Author(s)	: R. Droms, J. Schnizlein
	Filename	: draft-ietf-dhc-agentopt-radius-02.txt
	Pages		: 8
	Date		: 2002-11-4
A network access device may choose to authenticate the identity of a
device before granting that device access to the network.  The IEEE
802.1X protocol is an example of a mechanism for providing
authenticated layer 2 network access.  A network element using RADIUS
as an authentication authority will receive attributes from a RADIUS
server that may be used by a DHCP server in the selection of an IP
address for assignment to the device through its DHCP client.  The
RADIUS Attributes sub-option allows a network element to pass along
attributes for the user of a device received during RADIUS
authentication to a DHCP server.

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-agentopt-radius-02.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-agentopt-radius-02.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