draft-ietf-dmm-4283mnids-03.txt   draft-ietf-dmm-4283mnids-04.txt 
Distributed Mobility Management [dmm] C. Perkins Distributed Mobility Management [dmm] C. Perkins
Internet-Draft Futurewei Internet-Draft Futurewei
Intended status: Standards Track V. Devarapalli Intended status: Standards Track V. Devarapalli
Expires: May 17, 2017 Vasona Networks Expires: July 21, 2017 Vasona Networks
November 13, 2016 January 17, 2017
MN Identifier Types for RFC 4283 Mobile Node Identifier Option MN Identifier Types for RFC 4283 Mobile Node Identifier Option
draft-ietf-dmm-4283mnids-03.txt draft-ietf-dmm-4283mnids-04.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 May 17, 2017. This Internet-Draft will expire on July 21, 2017.
Copyright Notice Copyright Notice
Copyright (c) 2016 IETF Trust and the persons identified as the Copyright (c) 2017 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
skipping to change at page 2, line 15 skipping to change at page 2, line 15
Table of Contents Table of Contents
1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 2 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 2
2. Terminology . . . . . . . . . . . . . . . . . . . . . . . . . 3 2. Terminology . . . . . . . . . . . . . . . . . . . . . . . . . 3
3. New Mobile Node Identifier Types . . . . . . . . . . . . . . 3 3. New Mobile Node Identifier Types . . . . . . . . . . . . . . 3
4. Descriptions of MNID types . . . . . . . . . . . . . . . . . 5 4. Descriptions of MNID types . . . . . . . . . . . . . . . . . 5
4.1. Description of the IPv6 address type . . . . . . . . . . 5 4.1. Description of the IPv6 address type . . . . . . . . . . 5
4.2. Description of the IMSI MNID type . . . . . . . . . . . . 5 4.2. Description of the IMSI MNID type . . . . . . . . . . . . 5
4.3. Description of the EUI-48 address type . . . . . . . . . 5 4.3. Description of the EUI-48 address type . . . . . . . . . 5
4.4. Description of the EUI-64 address type . . . . . . . . . 5 4.4. Description of the EUI-64 address type . . . . . . . . . 5
4.5. Description of the DUID-LLT type . . . . . . . . . . . . 5 4.5. Description of the DUID-LLT type . . . . . . . . . . . . 6
4.6. Description of the DUID-EN type . . . . . . . . . . . . . 6 4.6. Description of the DUID-EN type . . . . . . . . . . . . . 6
4.7. Description of the DUID-LL type . . . . . . . . . . . . . 6 4.7. Description of the DUID-LL type . . . . . . . . . . . . . 6
4.8. Description of the DUID-UUID type . . . . . . . . . . . . 6 4.8. Description of the DUID-UUID type . . . . . . . . . . . . 6
4.9. Description of the RFID types . . . . . . . . . . . . . . 6 4.9. Description of the RFID types . . . . . . . . . . . . . . 7
4.9.1. Description of the RFID-SGTIN-64 type . . . . . . . . 7 4.9.1. Description of the RFID-SGTIN-64 type . . . . . . . . 8
4.9.2. Description of the RFID-SGTIN-96 type . . . . . . . . 8 4.9.2. Description of the RFID-SGTIN-96 type . . . . . . . . 8
4.9.3. Description of the RFID-SSCC-64 type . . . . . . . . 8 4.9.3. Description of the RFID-SSCC-64 type . . . . . . . . 8
4.9.4. Description of the RFID-SSCC-96 type . . . . . . . . 8 4.9.4. Description of the RFID-SSCC-96 type . . . . . . . . 8
4.9.5. Description of the RFID-SGLN-64 type . . . . . . . . 8 4.9.5. Description of the RFID-SGLN-64 type . . . . . . . . 8
4.9.6. Description of the RFID-SGLN-96 type . . . . . . . . 8 4.9.6. Description of the RFID-SGLN-96 type . . . . . . . . 8
4.9.7. Description of the RFID-GRAI-64 type . . . . . . . . 8 4.9.7. Description of the RFID-GRAI-64 type . . . . . . . . 9
4.9.8. Description of the RFID-GRAI-96 type . . . . . . . . 8 4.9.8. Description of the RFID-GRAI-96 type . . . . . . . . 9
4.9.9. Description of the RFID-GIAI-64 type . . . . . . . . 9 4.9.9. Description of the RFID-GIAI-64 type . . . . . . . . 9
4.9.10. Description of the RFID-GIAI-96 type . . . . . . . . 9 4.9.10. Description of the RFID-GIAI-96 type . . . . . . . . 9
4.9.11. Description of the RFID-DoD-64 type . . . . . . . . . 9 4.9.11. Description of the RFID-DoD-64 type . . . . . . . . . 9
4.9.12. Description of the RFID-DoD-96 type . . . . . . . . . 9 4.9.12. Description of the RFID-DoD-96 type . . . . . . . . . 9
4.9.13. Description of the RFID URI types . . . . . . . . . . 9 4.9.13. Description of the RFID URI types . . . . . . . . . . 9
5. Security Considerations . . . . . . . . . . . . . . . . . . . 9 5. Security Considerations . . . . . . . . . . . . . . . . . . . 10
6. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 10 6. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 10
7. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 12 7. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 12
8. References . . . . . . . . . . . . . . . . . . . . . . . . . 12 8. References . . . . . . . . . . . . . . . . . . . . . . . . . 12
8.1. Normative References . . . . . . . . . . . . . . . . . . 12 8.1. Normative References . . . . . . . . . . . . . . . . . . 12
8.2. Informative 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
skipping to change at page 5, line 24 skipping to change at page 5, line 24
Table 1 Table 1
4. 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.
4.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. The IPv6 address MUST be a unicast routable
IPv6 address. Multicast addresses, link-local addresses, and the
unspecified IPv6 address MUST NOT be used. IPv6 Unique Local
Addresses (ULAs) MAY be used, as long as any security operations
making use of the ULA also take into account the domain in which the
ULA is guaranteed to be unique.
4.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:
skipping to change at page 6, line 10 skipping to change at page 6, line 16
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 the DUID-LLT is of variable length.
4.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
skipping to change at page 7, line 29 skipping to change at page 7, line 38
schemes are specified, SSCC-64 (64 bits) and SSCC-96 (96 bits). schemes are specified, SSCC-64 (64 bits) and SSCC-96 (96 bits).
The Global Location Number (GLN) is defined by the EAN.UCC The Global Location Number (GLN) is defined by the EAN.UCC
Specifications. A GLN can represent either a discrete, unique Specifications. A GLN can represent either a discrete, unique
physical location such as a warehouse slot, or an aggregate physical physical location such as a warehouse slot, or an aggregate physical
location such as an entire warehouse. In addition, a GLN can location such as an entire warehouse. In addition, a GLN can
represent a logical entity that performs a business function such as represent a logical entity that performs a business function such as
placing an order. The Serialized Global Location Number (SGLN) placing an order. The Serialized Global Location Number (SGLN)
includes the Company Prefix, Location Reference, and Serial Number. includes the Company Prefix, Location Reference, and Serial Number.
The Global Returnable Asset Identifier is (GRAI) is defined by the The Global Returnable Asset Identifier (GRAI) is defined by the
General EAN.UCC Specifications. Unlike the GTIN, the GRAI is already General EAN.UCC Specifications. Unlike the GTIN, the GRAI 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, Asset Type, and Serial Number. GRAI includes the Company Prefix, Asset Type, and Serial Number.
The Global Individual Asset Identifier (GIAI) is defined by the The Global Individual Asset Identifier (GIAI) is defined by the
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.
skipping to change at page 10, line 10 skipping to change at page 10, line 21
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. Operators can inadvertently disclosed to passive observers. Operators can
potentially apply IPsec Encapsulating Security Payload (ESP) with potentially apply IPsec Encapsulating Security Payload (ESP)
confidentiality and integrity protection for protecting the location [RFC4303], with confidentiality and integrity protection for
information. protecting the location 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.
6. IANA Considerations 6. IANA Considerations
skipping to change at page 12, line 7 skipping to change at page 12, line 7
| RFID-GIAI-URI | 38 | | RFID-GIAI-URI | 38 |
| | 39-255 reserved | | | 39-255 reserved |
+-----------------+------------------------+ +-----------------+------------------------+
Table 2 Table 2
See Section 4 for additional information about the identifier types. See Section 4 for additional information about the identifier types.
7. Acknowledgements 7. Acknowledgements
The authors wish to acknowledge Hakima Chaouchi, Jouni Korhonen and The authors wish to acknowledge Hakima Chaouchi, Tatuya Jinmei, Jouni
Sri Gundavelli for their helpful comments. Korhonen and Sri Gundavelli for their helpful comments.
8. References 8. References
8.1. Normative References 8.1. Normative References
[RFC2119] Bradner, S., "Key words for use in RFCs to Indicate [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate
Requirement Levels", BCP 14, RFC 2119, Requirement Levels", BCP 14, RFC 2119,
DOI 10.17487/RFC2119, March 1997, DOI 10.17487/RFC2119, March 1997,
<http://www.rfc-editor.org/info/rfc2119>. <http://www.rfc-editor.org/info/rfc2119>.
[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>.
[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>.
[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>.
[RFC4303] Kent, S., "IP Encapsulating Security Payload (ESP)",
RFC 4303, DOI 10.17487/RFC4303, December 2005,
<http://www.rfc-editor.org/info/rfc4303>.
[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>.
8.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.
 End of changes. 15 change blocks. 
23 lines changed or deleted 28 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/