metasystema.org
UpdatedPROPOSED STANDARDIETF stream

RFC 3972: Cryptographically Generated Addresses (CGA)

Still current, but amended. Parts of this document are changed or extended by RFC 4581, RFC 4982. Read both.

In plain English — editorial summary, not part of the RFC

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. [STANDARDS-TRACK]

Document record

Document ID
RFC3972
Published
March 2005
Authors
T. Aura
Status
PROPOSED STANDARD
Stream
IETF
Area
int
Pages
22
Also known as
—
Updated by:
RFC 4581, RFC 4982

Topics

Referenced by

2 later RFCs formally update or obsolete part of this document.

Related documents

Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.

Also filed under

About this page

The document record above — title, authors, date, status, stream, area, relationships, DOI and errata — is imported verbatim from the public RFC Editor index. The “in plain English” section is editorial: written by The metasystema editorial team, not part of the RFC. Where the two differ, the RFC text governs.

Last checked against the RFC Editor index on . RFCs are never revised after publication; changes are issued as new documents.

Data sources · Editorial policy · Report a correction · What is an RFC?

canonical URL: /rfc/3972-cryptographically-generated-addresses-cga