RFC 4225: Mobile IP Version 6 Route Optimization Security Design Background
In plain English — editorial summary, not part of the RFC
This document is an account of the rationale behind the Mobile IPv6 (MIPv6) Route Optimization security design. The purpose of this document is to present the thinking and to preserve the reasoning behind the Mobile IPv6 security design in 2001 - 2002. The document has two target audiences: (1) helping MIPv6 implementors to better understand the design choices in MIPv6 security procedures, and (2) allowing people dealing with mobility or multi-homing to avoid a number of potential security pitfalls in their designs. This memo provides information for the Internet community.
Document record
- Document ID
- RFC4225
- Published
- December 2005
- Authors
- P. Nikander; J. Arkko; T. Aura; G. Montenegro; E. Nordmark
- Status
- INFORMATIONAL
- Stream
- IETF
- Area
- int
- Pages
- 37
- Also known as
- —
Topics
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 4295Mobile IPv6 Management Information BaseCurrent
April 2006
- RFC 3519Mobile IP Traversal of Network Address Translation (NAT) DevicesCurrent
May 2003
- RFC 4977Problem Statement: Dual Stack MobilityCurrent
August 2007
- RFC 5030Mobile IPv4 RADIUS RequirementsCurrent
October 2007
- RFC 5094Mobile IPv6 Vendor Specific OptionCurrent
December 2007
- RFC 5096Mobile IPv6 Experimental MessagesCurrent
December 2007
- RFC 5268Mobile IPv6 Fast HandoversObsoleted
June 2008
- RFC 5555Mobile IPv6 Support for Dual Stack Hosts and RoutersUpdated
June 2009
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?