RFC 3220: IP Mobility Support for IPv4
This RFC has been replaced. Do not implement against it for new work — it was formally obsoleted by RFC 3344.
Current document in this lineage: 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
- RFC3220
- Published
- January 2002
- Authors
- C. Perkins
- Status
- PROPOSED STANDARD
- Stream
- IETF
- Area
- int
- Pages
- 98
- Also known as
- —
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 →
Referenced by
One later RFC formally updates or obsoletes part of this document.
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 3178IPv6 Multihoming Support at Site Exit RoutersCurrent
October 2001
- RFC 3041Privacy Extensions for Stateless Address Autoconfiguration in IPv6Obsoleted
January 2001
- RFC 3012Mobile IPv4 Challenge/Response ExtensionsObsoleted
November 2000
- RFC 2977Mobile IP Authentication, Authorization, and Accounting RequirementsCurrent
October 2000
- RFC 3493Basic Socket Interface Extensions for IPv6Current
March 2003
- RFC 2939Procedures and IANA Guidelines for Definition of New DHCP Options and Message TypesCurrent
September 2000
- RFC 3513Internet Protocol Version 6 (IPv6) Addressing ArchitectureObsoleted
April 2003
- RFC 3587IPv6 Global Unicast Address FormatCurrent
August 2003
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?