Network Working Group J. Salowey Internet-Draft R. Droms Expires: March 25, 2006 Cisco Systems, Inc. September 21, 2005 RADIUS Delegated-IPv6-Prefix Attribute draft-salowey-radext-delegated-prefix-00.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 March 25, 2006. Copyright Notice Copyright (C) The Internet Society (2005). Abstract The Delegated-IPv6-Prefix attribute indicates an IPv6 prefix that is to be delegated to the user. 1. Introduction This Delegated-IPv6-Prefix indicates an IPv6 prefix to be delegated to the user. It MAY be used in Access-Accept packets, and can appear multiple times. It MAY be used in an Access-Request packet as a hint Salowey & Droms Expires March 25, 2006 [Page 1] Internet-Draft Delegated-IPv6-Prefix Attribute September 2005 by the Network Access Server (NAS) to the server that it would prefer these prefix(es), but the server is not required to honor the hint. The Delegated-IPv6-Prefix attribute is related to the Framed-IPv6- Prefix attribute [1]; it differs from the Framed-IPv6-Prefix attribute in its intended usage. The prefix in the Delegated-IPv6- Prefix attribute is delegated to another entity, while the Framed- IPv6-Prefix attribute is under the control of the NAS. For example, the prefix in a Delegated-IPv6-Prefix attribute can be delegated to another node through DHCP Prefix Delegation [2], while the prefix in a Framed-IPv6-Prefix attribute can be assigned to a link to which the NAS is attached, and subsequently advertised through Router Advertisement messages [3]. 2. 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 RFC 2119 [4]. 3. Attribute format The format of the Delegated-IPv6-Prefix is: 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 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | Type | Length | Reserved | Prefix-Length | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ Prefix +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ Prefix +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ Prefix +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ Prefix | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ Type (to be assigned by IANA). Length At least 4 and no larger than 20 Reserved Always set to zero Prefix-Length The length of the prefix, in bits. At least 0 and no larger than 128 Note that the prefix field is only required to be long enough to hold the prefix bits and can be shorter than 16 bytes. Any bits in the prefix field that are not part of the prefix MUST be zero. Salowey & Droms Expires March 25, 2006 [Page 2] Internet-Draft Delegated-IPv6-Prefix Attribute September 2005 The definition of the Delegated-IPv6-Prefix Attribute is based on the Framed-IPv6-Prefix attribute. 4. IANA Considerations IANA is requested to assign a Type value for this Attribute from the RADIUS Types registry. 5. Security Considerations Known security vulnerabilities of the RADIUS protocol are discussed in RFC 2607 [5], RFC 2865 [6] and RFC 2869 [7]. Use of IPSEC [8] for providing security when RADIUS is carried in IPv6 is discussed in RFC 3162 [1]. 6. Normative References [1] Aboba, B., Zorn, G., and D. Mitton, "RADIUS and IPv6", RFC 3162, August 2001. [2] Troan, O. and R. Droms, "IPv6 Prefix Options for Dynamic Host Configuration Protocol (DHCP) version 6", RFC 3633, December 2003. [3] Narten, T., Nordmark, E., and W. Simpson, "Neighbor Discovery for IP Version 6 (IPv6)", RFC 2461, December 1998. [4] Bradner, S., "Key words for use in RFCs to Indicate Requirement Levels", BCP 14, RFC 2119, March 1997. [5] Aboba, B. and J. Vollbrecht, "Proxy Chaining and Policy Implementation in Roaming", RFC 2607, June 1999. [6] Rigney, C., Willens, S., Rubens, A., and W. Simpson, "Remote Authentication Dial In User Service (RADIUS)", RFC 2865, June 2000. [7] Rigney, C., Willats, W., and P. Calhoun, "RADIUS Extensions", RFC 2869, June 2000. [8] Kent, S. and R. Atkinson, "Security Architecture for the Internet Protocol", RFC 2401, November 1998. Salowey & Droms Expires March 25, 2006 [Page 3] Internet-Draft Delegated-IPv6-Prefix Attribute September 2005 Authors' Addresses Joe Salowey Cisco Systems, Inc. 2901 Third Avenue Seattle, WA 98121 USA Phone: +1 206.310.0596 Email: jsalowey@cisco.com Ralph Droms Cisco Systems, Inc. 1414 Massachusetts Avenue Boxborough, MA 01719 USA Phone: +1 978.936.1674 Email: rdroms@cisco.com Salowey & Droms Expires March 25, 2006 [Page 4] Internet-Draft Delegated-IPv6-Prefix Attribute September 2005 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 ietf-ipr@ietf.org. The IETF has been notified of intellectual property rights claimed in regard to some or all of the specification contained in this document. For more information consult the online list of claimed rights. 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). 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. Salowey & Droms Expires March 25, 2006 [Page 5] Internet-Draft Delegated-IPv6-Prefix Attribute September 2005 Acknowledgment Funding for the RFC Editor function is currently provided by the Internet Society. Salowey & Droms Expires March 25, 2006 [Page 6]