RFC 8371
Mobile Node Identifier Types for MIPv6
Mobile Node Identifier Types for MIPv6 🦋
okay bestie, RFC 8371 is literally an identifier buffet 💖 here's the title block tea first:
- Number and title: RFC 8371, "Mobile Node Identifier Types for MIPv6"
- Stream: Internet Engineering Task Force (IETF)
- Authors: C. Perkins (Futurewei) and V. Devarapalli (Vasona Networks)
- Category: Standards Track
- Date: July 2018
- ISSN: 2070-1721
- Obsoletes and updates: the title block doesn't list anything this document obsoletes or updates
Abstract ✨
This doc defines extra identifier type numbers for the mobile node identifier option for Mobile IPv6 (MIPv6), which is defined in RFC 4283. It's giving "new options unlocked" 🔓
Status of This Memo 📋
This is an Internet Standards Track document.
This document is a product of the Internet Engineering Task Force (IETF). It represents the consensus of the IETF community. It has received public review and has been approved for publication by the Internet Engineering Steering Group (IESG). More info on Internet Standards is in Section 2 of RFC 7841.
Info about the current status of this document, any errata, and how to send feedback is at https://www.rfc-editor.org/info/rfc8371.
Copyright Notice ⚖️
Copyright (c) 2018 IETF Trust and the persons identified as the document authors. All rights reserved.
This document is subject to BCP 78 and the IETF Trust's Legal Provisions Relating to IETF Documents (https://trustee.ietf.org/license-info) in effect on the date of publication of this document. Please review these documents carefully, since they describe your rights and restrictions with respect to this document. Code Components extracted from this document must include Simplified BSD License text as described in Section 4.e of the Trust Legal Provisions, and they're provided without warranty as described in the Simplified BSD License.
Table of Contents 🗺️
1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 3
2. Terminology . . . . . . . . . . . . . . . . . . . . . . . . . 3
3. New Mobile Node Identifier Types . . . . . . . . . . . . . . 4
4. Descriptions of MN Identifier Types . . . . . . . . . . . . . 4
4.1. Description of the IPv6 Address Type . . . . . . . . . . 4
4.2. Description of the IMSI MN Identifier Type . . . . . . . 5
4.3. Description of the EUI-48 Address Type . . . . . . . . . 5
4.4. Description of the EUI-64 Address Type . . . . . . . . . 5
4.5. Description of the DUID Type . . . . . . . . . . . . . . 5
5. Security Considerations . . . . . . . . . . . . . . . . . . . 5
6. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 6
7. References . . . . . . . . . . . . . . . . . . . . . . . . . 6
7.1. Normative References . . . . . . . . . . . . . . . . . . 6
7.2. Informative References . . . . . . . . . . . . . . . . . 7
Appendix A. RFID Types . . . . . . . . . . . . . . . . . . . . . 9
A.1. Description of the RFID Types . . . . . . . . . . . . . . 13
A.1.1. Description of the RFID-SGTIN-64 Type . . . . . . . . 14
A.1.2. Description of the RFID-SGTIN-96 Type . . . . . . . . 14
A.1.3. Description of the RFID-SSCC-64 Type . . . . . . . . 14
A.1.4. Description of the RFID-SSCC-96 Type . . . . . . . . 14
A.1.5. Description of the RFID-SGLN-64 Type . . . . . . . . 14
A.1.6. Description of the RFID-SGLN-96 Type . . . . . . . . 14
A.1.7. Description of the RFID-GRAI-64 Type . . . . . . . . 15
A.1.8. Description of the RFID-GRAI-96 Type . . . . . . . . 15
A.1.9. Description of the RFID-GIAI-64 Type . . . . . . . . 15
A.1.10. Description of the RFID-GIAI-96 Type . . . . . . . . 15
A.1.11. Description of the RFID-DoD-64 Type . . . . . . . . . 15
A.1.12. Description of the RFID-DoD-96 Type . . . . . . . . . 15
A.1.13. Description of the RFID URI Types . . . . . . . . . . 15
Acknowledgements . . . . . . . . . . . . . . . . . . . . . . . . 16
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 161. Introduction 🌸
The "Mobile Node Identifier Option for Mobile IPv6 (MIPv6)" [RFC4283] has proved to be a super popular design tool for giving mobile nodes identifiers during authentication with Authentication, Authorization, and Accounting (AAA) protocols like Diameter [RFC6733]. So far only one identifier type has been specified, the Mobile Node (MN) NAI. Other identifier types are in common use and RFC 4283 even references them 👀
This doc proposes adding some basic identifier types from various telecom standards, including types for International Mobile Subscriber Identity (IMSI) [ThreeGPP-IDS], Packet - Temporary Mobile Subscriber Identity (P-TMSI) [ThreeGPP-IDS], International Mobile station Equipment Identities (IMEI) [ThreeGPP-IDS], and Globally Unique Temporary UE Identity (GUTI) [ThreeGPP-IDS]. It also specifies the IPv6 address itself and IEEE MAC-layer addresses as Mobile Node identifiers.
Identifiers tied to the physical parts of the device (like the MAC address) are a huge help for deploying Mobile IP 🧚 In lots of cases they're the most natural way to uniquely identify a device, and they skip the extra lookup steps you'd need with other identifiers.
2. Terminology 📖
Quick glossary moment! The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", "SHOULD", "SHOULD NOT", "RECOMMENDED", "NOT RECOMMENDED", "MAY", and "OPTIONAL" in this document are to be read as BCP 14 [RFC2119] [RFC8174] describes, but only when they show up in all capitals, just like here.
3. New Mobile Node Identifier Types 🎀
These are the identifier types that get used a lot to identify mobile nodes. For each type, the references have all the full format details.
+--------------+-----------------------------------+----------------+
| Identifier | Description | Reference |
| Type | | |
+--------------+-----------------------------------+----------------+
| IPv6 Address | | [RFC4291] |
| | | |
| IMSI | International Mobile Subscriber | [ThreeGPP-IDS] |
| | Identity | |
| | | |
| P-TMSI | Packet - Temporary Mobile | [ThreeGPP-IDS] |
| | Subscriber Identity | |
| | | |
| GUTI | Globally Unique Temporary UE | [ThreeGPP-IDS] |
| | Identity | |
| | | |
| EUI-48 | 48-Bit Extended Unique Identifier | [IEEE802] |
| Address | | |
| | | |
| EUI-64 | 64-Bit Extended Unique Identifier | [IEEE802] |
| Address | | |
| | | |
| DUID | DHCPv6 Unique Identifier | [RFC3315] |
+--------------+-----------------------------------+----------------+
Table 1: Mobile Node Identifier Description4. Descriptions of MN Identifier Types 💜
This section breaks down each of the MN identifier types, one by one. Let's go!
4.1. Description of the IPv6 Address Type 🌐
The IPv6 address [RFC4291] is encoded as a 16-octet string containing a full IPv6 address that's been assigned to the mobile node. The IPv6 address MUST be a unicast routable IPv6 address. Multicast addresses, link-local addresses, and the unspecified IPv6 address MUST NOT be used. IPv6 Unique Local Addresses (ULAs) MAY be used, as long as any security operations that use the ULA also take into account the domain in which the ULA is guaranteed to be unique. bestie, that last bit is a whole vibe 🙈
4.2. Description of the IMSI MN Identifier Type 📱
The International Mobile Subscriber Identity (IMSI) [ThreeGPP-IDS] is at most 15 decimal digits (i.e., digits from 0 through 9). The IMSI MUST be encoded as a string of octets in network order (i.e., high to low for all digits), where each digit takes up 4 bits. If it's needed to fill a full octet, the last digit MUST be padded with 0xf. For instance, the example IMSI 123456123456789 would be encoded as follows:
0x12, 0x34, 0x56, 0x12, 0x34, 0x56, 0x78, 0x9f4.3. Description of the EUI-48 Address Type 🔢
The IEEE EUI-48 address [IEEE802-GUIDELINES] is encoded as 6 octets containing the IEEE EUI-48 address.
4.4. Description of the EUI-64 Address Type 🔢
The IEEE EUI-64 address [IEEE802-GUIDELINES] is encoded as 8 octets containing the full IEEE EUI-64 address.
4.5. Description of the DUID Type 🧩
The DUID is the DHCPv6 Unique Identifier [RFC3315]. There are various types of DUIDs, and they're told apart by an initial two-octet type field. Clients and servers MUST treat DUIDs as opaque values, and they MUST only compare DUIDs for equality. no peeking inside, periodt 💅
6. IANA Considerations 🎀
Okay so the new mobile node identifier types in this doc got their values from the "Mobile Node Identifier Option Subtypes" registry, and IANA has officially registered these numbers 💅
Table 2 is the cute little lineup:
+-----------------+------------------------+
| Identifier Type | Identifier Type Number |
+-----------------+------------------------+
| IPv6 Address | 2 |
| IMSI | 3 |
| P-TMSI | 4 |
| EUI-48 address | 5 |
| EUI-64 address | 6 |
| GUTI | 7 |
| DUID | 8 |
| Reserved | 9-15 |
| Unassigned | 16-255 |
+-----------------+------------------------+
Table 2: New Mobile Node Identifier TypesCheck Section 4 for more deets on each identifier type 🦋 The registration procedure is Standards Action [RFC8126]. The expert has to make sure the identifier type can uniquely identify the mobile device. Since all MN identifiers need encryption, the new types don't add any extra privacy exposure. Iconic, right? 🫶
7. References 📚
7.1. Normative References
Here's the normative crew, the must-read docs 🤓
[RFC2119] Bradner, S., "Key words for use in RFCs to Indicate
Requirement Levels", BCP 14, RFC 2119,
DOI 10.17487/RFC2119, March 1997,
<https://www.rfc-editor.org/info/rfc2119>.
[RFC3315] Droms, R., Ed., Bound, J., Volz, B., Lemon, T., Perkins,
C., and M. Carney, "Dynamic Host Configuration Protocol
for IPv6 (DHCPv6)", RFC 3315, DOI 10.17487/RFC3315, July
2003, <https://www.rfc-editor.org/info/rfc3315>.
[RFC4283] Patel, A., Leung, K., Khalil, M., Akhtar, H., and K.
Chowdhury, "Mobile Node Identifier Option for Mobile IPv6
(MIPv6)", RFC 4283, DOI 10.17487/RFC4283, November 2005,
<https://www.rfc-editor.org/info/rfc4283>.
[RFC4291] Hinden, R. and S. Deering, "IP Version 6 Addressing
Architecture", RFC 4291, DOI 10.17487/RFC4291, February
2006, <https://www.rfc-editor.org/info/rfc4291>.
[RFC4303] Kent, S., "IP Encapsulating Security Payload (ESP)",
RFC 4303, DOI 10.17487/RFC4303, December 2005,
<https://www.rfc-editor.org/info/rfc4303>.
[RFC8126] Cotton, M., Leiba, B., and T. Narten, "Guidelines for
Writing an IANA Considerations Section in RFCs", BCP 26,
RFC 8126, DOI 10.17487/RFC8126, June 2017,
<https://www.rfc-editor.org/info/rfc8126>.
[RFC8174] Leiba, B., "Ambiguity of Uppercase vs Lowercase in RFC
2119 Key Words", BCP 14, RFC 8174, DOI 10.17487/RFC8174,
May 2017, <https://www.rfc-editor.org/info/rfc8174>.7.2. Informative References
And now the informative ones, the bonus reading for the curious 🌈
[EANUCCGS]
EAN International and the Uniform Code Council, "General
EAN.UCC Specifications", Version 5.0, January 2004.
[EPC-Tag-Data]
EPCglobal, Inc., "EPC Generation 1 Tag Data Standards
Version 1.1 Rev.1.27", May 2005,
<https://www.gs1.org/sites/default/files/docs/epc/
tds_1_1_rev_1_27-standard-20050510.pdf>.
[IEEE802] IEEE, "IEEE Standard for Local and Metropolitan Area
Networks: Overview and Architecture", IEEE 802.
[IEEE802-GUIDELINES]
IEEE, "Guidelines for Use of Extended Unique Identifier
(EUI), Organizationally Unique Identifier (OUI), and
Company ID (CID)", August 2018,
<http://standards.ieee.org/develop/regauth/tut/eui.pdf>.
[RFC6733] Fajardo, V., Ed., Arkko, J., Loughney, J., and G. Zorn,
Ed., "Diameter Base Protocol", RFC 6733,
DOI 10.17487/RFC6733, October 2012,
<https://www.rfc-editor.org/info/rfc6733>.
[RFID-DoD-spec]
Department of Defense, "United States Department of
Defense Suppliers' Passive RFID Information Guide",
Version 15.0, January 2010.
[RFID-framework]
Botero, O., "Heterogeneous RFID framework design, analysis
and evaluation", Institut National des Telecommunications,
July 2012.
[ThreeGPP-IDS]
3GPP, "3rd Generation Partnership Project; Technical
Specification Group Core Network and Terminals; Numbering,
addressing and identification (Release 15)", 3GPP
TS 23.003, V15.3.0, March 2018.
[TRACK-IoT]
Chaouchi, H., "Heterogeneous IoT Network: TRACK-IoT
Plateform", Telecom SudParis, Internal Report, March 2012.
[Using-RFID-IPv6]
IPv6.com, "Using RFID & IPv6", September 2006.Appendix A. RFID Types 🎀
Okay bestie, this appendix is non-normative 💅, so it's background vibes and not rules. It was originally written for the main body of the spec, but there wasn't enough support for allocating RFID types at the time, so it got moved here. The big concern was that RFID-based mobile devices can create privacy exposures unless confidentiality is assured for signaling 🙈. The doc also says a spec for eliminating unauthorized RFID tracking based on Layer 2 addresses would be super helpful.
Much of this text came from Hakima Chaouchi 🫶. For an overview and some starter ideas about using RFID with IPv6 on mobile devices, check out [Using-RFID-IPv6].
In the Internet of Things (IoT) and Industry 4.0, vertical domains, efficient inventory, and tracking items are a huge deal, and RFID is the identification tech built into the hardware of a lot of these items 📦✨
The "TRACK-IoT" project [TRACK-IoT] [RFID-framework] explored Mobile IPv6 as a mobility management protocol for RFID-based mobile devices 🦋
- Passive RFID tags (which have no processing resources) need to be handled by the gateway (probably the RFID reader too). That gateway is the endpoint of the mobility protocol, and it's also where the Change of Address (CoA) gets created, based on some combination like the RFID tag and the gateway's prefix. The point is to give passive RFID items a shot at an IPv6 address so they can use the mobility framework to follow the mobile device (the passive tag on the item) 🌸. One example is art pieces tagged with passive tags that need to be monitored while they're transported.
- Active RFID tags (where the processing resource is available on the tag) can host the endpoint of the mobility protocol directly on the tag, which is also called an identification sensor 🔥. A use case here is traceability of cold food during transport. Cars equipped with active RFID tags that are already used for toll payment could also get mobility management added.
One major effort to connect IETF work to EPCglobal (the RFID standardization group) led to the Object Name Service (ONS), which is the DNS version used for RFID logical names and page information retrieval 💜. People have also tried to connect the IPv6 address space to the RFID identifier format. Other initiatives started working on gateways that map tag identifiers to IPv6 addresses and build application-level signaling protocols 🧚.
Tracking a mobile item with a tag can be triggered remotely by a remote correspondent node, all the way until the item reaches the visiting area where it's located. An RFID reader gets IPv6-to-RFID tag translation added to it. One option is to build a home IPv6 address for the tagged item by combining the prefix of the home agent with the tag's RFID identifier. Since the tag ID is unique, the home IPv6 address of that item will also be unique 👑. Then the visiting RFID reader composes the IPv6 care-of address of the tagged mobile item by combining the prefix of the RFID reader with the item's tag ID. MIPv6 can then normally provide the mobility management for that RFID-tagged item.
A different example involves items in a factory that can be tracked while they're transported, especially for real-time localization and tracking of precious items moved without GPS 🌈. An automotive manufacturer can assign IPv6 addresses to RFID-tagged cars or mechanical car parts and build a tracking dataset of the mobility not only of the cars, but also of the mechanical pieces 🚗.
The Tag Data Standard promoted by Electronic Product Code (EPC) [EPC-Tag-Data] supports several encoding systems or schemes that are commonly used in RFID applications, including:
- RFID-GID (Global Identifier),
- RFID-SGTIN (Serialized Global Trade Item Number),
- RFID-SSCC (Serial Shipping Container Code),
- RFID-SGLN (Serialized Global Location Number),
- RFID-GRAI (Global Returnable Asset Identifier),
- RFID-DOD (Department of Defense ID), and
- RFID-GIAI (Global Individual Asset Identifier).
For each RFID scheme except GID, there are three representations:
- a 64-bit binary representation (for example, SGLN-64), excluding GID,
- a 96-bit binary representation (SGLN-96), and
- a representation as a URI.
The URI representation for RFID is actually a URN. The EPC document says:
All categories of URIs are represented as Uniform Reference Names (URNs) as defined by [RFC2141], where the URN Namespace is epc.
Here's the list of the RFID types above, in one big table 🍓:
+----------------+--------------------------------+-----------------+
| Identifier | Description | Reference |
| Type | | |
+----------------+--------------------------------+-----------------+
| RFID-SGTIN-64 | 64-bit Serialized Global Trade | [EPC-Tag-Data] |
| | Item Number | |
| RFID-SSCC-64 | 64-bit Serial Shipping | [EPC-Tag-Data] |
| | Container Code | |
| RFID-SGLN-64 | 64-bit Serialized Global | [EPC-Tag-Data] |
| | Location Number | |
| RFID-GRAI-64 | 64-bit Global Returnable Asset | [EPC-Tag-Data] |
| | Identifier | |
| RFID-DOD-64 | 64-bit Department of Defense | [RFID-DoD-spec] |
| | ID | |
| RFID-GIAI-64 | 64-bit Global Individual Asset | [EPC-Tag-Data] |
| | Identifier | |
| RFID-GID-96 | 96-bit Global Identifier | [EPC-Tag-Data] |
| RFID-SGTIN-96 | 96-bit Serialized Global Trade | [EPC-Tag-Data] |
| | Item Number | |
| RFID-SSCC-96 | 96-bit Serial Shipping | [EPC-Tag-Data] |
| | Container | |
| RFID-SGLN-96 | 96-bit Serialized Global | [EPC-Tag-Data] |
| | Location Number | |
| RFID-GRAI-96 | 96-bit Global Returnable Asset | [EPC-Tag-Data] |
| | Identifier | |
| RFID-DOD-96 | 96-bit Department of Defense | [RFID-DoD-spec] |
| | ID | |
| RFID-GIAI-96 | 96-bit Global Individual Asset | [EPC-Tag-Data] |
| | Identifier | |
| RFID-GID-URI | Global Identifier represented | [EPC-Tag-Data] |
| | as a URI | |
| RFID-SGTIN-URI | Serialized Global Trade Item | [EPC-Tag-Data] |
| | Number represented as a URI | |
| RFID-SSCC-URI | Serial Shipping Container Code | [EPC-Tag-Data] |
| | represented as a URI | |
| RFID-SGLN-URI | Global Location Number | [EPC-Tag-Data] |
| | represented as a URI | |
| RFID-GRAI-URI | Global Returnable Asset | [EPC-Tag-Data] |
| | Identifier represented as a | |
| | URI | |
| RFID-DOD-URI | Department of Defense ID | [RFID-DoD-spec] |
| | represented as a URI | |
| RFID-GIAI-URI | Global Individual Asset | [EPC-Tag-Data] |
| | Identifier represented as a | |
| | URI | |
+----------------+--------------------------------+-----------------+
Table 3: Mobile Node RFID Identifier DescriptionA.1. Description of the RFID Types
The material in this appendix has been either quoted or loosely adapted from [EPC-Tag-Data] 📖.
The General Identifier (GID) used with RFID is made up of three fields: General Manager Number, Object Class, and Serial Number. The General Manager Number identifies the organizational entity responsible for maintaining the numbers in the subsequent fields. GID encodings also include a fourth field, the header, which guarantees uniqueness in the namespace defined by EPC 💖.
Some RFID types depend on the Global Trade Item Number (GTIN) code defined in the EAN.UCC General Specifications [EANUCCGS]. A GTIN identifies a particular class of object, like a specific kind of product or SKU 🛍️.
The EPC encoding scheme for SGTIN lets you embed EAN.UCC System standard GTIN and Serial Number codes directly on EPC tags. In all cases, the check digit is not encoded. Two encoding schemes are specified: SGTIN-64 (64 bits) and SGTIN-96 (96 bits).
The Serial Shipping Container Code (SSCC) is defined by the EAN.UCC Specifications. Unlike the GTIN, the SSCC is already meant to be assigned to individual objects, so it doesn't need extra fields to serve as an EPC pure identity. Two encoding schemes are specified: SSCC-64 (64 bits) and SSCC-96 (96 bits) 📦.
The Global Location Number (GLN) is defined by the EAN.UCC Specifications. A GLN can represent either a discrete, unique physical location, like a warehouse slot, or an aggregate physical location, like an entire warehouse. A GLN can also represent a logical entity that performs a business function, like placing an order. The Serialized Global Location Number (SGLN) includes the Company Prefix, Location Reference, and Serial Number 📍.
The Global Returnable Asset Identifier (GRAI) is defined by the General EAN.UCC Specifications. Unlike the GTIN, the GRAI is already meant for individual objects, so it doesn't require any additional fields to serve as an EPC pure identity. The GRAI includes the Company Prefix, Asset Type, and Serial Number ♻️.
The Global Individual Asset Identifier (GIAI) is defined by the General EAN.UCC Specifications. Like the GRAI, the GIAI is already meant for individual objects and doesn't require any additional fields to serve as an EPC pure identity. The GRAI includes the Company Prefix and Individual Asset Reference 🧾.
The DoD Construct identifier is defined by the United States Department of Defense (DoD). This tag data construct may be used to encode tags for shipping goods to the DoD by a supplier who has already been assigned a Commercial and Government Entity (CAGE) code 🇺🇸.
A.1.1. Description of the RFID-SGTIN-64 Type
The RFID-SGTIN-64 is encoded as specified in [EPC-Tag-Data]. The SGTIN-64 has five fields: Header, Filter Value (extra data used for fast filtering and preselection), Company Prefix Index, Item Reference, and Serial Number. Only a limited number of Company Prefixes can be represented in the 64-bit tag 💅✨.
A.1.2. Description of the RFID-SGTIN-96 Type
okay so the RFID-SGTIN-96 is encoded as specified in [EPC-Tag-Data] 🏷️✨ and it has six fields: Header, Filter Value, Partition, Company Prefix Index, Item Reference, and Serial Number. The Partition is basically the marker that tells you where the Company Prefix and Item Reference numbers get split up 🔪💅 it's giving main character energy 👑
A.1.3. Description of the RFID-SSCC-64 Type
the RFID-SSCC-64 is encoded as specified in [EPC-Tag-Data] 🎀 it has four fields: Header, Filter Value, Company Prefix Index, and Serial Reference. ngl the catch is that only a limited number of Company Prefixes can be represented in the 64-bit tag 🥺
A.1.4. Description of the RFID-SSCC-96 Type
the RFID-SSCC-96 is encoded as specified in [EPC-Tag-Data] 🦋 it has six fields: Header, Filter Value, Partition, Company Prefix, and Serial Reference. On top of that, there are 24 bits that remain unallocated and must be zero 🙈 no sneaking anything in there, bestie
A.1.5. Description of the RFID-SGLN-64 Type
the RFID-SGLN-64 type is encoded as specified in [EPC-Tag-Data] 🌸 it includes five fields: Header, Filter Value, Company Prefix Index, Location Reference, and Serial Number.
A.1.6. Description of the RFID-SGLN-96 Type
the RFID-SGLN-96 type is encoded as specified in [EPC-Tag-Data] 💜 it includes six fields: Header, Filter Value, Partition, Company Prefix, Location Reference, and Serial Number.
A.1.7. Description of the RFID-GRAI-64 Type
the RFID-GRAI-64 type is encoded as specified in [EPC-Tag-Data] 🍓 it includes five fields: Header, Filter Value, Company Prefix Index, Asset Type, and Serial Number.
A.1.8. Description of the RFID-GRAI-96 Type
the RFID-GRAI-96 type is encoded as specified in [EPC-Tag-Data] 🧚 it includes six fields: Header, Filter Value, Partition, Company Prefix, Asset Type, and Serial Number.
A.1.9. Description of the RFID-GIAI-64 Type
the RFID-GIAI-64 type is encoded as specified in [EPC-Tag-Data] 🌈 it includes four fields: Header, Filter Value, Company Prefix Index, and Individual Asset Reference.
A.1.10. Description of the RFID-GIAI-96 Type
the RFID-GIAI-96 type is encoded as specified in [EPC-Tag-Data] ⭐ it includes five fields: Header, Filter Value, Partition, Company Prefix, and Individual Asset Reference.
A.1.11. Description of the RFID-DoD-64 Type
the RFID-DoD-64 type is encoded as specified in [RFID-DoD-spec] 🫶 it includes four fields: Header, Filter Value, Government Managed Identifier, and Serial Number.
A.1.12. Description of the RFID-DoD-96 Type
the RFID-DoD-96 type is encoded as specified in [RFID-DoD-spec] 💅 it includes four fields: Header, Filter Value, Government Managed Identifier, and Serial Number.
A.1.13. Description of the RFID URI Types
sometimes it's desirable to encode an RFID tag in URI form, so a specific encoding gets its own URI representation 🔥 for example, an application might prefer a URI representation when it's preparing reports. Applications that want to manipulate any additional data fields on tags may need some representation other than the pure identity forms 👑
so for this purpose, the fields from the previous sections get linked up with specified fields in the various URI types. For instance, the URI may have fields like CompanyPrefix, ItemReference, or SerialNumber ✨ for the details and encoding specifics, go check [EPC-Tag-Data] 🧚
Acknowledgements
the authors wanted to thank Hakima Chaouchi, Tatuya Jinmei, Jouni Korhonen, Sri Gundavelli, Suresh Krishnan, Dapeng Liu, Dale Worley, Joseph Salowey, Linda Dunbar, and Mirja Kuehlewind for their helpful comments 🫶💖 they also want to shout out the RFC Editor for a number of valuable suggestions and updates during the final stages of producing this document 🌸
Authors' Addresses
Charles E. Perkins
Futurewei Inc.
2330 Central Expressway
Santa Clara, CA 95050
United States of America
Phone: +1-408-330-4586
Email: charliep@computer.org
Vijay Devarapalli
Vasona Networks
2900 Lakeside Drive, Suite 180
Santa Clara, CA 95054
United States of America
Email: dvijay@gmail.com📦 where this page comes from
- ietf: rfc8371 2018-07
- 💖 girlified by claude-haiku-5-5 on : a language model's rewrite of the original, under its terms