MN Identifier Types for RFC 4283 Mobile Node Identifier Option
Futurewei Inc.
2330 Central Expressway
Santa Clara
95050
CA
USA
+1-408-330-4586
charliep@computer.org
Vasona Networks
2900 Lakeside Drive, Suite 180
Santa Clara
CA 95054
USA
dvijay@gmail.com
Internet
Distributed Mobility Management [dmm]
Mobility
IPv6
Authentication
Additional Identifier Type Numbers are defined for use with
the Mobile Node Identifier Option for MIPv6 (RFC 4283).
The Mobile Node Identifier Option for MIPv6
has proved to be a popular design tool for providing
identifiers for mobile nodes during authentication procedures
with AAA protocols such as Diameter .
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 ,
P-TMSI ,
IMEI ,
and GUTI . In addition, we
specify the IPv6 address itself and IEEE MAC-layer addresses
as mobile node identifiers.
Defining identifiers that are tied to the physical elements of the
device ( 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.
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 .
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.
Mobile Node Identifier Description
Identifier Type
Description
Reference
IPv6 Address
IMSI
International Mobile Subscriber Identity
P-TMSI
Packet-Temporary Mobile Subscriber Identity
GUTI
Globally Unique Temporary ID
EUI-48 address
48-bit Extended Unique Identifier
EUI-64 address
64-bit Extended Unique Identifier-64 bit
DUID
DHCPv6 Unique Identifier
In this section descriptions for the various MNID types are provided.
The IPv6 address is encoded as a 16 octet
string containing a full IPv6 address which has been assigned to the
mobile node. 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.
The International Mobile Subscriber Identity (IMSI)
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 (i.e., high-to-low
for all digits), where each digit occupies 4 bits. If needed for
full octet size, the last digit MUST be padded with 0xf. For example
an example IMSI 123456123456789 would be encoded as follows:
0x12, 0x34, 0x56, 0x12, 0x34, 0x56, 0x78, 0x9f
The IEEE EUI-48 address is encoded
as 6 octets containing the IEEE EUI-48 address.
The IEEE EUI-64 address is encoded
as 8 octets containing the full IEEE EUI-64 address.
The DUID is the DHCPv6 Unique Identifier (DUID)
. There are various types of DUID, which are
distinguished by an initial two-octet type field. Clients and servers
MUST treat DUIDs as opaque values and MUST only compare DUIDs for
equality.
This document does not introduce any security mechanisms,
and does not have any impact on existing security mechanisms.
Mobile Node Identifiers such as those described in this document are
considered to be private information. If used in the MNID extension
as defined in , the packet including the MNID
extension MUST be
encrypted so that no personal information or trackable identifiers
is inadvertently disclosed to passive observers.
Operators can potentially apply IPsec Encapsulating Security Payload
(ESP) , in transport mode, with confidentiality
and integrity protection for protecting the identity and location
information in Mobile IPv6 signaling messages.
Some MNIDs contain sensitive identifiers which, as used in
protocols specified by other SDOs, are only used for signaling
during initial network entry. In such protocols, subsequent
exchanges then rely on a temporary identifier allocated during the
initial network entry. Managing the association between
long-lived and temporary identifiers is outside the scope
of this document.
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.
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-255 unassigned
See for additional information
about the identifier types.
Future new assignments are to be made only after Expert Review
.
The expert must ascertain that the identifier type allows unique
identification of the mobile device; since all MNIDs require
encryption there is no additional privacy exposure attendent to
the use of new types.
The authors wish to acknowledge Hakima Chaouchi, Tatuya Jinmei,
Jouni Korhonen, Sri Gundavelli, Suresh Krishnan, Dapeng Liu,
Dale Worley, Joseph Salowey,
Linda Dunbar, and Mirja Kuehlewind for their helpful comments.
3GPP Technical Specification 23.003 V8.4.0: Technical
Specification Group Core Network and Terminals; Numbering,
addressing and identification (Release 8)
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
United States Department of Defense Suppliers Passive RFID
Information Guide (Version 15.0)
IEEE Std 802: IEEE Standards for Local and
Metropolitan Networks: Overview and Architecture
Guidelines for 48-Bit Global Identifier (EUI-48) https://standards.ieee.org/develop/regauth/tut/eui48.pdf
Guidelines for 64-Bit Global Identifier (EUI-64) https://standards.ieee.org/develop/regauth/tut/eui.pdf64
General EAN.UCC Specifications Version 5.0
The Tag Data standard promoted by Electronic Product Code(TM)
(abbreviated EPC) supports several
encoding systems or schemes, which are commonly used in RFID
(radio-frequency identification) applications, including
RFID-GID (Global Identifier),
RFID-SGTIN (Serialized Global Trade Item Number),
RFID-SSCC (Serial Shipping Container),
RFID-SGLN (Global Location Number),
RFID-GRAI (Global Returnable Asset Identifier),
RFID-DOD (Department of Defense ID), and
RFID-GIAI (Global Individual Asset Identifier).
For each RFID scheme except GID, there are three representations:
a 64-bit binary representation (for example, SGLN-64)
(except for GID)
a 96-bit binary representation (SGLN-96)
a representation as a URI
The URI representation for the RFID is actually a URN.
The EPC document has the following language:
All categories of URIs are represented as Uniform Reference Names
(URNs) as defined by [RFC2141], where the URN Namespace is epc.
The following list includes the above RFID types.
Mobile Node RFID Identifier Description
Identifier Type
Description
Reference
RFID-SGTIN-64
64-bit Serialized Global Trade Item Number
RFID-SSCC-64
64-bit Serial Shipping Container
RFID-SGLN-64
64-bit Serialized Global Location Number
RFID-GRAI-64
64-bit Global Returnable Asset Identifier
RFID-DOD-64
64-bit Department of Defense ID
RFID-GIAI-64
64-bit Global Individual Asset Identifier
RFID-GID-96
96-bit Global Identifier
RFID-SGTIN-96
96-bit Serialized Global Trade Item Number
RFID-SSCC-96
96-bit Serial Shipping Container
RFID-SGLN-96
96-bit Serialized Global Location Number
RFID-GRAI-96
96-bit Global Returnable Asset Identifier
RFID-DOD-96
96-bit Department of Defense ID
RFID-GIAI-96
96-bit Global Individual Asset Identifier
RFID-GID-URI
Global Identifier represented as URI
RFID-SGTIN-URI
Serialized Global Trade Item Number represented as URI
RFID-SSCC-URI
Serial Shipping Container represented as URI
RFID-SGLN-URI
Global Location Number represented as URI
RFID-GRAI-URI
Global Returnable Asset Identifier represented as URI
RFID-DOD-URI
Department of Defense ID represented as URI
RFID-GIAI-URI
Global Individual Asset Identifier represented as URI
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
. 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 (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.
The RFID-SGTIN-64 is encoded as specified in
.
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.
The RFID-SGTIN-96 is encoded as specified in
.
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.
The RFID-SSCC-64 is encoded as specified in
.
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.
The RFID-SSCC-96 is encoded as specified in
.
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.
The RFID-SGLN-64 type is encoded as specified in
.
The SGLN-64 includes five fields: Header, Filter Value,
Company Prefix Index, Location Reference, and Serial Number.
The RFID-SGLN-96 type is encoded as specified in
.
The SGLN-96 includes six fields: Header, Filter Value,
Partition, Company Prefix, Location Reference, and Serial Number.
The RFID-GRAI-64 type is encoded as specified in
.
The GRAI-64 includes five fields: Header, Filter Value,
Company Prefix Index, Asset Type, and Serial Number.
The RFID-GRAI-96 type is encoded as specified in
.
The GRAI-96 includes six fields: Header, Filter Value,
Partition, Company Prefix, Asset Type, and Serial Number.
The RFID-GIAI-64 type is encoded as specified in
.
The GIAI-64 includes four fields: Header, Filter Value,
Company Prefix Index, and Individual Asset Reference.
The RFID-GIAI-96 type is encoded as specified in
.
The GIAI-96 includes five fields: Header, Filter Value,
Partition, Company Prefix, and Individual Asset Reference.
The RFID-DoD-64 type is encoded as specified in
.
The DoD-64 type includes four fields: Header, Filter Value,
Government Managed Identifier, and Serial Number.
The RFID-DoD-96 type is encoded as specified in
.
The DoD-96 type includes four fields: Header, Filter Value,
Government Managed Identifier, and Serial Number.
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 .