Distributed Mobility Management [dmm] C. Perkins
Internet-Draft Futurewei
Expires: April 21, 2016 V. Devarapalli
Vasona Networks
October 19, 2015
MN Identifier Types for RFC 4283 Mobile Node Identifier Option
draft-ietf-dmm-4283mnids-01.txt
Abstract
Additional Identifier Types are proposed for use with the Mobile Node
Identifier Option for MIPv6 (RFC 4283).
Status of This Memo
This Internet-Draft is submitted in full conformance with the
provisions of BCP 78 and BCP 79.
Internet-Drafts are working documents of the Internet Engineering
Task Force (IETF). Note that other groups may also distribute
working documents as Internet-Drafts. The list of current Internet-
Drafts is at http://datatracker.ietf.org/drafts/current/.
Internet-Drafts are draft documents valid for a maximum of six months
and may be updated, replaced, or obsoleted by other documents at any
time. It is inappropriate to use Internet-Drafts as reference
material or to cite them other than as "work in progress."
This Internet-Draft will expire on April 21, 2016.
Copyright Notice
Copyright (c) 2015 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
(http://trustee.ietf.org/license-info) in effect on the date of
publication of this document. Please review these documents
carefully, as 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 are provided without warranty as
described in the Simplified BSD License.
Perkins & Devarapalli Expires April 21, 2016 [Page 1]
Internet-Draft MN Identifier Types for RFC 4283 October 2015
Table of Contents
1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 2
2. New Mobile Node Identifier Types . . . . . . . . . . . . . . 2
3. Security Considerations . . . . . . . . . . . . . . . . . . . 4
4. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 5
5. References . . . . . . . . . . . . . . . . . . . . . . . . . 7
5.1. Normative References . . . . . . . . . . . . . . . . . . 7
5.2. Informative References . . . . . . . . . . . . . . . . . 7
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 8
1. Introduction
The Mobile Node Identifier Option for MIPv6 [RFC4283] has proved to
be a popular design tool for providing identifiers for mobile nodes
during authentication procedures with AAA protocols such as Diameter
[RFC3588]. To date, only a single type of identifier has been
specified, namely the MN NAI. Other types of identifiers are in
common use, and even referenced in RFC 4283. In this document, we
propose adding some basic types that are defined in various
telecommunications standards, including types for IMSI
[ThreeGPP-IDS], P-TMSI [ThreeGPP-IDS], IMEI [ThreeGPP-IDS], and GUTI
[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
The following types of identifiers are commonly used to identify
mobile nodes. For each type, references are provided with full
details on the format of the type of identifer.
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-SGTIN (Serialized Global Trade Item Number),
o RFID-SSCC (Serial Shipping Container),
o RFID-GLN (Global Location Number),
o RFID-GRAI (Global Returnable Asset Identifier),
o RFID-DOD (Department of Defense ID), and
o RFID-GIAI (Global Individual Asset Identifier).
Perkins & Devarapalli Expires April 21, 2016 [Page 2]
Internet-Draft MN Identifier Types for RFC 4283 October 2015
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
only a 96-bit scheme. Within each scheme, an EPC identifier can be
represented in a binary form or other forms such as URI.
The following list includes the above RFID types as well as various
other common identifiers and several different types of DUIDs.
Mobile Node Identifier Description
+----------------+---------------------------------+----------------+
| Identifier | Description | Reference |
| Type | | |
+----------------+---------------------------------+----------------+
| IPv6 Address | | [RFC2373] |
| IMSI | International Mobile Subscriber | [ThreeGPP-IDS] |
| | Identity | |
| P-TMSI | Packet-Temporary Mobile | [ThreeGPP-IDS] |
| | Subscriber Identity | |
| GUTI | Globally Unique Temporary ID | [ThreeGPP-IDS] |
| EUI-48 address | 48-bit Extended Unique | [IEEE802] |
| | Identifier | |
| EUI-64 address | 64-bit Extended Unique | [IEEE802] |
| | Identifier-64 bit | |
| DUID-LLT | DHCPv6 Unique Identifier: Link- | [RFC3315] |
| | Layer address plus timestamp | |
| DUID-EN | DHCPv6 Unique Identifier: | [RFC3315] |
| | Enterprise Number plus add'l | |
| | data | |
| DUID-LL | DHCPv6 Unique Identifier: Link- | [RFC3315] |
| | Layer address | |
| DUID-UUID | DHCPv6 Unique Identifier: other | [RFC6355] |
| | conformant format | |
| RFID-SGTIN-64 | 64-bit Serialized Global Trade | [EPC-Tag-Data] |
| | Item Number | |
| RFID-SSCC-64 | 64-bit Serial Shipping | [EPC-Tag-Data] |
| | Container | |
| RFID-GLN-64 | 64-bit Global Location Number | [EPC-Tag-Data] |
| RFID-GRAI-64 | 64-bit Global Returnable Asset | [EPC-Tag-Data] |
| | Identifier | |
| RFID-DOD-64 | 64-bit Department of Defense ID | [RFID-DoD-96] |
| 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 | |
Perkins & Devarapalli Expires April 21, 2016 [Page 3]
Internet-Draft MN Identifier Types for RFC 4283 October 2015
| 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
This document does not introduce any security mechanisms, and does
not have any impact on existing security mechanisms. Insofar as the
selection of a security association may be dependent on the exact
form of a mobile node identifier, additional specification may be
necessary when the new identifier types are employed with the general
AAA mechanisms for mobile node authorizations.
Some identifiers (e.g., IMSI) are considered to be private
information. If used in the MNID extension as defined in this
document, the packet including the MNID extension should be encrypted
so that personal information or trackable identifiers would not be
inadvertently disclosed to passive observers. Operators can
potentially apply IPsec Encapsulating Security Payload (ESP) with
confidentiality and integrity protection for protecting the location
information.
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-
Perkins & Devarapalli Expires April 21, 2016 [Page 4]
Internet-Draft MN Identifier Types for RFC 4283 October 2015
lived and temporary identifiers is outside the scope of this
document.
4. IANA Considerations
The new mobile node identifier types defined in the document should
be assigned values from the "Mobile Node Identifier Option Subtypes"
registry. The following values should be assigned.
Perkins & Devarapalli Expires April 21, 2016 [Page 5]
Internet-Draft MN Identifier Types for RFC 4283 October 2015
New Mobile Node Identifier Types
+-----------------+------------------------+
| Identifier Type | Identifier Type Number |
+-----------------+------------------------+
| IPv6 Address | 2 |
| IMSI | 3 |
| P-TMSI | 4 |
| EUI-48 address | 5 |
| EUI-64 address | 6 |
| GUTI | 7 |
| DUID-LLT | 8 |
| DUID-EN | 9 |
| DUID-LL | 10 |
| DUID-UUID | 11 |
| | 12-15 reserved |
| | 16 reserved |
| RFID-SGTIN-64 | 17 |
| RFID-SSCC-64 | 18 |
| RFID-GLN-64 | 19 |
| RFID-GRAI-64 | 20 |
| RFID-DOD-64 | 21 |
| RFID-GIAI-64 | 22 |
| | 23 reserved |
| RFID-GID-96 | 24 |
| RFID-SGTIN-96 | 25 |
| RFID-SSCC-96 | 26 |
| RFID-GLN-96 | 27 |
| RFID-GRAI-96 | 28 |
| RFID-DOD-96 | 29 |
| RFID-GIAI-96 | 30 |
| | 31 reserved |
| RFID-GID-URI | 32 |
| RFID-SGTIN-URI | 33 |
| RFID-SSCC-URI | 34 |
| RFID-GLN-URI | 35 |
| RFID-GRAI-URI | 36 |
| RFID-DOD-URI | 37 |
| RFID-GIAI-URI | 38 |
| | 39-255 reserved |
+-----------------+------------------------+
Table 2
See Section 2 for additional information about the identifier types.
Perkins & Devarapalli Expires April 21, 2016 [Page 6]
Internet-Draft MN Identifier Types for RFC 4283 October 2015
5. References
5.1. Normative References
[RFC2373] Hinden, R. and S. Deering, "IP Version 6 Addressing
Architecture", RFC 2373, DOI 10.17487/RFC2373, July 1998,
<http://www.rfc-editor.org/info/rfc2373>.
[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, <http://www.rfc-editor.org/info/rfc3315>.
[RFC4122] Leach, P., Mealling, M., and R. Salz, "A Universally
Unique IDentifier (UUID) URN Namespace", RFC 4122,
DOI 10.17487/RFC4122, July 2005,
<http://www.rfc-editor.org/info/rfc4122>.
[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,
<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>.
[RFC6355] Narten, T. and J. Johnson, "Definition of the UUID-Based
DHCPv6 Unique Identifier (DUID-UUID)", RFC 6355,
DOI 10.17487/RFC6355, August 2011,
<http://www.rfc-editor.org/info/rfc6355>.
5.2. Informative References
[EPC-Tag-Data]
EPCglobal Inc., , "EPC(TM) Generation 1 Tag Data Standards
Version 1.1 Rev.1.27
http://www.gs1.org/gsmp/kc/epcglobal/tds/
tds_1_1_rev_1_27-standard-20050510.pdf", January 2005.
[IEEE802] IEEE, , "IEEE Std 802: IEEE Standards for Local and
Metropolitan Networks: Overview and Architecture", 2001.
[RFC3588] Calhoun, P., Loughney, J., Guttman, E., Zorn, G., and J.
Arkko, "Diameter Base Protocol", RFC 3588,
DOI 10.17487/RFC3588, September 2003,
<http://www.rfc-editor.org/info/rfc3588>.
Perkins & Devarapalli Expires April 21, 2016 [Page 7]
Internet-Draft MN Identifier Types for RFC 4283 October 2015
[RFID-DoD-96]
Department of Defense, , "United States Department of
Defense Suppliers Passive RFID Information Guide (Version
15.0)", January 2010.
[ThreeGPP-IDS]
3rd Generation Partnership Project, , "3GPP Technical
Specification 23.003 V8.4.0: Technical Specification Group
Core Network and Terminals; Numbering, addressing and
identification (Release 8)", March 2009.
Authors' Addresses
Charles E. Perkins
Futurewei Inc.
2330 Central Expressway
Santa Clara, CA 95050
USA
Phone: +1-408-330-4586
Email: charliep@computer.org
Vijay Devarapalli
Vasona Networks
2900 Lakeside Drive, Suite 180
Santa Clara, CA 95054
USA
Perkins & Devarapalli Expires April 21, 2016 [Page 8]
