Re: [ppsp] PPSP WG Update

Arno Bakker <arno@cs.vu.nl> Tue, 05 June 2012 07:03 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 5530C21F86A4 for <ppsp@ietfa.amsl.com>; Tue, 5 Jun 2012 00:03:53 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.504
X-Spam-Level:
X-Spam-Status: No, score=-4.504 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HELO_EQ_NL=0.55, HOST_EQ_NL=1.545, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id WjpyiO0R9BAi for <ppsp@ietfa.amsl.com>; Tue, 5 Jun 2012 00:03:52 -0700 (PDT)
Received: from mailin.vu.nl (mailin.vu.nl [130.37.164.16]) by ietfa.amsl.com (Postfix) with ESMTP id 32A7A21F86A2 for <ppsp@ietf.org>; Tue, 5 Jun 2012 00:03:50 -0700 (PDT)
Received: from PEXHB011A.vu.local (130.37.236.64) by mailin.vu.nl (130.37.164.16) with Microsoft SMTP Server (TLS) id 14.2.283.3; Tue, 5 Jun 2012 09:03:48 +0200
Received: from [130.37.193.73] (130.37.238.20) by mails.vu.nl (130.37.236.64) with Microsoft SMTP Server (TLS) id 14.2.283.3; Tue, 5 Jun 2012 09:03:48 +0200
Message-ID: <4FCDAFA7.2020903@cs.vu.nl>
Date: Tue, 05 Jun 2012 09:05:11 +0200
From: Arno Bakker <arno@cs.vu.nl>
User-Agent: Mozilla/5.0 (Windows NT 6.1; rv:11.0) Gecko/20120312 Thunderbird/11.0
MIME-Version: 1.0
To: ppsp@ietf.org
References: <C2917A21-A82F-412E-8B34-9B4053504929@cisco.com>
In-Reply-To: <C2917A21-A82F-412E-8B34-9B4053504929@cisco.com>
Content-Type: text/plain; charset="ISO-8859-1"; format="flowed"
Content-Transfer-Encoding: 7bit
X-Originating-IP: [130.37.238.20]
Subject: Re: [ppsp] PPSP WG Update
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: Tue, 05 Jun 2012 07:03:53 -0000

Hi all

please see inline.

On 04/06/2012 11:39, stefano previdi wrote:
> All,
>
> here are some notes i preparation of the next PPSP meeting we're
> going to have in Vancouver (http://www.ietf.org/meeting/84/index.html)
>
> 1. Peer Protocol - chunk addressing mechanism
>     Option-1: We propose both solutions in the peer protocol
>               specification and we define them both MANDATORY so
>               to cope with interoperability issues.

As long as they use the same division into chunks (e.g. required by the
Merkle hash tree for content integrity protection) there should not
be a problem translating bins to ranges and vice versa. Note there are 
two possible types of ranges: ranges of chunk IDs, and
byte ranges.

I'm currently updating the -01 draft following the issues raised since
January, which includes freedom to have different addressing schemes and 
the two proposals.

> 2. Peer Protocol - Security Section

Part of the update the security section is extending the
security analyses and solutions discussed since January.

The update will give us a draft that addresses all major topics,
with some strategic decisions to be made on default transport,
and extra features to add or reject.

We hope to have a new version next week.

CU,
     Arno