draft-ietf-dmm-4283mnids-02.txt   draft-ietf-dmm-4283mnids-03.txt 
Distributed Mobility Management [dmm] C. Perkins Distributed Mobility Management [dmm] C. Perkins
Internet-Draft Futurewei Internet-Draft Futurewei
Expires: December 11, 2016 V. Devarapalli Intended status: Standards Track V. Devarapalli
Vasona Networks Expires: May 17, 2017 Vasona Networks
June 9, 2016 November 13, 2016
MN Identifier Types for RFC 4283 Mobile Node Identifier Option MN Identifier Types for RFC 4283 Mobile Node Identifier Option
draft-ietf-dmm-4283mnids-02.txt draft-ietf-dmm-4283mnids-03.txt
Abstract Abstract
Additional Identifier Types are proposed for use with the Mobile Node Additional Identifier Types are proposed for use with the Mobile Node
Identifier Option for MIPv6 (RFC 4283). Identifier Option for MIPv6 (RFC 4283).
Status of This Memo Status of This Memo
This Internet-Draft is submitted in full conformance with the This Internet-Draft is submitted in full conformance with the
provisions of BCP 78 and BCP 79. provisions of BCP 78 and BCP 79.
skipping to change at page 1, line 32 skipping to change at page 1, line 32
Internet-Drafts are working documents of the Internet Engineering Internet-Drafts are working documents of the Internet Engineering
Task Force (IETF). Note that other groups may also distribute Task Force (IETF). Note that other groups may also distribute
working documents as Internet-Drafts. The list of current Internet- working documents as Internet-Drafts. The list of current Internet-
Drafts is at http://datatracker.ietf.org/drafts/current/. Drafts is at http://datatracker.ietf.org/drafts/current/.
Internet-Drafts are draft documents valid for a maximum of six months Internet-Drafts are draft documents valid for a maximum of six months
and may be updated, replaced, or obsoleted by other documents at any and may be updated, replaced, or obsoleted by other documents at any
time. It is inappropriate to use Internet-Drafts as reference time. It is inappropriate to use Internet-Drafts as reference
material or to cite them other than as "work in progress." material or to cite them other than as "work in progress."
This Internet-Draft will expire on December 11, 2016. This Internet-Draft will expire on May 17, 2017.
Copyright Notice Copyright Notice
Copyright (c) 2016 IETF Trust and the persons identified as the Copyright (c) 2016 IETF Trust and the persons identified as the
document authors. All rights reserved. document authors. All rights reserved.
This document is subject to BCP 78 and the IETF Trust's Legal This document is subject to BCP 78 and the IETF Trust's Legal
Provisions Relating to IETF Documents Provisions Relating to IETF Documents
(http://trustee.ietf.org/license-info) in effect on the date of (http://trustee.ietf.org/license-info) in effect on the date of
publication of this document. Please review these documents publication of this document. Please review these documents
carefully, as they describe your rights and restrictions with respect carefully, as they describe your rights and restrictions with respect
to this document. Code Components extracted from this document must to this document. Code Components extracted from this document must
include Simplified BSD License text as described in Section 4.e of include Simplified BSD License text as described in Section 4.e of
the Trust Legal Provisions and are provided without warranty as the Trust Legal Provisions and are provided without warranty as
described in the Simplified BSD License. described in the Simplified BSD License.
Table of Contents Table of Contents
1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 2 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 2
2. New Mobile Node Identifier Types . . . . . . . . . . . . . . 3 2. Terminology . . . . . . . . . . . . . . . . . . . . . . . . . 3
3. Descriptions of MNID types . . . . . . . . . . . . . . . . . 5 3. New Mobile Node Identifier Types . . . . . . . . . . . . . . 3
3.1. Description of the IPv6 address type . . . . . . . . . . 5 4. Descriptions of MNID types . . . . . . . . . . . . . . . . . 5
3.2. Description of the IMSI MNID type . . . . . . . . . . . . 5 4.1. Description of the IPv6 address type . . . . . . . . . . 5
3.3. Description of the EUI-48 address type . . . . . . . . . 5 4.2. Description of the IMSI MNID type . . . . . . . . . . . . 5
3.4. Description of the EUI-64 address type . . . . . . . . . 5 4.3. Description of the EUI-48 address type . . . . . . . . . 5
3.5. Description of the DUID-LLT type . . . . . . . . . . . . 5 4.4. Description of the EUI-64 address type . . . . . . . . . 5
3.6. Description of the DUID-EN type . . . . . . . . . . . . . 6 4.5. Description of the DUID-LLT type . . . . . . . . . . . . 5
3.7. Description of the DUID-LL type . . . . . . . . . . . . . 6 4.6. Description of the DUID-EN type . . . . . . . . . . . . . 6
3.8. Description of the DUID-UUID type . . . . . . . . . . . . 6 4.7. Description of the DUID-LL type . . . . . . . . . . . . . 6
3.9. Description of the RFID types . . . . . . . . . . . . . . 6 4.8. Description of the DUID-UUID type . . . . . . . . . . . . 6
3.9.1. Description of the RFID-SGTIN-64 type . . . . . . . . 7 4.9. Description of the RFID types . . . . . . . . . . . . . . 6
3.9.2. Description of the RFID-SGTIN-96 type . . . . . . . . 7 4.9.1. Description of the RFID-SGTIN-64 type . . . . . . . . 7
3.9.3. Description of the RFID-SSCC-64 type . . . . . . . . 8 4.9.2. Description of the RFID-SGTIN-96 type . . . . . . . . 8
3.9.4. Description of the RFID-SSCC-96 type . . . . . . . . 8 4.9.3. Description of the RFID-SSCC-64 type . . . . . . . . 8
3.9.5. Description of the RFID-SGLN-64 type . . . . . . . . 8 4.9.4. Description of the RFID-SSCC-96 type . . . . . . . . 8
3.9.6. Description of the RFID-SGLN-96 type . . . . . . . . 8 4.9.5. Description of the RFID-SGLN-64 type . . . . . . . . 8
3.9.7. Description of the RFID-GRAI-64 type . . . . . . . . 8 4.9.6. Description of the RFID-SGLN-96 type . . . . . . . . 8
3.9.8. Description of the RFID-GRAI-96 type . . . . . . . . 8 4.9.7. Description of the RFID-GRAI-64 type . . . . . . . . 8
3.9.9. Description of the RFID-GIAI-64 type . . . . . . . . 8 4.9.8. Description of the RFID-GRAI-96 type . . . . . . . . 8
3.9.10. Description of the RFID-GIAI-96 type . . . . . . . . 9 4.9.9. Description of the RFID-GIAI-64 type . . . . . . . . 9
3.9.11. Description of the RFID-DoD-64 type . . . . . . . . . 9 4.9.10. Description of the RFID-GIAI-96 type . . . . . . . . 9
3.9.12. Description of the RFID-DoD-96 type . . . . . . . . . 9 4.9.11. Description of the RFID-DoD-64 type . . . . . . . . . 9
3.9.13. Description of the RFID URI types . . . . . . . . . . 9 4.9.12. Description of the RFID-DoD-96 type . . . . . . . . . 9
4. Security Considerations . . . . . . . . . . . . . . . . . . . 9 4.9.13. Description of the RFID URI types . . . . . . . . . . 9
5. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 10 5. Security Considerations . . . . . . . . . . . . . . . . . . . 9
6. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 12 6. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 10
7. References . . . . . . . . . . . . . . . . . . . . . . . . . 12 7. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 12
7.1. Normative References . . . . . . . . . . . . . . . . . . 12 8. References . . . . . . . . . . . . . . . . . . . . . . . . . 12
7.2. Informative References . . . . . . . . . . . . . . . . . 12 8.1. Normative References . . . . . . . . . . . . . . . . . . 12
8.2. Informative References . . . . . . . . . . . . . . . . . 12
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 13 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 13
1. Introduction 1. Introduction
The Mobile Node Identifier Option for MIPv6 [RFC4283] has proved to The Mobile Node Identifier Option for MIPv6 [RFC4283] has proved to
be a popular design tool for providing identifiers for mobile nodes be a popular design tool for providing identifiers for mobile nodes
during authentication procedures with AAA protocols such as Diameter during authentication procedures with AAA protocols such as Diameter
[RFC3588]. To date, only a single type of identifier has been [RFC3588]. To date, only a single type of identifier has been
specified, namely the MN NAI. Other types of identifiers are in specified, namely the MN NAI. Other types of identifiers are in
common use, and even referenced in RFC 4283. In this document, we common use, and even referenced in RFC 4283. In this document, we
skipping to change at page 3, line 10 skipping to change at page 3, line 11
telecommunications standards, including types for IMSI telecommunications standards, including types for IMSI
[ThreeGPP-IDS], P-TMSI [ThreeGPP-IDS], IMEI [ThreeGPP-IDS], and GUTI [ThreeGPP-IDS], P-TMSI [ThreeGPP-IDS], IMEI [ThreeGPP-IDS], and GUTI
[ThreeGPP-IDS]. In addition, we specify the IPv6 address itself and [ThreeGPP-IDS]. In addition, we specify the IPv6 address itself and
IEEE MAC-layer addresses as mobile node identifiers. Defining IEEE MAC-layer addresses as mobile node identifiers. Defining
identifiers that are tied to the physical elements of the device identifiers that are tied to the physical elements of the device
(RFID, MAC address etc.) help in deployment of Mobile IP because in (RFID, MAC address etc.) help in deployment of Mobile IP because in
many cases such identifiers are the most natural means for uniquely many cases such identifiers are the most natural means for uniquely
identifying the device, and will avoid additional look-up steps that identifying the device, and will avoid additional look-up steps that
might be needed if other identifiers were used. might be needed if other identifiers were used.
2. New Mobile Node Identifier Types 2. Terminology
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 interpreted as described in
[RFC2119].
3. New Mobile Node Identifier Types
The following types of identifiers are commonly used to identify The following types of identifiers are commonly used to identify
mobile nodes. For each type, references are provided with full mobile nodes. For each type, references are provided with full
details on the format of the type of identifer. details on the format of the type of identifer.
The Tag Data standard promoted by Electronic Product Code(TM) The Tag Data standard promoted by Electronic Product Code(TM)
(abbreviated EPC) supports several encoding systems or schemes (abbreviated EPC) supports several encoding systems or schemes
including including
o RFID-GID (Global Identifier), o RFID-GID (Global Identifier),
skipping to change at page 5, line 9 skipping to change at page 5, line 17
| RFID-GRAI-URI | Global Returnable Asset | [EPC-Tag-Data] | | RFID-GRAI-URI | Global Returnable Asset | [EPC-Tag-Data] |
| | Identifier represented as URI | | | | Identifier represented as URI | |
| RFID-DOD-URI | Department of Defense ID | [RFID-DoD-spec] | | RFID-DOD-URI | Department of Defense ID | [RFID-DoD-spec] |
| | represented as URI | | | | represented as URI | |
| RFID-GIAI-URI | Global Individual Asset | [EPC-Tag-Data] | | RFID-GIAI-URI | Global Individual Asset | [EPC-Tag-Data] |
| | Identifier represented as URI | | | | Identifier represented as URI | |
+----------------+--------------------------------+-----------------+ +----------------+--------------------------------+-----------------+
Table 1 Table 1
3. Descriptions of MNID types 4. Descriptions of MNID types
In this section descriptions for the various MNID types are provided. In this section descriptions for the various MNID types are provided.
3.1. Description of the IPv6 address type 4.1. Description of the IPv6 address type
The IPv6 address [RFC4291] is encoded as a 16 octet string containing The IPv6 address [RFC4291] is encoded as a 16 octet string containing
the full IPv6 address. the full IPv6 address.
3.2. Description of the IMSI MNID type 4.2. Description of the IMSI MNID type
The International Mobile Subscriber Identity (IMSI) [ThreeGPP-IDS] is The International Mobile Subscriber Identity (IMSI) [ThreeGPP-IDS] is
at most 15 decimal digits (i.e., digits from 0 through 9). The IMSI 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, where each MUST be encoded as a string of octets in network order, where each
digit occupies 4 bits. The last digit MUST be zero padded, if digit occupies 4 bits. The last digit MUST be zero padded, if
needed, for full octet size. For example an example IMSI needed, for full octet size. For example an example IMSI
123456123456789 would be encoded as follows: 123456123456789 would be encoded as follows:
0x12, 0x34, 0x56, 0x12, 0x34, 0x56, 0x78, 0x90 0x12, 0x34, 0x56, 0x12, 0x34, 0x56, 0x78, 0x90
3.3. Description of the EUI-48 address type 4.3. Description of the EUI-48 address type
The IEEE EUI-48 address [IEEE802-eui48] is encoded as a 6 octet The IEEE EUI-48 address [IEEE802-eui48] is encoded as a 6 octet
string containing the IEEE EUI-48 address. string containing the IEEE EUI-48 address.
3.4. Description of the EUI-64 address type 4.4. Description of the EUI-64 address type
The IEEE EUI-64 address [IEEE802-eui64] is encoded as a 8 octet The IEEE EUI-64 address [IEEE802-eui64] is encoded as a 8 octet
string containing the full IEEE EUI-64 address. string containing the full IEEE EUI-64 address.
3.5. Description of the DUID-LLT type 4.5. Description of the DUID-LLT type
The DUID-LLT is the DHCPv6 Unique Identifier (DUID) formulated by The DUID-LLT is the DHCPv6 Unique Identifier (DUID) formulated by
concatenating the link-layer address plus a timestamp [RFC3315]. concatenating the link-layer address plus a timestamp [RFC3315].
This type of DUID consists of a two octet type field containing the This type of DUID consists of a two octet type field containing the
value 1, a two octet hardware type code, four octets containing a value 1, a two octet hardware type code, four octets containing a
time value, followed by link-layer address of any one network time value, followed by link-layer address of any one network
interface that is connected to the DHCP device at the time that the interface that is connected to the DHCP device at the time that the
DUID is generated. The time value is the time that the DUID is DUID is generated. The time value is the time that the DUID is
generated represented in seconds since midnight (UTC), January 1, generated represented in seconds since midnight (UTC), January 1,
2000, modulo 2^32. Since the link-layer address can be of variable 2000, modulo 2^32. Since the link-layer address can be of variable
length [RFC2464], the DUID-LLT is of variable length. length [RFC2464], the DUID-LLT is of variable length.
3.6. Description of the DUID-EN type 4.6. Description of the DUID-EN type
The DUID-EN is the DHCPv6 Unique Identifier (DUID) formulated by The DUID-EN is the DHCPv6 Unique Identifier (DUID) formulated by
concatenating the Enterprise Number plus some additional data concatenating the Enterprise Number plus some additional data
[RFC3315]. This form of DUID is assigned by the vendor to the [RFC3315]. This form of DUID is assigned by the vendor to the
device. It consists of a two octet type field containing the value device. It consists of a two octet type field containing the value
2, the vendor's registered Private Enterprise Number as maintained by 2, the vendor's registered Private Enterprise Number as maintained by
IANA, followed by a unique identifier assigned by the vendor. Since IANA, followed by a unique identifier assigned by the vendor. Since
the vendor's unique identifier can be of variable length, the DUID-EN the vendor's unique identifier can be of variable length, the DUID-EN
is of variable length. is of variable length.
3.7. Description of the DUID-LL type 4.7. Description of the DUID-LL type
The DUID-LL is the DHCPv6 Unique Identifier (DUID) formulated by The DUID-LL is the DHCPv6 Unique Identifier (DUID) formulated by
concatenating the network hardware type code and the link-layer concatenating the network hardware type code and the link-layer
address [RFC3315]. This type of DUID consists of two octets address [RFC3315]. This type of DUID consists of two octets
containing the DUID type 3, a two octet network hardware type code, containing the DUID type 3, a two octet network hardware type code,
followed by the link-layer address of any one network interface that followed by the link-layer address of any one network interface that
is permanently connected to the client or server device. For is permanently connected to the client or server device. For
example, a host that has a network interface implemented in a chip example, a host that has a network interface implemented in a chip
that is unlikely to be removed and used elsewhere could use a DUID- that is unlikely to be removed and used elsewhere could use a DUID-
LL. Since the link-layer address can be of variable length, the LL. Since the link-layer address can be of variable length, the
DUID-LL is of variable length. DUID-LL is of variable length.
3.8. Description of the DUID-UUID type 4.8. Description of the DUID-UUID type
The DUID-UUID [RFC6355] is the DHCPv6 Unique Identifier based on the The DUID-UUID [RFC6355] is the DHCPv6 Unique Identifier based on the
Universally Unique IDentifier (UUID) [RFC4122]. This type of DUID Universally Unique IDentifier (UUID) [RFC4122]. This type of DUID
consists of two octets containing the DUID type 4, followed by consists of two octets containing the DUID type 4, followed by
128-bit UUID. 128-bit UUID.
3.9. Description of the RFID types 4.9. Description of the RFID types
The General Identifier (GID) that is used with RFID is composed of The General Identifier (GID) that is used with RFID is composed of
three fields - the General Manager Number, Object Class and Serial three fields - the General Manager Number, Object Class and Serial
Number. The General Manager Number identifies an organizational Number. The General Manager Number identifies an organizational
entity that is responsible for maintaining the numbers in subsequent entity that is responsible for maintaining the numbers in subsequent
fields. GID encodings include a fourth field, the header, to fields. GID encodings include a fourth field, the header, to
guarantee uniqueness in the namespace defined by EPC. guarantee uniqueness in the namespace defined by EPC.
Some of the RFID types depend on the Global Trade Item Number (GTIN) Some of the RFID types depend on the Global Trade Item Number (GTIN)
code defined in the General EAN.UCC Specifications [EANUCCGS]. A code defined in the General EAN.UCC Specifications [EANUCCGS]. A
skipping to change at page 7, line 38 skipping to change at page 7, line 46
General EAN.UCC Specifications. Unlike the GTIN, the GIAI is already General EAN.UCC Specifications. Unlike the GTIN, the GIAI is already
intended for assignment to individual objects and therefore does not intended for assignment to individual objects and therefore does not
require any additional fields to serve as an EPC pure identity. The require any additional fields to serve as an EPC pure identity. The
GRAI includes the Company Prefix, and Individual Asset Reference. GRAI includes the Company Prefix, and Individual Asset Reference.
The DoD Construct identifier is defined by the United States The DoD Construct identifier is defined by the United States
Department of Defense (DoD). This tag data construct may be used to 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 encode tags for shipping goods to the DoD by a supplier who has
already been assigned a CAGE (Commercial and Government Entity) code. already been assigned a CAGE (Commercial and Government Entity) code.
3.9.1. Description of the RFID-SGTIN-64 type 4.9.1. Description of the RFID-SGTIN-64 type
The RFID-SGTIN-64 is encoded as specified in [EPC-Tag-Data]. The The RFID-SGTIN-64 is encoded as specified in [EPC-Tag-Data]. The
SGTIN-64 includes five fields: Header, Filter Value (additional data SGTIN-64 includes five fields: Header, Filter Value (additional data
that is used for fast filtering and pre-selection), Company Prefix that is used for fast filtering and pre-selection), Company Prefix
Index, Item Reference, and Serial Number. Only a limited number of Index, Item Reference, and Serial Number. Only a limited number of
Company Prefixes can be represented in the 64-bit tag. Company Prefixes can be represented in the 64-bit tag.
3.9.2. Description of the RFID-SGTIN-96 type 4.9.2. Description of the RFID-SGTIN-96 type
The RFID-SGTIN-96 is encoded as specified in [EPC-Tag-Data]. The The RFID-SGTIN-96 is encoded as specified in [EPC-Tag-Data]. The
SGTIN-96 includes six fields: Header, Filter Value, Partition (an SGTIN-96 includes six fields: Header, Filter Value, Partition (an
indication of where the subsequent Company Prefix and Item Reference indication of where the subsequent Company Prefix and Item Reference
numbers are divided), Company Prefix Index, Item Reference, and numbers are divided), Company Prefix Index, Item Reference, and
Serial Number. Serial Number.
3.9.3. Description of the RFID-SSCC-64 type 4.9.3. Description of the RFID-SSCC-64 type
The RFID-SSCC-64 is encoded as specified in [EPC-Tag-Data]. The The RFID-SSCC-64 is encoded as specified in [EPC-Tag-Data]. The
SSCC-64 includes four fields: Header, Filter Value, Company Prefix SSCC-64 includes four fields: Header, Filter Value, Company Prefix
Index, and Serial Reference. Only a limited number of Company Index, and Serial Reference. Only a limited number of Company
Prefixes can be represented in the 64-bit tag. Prefixes can be represented in the 64-bit tag.
3.9.4. Description of the RFID-SSCC-96 type 4.9.4. Description of the RFID-SSCC-96 type
The RFID-SSCC-96 is encoded as specified in [EPC-Tag-Data]. The The RFID-SSCC-96 is encoded as specified in [EPC-Tag-Data]. The
SSCC-96 includes six fields: Header, Filter Value, Partition, Company SSCC-96 includes six fields: Header, Filter Value, Partition, Company
Prefix, and Serial Reference, as well as 24 bits that remain Prefix, and Serial Reference, as well as 24 bits that remain
Unallocated and must be zero. Unallocated and must be zero.
3.9.5. Description of the RFID-SGLN-64 type 4.9.5. Description of the RFID-SGLN-64 type
The RFID-SGLN-64 type is encoded as specified in [EPC-Tag-Data]. The The RFID-SGLN-64 type is encoded as specified in [EPC-Tag-Data]. The
SGLN-64 includes five fields: Header, Filter Value, Company Prefix SGLN-64 includes five fields: Header, Filter Value, Company Prefix
Index, Location Reference, and Serial Number. Index, Location Reference, and Serial Number.
3.9.6. Description of the RFID-SGLN-96 type 4.9.6. Description of the RFID-SGLN-96 type
The RFID-SGLN-96 type is encoded as specified in [EPC-Tag-Data]. The The RFID-SGLN-96 type is encoded as specified in [EPC-Tag-Data]. The
SGLN-96 includes six fields: Header, Filter Value, Partition, Company SGLN-96 includes six fields: Header, Filter Value, Partition, Company
Prefix, Location Reference, and Serial Number. Prefix, Location Reference, and Serial Number.
3.9.7. Description of the RFID-GRAI-64 type 4.9.7. Description of the RFID-GRAI-64 type
The RFID-GRAI-64 type is encoded as specified in [EPC-Tag-Data]. The The RFID-GRAI-64 type is encoded as specified in [EPC-Tag-Data]. The
GRAI-64 includes five fields: Header, Filter Value, Company Prefix GRAI-64 includes five fields: Header, Filter Value, Company Prefix
Index, Asset Type, and Serial Number. Index, Asset Type, and Serial Number.
3.9.8. Description of the RFID-GRAI-96 type 4.9.8. Description of the RFID-GRAI-96 type
The RFID-GRAI-96 type is encoded as specified in [EPC-Tag-Data]. The The RFID-GRAI-96 type is encoded as specified in [EPC-Tag-Data]. The
GRAI-96 includes six fields: Header, Filter Value, Partition, Company GRAI-96 includes six fields: Header, Filter Value, Partition, Company
Prefix, Asset Type, and Serial Number. Prefix, Asset Type, and Serial Number.
3.9.9. Description of the RFID-GIAI-64 type 4.9.9. Description of the RFID-GIAI-64 type
The RFID-GIAI-64 type is encoded as specified in [EPC-Tag-Data]. The The RFID-GIAI-64 type is encoded as specified in [EPC-Tag-Data]. The
GIAI-64 includes four fields: Header, Filter Value, Company Prefix GIAI-64 includes four fields: Header, Filter Value, Company Prefix
Index, and Individual Asset Reference. Index, and Individual Asset Reference.
3.9.10. Description of the RFID-GIAI-96 type 4.9.10. Description of the RFID-GIAI-96 type
The RFID-GIAI-96 type is encoded as specified in [EPC-Tag-Data]. The The RFID-GIAI-96 type is encoded as specified in [EPC-Tag-Data]. The
GIAI-96 includes five fields: Header, Filter Value, Partition, GIAI-96 includes five fields: Header, Filter Value, Partition,
Company Prefix, and Individual Asset Reference. Company Prefix, and Individual Asset Reference.
3.9.11. Description of the RFID-DoD-64 type 4.9.11. Description of the RFID-DoD-64 type
The RFID-DoD-64 type is encoded as specified in [RFID-DoD-spec]. The The RFID-DoD-64 type is encoded as specified in [RFID-DoD-spec]. The
DoD-64 type includes four fields: Header, Filter Value, Government DoD-64 type includes four fields: Header, Filter Value, Government
Managed Identifier, and Serial Number. Managed Identifier, and Serial Number.
3.9.12. Description of the RFID-DoD-96 type 4.9.12. Description of the RFID-DoD-96 type
The RFID-DoD-96 type is encoded as specified in [RFID-DoD-spec]. The The RFID-DoD-96 type is encoded as specified in [RFID-DoD-spec]. The
DoD-96 type includes four fields: Header, Filter Value, Government DoD-96 type includes four fields: Header, Filter Value, Government
Managed Identifier, and Serial Number. Managed Identifier, and Serial Number.
3.9.13. Description of the RFID URI types 4.9.13. Description of the RFID URI types
In some cases, it is desirable to encode in URI form a specific In some cases, it is desirable to encode in URI form a specific
encoding of an RFID tag. For example, an application may prefer a encoding of an RFID tag. For example, an application may prefer a
URI representation for report preparation. Applications that wish to URI representation for report preparation. Applications that wish to
manipulate any additional data fields on tags may need some manipulate any additional data fields on tags may need some
representation other than the pure identity forms. representation other than the pure identity forms.
For this purpose, the fields as represented the previous sections are For this purpose, the fields as represented the previous sections are
associated with specified fields in the various URI types. For associated with specified fields in the various URI types. For
instance, the URI may have fields such as CompanyPrefix, instance, the URI may have fields such as CompanyPrefix,
ItemReference, or SerialNumber. For details and encoding specifics, ItemReference, or SerialNumber. For details and encoding specifics,
consult [EPC-Tag-Data]. consult [EPC-Tag-Data].
4. Security Considerations 5. Security Considerations
This document does not introduce any security mechanisms, and does This document does not introduce any security mechanisms, and does
not have any impact on existing security mechanisms. Insofar as the not have any impact on existing security mechanisms. Insofar as the
selection of a security association may be dependent on the exact selection of a security association may be dependent on the exact
form of a mobile node identifier, additional specification may be form of a mobile node identifier, additional specification may be
necessary when the new identifier types are employed with the general necessary when the new identifier types are employed with the general
AAA mechanisms for mobile node authorizations. AAA mechanisms for mobile node authorizations.
Some identifiers (e.g., IMSI) are considered to be private Some identifiers (e.g., IMSI) are considered to be private
information. If used in the MNID extension as defined in this information. If used in the MNID extension as defined in this
skipping to change at page 10, line 15 skipping to change at page 10, line 22
information. information.
Moreover, MNIDs containing sensitive identifiers might only be used Moreover, MNIDs containing sensitive identifiers might only be used
for signaling during initial network entry. Subsequent binding for signaling during initial network entry. Subsequent binding
update exchanges might then rely on a temporary identifier allocated update exchanges might then rely on a temporary identifier allocated
during the initial network entry, perhaps using mechanisms not during the initial network entry, perhaps using mechanisms not
standardized within the IETF. Managing the association between long- standardized within the IETF. Managing the association between long-
lived and temporary identifiers is outside the scope of this lived and temporary identifiers is outside the scope of this
document. document.
5. IANA Considerations 6. IANA Considerations
The new mobile node identifier types defined in the document should The new mobile node identifier types defined in the document should
be assigned values from the "Mobile Node Identifier Option Subtypes" be assigned values from the "Mobile Node Identifier Option Subtypes"
registry. The following values should be assigned. registry. The following values should be assigned.
New Mobile Node Identifier Types New Mobile Node Identifier Types
+-----------------+------------------------+ +-----------------+------------------------+
| Identifier Type | Identifier Type Number | | Identifier Type | Identifier Type Number |
+-----------------+------------------------+ +-----------------+------------------------+
skipping to change at page 11, line 49 skipping to change at page 11, line 49
| RFID-SSCC-URI | 34 | | RFID-SSCC-URI | 34 |
| RFID-SGLN-URI | 35 | | RFID-SGLN-URI | 35 |
| RFID-GRAI-URI | 36 | | RFID-GRAI-URI | 36 |
| RFID-DOD-URI | 37 | | RFID-DOD-URI | 37 |
| RFID-GIAI-URI | 38 | | RFID-GIAI-URI | 38 |
| | 39-255 reserved | | | 39-255 reserved |
+-----------------+------------------------+ +-----------------+------------------------+
Table 2 Table 2
See Section 3 for additional information about the identifier types. See Section 4 for additional information about the identifier types.
6. Acknowledgements 7. Acknowledgements
The authors wish to acknowledge Hakima Chaouchi, Jouni Korhonen and The authors wish to acknowledge Hakima Chaouchi, Jouni Korhonen and
Sri Gundavelli for their helpful comments. Sri Gundavelli for their helpful comments.
7. References 8. References
7.1. Normative References 8.1. Normative References
[RFC2119] Bradner, S., "Key words for use in RFCs to Indicate
Requirement Levels", BCP 14, RFC 2119,
DOI 10.17487/RFC2119, March 1997,
<http://www.rfc-editor.org/info/rfc2119>.
[RFC2464] Crawford, M., "Transmission of IPv6 Packets over Ethernet [RFC2464] Crawford, M., "Transmission of IPv6 Packets over Ethernet
Networks", RFC 2464, DOI 10.17487/RFC2464, December 1998, Networks", RFC 2464, DOI 10.17487/RFC2464, December 1998,
<http://www.rfc-editor.org/info/rfc2464>. <http://www.rfc-editor.org/info/rfc2464>.
[RFC3315] Droms, R., Ed., Bound, J., Volz, B., Lemon, T., Perkins, [RFC3315] Droms, R., Ed., Bound, J., Volz, B., Lemon, T., Perkins,
C., and M. Carney, "Dynamic Host Configuration Protocol C., and M. Carney, "Dynamic Host Configuration Protocol
for IPv6 (DHCPv6)", RFC 3315, DOI 10.17487/RFC3315, July for IPv6 (DHCPv6)", RFC 3315, DOI 10.17487/RFC3315, July
2003, <http://www.rfc-editor.org/info/rfc3315>. 2003, <http://www.rfc-editor.org/info/rfc3315>.
[RFC4122] Leach, P., Mealling, M., and R. Salz, "A Universally [RFC4122] Leach, P., Mealling, M., and R. Salz, "A Universally
Unique IDentifier (UUID) URN Namespace", RFC 4122, Unique IDentifier (UUID) URN Namespace", RFC 4122,
DOI 10.17487/RFC4122, July 2005, DOI 10.17487/RFC4122, July 2005,
<http://www.rfc-editor.org/info/rfc4122>. <http://www.rfc-editor.org/info/rfc4122>.
[RFC4283] Patel, A., Leung, K., Khalil, M., Akhtar, H., and K. [RFC4283] Patel, A., Leung, K., Khalil, M., Akhtar, H., and K.
Chowdhury, "Mobile Node Identifier Option for Mobile IPv6 Chowdhury, "Mobile Node Identifier Option for Mobile IPv6
(MIPv6)", RFC 4283, DOI 10.17487/RFC4283, November 2005, (MIPv6)", RFC 4283, DOI 10.17487/RFC4283, November 2005,
<http://www.rfc-editor.org/info/rfc4283>. <http://www.rfc-editor.org/info/rfc4283>.
[RFC4285] Patel, A., Leung, K., Khalil, M., Akhtar, H., and K.
Chowdhury, "Authentication Protocol for Mobile IPv6",
RFC 4285, DOI 10.17487/RFC4285, January 2006,
<http://www.rfc-editor.org/info/rfc4285>.
[RFC4291] Hinden, R. and S. Deering, "IP Version 6 Addressing [RFC4291] Hinden, R. and S. Deering, "IP Version 6 Addressing
Architecture", RFC 4291, DOI 10.17487/RFC4291, February Architecture", RFC 4291, DOI 10.17487/RFC4291, February
2006, <http://www.rfc-editor.org/info/rfc4291>. 2006, <http://www.rfc-editor.org/info/rfc4291>.
[RFC6355] Narten, T. and J. Johnson, "Definition of the UUID-Based [RFC6355] Narten, T. and J. Johnson, "Definition of the UUID-Based
DHCPv6 Unique Identifier (DUID-UUID)", RFC 6355, DHCPv6 Unique Identifier (DUID-UUID)", RFC 6355,
DOI 10.17487/RFC6355, August 2011, DOI 10.17487/RFC6355, August 2011,
<http://www.rfc-editor.org/info/rfc6355>. <http://www.rfc-editor.org/info/rfc6355>.
7.2. Informative References 8.2. Informative References
[EANUCCGS] [EANUCCGS]
EAN International and the Uniform Code Council, , "General EAN International and the Uniform Code Council, , "General
EAN.UCC Specifications Version 5.0", Jan 2004. EAN.UCC Specifications Version 5.0", Jan 2004.
[EPC-Tag-Data] [EPC-Tag-Data]
EPCglobal Inc., , "EPC(TM) Generation 1 Tag Data Standards EPCglobal Inc., , "EPC(TM) Generation 1 Tag Data Standards
Version 1.1 Rev.1.27 Version 1.1 Rev.1.27
http://www.gs1.org/gsmp/kc/epcglobal/tds/ http://www.gs1.org/gsmp/kc/epcglobal/tds/
tds_1_1_rev_1_27-standard-20050510.pdf", January 2005. tds_1_1_rev_1_27-standard-20050510.pdf", January 2005.
[IEEE802] IEEE, , "IEEE Std 802: IEEE Standards for Local and [IEEE802] IEEE, , "IEEE Std 802: IEEE Standards for Local and
Metropolitan Networks: Overview and Architecture", 2001. Metropolitan Networks: Overview and Architecture", 2001.
[IEEE802-eui]
IEEE, , "Guidelines for Use Organizationally Unique
Identifier (OUI) and Company ID (CID)
https://standards.ieee.org/develop/regauth/tut/eui.pdf",
2001.
[IEEE802-eui48] [IEEE802-eui48]
IEEE, , "Guidelines for 48-Bit Global Identifier (EUI-48) IEEE, , "Guidelines for 48-Bit Global Identifier (EUI-48)
https://standards.ieee.org/develop/regauth/tut/eui48.pdf", https://standards.ieee.org/develop/regauth/tut/eui48.pdf",
2001. 2001.
[IEEE802-eui64] [IEEE802-eui64]
IEEE, , "Guidelines for 64-Bit Global Identifier (EUI-64) IEEE, , "Guidelines for 64-Bit Global Identifier (EUI-64)
https://standards.ieee.org/develop/regauth/tut/eui.pdf64", https://standards.ieee.org/develop/regauth/tut/eui.pdf64",
2001. 2001.
 End of changes. 37 change blocks. 
77 lines changed or deleted 79 lines changed or added

This html diff was produced by rfcdiff 1.45. The latest version is available from http://tools.ietf.org/tools/rfcdiff/