RTP (Real-time Transport Protocol)
This article was accepted into the corpus but its outbound wikilinks were never NER-processed — typical at the deepest BFS hop or when the run's entity cap was reached. No expansion funnel to show.
| RTP (Real-time Transport Protocol) | |
|---|---|
.png) | |
| Name | RTP |
| Caption | Real-time data transport in multimedia systems |
| Developer | Audio–Video Transport Working Group, Internet Engineering Task Force |
| Introduced | 1996 |
| Os | Cross-platform |
| License | Various (open source, proprietary) |
RTP (Real-time Transport Protocol) is an Internet protocol for delivering audio, video, and other time-sensitive data over packet-switched networks. It was standardized by the Internet Engineering Task Force and designed to interoperate with signaling and session protocols used by systems developed by organizations such as Cisco Systems, Apple Inc., Microsoft, and Google. RTP commonly operates with companion protocols used by implementations from vendors including Polycom, Avaya, Zoom Video Communications, and research groups at institutions like Massachusetts Institute of Technology and Stanford University.
Overview
RTP provides end-to-end network transport functions suitable for applications developed by groups such as the IETF, European Telecommunications Standards Institute, 3rd Generation Partnership Project, and standards bodies like the International Telecommunication Union. It is often used alongside session control frameworks authored in documents by contributors from Bell Labs, Nokia, Ericsson, and Alcatel-Lucent. Major deployments appear in products by Skype Technologies S.A., Cisco Systems, and cloud services from Amazon Web Services and Microsoft Azure, while academic evaluations have been performed at Carnegie Mellon University and University of California, Berkeley.
Protocol Design and Architecture
RTP's architecture reflects designs used in projects at Bell Labs, Xerox PARC, and the University of Cambridge multimedia labs. The protocol separates media delivery from control and session management, a design pattern also adopted by Session Initiation Protocol work from the IETF and by systems developed at Sun Microsystems and IBM. RTP is implemented on top of User Datagram Protocol stacks originally used by vendors such as Juniper Networks and Netgear, and it aligns with timing and synchronization concepts explored by researchers at MIT Media Lab and ETH Zurich.
Packet Structure and Payload Formats
RTP packets include headers that carry sequence numbers, timestamps, and payload type identifiers, concepts analogous to packet formats defined by engineers at Bell Labs, AT&T Laboratories, and Siemens AG. Payload formats are specified for codecs and formats standardized by organizations like Moving Picture Experts Group, 3GPP, Advanced Television Systems Committee, and codec developers including Fraunhofer Society (for MP3) and SIP Forum contributors. Implementations in consumer products from Samsung Electronics, LG Electronics, and Sony Corporation map media frames from codecs such as formats created by H.264 authors and the Opus working group.
Control Protocols and RTCP
RTP is paired with the Real-time Transport Control Protocol, developed in IETF working groups with participation from companies like Polycom, Cisco Systems, and academic institutions such as University College London. RTCP provides statistics and control messages, a design influenced by monitoring work at Bellcore and evaluation frameworks from RIPE NCC and IAB. Control interactions are integrated in conferencing systems produced by Zoom Video Communications, BlueJeans Network, and enterprise telephony suites from Avaya.
Security and Encryption
Security extensions for RTP were developed in collaboration with cryptography research originating at RSA Security, IETF, and academic labs including ETH Zurich and University of Cambridge Computer Laboratory. Approaches include SRTP developed by companies such as Cisco Systems and Cisco's partners, and key management mechanisms that reference standards influenced by NIST and protocols from IETF working groups. Encryption and authentication are applied in products from Google LLC, Apple Inc., and messaging platforms such as WhatsApp, reflecting adoption by mobile ecosystems led by Samsung Electronics and operators like Verizon Communications.
Implementations and Applications
RTP implementations exist in open-source projects maintained by communities around Free Software Foundation and organizations like the Apache Software Foundation and Mozilla Foundation. Commercial stacks are offered by Cisco Systems, Avaya, Polycom, and start-ups incubated by Y Combinator. Applications include video conferencing by Zoom Video Communications, streaming services by Netflix, telephony systems in deployments by AT&T and Deutsche Telekom, and live-event streaming platforms used by BBC and CNN.
Performance, Timing, and QoS
RTP timing mechanisms draw on work from timing research at National Institute of Standards and Technology and synchronization systems such as Network Time Protocol deployments by the IETF. Quality of Service considerations intersect with architectures promoted by Cisco Systems and standards from the Internet Engineering Task Force, and have been evaluated in trials by carriers like Telefonica and Vodafone Group. Performance tuning appears in products from Intel Corporation and AMD for CPU optimization, and in networking gear from Arista Networks and Huawei Technologies for packet scheduling and policing.
Category:Internet protocols Category:Streaming media