idnits 2.17.1 draft-ietf-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 (April 22, 2015) is 3285 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: 'RFC4122' is defined on line 214, but no explicit reference was found in the text == Unused Reference: 'RFC4285' is defined on line 222, but no explicit reference was found in the text ** Obsolete normative reference: RFC 2373 (Obsoleted by RFC 3513) ** Obsolete normative reference: RFC 3315 (Obsoleted by RFC 8415) ** Downref: Normative reference to an Informational RFC: RFC 4285 -- Obsolete informational reference (is this intentional?): RFC 3588 (Obsoleted by RFC 6733) Summary: 3 errors (**), 0 flaws (~~), 4 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: October 24, 2015 V. Devarapalli 5 Vasona Networks 6 April 22, 2015 8 MN Identifier Types for RFC 4283 Mobile Node Identifier Option 9 draft-ietf-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 October 24, 2015. 33 Copyright Notice 35 Copyright (c) 2015 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 . . . . . . . . . . . . . . . . . . . 3 53 4. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 4 54 5. References . . . . . . . . . . . . . . . . . . . . . . . . . 6 55 5.1. Normative References . . . . . . . . . . . . . . . . . . 6 56 5.2. Informative References . . . . . . . . . . . . . . . . . 6 57 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 7 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 EPC supports several encoding systems or schemes including 80 o RFID-GID (Global Identifier), 81 o RFID-SGTIN (Serialized Global Trade Item Number), 82 o RFID-SSCC (Serial Shipping Container), 83 o RFID-GLN (Global Location Number), 84 o RFID-GRAI (Global Returnable Asset Identifier), 85 o RFID-DOD (Department of Defense) and 86 o RFID-GIAI (Global Individual Asset Identifier). 88 For each RFID scheme except GID, there are two variations: a 64-bit 89 scheme (for example, GLN-64) and a 96-bit scheme (GLN-96). GID has 90 only a 96-bit scheme. Within each scheme, an EPC identifier can be 91 represented in a binary form or other forms such as URI. 93 The following list includes the above RFID types as well as various 94 other common identifiers and several different types of DUIDs. 96 o IPv6 Address [RFC2373] 97 o IMSI [ThreeGPP-IDS] 98 o P-TMSI [ThreeGPP-IDS] 99 o GUTI [ThreeGPP-IDS] 100 o EUI-48 address [IEEE802] 101 o EUI-64 address [IEEE802] 102 o DUID-LLT [RFC3315] 103 o DUID-EN [RFC3315] 104 o DUID-LL [RFC3315] 105 o DUID-UUID [RFC6355] 106 o 12-15 reserved 107 o 16 reserved 108 o RFID-SGTIN-64 [EPC-Tag-Data] 109 o RFID-SSCC-64 [EPC-Tag-Data] 110 o RFID-GLN-64 [EPC-Tag-Data] 111 o RFID-GRAI-64 [EPC-Tag-Data] 112 o RFID-DOD-64 [RFID-DoD-96] 113 o RFID-GIAI-64 [EPC-Tag-Data] 114 o 23 reserved 115 o RFID-GID-96 [EPC-Tag-Data] 116 o RFID-SGTIN-96 [EPC-Tag-Data] 117 o RFID-SSCC-96 [EPC-Tag-Data] 118 o RFID-GLN-96 [EPC-Tag-Data] 119 o RFID-GRAI-96 [EPC-Tag-Data] 120 o RFID-DOD-96 [RFID-DoD-96] 121 o RFID-GIAI-96 [EPC-Tag-Data] 122 o 31 reserved 123 o RFID-GID-URI [EPC-Tag-Data] 124 o RFID-SGTIN-URI [EPC-Tag-Data] 125 o RFID-SSCC-URI [EPC-Tag-Data] 126 o RFID-GLN-URI [EPC-Tag-Data] 127 o RFID-GRAI-URI [EPC-Tag-Data] 128 o RFID-DOD-URI [RFID-DoD-96] 129 o RFID-GIAI-URI [EPC-Tag-Data] 130 o 39-255 reserved 132 3. Security Considerations 134 This document does not introduce any security mechanisms, and does 135 not have any impact on existing security mechanisms. Insofar as the 136 selection of a security association may be dependent on the exact 137 form of a mobile node identifier, additional specification may be 138 necessary when the new identifier types are employed with the general 139 AAA mechanisms for mobile node authorizations. 141 Some identifiers (e.g., IMSI) are considered to be private 142 information. If used in the MNID extension as defined in this 143 document, the packet including the MNID extension should be encrypted 144 so that personal information or trackable identifiers would not be 145 inadvertently disclosed to passive observers. Moreover, MNIDs 146 containing sensitive identifiers might only be used for signaling 147 during initial network entry. Subsequent binding update exchanges 148 would then rely on a temporary identifier allocated during the 149 initial network entry. 151 4. IANA Considerations 153 The new mobile node identifier types defined in the document should 154 be assigned values from the "Mobile Node Identifier Option Subtypes" 155 registry. The following values should be assigned. 157 New Mobile Node Identifier Types 159 +-----------------+------------------------+ 160 | Identifier Type | Identifier Type Number | 161 +-----------------+------------------------+ 162 | IPv6 Address | 2 | 163 | IMSI | 3 | 164 | P-TMSI | 4 | 165 | EUI-48 address | 5 | 166 | EUI-64 address | 6 | 167 | GUTI | 7 | 168 | DUID-LLT | 8 | 169 | DUID-EN | 9 | 170 | DUID-LL | 10 | 171 | DUID-UUID | 11 | 172 | | 12-15 reserved | 173 | | 16 reserved | 174 | RFID-SGTIN-64 | 17 | 175 | RFID-SSCC-64 | 18 | 176 | RFID-GLN-64 | 19 | 177 | RFID-GRAI-64 | 20 | 178 | RFID-DOD-64 | 21 | 179 | RFID-GIAI-64 | 22 | 180 | | 23 reserved | 181 | RFID-GID-96 | 24 | 182 | RFID-SGTIN-96 | 25 | 183 | RFID-SSCC-96 | 26 | 184 | RFID-GLN-96 | 27 | 185 | RFID-GRAI-96 | 28 | 186 | RFID-DOD-96 | 29 | 187 | RFID-GIAI-96 | 30 | 188 | | 31 reserved | 189 | RFID-GID-URI | 32 | 190 | RFID-SGTIN-URI | 33 | 191 | RFID-SSCC-URI | 34 | 192 | RFID-GLN-URI | 35 | 193 | RFID-GRAI-URI | 36 | 194 | RFID-DOD-URI | 37 | 195 | RFID-GIAI-URI | 38 | 196 | | 39-255 reserved | 197 +-----------------+------------------------+ 199 Table 1 201 See Section 2 for details about the identifer types. 203 5. References 205 5.1. Normative References 207 [RFC2373] Hinden, R. and S. Deering, "IP Version 6 Addressing 208 Architecture", RFC 2373, July 1998. 210 [RFC3315] Droms, R., Bound, J., Volz, B., Lemon, T., Perkins, C., 211 and M. Carney, "Dynamic Host Configuration Protocol for 212 IPv6 (DHCPv6)", RFC 3315, July 2003. 214 [RFC4122] Leach, P., Mealling, M., and R. Salz, "A Universally 215 Unique IDentifier (UUID) URN Namespace", RFC 4122, July 216 2005. 218 [RFC4283] Patel, A., Leung, K., Khalil, M., Akhtar, H., and K. 219 Chowdhury, "Mobile Node Identifier Option for Mobile IPv6 220 (MIPv6)", RFC 4283, November 2005. 222 [RFC4285] Patel, A., Leung, K., Khalil, M., Akhtar, H., and K. 223 Chowdhury, "Authentication Protocol for Mobile IPv6", RFC 224 4285, January 2006. 226 [RFC6355] Narten, T. and J. Johnson, "Definition of the UUID-Based 227 DHCPv6 Unique Identifier (DUID-UUID)", RFC 6355, August 228 2011. 230 5.2. Informative References 232 [EPC-Tag-Data] 233 EPCglobal Inc., , "EPC(TM) Generation 1 Tag Data Standards 234 Version 1.1 Rev.1.27 235 http://www.gs1.org/gsmp/kc/epcglobal/tds/ 236 tds_1_1_rev_1_27-standard-20050510.pdf", January 2005. 238 [IEEE802] IEEE, , "IEEE Std 802: IEEE Standards for Local and 239 Metropolitan Networks: Overview and Architecture", 2001. 241 [RFC3588] Calhoun, P., Loughney, J., Guttman, E., Zorn, G., and J. 242 Arkko, "Diameter Base Protocol", RFC 3588, September 2003. 244 [RFID-DoD-96] 245 Department of Defense, , "United States Department of 246 Defense Suppliers Passive RFID Information Guide (Version 247 15.0)", January 2010. 249 [ThreeGPP-IDS] 250 3rd Generation Partnership Project, , "3GPP Technical 251 Specification 23.003 V8.4.0: Technical Specification Group 252 Core Network and Terminals; Numbering, addressing and 253 identification (Release 8)", March 2009. 255 Authors' Addresses 257 Charles E. Perkins 258 Futurewei Inc. 259 2330 Central Expressway 260 Santa Clara, CA 95050 261 USA 263 Phone: +1-408-330-4586 264 Email: charliep@computer.org 266 Vijay Devarapalli 267 Vasona Networks 268 2900 Lakeside Drive, Suite 180 269 Santa Clara, CA 95054 270 USA