Re: [ppsp] New draft for usage of PPSP

"Huangyihong (Rachel)" <rachel.huang@huawei.com> Wed, 02 July 2014 02:24 UTC

Return-Path: <rachel.huang@huawei.com>
X-Original-To: ppsp@ietfa.amsl.com
Delivered-To: ppsp@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id C21541B2896 for <ppsp@ietfa.amsl.com>; Tue, 1 Jul 2014 19:24:15 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.552
X-Spam-Level:
X-Spam-Status: No, score=-4.552 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, MIME_8BIT_HEADER=0.3, RCVD_IN_DNSWL_MED=-2.3, RP_MATCHES_RCVD=-0.651, SPF_PASS=-0.001] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 6EVjG92hEQ1K for <ppsp@ietfa.amsl.com>; Tue, 1 Jul 2014 19:24:14 -0700 (PDT)
Received: from lhrrgout.huawei.com (lhrrgout.huawei.com [194.213.3.17]) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id D42471B288B for <ppsp@ietf.org>; Tue, 1 Jul 2014 19:24:13 -0700 (PDT)
Received: from 172.18.7.190 (EHLO lhreml401-hub.china.huawei.com) ([172.18.7.190]) by lhrrg01-dlp.huawei.com (MOS 4.3.7-GA FastPath queued) with ESMTP id BJL99738; Wed, 02 Jul 2014 02:24:12 +0000 (GMT)
Received: from NKGEML406-HUB.china.huawei.com (10.98.56.37) by lhreml401-hub.china.huawei.com (10.201.5.240) with Microsoft SMTP Server (TLS) id 14.3.158.1; Wed, 2 Jul 2014 03:24:11 +0100
Received: from NKGEML501-MBS.china.huawei.com ([169.254.2.155]) by nkgeml406-hub.china.huawei.com ([10.98.56.37]) with mapi id 14.03.0158.001; Wed, 2 Jul 2014 10:24:01 +0800
From: "Huangyihong (Rachel)" <rachel.huang@huawei.com>
To: 邓灵莉/Lingli Deng <denglingli@chinamobile.com>, 'fsong' <fsong@bjtu.edu.cn>, Zongning <zongning@huawei.com>, "ppsp@ietf.org" <ppsp@ietf.org>
Thread-Topic: [ppsp] New draft for usage of PPSP
Thread-Index: Ac+Vj3yU+BgZ9pUMREWe7zKO5iMjIQABuckgAAC6soA=
Date: Wed, 02 Jul 2014 02:23:59 +0000
Message-ID: <51E6A56BD6A85142B9D172C87FC3ABBB861E8A0C@nkgeml501-mbs.china.huawei.com>
References: <604109602.03243@bjtu.edu.cn> <604261758.30941@bjtu.edu.cn> <015e01cf9597$2ea5eca0$8bf1c5e0$@com>
In-Reply-To: <015e01cf9597$2ea5eca0$8bf1c5e0$@com>
Accept-Language: zh-CN, en-US
Content-Language: zh-CN
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [10.138.41.144]
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64
MIME-Version: 1.0
X-CFilter-Loop: Reflected
Archived-At: http://mailarchive.ietf.org/arch/msg/ppsp/kEP0f0MmDDEC6Ao4oIuz-2J8w4U
Cc: "hishigh@sina.com" <hishigh@sina.com>
Subject: Re: [ppsp] New draft for usage of PPSP
X-BeenThere: ppsp@ietf.org
X-Mailman-Version: 2.1.15
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: Wed, 02 Jul 2014 02:24:15 -0000

Hi Fei,

As Lingli said, issue 4 and issue 5 have been addressed in the extended tracker protocol. Extended tracker protocol extends the JOIN message and STAT_REPORT message to include content information.
We'll submit the new version of extended tracker protocol soon before the deadline.

As for issue 6, I'm not sure that PPSP system should provide message to change its PeerMode when the peer gets the whole content. If it wants to become SEED, it can leave the swarm and join the swarm again as SEED.

BR,
Rachel

> -----Original Message-----
> From: ppsp [mailto:ppsp-bounces@ietf.org] On Behalf Of 邓灵莉/Lingli Deng
> Sent: Wednesday, July 02, 2014 9:45 AM
> To: 'fsong'; Zongning; ppsp@ietf.org
> Cc: hishigh@sina.com
> Subject: Re: [ppsp] New draft for usage of PPSP
> 
> Hi Fei,
> 
> This is an interesting draft. Thanks for set up this discussion for PPSP operation.
> As for the parameter recommendations, I am wondering if it would help if more
> information about the system you are targeting is provided? Would the
> recommendations be dependent on the system settings, like the scale of the
> system, etc.?
> You might also want to take a look at the extended tracker protocol, which I
> believe aims to solve at least some of the issues you raised in terms of the base
> tracker protocol.
> 
> Lingli
> 
> > -----Original Message-----
> > From: ppsp [mailto:ppsp-bounces@ietf.org] On Behalf Of Fei Song
> > Sent: Wednesday, July 02, 2014 8:49 AM
> > To: Zongning; ppsp@ietf.org
> > Cc: hishigh@sina.com
> > Subject: [ppsp] New draft for usage of PPSP
> >
> > Dear all:
> >
> > We have submitted a new draft about usage of PPSP.
> > http://www.ietf.org/id/draft-zhang-ppsp-usage-00.txt
> > Comments and suggestions are more than welcome.
> > Thank you very much!
> >
> > --------------
> > Fei Song
> > >Dear all,
> > >
> > >Please let Yunfei and I know if you plan to present any drafts in the
> > >PPSP
> > WG session in Toronto.
> > >We have put Tracker Base Protocol and Tracker Extended Protocol into
> > >the
> > agenda, but obviously have enough time to accommodate more topics &
> > drafts...
> > >
> > >Thanks.
> > >
> > >-Yunfei & Ning
> > >
> > _______________________________________________
> > ppsp mailing list
> > ppsp@ietf.org
> > https://www.ietf.org/mailman/listinfo/ppsp
> 
> 
> 
> _______________________________________________
> ppsp mailing list
> ppsp@ietf.org
> https://www.ietf.org/mailman/listinfo/ppsp