DHC B. Volz Internet-Draft Cisco Systems, Inc. Expires:
October 9, 2005 April 07, 2005September 5, 2006 March 4, 2006 DHCPv6 Relay Agent Subscriber-ID Option draft-ietf-dhc-dhcpv6-subid-00.txtdraft-ietf-dhc-dhcpv6-subid-01.txt Status of this Memo By submitting this Internet-Draft, each author represents that any applicable patent or other IPR claims of which he or she is aware have been or will be disclosed, and any of which he or she becomes aware will be disclosed, in accordance with Section 6 of BCP 79. Internet-Drafts are working documents of the Internet Engineering Task Force (IETF), its areas, and its working groups. Note that other groups may also distribute working documents as Internet- Drafts. Internet-Drafts are draft documents valid for a maximum of six months and may be updated, replaced, or obsoleted by other documents at any time. It is inappropriate to use Internet-Drafts as reference material or to cite them other than as "work in progress." The list of current Internet-Drafts can be accessed at http://www.ietf.org/ietf/1id-abstracts.txt. The list of Internet-Draft Shadow Directories can be accessed at http://www.ietf.org/shadow.html. This Internet-Draft will expire on October 9, 2005.September 5, 2006. Copyright Notice Copyright (C) The Internet Society (2005).(2006). Abstract This memo defines a new Relay Agent Subscriber-ID option for the Dynamic Host Configuration Protocol for IPv6 (DHCPv6). The option allows a DHCPv6 relay agent to associate a stable "Subscriber-ID" with DHCPv6 client messages in a way that is independent of the client and of the underlying physical network infrastructure. Table of Contents 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 3 2. Requirements Terminology . . . . . . . . . . . . . . . . . . . 3 3. The Relay Agent Subscriber-ID Option . . . . . . . . . . . . . 3 4. DHCPv6 Relay Agent Behavior . . . . . . . . . . . . . . . . . . 4 5. DHCPv6 Server Behavior . . . . . . . . . . . . . . . . . . . . 4 6. Security Considerations . . . . . . . . . . . . . . . . . . . 4. 5 7. IANA Considerations . . . . . . . . . . . . . . . . . . . . . . 5 8. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . . 5 9. References . . . . . . . . . . . . . . . . . . . . . . . . . . 5 9.19.1. Normative References . . . . . . . . . . . . . . . . . . . 5 9.29.2. Informative References . . . . . . . . . . . . . . . . . . 5 Author's Address . . . . . . . . . . . . . . . . . . . . . . . 5. . 7 Intellectual Property and Copyright Statements . . . . . . . . 6. . 8 1. Introduction DHCPv6  provides IP addresses and configuration information for IPv6 clients. It includes a relay agent capability, in which processes within the network infrastructure receive multicast messages from clients and relay them to DHCPv6 servers. In some network environments, it will be useful for the relay agent to add information to the DHCPv6 message before relaying it. The information that relay agents supply can also be used in the server's decision making about the addresses, delegated prefixes , and configuration parameters that the client is to receive. In many service provider environments, it is believed to be desirable to associate some provider-specific information with clients' DHCPv6 messages that is independent of the physical network configuration and which the relay agent has learned through some means which is outside the scope of this memo. 2. Requirements Terminology The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this document are to be interpreted as described in . 3. The Relay Agent Subscriber-ID Option In complex service provider environments, there is a need to connect a customer's DHCPv6 configuration with the customer's administrative information. The Relay Agent Subscriber-ID option carries a value that can be independent of the physical network configuration through which the subscriber is connected. This value complements, and might well be used in addition to, the network-based information. The "subscriber-id" assigned by the provider is intended to be stable as customers connect through different paths, and as network changes occur. The subscriber-id information allows the service provider to assign/ activate subscriber-specific actions, e.g. assignment of specific IP addresses, prefixes, DNS configuration, trigger accounting, etc. This option is de-coupled from the access network's physical structure, so subscriber moves from one access-point to another, for example, would not require reconfiguration at the service provider's DHCPv6 servers. The subscriber-id information is an NVT ASCII  string. The semantic contents ofonly intended for use within a single administrative domain and is only exchanged between the subscriber-id field arerelay agents and DHCPv6 servers within that domain. Therefore, the format of course provider-specific. Thisand encoding of the data in the option is not standardized and this specification does not establish any semantic requirements on the data indata. This specification only defines the option for conveying this information from relay agents to DHCPv6 servers. However, as the string.DHCPv4 Subscriber-ID suboption  specifies NVT ASCII  encoded data, in environments where both DHCPv4  and DHCPv6 are being used, it MAY be beneficial to use that encoding. The format of the DHCPv6 Relay Agent Subscriber-ID option is shown below: 0 1 2 3 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | OPTION_SUBSCRIBER_ID | option-len | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ . . . subscriber-id . . . +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ option-code OPTION_SUBSCRIBER_ID (TBD) option-len length, in octets, of the subscriber-id field. The minimum length is 1 octet. subscriber-id A NVT ASCII string. It MUST NOT be null terminated.The subscriber's identity. 4. DHCPv6 Relay Agent Behavior DHCPv6 relay agents MAY be configured to include a Subscriber-ID option in relayed (RELAY-FORW) DHCPv6 messages. TheHow the subscriber-id strings themselves areis assigned and configured throughthe mechanisms thatused to configure it are outside the scope of this memo. 5. DHCPv6 Server Behavior This option provides additional information to the DHCPv6 server. The DHCPv6 server, if it is configured to support this option,server MAY use this informationinformation, if available, in addition to other relay agent option data, other options included in the DHCPv6 client messages, and physical network topology information in order to assign IP addresses, delegate prefixes, and/or other configuration parameters to the client. There is no special additional processing for this option. There is no requirement that a server return this option and its data in a RELAY-REPLY message. 6. Security Considerations SeeAs the subscriber-id option is only exchanged between relay agents and DHCPv6 servers,  section 21.1, provides details on securing DHCPv6 messages sent between servers and relay agents, andagents. And,  section 23, onprovides general DHCPv6 security considerations. 7. IANA Considerations IANA is requested to assign a DHCPv6 option code for the Relay Agent Subscriber-ID Option. 8. Acknowledgements Thanks to Richard Johnson, Theyn Palaniappan, and Mark Stapp as this document is essentially an edited verisonversion of their memo .. 9. References 9.19.1. Normative References  Droms, R., Bound, J., Volz, B., Lemon, T., Perkins, C., and M. Carney, "Dynamic Host Configuration Protocol for IPv6 (DHCPv6)", RFC 3315, July 2003.  Bradner, S., "Key words for use in RFCs to Indicate Requirement Levels", BCP 14, RFC 2119, March 1997. 9.29.2. Informative References  Troan, O. and R. Droms, "IPv6 Prefix Options for Dynamic Host Configuration Protocol (DHCP) version 6", RFC 3633, December 2003.  Postel, J. and J. Reynolds, "Telnet Protocol Specification", STD 8, RFC 854, May 1983. Johnson, R., Palaniappan, T., and M. Stapp, "Subscriber-ID Suboption for the Dynamic Host Configuration Protocol (DHCP) Relay Agent Option", RFC 3993, March 2005.  Postel, J. and J. Reynolds, "Telnet Protocol Specification", STD 8, RFC 854, May 1983.  Droms, R., "Dynamic Host Configuration Protocol", RFC 2131, March 1997. Author's Address Bernard Volz Cisco Systems, Inc. 1414 Massachusetts Ave. Boxborough, MA 01719 USA Phone: +1 978 936 0382 Email: email@example.com Intellectual Property Statement The IETF takes no position regarding the validity or scope of any Intellectual Property Rights or other rights that might be claimed to pertain to the implementation or use of the technology described in this document or the extent to which any license under such rights might or might not be available; nor does it represent that it has made any independent effort to identify any such rights. Information on the procedures with respect to rights in RFC documents can be found in BCP 78 and BCP 79. Copies of IPR disclosures made to the IETF Secretariat and any assurances of licenses to be made available, or the result of an attempt made to obtain a general license or permission for the use of such proprietary rights by implementers or users of this specification can be obtained from the IETF on-line IPR repository at http://www.ietf.org/ipr. The IETF invites any interested party to bring to its attention any copyrights, patents or patent applications, or other proprietary rights that may cover technology that may be required to implement this standard. Please address the information to the IETF at firstname.lastname@example.org. Disclaimer of Validity This document and the information contained herein are provided on an "AS IS" basis and THE CONTRIBUTOR, THE ORGANIZATION HE/SHE REPRESENTS OR IS SPONSORED BY (IF ANY), THE INTERNET SOCIETY AND THE INTERNET ENGINEERING TASK FORCE DISCLAIM ALL WARRANTIES, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE INFORMATION HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE. Copyright Statement Copyright (C) The Internet Society (2005).(2006). This document is subject to the rights, licenses and restrictions contained in BCP 78, and except as set forth therein, the authors retain all their rights. Acknowledgment Funding for the RFC Editor function is currently provided by the Internet Society.