RFC 6054: Using Counter Modes with Encapsulating Security Payload (ESP) and Authentication Header (AH) to Protect Group Traffic
In plain English — editorial summary, not part of the RFC
Counter modes have been defined for block ciphers such as the Advanced Encryption Standard (AES). Counter modes use a counter, which is typically assumed to be incremented by a single sender. This memo describes the use of counter modes when applied to the Encapsulating Security Payload (ESP) and Authentication Header (AH) in multiple-sender group applications. [STANDARDS-TRACK]
Document record
- Document ID
- RFC6054
- Published
- November 2010
- Authors
- D. McGrew; B. Weis
- Status
- PROPOSED STANDARD
- Stream
- IETF
- Area
- sec
- Pages
- 10
- Also known as
- —
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 6063Dynamic Symmetric Key Provisioning Protocol (DSKPP)Current
December 2010
- RFC 6066Transport Layer Security (TLS) Extensions: Extension DefinitionsUpdated
January 2011
- RFC 6071IP Security (IPsec) and Internet Key Exchange (IKE) Document RoadmapCurrent
February 2011
- RFC 6031Cryptographic Message Syntax (CMS) Symmetric Key Package Content TypeCurrent
December 2010
- RFC 6030Portable Symmetric Key Container (PSKC)Current
October 2010
- RFC 6027IPsec Cluster Problem StatementCurrent
October 2010
- RFC 6025ASN.1 TranslationCurrent
October 2010
- RFC 6024Trust Anchor Management RequirementsCurrent
October 2010
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?