RFC 7846: Peer-to-Peer Streaming Tracker Protocol (PPSTP)
In plain English — editorial summary, not part of the RFC
This document specifies the base Peer-to-Peer Streaming Tracker Protocol (PPSTP) version 1, an application-layer control (signaling) protocol for the exchange of meta information between trackers and peers. The specification outlines the architecture of the protocol and its functionality; it also describes message flows, message processing instructions, message formats, formal syntax, and semantics. The PPSTP enables cooperating peers to form content-streaming overlay networks to support near real-time delivery of structured media content (audio, video, and associated timed text and metadata), such as adaptive multi-rate, layered (scalable), and multi-view (3D) videos in live, time-shifted, and on-demand modes.
Document record
- Document ID
- RFC7846
- Published
- May 2016
- Authors
- R. Cruz; M. Nunes; J. Xia; R. Huang; J. Taveira; D. Lingli
- Status
- PROPOSED STANDARD
- Stream
- IETF
- Area
- tsv
- Pages
- 55
- Also known as
- —
Topics
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 7574Peer-to-Peer Streaming Peer Protocol (PPSPP)Current
July 2015
- RFC 9317Operational Considerations for Streaming MediaCurrent
October 2022
- RFC 7837IPv6 Destination Option for Congestion Exposure (ConEx)Current
May 2016
- RFC 7806On Queuing, Marking, and DroppingCurrent
April 2016
- RFC 7786TCP Modifications for Congestion Exposure (ConEx)Current
May 2016
- RFC 7778Mobile Communication Congestion Exposure ScenarioCurrent
March 2016
- RFC 7928Characterization Guidelines for Active Queue Management (AQM)Current
July 2016
- RFC 7713Congestion Exposure (ConEx) Concepts, Abstract Mechanism, and RequirementsCurrent
December 2015
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?