Peer-to-Peer Streaming Peer Protocol (PPSPP)
draft-ietf-ppsp-peer-protocol-03

The information below is for an old version of the document
Document Type Active Internet-Draft (ppsp WG)
Last updated 2012-10-21
Stream IETF
Intended RFC status Proposed Standard
Formats pdf htmlized bibtex
Reviews
Stream WG state WG Document
Document shepherd None
IESG IESG state AD is watching
Consensus Boilerplate Unknown
Telechat date
Responsible AD Martin Stiemerling
Send notices to ppsp-chairs@tools.ietf.org, draft-ietf-ppsp-peer-protocol@tools.ietf.org
PPSP                                                           A. Bakker
Internet-Draft                                               R. Petrocco
Intended status: Informational                            V. Grishchenko
Expires: April 25, 2013                    Technische Universiteit Delft
                                                        October 22, 2012

              Peer-to-Peer Streaming Peer Protocol (PPSPP)
                    draft-ietf-ppsp-peer-protocol-03

Abstract

   The Peer-to-Peer Streaming Peer Protocol (PPSPP) is a transport
   protocol for disseminating the same content to a group of interested
   parties in a streaming fashion.  PPSPP supports streaming of both
   pre-recorded (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
   LEDBAT for congestion control.

Status of this Memo

   This Internet-Draft is submitted in full conformance with the
   provisions of BCP 78 and BCP 79.

   Internet-Drafts are working documents of the Internet Engineering
   Task Force (IETF).  Note that other groups may also distribute
   working documents as Internet-Drafts.  The list of current Internet-
   Drafts is at http://datatracker.ietf.org/drafts/current/.

   Internet-Drafts are draft documents valid for a maximum of six months
   and may be updated, replaced, or obsoleted by other documents at any
   time.  It is inappropriate to use Internet-Drafts as reference
   material or to cite them other than as "work in progress."

   This Internet-Draft will expire on April 25, 2013.

Copyright Notice

Bakker, et al.           Expires April 25, 2013                 [Page 1]
Internet-Draft             PPSP Peer Protocol               October 2012

   Copyright (c) 2012 IETF Trust and the persons identified as the
   document authors.  All rights reserved.

   This document is subject to BCP 78 and the IETF Trust's Legal
   Provisions Relating to IETF Documents
   (http://trustee.ietf.org/license-info) in effect on the date of
   publication of this document.  Please review these documents
   carefully, as they describe your rights and restrictions with respect
   to this document.  Code Components extracted from this document must
   include Simplified BSD License text as described in Section 4.e of
   the Trust Legal Provisions and are provided without warranty as
   described in the Simplified BSD License.

Table of Contents

   1.  Introduction . . . . . . . . . . . . . . . . . . . . . . . . .  5
     1.1.  Purpose  . . . . . . . . . . . . . . . . . . . . . . . . .  5
     1.2.  Requirements Language  . . . . . . . . . . . . . . . . . .  6
     1.3.  Terminology  . . . . . . . . . . . . . . . . . . . . . . .  6
   2.  Overall Operation  . . . . . . . . . . . . . . . . . . . . . .  8
     2.1.  Joining a Swarm  . . . . . . . . . . . . . . . . . . . . .  8
     2.2.  Exchanging Chunks  . . . . . . . . . . . . . . . . . . . .  9
     2.3.  Leaving a Swarm  . . . . . . . . . . . . . . . . . . . . .  9
   3.  Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . 10
     3.1.  HANDSHAKE  . . . . . . . . . . . . . . . . . . . . . . . . 10
     3.2.  HAVE . . . . . . . . . . . . . . . . . . . . . . . . . . . 10
     3.3.  DATA . . . . . . . . . . . . . . . . . . . . . . . . . . . 11
     3.4.  ACK  . . . . . . . . . . . . . . . . . . . . . . . . . . . 11
     3.5.  INTEGRITY  . . . . . . . . . . . . . . . . . . . . . . . . 11
     3.6.  SIGNED_INTEGRITY . . . . . . . . . . . . . . . . . . . . . 11
     3.7.  REQUEST  . . . . . . . . . . . . . . . . . . . . . . . . . 11
     3.8.  CANCEL . . . . . . . . . . . . . . . . . . . . . . . . . . 12
     3.9.  CHOKE and UNCHOKE  . . . . . . . . . . . . . . . . . . . . 12
     3.10. Peer Address Exchange and NAT Hole Punching  . . . . . . . 13
       3.10.1.  PEX_REQ and PEX_RES Messages  . . . . . . . . . . . . 13
       3.10.2.  Hole Punching via PPSPP Messages  . . . . . . . . . . 13
     3.11. Keep Alive Signalling  . . . . . . . . . . . . . . . . . . 13
     3.12. Storage Independence . . . . . . . . . . . . . . . . . . . 14
   4.  Chunk Addressing Schemes . . . . . . . . . . . . . . . . . . . 14
     4.1.  Start-End Ranges . . . . . . . . . . . . . . . . . . . . . 14
Show full document text