RFC 7574: Peer-to-Peer Streaming Peer Protocol (PPSPP)
In plain English — editorial summary, not part of the RFC
The Peer-to-Peer Streaming Peer Protocol (PPSPP) is a protocol for disseminating the same content to a group of interested parties in a streaming fashion. PPSPP supports streaming of both prerecorded (on- demand) and live audio/video content. It is based on the peer-to- peer paradigm, where clients consuming the content are put on equal footing with the servers initially providing the content, to create a system where everyone can potentially provide upload bandwidth. It has been designed to provide short time-till-playback for the end user and to prevent disruption of the streams by malicious peers. PPSPP has also been designed to be flexible and extensible. It can use different mechanisms to optimize peer uploading, prevent freeriding, and work with different peer discovery schemes (centralized trackers or Distributed Hash Tables). It supports multiple methods for content integrity protection and chunk addressing. Designed as a generic protocol that can run on top of various transport protocols, it currently runs on top of UDP using Low Extra Delay Background Transport (LEDBAT) for congestion control.
Document record
- Document ID
- RFC7574
- Published
- July 2015
- Authors
- A. Bakker; R. Petrocco; V. Grishchenko
- Status
- PROPOSED STANDARD
- Stream
- IETF
- Area
- tsv
- Pages
- 85
- Also known as
- —
Topics
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 7846Peer-to-Peer Streaming Tracker Protocol (PPSTP)Current
May 2016
- RFC 9317Operational Considerations for Streaming MediaCurrent
October 2022
- RFC 7567IETF Recommendations Regarding Active Queue ManagementCurrent
July 2015
- RFC 7635Session Traversal Utilities for NAT (STUN) Extension for Third-Party AuthorizationCurrent
August 2015
- RFC 7443Application-Layer Protocol Negotiation (ALPN) Labels for Session Traversal Utilities for NAT (STUN) UsagesCurrent
January 2015
- RFC 7713Congestion Exposure (ConEx) Concepts, Abstract Mechanism, and RequirementsCurrent
December 2015
- RFC 7430Analysis of Residual Threats and Possible Fixes for Multipath TCP (MPTCP)Current
July 2015
- RFC 7376Problems with Session Traversal Utilities for NAT (STUN) Long-Term Authentication for Traversal Using Relays around NAT (TURN)Current
September 2014
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?