RFC 7202
Securing the RTP Framework: Why RTP Does Not Mandate a Single Media Security Solution, April 2014
Cite this RFC: TXT | XML | BibTeX
DOI: 10.17487/RFC7202
Discuss this RFC: Send questions or comments to the mailing list [email protected]
Other actions: Submit Errata | Find IPR Disclosures from the IETF | View History of RFC 7202
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.
For the definition of Status, see RFC 2026.
For the definition of Stream, see RFC 8729.