Securing the RTP Framework: Why RTP Does Not Mandate a Single Media Security Solution

Metadata

Publisher: IETF
Doc Type: Informational
Pages: 10
Abstract: This memo discusses the problem of securing real-time multimedia sessions. It also explains why the Real-time Transport Protocol (RTP) and the associated RTP Control Protocol (RTCP) do not mandate a single media security mechanism. This is relevant for designers and reviewers of future RTP extensions to ensure that appropriate security mechanisms are mandated and that any such mechanisms are specified in a manner that conforms with the RTP architecture.
Publication Date: 2014-04-01
Status Note: Informational
DOI: 10.17487/RFC7202
Link: https://doi.org/10.17487/RFC7202
Author(s): Colin Perkins
Magnus Westerlund
Keyword(s): SRTP, RTP Profile

Latest version of IETF RFC 7202

Document Versions — IETF RFC 7202

▶ IETF RFC 7202 (2014-04-01)

THIS DOC [ACTIVE] [LATEST VERSION]

Bibliographic Reference(s)

3GPP.TS-26.346.201303 — T3GPP.26.346 EXTERNAL
Internet Streaming Media Alliance (ISMA), "ISMA Encryption and Authentication Version 2.0", November 2007, < http://www.oipf.tv/images/site/DOCS/mpegif/ISMA/ isma_easpec2.0.pdf >. EXTERNAL
Schulzrinne, H., Rao, A., Lanphier, R., Westerlund, M., and M. Stiemerling, "Real Time Streaming Protocol 2.0 (RTSP)", Work in Progress, February 2014. EXTERNAL
Rescorla, E., "WebRTC Security Architecture" , Work in Progress, February 2014. EXTERNAL
IETF RFC 768 [Active*]
IETF RFC 793 [Superseded*]
IETF RFC 3365 [Active*]
IETF RFC 3550 [Active*]
IETF RFC 3711 [Active*]
IETF RFC 4340 [Active*]
IETF RFC 4585 [Active*]
IETF RFC 4614 [Superseded*]
IETF RFC 5479 [Active*]
IETF RFC 7201 [Active*]

Source Data (JSON)

Full registry record with provenance metadata. Open directly: /api/doc/RFC7202.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 7202, Securing the RTP Framework: Why RTP Does Not Mandate a Single Media Security Solution. Available at https://doi.org/10.17487/RFC7202

Snippet:

IETF RFC 7202, Securing the RTP Framework: Why RTP Does Not Mandate a Single Media Security Solution. Available at https://doi.org/10.17487/RFC7202

HTML (ISO 690 compliant)

Preview:

IETF RFC 7202, Securing the RTP Framework: Why RTP Does Not Mandate a Single Media Security Solution. Available at https://doi.org/10.17487/RFC7202

Snippet:

<span class="citation"><cite>IETF RFC 7202</cite>, Securing the RTP Framework: Why RTP Does Not Mandate a Single Media Security Solution. Available at <a href="https://doi.org/10.17487/RFC7202" target="_blank" rel="noopener">https://doi.org/10.17487/RFC7202</a></span>

SMPTE's HTML Pub

Preview:

IETF RFC 7202, Securing the RTP Framework: Why RTP Does Not Mandate a Single Media Security Solution
doi: 10.17487/RFC7202
url: https://doi.org/10.17487/RFC7202

Snippet:

<li>
<cite id="bib-rfc7202">IETF RFC 7202</cite>, Securing the RTP Framework: Why RTP Does Not Mandate a Single Media Security Solution
<span class="doi">10.17487/RFC7202</span>
</li>

Referenced By

IETF RFC 7201 [Active*]
IETF RFC 7587 [Active*]
IETF RFC 8088 [Active*]
IETF RFC 8860 [Active*]
IETF RFC 9134 [Active*]