Generated by GPT-5-miniSRTP Secure Real-time Transport Protocol (commonly abbreviated in literature) is a profile of the Real-time Transport Protocol designed to provide confidentiality, message authentication, and replay protection for voice and video communications over packet networks. It integrates cryptographic mechanisms with media transport to secure flows used in telephony, conferencing, and streaming, interoperating with signaling protocols and key-management frameworks to enable end-to-end and hop-by-hop protection.
SRTP secures audio and video carried in RTP streams by applying symmetric encryption, message authentication codes, and sequence numbers on each RTP packet. It is deployed alongside signaling and session-control protocols such as Session Initiation Protocol, SIP, H.323, Megaco and interacts with key-exchange mechanisms like Datagram Transport Layer Security, Interactive Connectivity Establishment, Zfone-style keying proposals, and media gateway controls such as Media Gateway Control Protocol. Major standards organizations and industry consortia including Internet Engineering Task Force, 3rd Generation Partnership Project, European Telecommunications Standards Institute, and Alliance for Telecommunications Industry Solutions have referenced SRTP in interoperability profiles for endpoints, gateways, and infrastructure.
SRTP emerged from work within the Internet Engineering Task Force's secure multimedia working groups to address vulnerabilities observed in early Voice over IP deployments and streaming platforms. The initial specification was developed to complement the Real-time Transport Protocol core defined in foundational IETF documents and was later advanced through revisions and extensions to support a variety of cipher suites and authentication algorithms. Standardization influenced by interoperability events and industry testing was shaped by contributions from vendors, academic groups at institutions like Massachusetts Institute of Technology and University of California, Berkeley, and telecom bodies such as ITU-T and 3GPP. Subsequent RFCs and informational documents expanded support for crypto-agility, key-derivation techniques, and packet protection extensions tied to signaling frameworks like SIP and session description formats used by IETF working groups.
SRTP operates as a media-layer profile applied to RTP packet streams and pairs with extensions for control packets carried by RTCP. The architecture separates key management from packet processing: encryption and authentication are performed using session keys derived via key management protocols such as Datagram Transport Layer Security, MIKEY, and ZRTP, while SRTP itself specifies packet formats, header protection modes, and cryptographic context lifetimes. Core components include the cipher transformation (e.g., AES in counter mode), message authentication code algorithms (e.g., HMAC based on SHA family algorithms), rollover counters to prevent sequence wrap ambiguity, and policies for rekeying and replay-window maintenance. The design aligns with transport-layer behaviors found in RTP deployments and with signaling description mechanisms like Session Description Protocol for negotiating cryptographic suites.
SRTP provides confidentiality using symmetric ciphers (notably AES-based constructions), integrity protection and origin authentication via HMAC or AEAD constructions, and replay protection using sequence numbers and sliding windows. Anti-replay and packet-loss resilience are tuned for real-time constraints present in deployments associated with vendors such as Cisco Systems, Avaya, Polycom, and cloud providers like Amazon Web Services and Google Cloud Platform that host media-processing services. Cryptographic agility in the specification allows operators to select from algorithms documented by bodies such as National Institute of Standards and Technology and to adopt Authenticated Encryption with Associated Data modes sanctioned in IETF profiles. SRTP also anticipates header-extension privacy and selective encryption schemes referenced in research from institutions like Stanford University and Carnegie Mellon University.
SRTP has been implemented in a broad set of endpoints, softphones, media gateways, and conferencing systems from companies including Skype Technologies, Cisco Systems, Microsoft Corporation, Google LLC, Zoom Video Communications, and open-source projects such as Asterisk (PBX), Jitsi, and FreeSWITCH. Platforms embed SRTP in mobile stacks for vendors like Apple Inc. and Samsung Electronics and in embedded systems supplied by manufacturers like Polycom and Yealink. Carrier-grade deployments in fixed and mobile networks have integrated SRTP with IMS architectures standardized by 3GPP and with session border controllers produced by companies like Acme Packet and Ribbon Communications to enforce media-plane security across administrative boundaries.
SRTP is designed to minimize computational and bandwidth overhead, employing counter-mode encryption and compact authentication tags to reduce per-packet latency. Performance benchmarks conducted by research groups and vendors such as Bell Labs and Nokia compare cipher-suite choices (AES-GCM vs AES-CM with HMAC) and show trade-offs in CPU usage and packet-rate capacity on hardware from Intel Corporation and ARM Holdings. Interoperability efforts, test events organized by IETF and telecom fora like ETSI and GSMA, address mismatches in crypto-suites, keying semantics, and header-extension handling. Backwards compatibility and interworking with legacy RTP streams often require transcoding or gateway-based security termination provided by platforms from Oracle Corporation and Avaya.
SRTP is used in enterprise unified communications, cloud contact centers, telemedicine platforms, secure governmental conferencing, and military-grade voice systems where confidentiality and integrity are required. Telecommunications operators deploy SRTP in VoLTE services standardized by 3GPP, in WebRTC-based browsers like Chromium and Mozilla Firefox to secure browser-to-browser media, and in streaming scenarios for corporate webinars hosted via services from Cisco Systems and Microsoft Corporation. Regulatory and compliance contexts reference SRTP when specifying technical controls for privacy frameworks overseen by agencies such as Federal Communications Commission and standards influenced by International Organization for Standardization.
Category:Network protocols