idnits 2.17.1 draft-ietf-dmm-4283mnids-04.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 issues found here. 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 (January 17, 2017) is 2653 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) ** Obsolete normative reference: RFC 3315 (Obsoleted by RFC 8415) -- Obsolete informational reference (is this intentional?): RFC 3588 (Obsoleted by RFC 6733) Summary: 1 error (**), 0 flaws (~~), 1 warning (==), 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 Intended status: Standards Track V. Devarapalli 5 Expires: July 21, 2017 Vasona Networks 6 January 17, 2017 8 MN Identifier Types for RFC 4283 Mobile Node Identifier Option 9 draft-ietf-dmm-4283mnids-04.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 July 21, 2017. 33 Copyright Notice 35 Copyright (c) 2017 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. Terminology . . . . . . . . . . . . . . . . . . . . . . . . . 3 52 3. New Mobile Node Identifier Types . . . . . . . . . . . . . . 3 53 4. Descriptions of MNID types . . . . . . . . . . . . . . . . . 5 54 4.1. Description of the IPv6 address type . . . . . . . . . . 5 55 4.2. Description of the IMSI MNID type . . . . . . . . . . . . 5 56 4.3. Description of the EUI-48 address type . . . . . . . . . 5 57 4.4. Description of the EUI-64 address type . . . . . . . . . 5 58 4.5. Description of the DUID-LLT type . . . . . . . . . . . . 6 59 4.6. Description of the DUID-EN type . . . . . . . . . . . . . 6 60 4.7. Description of the DUID-LL type . . . . . . . . . . . . . 6 61 4.8. Description of the DUID-UUID type . . . . . . . . . . . . 6 62 4.9. Description of the RFID types . . . . . . . . . . . . . . 7 63 4.9.1. Description of the RFID-SGTIN-64 type . . . . . . . . 8 64 4.9.2. Description of the RFID-SGTIN-96 type . . . . . . . . 8 65 4.9.3. Description of the RFID-SSCC-64 type . . . . . . . . 8 66 4.9.4. Description of the RFID-SSCC-96 type . . . . . . . . 8 67 4.9.5. Description of the RFID-SGLN-64 type . . . . . . . . 8 68 4.9.6. Description of the RFID-SGLN-96 type . . . . . . . . 8 69 4.9.7. Description of the RFID-GRAI-64 type . . . . . . . . 9 70 4.9.8. Description of the RFID-GRAI-96 type . . . . . . . . 9 71 4.9.9. Description of the RFID-GIAI-64 type . . . . . . . . 9 72 4.9.10. Description of the RFID-GIAI-96 type . . . . . . . . 9 73 4.9.11. Description of the RFID-DoD-64 type . . . . . . . . . 9 74 4.9.12. Description of the RFID-DoD-96 type . . . . . . . . . 9 75 4.9.13. Description of the RFID URI types . . . . . . . . . . 9 76 5. Security Considerations . . . . . . . . . . . . . . . . . . . 10 77 6. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 10 78 7. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 12 79 8. References . . . . . . . . . . . . . . . . . . . . . . . . . 12 80 8.1. Normative References . . . . . . . . . . . . . . . . . . 12 81 8.2. Informative References . . . . . . . . . . . . . . . . . 12 82 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 13 84 1. Introduction 86 The Mobile Node Identifier Option for MIPv6 [RFC4283] has proved to 87 be a popular design tool for providing identifiers for mobile nodes 88 during authentication procedures with AAA protocols such as Diameter 89 [RFC3588]. To date, only a single type of identifier has been 90 specified, namely the MN NAI. Other types of identifiers are in 91 common use, and even referenced in RFC 4283. In this document, we 92 propose adding some basic types that are defined in various 93 telecommunications standards, including types for IMSI 94 [ThreeGPP-IDS], P-TMSI [ThreeGPP-IDS], IMEI [ThreeGPP-IDS], and GUTI 95 [ThreeGPP-IDS]. In addition, we specify the IPv6 address itself and 96 IEEE MAC-layer addresses as mobile node identifiers. Defining 97 identifiers that are tied to the physical elements of the device 98 (RFID, MAC address etc.) help in deployment of Mobile IP because in 99 many cases such identifiers are the most natural means for uniquely 100 identifying the device, and will avoid additional look-up steps that 101 might be needed if other identifiers were used. 103 2. Terminology 105 The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", 106 "SHOULD", "SHOULD NOT", "RECOMMENDED", "NOT RECOMMENDED", "MAY", and 107 "OPTIONAL" in this document are to be interpreted as described in 108 [RFC2119]. 110 3. New Mobile Node Identifier Types 112 The following types of identifiers are commonly used to identify 113 mobile nodes. For each type, references are provided with full 114 details on the format of the type of identifer. 116 The Tag Data standard promoted by Electronic Product Code(TM) 117 (abbreviated EPC) supports several encoding systems or schemes 118 including 120 o RFID-GID (Global Identifier), 121 o RFID-SGTIN (Serialized Global Trade Item Number), 122 o RFID-SSCC (Serial Shipping Container), 123 o RFID-SGLN (Global Location Number), 124 o RFID-GRAI (Global Returnable Asset Identifier), 125 o RFID-DOD (Department of Defense ID), and 126 o RFID-GIAI (Global Individual Asset Identifier). 128 For each RFID scheme except GID, there are two variations: a 64-bit 129 scheme (for example, SGLN-64) and a 96-bit scheme (SGLN-96). GID has 130 only a 96-bit scheme. Within each scheme, an EPC identifier can be 131 represented in a binary form or other forms such as URI. 133 The following list includes the above RFID types as well as various 134 other common identifiers and several different types of DUIDs. 136 Mobile Node Identifier Description 138 +----------------+--------------------------------+-----------------+ 139 | Identifier | Description | Reference | 140 | Type | | | 141 +----------------+--------------------------------+-----------------+ 142 | IPv6 Address | | [RFC4291] | 143 | IMSI | International Mobile | [ThreeGPP-IDS] | 144 | | Subscriber Identity | | 145 | P-TMSI | Packet-Temporary Mobile | [ThreeGPP-IDS] | 146 | | Subscriber Identity | | 147 | GUTI | Globally Unique Temporary ID | [ThreeGPP-IDS] | 148 | EUI-48 address | 48-bit Extended Unique | [IEEE802] | 149 | | Identifier | | 150 | EUI-64 address | 64-bit Extended Unique | [IEEE802] | 151 | | Identifier-64 bit | | 152 | DUID-LLT | DHCPv6 Unique Identifier: | [RFC3315] | 153 | | Link-Layer address plus | | 154 | | timestamp | | 155 | DUID-EN | DHCPv6 Unique Identifier: | [RFC3315] | 156 | | Enterprise Number plus add'l | | 157 | | data | | 158 | DUID-LL | DHCPv6 Unique Identifier: | [RFC3315] | 159 | | Link-Layer address | | 160 | DUID-UUID | DHCPv6 Unique Identifier: | [RFC6355] | 161 | | other conformant format | | 162 | RFID-SGTIN-64 | 64-bit Serialized Global Trade | [EPC-Tag-Data] | 163 | | Item Number | | 164 | RFID-SSCC-64 | 64-bit Serial Shipping | [EPC-Tag-Data] | 165 | | Container | | 166 | RFID-SGLN-64 | 64-bit Serialized Global | [EPC-Tag-Data] | 167 | | Location Number | | 168 | RFID-GRAI-64 | 64-bit Global Returnable Asset | [EPC-Tag-Data] | 169 | | Identifier | | 170 | RFID-DOD-64 | 64-bit Department of Defense | [RFID-DoD-spec] | 171 | | ID | | 172 | RFID-GIAI-64 | 64-bit Global Individual Asset | [EPC-Tag-Data] | 173 | | Identifier | | 174 | RFID-GID-96 | 96-bit Global Identifier | [EPC-Tag-Data] | 175 | RFID-SGTIN-96 | 96-bit Serialized Global Trade | [EPC-Tag-Data] | 176 | | Item Number | | 177 | RFID-SSCC-96 | 96-bit Serial Shipping | [EPC-Tag-Data] | 178 | | Container | | 179 | RFID-SGLN-96 | 96-bit Serialized Global | [EPC-Tag-Data] | 180 | | Location Number | | 181 | RFID-GRAI-96 | 96-bit Global Returnable Asset | [EPC-Tag-Data] | 182 | | Identifier | | 183 | RFID-DOD-96 | 96-bit Department of Defense | [RFID-DoD-spec] | 184 | | ID | | 185 | RFID-GIAI-96 | 96-bit Global Individual Asset | [EPC-Tag-Data] | 186 | | Identifier | | 187 | RFID-GID-URI | Global Identifier represented | [EPC-Tag-Data] | 188 | | as URI | | 189 | RFID-SGTIN-URI | Serialized Global Trade Item | [EPC-Tag-Data] | 190 | | Number represented as URI | | 191 | RFID-SSCC-URI | Serial Shipping Container | [EPC-Tag-Data] | 192 | | represented as URI | | 193 | RFID-SGLN-URI | Global Location Number | [EPC-Tag-Data] | 194 | | represented as URI | | 195 | RFID-GRAI-URI | Global Returnable Asset | [EPC-Tag-Data] | 196 | | Identifier represented as URI | | 197 | RFID-DOD-URI | Department of Defense ID | [RFID-DoD-spec] | 198 | | represented as URI | | 199 | RFID-GIAI-URI | Global Individual Asset | [EPC-Tag-Data] | 200 | | Identifier represented as URI | | 201 +----------------+--------------------------------+-----------------+ 203 Table 1 205 4. Descriptions of MNID types 207 In this section descriptions for the various MNID types are provided. 209 4.1. Description of the IPv6 address type 211 The IPv6 address [RFC4291] is encoded as a 16 octet string containing 212 the full IPv6 address. The IPv6 address MUST be a unicast routable 213 IPv6 address. Multicast addresses, link-local addresses, and the 214 unspecified IPv6 address MUST NOT be used. IPv6 Unique Local 215 Addresses (ULAs) MAY be used, as long as any security operations 216 making use of the ULA also take into account the domain in which the 217 ULA is guaranteed to be unique. 219 4.2. Description of the IMSI MNID type 221 The International Mobile Subscriber Identity (IMSI) [ThreeGPP-IDS] is 222 at most 15 decimal digits (i.e., digits from 0 through 9). The IMSI 223 MUST be encoded as a string of octets in network order, where each 224 digit occupies 4 bits. The last digit MUST be zero padded, if 225 needed, for full octet size. For example an example IMSI 226 123456123456789 would be encoded as follows: 228 0x12, 0x34, 0x56, 0x12, 0x34, 0x56, 0x78, 0x90 230 4.3. Description of the EUI-48 address type 232 The IEEE EUI-48 address [IEEE802-eui48] is encoded as a 6 octet 233 string containing the IEEE EUI-48 address. 235 4.4. Description of the EUI-64 address type 237 The IEEE EUI-64 address [IEEE802-eui64] is encoded as a 8 octet 238 string containing the full IEEE EUI-64 address. 240 4.5. Description of the DUID-LLT type 242 The DUID-LLT is the DHCPv6 Unique Identifier (DUID) formulated by 243 concatenating the link-layer address plus a timestamp [RFC3315]. 244 This type of DUID consists of a two octet type field containing the 245 value 1, a two octet hardware type code, four octets containing a 246 time value, followed by link-layer address of any one network 247 interface that is connected to the DHCP device at the time that the 248 DUID is generated. The time value is the time that the DUID is 249 generated represented in seconds since midnight (UTC), January 1, 250 2000, modulo 2^32. Since the link-layer address can be of variable 251 length the DUID-LLT is of variable length. 253 4.6. Description of the DUID-EN type 255 The DUID-EN is the DHCPv6 Unique Identifier (DUID) formulated by 256 concatenating the Enterprise Number plus some additional data 257 [RFC3315]. This form of DUID is assigned by the vendor to the 258 device. It consists of a two octet type field containing the value 259 2, the vendor's registered Private Enterprise Number as maintained by 260 IANA, followed by a unique identifier assigned by the vendor. Since 261 the vendor's unique identifier can be of variable length, the DUID-EN 262 is of variable length. 264 4.7. Description of the DUID-LL type 266 The DUID-LL is the DHCPv6 Unique Identifier (DUID) formulated by 267 concatenating the network hardware type code and the link-layer 268 address [RFC3315]. This type of DUID consists of two octets 269 containing the DUID type 3, a two octet network hardware type code, 270 followed by the link-layer address of any one network interface that 271 is permanently connected to the client or server device. For 272 example, a host that has a network interface implemented in a chip 273 that is unlikely to be removed and used elsewhere could use a DUID- 274 LL. Since the link-layer address can be of variable length, the 275 DUID-LL is of variable length. 277 4.8. Description of the DUID-UUID type 279 The DUID-UUID [RFC6355] is the DHCPv6 Unique Identifier based on the 280 Universally Unique IDentifier (UUID) [RFC4122]. This type of DUID 281 consists of two octets containing the DUID type 4, followed by 282 128-bit UUID. 284 4.9. Description of the RFID types 286 The General Identifier (GID) that is used with RFID is composed of 287 three fields - the General Manager Number, Object Class and Serial 288 Number. The General Manager Number identifies an organizational 289 entity that is responsible for maintaining the numbers in subsequent 290 fields. GID encodings include a fourth field, the header, to 291 guarantee uniqueness in the namespace defined by EPC. 293 Some of the RFID types depend on the Global Trade Item Number (GTIN) 294 code defined in the General EAN.UCC Specifications [EANUCCGS]. A 295 GTIN identifies a particular class of object, such as a particular 296 kind of product or SKU. 298 The EPC encoding scheme for SGTIN permits the direct embedding of 299 EAN.UCC System standard GTIN and Serial Number codes on EPC tags. In 300 all cases, the check digit is not encoded. Two encoding schemes are 301 specified, SGTIN-64 (64 bits) and SGTIN-96 (96 bits). 303 The Serial Shipping Container Code (SSCC) is defined by the EAN.UCC 304 Specifications. Unlike the GTIN, the SSCC is already intended for 305 assignment to individual objects and therefore does not require 306 additional fields to serve as an EPC pure identity. Two encoding 307 schemes are specified, SSCC-64 (64 bits) and SSCC-96 (96 bits). 309 The Global Location Number (GLN) is defined by the EAN.UCC 310 Specifications. A GLN can represent either a discrete, unique 311 physical location such as a warehouse slot, or an aggregate physical 312 location such as an entire warehouse. In addition, a GLN can 313 represent a logical entity that performs a business function such as 314 placing an order. The Serialized Global Location Number (SGLN) 315 includes the Company Prefix, Location Reference, and Serial Number. 317 The Global Returnable Asset Identifier (GRAI) is defined by the 318 General EAN.UCC Specifications. Unlike the GTIN, the GRAI is already 319 intended for assignment to individual objects and therefore does not 320 require any additional fields to serve as an EPC pure identity. The 321 GRAI includes the Company Prefix, Asset Type, and Serial Number. 323 The Global Individual Asset Identifier (GIAI) is defined by the 324 General EAN.UCC Specifications. Unlike the GTIN, the GIAI is already 325 intended for assignment to individual objects and therefore does not 326 require any additional fields to serve as an EPC pure identity. The 327 GRAI includes the Company Prefix, and Individual Asset Reference. 329 The DoD Construct identifier is defined by the United States 330 Department of Defense (DoD). This tag data construct may be used to 331 encode tags for shipping goods to the DoD by a supplier who has 332 already been assigned a CAGE (Commercial and Government Entity) code. 334 4.9.1. Description of the RFID-SGTIN-64 type 336 The RFID-SGTIN-64 is encoded as specified in [EPC-Tag-Data]. The 337 SGTIN-64 includes five fields: Header, Filter Value (additional data 338 that is used for fast filtering and pre-selection), Company Prefix 339 Index, Item Reference, and Serial Number. Only a limited number of 340 Company Prefixes can be represented in the 64-bit tag. 342 4.9.2. Description of the RFID-SGTIN-96 type 344 The RFID-SGTIN-96 is encoded as specified in [EPC-Tag-Data]. The 345 SGTIN-96 includes six fields: Header, Filter Value, Partition (an 346 indication of where the subsequent Company Prefix and Item Reference 347 numbers are divided), Company Prefix Index, Item Reference, and 348 Serial Number. 350 4.9.3. Description of the RFID-SSCC-64 type 352 The RFID-SSCC-64 is encoded as specified in [EPC-Tag-Data]. The 353 SSCC-64 includes four fields: Header, Filter Value, Company Prefix 354 Index, and Serial Reference. Only a limited number of Company 355 Prefixes can be represented in the 64-bit tag. 357 4.9.4. Description of the RFID-SSCC-96 type 359 The RFID-SSCC-96 is encoded as specified in [EPC-Tag-Data]. The 360 SSCC-96 includes six fields: Header, Filter Value, Partition, Company 361 Prefix, and Serial Reference, as well as 24 bits that remain 362 Unallocated and must be zero. 364 4.9.5. Description of the RFID-SGLN-64 type 366 The RFID-SGLN-64 type is encoded as specified in [EPC-Tag-Data]. The 367 SGLN-64 includes five fields: Header, Filter Value, Company Prefix 368 Index, Location Reference, and Serial Number. 370 4.9.6. Description of the RFID-SGLN-96 type 372 The RFID-SGLN-96 type is encoded as specified in [EPC-Tag-Data]. The 373 SGLN-96 includes six fields: Header, Filter Value, Partition, Company 374 Prefix, Location Reference, and Serial Number. 376 4.9.7. Description of the RFID-GRAI-64 type 378 The RFID-GRAI-64 type is encoded as specified in [EPC-Tag-Data]. The 379 GRAI-64 includes five fields: Header, Filter Value, Company Prefix 380 Index, Asset Type, and Serial Number. 382 4.9.8. Description of the RFID-GRAI-96 type 384 The RFID-GRAI-96 type is encoded as specified in [EPC-Tag-Data]. The 385 GRAI-96 includes six fields: Header, Filter Value, Partition, Company 386 Prefix, Asset Type, and Serial Number. 388 4.9.9. Description of the RFID-GIAI-64 type 390 The RFID-GIAI-64 type is encoded as specified in [EPC-Tag-Data]. The 391 GIAI-64 includes four fields: Header, Filter Value, Company Prefix 392 Index, and Individual Asset Reference. 394 4.9.10. Description of the RFID-GIAI-96 type 396 The RFID-GIAI-96 type is encoded as specified in [EPC-Tag-Data]. The 397 GIAI-96 includes five fields: Header, Filter Value, Partition, 398 Company Prefix, and Individual Asset Reference. 400 4.9.11. Description of the RFID-DoD-64 type 402 The RFID-DoD-64 type is encoded as specified in [RFID-DoD-spec]. The 403 DoD-64 type includes four fields: Header, Filter Value, Government 404 Managed Identifier, and Serial Number. 406 4.9.12. Description of the RFID-DoD-96 type 408 The RFID-DoD-96 type is encoded as specified in [RFID-DoD-spec]. The 409 DoD-96 type includes four fields: Header, Filter Value, Government 410 Managed Identifier, and Serial Number. 412 4.9.13. Description of the RFID URI types 414 In some cases, it is desirable to encode in URI form a specific 415 encoding of an RFID tag. For example, an application may prefer a 416 URI representation for report preparation. Applications that wish to 417 manipulate any additional data fields on tags may need some 418 representation other than the pure identity forms. 420 For this purpose, the fields as represented the previous sections are 421 associated with specified fields in the various URI types. For 422 instance, the URI may have fields such as CompanyPrefix, 423 ItemReference, or SerialNumber. For details and encoding specifics, 424 consult [EPC-Tag-Data]. 426 5. Security Considerations 428 This document does not introduce any security mechanisms, and does 429 not have any impact on existing security mechanisms. Insofar as the 430 selection of a security association may be dependent on the exact 431 form of a mobile node identifier, additional specification may be 432 necessary when the new identifier types are employed with the general 433 AAA mechanisms for mobile node authorizations. 435 Some identifiers (e.g., IMSI) are considered to be private 436 information. If used in the MNID extension as defined in this 437 document, the packet including the MNID extension should be encrypted 438 so that personal information or trackable identifiers would not be 439 inadvertently disclosed to passive observers. Operators can 440 potentially apply IPsec Encapsulating Security Payload (ESP) 441 [RFC4303], with confidentiality and integrity protection for 442 protecting the location information. 444 Moreover, MNIDs containing sensitive identifiers might only be used 445 for signaling during initial network entry. Subsequent binding 446 update exchanges might then rely on a temporary identifier allocated 447 during the initial network entry, perhaps using mechanisms not 448 standardized within the IETF. Managing the association between long- 449 lived and temporary identifiers is outside the scope of this 450 document. 452 6. IANA Considerations 454 The new mobile node identifier types defined in the document should 455 be assigned values from the "Mobile Node Identifier Option Subtypes" 456 registry. The following values should be assigned. 458 New Mobile Node Identifier Types 460 +-----------------+------------------------+ 461 | Identifier Type | Identifier Type Number | 462 +-----------------+------------------------+ 463 | IPv6 Address | 2 | 464 | IMSI | 3 | 465 | P-TMSI | 4 | 466 | EUI-48 address | 5 | 467 | EUI-64 address | 6 | 468 | GUTI | 7 | 469 | DUID-LLT | 8 | 470 | DUID-EN | 9 | 471 | DUID-LL | 10 | 472 | DUID-UUID | 11 | 473 | | 12-15 reserved | 474 | | 16 reserved | 475 | RFID-SGTIN-64 | 17 | 476 | RFID-SSCC-64 | 18 | 477 | RFID-SGLN-64 | 19 | 478 | RFID-GRAI-64 | 20 | 479 | RFID-DOD-64 | 21 | 480 | RFID-GIAI-64 | 22 | 481 | | 23 reserved | 482 | RFID-GID-96 | 24 | 483 | RFID-SGTIN-96 | 25 | 484 | RFID-SSCC-96 | 26 | 485 | RFID-SGLN-96 | 27 | 486 | RFID-GRAI-96 | 28 | 487 | RFID-DOD-96 | 29 | 488 | RFID-GIAI-96 | 30 | 489 | | 31 reserved | 490 | RFID-GID-URI | 32 | 491 | RFID-SGTIN-URI | 33 | 492 | RFID-SSCC-URI | 34 | 493 | RFID-SGLN-URI | 35 | 494 | RFID-GRAI-URI | 36 | 495 | RFID-DOD-URI | 37 | 496 | RFID-GIAI-URI | 38 | 497 | | 39-255 reserved | 498 +-----------------+------------------------+ 500 Table 2 502 See Section 4 for additional information about the identifier types. 504 7. Acknowledgements 506 The authors wish to acknowledge Hakima Chaouchi, Tatuya Jinmei, Jouni 507 Korhonen and Sri Gundavelli for their helpful comments. 509 8. References 511 8.1. Normative References 513 [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate 514 Requirement Levels", BCP 14, RFC 2119, 515 DOI 10.17487/RFC2119, March 1997, 516 . 518 [RFC3315] Droms, R., Ed., Bound, J., Volz, B., Lemon, T., Perkins, 519 C., and M. Carney, "Dynamic Host Configuration Protocol 520 for IPv6 (DHCPv6)", RFC 3315, DOI 10.17487/RFC3315, July 521 2003, . 523 [RFC4122] Leach, P., Mealling, M., and R. Salz, "A Universally 524 Unique IDentifier (UUID) URN Namespace", RFC 4122, 525 DOI 10.17487/RFC4122, July 2005, 526 . 528 [RFC4283] Patel, A., Leung, K., Khalil, M., Akhtar, H., and K. 529 Chowdhury, "Mobile Node Identifier Option for Mobile IPv6 530 (MIPv6)", RFC 4283, DOI 10.17487/RFC4283, November 2005, 531 . 533 [RFC4291] Hinden, R. and S. Deering, "IP Version 6 Addressing 534 Architecture", RFC 4291, DOI 10.17487/RFC4291, February 535 2006, . 537 [RFC4303] Kent, S., "IP Encapsulating Security Payload (ESP)", 538 RFC 4303, DOI 10.17487/RFC4303, December 2005, 539 . 541 [RFC6355] Narten, T. and J. Johnson, "Definition of the UUID-Based 542 DHCPv6 Unique Identifier (DUID-UUID)", RFC 6355, 543 DOI 10.17487/RFC6355, August 2011, 544 . 546 8.2. Informative References 548 [EANUCCGS] 549 EAN International and the Uniform Code Council, , "General 550 EAN.UCC Specifications Version 5.0", Jan 2004. 552 [EPC-Tag-Data] 553 EPCglobal Inc., , "EPC(TM) Generation 1 Tag Data Standards 554 Version 1.1 Rev.1.27 555 http://www.gs1.org/gsmp/kc/epcglobal/tds/ 556 tds_1_1_rev_1_27-standard-20050510.pdf", January 2005. 558 [IEEE802] IEEE, , "IEEE Std 802: IEEE Standards for Local and 559 Metropolitan Networks: Overview and Architecture", 2001. 561 [IEEE802-eui48] 562 IEEE, , "Guidelines for 48-Bit Global Identifier (EUI-48) 563 https://standards.ieee.org/develop/regauth/tut/eui48.pdf", 564 2001. 566 [IEEE802-eui64] 567 IEEE, , "Guidelines for 64-Bit Global Identifier (EUI-64) 568 https://standards.ieee.org/develop/regauth/tut/eui.pdf64", 569 2001. 571 [RFC3588] Calhoun, P., Loughney, J., Guttman, E., Zorn, G., and J. 572 Arkko, "Diameter Base Protocol", RFC 3588, 573 DOI 10.17487/RFC3588, September 2003, 574 . 576 [RFID-DoD-spec] 577 Department of Defense, , "United States Department of 578 Defense Suppliers Passive RFID Information Guide (Version 579 15.0)", January 2010. 581 [ThreeGPP-IDS] 582 3rd Generation Partnership Project, , "3GPP Technical 583 Specification 23.003 V8.4.0: Technical Specification Group 584 Core Network and Terminals; Numbering, addressing and 585 identification (Release 8)", March 2009. 587 Authors' Addresses 589 Charles E. Perkins 590 Futurewei Inc. 591 2330 Central Expressway 592 Santa Clara, CA 95050 593 USA 595 Phone: +1-408-330-4586 596 Email: charliep@computer.org 597 Vijay Devarapalli 598 Vasona Networks 599 2900 Lakeside Drive, Suite 180 600 Santa Clara, CA 95054 601 USA