API Build-data JSON Resources
Theme

Choose how MSRBot.io looks on this device.

Preference is stored in this browser only.

IETF RFC 6188
[ACTIVE]

The Use of AES-192 and AES-256 in Secure RTP

Metadata

Publisher
IETF
Doc Type
Standard
Pages
16
Abstract
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]
Publication Date
2011-03-01
Status Note
Proposed Standard
DOI
10.17487/RFC6188
Link
https://doi.org/10.17487/RFC6188
Author(s)
David McGrew
Keyword(s)
SRTP
Latest version of IETF RFC 6188

Document Versions — IETF RFC 6188

  • ▶ IETF RFC 6188 (2011-03-01)
    THIS DOC [ACTIVE] [LATEST VERSION]
Source Data (JSON)

Full registry record with provenance metadata. Open directly: /api/doc/RFC6188.json

Reference Tree

Explore all references and references to this document, as a navigable tree.

Open Reference Tree
Reference this Doc

Plain text (ISO 690 compliant)

Preview:
IETF RFC 6188, The Use of AES-192 and AES-256 in Secure RTP. Available at https://doi.org/10.17487/RFC6188
Snippet:
IETF RFC 6188, The Use of AES-192 and AES-256 in Secure RTP. Available at https://doi.org/10.17487/RFC6188

HTML (ISO 690 compliant)

Preview:
IETF RFC 6188, The Use of AES-192 and AES-256 in Secure RTP. Available at https://doi.org/10.17487/RFC6188
Snippet:
<span class="citation"><cite>IETF RFC 6188</cite>, The Use of AES-192 and AES-256 in Secure RTP. Available at <a href="https://doi.org/10.17487/RFC6188" target="_blank" rel="noopener">https://doi.org/10.17487/RFC6188</a></span>

SMPTE Icon SMPTE's HTML Pub

Preview:
IETF RFC 6188, The Use of AES-192 and AES-256 in Secure RTP
doi: 10.17487/RFC6188
url: https://doi.org/10.17487/RFC6188
Snippet:
<li>
<cite id="bib-rfc6188">IETF RFC 6188</cite>, The Use of AES-192 and AES-256 in Secure RTP
<span class="doi">10.17487/RFC6188</span>
</li>

Referenced By