Network Working Group L. Morand (Ed.) Internet-Draft France Telecom R&D Expires: January 1, 2007 S. Kumar Samsung India Software Operations A. Yegin Samsung Advanced Institute of Technology S. Madanapalli Samsung India Software Operations June 30, 2006 DHCP options for PANA Authentication Agents draft-ietf-dhc-paa-option-03 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 January 1, 2007. Copyright Notice Copyright (C) The Internet Society (2006). Abstract This document defines new DHCPv4 and DHCPv6 options that contain a list of IP addresses to locate one or more of PANA Authentication Morand (Ed.), et al. Expires January 1, 2007 [Page 1] Internet-Draft PAA DHCP options June 2006 Agents. This is one of the many methods that a PANA Client can use to locate PANA Authentication Agents. Requirements Language 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 [RFC2119]. Table of Contents 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 3 2. Terminology . . . . . . . . . . . . . . . . . . . . . . . . . . 3 3. Requirements . . . . . . . . . . . . . . . . . . . . . . . . . 3 4. DHCP Specification Dependency . . . . . . . . . . . . . . . . . 3 5. PANA Authentication Agent DHCPv4 Option . . . . . . . . . . . . 4 6. PANA Authentication Agent DHCPv6 Option . . . . . . . . . . . . 4 7. IANA Considerations . . . . . . . . . . . . . . . . . . . . . . 5 8. Security Considerations . . . . . . . . . . . . . . . . . . . . 6 9. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . . 6 10. Normative References . . . . . . . . . . . . . . . . . . . . . 6 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . . 7 Intellectual Property and Copyright Statements . . . . . . . . . . 8 Morand (Ed.), et al. Expires January 1, 2007 [Page 2] Internet-Draft PAA DHCP options June 2006 1. Introduction The Protocol for carrying Authentication for Network Access (PANA) [I-D.ietf-pana-pana] defines a new Extensible Authentication Protocol (EAP) lower layer that uses IP between the protocol end points. The PANA protocol is run between a PANA Client (PaC) and a PANA Authentication Agent (PAA) in order to perform authentication and authorization for the network access service. This document specifies DHCPv4 [RFC2131] and DHCPv6 [RFC3315] options that allow PANA client (PaC) to discover PANA Authentication Agents (PAA). This is one of the many methods for locating PANA Authentication Agents: manual configuration is an example of another one. 2. Terminology This document uses the PANA terminology defined in [I-D.ietf-pana- pana]. This document uses the DHCP terminology defined in [RFC2131], [RFC2132] and [RFC3315]. 3. Requirements The keywords MUST, MUST NOT, REQUIRED, SHALL, SHALL NOT, SHOULD, SHOULD NOT, RECOMMENDED, MAY, and OPTIONAL, when they appear in this document, are to be interpreted as described in [RFC2119]. 4. DHCP Specification Dependency This document describes new options for DHCPv4 and DHCPv6 for obtaining a list of IP addresses to locate a PANA Authentication Agent. This document should be read in conjunction with the DHCPv4 specifications [RFC2131], [RFC2132] and DHCPv6 specification [RFC3315]. Definitions for terms and acronyms not specifically defined in this document are defined in [RFC2131], [RFC2132] and [RFC3315]. Morand (Ed.), et al. Expires January 1, 2007 [Page 3] Internet-Draft PAA DHCP options June 2006 5. PANA Authentication Agent DHCPv4 Option This section defines a DHCPv4 option that carries a list of 32-bit (binary) IPv4 addresses indicating one or more PANA Authentication Agents (PAA) available to the PANA client. The DHCPv4 option for PANA Authentication Agent has the format shown in Fig. 1. 0 1 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | option-code | option-length | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | | + PAA IPv4 Address + | | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | ... | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ Figure 1: PAA DHCPv4 option option-code: OPTION_PANA_AGENT (TBD) option-length: Length of the 'options' field in octets; Must be a multiple of four (4) PAA IPv4 Address: IPv4 address of a PAA for the client to use. The PAAs are listed in the order of preference for use by the client. A DHCPv4 client requests the PAA DHCPv4 Option in a Parameter Request List as described in [RFC2131] and [RFC2132]. The DHCPv4 client MUST try the records in the order listed in the PAA DHCPv4 option. 6. PANA Authentication Agent DHCPv6 Option This section defines a DHCPv6 option that carries a list of 128-bit (binary) IPv6 addresses indicating one or more PANA Authentication Agents (PAA) available to the PANA client. The DHCPv6 option for PANA Authentication Agent has the format shown in Fig. 2. Morand (Ed.), et al. Expires January 1, 2007 [Page 4] Internet-Draft PAA DHCP options June 2006 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-code | option-length | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | | + + | | + PAA IPv6 Address + | | + + | | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | .... | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ Figure 2: PAA DHCPv6 option option-code: OPTION_PANA_AGENT (TBD) option-length: Length of the 'options' field in octets; Must be a multiple of sixteen (16) PAA IPv6 Address: IPv6 address of a PAA for the client to use. The PAAs are listed in the order of preference for use by the client. A DHCPv6 client requests the PAA DHCPv6 option in an Options Request Option (ORO) as described in the DHCPv6 specification [RFC3315]. The DHCPv6 client MUST try the records in the order listed in the PAA DHCPv6 option. 7. IANA Considerations The following DHCPv4 option code for PANA Authentication Agent option must be assigned by IANA: Option Name Value Described in ----------------------------------------------- OPTION_PANA_AGENT TBD Section 5 The following DHCPv6 option codes for PANA Authentication Agent options must be assigned by IANA: Morand (Ed.), et al. Expires January 1, 2007 [Page 5] Internet-Draft PAA DHCP options June 2006 Option Name Value Described in ------------------------------------------------ OPTION_PANA_AGENT TBD Section 6 8. Security Considerations The security considerations in [RFC2131], [RFC2132] and [RFC3315] apply. If an adversary manages to modify the response from a DHCP server or insert its own response, a PANA Client could be led to contact a rogue PANA Agent, possibly one that then intercepts call requests or denies service. 9. Acknowledgements Thanks to Ralph Droms, Stig Venaas, Ted Lemon, Andre Kostur and Bernie Volz for their valuable comments. 10. Normative References [I-D.ietf-pana-pana] Forsberg, D., "Protocol for Carrying Authentication for Network Access (PANA)", draft-ietf-pana-pana-11 (work in progress), March 2006. [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate Requirement Levels", BCP 14, RFC 2119, March 1997. [RFC2131] Droms, R., "Dynamic Host Configuration Protocol", RFC 2131, March 1997. [RFC2132] Alexander, S. and R. Droms, "DHCP Options and BOOTP Vendor Extensions", RFC 2132, March 1997. [RFC2434] Narten, T. and H. Alvestrand, "Guidelines for Writing an IANA Considerations Section in RFCs", BCP 26, RFC 2434, October 1998. [RFC3315] Droms, R., Bound, J., Volz, B., Lemon, T., Perkins, C., and M. Carney, "Dynamic Host Configuration Protocol for IPv6 (DHCPv6)", RFC 3315, July 2003. Morand (Ed.), et al. Expires January 1, 2007 [Page 6] Internet-Draft PAA DHCP options June 2006 Authors' Addresses Lionel Morand France Telecom R&D 38-40 rue du general Leclerc 92794 Issy-Les-Moulineaux Cedex 9 France Phone: +33 1 45296257 Email: lionel.morand@orange-ft.com Suraj Kumar Samsung India Software Operations No. 66/1, BAGMANE TECH PARK, C V RAMAN NAGAR Bangalore India Phone: +91 80 41819999 Email: suraj.kumar@samsung.com Alper E. Yegin Samsung Advanced Institute of Technology 75 West Plumeria Drive San Jose, CA 95134 USA Phone: +1 408 544 5656 Email: alper.yegin@samsung.com Syam Madanapalli Samsung India Software Operations No. 66/1, BAGMANE TECH PARK, C V RAMAN NAGAR Bangalore India Phone: +91 80 41819999 Email: syam@samsung.com Morand (Ed.), et al. Expires January 1, 2007 [Page 7] Internet-Draft PAA DHCP options June 2006 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. 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 (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. Morand (Ed.), et al. Expires January 1, 2007 [Page 8]