One document matched: draft-perkins-mext-4283mnids-00.xml

<?xml version="1.0"?>
<!DOCTYPE rfc SYSTEM "rfc2629.dtd">
<?rfc toc="no"?>
<!-- rfc ipr="pre5378Trust200902" docName='draft-perkins-mip4-authreq-00.txt'-->
<rfc ipr="trust200811" docName='draft-perkins-mext-4283mnids-00.txt' >
<?rfc symrefs="no"?>
<front>

<title abbrev="MN Identifier Types for RFC 4283">
	MN Identifier Types for RFC 4283 Mobile Node Identifier Option</title>

    <author initials="C." surname="Perkins" fullname="Charles E. Perkins">
       <organization>WiChorus Inc.</organization>
      <address>
        <postal>
          <street>3590 North, 1st Street, Suite 300</street>
          <city>San Jose</city>
          <region>CA 95134</region>
          <country>USA</country>
        </postal>
        <email>charliep@computer.org</email>
      </address>
    </author>

    <author initials="V." surname="Devarapalli" fullname="Vijay Devarapalli">
       <organization>WiChorus Inc.</organization>
      <address>
        <postal>
          <street>3590 North, 1st Street, Suite 300</street>
          <city>San Jose</city>
          <region>CA 95134</region>
          <country>USA</country>
        </postal>
        <email>vijay@wichorus.com</email>
      </address>
    </author>

<date month="October" year="2009" />

  <area>Internet</area>
  <workgroup>Mobility Extensions for IPv6 [mext]</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 itself.  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>
   <list style="symbols">
   <t> IPv6 Address <xref target="RFC2373"/> </t>
   <t> IMSI <xref target="3GPP-IDS"/> </t>
   <t> P-TMSI <xref target="3GPP-IDS"/> </t>
   <t> EUI-48 address <xref target="IEEE802"/> </t>
   <t> EUI-64 address <xref target="IEEE802"/> </t>
   <t> GUTI <xref target="3GPP-IDS"/> </t>
   </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>

</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>
	<!-- <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.4283.xml'?>
<?rfc include='reference.RFC.4285.xml'?>
</references>
<references title="Informative References">
<?rfc include='reference.RFC.3588.xml'?>
<reference anchor="3GPP-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="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>