RFC 7714: AES-GCM Authenticated Encryption in the Secure Real-time Transport Protocol (SRTP)
In plain English — editorial summary, not part of the RFC
This document defines how the AES-GCM Authenticated Encryption with Associated Data family of algorithms can be used to provide confidentiality and data authentication in the Secure Real-time Transport Protocol (SRTP).
Document record
- Document ID
- RFC7714
- Published
- December 2015
- Authors
- D. McGrew; K. Igoe
- Status
- PROPOSED STANDARD
- Stream
- IETF
- Area
- wit
- Pages
- 48
- Also known as
- —
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 7725An HTTP Status Code to Report Legal ObstaclesCurrent
February 2016
- RFC 7694Hypertext Transfer Protocol (HTTP) Client-Initiated Content-EncodingObsoleted
November 2015
- RFC 7736Content Delivery Network Interconnection (CDNI) Media Type RegistrationCurrent
December 2015
- RFC 7742WebRTC Video Processing and Codec RequirementsCurrent
March 2016
- RFC 7675Session Traversal Utilities for NAT (STUN) Usage for Consent FreshnessCurrent
October 2015
- RFC 7667RTP TopologiesCurrent
November 2015
- RFC 7765TCP and Stream Control Transmission Protocol (SCTP) RTO RestartCurrent
February 2016
- RFC 7661Updating TCP to Support Rate-Limited TrafficCurrent
October 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?