RFC 2290 (rfc2290) - Page 2 of 17

Mobile-IPv4 Configuration Option for PPP IPCP

RFC 2290            Mobile-IPv4 Option for PPP IPCP        February 1998


       2.3. High-Level Requirements for Non-Mobile-Nodes . . . . . .   7
       2.4. High-Level Requirements for Mobile Nodes . . . . . . . .   8
       2.5. Detailed Description . . . . . . . . . . . . . . . . . .   8
       2.6. Example Scenarios  . . . . . . . . . . . . . . . . . . .  12
   3. Additional Requirements  . . . . . . . . . . . . . . . . . . .  14
       3.1. Other IPCP Options . . . . . . . . . . . . . . . . . . .  14
       3.2. Move Detection . . . . . . . . . . . . . . . . . . . . .  14
   4. Security Considerations  . . . . . . . . . . . . . . . . . . .  15
   5. References . . . . . . . . . . . . . . . . . . . . . . . . . .  15
   6. Acknowledgments  . . . . . . . . . . . . . . . . . . . . . . .  16
   7. Authors' Addresses . . . . . . . . . . . . . . . . . . . . . .  16
   8. Full Copyright Statement . . . . . . . . . . . . . . . . . . .  17

1. Introduction

   Mobile IP [RFC 2002] defines protocols and procedures by which
   packets can be routed to a mobile node, regardless of its current
   point-of-attachment to the Internet, and without changing its IP
   address.  Mobile IP is designed to run over any type of media and any
   type of data link-layer.  However, the interaction between Mobile IP
   and PPP is currently underspecified and generally results in an
   inappropriate application of Mobile IP when mobile nodes connect to
   the Internet via PPP.

   This document defines proper interaction between a mobile node [RFC
   2002] and a peer through which the mobile node connects to the
   Internet using PPP.  This requires the definition of a new option for
   IPCP [RFC 1332], named the "Mobile-IPv4" Configuration Option, which
   is defined in this document.  The mobile node and the peer use this
   option to negotiate the appropriate use of Mobile IP over the PPP
   link.

   The Mobile-IPv4 option defined in this document is intended to work
   in conjunction with the existing IP-Address option [RFC 1332].

1.1. Specification Language

   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 RFC 2119.

1.2. Terminology

   This document uses the following terms as defined in [RFC 2002]:







Solomon & Glass             Standards Track