RFC 4285 on Authentication Protocol for Mobile IPv6

A new Request for Comments is now available in online RFC libraries.


        RFC 4285

        Title:      Authentication Protocol for Mobile IPv6
        Author(s):  A. Patel, K. Leung, M. Khalil, H. Akhtar,
                    K. Chowdhury
        Status:     Informational
        Date:       January 2006
        Mailbox:    alpesh@xxxxxxxxx, kleung@xxxxxxxxx,
                    mkhalil@xxxxxxxxxx, haseebak@xxxxxxxxxx,
                    kchowdhury@xxxxxxxxxxxxxxxxxxx
        Pages:      19
        Characters: 40874
        Updates/Obsoletes/SeeAlso:    None

        I-D Tag:    draft-ietf-mip6-auth-protocol-07.txt

        URL:        ftp://ftp.rfc-editor.org/in-notes/rfc4285.txt


IPsec is specified as the means of securing signaling messages
between the Mobile Node and Home Agent for Mobile IPv6 (MIPv6).
MIPv6 signaling messages that are secured include the Binding
Updates and Acknowledgement messages used for managing the bindings
between a Mobile Node and its Home Agent.  This document proposes an
alternate method for securing MIPv6 signaling messages between
Mobile Nodes and Home Agents.  The alternate method defined here
consists of a MIPv6-specific mobility message authentication option
that can be added to MIPv6 signaling messages.

This document is a product of the Mobility for IPv6 Working Group of
the IETF. 

This memo provides information for the Internet community.  It does
not specify an Internet standard of any kind.  Distribution of this
memo is unlimited.

This announcement is sent to the IETF list and the RFC-DIST list.
Requests to be added to or deleted from the IETF distribution list
should be sent to IETF-REQUEST@xxxxxxxxx  Requests to be
added to or deleted from the RFC-DIST distribution list should
be sent to RFC-DIST-REQUEST@xxxxxxxxxxxxxxx

Details on obtaining RFCs via FTP or EMAIL may be obtained by sending
an EMAIL message to rfc-info@xxxxxxxxxxxxxx with the message body 
help: ways_to_get_rfcs.  For example:

        To: rfc-info@xxxxxxxxxxxxxx
        Subject: getting rfcs

        help: ways_to_get_rfcs

Requests for special distribution should be addressed to either the
author of the RFC in question, or to RFC-Manager@xxxxxxxxxxxxxxx  Unless
specifically noted otherwise on the RFC itself, all RFCs are for
unlimited distribution.

Submissions for Requests for Comments should be sent to
RFC-EDITOR@xxxxxxxxxxxxxxx  Please consult RFC 2223, Instructions to RFC
Authors, for further information.


Joyce K. Reynolds and Sandy Ginoza
USC/Information Sciences Institute

...

Below is the data which will enable a MIME compliant Mail Reader 
implementation to automatically retrieve the ASCII version
of the RFCs.

<ftp://ftp.isi.edu/in-notes/rfc4285.txt>

_______________________________________________
IETF-Announce mailing list
IETF-Announce@xxxxxxxx
https://www1.ietf.org/mailman/listinfo/ietf-announce