Re: [ppsp] I-D Action: draft-ietf-ppsp-peer-protocol-02.txt

zhangyunfei <> Wed, 20 June 2012 07:53 UTC

Return-Path: <>
Received: from localhost (localhost []) by (Postfix) with ESMTP id 9539B21F86BE for <>; Wed, 20 Jun 2012 00:53:53 -0700 (PDT)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: -97.531
X-Spam-Status: No, score=-97.531 tagged_above=-999 required=5 tests=[AWL=0.208, BAYES_00=-2.599, HTML_FONT_FACE_BAD=0.884, HTML_MESSAGE=0.001, MIME_BASE64_TEXT=1.753, RELAY_IS_221=2.222, USER_IN_WHITELIST=-100]
Received: from ([]) by localhost ( []) (amavisd-new, port 10024) with ESMTP id HjjsDUjMhvIU for <>; Wed, 20 Jun 2012 00:53:52 -0700 (PDT)
Received: from ( []) by (Postfix) with ESMTP id 1109221F85F7 for <>; Wed, 20 Jun 2012 00:53:52 -0700 (PDT)
Received: from (localhost []) by (Postfix) with ESMTP id 7733CE60B; Wed, 20 Jun 2012 15:53:50 +0800 (CST)
Received: from (unknown []) by (Postfix) with ESMTP id 56D03E5E4; Wed, 20 Jun 2012 15:53:50 +0800 (CST)
Received: from zyf-PC ([]) by (Lotus Domino Release 6.5.6) with ESMTP id 2012062015092877-11125 ; Wed, 20 Jun 2012 15:09:28 +0800
Date: Wed, 20 Jun 2012 15:09:25 +0800
From: zhangyunfei <>
To: "" <>, "Riccardo (" <>
References: <>
X-Priority: 3 (Normal)
X-Mailer: Foxmail[cn]
Mime-Version: 1.0
Message-ID: <>
X-MIMETrack: Itemize by SMTP Server on jtgsml01/servers/cmcc(Release 6.5.6|March 06, 2007) at 2012-06-20 15:09:28, Serialize by Router on jtgsml01/servers/cmcc(Release 6.5.6|March 06, 2007) at 2012-06-20 15:53:49, Serialize complete at 2012-06-20 15:53:49
Content-Type: multipart/alternative; boundary="----=_001_NextPart585374371356_=----"
X-TM-AS-Product-Ver: IMSS-
X-TM-AS-Result: No--24.157-7.0-31-10
X-imss-scan-details: No--24.157-7.0-31-10;No--24.157-7.0-31-10
X-TM-AS-User-Approved-Sender: No;No
X-TM-AS-User-Blocked-Sender: No;No
Cc: ppsp <>
Subject: Re: [ppsp] I-D Action: draft-ietf-ppsp-peer-protocol-02.txt
X-Mailman-Version: 2.1.12
Precedence: list
Reply-To: zhangyunfei <>
List-Id: discussing to draw up peer to peer streaming protocol <>
List-Unsubscribe: <>, <>
List-Archive: <>
List-Post: <>
List-Help: <>
List-Subscribe: <>, <>
X-List-Received-Date: Wed, 20 Jun 2012 07:53:53 -0000

Hi Arno and Riccardo (Speaking individually),
    Due to a following holiday started from tomorrow, I have a quick read on the draft. The following is my comments. I'll reply the emails until next week.

1) In general, this version is much better than last version in the sense of an IETF draft, instead of a paper or a technical report for the implementation. I mean the generality is better.
2)  bin numbers in 1st paragraph: Since there are at least two schemes introduced in section 4, the range scheme should be stated here as well.
3)Merkle hash tree in section 2.2:Occur for the first time without explaining before.It's better to add the term in section 1.3.
4)INTEGRITY in section 2.2: It should be stated that this message is not used all the time.
5)Section3.3: The sentence "it MUST send a ACK message containing a chunk specification for C". MUST or SHOULD.
6)Section 3.9, since TCP is abandoned by PPSPP, do we need to explain the related case?
7)  Section 4.3 PEX_ADD, no explanation before.
8)Section 6: I suggest to exclude this section  because it involves a over-strong limitation:fixed chunk size.Furthermore I am not clear of the necessity of this scheme.Just as the background of section 7?
9) Section 7:for the similar reason, remove the section 7.1.1
10)Section 9.3.2, why placed here? I suggest to remove this section. 



From: internet-drafts
Date: 2012-06-20 14:04
To: i-d-announce
CC: ppsp
Subject: [ppsp] I-D Action: draft-ietf-ppsp-peer-protocol-02.txt

A New Internet-Draft is available from the on-line Internet-Drafts directories.
 This draft is a work item of the Peer to Peer Streaming Protocol Working Group of the IETF.

Title           : Peer-to-Peer Streaming Peer Protocol (PPSPP)
Author(s)       : Arno Bakker
                          Riccardo Petrocco
Filename        : draft-ietf-ppsp-peer-protocol-02.txt
Pages           : 56
Date            : 2012-06-19

   The Peer-to-Peer Streaming Peer Protocol (PPSPP) is a peer-to-peer
   based transport protocol for content dissemination.  It can be used
   for streaming on-demand and live video content, as well as
   conventional downloading.  In PPSPP, the clients consuming the
   content participate in the dissemination by forwarding the content to
   other clients via a mesh-like structure.  It is a generic protocol
   which can run directly on top of UDP, TCP, or as a RTP profile.
   Features of PPSPP are short time-till-playback and extensibility.
   Hence, it can use different mechanisms to prevent freeriding, and
   work with different peer discovery schemes (centralized trackers or
   Distributed Hash Tables).  Depending on the underlying transport
   protocol, PPSPP can also use different congestion control algorithms,
   such as LEDBAT, and offer transparent NAT traversal.  Finally, PPSPP
   maintains only a small amount of state per peer and detects malicious
   modification of content.  This documents describes PPSPP and how it
   satisfies the requirements for the IETF Peer-to-Peer Streaming
   Protocol (PPSP) Working Group's peer protocol.

The IETF datatracker status page for this draft is:

There's also a htmlized version available at:

A diff from previous version is available at:

Internet-Drafts are also available by anonymous FTP at:

ppsp mailing list