<pre>Network  Working Group                                         P. Calhoun
Request for Comments: 2794                  Sun Microsystems Laboratories
Updates: <a href="./rfc2290">2290</a>                                                  C. Perkins
Category: Standards Track                           Nokia Research Center
                                                               March 2000


         <span class="h1">Mobile IP Network Access Identifier Extension for IPv4</span>

Status of this Memo

   This document specifies an Internet standards track protocol for the
   Internet community, and requests discussion and suggestions for
   improvements.  Please refer to the current edition of the "Internet
   Official Protocol Standards" (STD 1) for the standardization state
   and status of this protocol.  Distribution of this memo is unlimited.

Copyright Notice

   Copyright (C) The Internet Society (2000).  All Rights Reserved.

Abstract

   AAA servers are in use within the Internet today to provide
   authentication and authorization services for dial-up computers.
   Such services are likely to be equally valuable for mobile nodes
   using Mobile IP when the nodes are attempting to connect to foreign
   domains with AAA servers.  AAA servers today identify clients by
   using the Network Access Identifier (NAI). Our proposal defines a way
   for the mobile node to identify itself, by including the NAI along
   with the Mobile IP Registration Request.  This memo also updates <a href="./rfc2290">RFC</a>
   <a href="./rfc2290">2290</a> which specifies the Mobile-IPv4 Configuration option for IPCP,
   by allowing the Mobile Node's Home Address field of this option to be
   zero.

















<span class="grey">Calhoun &amp; Perkins           Standards Track                     [Page 1]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-2" ></span>
<span class="grey"><a href="./rfc2794">RFC 2794</a>                    Mobile Node NAI                   March 2000</span>


<span class="h2"><a class="selflink" id="section-1" href="#section-1">1</a>. Introduction</span>

   AAA servers are in use within the Internet today to provide
   authentication and authorization services for dial-up computers.
   Such services are likely to be equally valuable for mobile nodes
   using Mobile IP when the nodes are attempting to connect to foreign
   domains with AAA servers.  AAA servers today identify clients by
   using the Network Access Identifier (NAI) [<a href="#ref-1" title="&quot;The Network Access Identifier&quot;">1</a>].  This document
   specifies the Mobile Node NAI extension to the Mobile IP Registration
   Request [<a href="#ref-7" title="&quot;IP Mobility Support&quot;">7</a>] message from the mobile node.

   Since the NAI is typically used to uniquely identify the mobile node,
   the mobile node's home address is not always necessary to provide
   that function.  Thus, it is possible for a mobile node to
   authenticate itself, and be authorized for connection to the foreign
   domain, without even having a home address.  A message containing the
   Mobile Node NAI extension MAY set the Home Address field to zero (0)
   in the Registration Request, to request that a home address be
   assigned.

   The "Mobile-IPv4 Configuration" option to IPCP has been specified in
   <a href="./rfc2290">RFC 2290</a> [<a href="#ref-8" title="&quot;Mobile-IPv4 Configuration Option for PPP IPCP&quot;">8</a>] for proper interaction between a mobile node and a peer,
   through which the mobile node connects to the network using PPP.
   According to that specification the Mobile Node's Home Address field
   of the option MUST not be zero.  However, in the context of this memo
   which allows a mobile node to be identified by its NAI and to obtain
   an address after the PPP phase of connection establishment, the Home
   Address field is allowed to be zero while maintaining all other
   aspects of <a href="./rfc2290">RFC 2290</a>.  Interpretation of various scenarios from <a href="./rfc2290">RFC</a>
   <a href="./rfc2290">2290</a> is given in <a href="#section-4">section 4</a>.

   The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
   "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this
   document are to be interpreted as described in [<a href="#ref-3" title="&quot;Key words for use in RFCs to Indicate Requirement Levels&quot;">3</a>].

