idnits 2.17.1 draft-ietf-dmm-4283mnids-01.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 (October 19, 2015) is 3105 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 259, but no explicit reference was found in the text == Unused Reference: 'RFC4285' is defined on line 269, 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: April 21, 2016 V. Devarapalli 5 Vasona Networks 6 October 19, 2015 8 MN Identifier Types for RFC 4283 Mobile Node Identifier Option 9 draft-ietf-dmm-4283mnids-01.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 April 21, 2016. 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 . . . . . . . . . . . . . . . . . . . 4 53 4. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 5 54 5. References . . . . . . . . . . . . . . . . . . . . . . . . . 7 55 5.1. Normative References . . . . . . . . . . . . . . . . . . 7 56 5.2. Informative References . . . . . . . . . . . . . . . . . 7 57 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 8 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 defined in various 68 telecommunications standards, including types for IMSI 69 [ThreeGPP-IDS], P-TMSI [ThreeGPP-IDS], IMEI [ThreeGPP-IDS], and GUTI 70 [ThreeGPP-IDS]. In addition, we include IEEE MAC-layer addresses the 71 IPv6 address itself as a legitimate mobile node identifier. Defining 72 identifiers that are tied to the physical elements of the device 73 (RFID, MAC address etc.) help in deployment of Mobile IP because in 74 many cases such identifiers are the most natural means for uniquely 75 identifying the device, and will avoid additional look-up steps that 76 might be needed if other identifiers were used. 78 2. New Mobile Node Identifier Types 80 The following types of identifiers are commonly used to identify 81 mobile nodes. For each type, references are provided with full 82 details on the format of the type of identifer. 84 The Tag Data standard promoted by Electronic Product Code(TM) 85 (abbreviated EPC) supports several encoding systems or schemes 86 including 88 o RFID-GID (Global Identifier), 89 o RFID-SGTIN (Serialized Global Trade Item Number), 90 o RFID-SSCC (Serial Shipping Container), 91 o RFID-GLN (Global Location Number), 92 o RFID-GRAI (Global Returnable Asset Identifier), 93 o RFID-DOD (Department of Defense ID), and 94 o RFID-GIAI (Global Individual Asset Identifier). 96 For each RFID scheme except GID, there are two variations: a 64-bit 97 scheme (for example, GLN-64) and a 96-bit scheme (GLN-96). GID has 98 only a 96-bit scheme. Within each scheme, an EPC identifier can be 99 represented in a binary form or other forms such as URI. 101 The following list includes the above RFID types as well as various 102 other common identifiers and several different types of DUIDs. 104 Mobile Node Identifier Description 106 +----------------+---------------------------------+----------------+ 107 | Identifier | Description | Reference | 108 | Type | | | 109 +----------------+---------------------------------+----------------+ 110 | IPv6 Address | | [RFC2373] | 111 | IMSI | International Mobile Subscriber | [ThreeGPP-IDS] | 112 | | Identity | | 113 | P-TMSI | Packet-Temporary Mobile | [ThreeGPP-IDS] | 114 | | Subscriber Identity | | 115 | GUTI | Globally Unique Temporary ID | [ThreeGPP-IDS] | 116 | EUI-48 address | 48-bit Extended Unique | [IEEE802] | 117 | | Identifier | | 118 | EUI-64 address | 64-bit Extended Unique | [IEEE802] | 119 | | Identifier-64 bit | | 120 | DUID-LLT | DHCPv6 Unique Identifier: Link- | [RFC3315] | 121 | | Layer address plus timestamp | | 122 | DUID-EN | DHCPv6 Unique Identifier: | [RFC3315] | 123 | | Enterprise Number plus add'l | | 124 | | data | | 125 | DUID-LL | DHCPv6 Unique Identifier: Link- | [RFC3315] | 126 | | Layer address | | 127 | DUID-UUID | DHCPv6 Unique Identifier: other | [RFC6355] | 128 | | conformant format | | 129 | RFID-SGTIN-64 | 64-bit Serialized Global Trade | [EPC-Tag-Data] | 130 | | Item Number | | 131 | RFID-SSCC-64 | 64-bit Serial Shipping | [EPC-Tag-Data] | 132 | | Container | | 133 | RFID-GLN-64 | 64-bit Global Location Number | [EPC-Tag-Data] | 134 | RFID-GRAI-64 | 64-bit Global Returnable Asset | [EPC-Tag-Data] | 135 | | Identifier | | 136 | RFID-DOD-64 | 64-bit Department of Defense ID | [RFID-DoD-96] | 137 | RFID-GIAI-64 | 64-bit Global Individual Asset | [EPC-Tag-Data] | 138 | | Identifier | | 139 | RFID-GID-96 | 96-bit Global Identifier | [EPC-Tag-Data] | 140 | RFID-SGTIN-96 | 96-bit Serialized Global Trade | [EPC-Tag-Data] | 141 | | Item Number | | 142 | RFID-SSCC-96 | 96-bit Serial Shipping | [EPC-Tag-Data] | 143 | | Container | | 144 | RFID-GLN-96 | 96-bit Global Location Number | [EPC-Tag-Data] | 145 | RFID-GRAI-96 | 96-bit Global Returnable Asset | [EPC-Tag-Data] | 146 | | Identifier | | 147 | RFID-DOD-96 | 96-bit Department of Defense ID | [RFID-DoD-96] | 148 | RFID-GIAI-96 | 96-bit Global Individual Asset | [EPC-Tag-Data] | 149 | | Identifier | | 150 | RFID-GID-URI | Global Identifier represented | [EPC-Tag-Data] | 151 | | as URI | | 152 | RFID-SGTIN-URI | Serialized Global Trade Item | [EPC-Tag-Data] | 153 | | Number represented as URI | | 154 | RFID-SSCC-URI | Serial Shipping Container | [EPC-Tag-Data] | 155 | | represented as URI | | 156 | RFID-GLN-URI | Global Location Number | [EPC-Tag-Data] | 157 | | represented as URI | | 158 | RFID-GRAI-URI | Global Returnable Asset | [EPC-Tag-Data] | 159 | | Identifier represented as URI | | 160 | RFID-DOD-URI | Department of Defense ID | [RFID-DoD-96] | 161 | | represented as URI | | 162 | RFID-GIAI-URI | Global Individual Asset | [EPC-Tag-Data] | 163 | | Identifier represented as URI | | 164 +----------------+---------------------------------+----------------+ 166 Table 1 168 3. Security Considerations 170 This document does not introduce any security mechanisms, and does 171 not have any impact on existing security mechanisms. Insofar as the 172 selection of a security association may be dependent on the exact 173 form of a mobile node identifier, additional specification may be 174 necessary when the new identifier types are employed with the general 175 AAA mechanisms for mobile node authorizations. 177 Some identifiers (e.g., IMSI) are considered to be private 178 information. If used in the MNID extension as defined in this 179 document, the packet including the MNID extension should be encrypted 180 so that personal information or trackable identifiers would not be 181 inadvertently disclosed to passive observers. Operators can 182 potentially apply IPsec Encapsulating Security Payload (ESP) with 183 confidentiality and integrity protection for protecting the location 184 information. 186 Moreover, MNIDs containing sensitive identifiers might only be used 187 for signaling during initial network entry. Subsequent binding 188 update exchanges might then rely on a temporary identifier allocated 189 during the initial network entry, perhaps using mechanisms not 190 standardized within the IETF. Managing the association between long- 191 lived and temporary identifiers is outside the scope of this 192 document. 194 4. IANA Considerations 196 The new mobile node identifier types defined in the document should 197 be assigned values from the "Mobile Node Identifier Option Subtypes" 198 registry. The following values should be assigned. 200 New Mobile Node Identifier Types 202 +-----------------+------------------------+ 203 | Identifier Type | Identifier Type Number | 204 +-----------------+------------------------+ 205 | IPv6 Address | 2 | 206 | IMSI | 3 | 207 | P-TMSI | 4 | 208 | EUI-48 address | 5 | 209 | EUI-64 address | 6 | 210 | GUTI | 7 | 211 | DUID-LLT | 8 | 212 | DUID-EN | 9 | 213 | DUID-LL | 10 | 214 | DUID-UUID | 11 | 215 | | 12-15 reserved | 216 | | 16 reserved | 217 | RFID-SGTIN-64 | 17 | 218 | RFID-SSCC-64 | 18 | 219 | RFID-GLN-64 | 19 | 220 | RFID-GRAI-64 | 20 | 221 | RFID-DOD-64 | 21 | 222 | RFID-GIAI-64 | 22 | 223 | | 23 reserved | 224 | RFID-GID-96 | 24 | 225 | RFID-SGTIN-96 | 25 | 226 | RFID-SSCC-96 | 26 | 227 | RFID-GLN-96 | 27 | 228 | RFID-GRAI-96 | 28 | 229 | RFID-DOD-96 | 29 | 230 | RFID-GIAI-96 | 30 | 231 | | 31 reserved | 232 | RFID-GID-URI | 32 | 233 | RFID-SGTIN-URI | 33 | 234 | RFID-SSCC-URI | 34 | 235 | RFID-GLN-URI | 35 | 236 | RFID-GRAI-URI | 36 | 237 | RFID-DOD-URI | 37 | 238 | RFID-GIAI-URI | 38 | 239 | | 39-255 reserved | 240 +-----------------+------------------------+ 242 Table 2 244 See Section 2 for additional information about the identifier types. 246 5. References 248 5.1. Normative References 250 [RFC2373] Hinden, R. and S. Deering, "IP Version 6 Addressing 251 Architecture", RFC 2373, DOI 10.17487/RFC2373, July 1998, 252 . 254 [RFC3315] Droms, R., Ed., Bound, J., Volz, B., Lemon, T., Perkins, 255 C., and M. Carney, "Dynamic Host Configuration Protocol 256 for IPv6 (DHCPv6)", RFC 3315, DOI 10.17487/RFC3315, July 257 2003, . 259 [RFC4122] Leach, P., Mealling, M., and R. Salz, "A Universally 260 Unique IDentifier (UUID) URN Namespace", RFC 4122, 261 DOI 10.17487/RFC4122, July 2005, 262 . 264 [RFC4283] Patel, A., Leung, K., Khalil, M., Akhtar, H., and K. 265 Chowdhury, "Mobile Node Identifier Option for Mobile IPv6 266 (MIPv6)", RFC 4283, DOI 10.17487/RFC4283, November 2005, 267 . 269 [RFC4285] Patel, A., Leung, K., Khalil, M., Akhtar, H., and K. 270 Chowdhury, "Authentication Protocol for Mobile IPv6", 271 RFC 4285, DOI 10.17487/RFC4285, January 2006, 272 . 274 [RFC6355] Narten, T. and J. Johnson, "Definition of the UUID-Based 275 DHCPv6 Unique Identifier (DUID-UUID)", RFC 6355, 276 DOI 10.17487/RFC6355, August 2011, 277 . 279 5.2. Informative References 281 [EPC-Tag-Data] 282 EPCglobal Inc., , "EPC(TM) Generation 1 Tag Data Standards 283 Version 1.1 Rev.1.27 284 http://www.gs1.org/gsmp/kc/epcglobal/tds/ 285 tds_1_1_rev_1_27-standard-20050510.pdf", January 2005. 287 [IEEE802] IEEE, , "IEEE Std 802: IEEE Standards for Local and 288 Metropolitan Networks: Overview and Architecture", 2001. 290 [RFC3588] Calhoun, P., Loughney, J., Guttman, E., Zorn, G., and J. 291 Arkko, "Diameter Base Protocol", RFC 3588, 292 DOI 10.17487/RFC3588, September 2003, 293 . 295 [RFID-DoD-96] 296 Department of Defense, , "United States Department of 297 Defense Suppliers Passive RFID Information Guide (Version 298 15.0)", January 2010. 300 [ThreeGPP-IDS] 301 3rd Generation Partnership Project, , "3GPP Technical 302 Specification 23.003 V8.4.0: Technical Specification Group 303 Core Network and Terminals; Numbering, addressing and 304 identification (Release 8)", March 2009. 306 Authors' Addresses 308 Charles E. Perkins 309 Futurewei Inc. 310 2330 Central Expressway 311 Santa Clara, CA 95050 312 USA 314 Phone: +1-408-330-4586 315 Email: charliep@computer.org 317 Vijay Devarapalli 318 Vasona Networks 319 2900 Lakeside Drive, Suite 180 320 Santa Clara, CA 95054 321 USA