RFC 7826: Real-Time Streaming Protocol Version 2.0
In plain English — editorial summary, not part of the RFC
This memorandum defines the Real-Time Streaming Protocol (RTSP) version 2.0, which obsoletes RTSP version 1.0 defined in RFC 2326. RTSP is an application-layer protocol for the setup and control of the delivery of data with real-time properties. RTSP provides an extensible framework to enable controlled, on-demand delivery of real-time data, such as audio and video. Sources of data can include both live data feeds and stored clips. This protocol is intended to control multiple data delivery sessions; provide a means for choosing delivery channels such as UDP, multicast UDP, and TCP; and provide a means for choosing delivery mechanisms based upon RTP (RFC 3550).
Document record
- Document ID
- RFC7826
- Published
- December 2016
- Authors
- H. Schulzrinne; A. Rao; R. Lanphier; M. Westerlund; M. Stiemerling
- Status
- PROPOSED STANDARD
- Stream
- IETF
- Area
- art
- Pages
- 318
- Also known as
- —
- Obsoletes:
- RFC 2326
Topics
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 8843Negotiating Media Multiplexing Using the Session Description Protocol (SDP)Obsoleted
January 2021
- RFC 8866SDP: Session Description ProtocolCurrent
January 2021
- RFC 9143Negotiating Media Multiplexing Using the Session Description Protocol (SDP)Current
February 2022
- RFC 6064SDP and RTSP Extensions Defined for 3GPP Packet-Switched Streaming Service and Multimedia Broadcast/Multicast ServiceCurrent
January 2011
- RFC 7825A Network Address Translator (NAT) Traversal Mechanism for Media Controlled by the Real-Time Streaming Protocol (RTSP)Current
December 2016
- RFC 7840A Routing Request Extension for the HTTP-Enabled Location Delivery (HELD) ProtocolCurrent
May 2016
- RFC 7809Calendaring Extensions to WebDAV (CalDAV): Time Zones by ReferenceCurrent
March 2016
- RFC 7808Time Zone Data Distribution ServiceCurrent
March 2016
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?