Options for Securing RTP Sessions
RFC 7201, “Options for Securing RTP Sessions”, is an Informational document published in April 2014 by M. Westerlund, C. Perkins. The canonical text is published by the RFC Editor.
Abstract
The Real-time Transport Protocol (RTP) is used in a large number of different application domains and environments. This heterogeneity implies that different security mechanisms are needed to provide services such as confidentiality, integrity, and source authentication of RTP and RTP Control Protocol (RTCP) packets suitable for the various environments. The range of solutions makes it difficult for RTP-based application developers to pick the most suitable mechanism. This document provides an overview of a number of security solutions for RTP and gives guidance for developers on how to choose the appropriate security mechanism.
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 7201 is hosted at rfc-editor.org. Available in TXT,HTML.
- RFC 7200 A Session Initiation Protocol Load-Control Event Package
- RFC 7202 Securing the RTP Framework: Why RTP Does Not Mandate a Single Media Security Solution
- RFC 7199 Location Configuration Extensions for Policy Management
- RFC 7203 An Incident Object Description Exchange Format Extension for Structured Cybersecurity Information
- RFC 7198 Duplicating RTP Streams
- RFC 7204 Requirements for Labeled NFS
- RFC 7197 Duplication Delay Attribute in the Session Description Protocol
- RFC 7205 Use Cases for Telepresence Multistreams