RFC 5944: IP Mobility Support for IPv4, Revised
In plain English — editorial summary, not part of the RFC
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. [STANDARDS-TRACK]
Document record
- Document ID
- RFC5944
- Published
- November 2010
- Authors
- C. Perkins
- Status
- PROPOSED STANDARD
- Stream
- IETF
- Area
- int
- Pages
- 100
- Also known as
- —
- Obsoletes:
- RFC 3344
Topics
Standards lineage
This document is one revision in a chain of 4 RFCs, each formally replacing the one before it.
- RFC 2002 (1996)
- RFC 3220 (2002)
- RFC 3344 (2002)
- RFC 5944 (2010)
Read the full history of IP Mobility Support for IPv4, Revised →
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 3519Mobile IP Traversal of Network Address Translation (NAT) DevicesCurrent
May 2003
- RFC 6098Generic Notification Message for Mobile IPv4Current
April 2012
- RFC 6275Mobility Support in IPv6Current
July 2011
- RFC 6434IPv6 Node RequirementsObsoleted
December 2011
- RFC 5454Dual-Stack Mobile IPv4Current
March 2009
- RFC 5265Mobile IPv4 Traversal across IPsec-Based VPN GatewaysCurrent
June 2008
- RFC 6644Rebind Capability in DHCPv6 Reconfigure MessagesCurrent
July 2012
- RFC 5030Mobile IPv4 RADIUS RequirementsCurrent
October 2007
Also filed under
About this page
The document record above — title, authors, date, status, stream, area, relationships, DOI and errata — is imported verbatim from the public RFC Editor index. The “in plain English” section is editorial: written by The metasystema editorial team, not part of the RFC. Where the two differ, the RFC text governs.
Last checked against the RFC Editor index on . RFCs are never revised after publication; changes are issued as new documents.
Data sources · Editorial policy · Report a correction · What is an RFC?