idnits 2.17.1 draft-ietf-dhc-agent-subnet-selection-04.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 3527 5 Title: Link Selection sub-option 6 for the Relay Agent Information Option for DHCPv4 7 Author(s): K. Kinnear, M. Stapp, R. Johnson, J. Kumarasamy 8 Status: Standards Track 9 Date: April 2003 10 Mailbox: kkinnear@cisco.com, mjs@cisco.com, jayk@cisco.com, 11 raj@cisco.com 12 Pages: 9 13 Characters: 16831 14 Updates/Obsoletes/SeeAlso: None 16 I-D Tag: draft-ietf-dhc-agent-subnet-selection-04.txt 18 URL: ftp://ftp.rfc-editor.org/in-notes/rfc3527.txt 20 This document describes the link selection sub-option of the 21 relay-agent-information option for the Dynamic Host Configuration 22 Protocol (DHCPv4). The giaddr specifies an IP address which 23 determines both a subnet, and thereby a link on which a Dynamic Host 24 Configuration Protocol (DHCP) client resides as well as an IP address 25 that can be used to communicate with the relay agent. The 26 subnet-selection option allows the functions of the giaddr to be split 27 so that when one entity is performing as a DHCP proxy, it can specify 28 the subnet/link from which to allocate an IP address, which is 29 different from the IP address with which it desires to communicate 30 with the DHCP server. Analogous situations exist where the relay 31 agent needs to specify the subnet/link on which a DHCP client resides, 32 which is different from an IP address that can be used to communicate 33 with the relay agent. 35 This document is a product of the Dynamic Host Configuration Working 36 Group of the IETF. 38 This is now a Proposed Standard Protocol. 40 This document specifies an Internet standards track protocol for 41 the Internet community, and requests discussion and suggestions 42 for improvements. Please refer to the current edition of the 43 "Internet Official Protocol Standards" (STD 1) for the 44 standardization state and status of this protocol. Distribution 45 of this memo is unlimited. 47 This announcement is sent to the IETF list and the RFC-DIST list. 48 Requests to be added to or deleted from the IETF distribution list 49 should be sent to IETF-REQUEST@IETF.ORG. Requests to be 50 added to or deleted from the RFC-DIST distribution list should 51 be sent to RFC-DIST-REQUEST@RFC-EDITOR.ORG. 53 Details on obtaining RFCs via FTP or EMAIL may be obtained by sending 54 an EMAIL message to rfc-info@RFC-EDITOR.ORG with the message body 55 help: ways_to_get_rfcs. For example: 57 To: rfc-info@RFC-EDITOR.ORG 58 Subject: getting rfcs 60 help: ways_to_get_rfcs 62 Requests for special distribution should be addressed to either the 63 author of the RFC in question, or to RFC-Manager@RFC-EDITOR.ORG. Unless 64 specifically noted otherwise on the RFC itself, all RFCs are for 65 unlimited distribution.echo 66 Submissions for Requests for Comments should be sent to 67 RFC-EDITOR@RFC-EDITOR.ORG. Please consult RFC 2223, Instructions to RFC 68 Authors, for further information.