RFC 3972 on Cryptographically Generated Addresses (CGA)

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

        RFC 3972

        Title:      Cryptographically Generated Addresses (CGA)
        Author(s):  T. Aura
        Status:     Standards Track
        Date:       March 2005
        Mailbox:    tuomaura@microsoft.com
        Pages:      22
        Characters: 51473
        Updates/Obsoletes/SeeAlso:    None

        I-D Tag:    draft-ietf-send-cga-06.txt

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

This document describes a method for binding a public signature key
to an IPv6 address in the Secure Neighbor Discovery (SEND) protocol.
Cryptographically Generated Addresses (CGA) are IPv6 addresses for
which
the interface identifier is generated by computing a cryptographic
one-way hash function from a public key and auxiliary parameters.  The
binding between the public key and the address can be verified by
re-computing the hash value and by comparing the hash with the
interface identifier.  Messages sent from an IPv6 address can be
protected by attaching the public key and auxiliary parameters and by
signing the message with the corresponding private key.  The
protection works without a certification authority or any security
infrastructure.

This document is a product of the Securing Neighbor Discovery Working
Group of the IETF.

This is now a Proposed Standard Protocol.

This document specifies an Internet standards track protocol for
the Internet community, and requests discussion and suggestions
for improvements.  Please refer to the current edition of the
"Internet Official Protocol Standards" (STD 1) for the
standardization state and status of this protocol.  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@IETF.ORG.  Requests to be
added to or deleted from the RFC-DIST distribution list should
be sent to RFC-DIST-REQUEST@RFC-EDITOR.ORG.

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

        To: rfc-info@RFC-EDITOR.ORG
        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@RFC-EDITOR.ORG.  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@RFC-EDITOR.ORG.  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.