Why Authentication Data suboption is needed for MIP6

Document Type Expired Internet-Draft (individual)
Last updated 2005-08-30
Stream (None)
Intended RFC status (None)
Expired & archived
pdf htmlized bibtex
Stream Stream state (No stream defined)
Consensus Boilerplate Unknown
RFC Editor Note (None)
IESG IESG state Expired
Telechat date
Responsible AD (None)
Send notices to (None)

This Internet-Draft is no longer active. A copy of the expired Internet-Draft can be found at


Mobile IPv6 defines a set of 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 SA that is established between the MN and HA. The MIP6 Working group ID draft-ietf-mip6-auth- protocol-04.txt specifies a mechanism to secure the binding update and binding acknowledgement messages using an authentication option, similar to authentication option in Mobile IPv4, carried within the 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 deployment environments.


Gopal Dommety (gdommety@cisco.com)
Basavaraj Patil (basavaraj.patil@nokia.com)

(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)