idnits 2.17.1 draft-ietf-dhc-authentication-16.txt: Skipping this file; it looks like a tombstone file to me. -------------------------------------------------------------------------------- 1 A new Request for Comments is now available in online RFC libraries. 3 RFC 3118 5 Title: Authentication for DHCP Messages 6 Author(s): R. Droms, Editor, W. Arbaugh, Editor 7 Status: Standards Track 8 Date: June 2001 9 Mailbox: rdroms@cisco.com, waa@cs.umd.edu 10 Pages: 17 11 Characters: 35536 12 Updates/Obsoletes/SeeAlso: None 14 I-D Tag: draft-ietf-dhc-authentication-16.txt 16 URL: ftp://ftp.rfc-editor.org/in-notes/rfc3118.txt 18 This document defines a new Dynamic Host Configuration Protocol (DHCP) 19 option through which authorization tickets can be easily generated and 20 newly attached hosts with proper authorization can be automatically 21 configured from an authenticated DHCP server. DHCP provides a 22 framework for passing configuration information to hosts on a TCP/IP 23 network. In some situations, network administrators may wish to 24 constrain the allocation of addresses to authorized hosts. 25 Additionally, some network administrators may wish to provide for 26 authentication of the source and contents of DHCP messages. 28 This document is a product of the Dynamic Host Configuration Working 29 Group of the IETF. 31 This is now a Proposed Standard Protocol. 33 This document specifies an Internet standards track protocol for 34 the Internet community, and requests discussion and suggestions 35 for improvements. Please refer to the current edition of the 36 "Internet Official Protocol Standards" (STD 1) for the 37 standardization state and status of this protocol. Distribution 38 of this memo is unlimited. 40 This announcement is sent to the IETF list and the RFC-DIST list. 41 Requests to be added to or deleted from the IETF distribution list 42 should be sent to IETF-REQUEST@IETF.ORG. Requests to be 43 added to or deleted from the RFC-DIST distribution list should 44 be sent to RFC-DIST-REQUEST@RFC-EDITOR.ORG. 46 Details on obtaining RFCs via FTP or EMAIL may be obtained by sending 47 an EMAIL message to rfc-info@RFC-EDITOR.ORG with the message body 48 help: ways_to_get_rfcs. For example: 50 To: rfc-info@RFC-EDITOR.ORG 51 Subject: getting rfcs 53 help: ways_to_get_rfcs 55 Requests for special distribution should be addressed to either the 56 author of the RFC in question, or to RFC-Manager@RFC-EDITOR.ORG. Unless 57 specifically noted otherwise on the RFC itself, all RFCs are for 58 unlimited distribution.echo 59 Submissions for Requests for Comments should be sent to 60 RFC-EDITOR@RFC-EDITOR.ORG. Please consult RFC 2223, Instructions to RFC 61 Authors, for further information.