idnits 2.17.1 draft-ietf-mobileip-reg-revok-07.txt: Skipping this file; it looks like a tombstone file to me. -------------------------------------------------------------------------------- 1 A new Request for Comments is now available in online RFC libraries. 3 RFC 3543 5 Title: Registration Revocation in Mobile IPv4 6 Author(s): S. Glass, M. Chandra 7 Status: Standards Track 8 Date: August 2003 9 Mailbox: steven.glass@sun.com, mchandra@cisco.com 10 Pages: 33 11 Characters: 81805 12 Updates/Obsoletes/SeeAlso: None 14 I-D Tag: draft-ietf-mobileip-reg-revok-07.txt 16 URL: ftp://ftp.rfc-editor.org/in-notes/rfc3543.txt 18 This document defines a Mobile IPv4 Registration Revocation 19 mechanism whereby a mobility agent involved in providing Mobile IP 20 services to a mobile node can notify the other mobility agent 21 providing Mobile IP services to the same mobile node of the 22 termination of this registration. The mechanism is also usable by a 23 home agent to notify a co-located mobile node of the termination of 24 its binding as well. Moreover, the mechanism provides for this 25 notification to be acknowledged. A signaling mechanism already 26 defined by the Mobile IPv4 protocol is leveraged as a way to inform a 27 mobile node of the revocation of its binding. 29 This document is a product of the IP Routing for Wireless/Mobile Hosts 30 Working Group. 32 This is now a Proposed Standard Protocol. 34 This document specifies an Internet standards track protocol for 35 the Internet community, and requests discussion and suggestions 36 for improvements. Please refer to the current edition of the 37 "Internet Official Protocol Standards" (STD 1) for the 38 standardization state and status of this protocol. Distribution 39 of this memo is unlimited. 41 This announcement is sent to the IETF list and the RFC-DIST list. 42 Requests to be added to or deleted from the IETF distribution list 43 should be sent to IETF-REQUEST@IETF.ORG. Requests to be 44 added to or deleted from the RFC-DIST distribution list should 45 be sent to RFC-DIST-REQUEST@RFC-EDITOR.ORG. 47 Details on obtaining RFCs via FTP or EMAIL may be obtained by sending 48 an EMAIL message to rfc-info@RFC-EDITOR.ORG with the message body 49 help: ways_to_get_rfcs. For example: 51 To: rfc-info@RFC-EDITOR.ORG 52 Subject: getting rfcs 54 help: ways_to_get_rfcs 56 Requests for special distribution should be addressed to either the 57 author of the RFC in question, or to RFC-Manager@RFC-EDITOR.ORG. Unless 58 specifically noted otherwise on the RFC itself, all RFCs are for 59 unlimited distribution.echo 60 Submissions for Requests for Comments should be sent to 61 RFC-EDITOR@RFC-EDITOR.ORG. Please consult RFC 2223, Instructions to RFC 62 Authors, for further information.