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 to support topologically correct reverse tunnels. This document does not attempt to solve the problems posed by firewalls located between the home agent and the mobile node's care-of address. [STANDARDS-TRACK]
Document record
- Document ID
- RFC3024
- Published
- January 2001
- Authors
- G. Montenegro
- Status
- PROPOSED STANDARD
- Stream
- IETF
- Area
- int
- Pages
- 30
- Also known as
- —
- Obsoletes:
- RFC 2344
Topics
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 3115Mobile IP Vendor/Organization-Specific ExtensionsCurrent
April 2001
- RFC 3519Mobile IP Traversal of Network Address Translation (NAT) DevicesCurrent
May 2003
- RFC 3583Requirements of a Quality of Service (QoS) Solution for Mobile IPCurrent
September 2003
- RFC 3019IP Version 6 Management Information Base for The Multicast Listener Discovery ProtocolObsoleted
January 2001
- RFC 3011The IPv4 Subnet Selection Option for DHCPCurrent
November 2000
- RFC 3111Service Location Protocol Modifications for IPv6Current
May 2001
- RFC 2928Initial IPv6 Sub-TLA ID AssignmentsCurrent
September 2000
- RFC 3122Extensions to IPv6 Neighbor Discovery for Inverse Discovery SpecificationCurrent
June 2001
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?