Re: [ppsp] tickets for IETF 83

zhangyunfei <zhangyunfei@chinamobile.com> Tue, 15 May 2012 03:10 UTC

Return-Path: <zhangyunfei@chinamobile.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 1E66B21F8657 for <ppsp@ietfa.amsl.com>; Mon, 14 May 2012 20:10:48 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -95.738
X-Spam-Level:
X-Spam-Status: No, score=-95.738 tagged_above=-999 required=5 tests=[AWL=2.885, BAYES_00=-2.599, HTML_MESSAGE=0.001, MIME_BASE64_TEXT=1.753, RELAY_IS_221=2.222, USER_IN_WHITELIST=-100]
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 0T9kan-ff9ga for <ppsp@ietfa.amsl.com>; Mon, 14 May 2012 20:10:44 -0700 (PDT)
Received: from imss.chinamobile.com (imss.chinamobile.com [221.130.253.135]) by ietfa.amsl.com (Postfix) with ESMTP id 0A04A21F8655 for <ppsp@ietf.org>; Mon, 14 May 2012 20:10:44 -0700 (PDT)
Received: from imss.chinamobile.com (localhost [127.0.0.1]) by localhost.chinamobile.com (Postfix) with ESMTP id 15CD3E6E9; Tue, 15 May 2012 11:10:42 +0800 (CST)
Received: from mail.chinamobile.com (unknown [10.1.28.22]) by imss.chinamobile.com (Postfix) with ESMTP id 52918E6E4; Tue, 15 May 2012 11:10:41 +0800 (CST)
Received: from zyf-PC ([10.2.43.220]) by mail.chinamobile.com (Lotus Domino Release 6.5.6) with ESMTP id 2012051511103923-7527 ; Tue, 15 May 2012 11:10:39 +0800
Date: Tue, 15 May 2012 11:10:36 +0800
From: zhangyunfei <zhangyunfei@chinamobile.com>
To: Picconi Fabio <Fabio.Picconi@technicolor.com>, ppsp <ppsp@ietf.org>, 'Rui Cruz' <rui.cruz@ieee.org>, "Yingjie Gu(yingjie)" <guyingjie@huawei.com>
References: <2012050316123830359558@chinamobile.com>, <320C4182454E96478DC039F2C481987204EB1CD469@MOPESMBX01.eu.thmulti.com>
X-Priority: 3 (Normal)
X-Mailer: Foxmail 7.0.1.85[cn]
Mime-Version: 1.0
Message-ID: <2012051511103610737239@chinamobile.com>
X-MIMETrack: Itemize by SMTP Server on jtgsml01/servers/cmcc(Release 6.5.6|March 06, 2007) at 2012-05-15 11:10:39, Serialize by Router on jtgsml01/servers/cmcc(Release 6.5.6|March 06, 2007) at 2012-05-15 11:10:41, Serialize complete at 2012-05-15 11:10:41
Content-Type: multipart/alternative; boundary="----=_001_NextPart420237135354_=----"
X-TM-AS-Product-Ver: IMSS-7.0.0.8231-6.8.0.1017-18906.003
X-TM-AS-Result: No--37.753-7.0-31-10
X-imss-scan-details: No--37.753-7.0-31-10;No--37.753-7.0-31-10
X-TM-AS-User-Approved-Sender: No;No
X-TM-AS-User-Blocked-Sender: No;No
Subject: Re: [ppsp] tickets for IETF 83
X-BeenThere: ppsp@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
Reply-To: zhangyunfei <zhangyunfei@chinamobile.com>
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, 15 May 2012 03:10:48 -0000

Hi Rui and Yingjie,
    Would you please confirm the ticket #4 for Paris meeting?
     For ticket #5, I am fine with Fabio's proposal.

BR
Yunfei




zhangyunfei

From: Picconi Fabio
Date: 2012-05-14 20:04
To: zhangyunfei; ppsp
Subject: RE: [ppsp] tickets for IETF 83
Hi,
Somme comments:
Ticket #1 (chunk addressing mechanism). See my email send today.
Ticket #2. I can’t remember what this was about. :-)
Ticket #3 (secure PEX): I think that we can stick to a simple PEX mechanism that can be augmented by an optional secure algorithm. In addition to the solution proposed by Arno, there is a simple mechanism described by Jesi et al. [1].
Ticket #4 (FIND use case). I don’t recall exactly the details of this issue. If it’s only motivating a request to the tracker to find peers subject to attribute constraints, then finding peers with a similar upload capacity (to speed up the discovery phase) is already a good motivation.
Ticket #5 (additional messages). I think the proponents of these messages should describe the use cases where these messages can be useful.
Cheers,
Fabio
[1] G.P. Jesi, A. Montresor, and M. van Steen. Secure Peer Sampling. In Computer Networks, 2010.
 
From: ppsp-bounces@ietf.org [mailto:ppsp-bounces@ietf.org] On Behalf Of zhangyunfei
Sent: jeudi 3 mai 2012 10:13
To: ppsp
Subject: [ppsp] tickets for IETF 83
 
Hi all,
    I have summarized an initial tickets list for IETF 83 meeting. Please review it and actions on these tickets are expected. Thanks.
 
BR
Yunfei &Stefano
-----------------------------------------------------------------------------------------------------------
Peer protocol:
Ticket #1:Post and discuss the alternative proposal besides MHT in peer protocol (Proposal 10+13), list intervals (Tradeoff among complexity / overhead / efficiency / implementation) and check gaps. [Martin, Yunfei, Fabio, Lichun]
This ticket is partly solved. Simple nature number addressing and ranged expression on chunk availability. The analysis and comparison is ongoing. I'd suggest to have a deadline for the resolution time after discussing with Stefano, i.e.,  May 26th from now on to make the decision in the WG level.
 
Ticket #2:Discuss the possible “"state-building attacks" attack on peers.[Martin](related Proposal 26)
Martin, Do you still have concerns on this? If nobody shows up, we propose to close this ticket.
 
Ticket #3: Discuss the Membership certificates impact on the tracker’s workload.[Fabio](related to Proposal 17+20)
 
Tracker protocol:
Ticket#4: Specify the FIND use case and reduce the overhead to the tracker.[Martin,Yunfei,Fabio,Richardo]
Ticket#5: Discuss concrete use cases of additional messages if there are(e.g.,reconnect and rejoin) , and conclude the basic messages and optional ones in tracker protocol. [Mark, Fabio]
 We propose to the tracker protocol authors to address their tickets with a splitting of their proposal:
. base spec
. additional options.
 
Survey
Ticket#6: Call for reviewers for survey draft, and maybe P2P streaming providers’ contribution on updating the draft.   
 



zhangyunfei