[ppsp] RFC 7574 on Peer-to-Peer Streaming Peer Protocol (PPSPP)

rfc-editor@rfc-editor.org Thu, 09 July 2015 22:41 UTC

Return-Path: <wwwrun@rfc-editor.org>
X-Original-To: ppsp@ietfa.amsl.com
Delivered-To: ppsp@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com []) by ietfa.amsl.com (Postfix) with ESMTP id A061C1A1BFA; Thu, 9 Jul 2015 15:41:04 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.912
X-Spam-Status: No, score=-106.912 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_HI=-5, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01, USER_IN_WHITELIST=-100] autolearn=ham
Received: from mail.ietf.org ([]) by localhost (ietfa.amsl.com []) (amavisd-new, port 10024) with ESMTP id lOMbikFvu6lG; Thu, 9 Jul 2015 15:40:59 -0700 (PDT)
Received: from rfc-editor.org (rfc-editor.org []) by ietfa.amsl.com (Postfix) with ESMTP id 4202B1A1B40; Thu, 9 Jul 2015 15:40:58 -0700 (PDT)
Received: by rfc-editor.org (Postfix, from userid 30) id AA249181B3D; Thu, 9 Jul 2015 15:37:20 -0700 (PDT)
To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org
X-PHP-Originating-Script: 1005:ams_util_lib.php
From: rfc-editor@rfc-editor.org
Message-Id: <20150709223720.AA249181B3D@rfc-editor.org>
Date: Thu, 09 Jul 2015 15:37:20 -0700
Archived-At: <http://mailarchive.ietf.org/arch/msg/ppsp/sDUqjNJQTlCl_Wo_nbiRBMyaI3o>
Cc: drafts-update-ref@iana.org, ppsp@ietf.org, rfc-editor@rfc-editor.org
Subject: [ppsp] RFC 7574 on Peer-to-Peer Streaming Peer Protocol (PPSPP)
X-BeenThere: ppsp@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: discussing to draw up peer to peer streaming protocol <ppsp.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ppsp>, <mailto:ppsp-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ppsp/>
List-Post: <mailto:ppsp@ietf.org>
List-Help: <mailto:ppsp-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ppsp>, <mailto:ppsp-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 09 Jul 2015 22:41:04 -0000

A new Request for Comments is now available in online RFC libraries.

        RFC 7574

        Title:      Peer-to-Peer Streaming Peer Protocol (PPSPP) 
        Author:     A. Bakker, R. Petrocco, V. Grishchenko
        Status:     Standards Track
        Stream:     IETF
        Date:       July 2015
        Mailbox:    arno@cs.vu.nl, 
        Pages:      85
        Characters: 208360
        Updates/Obsoletes/SeeAlso:   None

        I-D Tag:    draft-ietf-ppsp-peer-protocol-12.txt

        URL:        https://www.rfc-editor.org/info/rfc7574

        DOI:        http://dx.doi.org/10.17487/RFC7574

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.

This document is a product of the Peer to Peer Streaming Protocol Working Group of the IETF.

This is now a Proposed Standard.

STANDARDS TRACK: This document specifies an Internet Standards Track
protocol for the Internet community, and requests discussion and suggestions
for improvements.  Please refer to the current edition of the Official
Internet Protocol Standards (https://www.rfc-editor.org/standards) for the 
standardization state and status of this protocol.  Distribution of this 
memo is unlimited.

This announcement is sent to the IETF-Announce and rfc-dist lists.
To subscribe or unsubscribe, see

For searching the RFC series, see https://www.rfc-editor.org/search
For downloading RFCs, see https://www.rfc-editor.org/rfc.html

Requests for special distribution should be addressed to either the
author of the RFC in question, or to rfc-editor@rfc-editor.org.  Unless
specifically noted otherwise on the RFC itself, all RFCs are for
unlimited distribution.

The RFC Editor Team
Association Management Solutions, LLC