One document matched: draft-perkins-dmm-4283mnids-01.xml
<?xml version="1.0" encoding="US-ASCII"?>
<!DOCTYPE rfc SYSTEM "rfc2629.dtd">
<?xml-stylesheet type='text/xsl' href='rfc2629.xslt' ?>
<?rfc toc="yes"?>
<?rfc tocompact="yes"?>
<?rfc tocdepth="3"?>
<?rfc tocindent="yes"?>
<?rfc symrefs="yes"?>
<!-- use symbolic references tags, i.e, [RFC2119] instead of [1] -->
<?rfc sortrefs="yes" ?>
<!-- sort the reference entries alphabetically -->
<!-- control vertical white space
(using these PIs as follows is recommended by the RFC Editor) -->
<?rfc comments="yes"?>
<?rfc inline="yes"?>
<?rfc compact="yes" ?>
<!-- do not start each main section on a new page -->
<?rfc subcompact="yes" ?>
<!-- ?rfc subcompact="no" ? -->
<!-- keep one blank line between list items -->
<?rfc strict="yes" ?>
<!-- give errors regarding ID-nits and DTD validation -->
<!--
==================================== 80 ========================================
==================================== 72 ================================
-->
<rfc ipr="trust200902" docName='draft-perkins-dmm-4283mnids-01.txt' >
<front>
<title abbrev="MN Identifier Types for RFC 4283">
MN Identifier Types for RFC 4283 Mobile Node Identifier Option</title>
<author fullname="Charles E. Perkins" initials="C.E." surname="Perkins">
<organization abbrev="Futurewei">Futurewei Inc. </organization>
<address>
<postal>
<street>2330 Central Expressway</street>
<city>Santa Clara</city>
<code>95050</code>
<region>CA</region>
<country>USA</country>
</postal>
<phone>+1-408-330-4586</phone>
<email>charliep@computer.org</email>
</address>
</author>
<author initials="V." surname="Devarapalli" fullname="Vijay Devarapalli">
<organization>Vasona Networks</organization>
<address>
<postal>
<street>2900 Lakeside Drive, Suite 180</street>
<city>Santa Clara</city>
<region>CA 95054</region>
<country>USA</country>
</postal>
<!-- <email>vijay@vasonanetworks.com dvijay@gmail.com</email> -->
</address>
</author>
<date/> <!-- day="25" month="October" year="2010" /> -->
<area>Internet</area>
<workgroup>Distributed Mobility Management [dmm]</workgroup>
<keyword>Mobility</keyword>
<keyword>IPv6</keyword>
<keyword>Authentication</keyword>
<abstract>
<t>
Additional Identifier Types are proposed for use with
the Mobile Node Identifier Option for MIPv6 (RFC 4283).
</t>
</abstract>
</front>
<middle>
<section anchor='intro' title='Introduction'>
<t>
The Mobile Node Identifier Option for MIPv6
<xref target="RFC4283"/>
has proved to be a popular design tool for providing
identifiers for mobile nodes during authentication procedures
with AAA protocols such as Diameter <xref target="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 commonly in use in various
telecommunications standards, including the IMSI, P-TMSI,
IMEI, GUTI, and IEEE MAC-layer addresses. In addition, we
include the IPv6 address
itself as a legitimate mobile node identifier.
</t>
</section>
<section anchor='types'
title='New Mobile Node Identifier Types'>
<t>
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.
</t>
<t>
EPC supports several encoding systems or schemes including
<list style="symbols">
<t> RFID-GID (Global Identifier), </t>
<t> RFID-SGTIN (Serialized Global Trade Item Number), </t>
<t> RFID-SSCC (Serial Shipping Container), </t>
<t> RFID-GLN (Global Location Number), </t>
<t> RFID-GRAI (Global Returnable Asset Identifier), </t>
<t> RFID-DOD (Department of Defense) and </t>
<t> RFID-GIAI (Global Individual Asset Identifier). </t>
</list>
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.
</t>
<t>
The following list includes the above RFID types as well
as various other common identifiers and several different
types of DUIDs.
</t>
<t>
<list style="symbols">
<t> IPv6 Address <xref target="RFC2373"/> </t>
<t> IMSI <xref target="ThreeGPP-IDS"/> </t>
<t> P-TMSI <xref target="ThreeGPP-IDS"/> </t>
<t> GUTI <xref target="ThreeGPP-IDS"/> </t>
<t> EUI-48 address <xref target="IEEE802"/> </t>
<t> EUI-64 address <xref target="IEEE802"/> </t>
<t> DUID-LLT <xref target="RFC3315"/> </t>
<t> DUID-EN <xref target="RFC3315"/> </t>
<t> DUID-LL <xref target="RFC3315"/> </t>
<t> DUID-UUID <xref target="RFC6355"/> </t>
<t> 12-15 reserved </t>
<t> 16 reserved </t>
<t> RFID-SGTIN-64 <xref target="EPC-Tag-Data"/> </t>
<t> RFID-SSCC-64 <xref target="EPC-Tag-Data"/> </t>
<t> RFID-GLN-64 <xref target="EPC-Tag-Data"/> </t>
<t> RFID-GRAI-64 <xref target="EPC-Tag-Data"/> </t>
<t> RFID-DOD-64 <xref target="RFID-DoD-96"/> </t>
<t> RFID-GIAI-64 <xref target="EPC-Tag-Data"/> </t>
<t> 23 reserved </t>
<t> RFID-GID-96 <xref target="EPC-Tag-Data"/> </t>
<t> RFID-SGTIN-96 <xref target="EPC-Tag-Data"/> </t>
<t> RFID-SSCC-96 <xref target="EPC-Tag-Data"/> </t>
<t> RFID-GLN-96 <xref target="EPC-Tag-Data"/> </t>
<t> RFID-GRAI-96 <xref target="EPC-Tag-Data"/> </t>
<t> RFID-DOD-96 <xref target="RFID-DoD-96"/> </t>
<t> RFID-GIAI-96 <xref target="EPC-Tag-Data"/> </t>
<t> 31 reserved </t>
<t> RFID-GID-URI <xref target="EPC-Tag-Data"/> </t>
<t> RFID-SGTIN-URI <xref target="EPC-Tag-Data"/> </t>
<t> RFID-SSCC-URI <xref target="EPC-Tag-Data"/> </t>
<t> RFID-GLN-URI <xref target="EPC-Tag-Data"/> </t>
<t> RFID-GRAI-URI <xref target="EPC-Tag-Data"/> </t>
<t> RFID-DOD-URI <xref target="RFID-DoD-96"/> </t>
<t> RFID-GIAI-URI <xref target="EPC-Tag-Data"/> </t>
<t> 39-255 reserved </t>
<!--
http://www.gs1.org/gsmp/kc/epcglobal/tds/tds_1_1_rev_1_27-standard-20050510.pdf
-->
</list>
</t>
</section>
<section anchor='sec' title='Security Considerations'>
<t>
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.
</t>
<t>
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.
Moreover, MNIDs containing sensitive identifiers might
only be used for signaling during initial network entry.
Subsequent binding update exchanges would then rely on
a temporary identifier allocated during the initial
network entry.
</t>
</section>
<section anchor='iana' title='IANA Considerations'>
<t>
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.
</t>
<texttable anchor='mnids'>
<preamble>New Mobile Node Identifier Types</preamble>
<ttcol align='left'>Identifier Type</ttcol>
<ttcol align='left'>Identifier Type Number</ttcol>
<c> IPv6 Address </c> <c> 2 </c>
<c> IMSI </c> <c> 3 </c>
<c> P-TMSI </c> <c> 4 </c>
<c> EUI-48 address </c> <c> 5 </c>
<c> EUI-64 address </c> <c> 6 </c>
<c> GUTI </c> <c> 7 </c>
<c> DUID-LLT </c> <c> 8 </c>
<c> DUID-EN </c> <c> 9 </c>
<c> DUID-LL </c> <c> 10 </c>
<c> DUID-UUID </c> <c> 11 </c>
<c> </c> <c> 12-15 reserved </c>
<c> </c> <c> 16 reserved </c>
<c> RFID-SGTIN-64 </c> <c> 17 </c>
<c> RFID-SSCC-64 </c> <c> 18 </c>
<c> RFID-GLN-64 </c> <c> 19 </c>
<c> RFID-GRAI-64 </c> <c> 20 </c>
<c> RFID-DOD-64 </c> <c> 21 </c>
<c> RFID-GIAI-64 </c> <c> 22 </c>
<c> </c> <c> 23 reserved </c>
<c> RFID-GID-96 </c> <c> 24 </c>
<c> RFID-SGTIN-96 </c> <c> 25 </c>
<c> RFID-SSCC-96 </c> <c> 26 </c>
<c> RFID-GLN-96 </c> <c> 27 </c>
<c> RFID-GRAI-96 </c> <c> 28 </c>
<c> RFID-DOD-96 </c> <c> 29 </c>
<c> RFID-GIAI-96 </c> <c> 30 </c>
<c> </c> <c> 31 reserved </c>
<c> RFID-GID-URI </c> <c> 32 </c>
<c> RFID-SGTIN-URI </c> <c> 33 </c>
<c> RFID-SSCC-URI </c> <c> 34 </c>
<c> RFID-GLN-URI </c> <c> 35 </c>
<c> RFID-GRAI-URI </c> <c> 36 </c>
<c> RFID-DOD-URI </c> <c> 37 </c>
<c> RFID-GIAI-URI </c> <c> 38 </c>
<c> </c> <c> 39-255 reserved </c>
<!-- <postamble> example text </postamble> -->
</texttable>
<t>
See <xref target='types' /> for details about the identifer types.
</t>
<!-- <t> -->
<!-- <list style='hanging'> -->
<!-- <t hangText='IPv6 Address'> 2 </t> -->
<!-- <t hangText='IMSI'> 3 </t> -->
<!-- <t hangText='P-TMSI'> 4 </t> -->
<!-- <t hangText='EUI-48 address'> 5 </t> -->
<!-- <t hangText='EUI-64 address'> 6 </t> -->
<!-- <t hangText='GUTI'> 7 </t> -->
<!-- </list> -->
<!-- </t> -->
</section>
</middle>
<back>
<references title='Normative References'>
<?rfc include='reference.RFC.2373.xml'?>
<?rfc include='reference.RFC.3315.xml'?>
<?rfc include='reference.RFC.4122.xml'?>
<?rfc include='reference.RFC.4283.xml'?>
<?rfc include='reference.RFC.4285.xml'?>
<?rfc include='reference.RFC.6355.xml'?>
</references>
<references title="Informative References">
<?rfc include='reference.RFC.3588.xml'?>
<reference anchor="ThreeGPP-IDS">
<front>
<title>3GPP Technical Specification 23.003 V8.4.0: Technical
Specification Group Core Network and Terminals; Numbering,
addressing and identification (Release 8)</title>
<author surname="3rd Generation Partnership Project">
<organization>
</organization>
</author>
<date month="March" year="2009"/>
</front>
</reference>
<reference anchor="EPC-Tag-Data">
<front>
<title>
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
</title>
<author surname="EPCglobal Inc.">
<organization>
</organization>
</author>
<date day='10' month="January" year="2005"/>
</front>
</reference>
<reference anchor="RFID-DoD-96">
<front>
<title>United States Department of Defense Suppliers Passive RFID
Information Guide (Version 15.0)</title>
<author surname="Department of Defense">
<organization>
</organization>
</author>
<date month="January" year="2010"/>
</front>
</reference>
<reference anchor="IEEE802">
<front>
<title>IEEE Std 802: IEEE Standards for Local and
Metropolitan Networks: Overview and Architecture</title>
<author surname="IEEE">
<organization>
</organization>
</author>
<date year="2001"/>
</front>
</reference>
</references>
</back>
</rfc>
| PAFTECH AB 2003-2026 | 2026-04-24 01:20:36 |