RFC 3344 on IP Mobility Support for IPv4

rfc-editor@rfc-editor.org Mon, 16 September 2002 17:30 UTC

Message-Id: <200209161718.g8GHIlD03994@gamma.isi.edu>
To: IETF-Announce:;
Subject: RFC 3344 on IP Mobility Support for IPv4
Cc: rfc-editor@rfc-editor.org, mobile-ip@standards.nortelnetworks.com
From: rfc-editor@rfc-editor.org
Mime-Version: 1.0
Content-Type: Multipart/Mixed; Boundary="NextPart"
Date: Mon, 16 Sep 2002 10:18:47 -0700
Sender: rfc-ed@ISI.EDU

A new Request for Comments is now available in online RFC libraries.


        RFC 3344

        Title:	    IP Mobility Support for IPv4
        Author(s):  C. Perkins, Ed.
        Status:	    Standards Track
	Date:       August 2002
        Mailbox:    charliep@iprg.nokia.com
        Pages:      99
        Characters: 241041
        Obsoletes:  3220

        URL:        ftp://ftp.rfc-editor.org/in-notes/rfc3344.txt


This document specifies protocol enhancements that allow transparent
routing of IP datagrams to mobile nodes in the Internet.  Each
mobile node is always identified by its home address, regardless of
its current point of attachment to the Internet.  While situated
away from its home, a mobile node is also associated with a
care-of address, which provides information about its current
point of attachment to the Internet.  The protocol provides for
registering the care-of address with a home agent.  The home agent
sends datagrams destined for the mobile node through a tunnel to
the care-of address.  After arriving at the end of the tunnel, each
datagram is then delivered to the mobile node.

This document is a product of the IP Routing for Wireless/Mobile Hosts
Working Group of the IETF.

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.

This announcement is sent to the IETF list and the RFC-DIST list.
Requests to be added to or deleted from the IETF distribution list
should be sent to IETF-REQUEST@IETF.ORG.  Requests to be
added to or deleted from the RFC-DIST distribution list should
be sent to RFC-DIST-REQUEST@RFC-EDITOR.ORG.

Details on obtaining RFCs via FTP or EMAIL may be obtained by sending
an EMAIL message to rfc-info@RFC-EDITOR.ORG with the message body 
help: ways_to_get_rfcs.  For example:

        To: rfc-info@RFC-EDITOR.ORG
        Subject: getting rfcs

        help: ways_to_get_rfcs

Requests for special distribution should be addressed to either the
author of the RFC in question, or to RFC-Manager@RFC-EDITOR.ORG.  Unless
specifically noted otherwise on the RFC itself, all RFCs are for
unlimited distribution.echo 
Submissions for Requests for Comments should be sent to
RFC-EDITOR@RFC-EDITOR.ORG.  Please consult RFC 2223, Instructions to RFC
Authors, for further information.


Joyce K. Reynolds and Sandy Ginoza
USC/Information Sciences Institute

...

Below is the data which will enable a MIME compliant Mail Reader 
implementation to automatically retrieve the ASCII version
of the RFCs.

ftp://ftp.isi.edu/in-notes/rfc3344.txt"><ftp://ftp.isi.edu/in-notes/rfc3344.txt>

RFC 3344 on IP Mobility Support for IPv4 rfc-editor
RFC 3344 on IP Mobility Support for IPv4 rfc-editor