RFC 3543 (rfc3543) - Page 2 of 33

Registration Revocation in Mobile IPv4

RFC 3543         Registration Revocation in Mobile IPv4      August 2003


             4.2.2.  Home Domain Revoking a Registration. . . . . . . 19
                     4.2.2.1.  Home Agent Responsibilities. . . . . . 19
                     4.2.2.2.  Foreign Agent Responsibilities . . . . 20
                     4.2.2.3.  'Direct' Co-located Mobile Node
                               Responsibilities . . . . . . . . . . . 20
             4.2.3.  Foreign Domain Revoking a Registration . . . . . 21
                     4.2.3.1.  Foreign Agent Responsibilities . . . . 21
                     4.2.3.2.  Home Agent Responsibilities. . . . . . 22
             4.2.4.  Mobile Node Deregistering a Registration . . . . 23
       4.3.  Mobile IP Registration Bits in the Revocation Process. . 23
             4.3.1.  The 'R' Bit in Use . . . . . . . . . . . . . . . 23
             4.3.2.  The 'D' Bit in Use (co-located mobile nodes) . . 23
   5.  Error Codes. . . . . . . . . . . . . . . . . . . . . . . . . . 24
   6.  Security Considerations. . . . . . . . . . . . . . . . . . . . 24
       6.1.  Agent Advertisements . . . . . . . . . . . . . . . . . . 24
       6.2.  Revocation Messages. . . . . . . . . . . . . . . . . . . 25
   7.  IANA Considerations. . . . . . . . . . . . . . . . . . . . . . 27
       7.1.  New Message Types. . . . . . . . . . . . . . . . . . . . 27
       7.2.  New Extension Values . . . . . . . . . . . . . . . . . . 27
       7.3.  New Error Codes. . . . . . . . . . . . . . . . . . . . . 27
   8.  References . . . . . . . . . . . . . . . . . . . . . . . . . . 27
       8.1.  Normative (Numerical References) . . . . . . . . . . . . 27
       8.2.  Informational (Alphabetical References). . . . . . . . . 28
   Appendix A  An Example of the New Messages in Use. . . . . . . . . 29
               A.1.  The Registration Phase . . . . . . . . . . . . . 29
               A.2.  The Revocation Phase . . . . . . . . . . . . . . 29
   Appendix B  Disparate Address, and Receiver Considerations . . . . 30
   Acknowledgments. . . . . . . . . . . . . . . . . . . . . . . . . . 32
   Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . . 32
   Full Copyright Statement . . . . . . . . . . . . . . . . . . . . . 33

1.  Introduction and Applicability

   Mobile IP [1] defines registration of a mobile node's location to
   provide connectivity between the mobile node and its home domain,
   facilitating communication between mobile nodes and any correspondent
   node.  At any time, either the home or foreign agent may wish to
   cease servicing a mobile node, or for administrative reasons may no
   longer be required to service a mobile node.

   This document defines a general registration revocation mechanism for
   Mobile IPv4, whereby a mobility agent can notify another mobility
   agent (or a 'direct' co-located mobile node) of the termination of
   mobility bindings.  A mobility agent that receives a revocation
   notification no longer has to provide services to the mobile node
   whose registration has been revoked.  A signaling mechanism already
   defined by the Mobile IPv4 protocol [1] is leveraged as a way to
   inform a mobile node of the revocation of its binding.



Glass & Chandra             Standards Track