Securing the RTP Framework: Why RTP Does Not Mandate a Single Media Security Solution
RFC 7202, “Securing the RTP Framework: Why RTP Does Not Mandate a Single Media Security Solution”, is an Informational document published in April 2014 by C. Perkins, M. Westerlund. The canonical text is published by the RFC Editor.
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.
What “Informational” means
Published for the general information of the community. It does not define an IETF standard and carries no standards-track status.
The canonical text of RFC 7202 is hosted at rfc-editor.org. Available in TXT,HTML.
- RFC 7201 Options for Securing RTP Sessions
- RFC 7203 An Incident Object Description Exchange Format Extension for Structured Cybersecurity Information
- RFC 7200 A Session Initiation Protocol Load-Control Event Package
- RFC 7204 Requirements for Labeled NFS
- RFC 7199 Location Configuration Extensions for Policy Management
- RFC 7205 Use Cases for Telepresence Multistreams
- RFC 7198 Duplicating RTP Streams
- RFC 7206 Requirements for an End-to-End Session Identification in IP-Based Multimedia Communication Networks