Re: [ppsp] WG Last Call for draft-ietf-ppsp-problem-statement

Zongning <zongning@huawei.com> Fri, 13 July 2012 00:59 UTC

Return-Path: <zongning@huawei.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 32B6511E8095 for <ppsp@ietfa.amsl.com>; Thu, 12 Jul 2012 17:59:26 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -105.348
X-Spam-Level:
X-Spam-Status: No, score=-105.348 tagged_above=-999 required=5 tests=[AWL=1.250, BAYES_00=-2.599, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_MED=-4, 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 uFEv1e8V7ypa for <ppsp@ietfa.amsl.com>; Thu, 12 Jul 2012 17:59:24 -0700 (PDT)
Received: from dfwrgout.huawei.com (dfwrgout.huawei.com [206.16.17.72]) by ietfa.amsl.com (Postfix) with ESMTP id 930A311E8087 for <ppsp@ietf.org>; Thu, 12 Jul 2012 17:59:24 -0700 (PDT)
Received: from 172.18.9.243 (EHLO dfweml201-edg.china.huawei.com) ([172.18.9.243]) by dfwrg02-dlp.huawei.com (MOS 4.2.3-GA FastPath) with ESMTP id AHS11886; Thu, 12 Jul 2012 20:59:59 -0400 (EDT)
Received: from DFWEML408-HUB.china.huawei.com (10.193.5.134) by dfweml201-edg.china.huawei.com (172.18.9.107) with Microsoft SMTP Server (TLS) id 14.1.323.3; Thu, 12 Jul 2012 17:57:23 -0700
Received: from SZXEML435-HUB.china.huawei.com (10.72.61.63) by dfweml408-hub.china.huawei.com (10.193.5.134) with Microsoft SMTP Server (TLS) id 14.1.323.3; Thu, 12 Jul 2012 17:57:28 -0700
Received: from SZXEML504-MBS.china.huawei.com ([169.254.8.92]) by szxeml435-hub.china.huawei.com ([::1]) with mapi id 14.01.0323.003; Fri, 13 Jul 2012 08:57:21 +0800
From: Zongning <zongning@huawei.com>
To: "Y. Richard Yang" <yry@cs.yale.edu>, Rui Cruz <rui.cruz@ieee.org>
Thread-Topic: [ppsp] WG Last Call for draft-ietf-ppsp-problem-statement
Thread-Index: AQHNYAzeMWsMDpVuSEaQdL26Y7bxBJclYvPV//+RVgCAAE0rAIABIvSQ
Date: Fri, 13 Jul 2012 00:57:20 +0000
Message-ID: <B0D29E0424F2DE47A0B36779EC66677924AB5B56@szxeml504-mbs.china.huawei.com>
References: <D0CDD8DF-E87E-41C6-9198-08CFE0916068@cisco.com>, <500D2A74-221C-4174-9E97-8007B8BF34FA@ieee.org> <2012071217335750147860@chinamobile.com> <C23ED253-6A87-4814-9ABC-8E9C4F92C9DB@ieee.org> <4FFEEE88.6010504@cs.yale.edu>
In-Reply-To: <4FFEEE88.6010504@cs.yale.edu>
Accept-Language: en-US, zh-CN
Content-Language: zh-CN
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [10.138.41.35]
Content-Type: multipart/alternative; boundary="_000_B0D29E0424F2DE47A0B36779EC66677924AB5B56szxeml504mbschi_"
MIME-Version: 1.0
X-CFilter-Loop: Reflected
Cc: ppsp <ppsp@ietf.org>
Subject: Re: [ppsp] WG Last Call for draft-ietf-ppsp-problem-statement
X-BeenThere: ppsp@ietf.org
X-Mailman-Version: 2.1.12
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, 13 Jul 2012 00:59:26 -0000

Hi,

I also support adding a subsection for P2P proxy use cases.

-Ning

From: ppsp-bounces@ietf.org [mailto:ppsp-bounces@ietf.org] On Behalf Of Y. Richard Yang
Sent: Thursday, July 12, 2012 11:35 PM
To: Rui Cruz
Cc: ppsp
Subject: Re: [ppsp] WG Last Call for draft-ietf-ppsp-problem-statement

Hi Yunfei and Rui,

The idea of showing a use case of a proxy is good and helpful. One short comment is that I am not sure if it needs two sub sections 5.4/5.5. Maybe a single P2P proxy subsec is enough? Inside the subsec, it can mention multiple instances. Just a short suggestion that you may consider.

Thanks!

Richard

On 7/12/12 6:58 PM, Rui Cruz wrote:
Hi Yunfei,

I am happy that you like the Use Case.

>From your other description, it reminds me of an existing solution that I have tested and works quite well: http://www.littleshoot.org/
It just requires a browser, and via a plugin, launches a P2P proxy process to make P2P HTTP-based downloading.

I also like your Use Case, but  I think it deserves to be a new one (5.5 Proxy service for Browser-based HTTP streaming).

Regards,

Rui Cruz
rui.cruz@ieee.org<mailto:rui.cruz@ieee.org>

IST/INESC-ID/INOV - Lisbon, Portugal
__________________________________________
ppsp mailing list
ppsp@ietf.org<mailto:ppsp@ietf.org>
https://www.ietf.org/mailman/listinfo/ppsp

On 12/07/2012, at 10:33, zhangyunfei wrote:


Hi Rui,
    Thanks for the contribution. I like this use case.
    I happen to think of one similar one: Plug-ins supporting P2P streaming where plug-ins are often used in browser-based environment and with plug-ins http based streaming can be turned into a de facto P2P streaming( For the users and browsers, it's just http based streaming but the plug-ins are equipped with PPSP can actually accelerate the process from multiple sources/peers. In this case the plug-ins are just like the proxy.
   Can we merge them together?

BR
Yunfei

________________________________
zhangyunfei

From: Rui Cruz<mailto:rui.cruz@ieee.org>
Date: 2012-07-12 17:19
To: stefano previdi<mailto:sprevidi@cisco.com>
CC: Rui Cruz<mailto:rui.cruz@ieee.org>; ppsp<mailto:ppsp@ietf.org>; zhangyunfei Zhang<mailto:zhangyunfei@chinamobile.com>
Subject: Re: [ppsp] WG Last Call for draft-ietf-ppsp-problem-statement
Hi,

We would like to introduce a new Use Case that may be of interest.

The description would be as follows:


5.4. Proxy service supporting P2P streaming

For applications where the Peer is not co-located with the Media Player in the same device (e.g. the Peer is located in a Home Media Gateway), we can use a P2P Proxy, as shown in figure 6.

As shown in this figure 6, the P2P Proxy terminates the Tracker and Peer protools, allowing the  legacy presentation devices to access P2P content. In this figure the DLNA protocol is used to communicate with the presentation devices due to its wide deployement in the industry, but of course other protocols can be used.

   +----------------------------------------------------------------+
   |                                                                |
   |  0:Tracker Protocol +---------+                                |
   |  +----------------> | Tracker |                                |
   |  |                  +---------+                                |
   |  |                       ^                                     |
   |  |                       |                                     |
   |  |                    2: | Tracker Protocol                    |
   |  |                       |                                     |
   |  |             +---------|-------------------------------------|
   |  |             |         V                                     |
   |  |             |     +---------+                               |
   |  |  +----------|---> |  P2P    |<-------------------+          |
   |  |  |          |     |  Proxy  |       DLNA         |          |
   |  |  |3: Peer   |     +---------+       Protocol     |          |
   |  |  | Protocol |                                    |          |
   |  |  |          |                                    |          |
   |  V  V          |                                    V          |
   |  +-----------+ |        Home Domain            +------------+  |
   |  |  Outward  | |                               | DLNA  Pres.|  |
   |  |  Peer     | |                               | Devices    |  |
   |  +-----------+ |                               +------------+  |
   +----------------------------------------------------------------+

Figure 6 Proxy service Supporting P2P, with DLNA interface, for Home application



Regards,

Rui Cruz
rui.cruz@ieee.org<mailto:rui.cruz@ieee.org>

IST/INESC-ID/INOV - Lisbon, Portugal
__________________________________________
ppsp mailing list
ppsp@ietf.org<mailto:ppsp@ietf.org>
https://www.ietf.org/mailman/listinfo/ppsp

On 12/07/2012, at 09:46, stefano previdi wrote:


All,

we're (re)spin the WG last call process for the problem statement and
requirements draft. Note that the doc (originally separated drafts)
went already through one cycle of WG and IESG review so we don't expect
massive/substantial updates.

Title           : Problem Statement and Requirements of Peer-to-Peer Streaming Protocol (PPSP)
Author(s)       : Yunfei Zhang
                 Ning Zong
Filename        : draft-ietf-ppsp-problem-statement-09.txt

https://datatracker.ietf.org/doc/draft-ietf-ppsp-problem-statement

Thanks.

Yunfei & Stefano.
_______________________________________________
ppsp mailing list
ppsp@ietf.org<mailto:ppsp@ietf.org>
https://www.ietf.org/mailman/listinfo/ppsp

_______________________________________________
ppsp mailing list
ppsp@ietf.org<mailto:ppsp@ietf.org>
https://www.ietf.org/mailman/listinfo/ppsp





_______________________________________________

ppsp mailing list

ppsp@ietf.org<mailto:ppsp@ietf.org>

https://www.ietf.org/mailman/listinfo/ppsp