RFC 7201

Options for Securing RTP Sessions, April 2014

File formats:
icon for text file icon for PDF icon for HTML
Status:
INFORMATIONAL
Authors:
M. Westerlund
C. Perkins
Stream:
IETF
Source:
avtcore (wit)

Cite this RFC: TXT  |  XML  |   BibTeX

DOI:  https://doi.org/10.17487/RFC7201

Discuss this RFC: Send questions or comments to the mailing list avt@ietf.org

Other actions: Submit Errata  |  Find IPR Disclosures from the IETF  |  View History of RFC 7201


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.


For the definition of Status, see RFC 2026.

For the definition of Stream, see RFC 8729.




Advanced Search