IETF Logo Mail Archive

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

邓灵莉/Lingli Deng <denglingli@chinamobile.com> Fri, 04 July 2014 11:07 UTC

Return-Path: <denglingli@chinamobile.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 936281B2D0A for <ppsp@ietfa.amsl.com>; Fri, 4 Jul 2014 04:07:15 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.03
X-Spam-Level:
X-Spam-Status: No, score=-0.03 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, MIME_8BIT_HEADER=0.3, RELAY_IS_221=2.222, RP_MATCHES_RCVD=-0.651, SPF_PASS=-0.001] autolearn=no
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 fx_B8HCcHdak for <ppsp@ietfa.amsl.com>; Fri, 4 Jul 2014 04:07:13 -0700 (PDT)
Received: from cmccmta1.chinamobile.com (cmccmta1.chinamobile.com [221.176.66.79]) by ietfa.amsl.com (Postfix) with SMTP id 351D51B2D06 for <ppsp@ietf.org>; Fri, 4 Jul 2014 04:07:13 -0700 (PDT)
Received: from spf.mail.chinamobile.com (unknown[172.16.121.9]) by rmmx-syy-dmz-app02-12002 (RichMail) with SMTP id 2ee253b68ac5706-4c706; Fri, 04 Jul 2014 19:06:45 +0800 (CST)
X-RM-TRANSID: 2ee253b68ac5706-4c706
Received: from cmccPC (unknown[10.2.43.183]) by rmsmtp-syy-appsvr05-12005 (RichMail) with SMTP id 2ee553b68ac19bc-f9a21; Fri, 04 Jul 2014 19:06:45 +0800 (CST)
X-RM-TRANSID: 2ee553b68ac19bc-f9a21
From: 邓灵莉/Lingli Deng <denglingli@chinamobile.com>
To: "'Huangyihong (Rachel)'" <rachel.huang@huawei.com>, 'Di Wu' <diwu2@seas.upenn.edu>, 'Fei Song' <fsong@bjtu.edu.cn>, 'PPSP' <ppsp@ietf.org>
References: <201407031731421187028@bjtu.edu.cn> <eefda5baa5c5c3c3c9d1e5b9262a6622@seas.upenn.edu> <51E6A56BD6A85142B9D172C87FC3ABBB861E97AB@nkgeml501-mbs.china.huawei.com> <28131bc31a9fb0e6454557323ab6f438@seas.upenn.edu> <51E6A56BD6A85142B9D172C87FC3ABBB861E981E@nkgeml501-mbs.china.huawei.com>
In-Reply-To: <51E6A56BD6A85142B9D172C87FC3ABBB861E981E@nkgeml501-mbs.china.huawei.com>
Date: Fri, 04 Jul 2014 19:06:47 +0800
Message-ID: <00b801cf9778$0ca7d8b0$25f78a10$@com>
MIME-Version: 1.0
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Mailer: Microsoft Office Outlook 12.0
Thread-Index: AQHPly85Y6Q1cnqzF0exT9tQigkR9JuPZ1Sw//+NqACAAIldAIAADjDw
Content-Language: zh-cn
Archived-At: http://mailarchive.ietf.org/arch/msg/ppsp/8ixDMsxE51U2ek6L3tfXlFMsTK8
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 11:07:15 -0000


> -----Original Message-----
> From: ppsp [mailto:ppsp-bounces@ietf.org] On Behalf Of Huangyihong
> (Rachel)
> Sent: Friday, July 04, 2014 3:23 PM
> To: Di Wu; Fei Song; PPSP
> Subject: Re: [ppsp] Fw: RE: New draft for usage of PPSP
> 
> Hi Di Wu,
> 
> I take out the parts we agree on. Please see Inline.
> 
> BR,
> Rachel
> > >> > 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.
> >
> [Rachel] It's a implementation v.s. protocol issue. IMO, we don't have to
> complex the protocol in order to simplify the implementation. So I think my
> option and your last option is acceptable, while the option to change
> STAT_REPORT is unnecessary.
[邓灵莉/Lingli Deng] Just for discussion, I am afraid that I don't like the option by sending CHOKE, which means that the peer is being visible to other peers against its explicit will.
> _______________________________________________
> ppsp mailing list
> ppsp@ietf.org
> https://www.ietf.org/mailman/listinfo/ppsp

v2.23.0 | Report a Bug | By Email