RFC 5116: An Interface and Algorithms for Authenticated Encryption
In plain English — editorial summary, not part of the RFC
This document defines algorithms for Authenticated Encryption with Associated Data (AEAD), and defines a uniform interface and a registry for such algorithms. The interface and registry can be used as an application-independent set of cryptoalgorithm suites. This approach provides advantages in efficiency and security, and promotes the reuse of crypto implementations. [STANDARDS-TRACK]
Document record
- Document ID
- RFC5116
- Published
- January 2008
- Authors
- D. McGrew
- Status
- PROPOSED STANDARD
- Stream
- IETF
- Area
- —
- Pages
- 22
- Also known as
- —
Topics
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 5403RPCSEC_GSS Version 2Updated
February 2009
- RFC 3647Internet X.509 Public Key Infrastructure Certificate Policy and Certification Practices FrameworkCurrent
November 2003
- RFC 6655AES-CCM Cipher Suites for Transport Layer Security (TLS)Updated
July 2012
- RFC 3195Reliable Delivery for syslogCurrent
November 2001
- RFC 3156MIME Security with OpenPGPCurrent
August 2001
- RFC 2866RADIUS AccountingUpdated
June 2000
- RFC 7435Opportunistic Security: Some Protection Most of the TimeCurrent
December 2014
- RFC 7590Use of Transport Layer Security (TLS) in the Extensible Messaging and Presence Protocol (XMPP)Current
June 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?