<span class="h2"><a class="selflink" id="section-2" href="#section-2">2</a>. Mobile Node NAI Extension</span>

   The Mobile Node NAI extension, shown in figure 1, contains the user
   name following the format defined in [<a href="#ref-1" title="&quot;The Network Access Identifier&quot;">1</a>].  When it is present in the
   Registration Request, the Home Address field MAY be set to zero (0).
   The Mobile Node NAI extension MUST appear in the Registration Request
   before both the Mobile-Home Authentication extension and Mobile-
   Foreign Authentication extension, if present.








<span class="grey">Calhoun &amp; Perkins           Standards Track                     [Page 2]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-3" ></span>
<span class="grey"><a href="./rfc2794">RFC 2794</a>                    Mobile Node NAI                   March 2000</span>


       0                   1                   2                   3
       0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
      +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
      |     Type      |    Length     |           MN-NAI ...
      +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+

                Figure 1: The Mobile Node NAI Extension


      Type       131 (skippable) [<a href="#ref-7" title="&quot;IP Mobility Support&quot;">7</a>]

      Length     The length in bytes of the MN-NAI field

      MN-NAI     A string in the NAI format defined in [<a href="#ref-1" title="&quot;The Network Access Identifier&quot;">1</a>].

<span class="h2"><a class="selflink" id="section-3" href="#section-3">3</a>. Foreign Agent Considerations</span>

   If Home Address is zero in the Registration Request, the foreign
   agent MUST use the NAI instead in its pending registration request
   records, along with the Identification field as usual.  If the
   foreign agent cannot manage pending registration request records in
   this way, it MUST return a Registration Reply with Code indicating
   NONZERO_HOMEADDR_REQD (see <a href="#section-5">section 5</a>).

   If the mobile node includes the Mobile Node NAI extension in its
   Registration Request, then the Registration Reply from the home agent
   MUST include the Mobile Node NAI extension.  If not, the foreign
   agent SHOULD send the Registration Reply to the mobile node, changing
   the Code to the value MISSING_NAI (see <a href="#section-5">section 5</a>).  The Registration
   Reply MUST include a nonzero Home Agent address and mobile node's
   Home Address.  If not, the foreign agent SHOULD send the Registration
   Reply to the mobile node, changing the Code to the value
   MISSING_HOME_AGENT or MISSING_HOMEADDR, respectively (see <a href="#section-5">section 5</a>).

<span class="h2"><a class="selflink" id="section-4" href="#section-4">4</a>. Interactions with Mobile-IPv4 Configuration Option to IPCP</span>

   In the Mobile-IPv4 Configuration Option to IPCP [<a href="#ref-8" title="&quot;Mobile-IPv4 Configuration Option for PPP IPCP&quot;">8</a>], the Mobile
   Node's Home Address field may be zero.  In this section, we specify
   the action to be taken in that case, when the mobile node is using
   the Mobile Node NAI extension in the Mobile IP Registration Request.
   Whether or not the IP Address Configuration Option contains a nonzero
   IP address, the mobile node will subsequently attempt to obtain a
   home address from the Mobile IP Registration Reply.

   If the IP Address Configuration Option to IPCP has IP address equal
   to zero, the PPP peer is expected to allocate and assign a co-located
   care-of address to the Mobile Node.  If, on the other hand, the IP




<span class="grey">Calhoun &amp; Perkins           Standards Track                     [Page 3]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-4" ></span>
<span class="grey"><a href="./rfc2794">RFC 2794</a>                    Mobile Node NAI                   March 2000</span>


   Address Configuration Option to IPCP has a nonzero IP address, the
   PPP peer is expected to assign that address to the Mobile Node as its
   co-located care-of address.

   Finally, if the IP Address Configuration Option is left out of the
   IPCP Configure-Request, then no co-located care of address is
   assigned during IPCP. The mobile node will acquire a co-located care
   of address during a later stage of configuration or will use an FA-
   located care-of address.

