draft-ietf-dmm-4283mnids-01.txt		draft-ietf-dmm-4283mnids-02.txt
	Distributed Mobility Management [dmm] C. Perkins		Distributed Mobility Management [dmm] C. Perkins
	Internet-Draft Futurewei		Internet-Draft Futurewei
	Expires: April 21, 2016 V. Devarapalli		Expires: December 11, 2016 V. Devarapalli
	Vasona Networks		Vasona Networks
	October 19, 2015		June 9, 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-01.txt		draft-ietf-dmm-4283mnids-02.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 April 21, 2016.		This Internet-Draft will expire on December 11, 2016.
	Copyright Notice		Copyright Notice
	Copyright (c) 2015 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 . . . . . . . . . . . . . . 2		2. New Mobile Node Identifier Types . . . . . . . . . . . . . . 3
	3. Security Considerations . . . . . . . . . . . . . . . . . . . 4		3. Descriptions of MNID types . . . . . . . . . . . . . . . . . 5
	4. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 5		3.1. Description of the IPv6 address type . . . . . . . . . . 5
	5. References . . . . . . . . . . . . . . . . . . . . . . . . . 7		3.2. Description of the IMSI MNID type . . . . . . . . . . . . 5
	5.1. Normative References . . . . . . . . . . . . . . . . . . 7		3.3. Description of the EUI-48 address type . . . . . . . . . 5
	5.2. Informative References . . . . . . . . . . . . . . . . . 7		3.4. Description of the EUI-64 address type . . . . . . . . . 5
	Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 8		3.5. Description of the DUID-LLT type . . . . . . . . . . . . 5
			3.6. Description of the DUID-EN type . . . . . . . . . . . . . 6
			3.7. Description of the DUID-LL type . . . . . . . . . . . . . 6
			3.8. Description of the DUID-UUID type . . . . . . . . . . . . 6
			3.9. Description of the RFID types . . . . . . . . . . . . . . 6
			3.9.1. Description of the RFID-SGTIN-64 type . . . . . . . . 7
			3.9.2. Description of the RFID-SGTIN-96 type . . . . . . . . 7
			3.9.3. Description of the RFID-SSCC-64 type . . . . . . . . 8
			3.9.4. Description of the RFID-SSCC-96 type . . . . . . . . 8
			3.9.5. Description of the RFID-SGLN-64 type . . . . . . . . 8
			3.9.6. Description of the RFID-SGLN-96 type . . . . . . . . 8
			3.9.7. Description of the RFID-GRAI-64 type . . . . . . . . 8
			3.9.8. Description of the RFID-GRAI-96 type . . . . . . . . 8
			3.9.9. Description of the RFID-GIAI-64 type . . . . . . . . 8
			3.9.10. Description of the RFID-GIAI-96 type . . . . . . . . 9
			3.9.11. Description of the RFID-DoD-64 type . . . . . . . . . 9
			3.9.12. Description of the RFID-DoD-96 type . . . . . . . . . 9
			3.9.13. Description of the RFID URI types . . . . . . . . . . 9
			4. Security Considerations . . . . . . . . . . . . . . . . . . . 9
			5. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 10
			6. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 12
			7. References . . . . . . . . . . . . . . . . . . . . . . . . . 12
			7.1. Normative References . . . . . . . . . . . . . . . . . . 12
			7.2. Informative References . . . . . . . . . . . . . . . . . 12
			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
	propose adding some basic types that are defined in various		propose adding some basic types that are defined in various
	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 include IEEE MAC-layer addresses the		[ThreeGPP-IDS]. In addition, we specify the IPv6 address itself and
	IPv6 address itself as a legitimate mobile node identifier. 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. 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),
	o RFID-SGTIN (Serialized Global Trade Item Number),		o RFID-SGTIN (Serialized Global Trade Item Number),
	o RFID-SSCC (Serial Shipping Container),		o RFID-SSCC (Serial Shipping Container),
	o RFID-GLN (Global Location Number),		o RFID-SGLN (Global Location Number),
	o RFID-GRAI (Global Returnable Asset Identifier),		o RFID-GRAI (Global Returnable Asset Identifier),
	o RFID-DOD (Department of Defense ID), and		o RFID-DOD (Department of Defense ID), and
	o RFID-GIAI (Global Individual Asset Identifier).		o RFID-GIAI (Global Individual Asset Identifier).
	For each RFID scheme except GID, there are two variations: a 64-bit		For each RFID scheme except GID, there are two variations: a 64-bit
	scheme (for example, GLN-64) and a 96-bit scheme (GLN-96). GID has		scheme (for example, SGLN-64) and a 96-bit scheme (SGLN-96). GID has
	only a 96-bit scheme. Within each scheme, an EPC identifier can be		only a 96-bit scheme. Within each scheme, an EPC identifier can be
	represented in a binary form or other forms such as URI.		represented in a binary form or other forms such as URI.
	The following list includes the above RFID types as well as various		The following list includes the above RFID types as well as various
	other common identifiers and several different types of DUIDs.		other common identifiers and several different types of DUIDs.
	Mobile Node Identifier Description		Mobile Node Identifier Description
	+----------------+---------------------------------+----------------+		+----------------+--------------------------------+-----------------+
	| Identifier | Description | Reference |		| Identifier | Description | Reference |
	| Type | | |		| Type | | |
	+----------------+---------------------------------+----------------+		+----------------+--------------------------------+-----------------+
	| IPv6 Address | | [RFC2373] |		| IPv6 Address | | [RFC4291] |
	| IMSI | International Mobile Subscriber | [ThreeGPP-IDS] |		| IMSI | International Mobile | [ThreeGPP-IDS] |
	| | Identity | |		| | Subscriber Identity | |
	| P-TMSI | Packet-Temporary Mobile | [ThreeGPP-IDS] |		| P-TMSI | Packet-Temporary Mobile | [ThreeGPP-IDS] |
	| | Subscriber Identity | |		| | Subscriber Identity | |
	| GUTI | Globally Unique Temporary ID | [ThreeGPP-IDS] |		| GUTI | Globally Unique Temporary ID | [ThreeGPP-IDS] |
	| EUI-48 address | 48-bit Extended Unique | [IEEE802] |		| EUI-48 address | 48-bit Extended Unique | [IEEE802] |
	| | Identifier | |		| | Identifier | |
	| EUI-64 address | 64-bit Extended Unique | [IEEE802] |		| EUI-64 address | 64-bit Extended Unique | [IEEE802] |
	| | Identifier-64 bit | |		| | Identifier-64 bit | |
	| DUID-LLT | DHCPv6 Unique Identifier: Link- | [RFC3315] |		| DUID-LLT | DHCPv6 Unique Identifier: | [RFC3315] |
	| | Layer address plus timestamp | |		| | Link-Layer address plus | |
	| DUID-EN | DHCPv6 Unique Identifier: | [RFC3315] |		| | timestamp | |
	| | Enterprise Number plus add'l | |		| DUID-EN | DHCPv6 Unique Identifier: | [RFC3315] |
	| | data | |		| | Enterprise Number plus add'l | |
	| DUID-LL | DHCPv6 Unique Identifier: Link- | [RFC3315] |		| | data | |
	| | Layer address | |		| DUID-LL | DHCPv6 Unique Identifier: | [RFC3315] |
	| DUID-UUID | DHCPv6 Unique Identifier: other | [RFC6355] |		| | Link-Layer address | |
	| | conformant format | |		| DUID-UUID | DHCPv6 Unique Identifier: | [RFC6355] |
	| RFID-SGTIN-64 | 64-bit Serialized Global Trade | [EPC-Tag-Data] |		| | other conformant format | |
	| | Item Number | |		| RFID-SGTIN-64 | 64-bit Serialized Global Trade | [EPC-Tag-Data] |
	| RFID-SSCC-64 | 64-bit Serial Shipping | [EPC-Tag-Data] |		| | Item Number | |
	| | Container | |		| RFID-SSCC-64 | 64-bit Serial Shipping | [EPC-Tag-Data] |
	| RFID-GLN-64 | 64-bit Global Location Number | [EPC-Tag-Data] |		| | Container | |
	| RFID-GRAI-64 | 64-bit Global Returnable Asset | [EPC-Tag-Data] |		| RFID-SGLN-64 | 64-bit Serialized Global | [EPC-Tag-Data] |
	| | Identifier | |		| | Location Number | |
	| RFID-DOD-64 | 64-bit Department of Defense ID | [RFID-DoD-96] |		| RFID-GRAI-64 | 64-bit Global Returnable Asset | [EPC-Tag-Data] |
	| RFID-GIAI-64 | 64-bit Global Individual Asset | [EPC-Tag-Data] |		| | Identifier | |
	| | Identifier | |		| RFID-DOD-64 | 64-bit Department of Defense | [RFID-DoD-spec] |
	| RFID-GID-96 | 96-bit Global Identifier | [EPC-Tag-Data] |		| | ID | |
	| RFID-SGTIN-96 | 96-bit Serialized Global Trade | [EPC-Tag-Data] |		| RFID-GIAI-64 | 64-bit Global Individual Asset | [EPC-Tag-Data] |
	| | Item Number | |		| | Identifier | |
	| RFID-SSCC-96 | 96-bit Serial Shipping | [EPC-Tag-Data] |		| RFID-GID-96 | 96-bit Global Identifier | [EPC-Tag-Data] |
	| | Container | |		| RFID-SGTIN-96 | 96-bit Serialized Global Trade | [EPC-Tag-Data] |
	| RFID-GLN-96 | 96-bit Global Location Number | [EPC-Tag-Data] |		| | Item Number | |
	| RFID-GRAI-96 | 96-bit Global Returnable Asset | [EPC-Tag-Data] |		| RFID-SSCC-96 | 96-bit Serial Shipping | [EPC-Tag-Data] |
	| | Identifier | |		| | Container | |
	| RFID-DOD-96 | 96-bit Department of Defense ID | [RFID-DoD-96] |		| RFID-SGLN-96 | 96-bit Serialized Global | [EPC-Tag-Data] |
	| RFID-GIAI-96 | 96-bit Global Individual Asset | [EPC-Tag-Data] |		| | Location Number | |
	| | Identifier | |		| RFID-GRAI-96 | 96-bit Global Returnable Asset | [EPC-Tag-Data] |
	| RFID-GID-URI | Global Identifier represented | [EPC-Tag-Data] |		| | Identifier | |
	| | as URI | |		| RFID-DOD-96 | 96-bit Department of Defense | [RFID-DoD-spec] |
	| RFID-SGTIN-URI | Serialized Global Trade Item | [EPC-Tag-Data] |		| | ID | |
	| | Number represented as URI | |		| RFID-GIAI-96 | 96-bit Global Individual Asset | [EPC-Tag-Data] |
	| RFID-SSCC-URI | Serial Shipping Container | [EPC-Tag-Data] |		| | Identifier | |
	| | represented as URI | |		| RFID-GID-URI | Global Identifier represented | [EPC-Tag-Data] |
	| RFID-GLN-URI | Global Location Number | [EPC-Tag-Data] |		| | as URI | |
	| | represented as URI | |		| RFID-SGTIN-URI | Serialized Global Trade Item | [EPC-Tag-Data] |
	| RFID-GRAI-URI | Global Returnable Asset | [EPC-Tag-Data] |		| | Number represented as URI | |
	| | Identifier represented as URI | |		| RFID-SSCC-URI | Serial Shipping Container | [EPC-Tag-Data] |
	| RFID-DOD-URI | Department of Defense ID | [RFID-DoD-96] |		| | represented as URI | |
	| | represented as URI | |		| RFID-SGLN-URI | Global Location Number | [EPC-Tag-Data] |
	| RFID-GIAI-URI | Global Individual Asset | [EPC-Tag-Data] |		| | represented as URI | |
	| | Identifier represented as URI | |		| RFID-GRAI-URI | Global Returnable Asset | [EPC-Tag-Data] |
	+----------------+---------------------------------+----------------+		| | Identifier represented as URI | |
			| RFID-DOD-URI | Department of Defense ID | [RFID-DoD-spec] |
			| | represented as URI | |
			| RFID-GIAI-URI | Global Individual Asset | [EPC-Tag-Data] |
			| | Identifier represented as URI | |
			+----------------+--------------------------------+-----------------+
	Table 1		Table 1
	3. Security Considerations		3. Descriptions of MNID types
			In this section descriptions for the various MNID types are provided.
			3.1. Description of the IPv6 address type
			The IPv6 address [RFC4291] is encoded as a 16 octet string containing
			the full IPv6 address.
			3.2. Description of the IMSI MNID 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, where each
			digit occupies 4 bits. The last digit MUST be zero padded, if
			needed, for full octet size. For example an example IMSI
			123456123456789 would be encoded as follows:
			0x12, 0x34, 0x56, 0x12, 0x34, 0x56, 0x78, 0x90
			3.3. Description of the EUI-48 address type
			The IEEE EUI-48 address [IEEE802-eui48] is encoded as a 6 octet
			string containing the IEEE EUI-48 address.
			3.4. Description of the EUI-64 address type
			The IEEE EUI-64 address [IEEE802-eui64] is encoded as a 8 octet
			string containing the full IEEE EUI-64 address.
			3.5. Description of the DUID-LLT type
			The DUID-LLT is the DHCPv6 Unique Identifier (DUID) formulated by
			concatenating the link-layer address plus a timestamp [RFC3315].
			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
			time value, followed by link-layer address of any one network
			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
			generated represented in seconds since midnight (UTC), January 1,
			2000, modulo 2^32. Since the link-layer address can be of variable
			length [RFC2464], the DUID-LLT is of variable length.
			3.6. Description of the DUID-EN type
			The DUID-EN is the DHCPv6 Unique Identifier (DUID) formulated by
			concatenating the Enterprise Number plus some additional data
			[RFC3315]. This form of DUID is assigned by the vendor to the
			device. It consists of a two octet type field containing the value
			2, the vendor's registered Private Enterprise Number as maintained by
			IANA, followed by a unique identifier assigned by the vendor. Since
			the vendor's unique identifier can be of variable length, the DUID-EN
			is of variable length.
			3.7. Description of the DUID-LL type
			The DUID-LL is the DHCPv6 Unique Identifier (DUID) formulated by
			concatenating the network hardware type code and the link-layer
			address [RFC3315]. This type of DUID consists of two octets
			containing the DUID type 3, a two octet network hardware type code,
			followed by the link-layer address of any one network interface that
			is permanently connected to the client or server device. For
			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-
			LL. Since the link-layer address can be of variable length, the
			DUID-LL is of variable length.
			3.8. Description of the DUID-UUID type
			The DUID-UUID [RFC6355] is the DHCPv6 Unique Identifier based on the
			Universally Unique IDentifier (UUID) [RFC4122]. This type of DUID
			consists of two octets containing the DUID type 4, followed by
			128-bit UUID.
			3.9. Description of the RFID types
			The General Identifier (GID) that is used with RFID is composed of
			three fields - the General Manager Number, Object Class and Serial
			Number. The General Manager Number identifies an organizational
			entity that is responsible for maintaining the numbers in subsequent
			fields. GID encodings include a fourth field, the header, to
			guarantee uniqueness in the namespace defined by EPC.
			Some of the RFID types depend on the Global Trade Item Number (GTIN)
			code defined in the General EAN.UCC Specifications [EANUCCGS]. A
			GTIN identifies a particular class of object, such as a particular
			kind of product or SKU.
			The EPC encoding scheme for SGTIN permits the direct embedding of
			EAN.UCC System standard GTIN and Serial Number codes 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 intended for
			assignment to individual objects and therefore does not require
			additional 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 such as a warehouse slot, or an aggregate physical
			location such as an entire warehouse. In addition, a GLN can
			represent a logical entity that performs a business function such as
			placing an order. The Serialized Global Location Number (SGLN)
			includes the Company Prefix, Location Reference, and Serial Number.
			The Global Returnable Asset Identifier is (GRAI) is defined by the
			General EAN.UCC Specifications. Unlike the GTIN, the GRAI is already
			intended for assignment to individual objects and therefore does not
			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. Unlike the GTIN, the GIAI is already
			intended for assignment to individual objects and therefore does not
			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 CAGE (Commercial and Government Entity) code.
			3.9.1. Description of the RFID-SGTIN-64 type
			The RFID-SGTIN-64 is encoded as specified in [EPC-Tag-Data]. The
			SGTIN-64 includes five fields: Header, Filter Value (additional data
			that is used for fast filtering and pre-selection), Company Prefix
			Index, Item Reference, and Serial Number. Only a limited number of
			Company Prefixes can be represented in the 64-bit tag.
			3.9.2. Description of the RFID-SGTIN-96 type
			The RFID-SGTIN-96 is encoded as specified in [EPC-Tag-Data]. The
			SGTIN-96 includes six fields: Header, Filter Value, Partition (an
			indication of where the subsequent Company Prefix and Item Reference
			numbers are divided), Company Prefix Index, Item Reference, and
			Serial Number.
			3.9.3. Description of the RFID-SSCC-64 type
			The RFID-SSCC-64 is encoded as specified in [EPC-Tag-Data]. The
			SSCC-64 includes four fields: Header, Filter Value, Company Prefix
			Index, and Serial Reference. Only a limited number of Company
			Prefixes can be represented in the 64-bit tag.
			3.9.4. Description of the RFID-SSCC-96 type
			The RFID-SSCC-96 is encoded as specified in [EPC-Tag-Data]. The
			SSCC-96 includes six fields: Header, Filter Value, Partition, Company
			Prefix, and Serial Reference, as well as 24 bits that remain
			Unallocated and must be zero.
			3.9.5. Description of the RFID-SGLN-64 type
			The RFID-SGLN-64 type is encoded as specified in [EPC-Tag-Data]. The
			SGLN-64 includes five fields: Header, Filter Value, Company Prefix
			Index, Location Reference, and Serial Number.
			3.9.6. Description of the RFID-SGLN-96 type
			The RFID-SGLN-96 type is encoded as specified in [EPC-Tag-Data]. The
			SGLN-96 includes six fields: Header, Filter Value, Partition, Company
			Prefix, Location Reference, and Serial Number.
			3.9.7. Description of the RFID-GRAI-64 type
			The RFID-GRAI-64 type is encoded as specified in [EPC-Tag-Data]. The
			GRAI-64 includes five fields: Header, Filter Value, Company Prefix
			Index, Asset Type, and Serial Number.
			3.9.8. Description of the RFID-GRAI-96 type
			The RFID-GRAI-96 type is encoded as specified in [EPC-Tag-Data]. The
			GRAI-96 includes six fields: Header, Filter Value, Partition, Company
			Prefix, Asset Type, and Serial Number.
			3.9.9. Description of the RFID-GIAI-64 type
			The RFID-GIAI-64 type is encoded as specified in [EPC-Tag-Data]. The
			GIAI-64 includes four fields: Header, Filter Value, Company Prefix
			Index, and Individual Asset Reference.
			3.9.10. Description of the RFID-GIAI-96 type
			The RFID-GIAI-96 type is encoded as specified in [EPC-Tag-Data]. The
			GIAI-96 includes five fields: Header, Filter Value, Partition,
			Company Prefix, and Individual Asset Reference.
			3.9.11. Description of the RFID-DoD-64 type
			The RFID-DoD-64 type is encoded as specified in [RFID-DoD-spec]. The
			DoD-64 type includes four fields: Header, Filter Value, Government
			Managed Identifier, and Serial Number.
			3.9.12. Description of the RFID-DoD-96 type
			The RFID-DoD-96 type is encoded as specified in [RFID-DoD-spec]. The
			DoD-96 type includes four fields: Header, Filter Value, Government
			Managed Identifier, and Serial Number.
			3.9.13. Description of the RFID URI types
			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
			URI representation for report preparation. Applications that wish to
			manipulate any additional data fields on tags may need some
			representation other than the pure identity forms.
			For this purpose, the fields as represented the previous sections are
			associated with specified fields in the various URI types. For
			instance, the URI may have fields such as CompanyPrefix,
			ItemReference, or SerialNumber. For details and encoding specifics,
			consult [EPC-Tag-Data].
			4. 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 5, line 7 ¶		skipping to change at page 10, line 15 ¶
	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.
	4. IANA Considerations		5. 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 6, line 24 ¶		skipping to change at page 11, line 24 ¶
	| EUI-64 address | 6 |		| EUI-64 address | 6 |
	| GUTI | 7 |		| GUTI | 7 |
	| DUID-LLT | 8 |		| DUID-LLT | 8 |
	| DUID-EN | 9 |		| DUID-EN | 9 |
	| DUID-LL | 10 |		| DUID-LL | 10 |
	| DUID-UUID | 11 |		| DUID-UUID | 11 |
	| | 12-15 reserved |		| | 12-15 reserved |
	| | 16 reserved |		| | 16 reserved |
	| RFID-SGTIN-64 | 17 |		| RFID-SGTIN-64 | 17 |
	| RFID-SSCC-64 | 18 |		| RFID-SSCC-64 | 18 |
	| RFID-GLN-64 | 19 |		| RFID-SGLN-64 | 19 |
	| RFID-GRAI-64 | 20 |		| RFID-GRAI-64 | 20 |
	| RFID-DOD-64 | 21 |		| RFID-DOD-64 | 21 |
	| RFID-GIAI-64 | 22 |		| RFID-GIAI-64 | 22 |
	| | 23 reserved |		| | 23 reserved |
	| RFID-GID-96 | 24 |		| RFID-GID-96 | 24 |
	| RFID-SGTIN-96 | 25 |		| RFID-SGTIN-96 | 25 |
	| RFID-SSCC-96 | 26 |		| RFID-SSCC-96 | 26 |
	| RFID-GLN-96 | 27 |		| RFID-SGLN-96 | 27 |
	| RFID-GRAI-96 | 28 |		| RFID-GRAI-96 | 28 |
	| RFID-DOD-96 | 29 |		| RFID-DOD-96 | 29 |
	| RFID-GIAI-96 | 30 |		| RFID-GIAI-96 | 30 |
	| | 31 reserved |		| | 31 reserved |
	| RFID-GID-URI | 32 |		| RFID-GID-URI | 32 |
	| RFID-SGTIN-URI | 33 |		| RFID-SGTIN-URI | 33 |
	| RFID-SSCC-URI | 34 |		| RFID-SSCC-URI | 34 |
	| RFID-GLN-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 2 for additional information about the identifier types.		See Section 3 for additional information about the identifier types.
	5. References		6. Acknowledgements
	5.1. Normative References		The authors wish to acknowledge Hakima Chaouchi, Jouni Korhonen and
			Sri Gundavelli for their helpful comments.
	[RFC2373] Hinden, R. and S. Deering, "IP Version 6 Addressing		7. References
	Architecture", RFC 2373, DOI 10.17487/RFC2373, July 1998,
	<http://www.rfc-editor.org/info/rfc2373>.		7.1. Normative References
			[RFC2464] Crawford, M., "Transmission of IPv6 Packets over Ethernet
			Networks", RFC 2464, DOI 10.17487/RFC2464, December 1998,
			<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>.
	skipping to change at page 7, line 33 ¶		skipping to change at page 12, line 38 ¶
	[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.		[RFC4285] Patel, A., Leung, K., Khalil, M., Akhtar, H., and K.
	Chowdhury, "Authentication Protocol for Mobile IPv6",		Chowdhury, "Authentication Protocol for Mobile IPv6",
	RFC 4285, DOI 10.17487/RFC4285, January 2006,		RFC 4285, DOI 10.17487/RFC4285, January 2006,
	<http://www.rfc-editor.org/info/rfc4285>.		<http://www.rfc-editor.org/info/rfc4285>.
			[RFC4291] Hinden, R. and S. Deering, "IP Version 6 Addressing
			Architecture", RFC 4291, DOI 10.17487/RFC4291, February
			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>.
	5.2. Informative References		7.2. Informative References
			[EANUCCGS]
			EAN International and the Uniform Code Council, , "General
			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]
			IEEE, , "Guidelines for 48-Bit Global Identifier (EUI-48)
			https://standards.ieee.org/develop/regauth/tut/eui48.pdf",
			2001.
			[IEEE802-eui64]
			IEEE, , "Guidelines for 64-Bit Global Identifier (EUI-64)
			https://standards.ieee.org/develop/regauth/tut/eui.pdf64",
			2001.
	[RFC3588] Calhoun, P., Loughney, J., Guttman, E., Zorn, G., and J.		[RFC3588] Calhoun, P., Loughney, J., Guttman, E., Zorn, G., and J.
	Arkko, "Diameter Base Protocol", RFC 3588,		Arkko, "Diameter Base Protocol", RFC 3588,
	DOI 10.17487/RFC3588, September 2003,		DOI 10.17487/RFC3588, September 2003,
	<http://www.rfc-editor.org/info/rfc3588>.		<http://www.rfc-editor.org/info/rfc3588>.
	[RFID-DoD-96]		[RFID-DoD-spec]
	Department of Defense, , "United States Department of		Department of Defense, , "United States Department of
	Defense Suppliers Passive RFID Information Guide (Version		Defense Suppliers Passive RFID Information Guide (Version
	15.0)", January 2010.		15.0)", January 2010.
	[ThreeGPP-IDS]		[ThreeGPP-IDS]
	3rd Generation Partnership Project, , "3GPP Technical		3rd Generation Partnership Project, , "3GPP Technical
	Specification 23.003 V8.4.0: Technical Specification Group		Specification 23.003 V8.4.0: Technical Specification Group
	Core Network and Terminals; Numbering, addressing and		Core Network and Terminals; Numbering, addressing and
	identification (Release 8)", March 2009.		identification (Release 8)", March 2009.
End of changes. 23 change blocks.
	88 lines changed or deleted		362 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/