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

In plain English — editorial summary, not part of the RFC

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.

Document record

Document ID

RFC7202

Published

April 2014

Authors

C. Perkins; M. Westerlund

Status

INFORMATIONAL

Stream

IETF

Area

wit

Pages

10

Also known as

—

• Read the full RFC text →
• Plain text version
• IETF Datatracker history
• DOI: 10.17487/RFC7202

Topics

• SRTP
• RTP Profile
• Payload Format

Related documents

Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.

• RFC 7201Options for Securing RTP SessionsCurrent

  April 2014

• RFC 8269The ARIA Algorithm and Its Use with the Secure Real-Time Transport Protocol (SRTP)Current

  October 2017

• RFC 9335Completely Encrypting RTP Header Extensions and Contributing SourcesCurrent

  January 2023

• RFC 8088How to Write an RTP Payload FormatUpdated

  May 2017

• RFC 6188The Use of AES-192 and AES-256 in Secure RTPCurrent

  March 2011

• RFC 6043MIKEY-TICKET: Ticket-Based Modes of Key Distribution in Multimedia Internet KEYing (MIKEY)Updated

  March 2011

• RFC 8643An Opportunistic Approach for Secure Real-time Transport Protocol (OSRTP)Current

  August 2019

• RFC 8723Double Encryption Procedures for the Secure Real-Time Transport Protocol (SRTP)Current

  April 2020

Also filed under

• INFORMATIONAL
• 2014
• IETF stream
• wit area