<span class="h2"><a class="selflink" id="section-5" href="#section-5">5</a>. Error Values</span>

   Each entry in the following table contains the name and value for the
   Code [<a href="#ref-7" title="&quot;IP Mobility Support&quot;">7</a>] to be returned in a Registration Reply, and the section in
   which the error Code is first mentioned in this specification.

      Error Name               Value   Section of Document
      ----------------------   -----   -------------------
      NONZERO_HOMEADDR_REQD    96      3
      MISSING_NAI              97      3
      MISSING_HOME_AGENT       98      3
      MISSING_HOMEADDR         99      3

<span class="h2"><a class="selflink" id="section-6" href="#section-6">6</a>. IANA Considerations</span>

   The Mobile Node NAI extension defined in <a href="#section-2">Section 2</a> is a Mobile IP
   registration extension as defined in <a href="./rfc2002">RFC 2002</a> [<a href="#ref-7" title="&quot;IP Mobility Support&quot;">7</a>] and extended in <a href="./rfc2356">RFC</a>
   <a href="./rfc2356">2356</a> [<a href="#ref-6" title="&quot;Sun's SKIP Firewall Traversal for Mobile IP&quot;">6</a>].  IANA should assign a value of 131 for this purpose.

   The Code values defined in <a href="#section-5">Section 5</a> are error codes as defined in
   <a href="./rfc2002">RFC 2002</a> and extended in <a href="./rfc2344">RFC 2344</a> [<a href="#ref-5" title="&quot;Reverse Tunneling for Mobile IP&quot;">5</a>] and <a href="./rfc2356">RFC 2356</a> [<a href="#ref-6" title="&quot;Sun's SKIP Firewall Traversal for Mobile IP&quot;">6</a>].  They
   correspond to error values conventionally associated with rejection
   by the foreign agent (i.e., values from the range 64-127).  IANA
   should record the values as defined in <a href="#section-5">Section 5</a>.

<span class="h2"><a class="selflink" id="section-7" href="#section-7">7</a>. Security Considerations</span>

   Mobile IP registration messages are authenticated, and the
   authentication verified by the recipient.  This proposal does not
   prohibit the mobile node from sending its NAI in the clear over the
   network, but that is not expected to be a security issue.

<span class="h2"><a class="selflink" id="section-8" href="#section-8">8</a>. IPv6 Considerations</span>

   Supporting NAI-based registrations for Mobile IPv6 [<a href="#ref-4" title="&quot;Mobility Support in IPv6&quot;">4</a>] is outside the
   scope of this document.  This section contains some ideas how
   Stateless Address Autoconfiguration [<a href="#ref-9" title="&quot;IPv6 Stateless Address Autoconfiguration&quot;">9</a>] and DHCPv6 [<a href="#ref-2" title="&quot;Dynamic Host Configuration Protocol for IPv6 (DHCPv6)&quot;">2</a>] might be
   extended to support NAI-based Mobile IPv6 registrations.



<span class="grey">Calhoun &amp; Perkins           Standards Track                     [Page 4]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-5" ></span>
<span class="grey"><a href="./rfc2794">RFC 2794</a>                    Mobile Node NAI                   March 2000</span>


   For mobile nodes using IPv6, there are no commonly deployed
   mechanisms by which a mobile node may present its credentials, such
   as exist today with IPv4.  Nevertheless, a mobile node using IPv6
   mobility may wish to specify the domain in which their credentials
   may be checked, by using a NAI just as this specification proposes
   for IPv4.  In the case of IPv6, however, there is no foreign agent in
   place to manage the connectivity of the mobile node, and thus to
   manage the verification of the credentials offered by the mobile
   node.  To identify the HDAF (see <a href="#appendix-A">appendix A</a>) that has the expected
   relationship with the mobile node, the NAI would have to be forwarded
   to a local AAA by the local agent involved with configuring the
   care-of address of the mobile node.

   This agent can either be a router sending out Router Advertisements
   [<a href="#ref-9" title="&quot;IPv6 Stateless Address Autoconfiguration&quot;">9</a>], or a DHCPv6 server.  In the former case, the router could signal
   its ability to handle the NAI by attaching some yet to be defined
   option to the Router Advertisement.  In the latter case, for managed
   links, the mobile node could include a yet to be defined NAI
   extension in its DHCP Solicitation message.  Such an NAI extension
   and appropriate authentication would also be required on the
   subsequent DHCP Request sent by the mobile node to the DHCP Server
   selected on the basis of received DHCP Advertisements.  Once a care-
   of address on the foreign network has been obtained, the mobile node
   can use regular MIPv6 [<a href="#ref-4" title="&quot;Mobility Support in IPv6&quot;">4</a>].

