The Secure Real-time Transport Protocol (SRTP)

Baugher, Mark; McGrew, David; Näslund, Mats; Carrara, Elisabetta; Norrman, Karl

doi:10.17487/rfc3711

Cited by 474 publications

(415 citation statements)

References 20 publications

Supporting

Mentioning

402

Contrasting

Unclassified

Order By: Relevance

“…This is indeed true if we assume that plain RTP and RTCP are being handled, but they may not be once any security is enforced on RTP packets and RTCP messages by means of Secure RTP (SRTP) [RFC3711].…”

Section: Security Considerationsmentioning

confidence: 99%

Guidelines for End-to-End Support of the RTP Control Protocol (RTCP) in Back-to-Back User Agents (B2BUAs)

Miniero¹,

Pascual²,

Murillo³

2017

View full text Add to dashboard Cite

SIP Back-to-Back User Agents (B2BUAs) are often designed to also be on the media path, rather than just to intercept signalling. This means that B2BUAs often implement an RTP or RTP Control Protocol (RTCP) stack as well, thus leading to separate multimedia sessions that the B2BUA correlates and bridges together. If not disciplined, this behaviour can severely impact the communication experience, especially when statistics and feedback information contained in RTCP messages get lost because of mismatches in the reported data.This document defines the proper behaviour B2BUAs should follow when acting on both the signalling plane and media plane in order to preserve the end-to-end functionality of RTCP.

show abstract

Section: Security Considerationsmentioning

confidence: 99%

Guidelines for End-to-End Support of the RTP Control Protocol (RTCP) in Back-to-Back User Agents (B2BUAs)

Miniero¹,

Pascual²,

Murillo³

2017

View full text Add to dashboard Cite

show abstract

“…[More specific rules only need to be included if some parameter does not match these RTP packets using the payload format defined in this specification are subject to the security considerations discussed in the RTP specification [RFC3550] , and in any applicable RTP profile such as RTP/AVP [RFC3551], RTP/AVPF [RFC4585], RTP/SAVP [RFC3711], or RTP/ SAVPF [RFC5124]. However, as "Securing the RTP Protocol Framework: Why RTP Does Not Mandate a Single Media Security Solution" [RFC7202] discusses, it is not an RTP payload format's responsibility to discuss or mandate what solutions are used to meet the basic security goals like confidentiality, integrity, and source authenticity for RTP in general.…”

Section: A112 Mapping To Sdpmentioning

confidence: 99%

How to Write an RTP Payload Format

Westerlund¹

2017

View full text Add to dashboard Cite

show abstract

“…The "UDP/DCCP/RTP/SAVP" protocol identifier refers to RTP using the Secure Real-time Transport Protocol [RFC3711] running over the DCCP-UDP encapsulation.…”

Section: Signalling the Use Of Dccp-udpmentioning

confidence: 99%

DCCP-UDP: A Datagram Congestion Control Protocol UDP Encapsulation for NAT Traversal

Phelan¹,

Fairhurst²,

Perkins³

2012

View full text Add to dashboard Cite

This document specifies an alternative encapsulation of the Datagram Congestion Control Protocol (DCCP), referred to as DCCP-UDP. This encapsulation allows DCCP to be carried through the current generation of Network Address Translation (NAT) middleboxes without modification of those middleboxes. This document also updates the Session Description Protocol (SDP) information for DCCP defined in RFC 5762.

show abstract

The Secure Real-time Transport Protocol (SRTP)

Cited by 474 publications

References 20 publications

Guidelines for End-to-End Support of the RTP Control Protocol (RTCP) in Back-to-Back User Agents (B2BUAs)

Guidelines for End-to-End Support of the RTP Control Protocol (RTCP) in Back-to-Back User Agents (B2BUAs)

How to Write an RTP Payload Format

DCCP-UDP: A Datagram Congestion Control Protocol UDP Encapsulation for NAT Traversal

Contact Info

Product

Resources

About