idnits 2.17.1 draft-ietf-dhc-agent-options-12.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 3046 5 Title: DHCP Relay Agent Information Option 6 Author(s): M. Patrick 7 Status: Standards Track 8 Date: January 2001 9 Mailbox: michael.patrick@motorola.com 10 Pages: 14 11 Characters: 30633 12 Updates/Obsoletes/SeeAlso: None 14 I-D Tag: draft-ietf-dhc-agent-options-12.txt 16 URL: ftp://ftp.rfc-editor.org/in-notes/rfc3046.txt 18 Newer high-speed public Internet access technologies call for a 19 high-speed modem to have a local area network (LAN) attachment to one 20 or more customer premise hosts. It is advantageous to use the Dynamic 21 Host Configuration Protocol (DHCP) as defined in RFC 2131 to assign 22 customer premise host IP addresses in this environment. However, a 23 number of security and scaling problems arise with such "public" DHCP 24 use. This document describes a new DHCP option to address these 25 issues. This option extends the set of DHCP options as defined in RFC 26 2132. 28 The new option is called the Relay Agent Information option and is 29 inserted by the DHCP relay agent when forwarding client-originated 30 DHCP packets to a DHCP server. Servers recognizing the Relay Agent 31 Information option may use the information to implement IP address or 32 other parameter assignment policies. The DHCP Server echoes the 33 option back verbatim to the relay agent in server-to-client replies, 34 and the relay agent strips the option before forwarding the reply to 35 the client. 37 The "Relay Agent Information" option is organized as a single DHCP 38 option that contains one or more "sub-options" that convey 39 information known by the relay agent. The initial sub-options are 40 defined for a relay agent that is co-located in a public circuit 41 access unit. These include a "circuit ID" for the incoming circuit, 42 and a "remote ID" which provides a trusted identifier for the remote 43 high-speed modem. 45 This document is a product of the Dynamic Host Configuration Working 46 Group of the IETF. 48 This is now a Proposed Standard Protocol. 50 This document specifies an Internet standards track protocol for 51 the Internet community, and requests discussion and suggestions 52 for improvements. Please refer to the current edition of the 53 "Internet Official Protocol Standards" (STD 1) for the 54 standardization state and status of this protocol. Distribution 55 of this memo is unlimited. 57 This announcement is sent to the IETF list and the RFC-DIST list. 58 Requests to be added to or deleted from the IETF distribution list 59 should be sent to IETF-REQUEST@IETF.ORG. Requests to be 60 added to or deleted from the RFC-DIST distribution list should 61 be sent to RFC-DIST-REQUEST@RFC-EDITOR.ORG. 63 Details on obtaining RFCs via FTP or EMAIL may be obtained by sending 64 an EMAIL message to rfc-info@RFC-EDITOR.ORG with the message body 65 help: ways_to_get_rfcs. For example: 67 To: rfc-info@RFC-EDITOR.ORG 68 Subject: getting rfcs 70 help: ways_to_get_rfcs 72 Requests for special distribution should be addressed to either the 73 author of the RFC in question, or to RFC-Manager@RFC-EDITOR.ORG. Unless 74 specifically noted otherwise on the RFC itself, all RFCs are for 75 unlimited distribution.echo 76 Submissions for Requests for Comments should be sent to 77 RFC-EDITOR@RFC-EDITOR.ORG. Please consult RFC 2223, Instructions to RFC 78 Authors, for further information.