<span class="h2"><a class="selflink" id="section-9" href="#section-9">9</a>. Acknowledgements</span>

   The authors would like to thank Gabriel Montenegro and Vipul Gupta
   for their useful discussions.  Thanks to Basaravaj Patil and Pete
   McCann for text describing actions to be taken when the home address
   is zero but the mobile node wishes to use the Mobile-IPv4
   Configuration Option to IPCP defined in <a href="./rfc2290">RFC 2290</a>.

References

   [<a id="ref-1">1</a>] Aboba, B. and M. Beadles, "The Network Access Identifier", <a href="./rfc2486">RFC</a>
       <a href="./rfc2486">2486</a>, January 1999.

   [<a id="ref-2">2</a>] Bound, J. and C. Perkins, "Dynamic Host Configuration Protocol
       for IPv6 (DHCPv6)", Work in Progress.

   [<a id="ref-3">3</a>] Bradner, S., "Key words for use in RFCs to Indicate Requirement
       Levels", <a href="https://www.rfc-editor.org/bcp/bcp14">BCP 14</a>, <a href="./rfc2119">RFC 2119</a>, March 1997.

   [<a id="ref-4">4</a>] Johnson, D. and C. Perkins <a style="text-decoration: none" href='https://www.google.com/search?sitesearch=datatracker.ietf.org%2Fdoc%2Fhtml%2F&amp;q=inurl:draft-+%22Mobility+Support+in+IPv6%22'>"Mobility Support in IPv6"</a>, Work in
       Progress.





<span class="grey">Calhoun &amp; Perkins           Standards Track                     [Page 5]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-6" ></span>
<span class="grey"><a href="./rfc2794">RFC 2794</a>                    Mobile Node NAI                   March 2000</span>


   [<a id="ref-5">5</a>] Montenegro, G., "Reverse Tunneling for Mobile IP", <a href="./rfc2344">RFC 2344</a>, May
       1998.

   [<a id="ref-6">6</a>] Montenegro, G. and V. Gupta, "Sun's SKIP Firewall Traversal for
       Mobile IP", <a href="./rfc2356">RFC 2356</a>, June 1998.

   [<a id="ref-7">7</a>] Perkins, C., "IP Mobility Support", <a href="./rfc2002">RFC 2002</a>, October 1996.

   [<a id="ref-8">8</a>] Solomon, J. and S. Glass, "Mobile-IPv4 Configuration Option for
       PPP IPCP", <a href="./rfc2290">RFC 2290</a>, February 1998.

   [<a id="ref-9">9</a>] Thomson, S. and T. Narten, "IPv6 Stateless Address
       Autoconfiguration", <a href="./rfc2462">RFC 2462</a>, December 1998.






































<span class="grey">Calhoun &amp; Perkins           Standards Track                     [Page 6]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-7" ></span>
<span class="grey"><a href="./rfc2794">RFC 2794</a>                    Mobile Node NAI                   March 2000</span>


