RFC 4285: Authentication Protocol for Mobile IPv6
In plain English — editorial summary, not part of the RFC
IPsec is specified as the means of securing signaling messages between the Mobile Node and Home Agent for Mobile IPv6 (MIPv6). MIPv6 signaling messages that are secured include the Binding Updates and Acknowledgement messages used for managing the bindings between a Mobile Node and its Home Agent. This document proposes an alternate method for securing MIPv6 signaling messages between Mobile Nodes and Home Agents. The alternate method defined here consists of a MIPv6-specific mobility message authentication option that can be added to MIPv6 signaling messages. This memo provides information for the Internet community.
Document record
- Document ID
- RFC4285
- Published
- January 2006
- Authors
- A. Patel; K. Leung; M. Khalil; H. Akhtar; K. Chowdhury
- Status
- INFORMATIONAL
- Stream
- IETF
- Area
- int
- Pages
- 19
- Also known as
- —
Topics
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 4301Security Architecture for the Internet ProtocolUpdated
December 2005
- RFC 4302IP Authentication HeaderCurrent
December 2005
- RFC 4303IP Encapsulating Security Payload (ESP)Current
December 2005
- RFC 4615The Advanced Encryption Standard-Cipher-based Message Authentication Code-Pseudo-Random Function-128 (AES-CMAC-PRF-128) Algorithm for the Internet Key Exchange Protocol (IKE)Current
August 2006
- RFC 3664The AES-XCBC-PRF-128 Algorithm for the Internet Key Exchange Protocol (IKE)Obsoleted
January 2004
- RFC 2401Security Architecture for the Internet ProtocolObsoleted
November 1998
- RFC 4280Dynamic Host Configuration Protocol (DHCP) Options for Broadcast and Multicast Control ServersCurrent
December 2005
- RFC 4449Securing Mobile IPv6 Route Optimization Using a Static Shared KeyCurrent
June 2006
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?