RFC 6618: Mobile IPv6 Security Framework Using Transport Layer Security for Communication between the Mobile Node and Home Agent
In plain English — editorial summary, not part of the RFC
Mobile IPv6 signaling between a Mobile Node (MN) and its Home Agent (HA) is secured using IPsec. The security association (SA) between an MN and the HA is established using Internet Key Exchange Protocol (IKE) version 1 or 2. The security model specified for Mobile IPv6, which relies on IKE/IPsec, requires interaction between the Mobile IPv6 protocol component and the IKE/IPsec module of the IP stack. This document proposes an alternate security framework for Mobile IPv6 and Dual-Stack Mobile IPv6, which relies on Transport Layer Security for establishing keying material and other bootstrapping parameters required to protect Mobile IPv6 signaling and data traffic between the MN and HA. This document defines an Experimental Protocol for the Internet community.
Document record
- Document ID
- RFC6618
- Published
- May 2012
- Authors
- J. Korhonen; B. Patil; H. Tschofenig; D. Kroeselberg
- Status
- EXPERIMENTAL
- Stream
- IETF
- Area
- int
- Pages
- 38
- Also known as
- —
Topics
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 6496Secure Proxy ND Support for SEcure Neighbor Discovery (SEND)Current
February 2012
- RFC 6164Using 127-Bit IPv6 Prefixes on Inter-Router LinksUpdated
April 2011
- RFC 6088Traffic Selectors for Flow BindingsCurrent
January 2011
- RFC 7830The EDNS(0) Padding OptionCurrent
May 2016
- RFC 5380Hierarchical Mobile IPv6 (HMIPv6) Mobility ManagementCurrent
October 2008
- RFC 5270Mobile IPv6 Fast Handovers over IEEE 802.16e NetworksCurrent
June 2008
- RFC 8387Practical Considerations and Implementation Experiences in Securing Smart Object NetworksCurrent
May 2018
- RFC 8467Padding Policies for Extension Mechanisms for DNS (EDNS(0))Current
October 2018
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?