Re: [ppsp] Call for Comments on Usage of PPSP

"Huangyihong (Rachel)" <rachel.huang@huawei.com> Mon, 22 December 2014 08:18 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 7AC211A8A08 for <ppsp@ietfa.amsl.com>; Mon, 22 Dec 2014 00:18:20 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.439
X-Spam-Level:
X-Spam-Status: No, score=0.439 tagged_above=-999 required=5 tests=[BAYES_20=-0.001, HTML_MESSAGE=0.001, MIME_8BIT_HEADER=0.3, MIME_CHARSET_FARAWAY=2.45, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01] 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 HSUKqwU7HhpP for <ppsp@ietfa.amsl.com>; Mon, 22 Dec 2014 00:18:17 -0800 (PST)
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 BCEAF1A8847 for <ppsp@ietf.org>; Mon, 22 Dec 2014 00:18:16 -0800 (PST)
Received: from 172.18.7.190 (EHLO lhreml403-hub.china.huawei.com) ([172.18.7.190]) by lhrrg01-dlp.huawei.com (MOS 4.3.7-GA FastPath queued) with ESMTP id BQI36225; Mon, 22 Dec 2014 08:18:15 +0000 (GMT)
Received: from nkgeml407-hub.china.huawei.com (10.98.56.38) by lhreml403-hub.china.huawei.com (10.201.5.217) with Microsoft SMTP Server (TLS) id 14.3.158.1; Mon, 22 Dec 2014 08:18:14 +0000
Received: from NKGEML501-MBS.china.huawei.com ([169.254.2.169]) by nkgeml407-hub.china.huawei.com ([10.98.56.38]) with mapi id 14.03.0158.001; Mon, 22 Dec 2014 16:18:08 +0800
From: "Huangyihong (Rachel)" <rachel.huang@huawei.com>
To: =?gb2312?B?1dTM7MP3?= <captainjhon.master@gmail.com>, "ppsp@ietf.org" <ppsp@ietf.org>
Thread-Topic: [ppsp] Call for Comments on Usage of PPSP
Thread-Index: AdAdtGJiA8YvRgdAQFSco/nVkvVJjwABOXkQ
Date: Mon, 22 Dec 2014 08:18:07 +0000
Message-ID: <51E6A56BD6A85142B9D172C87FC3ABBB862A1488@nkgeml501-mbs.china.huawei.com>
References: <008301d01db5$3b12fa90$b138efb0$@gmail.com>
In-Reply-To: <008301d01db5$3b12fa90$b138efb0$@gmail.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: multipart/alternative; boundary="_000_51E6A56BD6A85142B9D172C87FC3ABBB862A1488nkgeml501mbschi_"
MIME-Version: 1.0
X-CFilter-Loop: Reflected
Archived-At: http://mailarchive.ietf.org/arch/msg/ppsp/bu6zIkdHtDEkfP6OboAVm87mQT4
Subject: Re: [ppsp] Call for Comments on 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: Mon, 22 Dec 2014 08:18:20 -0000

Hi Tianming,

Thanks for replying. You omitted one comment regarding issue 2^^. And please see my further comments inline.

BR,
Rachel

From: 赵天明 [mailto:captainjhon.master@gmail.com]
Sent: Monday, December 22, 2014 3:02 PM
To: Huangyihong (Rachel); ppsp@ietf.org
Subject: Re: [ppsp] Call for Comments on Usage of PPSP

Hi,Rachel

    Thanks for your nice and kind review. Sorry for my late response. I would like to answer your questions 7-12.
    Please see in line~

BR
Tianming Zhao


7.      Section 5, issue 1, tracker protocol has an attribute in PeerGroup to indicate by what kind of access the peer is connecting. It’s kind of extending the P2P system in mobile and wireless environments. Of course we can extend the tracker protocol to include the packet loss rate and battery status. However, I’m not sure about it because these two parameters are not general enough, especially battery status.

I think usage in mobile environment should consider handover between base stations and switch between WIFI & Telecom Operator. Also, as data transmission uses power (and the power especially used in upload is sometimes considered as wasted by selfish users), I think we should consider that.

[Rachel]: Maybe we could put these parameters in as optional ones. It that okay for everyone?

8.      Section 5, issue 2, I think it depends on the implementations. For applications that will be supervised by ISPs, tracker protocol and peer protocol without searching peers should be used.
It makes sense. Different application scenarios could set the specific coordinated method of updating PeerList.
But we think if PPSP provides some efficiently way, it will be better for implementers and users.

[Rachel]: What kind of efficient way are you suggesting? IMHO, the protocols in PPSP already have the flexibility to deal with different application scenarios.

9.      Section 5, issue 4. This is addressed in the extended tracker protocol.

Yes, we write our protocol based on the two active Internet-Drafts, they haven’t mentioned it.

We agree with your point in extend tracker protocol. But our current Usage of PPSP is based on the base-tracker protocol and peer protocol, so we take this gap out.

10.  Section 5, issue 5. What’s the intention?

First, by splitting a large swarm, we can shorten the time used in searching & connecting. Second, users under different ISPs (Internet Service Provider) might face higher delay when connect with each other. So I think it would be better if we could adjust size of swarm according to QoS.

[Rachel]: I think it’s an implementation issue rather than a protocol issue.
11.   Section 5, issue 6. Message exchanging frequency is not issue for base tracker protocol, because there’s only a little signaling data delivered by tracker protocol. The most frequent message is STAT_REPORT message which may be 1 minute interval if setting Track_timeout to 3 minutes.


               That’s true. But the point we are trying to give is thatwe should take bandwidth into consideration to adjust the video definition and other parameters.
[Rachel]: I’m not sure I understand your point. The sentence in RFC6972 says
“The tracker (peer) protocol MUST take the frequency of message
      exchange and efficient bandwidth use into consideration when
      communicating chunk availability information (chunk information).
” IMO, the tracker protocol has already satisfied such requirement, just as I explained before. But you are say “the user may want to adjust the video
      definition based on the bandwidth (or user demand)
      automatically (or manually).
”I think this is not issue for tracker protocol, because peers report their bandwidth to the tracker which is already been included in current tracker protocol, and it is possible for a peer to leave a swarm firstly and then join another one (like you said based on user’s demard). So what kind of other abilities do you want the tracker protocol to have?