Real-time Transport Protocol

Real-time Transport Protocol
Name	Real-time Transport Protocol
Abbreviation	RTP
Initial publication	1996
Developer	Internet Engineering Task Force
Status	Active
Application	Audio conferencing, Video conferencing, Streaming media

Real-time Transport Protocol

Real-time Transport Protocol provides packet-based delivery for time-sensitive multimedia over packet-switched networks. Designed in the 1990s within the Internet Engineering Task Force, it complements control and session protocols to support interactive audio, video, and constrained-data flows across heterogeneous networks. RTP is deployed across telephony, broadcasting, and streaming infrastructures operated by major technology firms and standards organizations.

Overview

RTP was defined by the Internet Engineering Task Force in an effort to standardize multimedia transmission alongside protocols such as Transmission Control Protocol, User Datagram Protocol, Session Initiation Protocol, Real Time Streaming Protocol, and Internet Protocol. The protocol separates media transport from signaling and session control used by systems like H.323, SIP-T, Skype, Microsoft Lync, and Google Meet. RTP sessions are commonly negotiated using formats and enumerations published by organizations including the Internet Assigned Numbers Authority, International Telecommunication Union, 3rd Generation Partnership Project, and the European Telecommunications Standards Institute. Major implementations interoperate with platforms from Apple Inc., Cisco Systems, Microsoft, Google, and Amazon (company).

Protocol Architecture and Components

RTP operates as a payload-agnostic transport layer that typically runs over User Datagram Protocol, sometimes encapsulated in Real Time Streaming Protocol tunnels or carried within Multiprotocol Label Switching domains. Its companion protocols include the Real-time Transport Control Protocol and session description formats such as Session Description Protocol and signaling systems including Session Initiation Protocol and SIP. RTP's architecture references packet sequencing, timestamping, and payload type identifiers coordinated with registries maintained by Internet Assigned Numbers Authority and analyzed by standards groups like the Internet Engineering Task Force and European Telecommunications Standards Institute.

Packet Structure and Payload Formats

An RTP packet carries a fixed header with fields for sequence number, timestamp, marker bit, payload type, and synchronization source identifier, followed by payload data and optional header extensions. Payload type numbers are assigned through registries maintained by the Internet Assigned Numbers Authority and the Internet Engineering Task Force, with media coding specified by standards such as H.264, H.265, Opus (audio codec), G.711, AAC (Advanced Audio Coding), and VP8. RTP header extensions and profile specifications allow integration with work by the Moving Picture Experts Group, ISO/IEC, Bluetooth Special Interest Group, and the 3rd Generation Partnership Project for mobile media profiles.

Transmission, Timing, and Synchronization

RTP timestamps and sequence numbers enable playout synchronization and jitter compensation in systems that integrate clock domains from devices such as Apple iPhone, Samsung Galaxy, Cisco IP Phone, and Polycom endpoints. For inter-stream synchronization, RTP leverages RTCP sender and receiver reports and references to external timing sources such as Network Time Protocol and Precision Time Protocol. RTP-based flows are frequently carried over networks designed around architectures by Cisco Systems and Juniper Networks and traverse access networks provided by carriers like AT&T, Verizon Communications, and Deutsche Telekom.

Security and Congestion Control

Security extensions such as Secure Real-time Transport Protocol were specified to provide message authentication, integrity, and confidentiality using algorithms standardized by Internet Engineering Task Force and cryptographic suites approved by bodies including the National Institute of Standards and Technology and the Federal Information Processing Standards. Congestion control mechanisms for RTP media include approaches influenced by work at Google LLC (adaptive bitrate), adaptive jitter buffering in products by Microsoft Corporation and Apple Inc., and research from universities such as Massachusetts Institute of Technology, Stanford University, and University of California, Berkeley. RTP flows often integrate with transport-layer congestion control mechanisms developed for QUIC and enhancements defined in Internet Engineering Task Force working groups.

Implementations and Use Cases

RTP is implemented in a wide range of commercial and open-source systems including Asterisk (PBX), FreeSWITCH, FFmpeg, GStreamer, VLC media player, WebRTC stacks, and enterprise solutions from Cisco Systems, Polycom, Avaya, and Microsoft Teams. Use cases encompass telephony and unified communications in deployments by Deutsche Telekom, media streaming in services by Netflix, live broadcast contribution systems used by BBC, and real-time collaboration platforms developed by Zoom Video Communications and Slack Technologies.

Interoperability and Standards Evolution

RTP interoperability has been advanced through interop events, test suites, and profiles produced by standards bodies and industry consortia including the Internet Engineering Task Force, European Telecommunications Standards Institute, 3rd Generation Partnership Project, World Wide Web Consortium, and the Alliance for Open Media. Evolution of RTP functionality continues alongside codec developments from the Moving Picture Experts Group and the Alliance for Open Media, transport innovations like QUIC, and conferencing frameworks promoted by companies such as Google LLC and Microsoft Corporation. Deployment practices and profiles are cataloged in RFCs and updated by active working groups within the Internet Engineering Task Force.

Category:Internet protocols