RFC 6188: The Use of AES-192 and AES-256 in Secure RTP
In plain English — editorial summary, not part of the RFC
This memo describes the use of the Advanced Encryption Standard (AES) with 192- and 256-bit keys within the Secure RTP (SRTP) protocol. It details counter mode encryption for SRTP and Secure Realtime Transport Control Protocol (SRTCP) and a new SRTP Key Derivation Function (KDF) for AES-192 and AES-256. [STANDARDS-TRACK]
Document record
- Document ID
- RFC6188
- Published
- March 2011
- Authors
- D. McGrew
- Status
- PROPOSED STANDARD
- Stream
- IETF
- Area
- rai
- Pages
- 16
- Also known as
- —
Topics
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 5479Requirements and Analysis of Media Security Management ProtocolsCurrent
April 2009
- RFC 3711The Secure Real-time Transport Protocol (SRTP)Updated
March 2004
- RFC 6043MIKEY-TICKET: Ticket-Based Modes of Key Distribution in Multimedia Internet KEYing (MIKEY)Updated
March 2011
- RFC 5197On the Applicability of Various Multimedia Internet KEYing (MIKEY) Modes and ExtensionsCurrent
June 2008
- RFC 7201Options for Securing RTP SessionsCurrent
April 2014
- RFC 7202Securing the RTP Framework: Why RTP Does Not Mandate a Single Media Security SolutionCurrent
April 2014
- RFC 5027Security Preconditions for Session Description Protocol (SDP) Media StreamsCurrent
October 2007
- RFC 4738MIKEY-RSA-R: An Additional Mode of Key Distribution in Multimedia Internet KEYing (MIKEY)Current
November 2006
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?