I-D ACTION:draft-ietf-dhc-securing-dhc-00.txt

Internet-Drafts@ietf.org Tue, 05 August 1997 20:21 UTC

Received: from ietf.org by ietf.org id aa21662; 5 Aug 97 16:21 EDT
Received: from ietf.ietf.org by ietf.org id aa21419; 5 Aug 97 16:19 EDT
Mime-Version: 1.0
Content-Type: Multipart/Mixed; Boundary="NextPart"
To: IETF-Announce@ietf.org
Cc: dhcp-v4@bucknell.edu
Sender: ietf-announce-request@ietf.org
From: Internet-Drafts@ietf.org
Reply-to: Internet-Drafts@ietf.org
Subject: I-D ACTION:draft-ietf-dhc-securing-dhc-00.txt
Date: Tue, 05 Aug 1997 16:19:47 -0400
X-Orig-Sender: cclark@ietf.org
Message-ID: <9708051619.aa21419@ietf.org>

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		: Securing DHCP
	Author(s)	: B. Patel
	Filename	: draft-ietf-dhc-securing-dhc-00.txt
	Pages		: 5
	Date		: 1997-07-30
This proposal describes methods of securing DHCP based on IETF DHCP 
and IPSEC protocols. This protocol achieves security goals for DHCP 
client and servers without having to define a new security protocol. 
Instead, it first bootstraps the DHCP client in un-trusted mode using 
existing DHCP protocol and then proceeds to secure configuration of 
the client using existing DHCP and IP protocol features.

Internet-Drafts are available by anonymous FTP.  Login wih the username
"anonymous" and a password of your e-mail address.  After logging in,
type "cd internet-drafts" and then
	"get draft-ietf-dhc-securing-dhc-00.txt".
A URL for the Internet-Draft is:

Internet-Drafts directories are located at:

	Africa:	ftp.is.co.za
	Europe: ftp.nordu.net
	Pacific Rim: munnari.oz.au
	US East Coast: ds.internic.net
	US West Coast: ftp.isi.edu

Internet-Drafts are also available by mail.

Send a message to:	mailserv@ds.internic.net.  In the body type:
	"FILE /internet-drafts/draft-ietf-dhc-securing-dhc-00.txt".
NOTE:	The mail server at ds.internic.net 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