RFC 4093: Problem Statement: Mobile IPv4 Traversal of Virtual Private Network (VPN) Gateways
In plain English — editorial summary, not part of the RFC
Deploying Mobile-IP v4 in networks that are connected to the Internet through a Virtual Private Network (VPN) gateway presents some problems that do not currently have well-described solutions. This document aims to describe and illustrate these problems, and to propose some guidelines for possible solutions. This memo provides information for the Internet community.
Document record
- Document ID
- RFC4093
- Published
- August 2005
- Authors
- F. Adrangi; H. Levkowetz
- Status
- INFORMATIONAL
- Stream
- IETF
- Area
- int
- Pages
- 19
- Also known as
- —
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 4087IP Tunnel MIBCurrent
June 2005
- RFC 4076Renumbering Requirements for Stateless Dynamic Host Configuration Protocol for IPv6 (DHCPv6)Current
May 2005
- RFC 4075Simple Network Time Protocol (SNTP) Configuration Option for DHCPv6Current
May 2005
- RFC 4113Management Information Base for the User Datagram Protocol (UDP)Current
June 2005
- RFC 4068Fast Handovers for Mobile IPv6Obsoleted
July 2005
- RFC 4064Experimental Message, Extensions, and Error Codes for Mobile IPv4Current
May 2005
- RFC 4058Protocol for Carrying Authentication for Network Access (PANA) RequirementsCurrent
May 2005
- RFC 4135Goals of Detecting Network Attachment in IPv6Current
August 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?