RFC 5288: AES Galois Counter Mode (GCM) Cipher Suites for TLS
In plain English — editorial summary, not part of the RFC
This memo describes the use of the Advanced Encryption Standard (AES) in Galois/Counter Mode (GCM) as a Transport Layer Security (TLS) authenticated encryption operation. GCM provides both confidentiality and data origin authentication, can be efficiently implemented in hardware for speeds of 10 gigabits per second and above, and is also well-suited to software implementations. This memo defines TLS cipher suites that use AES-GCM with RSA, DSA, and Diffie-Hellman-based key exchange mechanisms. [STANDARDS-TRACK]
Document record
- Document ID
- RFC5288
- Published
- August 2008
- Authors
- J. Salowey; A. Choudhury; D. McGrew
- Status
- PROPOSED STANDARD
- Stream
- IETF
- Area
- sec
- Pages
- 8
- Also known as
- —
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.
- RFC 3268Advanced Encryption Standard (AES) Ciphersuites for Transport Layer Security (TLS)Obsoleted
July 2002
- RFC 5289TLS Elliptic Curve Cipher Suites with SHA-256/384 and AES Galois Counter Mode (GCM)Updated
August 2008
- RFC 5487Pre-Shared Key Cipher Suites for TLS with SHA-256/384 and AES Galois Counter ModeUpdated
March 2009
- RFC 5054Using the Secure Remote Password (SRP) Protocol for TLS AuthenticationUpdated
November 2007
- RFC 4309Using Advanced Encryption Standard (AES) CCM Mode with IPsec Encapsulating Security Payload (ESP)Current
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
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?