RFC 4494: The AES-CMAC-96 Algorithm and Its Use with IPsec
In plain English — editorial summary, not part of the RFC
The National Institute of Standards and Technology (NIST) has recently specified the Cipher-based Message Authentication Code (CMAC), which is equivalent to the One-Key CBC-MAC1 (OMAC1) algorithm submitted by Iwata and Kurosawa. OMAC1 efficiently reduces the key size of Extended Cipher Block Chaining mode (XCBC). This memo specifies the use of CMAC mode as an authentication mechanism of the IPsec Encapsulating Security Payload (ESP) and the Authentication Header (AH) protocols. This new algorithm is named AES-CMAC-96. [STANDARDS-TRACK]
Document record
- Document ID
- RFC4494
- Published
- June 2006
- Authors
- JH. Song; R. Poovendran; J. Lee
- Status
- PROPOSED STANDARD
- Stream
- IETF
- Area
- —
- Pages
- 8
- Also known as
- —
Topics
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 4493The AES-CMAC AlgorithmCurrent
June 2006
- RFC 4434The AES-XCBC-PRF-128 Algorithm for the Internet Key Exchange Protocol (IKE)Current
February 2006
- RFC 4106The Use of Galois/Counter Mode (GCM) in IPsec Encapsulating Security Payload (ESP)Current
June 2005
- RFC 3853S/MIME Advanced Encryption Standard (AES) Requirement for the Session Initiation Protocol (SIP)Current
July 2004
- RFC 5288AES Galois Counter Mode (GCM) Cipher Suites for TLSUpdated
August 2008
- RFC 3686Using Advanced Encryption Standard (AES) Counter Mode With IPsec Encapsulating Security Payload (ESP)Current
January 2004
- RFC 3664The AES-XCBC-PRF-128 Algorithm for the Internet Key Exchange Protocol (IKE)Obsoleted
January 2004
- RFC 3565Use of the Advanced Encryption Standard (AES) Encryption Algorithm in Cryptographic Message Syntax (CMS)Current
July 2003
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?