RFC 4581: Cryptographically Generated Addresses (CGA) Extension Field Format
In plain English — editorial summary, not part of the RFC
This document defines a Type-Length-Value format for Cryptographically Generated Address (CGA) Extensions. This document updates RFC 3972. [STANDARDS-TRACK]
Document record
- Document ID
- RFC4581
- Published
- October 2006
- Authors
- M. Bagnulo; J. Arkko
- Status
- PROPOSED STANDARD
- Stream
- IETF
- Area
- —
- Pages
- 4
- Also known as
- —
- Updates:
- RFC 3972
Topics
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 5003Attachment Individual Identifier (AII) Types for AggregationCurrent
September 2007
- RFC 5301Dynamic Hostname Exchange Mechanism for IS-ISUpdated
October 2008
- RFC 5308Routing IPv6 with IS-ISUpdated
October 2008
- RFC 5444Generalized Mobile Ad Hoc Network (MANET) Packet/Message FormatUpdated
February 2009
- RFC 5497Representing Multi-Value Time in Mobile Ad Hoc Networks (MANETs)Current
March 2009
- RFC 2763Dynamic Hostname Exchange Mechanism for IS-ISObsoleted
February 2000
- RFC 7188Optimized Link State Routing Protocol Version 2 (OLSRv2) and MANET Neighborhood Discovery Protocol (NHDP) Extension TLVsUpdated
April 2014
- RFC 7631TLV Naming in the Mobile Ad Hoc Network (MANET) Generalized Packet/Message FormatUpdated
September 2015
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?