RFC 3711: The Secure Real-time Transport Protocol (SRTP)
In plain English — editorial summary, not part of the RFC
This document describes the Secure Real-time Transport Protocol (SRTP), a profile of the Real-time Transport Protocol (RTP), which can provide confidentiality, message authentication, and replay protection to the RTP traffic and to the control traffic for RTP, the Real-time Transport Control Protocol (RTCP). [STANDARDS-TRACK]
Document record
- Document ID
- RFC3711
- Published
- March 2004
- Authors
- M. Baugher; D. McGrew; M. Naslund; E. Carrara; K. Norrman
- Status
- PROPOSED STANDARD
- Stream
- IETF
- Area
- rai
- Pages
- 56
- Also known as
- —
Topics
Referenced by
3 later RFCs formally update or obsolete part of this document.
- RFC 5506Support for Reduced-Size Real-Time Transport Control Protocol (RTCP): Opportunities and ConsequencesCurrent
April 2009
- RFC 6904Encryption of Header Extensions in the Secure Real-time Transport Protocol (SRTP)Current
April 2013
- RFC 9335Completely Encrypting RTP Header Extensions and Contributing SourcesCurrent
January 2023
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 3511Benchmarking Methodology for Firewall PerformanceObsoleted
April 2003
- RFC 3129Requirements for Kerberized Internet Negotiation of KeysCurrent
June 2001
- RFC 4568Session Description Protocol (SDP) Security Descriptions for Media StreamsCurrent
July 2006
- RFC 2510Internet X.509 Public Key Infrastructure Certificate Management ProtocolsObsoleted
March 1999
- RFC 5479Requirements and Analysis of Media Security Management ProtocolsCurrent
April 2009
- RFC 5922Domain Certificates in the Session Initiation Protocol (SIP)Current
June 2010
- RFC 5923Connection Reuse in the Session Initiation Protocol (SIP)Current
June 2010
- RFC 6188The Use of AES-192 and AES-256 in Secure RTPCurrent
March 2011
Also filed under
About this page
The document record above — title, authors, date, status, stream, area, relationships, DOI and errata — is imported verbatim from the public RFC Editor index. The “in plain English” section is editorial: written by The metasystema editorial team, not part of the RFC. Where the two differ, the RFC text governs.
Last checked against the RFC Editor index on . RFCs are never revised after publication; changes are issued as new documents.
Data sources · Editorial policy · Report a correction · What is an RFC?