idnits 2.17.1 draft-ietf-dmm-4283mnids-07.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 (March 4, 2018) is 2245 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) == Missing Reference: 'RFC2141' is mentioned on line 338, but not defined ** Obsolete undefined reference: RFC 2141 (Obsoleted by RFC 8141) ** Obsolete normative reference: RFC 3315 (Obsoleted by RFC 8415) -- Obsolete informational reference (is this intentional?): RFC 3588 (Obsoleted by RFC 6733) Summary: 2 errors (**), 0 flaws (~~), 2 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 Intended status: Standards Track V. Devarapalli 5 Expires: September 5, 2018 Vasona Networks 6 March 4, 2018 8 MN Identifier Types for RFC 4283 Mobile Node Identifier Option 9 draft-ietf-dmm-4283mnids-07.txt 11 Abstract 13 Additional Identifier Type Numbers are defined for use with the 14 Mobile Node 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 https://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 September 5, 2018. 33 Copyright Notice 35 Copyright (c) 2018 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 (https://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 . . . . . . . . . . . . . . . . . 3 54 4.1. Description of the IPv6 address type . . . . . . . . . . 3 55 4.2. Description of the IMSI MNID type . . . . . . . . . . . . 4 56 4.3. Description of the EUI-48 address type . . . . . . . . . 4 57 4.4. Description of the EUI-64 address type . . . . . . . . . 4 58 4.5. Description of the DUID type . . . . . . . . . . . . . . 4 59 5. Security Considerations . . . . . . . . . . . . . . . . . . . 4 60 6. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 5 61 7. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 5 62 8. References . . . . . . . . . . . . . . . . . . . . . . . . . 6 63 8.1. Normative References . . . . . . . . . . . . . . . . . . 6 64 8.2. Informative References . . . . . . . . . . . . . . . . . 6 65 Appendix A. RFID types . . . . . . . . . . . . . . . . . . . . . 7 66 A.1. Description of the RFID types . . . . . . . . . . . . . . 10 67 A.1.1. Description of the RFID-SGTIN-64 type . . . . . . . . 11 68 A.1.2. Description of the RFID-SGTIN-96 type . . . . . . . . 11 69 A.1.3. Description of the RFID-SSCC-64 type . . . . . . . . 11 70 A.1.4. Description of the RFID-SSCC-96 type . . . . . . . . 11 71 A.1.5. Description of the RFID-SGLN-64 type . . . . . . . . 11 72 A.1.6. Description of the RFID-SGLN-96 type . . . . . . . . 11 73 A.1.7. Description of the RFID-GRAI-64 type . . . . . . . . 12 74 A.1.8. Description of the RFID-GRAI-96 type . . . . . . . . 12 75 A.1.9. Description of the RFID-GIAI-64 type . . . . . . . . 12 76 A.1.10. Description of the RFID-GIAI-96 type . . . . . . . . 12 77 A.1.11. Description of the RFID-DoD-64 type . . . . . . . . . 12 78 A.1.12. Description of the RFID-DoD-96 type . . . . . . . . . 12 79 A.1.13. Description of the RFID URI types . . . . . . . . . . 12 80 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 13 82 1. Introduction 84 The Mobile Node Identifier Option for MIPv6 [RFC4283] has proved to 85 be a popular design tool for providing identifiers for mobile nodes 86 during authentication procedures with AAA protocols such as Diameter 87 [RFC3588]. To date, only a single type of identifier has been 88 specified, namely the MN NAI. Other types of identifiers are in 89 common use, and even referenced in RFC 4283. In this document, we 90 propose adding some basic types that are defined in various 91 telecommunications standards, including types for IMSI 92 [ThreeGPP-IDS], P-TMSI [ThreeGPP-IDS], IMEI [ThreeGPP-IDS], and GUTI 93 [ThreeGPP-IDS]. In addition, we specify the IPv6 address itself and 94 IEEE MAC-layer addresses as mobile node identifiers. Defining 95 identifiers that are tied to the physical elements of the device ( 96 MAC address etc.) help in deployment of Mobile IP because in many 97 cases such identifiers are the most natural means for uniquely 98 identifying the device, and will avoid additional look-up steps that 99 might be needed if other identifiers were used. 101 2. Terminology 103 The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", 104 "SHOULD", "SHOULD NOT", "RECOMMENDED", "NOT RECOMMENDED", "MAY", and 105 "OPTIONAL" in this document are to be interpreted as described in 106 [RFC2119]. 108 3. New Mobile Node Identifier Types 110 The following types of identifiers are commonly used to identify 111 mobile nodes. For each type, references are provided with full 112 details on the format of the type of identifer. 114 Mobile Node Identifier Description 116 +--------------+-----------------------------------+----------------+ 117 | Identifier | Description | Reference | 118 | Type | | | 119 +--------------+-----------------------------------+----------------+ 120 | IPv6 Address | | [RFC4291] | 121 | IMSI | International Mobile Subscriber | [ThreeGPP-IDS] | 122 | | Identity | | 123 | P-TMSI | Packet-Temporary Mobile | [ThreeGPP-IDS] | 124 | | Subscriber Identity | | 125 | GUTI | Globally Unique Temporary ID | [ThreeGPP-IDS] | 126 | EUI-48 | 48-bit Extended Unique Identifier | [IEEE802] | 127 | address | | | 128 | EUI-64 | 64-bit Extended Unique | [IEEE802] | 129 | address | Identifier-64 bit | | 130 | DUID | DHCPv6 Unique Identifier | [RFC3315] | 131 +--------------+-----------------------------------+----------------+ 133 Table 1 135 4. Descriptions of MNID types 137 In this section descriptions for the various MNID types are provided. 139 4.1. Description of the IPv6 address type 141 The IPv6 address [RFC4291] is encoded as a 16 octet string containing 142 a full IPv6 address which has been assigned to the mobile node. The 143 IPv6 address MUST be a unicast routable IPv6 address. Multicast 144 addresses, link-local addresses, and the unspecified IPv6 address 145 MUST NOT be used. IPv6 Unique Local Addresses (ULAs) MAY be used, as 146 long as any security operations making use of the ULA also take into 147 account the domain in which the ULA is guaranteed to be unique. 149 4.2. Description of the IMSI MNID type 151 The International Mobile Subscriber Identity (IMSI) [ThreeGPP-IDS] is 152 at most 15 decimal digits (i.e., digits from 0 through 9). The IMSI 153 MUST be encoded as a string of octets in network order (i.e., high- 154 to-low for all digits), where each digit occupies 4 bits. If needed 155 for full octet size, the last digit MUST be padded with 0xf. For 156 example an example IMSI 123456123456789 would be encoded as follows: 158 0x12, 0x34, 0x56, 0x12, 0x34, 0x56, 0x78, 0x9f 160 4.3. Description of the EUI-48 address type 162 The IEEE EUI-48 address [IEEE802-eui48] is encoded as 6 octets 163 containing the IEEE EUI-48 address. 165 4.4. Description of the EUI-64 address type 167 The IEEE EUI-64 address [IEEE802-eui64] is encoded as 8 octets 168 containing the full IEEE EUI-64 address. 170 4.5. Description of the DUID type 172 The DUID is the DHCPv6 Unique Identifier (DUID) [RFC3315]. There are 173 various types of DUID, which are distinguished by an initial two- 174 octet type field. Clients and servers MUST treat DUIDs as opaque 175 values and MUST only compare DUIDs for equality. 177 5. Security Considerations 179 This document does not introduce any security mechanisms, and does 180 not have any impact on existing security mechanisms. 182 Mobile Node Identifiers such as those described in this document are 183 considered to be private information. If used in the MNID extension 184 as defined in [RFC4283], the packet including the MNID extension MUST 185 be encrypted so that no personal information or trackable identifiers 186 is inadvertently disclosed to passive observers. Operators can 187 potentially apply IPsec Encapsulating Security Payload (ESP) 188 [RFC4303], in transport mode, with confidentiality and integrity 189 protection for protecting the identity and location information in 190 Mobile IPv6 signaling messages. 192 Some MNIDs contain sensitive identifiers which, as used in protocols 193 specified by other SDOs, are only used for signaling during initial 194 network entry. In such protocols, subsequent exchanges then rely on 195 a temporary identifier allocated during the initial network entry. 196 Managing the association between long-lived and temporary identifiers 197 is outside the scope of this document. 199 6. IANA Considerations 201 The new mobile node identifier types defined in the document should 202 be assigned values from the "Mobile Node Identifier Option Subtypes" 203 registry. The following values should be assigned. 205 New Mobile Node Identifier Types 207 +-----------------+------------------------+ 208 | Identifier Type | Identifier Type Number | 209 +-----------------+------------------------+ 210 | IPv6 Address | 2 | 211 | IMSI | 3 | 212 | P-TMSI | 4 | 213 | EUI-48 address | 5 | 214 | EUI-64 address | 6 | 215 | GUTI | 7 | 216 | DUID-LLT | 8 | 217 | DUID-EN | 9 | 218 | DUID-LL | 10 | 219 | DUID-UUID | 11 | 220 | | 12-15 reserved | 221 | | 16-255 unassigned | 222 +-----------------+------------------------+ 224 Table 2 226 See Section 4 for additional information about the identifier types. 227 Future new assignments are to be made only after Expert Review 228 [RFC8126]. The expert must ascertain that the identifier type allows 229 unique identification of the mobile device; since all MNIDs require 230 encryption there is no additional privacy exposure attendent to the 231 use of new types. 233 7. Acknowledgements 235 The authors wish to acknowledge Hakima Chaouchi, Tatuya Jinmei, Jouni 236 Korhonen, Sri Gundavelli, Suresh Krishnan, Dapeng Liu, Dale Worley, 237 Joseph Salowey, Linda Dunbar, and Mirja Kuehlewind for their helpful 238 comments. 240 8. References 242 8.1. Normative References 244 [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate 245 Requirement Levels", BCP 14, RFC 2119, 246 DOI 10.17487/RFC2119, March 1997, 247 . 249 [RFC3315] Droms, R., Ed., Bound, J., Volz, B., Lemon, T., Perkins, 250 C., and M. Carney, "Dynamic Host Configuration Protocol 251 for IPv6 (DHCPv6)", RFC 3315, DOI 10.17487/RFC3315, July 252 2003, . 254 [RFC4283] Patel, A., Leung, K., Khalil, M., Akhtar, H., and K. 255 Chowdhury, "Mobile Node Identifier Option for Mobile IPv6 256 (MIPv6)", RFC 4283, DOI 10.17487/RFC4283, November 2005, 257 . 259 [RFC4291] Hinden, R. and S. Deering, "IP Version 6 Addressing 260 Architecture", RFC 4291, DOI 10.17487/RFC4291, February 261 2006, . 263 [RFC4303] Kent, S., "IP Encapsulating Security Payload (ESP)", 264 RFC 4303, DOI 10.17487/RFC4303, December 2005, 265 . 267 [RFC8126] Cotton, M., Leiba, B., and T. Narten, "Guidelines for 268 Writing an IANA Considerations Section in RFCs", BCP 26, 269 RFC 8126, DOI 10.17487/RFC8126, June 2017, 270 . 272 8.2. Informative References 274 [EANUCCGS] 275 EAN International and the Uniform Code Council, "General 276 EAN.UCC Specifications Version 5.0", Jan 2004. 278 [EPC-Tag-Data] 279 EPCglobal Inc., "EPC(TM) Generation 1 Tag Data Standards 280 Version 1.1 Rev.1.27 281 http://www.gs1.org/gsmp/kc/epcglobal/tds/ 282 tds_1_1_rev_1_27-standard-20050510.pdf", January 2005. 284 [IEEE802] IEEE, "IEEE Std 802: IEEE Standards for Local and 285 Metropolitan Networks: Overview and Architecture", 2001. 287 [IEEE802-eui48] 288 IEEE, "Guidelines for 48-Bit Global Identifier (EUI-48) 289 https://standards.ieee.org/develop/regauth/tut/eui48.pdf", 290 2001. 292 [IEEE802-eui64] 293 IEEE, "Guidelines for 64-Bit Global Identifier (EUI-64) 294 https://standards.ieee.org/develop/regauth/tut/eui.pdf64", 295 2001. 297 [RFC3588] Calhoun, P., Loughney, J., Guttman, E., Zorn, G., and J. 298 Arkko, "Diameter Base Protocol", RFC 3588, 299 DOI 10.17487/RFC3588, September 2003, 300 . 302 [RFID-DoD-spec] 303 Department of Defense, "United States Department of 304 Defense Suppliers Passive RFID Information Guide (Version 305 15.0)", January 2010. 307 [ThreeGPP-IDS] 308 3rd Generation Partnership Project, "3GPP Technical 309 Specification 23.003 V8.4.0: Technical Specification Group 310 Core Network and Terminals; Numbering, addressing and 311 identification (Release 8)", March 2009. 313 Appendix A. RFID types 315 The Tag Data standard promoted by Electronic Product Code(TM) 316 (abbreviated EPC) [EPC-Tag-Data] supports several encoding systems or 317 schemes, which are commonly used in RFID (radio-frequency 318 identification) applications, including 320 o RFID-GID (Global Identifier), 321 o RFID-SGTIN (Serialized Global Trade Item Number), 322 o RFID-SSCC (Serial Shipping Container), 323 o RFID-SGLN (Global Location Number), 324 o RFID-GRAI (Global Returnable Asset Identifier), 325 o RFID-DOD (Department of Defense ID), and 326 o RFID-GIAI (Global Individual Asset Identifier). 328 For each RFID scheme except GID, there are three representations: 330 o a 64-bit binary representation (for example, SGLN-64) (except for 331 GID) 332 o a 96-bit binary representation (SGLN-96) 333 o a representation as a URI 334 The URI representation for the RFID is actually a URN. The EPC 335 document has the following language: 337 All categories of URIs are represented as Uniform Reference Names 338 (URNs) as defined by [RFC2141], where the URN Namespace is epc. 340 The following list includes the above RFID types. 342 Mobile Node RFID Identifier Description 344 +----------------+--------------------------------+-----------------+ 345 | Identifier | Description | Reference | 346 | Type | | | 347 +----------------+--------------------------------+-----------------+ 348 | RFID-SGTIN-64 | 64-bit Serialized Global Trade | [EPC-Tag-Data] | 349 | | Item Number | | 350 | RFID-SSCC-64 | 64-bit Serial Shipping | [EPC-Tag-Data] | 351 | | Container | | 352 | RFID-SGLN-64 | 64-bit Serialized Global | [EPC-Tag-Data] | 353 | | Location Number | | 354 | RFID-GRAI-64 | 64-bit Global Returnable Asset | [EPC-Tag-Data] | 355 | | Identifier | | 356 | RFID-DOD-64 | 64-bit Department of Defense | [RFID-DoD-spec] | 357 | | ID | | 358 | RFID-GIAI-64 | 64-bit Global Individual Asset | [EPC-Tag-Data] | 359 | | Identifier | | 360 | RFID-GID-96 | 96-bit Global Identifier | [EPC-Tag-Data] | 361 | RFID-SGTIN-96 | 96-bit Serialized Global Trade | [EPC-Tag-Data] | 362 | | Item Number | | 363 | RFID-SSCC-96 | 96-bit Serial Shipping | [EPC-Tag-Data] | 364 | | Container | | 365 | RFID-SGLN-96 | 96-bit Serialized Global | [EPC-Tag-Data] | 366 | | Location Number | | 367 | RFID-GRAI-96 | 96-bit Global Returnable Asset | [EPC-Tag-Data] | 368 | | Identifier | | 369 | RFID-DOD-96 | 96-bit Department of Defense | [RFID-DoD-spec] | 370 | | ID | | 371 | RFID-GIAI-96 | 96-bit Global Individual Asset | [EPC-Tag-Data] | 372 | | Identifier | | 373 | RFID-GID-URI | Global Identifier represented | [EPC-Tag-Data] | 374 | | as URI | | 375 | RFID-SGTIN-URI | Serialized Global Trade Item | [EPC-Tag-Data] | 376 | | Number represented as URI | | 377 | RFID-SSCC-URI | Serial Shipping Container | [EPC-Tag-Data] | 378 | | represented as URI | | 379 | RFID-SGLN-URI | Global Location Number | [EPC-Tag-Data] | 380 | | represented as URI | | 381 | RFID-GRAI-URI | Global Returnable Asset | [EPC-Tag-Data] | 382 | | Identifier represented as URI | | 383 | RFID-DOD-URI | Department of Defense ID | [RFID-DoD-spec] | 384 | | represented as URI | | 385 | RFID-GIAI-URI | Global Individual Asset | [EPC-Tag-Data] | 386 | | Identifier represented as URI | | 387 +----------------+--------------------------------+-----------------+ 389 Table 3 391 A.1. Description of the RFID types 393 The General Identifier (GID) that is used with RFID is composed of 394 three fields - the General Manager Number, Object Class and Serial 395 Number. The General Manager Number identifies an organizational 396 entity that is responsible for maintaining the numbers in subsequent 397 fields. GID encodings include a fourth field, the header, to 398 guarantee uniqueness in the namespace defined by EPC. 400 Some of the RFID types depend on the Global Trade Item Number (GTIN) 401 code defined in the General EAN.UCC Specifications [EANUCCGS]. A 402 GTIN identifies a particular class of object, such as a particular 403 kind of product or SKU. 405 The EPC encoding scheme for SGTIN permits the direct embedding of 406 EAN.UCC System standard GTIN and Serial Number codes on EPC tags. In 407 all cases, the check digit is not encoded. Two encoding schemes are 408 specified, SGTIN-64 (64 bits) and SGTIN-96 (96 bits). 410 The Serial Shipping Container Code (SSCC) is defined by the EAN.UCC 411 Specifications. Unlike the GTIN, the SSCC is already intended for 412 assignment to individual objects and therefore does not require 413 additional fields to serve as an EPC pure identity. Two encoding 414 schemes are specified, SSCC-64 (64 bits) and SSCC-96 (96 bits). 416 The Global Location Number (GLN) is defined by the EAN.UCC 417 Specifications. A GLN can represent either a discrete, unique 418 physical location such as a warehouse slot, or an aggregate physical 419 location such as an entire warehouse. In addition, a GLN can 420 represent a logical entity that performs a business function such as 421 placing an order. The Serialized Global Location Number (SGLN) 422 includes the Company Prefix, Location Reference, and Serial Number. 424 The Global Returnable Asset Identifier (GRAI) is defined by the 425 General EAN.UCC Specifications. Unlike the GTIN, the GRAI is already 426 intended for assignment to individual objects and therefore does not 427 require any additional fields to serve as an EPC pure identity. The 428 GRAI includes the Company Prefix, Asset Type, and Serial Number. 430 The Global Individual Asset Identifier (GIAI) is defined by the 431 General EAN.UCC Specifications. Unlike the GTIN, the GIAI is already 432 intended for assignment to individual objects and therefore does not 433 require any additional fields to serve as an EPC pure identity. The 434 GRAI includes the Company Prefix, and Individual Asset Reference. 436 The DoD Construct identifier is defined by the United States 437 Department of Defense (DoD). This tag data construct may be used to 438 encode tags for shipping goods to the DoD by a supplier who has 439 already been assigned a CAGE (Commercial and Government Entity) code. 441 A.1.1. Description of the RFID-SGTIN-64 type 443 The RFID-SGTIN-64 is encoded as specified in [EPC-Tag-Data]. The 444 SGTIN-64 includes five fields: Header, Filter Value (additional data 445 that is used for fast filtering and pre-selection), Company Prefix 446 Index, Item Reference, and Serial Number. Only a limited number of 447 Company Prefixes can be represented in the 64-bit tag. 449 A.1.2. Description of the RFID-SGTIN-96 type 451 The RFID-SGTIN-96 is encoded as specified in [EPC-Tag-Data]. The 452 SGTIN-96 includes six fields: Header, Filter Value, Partition (an 453 indication of where the subsequent Company Prefix and Item Reference 454 numbers are divided), Company Prefix Index, Item Reference, and 455 Serial Number. 457 A.1.3. Description of the RFID-SSCC-64 type 459 The RFID-SSCC-64 is encoded as specified in [EPC-Tag-Data]. The 460 SSCC-64 includes four fields: Header, Filter Value, Company Prefix 461 Index, and Serial Reference. Only a limited number of Company 462 Prefixes can be represented in the 64-bit tag. 464 A.1.4. Description of the RFID-SSCC-96 type 466 The RFID-SSCC-96 is encoded as specified in [EPC-Tag-Data]. The 467 SSCC-96 includes six fields: Header, Filter Value, Partition, Company 468 Prefix, and Serial Reference, as well as 24 bits that remain 469 Unallocated and must be zero. 471 A.1.5. Description of the RFID-SGLN-64 type 473 The RFID-SGLN-64 type is encoded as specified in [EPC-Tag-Data]. The 474 SGLN-64 includes five fields: Header, Filter Value, Company Prefix 475 Index, Location Reference, and Serial Number. 477 A.1.6. Description of the RFID-SGLN-96 type 479 The RFID-SGLN-96 type is encoded as specified in [EPC-Tag-Data]. The 480 SGLN-96 includes six fields: Header, Filter Value, Partition, Company 481 Prefix, Location Reference, and Serial Number. 483 A.1.7. Description of the RFID-GRAI-64 type 485 The RFID-GRAI-64 type is encoded as specified in [EPC-Tag-Data]. The 486 GRAI-64 includes five fields: Header, Filter Value, Company Prefix 487 Index, Asset Type, and Serial Number. 489 A.1.8. Description of the RFID-GRAI-96 type 491 The RFID-GRAI-96 type is encoded as specified in [EPC-Tag-Data]. The 492 GRAI-96 includes six fields: Header, Filter Value, Partition, Company 493 Prefix, Asset Type, and Serial Number. 495 A.1.9. Description of the RFID-GIAI-64 type 497 The RFID-GIAI-64 type is encoded as specified in [EPC-Tag-Data]. The 498 GIAI-64 includes four fields: Header, Filter Value, Company Prefix 499 Index, and Individual Asset Reference. 501 A.1.10. Description of the RFID-GIAI-96 type 503 The RFID-GIAI-96 type is encoded as specified in [EPC-Tag-Data]. The 504 GIAI-96 includes five fields: Header, Filter Value, Partition, 505 Company Prefix, and Individual Asset Reference. 507 A.1.11. Description of the RFID-DoD-64 type 509 The RFID-DoD-64 type is encoded as specified in [RFID-DoD-spec]. The 510 DoD-64 type includes four fields: Header, Filter Value, Government 511 Managed Identifier, and Serial Number. 513 A.1.12. Description of the RFID-DoD-96 type 515 The RFID-DoD-96 type is encoded as specified in [RFID-DoD-spec]. The 516 DoD-96 type includes four fields: Header, Filter Value, Government 517 Managed Identifier, and Serial Number. 519 A.1.13. Description of the RFID URI types 521 In some cases, it is desirable to encode in URI form a specific 522 encoding of an RFID tag. For example, an application may prefer a 523 URI representation for report preparation. Applications that wish to 524 manipulate any additional data fields on tags may need some 525 representation other than the pure identity forms. 527 For this purpose, the fields as represented the previous sections are 528 associated with specified fields in the various URI types. For 529 instance, the URI may have fields such as CompanyPrefix, 530 ItemReference, or SerialNumber. For details and encoding specifics, 531 consult [EPC-Tag-Data]. 533 Authors' Addresses 535 Charles E. Perkins 536 Futurewei Inc. 537 2330 Central Expressway 538 Santa Clara, CA 95050 539 USA 541 Phone: +1-408-330-4586 542 Email: charliep@computer.org 544 Vijay Devarapalli 545 Vasona Networks 546 2900 Lakeside Drive, Suite 180 547 Santa Clara, CA 95054 548 USA 550 Email: dvijay@gmail.com