RFC 4309: Using Advanced Encryption Standard (AES) CCM Mode with IPsec Encapsulating Security Payload (ESP)
In plain English — editorial summary, not part of the RFC
This document describes the use of Advanced Encryption Standard (AES) in Counter with CBC-MAC (CCM) Mode, with an explicit initialization vector (IV), as an IPsec Encapsulating Security Payload (ESP) mechanism to provide confidentiality, data origin authentication, and connectionless integrity. [STANDARDS-TRACK]
Document record
- Document ID
- RFC4309
- Published
- December 2005
- Authors
- R. Housley
- Status
- PROPOSED STANDARD
- Stream
- IETF
- Area
- sec
- Pages
- 13
- Also known as
- —
Topics
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 4312The Camellia Cipher Algorithm and Its Use With IPsecCurrent
December 2005
- RFC 4303IP Encapsulating Security Payload (ESP)Current
December 2005
- RFC 4302IP Authentication HeaderCurrent
December 2005
- RFC 4301Security Architecture for the Internet ProtocolUpdated
December 2005
- RFC 4503A Description of the Rabbit Stream Cipher AlgorithmCurrent
May 2006
- RFC 5288AES Galois Counter Mode (GCM) Cipher Suites for TLSUpdated
August 2008
- RFC 5930Using Advanced Encryption Standard Counter Mode (AES-CTR) with the Internet Key Exchange version 02 (IKEv2) ProtocolCurrent
July 2010
- RFC 9216S/MIME Example Keys and CertificatesCurrent
April 2022
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?