datatracker.ietf.org
Sign in
Version 5.3.0, 2014-04-12
Report a bug

Mobile IP Network Access Identifier Extension for IPv4
RFC 2794

Document type: RFC - Proposed Standard (March 2000)
Updates RFC 2290
Document stream: IETF
Last updated: 2013-03-02
Other versions: plain text, pdf, html

IETF State: (None)
Consensus: Unknown
Document shepherd: No shepherd assigned

IESG State: RFC 2794 (Proposed Standard)
Responsible AD: (None)
Send notices to: No addresses provided

Network  Working Group                                         P. Calhoun
Request for Comments: 2794                  Sun Microsystems Laboratories
Updates: 2290                                                  C. Perkins
Category: Standards Track                           Nokia Research Center
                                                               March 2000

         Mobile IP Network Access Identifier Extension for IPv4

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 RFC
   2290 which specifies the Mobile-IPv4 Configuration option for IPCP,
   by allowing the Mobile Node's Home Address field of this option to be
   zero.

Calhoun & Perkins           Standards Track                     [Page 1]
RFC 2794                    Mobile Node NAI                   March 2000

1. Introduction

   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) [1].  This document
   specifies the Mobile Node NAI extension to the Mobile IP Registration
   Request [7] 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
   RFC 2290 [8] 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 RFC 2290.  Interpretation of various scenarios from RFC
   2290 is given in section 4.

   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 [3].

2. Mobile Node NAI Extension

   The Mobile Node NAI extension, shown in figure 1, contains the user
   name following the format defined in [1].  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.

Calhoun & Perkins           Standards Track                     [Page 2]
RFC 2794                    Mobile Node NAI                   March 2000

       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

[include full document text]