RFC 2344: Reverse Tunneling for Mobile IP
This RFC has been replaced. Do not implement against it for new work — it was formally obsoleted by RFC 3024.
Current version: RFC 3024 — Reverse Tunneling for Mobile IP, revised
In plain English — editorial summary, not part of the RFC
This document proposes backwards-compatible extensions to Mobile IP in order to support topologically correct reverse tunnels. [STANDARDS-TRACK]
Document record
- Document ID
- RFC2344
- Published
- May 1998
- Authors
- G. Montenegro
- Status
- PROPOSED STANDARD
- Stream
- IETF
- Area
- int
- Pages
- 19
- Also known as
- —
- Obsoleted by:
- RFC 3024
Topics
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 3012Mobile IPv4 Challenge/Response ExtensionsObsoleted
November 2000
- RFC 2406IP Encapsulating Security Payload (ESP)Obsoleted
November 1998
- RFC 2156MIXER (Mime Internet X.400 Enhanced Relay): Mapping between X.400 and RFC 822/MIMECurrent
January 1998
- RFC 1829The ESP DES-CBC TransformCurrent
August 1995
- RFC 1767MIME Encapsulation of EDI ObjectsCurrent
March 1995
- RFC 2927MIME Directory Profile for LDAP SchemaCurrent
September 2000
- RFC 2936HTTP MIME Type Handler DetectionCurrent
September 2000
- RFC 4303IP Encapsulating Security Payload (ESP)Current
December 2005
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?