RFC 5419

Why the Authentication Data Suboption is Needed for Mobile IPv6 (MIPv6), January 2009

Canonical URL:
https://www.rfc-editor.org/rfc/rfc5419.txt
File formats:
Plain TextPDF
Status:
INFORMATIONAL
Authors:
B. Patil
G. Dommety
Stream:
IETF
Source:
mip6 (int)

Cite this RFC: TXT  |  XML

DOI:  10.17487/RFC5419

Discuss this RFC: Send questions or comments to iesg@ietf.org

Other actions: Submit Errata  |  Find IPR Disclosures from the IETF


Abstract

Mobile IPv6 defines a set of signaling messages that enable the mobile node (MN) to authenticate and perform registration with its home agent (HA). These authentication signaling messages between the mobile node and home agent are secured by an IPsec security association (SA) that is established between the MN and HA. The MIP6 working group has specified a mechanism to secure the Binding Update (BU) and Binding Acknowledgement (BAck) messages using an authentication option, similar to the authentication option in Mobile IPv4, carried within the signaling messages that are exchanged between the MN and HA to establish a binding. This document provides the justifications as to why the authentication option mechanism is needed for Mobile IPv6 deployment in certain environments. This memo provides information for the Internet community.


For the definition of Status, see RFC 2026.

For the definition of Stream, see RFC 4844.


Download PDF Reader



Search RFCs
Advanced Search
×