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

stefano previdi <sprevidi@cisco.com> Mon, 11 February 2013 11:46 UTC

Return-Path: <sprevidi@cisco.com>
X-Original-To: ppsp@ietfa.amsl.com
Delivered-To: ppsp@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 38A9121F879A for <ppsp@ietfa.amsl.com>; Mon, 11 Feb 2013 03:46:58 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -110.599
X-Spam-Level:
X-Spam-Status: No, score=-110.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_HI=-8, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id SiYhYY1hTg5g for <ppsp@ietfa.amsl.com>; Mon, 11 Feb 2013 03:46:57 -0800 (PST)
Received: from av-tac-bru.cisco.com (weird-brew.cisco.com [144.254.15.118]) by ietfa.amsl.com (Postfix) with ESMTP id 278D321F87D2 for <ppsp@ietf.org>; Mon, 11 Feb 2013 03:46:54 -0800 (PST)
X-TACSUNS: Virus Scanned
Received: from stew-brew.cisco.com (localhost.cisco.com [127.0.0.1]) by av-tac-bru.cisco.com (8.13.8+Sun/8.13.8) with ESMTP id r1BBkovp002391 for <ppsp@ietf.org>; Mon, 11 Feb 2013 12:46:51 +0100 (CET)
Received: from ams3-vpn-dhcp4559.cisco.com (ams3-vpn-dhcp4559.cisco.com [10.61.81.206]) by stew-brew.cisco.com (8.13.8+Sun/8.13.8) with ESMTP id r1BBkncx008948; Mon, 11 Feb 2013 12:46:49 +0100 (CET)
Mime-Version: 1.0 (Apple Message framework v1283)
Content-Type: text/plain; charset="us-ascii"
From: stefano previdi <sprevidi@cisco.com>
In-Reply-To: <5118C37D.6060505@cs.vu.nl>
Date: Mon, 11 Feb 2013 12:46:49 +0100
Content-Transfer-Encoding: quoted-printable
Message-Id: <61AFF7CA-9E92-4EF4-AC59-FBEFA0FC3764@cisco.com>
References: <20130211100428.15344.42812.idtracker@ietfa.amsl.com> <5118C37D.6060505@cs.vu.nl>
To: arno@cs.vu.nl
X-Mailer: Apple Mail (2.1283)
Cc: ppsp <ppsp@ietf.org>
Subject: Re: [ppsp] New Version Notification for draft-ietf-ppsp-peer-protocol-06.txt
X-BeenThere: ppsp@ietf.org
X-Mailman-Version: 2.1.12
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: <http://www.ietf.org/mail-archive/web/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: Mon, 11 Feb 2013 11:46:58 -0000

Thanks Arno.


All,

let's take this week for any comment on section 12. Then we'll move to 
IESG/AD review.


thanks.
s.



On Feb 11, 2013, at 11:10 AM, Arno Bakker wrote:

> Hi all
> 
> the review by the Area Director of the peer protocol is under way and as a result we added a Section 12 on Operation and Manageability Considerations, following the checklist in RFC5706.
> 
> Could you please review Section 12 and provide feedback?
> 
> Thanks,
>     Arno et al.
> 
> 
> 
> -------- Original Message --------
> Subject: New Version Notification for draft-ietf-ppsp-peer-protocol-06.txt
> Date: Mon, 11 Feb 2013 02:04:28 -0800
> From: <internet-drafts@ietf.org>
> To: <arno@cs.vu.nl>
> CC: <r.petrocco@gmail.com>, <victor.grishchenko@gmail.com>
> 
> 
> A new version of I-D, draft-ietf-ppsp-peer-protocol-06.txt
> has been successfully submitted by Arno Bakker and posted to the
> IETF repository.
> 
> Filename:	 draft-ietf-ppsp-peer-protocol
> Revision:	 06
> Title:		 Peer-to-Peer Streaming Peer Protocol (PPSPP)
> Creation date:	 2013-02-11
> WG ID:		 ppsp
> Number of pages: 64
> URL: http://www.ietf.org/internet-drafts/draft-ietf-ppsp-peer-protocol-06.txt
> Status: http://datatracker.ietf.org/doc/draft-ietf-ppsp-peer-protocol
> Htmlized:        http://tools.ietf.org/html/draft-ietf-ppsp-peer-protocol-06
> Diff: http://www.ietf.org/rfcdiff?url2=draft-ietf-ppsp-peer-protocol-06
> 
> 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
> ppsp@ietf.org
> https://www.ietf.org/mailman/listinfo/ppsp
>