RTP (protocol)

RTP (protocol)
Name	RTP
Title	Real-time Transport Protocol
Introduced	1996
Standard	Internet Engineering Task Force
Author	Henning Schulzrinne, Stephen Casner, R. Frederick (Fred)],?

RTP (protocol) RTP is a network protocol for end-to-end delivery of real-time data such as audio and video across packet-switched networks. It was standardized by the Internet Engineering Task Force and is widely used in conjunction with signaling protocols and media codecs developed by organizations and projects like IETF Media Area, 3GPP, ITU-T, H.323, Session Initiation Protocol, and SIP Forum. RTP is integral to many products and services from vendors and initiatives including Apple Inc., Google, Microsoft, Cisco Systems, and Zoom Video Communications.

Overview

RTP originates from work by researchers active in the Internet Engineering Task Force and research groups at institutions such as Columbia University, University of Massachusetts Amherst, Massachusetts Institute of Technology, and companies including Lucent Technologies. It is specified in standards published by the IETF and incorporated into multimedia architectures from 3GPP releases through 4G and 5G NR ecosystems, as well as multimedia conferencing systems like H.323 suites and SIP deployments. RTP operates over packet networks such as IPv4, IPv6, and can be carried by transport protocols like User Datagram Protocol and encapsulated in tunneling technologies developed by Internet Engineering Task Force working groups and proprietary stacks from Cisco Systems and Juniper Networks.

Protocol Design and Architecture

RTP follows a layered architecture designed by contributors from academic and standards communities including Henning Schulzrinne and Stephen Casner. It separates media transport from signaling such as Session Initiation Protocol and control like Real Time Control Protocol. RTP sessions are identified with parameters exchanged via session description formats from IETF SDP and provisioning systems from 3GPP management specifications. The architecture supports extensions designed by working groups in the IETF and collaborations with bodies such as ETSI, ITU-T, and industry consortia including GStreamer and WebRTC implementers like Google and Mozilla Foundation.

Packet Format and Header Fields

The RTP header format is defined in standards from the IETF and includes fields such as version, padding, extension, contributing source identifiers, marker bits, payload type, sequence number, timestamp, and synchronization source identifier. Those fields interact with codec payload formats standardized by organizations like IETF Audio/Video Transport Working Group, codec designers at Fraunhofer IIS (MP3, AAC), Xiph.Org Foundation (Opus), and standards from ISO/IEC and ITU-T (H.264, H.265). Header extension mechanisms and profile-specific mappings are specified in RFCs and informed by projects such as WebRTC, implementations in FFmpeg, GStreamer, Live555, and integration into multimedia servers like Kurento and Asterisk (PBX).

Transport and Codec Adaptation

RTP is codec-agnostic and relies on payload type identifiers and dynamic negotiation via protocols like SIP, SDP, and media negotiation frameworks used by WebRTC, IMS, and 3GPP IP Multimedia Subsystem. Adaptation strategies are deployed in systems from Netflix, YouTube, Zoom, Microsoft Teams, and Skype to handle bitrate changes, scalable codecs from Fraunhofer IIS and Google (Opus, VP8, VP9, AV1), and layering approaches such as Scalable Video Coding and simulcast used by WebRTC and 3GPP video services. Transport interaction includes techniques from QUIC initiatives, performance profiling with iperf, and congestion control algorithms evolving from research at MIT and Stanford University.

Control Protocols: RTCP and QoS

RTP is paired with RTCP for session control, quality reporting, and participant identification; RTCP reports are leveraged by conference controllers and monitoring systems from vendors such as Cisco Systems, Avaya, and Polycom. Quality of service mechanisms interact with network-layer facilities like Differentiated Services and Integrated Services and are considered in operator deployments by carriers including AT&T, Verizon Communications, Deutsche Telekom, and China Mobile. Performance monitoring uses metrics standardized in IETF documents and analyzed by tools from Wireshark, SolarWinds, and research platforms at Bell Labs and Nokia Bell Labs.

Security and Authentication

Security extensions for RTP include SRTP developed by contributors from Cisco Systems, Ericsson, and the IETF SRTP Working Group, offering confidentiality, message authentication, and replay protection. Key management and signaling security integrate with protocols and frameworks such as DTLS, SDES, ZRTP, MIKEY, and SIPS used by implementations from Mozilla Foundation, Google, and enterprise solutions by Cisco Systems and Microsoft. Authentication and authorization often tie into identity systems like OAuth 2.0, SAML, and enterprise directory services from Microsoft Active Directory and LDAP deployments.

Implementations and Applications

RTP is implemented in open-source projects including FFmpeg, GStreamer, LibAV, OpenH264, WebRTC stacks by Google and Mozilla Foundation, and telephony engines like Asterisk (PBX) and FreeSWITCH. Commercial implementations appear in products from Cisco Systems, Polycom, Avaya, Microsoft Teams, Zoom, and Skype for Business. Use cases span internet telephony in platforms such as Vonage, video streaming by Netflix and YouTube, unified communications in Microsoft, healthcare telemedicine systems at institutions like Mayo Clinic and Johns Hopkins Hospital, and real-time gaming and virtual reality systems developed by Epic Games and Unity Technologies.

Category:Network protocols