draft-ietf-dmm-4283mnids-00.txt		draft-ietf-dmm-4283mnids-01.txt
	Distributed Mobility Management [dmm] C. Perkins		Distributed Mobility Management [dmm] C. Perkins
	Internet-Draft Futurewei		Internet-Draft Futurewei
	Expires: October 24, 2015 V. Devarapalli		Expires: April 21, 2016 V. Devarapalli
	Vasona Networks		Vasona Networks
	April 22, 2015		October 19, 2015
	MN Identifier Types for RFC 4283 Mobile Node Identifier Option		MN Identifier Types for RFC 4283 Mobile Node Identifier Option
	draft-ietf-dmm-4283mnids-00.txt		draft-ietf-dmm-4283mnids-01.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 October 24, 2015.		This Internet-Draft will expire on April 21, 2016.
	Copyright Notice		Copyright Notice
	Copyright (c) 2015 IETF Trust and the persons identified as the		Copyright (c) 2015 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 . . . . . . . . . . . . . . 2
	3. Security Considerations . . . . . . . . . . . . . . . . . . . 3		3. Security Considerations . . . . . . . . . . . . . . . . . . . 4
	4. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 4		4. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 5
	5. References . . . . . . . . . . . . . . . . . . . . . . . . . 6		5. References . . . . . . . . . . . . . . . . . . . . . . . . . 7
	5.1. Normative References . . . . . . . . . . . . . . . . . . 6		5.1. Normative References . . . . . . . . . . . . . . . . . . 7
	5.2. Informative References . . . . . . . . . . . . . . . . . 6		5.2. Informative References . . . . . . . . . . . . . . . . . 7
	Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 7		Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 8
	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 commonly in use in various		propose adding some basic types that are defined in various
	telecommunications standards, including the IMSI, P-TMSI, IMEI, GUTI,		telecommunications standards, including types for IMSI
	and IEEE MAC-layer addresses. In addition, we include the IPv6		[ThreeGPP-IDS], P-TMSI [ThreeGPP-IDS], IMEI [ThreeGPP-IDS], and GUTI
	address itself as a legitimate mobile node identifier.		[ThreeGPP-IDS]. In addition, we include IEEE MAC-layer addresses the
			IPv6 address itself as a legitimate mobile node identifier. Defining
			identifiers that are tied to the physical elements of the device
			(RFID, MAC address etc.) help in deployment of Mobile IP because in
			many cases such identifiers are the most natural means for uniquely
			identifying the device, and will avoid additional look-up steps that
			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.
	EPC supports several encoding systems or schemes including		The Tag Data standard promoted by Electronic Product Code(TM)
			(abbreviated EPC) supports several encoding systems or schemes
			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-GLN (Global Location Number),
	o RFID-GRAI (Global Returnable Asset Identifier),		o RFID-GRAI (Global Returnable Asset Identifier),
	o RFID-DOD (Department of Defense) 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, GLN-64) and a 96-bit scheme (GLN-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.
	o IPv6 Address [RFC2373]		Mobile Node Identifier Description
	o IMSI [ThreeGPP-IDS]
	o P-TMSI [ThreeGPP-IDS]		+----------------+---------------------------------+----------------+
	o GUTI [ThreeGPP-IDS]		| Identifier | Description | Reference |
	o EUI-48 address [IEEE802]		| Type | | |
	o EUI-64 address [IEEE802]		+----------------+---------------------------------+----------------+
	o DUID-LLT [RFC3315]		| IPv6 Address | | [RFC2373] |
	o DUID-EN [RFC3315]		| IMSI | International Mobile Subscriber | [ThreeGPP-IDS] |
	o DUID-LL [RFC3315]		| | Identity | |
	o DUID-UUID [RFC6355]		| P-TMSI | Packet-Temporary Mobile | [ThreeGPP-IDS] |
	o 12-15 reserved		| | Subscriber Identity | |
	o 16 reserved		| GUTI | Globally Unique Temporary ID | [ThreeGPP-IDS] |
	o RFID-SGTIN-64 [EPC-Tag-Data]		| EUI-48 address | 48-bit Extended Unique | [IEEE802] |
	o RFID-SSCC-64 [EPC-Tag-Data]		| | Identifier | |
	o RFID-GLN-64 [EPC-Tag-Data]		| EUI-64 address | 64-bit Extended Unique | [IEEE802] |
	o RFID-GRAI-64 [EPC-Tag-Data]		| | Identifier-64 bit | |
	o RFID-DOD-64 [RFID-DoD-96]		| DUID-LLT | DHCPv6 Unique Identifier: Link- | [RFC3315] |
	o RFID-GIAI-64 [EPC-Tag-Data]		| | Layer address plus timestamp | |
	o 23 reserved		| DUID-EN | DHCPv6 Unique Identifier: | [RFC3315] |
	o RFID-GID-96 [EPC-Tag-Data]		| | Enterprise Number plus add'l | |
	o RFID-SGTIN-96 [EPC-Tag-Data]		| | data | |
	o RFID-SSCC-96 [EPC-Tag-Data]		| DUID-LL | DHCPv6 Unique Identifier: Link- | [RFC3315] |
	o RFID-GLN-96 [EPC-Tag-Data]		| | Layer address | |
	o RFID-GRAI-96 [EPC-Tag-Data]		| DUID-UUID | DHCPv6 Unique Identifier: other | [RFC6355] |
	o RFID-DOD-96 [RFID-DoD-96]		| | conformant format | |
	o RFID-GIAI-96 [EPC-Tag-Data]		| RFID-SGTIN-64 | 64-bit Serialized Global Trade | [EPC-Tag-Data] |
	o 31 reserved		| | Item Number | |
	o RFID-GID-URI [EPC-Tag-Data]		| RFID-SSCC-64 | 64-bit Serial Shipping | [EPC-Tag-Data] |
	o RFID-SGTIN-URI [EPC-Tag-Data]		| | Container | |
	o RFID-SSCC-URI [EPC-Tag-Data]		| RFID-GLN-64 | 64-bit Global Location Number | [EPC-Tag-Data] |
	o RFID-GLN-URI [EPC-Tag-Data]		| RFID-GRAI-64 | 64-bit Global Returnable Asset | [EPC-Tag-Data] |
	o RFID-GRAI-URI [EPC-Tag-Data]		| | Identifier | |
	o RFID-DOD-URI [RFID-DoD-96]		| RFID-DOD-64 | 64-bit Department of Defense ID | [RFID-DoD-96] |
	o RFID-GIAI-URI [EPC-Tag-Data]		| RFID-GIAI-64 | 64-bit Global Individual Asset | [EPC-Tag-Data] |
	o 39-255 reserved		| | 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-GLN-96 | 96-bit Global Location Number | [EPC-Tag-Data] |
			| RFID-GRAI-96 | 96-bit Global Returnable Asset | [EPC-Tag-Data] |
			| | Identifier | |
			| RFID-DOD-96 | 96-bit Department of Defense ID | [RFID-DoD-96] |
			| RFID-GIAI-96 | 96-bit Global Individual Asset | [EPC-Tag-Data] |
			| | Identifier | |
			| RFID-GID-URI | Global Identifier represented | [EPC-Tag-Data] |
			| | as URI | |
			| RFID-SGTIN-URI | Serialized Global Trade Item | [EPC-Tag-Data] |
			| | Number represented as URI | |
			| RFID-SSCC-URI | Serial Shipping Container | [EPC-Tag-Data] |
			| | represented as URI | |
			| RFID-GLN-URI | Global Location Number | [EPC-Tag-Data] |
			| | 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-96] |
			| | represented as URI | |
			| RFID-GIAI-URI | Global Individual Asset | [EPC-Tag-Data] |
			| | Identifier represented as URI | |
			+----------------+---------------------------------+----------------+
			Table 1
	3. Security Considerations		3. 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
	document, the packet including the MNID extension should be encrypted		document, the packet including the MNID extension should be encrypted
	so that personal information or trackable identifiers would not be		so that personal information or trackable identifiers would not be
	inadvertently disclosed to passive observers. Moreover, MNIDs		inadvertently disclosed to passive observers. Operators can
	containing sensitive identifiers might only be used for signaling		potentially apply IPsec Encapsulating Security Payload (ESP) with
	during initial network entry. Subsequent binding update exchanges		confidentiality and integrity protection for protecting the location
	would then rely on a temporary identifier allocated during the		information.
	initial network entry.
			Moreover, MNIDs containing sensitive identifiers might only be used
			for signaling during initial network entry. Subsequent binding
			update exchanges might then rely on a temporary identifier allocated
			during the initial network entry, perhaps using mechanisms not
			standardized within the IETF. Managing the association between long-
			lived and temporary identifiers is outside the scope of this
			document.
	4. IANA Considerations		4. 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
	+-----------------+------------------------+		+-----------------+------------------------+
	skipping to change at page 5, line 47		skipping to change at page 6, line 47
	| 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-GLN-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 1		Table 2
	See Section 2 for details about the identifer types.		See Section 2 for additional information about the identifier types.
	5. References		5. References
	5.1. Normative References		5.1. Normative References
	[RFC2373] Hinden, R. and S. Deering, "IP Version 6 Addressing		[RFC2373] Hinden, R. and S. Deering, "IP Version 6 Addressing
	Architecture", RFC 2373, July 1998.		Architecture", RFC 2373, DOI 10.17487/RFC2373, July 1998,
			<http://www.rfc-editor.org/info/rfc2373>.
	[RFC3315] Droms, R., Bound, J., Volz, B., Lemon, T., Perkins, C.,		[RFC3315] Droms, R., Ed., Bound, J., Volz, B., Lemon, T., Perkins,
	and M. Carney, "Dynamic Host Configuration Protocol for		C., and M. Carney, "Dynamic Host Configuration Protocol
	IPv6 (DHCPv6)", RFC 3315, July 2003.		for IPv6 (DHCPv6)", RFC 3315, DOI 10.17487/RFC3315, July
			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, July		Unique IDentifier (UUID) URN Namespace", RFC 4122,
	2005.		DOI 10.17487/RFC4122, July 2005,
			<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, November 2005.		(MIPv6)", RFC 4283, DOI 10.17487/RFC4283, November 2005,
			<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", RFC		Chowdhury, "Authentication Protocol for Mobile IPv6",
	4285, January 2006.		RFC 4285, DOI 10.17487/RFC4285, January 2006,
			<http://www.rfc-editor.org/info/rfc4285>.
	[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, August		DHCPv6 Unique Identifier (DUID-UUID)", RFC 6355,
	2011.		DOI 10.17487/RFC6355, August 2011,
			<http://www.rfc-editor.org/info/rfc6355>.
	5.2. Informative References		5.2. Informative References
	[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.
	[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, September 2003.		Arkko, "Diameter Base Protocol", RFC 3588,
			DOI 10.17487/RFC3588, September 2003,
			<http://www.rfc-editor.org/info/rfc3588>.
	[RFID-DoD-96]		[RFID-DoD-96]
	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
End of changes. 19 change blocks.
	70 lines changed or deleted		121 lines changed or added
This html diff was produced by rfcdiff 1.42. The latest version is available from http://tools.ietf.org/tools/rfcdiff/