A new Request for Comments is now available in online RFC libraries.
RFC 3118
Title: Authentication for DHCP Messages
Author(s): R. Droms, Editor, W. Arbaugh, Editor
Status: Standards Track
Date: June 2001
Mailbox: [EMAIL PROTECTED], [EMAIL PROTECTED]
Pages: 17
Characters: 35536
Updates/Obsoletes/SeeAlso: None
I-D Tag: draft-ietf-dhc-authentication-16.txt
URL: ftp://ftp.rfc-editor.org/in-notes/rfc3118.txt
This document defines a new Dynamic Host Configuration Protocol (DHCP)
option through which authorization tickets can be easily generated and
newly attached hosts with proper authorization can be automatically
configured from an authenticated DHCP server. DHCP provides a
framework for passing configuration information to hosts on a TCP/IP
network. In some situations, network administrators may wish to
constrain the allocation of addresses to authorized hosts.
Additionally, some network administrators may wish to provide for
authentication of the source and contents of DHCP messages.
This document is a product of the Dynamic Host Configuration Working
Group of the IETF.
This is now a Proposed Standard Protocol.
This document specifies an Internet standards track protocol for
the Internet community, and requests discussion and suggestions
for improvements. Please refer to the current edition of the
"Internet Official Protocol Standards" (STD 1) for the
standardization state and status of this protocol. Distribution
of this memo is unlimited.
This announcement is sent to the IETF list and the RFC-DIST list.
Requests to be added to or deleted from the IETF distribution list
should be sent to [EMAIL PROTECTED] Requests to be
added to or deleted from the RFC-DIST distribution list should
be sent to [EMAIL PROTECTED]
Details on obtaining RFCs via FTP or EMAIL may be obtained by sending
an EMAIL message to [EMAIL PROTECTED] with the message body
help: ways_to_get_rfcs. For example:
To: [EMAIL PROTECTED]
Subject: getting rfcs
help: ways_to_get_rfcs
Requests for special distribution should be addressed to either the
author of the RFC in question, or to [EMAIL PROTECTED] Unless
specifically noted otherwise on the RFC itself, all RFCs are for
unlimited distribution.echo
Submissions for Requests for Comments should be sent to
[EMAIL PROTECTED] Please consult RFC 2223, Instructions to RFC
Authors, for further information.
Joyce K. Reynolds and Sandy Ginoza
USC/Information Sciences Institute
...
Below is the data which will enable a MIME compliant Mail Reader
implementation to automatically retrieve the ASCII version
of the RFCs.
rfc3118.txt
