Mobility Extensions for IPv6 C. Perkins [mext] V. Devarapalli Internet-Draft WiChorus Inc. Expires: April 22, 2010 October 19, 2009 MN Identifier Types for RFC 4283 Mobile Node Identifier Option draft-perkins-mext-4283mnids-00.txt Status of this Memo This Internet-Draft is submitted to IETF in full conformance with the provisions of BCP 78 and 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 April 22, 2010. Copyright Notice Copyright (c) 2009 IETF Trust and the persons identified as the document authors. All rights reserved. This document is subject to BCP 78 and the IETF Trust's Legal Provisions Relating to IETF Documents in effect on the date of publication of this document (http://trustee.ietf.org/license-info). Please review these documents carefully, as they describe your rights and restrictions with respect to this document. Perkins & Devarapalli Expires April 22, 2010 [Page 1] Internet-Draft MN Identifier Types for RFC 4283 October 2009 Abstract Additional Identifier Types are proposed for use with the Mobile Node Identifier Option for MIPv6 (RFC 4283). Perkins & Devarapalli Expires April 22, 2010 [Page 2] Internet-Draft MN Identifier Types for RFC 4283 October 2009 1. Introduction The Mobile Node Identifier Option for MIPv6 [2] has proved to be a popular design tool for providing identifiers for mobile nodes during authentication procedures with AAA protocols such as Diameter [4]. To date, only a single type of identifier has been specified, namely the MN NAI. Other types of identifiers are in common use, and even referenced in RFC 4283 itself. In this document, we propose adding some basic types that are commonly in use in various telecommunications standards, including the IMSI, P-TMSI, IMEI, GUTI, and IEEE MAC-layer addresses. In addition, we include the IPv6 address itself as a legitimate mobile node identifier. Perkins & Devarapalli Expires April 22, 2010 [Page 3] Internet-Draft MN Identifier Types for RFC 4283 October 2009 2. New Mobile Node Identifier Types The following types of identifiers are commonly used to identify mobile nodes. For each type, references are provided with full details on the format of the type of identifer. o IPv6 Address [1] o IMSI [5] o P-TMSI [5] o EUI-48 address [6] o EUI-64 address [6] o GUTI [5] Perkins & Devarapalli Expires April 22, 2010 [Page 4] Internet-Draft MN Identifier Types for RFC 4283 October 2009 3. Security Considerations This document does not introduce any security mechanisms, and does not have any impact on existing security mechanisms. Insofar as the selection of a security association may be dependent on the exact form of a mobile node identifier, additional specification may be necessary when the new identifier types are employed with the general AAA mechanisms for mobile node authorizations. Perkins & Devarapalli Expires April 22, 2010 [Page 5] Internet-Draft MN Identifier Types for RFC 4283 October 2009 4. IANA Considerations The new mobile node identifier types defined in the document should be assigned values from the "Mobile Node Identifier Option Subtypes" registry. The following values should be assigned. New Mobile Node Identifier Types +-----------------+------------------------+ | Identifier Type | Identifier Type Number | +-----------------+------------------------+ | IPv6 Address | 2 | | | | | IMSI | 3 | | | | | P-TMSI | 4 | | | | | EUI-48 address | 5 | | | | | EUI-64 address | 6 | | | | | GUTI | 7 | +-----------------+------------------------+ Table 1 See Section 2 for details about the identifer types. Perkins & Devarapalli Expires April 22, 2010 [Page 6] Internet-Draft MN Identifier Types for RFC 4283 October 2009 5. References 5.1. Normative References [1] Hinden, R. and S. Deering, "IP Version 6 Addressing Architecture", RFC 2373, July 1998. [2] Patel, A., Leung, K., Khalil, M., Akhtar, H., and K. Chowdhury, "Mobile Node Identifier Option for Mobile IPv6 (MIPv6)", RFC 4283, November 2005. [3] Patel, A., Leung, K., Khalil, M., Akhtar, H., and K. Chowdhury, "Authentication Protocol for Mobile IPv6", RFC 4285, January 2006. 5.2. Informative References [4] Calhoun, P., Loughney, J., Guttman, E., Zorn, G., and J. Arkko, "Diameter Base Protocol", RFC 3588, September 2003. [5] 3rd Generation Partnership Project, "3GPP Technical Specification 23.003 V8.4.0: Technical Specification Group Core Network and Terminals; Numbering, addressing and identification (Release 8)", March 2009. [6] IEEE, "IEEE Std 802: IEEE Standards for Local and Metropolitan Networks: Overview and Architecture", 2001. Perkins & Devarapalli Expires April 22, 2010 [Page 7] Internet-Draft MN Identifier Types for RFC 4283 October 2009 Authors' Addresses Charles E. Perkins WiChorus Inc. 3590 North, 1st Street, Suite 300 San Jose, CA 95134 USA Email: charliep@computer.org Vijay Devarapalli WiChorus Inc. 3590 North, 1st Street, Suite 300 San Jose, CA 95134 USA Email: vijay@wichorus.com Perkins & Devarapalli Expires April 22, 2010 [Page 8]