[ppsp] Fwd: New Version Notification for draft-ietf-ppsp-peer-protocol-06.txt
Arno Bakker <arno@cs.vu.nl> Mon, 11 February 2013 10:09 UTC
Return-Path: <a.bakker@vu.nl>
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 C6AA421F86C0 for <ppsp@ietfa.amsl.com>; Mon, 11 Feb 2013 02:09:58 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.004
X-Spam-Level:
X-Spam-Status: No, score=-3.004 tagged_above=-999 required=5 tests=[AWL=1.500, BAYES_00=-2.599, HELO_EQ_NL=0.55, HOST_EQ_NL=1.545, RCVD_IN_DNSWL_MED=-4]
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 BCAdC-ZWHpTj for <ppsp@ietfa.amsl.com>; Mon, 11 Feb 2013 02:09:58 -0800 (PST)
Received: from mailin.vu.nl (mailin.vu.nl [130.37.164.16]) by ietfa.amsl.com (Postfix) with ESMTP id 815AF21F86BC for <ppsp@ietf.org>; Mon, 11 Feb 2013 02:09:56 -0800 (PST)
Received: from PEXHB012B.vu.local (130.37.236.67) by mailin.vu.nl (130.37.164.16) with Microsoft SMTP Server (TLS) id 14.2.298.4; Mon, 11 Feb 2013 11:09:52 +0100
Received: from [192.168.0.103] (130.37.238.20) by mails.vu.nl (130.37.236.67) with Microsoft SMTP Server (TLS) id 14.2.298.4; Mon, 11 Feb 2013 11:09:54 +0100
Message-ID: <5118C37D.6060505@cs.vu.nl>
Date: Mon, 11 Feb 2013 11:10:05 +0100
From: Arno Bakker <arno@cs.vu.nl>
User-Agent: Mozilla/5.0 (Windows NT 6.1; rv:17.0) Gecko/17.0 Thunderbird/17.0
MIME-Version: 1.0
To: ppsp <ppsp@ietf.org>
References: <20130211100428.15344.42812.idtracker@ietfa.amsl.com>
In-Reply-To: <20130211100428.15344.42812.idtracker@ietfa.amsl.com>
X-Forwarded-Message-Id: <20130211100428.15344.42812.idtracker@ietfa.amsl.com>
Content-Type: text/plain; charset="UTF-8"; format="flowed"
Content-Transfer-Encoding: 7bit
X-Originating-IP: [130.37.238.20]
Subject: [ppsp] Fwd: New Version Notification for draft-ietf-ppsp-peer-protocol-06.txt
X-BeenThere: ppsp@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
Reply-To: arno@cs.vu.nl
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 10:09:58 -0000
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] Fwd: New Version Notification for draft-ie… Arno Bakker
- Re: [ppsp] New Version Notification for draft-iet… stefano previdi