Registration Revocation in Mobile IPv4
RFC 3543
Document | Type | RFC - Proposed Standard (August 2003; No errata) | |
---|---|---|---|
Authors | M Chandra , Steven Glass | ||
Last updated | 2015-10-14 | ||
Stream | Internet Engineering Task Force (IETF) | ||
Formats | plain text html pdf htmlized (tools) htmlized bibtex | ||
Stream | WG state | (None) | |
Document shepherd | No shepherd assigned | ||
IESG | IESG state | RFC 3543 (Proposed Standard) | |
Action Holders |
(None)
|
||
Consensus Boilerplate | Unknown | ||
Telechat date | |||
Responsible AD | Thomas Narten | ||
IESG note | 2003-08-13: RFC 3543 appears | ||
Send notices to | <proberts@megisto.com> |
Network Working Group S. Glass Request for Comments: 3543 Sun Microsystems Category: Standards Track M. Chandra Cisco Systems August 2003 Registration Revocation in Mobile 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 (2003). All Rights Reserved. Abstract This document defines a Mobile IPv4 Registration Revocation mechanism whereby a mobility agent involved in providing Mobile IP services to a mobile node can notify the other mobility agent providing Mobile IP services to the same mobile node of the termination of this registration. The mechanism is also usable by a home agent to notify a co-located mobile node of the termination of its binding as well. Moreover, the mechanism provides for this notification to be acknowledged. A signaling mechanism already defined by the Mobile IPv4 protocol is leveraged as a way to inform a mobile node of the revocation of its binding. Table of Contents 1. Introduction and Applicability . . . . . . . . . . . . . . . . 2 2. Terminology. . . . . . . . . . . . . . . . . . . . . . . . . . 4 3. Registration Revocation Extensions and Messages. . . . . . . . 4 3.1. Advertising Registration Revocation Support. . . . . . . 5 3.2. Revocation Support Extension . . . . . . . . . . . . . . 6 3.3. Registration Revocation Message. . . . . . . . . . . . . 8 3.4. Registration Revocation Acknowledgment Message . . . . . 11 3.5. Replay Protection. . . . . . . . . . . . . . . . . . . . 14 4. Registration Revocation Overview . . . . . . . . . . . . . . . 15 4.1. Mobile Node Notification . . . . . . . . . . . . . . . . 15 4.2. Registration Revocation Mechanism - Agent Notification . 17 4.2.1. Negotiating Revocation Support . . . . . . . . . 17 Glass & Chandra Standards Track [Page 1] 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 correspondentShow full document text