idnits 2.17.1 draft-perkins-dmm-4283mnids-00.txt: Checking boilerplate required by RFC 5378 and the IETF Trust (see https://trustee.ietf.org/license-info): ---------------------------------------------------------------------------- No issues found here. Checking nits according to https://www.ietf.org/id-info/1id-guidelines.txt: ---------------------------------------------------------------------------- == No 'Intended status' indicated for this document; assuming Proposed Standard Checking nits according to https://www.ietf.org/id-info/checklist : ---------------------------------------------------------------------------- No issues found here. Miscellaneous warnings: ---------------------------------------------------------------------------- == The copyright year in the IETF Trust and authors Copyright Line does not match the current year -- The document date (September 23, 2014) is 3501 days in the past. Is this intentional? Checking references for intended status: Proposed Standard ---------------------------------------------------------------------------- (See RFCs 3967 and 4897 for information about using normative references to lower-maturity documents in RFCs) == Unused Reference: 'RFC4285' is defined on line 133, but no explicit reference was found in the text ** Obsolete normative reference: RFC 2373 (Obsoleted by RFC 3513) ** Downref: Normative reference to an Informational RFC: RFC 4285 -- Obsolete informational reference (is this intentional?): RFC 3588 (Obsoleted by RFC 6733) Summary: 2 errors (**), 0 flaws (~~), 3 warnings (==), 2 comments (--). Run idnits with the --verbose option for more detailed information about the items above. -------------------------------------------------------------------------------- 2 Distributed Mobility Management [dmm] C. Perkins 3 Internet-Draft Futurewei 4 Expires: March 27, 2015 V. Devarapalli 5 Vasona Networks 6 September 23, 2014 8 MN Identifier Types for RFC 4283 Mobile Node Identifier Option 9 draft-perkins-dmm-4283mnids-00.txt 11 Abstract 13 Additional Identifier Types are proposed for use with the Mobile Node 14 Identifier Option for MIPv6 (RFC 4283). 16 Status of This Memo 18 This Internet-Draft is submitted in full conformance with the 19 provisions of BCP 78 and BCP 79. 21 Internet-Drafts are working documents of the Internet Engineering 22 Task Force (IETF). Note that other groups may also distribute 23 working documents as Internet-Drafts. The list of current Internet- 24 Drafts is at http://datatracker.ietf.org/drafts/current/. 26 Internet-Drafts are draft documents valid for a maximum of six months 27 and may be updated, replaced, or obsoleted by other documents at any 28 time. It is inappropriate to use Internet-Drafts as reference 29 material or to cite them other than as "work in progress." 31 This Internet-Draft will expire on March 27, 2015. 33 Copyright Notice 35 Copyright (c) 2014 IETF Trust and the persons identified as the 36 document authors. All rights reserved. 38 This document is subject to BCP 78 and the IETF Trust's Legal 39 Provisions Relating to IETF Documents 40 (http://trustee.ietf.org/license-info) in effect on the date of 41 publication of this document. Please review these documents 42 carefully, as they describe your rights and restrictions with respect 43 to this document. Code Components extracted from this document must 44 include Simplified BSD License text as described in Section 4.e of 45 the Trust Legal Provisions and are provided without warranty as 46 described in the Simplified BSD License. 48 Table of Contents 50 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 2 51 2. New Mobile Node Identifier Types . . . . . . . . . . . . . . 2 52 3. Security Considerations . . . . . . . . . . . . . . . . . . . 2 53 4. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 3 54 5. References . . . . . . . . . . . . . . . . . . . . . . . . . 3 55 5.1. Normative References . . . . . . . . . . . . . . . . . . 3 56 5.2. Informative References . . . . . . . . . . . . . . . . . 3 57 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 4 59 1. Introduction 61 The Mobile Node Identifier Option for MIPv6 [RFC4283] has proved to 62 be a popular design tool for providing identifiers for mobile nodes 63 during authentication procedures with AAA protocols such as Diameter 64 [RFC3588]. To date, only a single type of identifier has been 65 specified, namely the MN NAI. Other types of identifiers are in 66 common use, and even referenced in RFC 4283. In this document, we 67 propose adding some basic types that are commonly in use in various 68 telecommunications standards, including the IMSI, P-TMSI, IMEI, GUTI, 69 and IEEE MAC-layer addresses. In addition, we include the IPv6 70 address itself as a legitimate mobile node identifier. 72 2. New Mobile Node Identifier Types 74 The following types of identifiers are commonly used to identify 75 mobile nodes. For each type, references are provided with full 76 details on the format of the type of identifer. 78 o IPv6 Address [RFC2373] 80 o IMSI [ThreeGPP-IDS] 82 o P-TMSI [ThreeGPP-IDS] 84 o EUI-48 address [IEEE802] 86 o EUI-64 address [IEEE802] 88 o GUTI [ThreeGPP-IDS] 90 3. Security Considerations 92 This document does not introduce any security mechanisms, and does 93 not have any impact on existing security mechanisms. Insofar as the 94 selection of a security association may be dependent on the exact 95 form of a mobile node identifier, additional specification may be 96 necessary when the new identifier types are employed with the general 97 AAA mechanisms for mobile node authorizations. 99 4. IANA Considerations 101 The new mobile node identifier types defined in the document should 102 be assigned values from the "Mobile Node Identifier Option Subtypes" 103 registry. The following values should be assigned. 105 New Mobile Node Identifier Types 107 +-----------------+------------------------+ 108 | Identifier Type | Identifier Type Number | 109 +-----------------+------------------------+ 110 | IPv6 Address | 2 | 111 | IMSI | 3 | 112 | P-TMSI | 4 | 113 | EUI-48 address | 5 | 114 | EUI-64 address | 6 | 115 | GUTI | 7 | 116 +-----------------+------------------------+ 118 Table 1 120 See Section 2 for details about the identifer types. 122 5. References 124 5.1. Normative References 126 [RFC2373] Hinden, R. and S. Deering, "IP Version 6 Addressing 127 Architecture", RFC 2373, July 1998. 129 [RFC4283] Patel, A., Leung, K., Khalil, M., Akhtar, H., and K. 130 Chowdhury, "Mobile Node Identifier Option for Mobile IPv6 131 (MIPv6)", RFC 4283, November 2005. 133 [RFC4285] Patel, A., Leung, K., Khalil, M., Akhtar, H., and K. 134 Chowdhury, "Authentication Protocol for Mobile IPv6", RFC 135 4285, January 2006. 137 5.2. Informative References 139 [IEEE802] IEEE, , "IEEE Std 802: IEEE Standards for Local and 140 Metropolitan Networks: Overview and Architecture", 2001. 142 [RFC3588] Calhoun, P., Loughney, J., Guttman, E., Zorn, G., and J. 143 Arkko, "Diameter Base Protocol", RFC 3588, September 2003. 145 [ThreeGPP-IDS] 146 3rd Generation Partnership Project, , "3GPP Technical 147 Specification 23.003 V8.4.0: Technical Specification Group 148 Core Network and Terminals; Numbering, addressing and 149 identification (Release 8)", March 2009. 151 Authors' Addresses 153 Charles E. Perkins 154 Futurewei Inc. 155 2330 Central Expressway 156 Santa Clara, CA 95050 157 USA 159 Phone: +1-408-330-4586 160 Email: charliep@computer.org 162 Vijay Devarapalli 163 Vasona Networks 164 2900 Lakeside Drive, Suite 180 165 Santa Clara, CA 95054 166 USA