RFC 5265: Mobile IPv4 Traversal across IPsec-Based VPN Gateways
In plain English — editorial summary, not part of the RFC
This document outlines a solution for the Mobile IPv4 (MIPv4) and IPsec coexistence problem for enterprise users. The solution consists of an applicability statement for using Mobile IPv4 and IPsec for session mobility in corporate remote access scenarios, and a required mechanism for detecting the trusted internal network securely. [STANDARDS-TRACK]
Document record
- Document ID
- RFC5265
- Published
- June 2008
- Authors
- S. Vaarala; E. Klovning
- Status
- PROPOSED STANDARD
- Stream
- IETF
- Area
- int
- Pages
- 39
- Also known as
- —
Topics
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 4977Problem Statement: Dual Stack MobilityCurrent
August 2007
- RFC 3519Mobile IP Traversal of Network Address Translation (NAT) DevicesCurrent
May 2003
- RFC 4301Security Architecture for the Internet ProtocolUpdated
December 2005
- RFC 2401Security Architecture for the Internet ProtocolObsoleted
November 1998
- RFC 5454Dual-Stack Mobile IPv4Current
March 2009
- RFC 5030Mobile IPv4 RADIUS RequirementsCurrent
October 2007
- RFC 5637Authentication, Authorization, and Accounting (AAA) Goals for Mobile IPv6Current
September 2009
- RFC 5944IP Mobility Support for IPv4, RevisedCurrent
November 2010
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?