Network Working Group A. Patel Internet-Draft K. Leung Expires: June 9, 2005 Cisco Systems M. Khalil H. Akhtar Nortel Networks K. Chowdhury Starent Networks December 9, 2004 MN Identifier Option for Mobile IPv6 draft-ietf-mip6-mn-ident-option-00.txt Status of this Memo By submitting this Internet-Draft, I certify that any applicable patent or other IPR claims of which I am aware have been disclosed, and any of which I become aware will be disclosed, in accordance with RFC 3668. 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 June 9, 2005. Copyright Notice Copyright (C) The Internet Society (2004). All Rights Reserved. Abstract This document defines new mobility option to identify mobility entities using identifiers other than the home IP address. This option can be used in messages containing a mobility header. Patel, et al. Expires June 9, 2005 [Page 1] Internet-Draft MN Identifier Option for Mobile IPv6 December 2004 Table of Contents 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 3 2. Terminology . . . . . . . . . . . . . . . . . . . . . . . . . 4 3. MN Identifier option . . . . . . . . . . . . . . . . . . . . . 5 3.1 MN-NAI mobility option . . . . . . . . . . . . . . . . . . 6 3.2 Processing Considerations . . . . . . . . . . . . . . . . 6 4. Security Considerations . . . . . . . . . . . . . . . . . . . 7 5. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 8 6. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . . 9 7. Normative References . . . . . . . . . . . . . . . . . . . . . 9 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . 9 Intellectual Property and Copyright Statements . . . . . . . . 11 Patel, et al. Expires June 9, 2005 [Page 2] Internet-Draft MN Identifier Option for Mobile IPv6 December 2004 1. Introduction The base specification of Mobile IPv6 [RFC3775] identifies mobility entities using an IPv6 address. A mechanism is needed where in mobility entities can be identified using other identifiers (for example, a network access identifier (NAI) [RFC2486], International Mobile Station Identifier (IMSI), an application/deployment specific opaque identifier etc). Using other identities for a mobile node (MN) permits various applicabilities, e.g. authentication using existing infrastructure (AAA (Authentication, Authorization and Accounting), HLR/AuC (Home Location Register/Authentication Center)), dynamic allocation of a mobility anchor point, dynamic allocation of an address etc. This document defines an option with subtype number which identify a specific type of identifier. One instance of subtype, the NAI is defined in Section 3.1. It is expected that other types of identifiers will be defined by other documents in the future. Patel, et al. Expires June 9, 2005 [Page 3] Internet-Draft MN Identifier Option for Mobile IPv6 December 2004 2. Terminology The keywords "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. Patel, et al. Expires June 9, 2005 [Page 4] Internet-Draft MN Identifier Option for Mobile IPv6 December 2004 3. MN Identifier option This section defines the Mobile Node Identifier option. Various forms of identifiers can be used to identify a MN. Some examples include a Network Access Identifier (NAI) [RFC2486], an opaque identifier applicable to a particular application, etc. The sub-type field in the option defines the specific type of identifier. This option can be used in mobility messages containing a mobility header. The subtype field in the option is used to interpret the specific type of identifier. 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 Type | Option Length | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | Subtype | Identifier ... +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ Option Type: MN-ID-OPTION-TYPE to be defined by IANA. An 8-bit identifier of the type mobility option. Option Length: 8-bit unsigned integer, representing the length in octets of the Subtype and Identifier fields. Subtype: Subtype field defines the specific type of identifier included in the identifier field. Identifier: A variable length identifier of type as specified by the subtype field of this option. Alignment requirements: This option does not have any alignment requirements. Patel, et al. Expires June 9, 2005 [Page 5] Internet-Draft MN Identifier Option for Mobile IPv6 December 2004 3.1 MN-NAI mobility option The format of the MN-NAI mobility option is as defined in Section 3. This option uses the subtype value of 1. The MN-NAI mobility option is used to identify the mobile node. The MN-NAI mobility option uses an identifier of the form user@realm [RFC2486]. 3.2 Processing Considerations When present, this option MUST appear before any authentication enabling extension in a message containing a mobility header. Also, if this option is present in the first Binding Update used to create a binding cache entry at the Home Agent, it MUST be present in all subsequent Binding Updates used to renew the binding cache entry. If this option is present in the Binding Update, it MUST be included in the corresponding reply (Binding Acknowledgement). Patel, et al. Expires June 9, 2005 [Page 6] Internet-Draft MN Identifier Option for Mobile IPv6 December 2004 4. Security Considerations None. This document defines new identifiers for a mobile node and does not introduce new security threats. Patel, et al. Expires June 9, 2005 [Page 7] Internet-Draft MN Identifier Option for Mobile IPv6 December 2004 5. IANA Considerations IANA services are required for this document. The values for new mobility options must be assigned from the Mobile IPv6 [RFC3775] numbering space. The values for Mobility Option types MN-ID-OPTION-TYPE as defined in Section 3 need to be assigned. The suggested value is 7 for the MN-ID-OPTION-TYPE. IANA should record value for this new Mobility Option. Patel, et al. Expires June 9, 2005 [Page 8] Internet-Draft MN Identifier Option for Mobile IPv6 December 2004 6. Acknowledgements The authors would like to thank Basavaraj Patil for his review and suggestions on this draft. 7 Normative References [RFC2486] Aboba, B. and M. Beadles, "The Network Access Identifier", RFC 2486, January 1999. [RFC3775] Johnson, D., Perkins, C. and J. Arkko, "Mobility Support in IPv6", RFC 3775, June 2004. Authors' Addresses Alpesh Patel Cisco Systems 170 W. Tasman Drive San Jose, CA 95134 US Phone: +1 408-853-9580 EMail: alpesh@cisco.com Kent Leung Cisco Systems 170 W. Tasman Drive San Jose, CA 95134 US Phone: +1 408-526-5030 EMail: kleung@cisco.com Mohamed Khalil Nortel Networks 2221 Lakeside Blvd. Richardson, TX 75082 US Phone: +1 972-685-0574 EMail: mkhalil@nortelnetworks.com Patel, et al. Expires June 9, 2005 [Page 9] Internet-Draft MN Identifier Option for Mobile IPv6 December 2004 Haseeb Akhtar Nortel Networks 2221 Lakeside Blvd. Richardson, TX 75082 US Phone: +1 972-684-4732 EMail: haseebak@nortelnetworks.com Kuntal Chowdhury Starent Networks 2540 Coolwater Dr. Plano, TX 75025 US Phone: +1 214 550 1416 EMail: kchowdury@starentnetworks.com Patel, et al. Expires June 9, 2005 [Page 10] Internet-Draft MN Identifier Option for Mobile IPv6 December 2004 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 (2004). 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. Patel, et al. Expires June 9, 2005 [Page 11]