Re: [ppsp] New Version Notification for draft-ietf-ppsp-peer-protocol-04.txt

[stefano previdi <[e-mail]>]

Arno, All,

Thanks for the update.

I believe, unless anyone has a different opinion, the draft is now 
mature for the next step (i.e.: IESG review) which is what we'll do 
after the holiday break.

Thanks, Happy Holidays and Happy New Year to everyone.

Stefano & Yunfei.


On Dec 6, 2012, at 2:08 PM, Arno Bakker wrote:

> Hi
> 
> I updated the peer protocol draft, see revision history below.
> 
> CU,
>    Arno
> 
> ==============
>   -04	2012-11-07 Minor revision
> 
>       *   Corrected typos.
> 
>       *   Added empty protocol option list when HANDSHAKE is used for
>           explicitly closing a channel in the UDP encapsulation.
> 
>       *   Corrected definition of a range chunk specification to be a
>           single (start,end) pair.  To send multiple disjunct ranges
>           multiple messages should be used.
> 
>       *   Clarified that in a range chunk specification the end is
>           inclusive.  I.e., [start,end] not [start,end)
> 
>       *   Added PEX_REScert message to carry a membership certificate.
>           Renamed PEX_RES to PEX_RESv4.
> 
>       *   Added a guideline about private and link-local addresses in
>           PEX_RES messages.
> 
>       *   Defined the format of the public key that is used as swarm ID
>           in live streaming.
> 
>       *   Clarified that a HANDSHAKE message must be the first message
>           in a datagram.
> 
>       *   Clarified sending INTEGRITY messages ahead in a separate
>           datagram if not all necessary hashes that still need to be
>           sent and the chunk fit into a single datagram.  Defined an
>           order for the INTEGRITY messages.
> 
>       *   Clarified rare case of sending multiple DATA messages in one
>           datagram.
> 
>       *   Clarified UDP datagrams carrying PPSPP should adhere to the
>           network's MTU to avoid IP fragmentation.
> 
>       *   Defined value for version protocol option.
> 
>       *   Added small clarifications and corrected typos.
> 
>       *   Extended versioning scheme to Min/max versioning scheme
>           defined in [RFC6709], Section 4.1, following Riccardo
>           Bernardini's suggestion.
> 
>       *   Processed comments on unclear phrasing from Riccardo
>           Bernardini.
> 
>       *   Added a guideline on when to declare a peer dead.
> 
>       *   Made sure all essential references are listed as Normative
>           references following RFC3967.
> 
> 
> 
> -------- Original Message --------
> Subject: New Version Notification for draft-ietf-ppsp-peer-protocol-04.txt
> Date: Thu, 6 Dec 2012 05:01:28 -0800
> From: <[e-mail]>
> To: <[e-mail]>
> CC: <[e-mail]>, <[e-mail]>
> 
> 
> A new version of I-D, draft-ietf-ppsp-peer-protocol-04.txt
> has been successfully submitted by Arno Bakker and posted to the
> IETF repository.
> 
> Filename:	 draft-ietf-ppsp-peer-protocol
> Revision:	 04
> Title:		 Peer-to-Peer Streaming Peer Protocol (PPSPP)
> Creation date:	 2012-12-06
> WG ID:		 ppsp
> Number of pages: 57
> URL: http://www.ietf.org/internet-drafts/draft-ietf-ppsp-peer-protocol-04.txt
> Status: http://datatracker.ietf.org/doc/draft-ietf-ppsp-peer-protocol
> Htmlized:        http://tools.ietf.org/html/draft-ietf-ppsp-peer-protocol-04
> Diff: http://www.ietf.org/rfcdiff?url2=draft-ietf-ppsp-peer-protocol-04
> 
> 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.
> 
> 
> 
> 
> The IETF Secretariat
> 
> _______________________________________________
> ppsp mailing list
> [e-mail]
> https://www.ietf.org/mailman/listinfo/ppsp
>