RFC 4285:Authentication Protocol for Mobile IPv6
RFC-Ref

IPsec


Click on the red underlined text to get to the source

... Home Agent (HA) to be secured by the IPsec Security Associations (IPsec SAs) that are established between ...
... HA) to be secured by the IPsec Security Associations (IPsec SAs) that are established between these two entities. ...
... IPv6 mobility in a host without having to establish an IPsec SA with its Home Agent. A ...
... Mobile Node can implement Mobile IPv6 without having to integrate it with the IPsec module, in which case the Binding Update and Binding Acknowledgement messages (between MN-HA ...
... home server). MIPv6 as per RFCs 3775 and 3776 relies on the IPsec SA between the MN and an HA ...


... Binding Update and Binding Acknowledgement messages. This option can be used along with IPsec or preferably as an alternate mechanism to authenticate Binding Update ...
... authenticate Binding Update and Binding Acknowledgement messages in the absence of IPsec. This document also defines subtype numbers, which identify the mode ...


... Home Agent, and/or home AAA (as an alternative to IPsec). The new options provide for authentication of Binding Update ...


... problem with sequence number exists. Since the base specification mandates the use of IPsec (and naturally that goes with IKE in most cases), the real replay protection ...
... IKE in most cases), the real replay protection is provided by IPsec/IKE. In case of BU/BA ...



Google
Web
RFC-Ref