<span class="h2"><a class="selflink" id="appendix-A" href="#appendix-A">A</a>. Home Domain Allocation Function (HDAF)</span>

   This appendix introduces a new function named the Home Domain
   Allocation Function (HDAF) that can dynamically assign a Home Address
   to the mobile node.

   Figure 2 illustrates the Home HDAF, which receives messages from
   foreign agents (e.g., FA) and assigns a Home Address within the Home
   Domain.  The HDAF does not perform any Mobile IP processing on the
   Registration Request, but simply forwards the request to a Home Agent
   (HA) within the network that is able to handle the request.

                                                     +------+
                                                     |      |
                                                 +---+ HA-1 |
        +------+       +------+       +------+   |   |      |
        |      |       |      |       |      |   |   +------+
        |  MN  |-------|  FA  |-------| HDAF +---+     ...
        |      |       |      |       |      |   |   +------+
        +------+       +------+       +------+   |   |      |
                                                 +---+ HA-n |
                                                     |      |
                                                     +------+

            Figure 2: Home Domain Allocator Function (HDAF)

   Upon receipt of the Registration Request from the mobile node (MN),
   FA extracts the NAI and finds the domain name associated with it.  FA
   then finds the HDAF that handles requests for the mobile node's
   domain.  The discovery protocol is outside of the scope of this
   specification.  As an example, however, FA might delegate the duty of
   finding a HDAF to a local AAA server.  The local AAA server may also
   assist FA in the process of verifying the credentials of the mobile
   node, using protocols not specified in this document.

















<span class="grey">Calhoun &amp; Perkins           Standards Track                     [Page 7]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-8" ></span>
<span class="grey"><a href="./rfc2794">RFC 2794</a>                    Mobile Node NAI                   March 2000</span>


Addresses

   The working group can be contacted via the current chairs:

   Basavaraj Patil
   Nokia Corporation
   6000 Connection Drive
   M/S M8-540
   Irving, TX 75039
   USA

   Phone:  +1 972-894-6709
   Fax :  +1 972-894-5349
   EMail:  Basavaraj.Patil@nokia.com


   Phil Roberts
   Motorola
   1501 West Shure Drive
   Arlington Heights, IL 60004
   USA

   Phone:  +1 847-632-3148
   EMail:  QA3445@email.mot.com


   Questions about this memo can be directed to:

   Charles E. Perkins
   Nokia Research Center
   313 Fairchild Drive
   Mountain View, California 94043
   USA

   Phone:  +1-650 625-2986
   Fax:    +1 650 625-2502
   EMail:  charliep@iprg.nokia.com


   Pat R. Calhoun
   Sun Microsystems Laboratories
   15 Network Circle
   Menlo Park, California 94025
   USA

   Phone:  +1 650-786-7733
   Fax:    +1 650-786-6445
   EMail:  pcalhoun@eng.sun.com



<span class="grey">Calhoun &amp; Perkins           Standards Track                     [Page 8]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-9" ></span>
<span class="grey"><a href="./rfc2794">RFC 2794</a>                    Mobile Node NAI                   March 2000</span>


Full Copyright Statement

   Copyright (C) The Internet Society (2000).  All Rights Reserved.

   This document and translations of it may be copied and furnished to
   others, and derivative works that comment on or otherwise explain it
   or assist in its implementation may be prepared, copied, published
   and distributed, in whole or in part, without restriction of any
   kind, provided that the above copyright notice and this paragraph are
   included on all such copies and derivative works.  However, this
   document itself may not be modified in any way, such as by removing
   the copyright notice or references to the Internet Society or other
   Internet organizations, except as needed for the purpose of
   developing Internet standards in which case the procedures for
   copyrights defined in the Internet Standards process must be
   followed, or as required to translate it into languages other than
   English.

   The limited permissions granted above are perpetual and will not be
   revoked by the Internet Society or its successors or assigns.

   This document and the information contained herein is provided on an
   "AS IS" basis and THE INTERNET SOCIETY AND THE INTERNET ENGINEERING
   TASK FORCE DISCLAIMS ALL WARRANTIES, EXPRESS OR IMPLIED, INCLUDING
   BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE INFORMATION
   HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED WARRANTIES OF
   MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE.

Acknowledgement

   Funding for the RFC Editor function is currently provided by the
   Internet Society.



















Calhoun &amp; Perkins           Standards Track                     [Page 9]
</pre>