[ppsp] comments on draft-ietf-ppsp-peer-protocol-03.txt

[zhangyunfei <[e-mail]>]

Hi Arno (Speaking individually),
   I've read the draft and the following is my comments:
1) The effect of "choke/unchoke" is not very clear in the draft. Will this increase the transfer efficiency?
2) I am fine with the update on section 4. It's good to discuss the compatibility issue in chunk addressing.
3) Is it better to combine section 5,6, 7 into security consideration section as all these 3 sections involve identifying the data is from the reliable source/peers, which is related to security more or less. What's more, it makes the draft better structured.
    

BR
yunfei





zhangyunfei

From: Arno Bakker
Date: 2012-10-22 15:12
To: zhangyunfei
CC: ppsp; stefano previdi
Subject: Re: [ppsp] I-D Action: draft-ietf-ppsp-peer-protocol-03.txt
On 22/10/2012 09:07, zhangyunfei wrote:
> Hi Arno,
> Would you please summarize the main changes of this version of draft?
> That will be helpful to review the draft. Thanks.

Hi Yunfei et al

there is still a revision history at the back of the document. I will 
update the tickets soon:

    Arno

    -03 2012-10-22 Major revision

        *   Updated Abstract and Introduction, removing download case.

        *   Resolved Ticket #4: Added explicit CHOKE/UNCHOKE messages.

        *   Removed directory lists unused in streaming.

        *   Resolved Ticket #22, #23, #28: Failure behaviour, error codes
            and dealing with peer crashes.

        *   Resolved Ticket #13: Chunk ranges are the default chunk
            addressing scheme that all peers MUST support.

        *   Added a section on compatibility between chunk addressing
            schemes.

        *   Expanded the explanation of Unified Merkle Trees as a method
            for content integrity protection for live streams.

        *   Added a section on forgetting chunks in live streaming.

        *   Added "End" option to protocol options and corrected bugs in
            UDP encapsulation, following Karl Knutsson's comments.

        *   Added SHA-2 support for Merkle Hash functions.

        *   Added content integrity protection methods for live streaming
            to the relevant protocol option.

        *   Added a Live Signature Algorithm protocol option.

        *   Resolved Ticket #24+27: The choice for UDP + LEDBAT as
            transport has now been reflected in the draft.  TCP and RTP
            encapsulations have been removed.

        *   Superfluous parts of Section 10 on extensibility have been
            removed.

        *   Removed appendix with Rationale.

        *   Resolved Ticket #21+25: PPSPP currently uses LEDBAT and the
            DATA and ACK messages now contain the time fields it
            requires.  Should other congestion control algorithms be
            supported in the future, a protocol option will be added.