RFC 4285:Authentication Protocol for Mobile IPv6
RFC-Ref

MIPv6


Click on the red underlined text to get to the source

... Authentication, Authorization, and Accounting (AAA) home server). MIPv6 as per RFCs 3775 and 3776 relies on the IPsec SA ...
... IKEv2 is not yet capable of addressing the immediate need for MIPv6 deployment. ...
... the primary means for identifying and authentication/authorizing a mobile user for MIPv6 service. ...
... number of signaling messages sent over such interfaces. MIPv6 signaling that relies on Internet Key Exchange ...


... Home Agent MUST send BA with Status Code MIPV6-AUTH-FAIL. If the Home Agent does not have shared-key-based ...
... Home Agent MUST send a Binding Acknowledgement with status code MIPV6-AUTH-FAIL to the Mobile Node, ...
... receiving a Binding Acknowledgement with status code MIPV6- AUTH-FAIL, the Mobile Node ...


... Status Code in BA to MIPV6-MESG-ID-REQD. When the Home Agent ...
... Binding Acknowledgement with status code MIPV6-ID-MISMATCH. The Home Agent does not create a ...
... Mobile Node receives a Binding Acknowledgement with the code MIPV6-ID-MISMATCH, the Mobile Node MUST authenticate the BA ...
... Upon receiving a BA that does not contain the MIPV6-ID-MISMATCH status code, the Mobile Node ...


... The values for status codes MIPV6-ID-MISMATCH, MIPv6-AUTH-FAIL, and ...
... The values for status codes MIPV6-ID-MISMATCH, MIPv6-AUTH-FAIL, and MIPV6 ...
... MIPv6-AUTH-FAIL, and MIPV6-MESG-ID-REQD, as defined in Section 6 and Section 5.3, have been assigned. The values are 144 for MIPV6-ID-MISMATCH 145 for ...
... MIPV6-MESG-ID-REQD, as defined in Section 6 and Section 5.3, have been assigned. The values are 144 for MIPV6-ID-MISMATCH 145 for MIPV6-MESG-ID-REQD and 146 for MIPV6 ...
... been assigned. The values are 144 for MIPV6-ID-MISMATCH 145 for MIPV6-MESG-ID-REQD and 146 for MIPV6-AUTH-FAIL. ...
... MIPV6-ID-MISMATCH 145 for MIPV6-MESG-ID-REQD and 146 for MIPV6-AUTH-FAIL. ...



Google
Web
RFC-Ref