Re: [ppsp] Fw: RE: New draft for usage of PPSP

Di Wu <diwu2@seas.upenn.edu> Fri, 04 July 2014 06:54 UTC

Return-Path: <diwu2@seas.upenn.edu>
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 67B951B2C01 for <ppsp@ietfa.amsl.com>; Thu, 3 Jul 2014 23:54:31 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.772
X-Spam-Level:
X-Spam-Status: No, score=-1.772 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RP_MATCHES_RCVD=-0.651, SPF_NEUTRAL=0.779] 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 8ysbCS97xatb for <ppsp@ietfa.amsl.com>; Thu, 3 Jul 2014 23:54:29 -0700 (PDT)
Received: from talbot.seas.upenn.edu (talbotv6.seas.upenn.edu [IPv6:2607:f470:8:64:5ea5::2]) (using SSLv3 with cipher ECDHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 882061A0AFC for <ppsp@ietf.org>; Thu, 3 Jul 2014 23:54:29 -0700 (PDT)
Received: from webmail.seas.upenn.edu (stamp.seas.upenn.edu [158.130.67.170]) (authenticated bits=0) by talbot.seas.upenn.edu (8.14.5/8.14.5) with ESMTP id s646s0vq023376 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=NOT); Fri, 4 Jul 2014 02:54:00 -0400
MIME-Version: 1.0
Content-Type: text/plain; charset="UTF-8"; format="flowed"
Content-Transfer-Encoding: 8bit
Date: Fri, 04 Jul 2014 14:54:00 +0800
From: Di Wu <diwu2@seas.upenn.edu>
To: "Huangyihong (Rachel)" <rachel.huang@huawei.com>, Fei Song <fsong@bjtu.edu.cn>, PPSP <ppsp@ietf.org>
In-Reply-To: <51E6A56BD6A85142B9D172C87FC3ABBB861E97AB@nkgeml501-mbs.china.huawei.com>
References: <201407031731421187028@bjtu.edu.cn> <eefda5baa5c5c3c3c9d1e5b9262a6622@seas.upenn.edu> <51E6A56BD6A85142B9D172C87FC3ABBB861E97AB@nkgeml501-mbs.china.huawei.com>
Message-ID: <28131bc31a9fb0e6454557323ab6f438@seas.upenn.edu>
X-Sender: diwu2@seas.upenn.edu
User-Agent: Roundcube Webmail/0.9.1
X-Proofpoint-Virus-Version: vendor=nai engine=5400 definitions=5800 signatures=585085
X-PP-Spam-Details: rule=add_spam_details policy=default score=0 spamscore=0 ipscore=0 suspectscore=0 phishscore=0 bulkscore=0 adultscore=0 classifier=spam adjust=0 reason=mlx scancount=1 engine=7.0.1-1111160001 definitions=main-1407040087
Archived-At: http://mailarchive.ietf.org/arch/msg/ppsp/QLsRq7SU8SUPoZUDw9ZI1X5J-OY
Subject: Re: [ppsp] Fw: RE: 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: Fri, 04 Jul 2014 06:54:31 -0000

Hi again,

Thank you very much! Please see below.

Best,
Di Wu
On 2014-07-04 14:09, Huangyihong (Rachel) wrote:
> Hi Di Wu,
> 
> Please see inline.
> 
> BR,
> Rachel
> 
>> -----Original Message-----
>> From: Di Wu [mailto:diwu2@seas.upenn.edu]
>> Sent: Friday, July 04, 2014 10:25 AM
>> To: fsong; Huangyihong (Rachel); ppsp@ietf.org
>> Subject: Re: Fw: RE: [ppsp] New draft for usage of PPSP
>> 
>> Hi, Dear Rachel,
>> 
>> Thank you for your suggestion. Please see my respond in line.
>> 
>> Best,
>> Di Wu
>> 
>> > FROM: Huangyihong (Rachel)
>> > DATE: 2014-07-02 10:23
>> > TO: 邓灵莉/Lingli Deng; 'fsong'; Zongning; ppsp@ietf.org
>> > CC: hishigh@sina.com
>> > SUBJECT: RE: [ppsp] New draft for usage of PPSP
>> >
>> > 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 I mentioned before, these usage of PPSP system are based on the 
>> current
>> tracker and peer protocol, so as the gap part. We are looking forward 
>> to your
>> new version of extended tracker protocol.
> 
> [Rachel]: Extended tracker protocol has been updated. Your comments
> are welcomed.
>> 
>> > 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.
>> As for issue 6, we think PPSP system should consider it to provided a 
>> better
>> service for peers.
> [Rachel]: Sure. I'm just explaining that base protocol could do it in
> another way. Some peers may not want to share their content when they
> finish downloading. If the ppsp system change it automatically. It
> will be against those people's will. Let's see what WG thinks of it.
> 
Yeah, you are right. But the way you illustrated is a little bit 
complex. That's why we put it into the limitation and gaps part. And as 
you explained below, the PeerMode usually used when a peer firstly 
connected to the tracker. Once they login to ppsp system and finished 
data transmission, the PeerMode may not represent their status. We are 
hoping to provide a simple way to solve this problem, which not defends 
peer's willing. For example, peers may change their PeerMode once they 
gets the whole content and are willing to share it with others via 
STAT_REPORT message. While another option is that PPSP system change it 
automatically (Just as you mentioned). For those people who are not 
willing to share the content, they could send CHONKE message to express 
their willing.

>> However, I'm not sure of the real motivation for putting the
>> PeerMode into system.
> 
> [Rachel]: PeerMode could distinguish peers. When a peer connects to
> the tracker, the tracker has to understand if it is to provide the
> content sharing or it asks for the peer list to exchange content. They
> are different process (see section 5.1 of base tracker protocol).
> 
Thanks. I just read this part again.
>> > 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