idnits 2.17.1 draft-ietf-mobileip-rfc2002-bis-08.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 3220 5 Title: IP Mobility Support for IPv4 6 Author(s): C. Perkins, Ed. 7 Status: Standards Track 8 Date: December 2001 9 Mailbox: charliep@iprg.nokia.com 10 Pages: 97 11 Characters: 238343 12 Obsoletes: 2002 14 I-D Tag: draft-ietf-mobileip-rfc2002-bis-08.txt 16 URL: ftp://ftp.rfc-editor.org/in-notes/rfc3220.txt 18 This document specifies protocol enhancements that allow transparent 19 routing of IP datagrams to mobile nodes in the Internet. Each 20 mobile node is always identified by its home address, regardless of 21 its current point of attachment to the Internet. While situated 22 away from its home, a mobile node is also associated with a 23 care-of address, which provides information about its current 24 point of attachment to the Internet. The protocol provides for 25 registering the care-of address with a home agent. The home agent 26 sends datagrams destined for the mobile node through a tunnel to 27 the care-of address. After arriving at the end of the tunnel, each 28 datagram is then delivered to the mobile node. 30 This document is a product of the IP Routing for Wireless/Mobile Hosts 31 Working Group of the IETF. 33 This is now a Proposed Standard Protocol. 35 This document specifies an Internet standards track protocol for 36 the Internet community, and requests discussion and suggestions 37 for improvements. Please refer to the current edition of the 38 "Internet Official Protocol Standards" (STD 1) for the 39 standardization state and status of this protocol. Distribution 40 of this memo is unlimited. 42 This announcement is sent to the IETF list and the RFC-DIST list. 43 Requests to be added to or deleted from the IETF distribution list 44 should be sent to IETF-REQUEST@IETF.ORG. Requests to be 45 added to or deleted from the RFC-DIST distribution list should 46 be sent to RFC-DIST-REQUEST@RFC-EDITOR.ORG. 48 Details on obtaining RFCs via FTP or EMAIL may be obtained by sending 49 an EMAIL message to rfc-info@RFC-EDITOR.ORG with the message body 50 help: ways_to_get_rfcs. For example: 52 To: rfc-info@RFC-EDITOR.ORG 53 Subject: getting rfcs 55 help: ways_to_get_rfcs 57 Requests for special distribution should be addressed to either the 58 author of the RFC in question, or to RFC-Manager@RFC-EDITOR.ORG. Unless 59 specifically noted otherwise on the RFC itself, all RFCs are for 60 unlimited distribution.echo 61 Submissions for Requests for Comments should be sent to 62 RFC-EDITOR@RFC-EDITOR.ORG. Please consult RFC 2223, Instructions to RFC 63 Authors, for further information.