RFC 3344: IP Mobility Support for IPv4
This RFC has been replaced. Do not implement against it for new work — it was formally obsoleted by RFC 5944.
Current document in this lineage: RFC 5944 — IP Mobility Support for IPv4, Revised
In plain English — editorial summary, not part of the RFC
RFC 3344, "IP Mobility Support for IPv4", was published in August 2002 by C. Perkins. This is one of the earlier, shorter RFCs and the RFC Editor index carries no abstract for it — the full text below is the authoritative source.
Document record
- Document ID
- RFC3344
- Published
- August 2002
- Authors
- C. Perkins
- Status
- PROPOSED STANDARD
- Stream
- IETF
- Area
- int
- Pages
- 99
- 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
3 later RFCs formally update or obsolete part of this document.
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 2002IP Mobility SupportObsoleted
October 1996
- RFC 3337Class Extensions for PPP over Asynchronous Transfer Mode Adaptation Layer 2Current
December 2002
- RFC 3336PPP Over Asynchronous Transfer Mode Adaptation Layer 2 (AAL2)Current
December 2002
- RFC 3363Representing Internet Protocol version 6 (IPv6) Addresses in the Domain Name System (DNS)Updated
August 2002
- RFC 3364Tradeoffs in Domain Name System (DNS) Support for Internet Protocol version 6 (IPv6)Current
August 2002
- RFC 3316Internet Protocol Version 6 (IPv6) for Some Second and Third Generation Cellular HostsObsoleted
May 2003
- RFC 3315Dynamic Host Configuration Protocol for IPv6 (DHCPv6)Obsoleted
July 2003
- RFC 3314Recommendations for IPv6 in Third Generation Partnership Project (3GPP) StandardsCurrent
September 2002
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?