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

zhangyunfei <zhangyunfei@chinamobile.com> Fri, 13 July 2012 01:40 UTC

Return-Path: <zhangyunfei@chinamobile.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 16E2321F85D8 for <ppsp@ietfa.amsl.com>; Thu, 12 Jul 2012 18:40:37 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -97.845
X-Spam-Level:
X-Spam-Status: No, score=-97.845 tagged_above=-999 required=5 tests=[AWL=0.778, BAYES_00=-2.599, HTML_MESSAGE=0.001, MIME_BASE64_TEXT=1.753, RELAY_IS_221=2.222, 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 5UPtod2WhAv3 for <ppsp@ietfa.amsl.com>; Thu, 12 Jul 2012 18:40:35 -0700 (PDT)
Received: from imss.chinamobile.com (imss.chinamobile.com [221.130.253.135]) by ietfa.amsl.com (Postfix) with ESMTP id 3263D21F85D5 for <ppsp@ietf.org>; Thu, 12 Jul 2012 18:40:35 -0700 (PDT)
Received: from imss.chinamobile.com (localhost [127.0.0.1]) by localhost.chinamobile.com (Postfix) with ESMTP id 52337E3C0; Fri, 13 Jul 2012 09:41:06 +0800 (CST)
Received: from mail.chinamobile.com (unknown [10.1.28.22]) by imss.chinamobile.com (Postfix) with ESMTP id 38CC9E661; Fri, 13 Jul 2012 09:41:06 +0800 (CST)
Received: from zyf-PC ([10.2.53.144]) by mail.chinamobile.com (Lotus Domino Release 6.5.6) with ESMTP id 2012071309410419-2308 ; Fri, 13 Jul 2012 09:41:04 +0800
Date: Fri, 13 Jul 2012 09:40:58 +0800
From: zhangyunfei <zhangyunfei@chinamobile.com>
To: "Rui Cruz" <rui.cruz@ieee-pt.org>, yry <yry@cs.yale.edu>
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>, <43DD5F3C-FCA8-4EBB-9157-980F6E9A38A2@ieee-pt.org>
X-Priority: 3 (Normal)
X-Mailer: Foxmail 7.0.1.85[cn]
Mime-Version: 1.0
Message-ID: <201207130940587726843@chinamobile.com>
X-MIMETrack: Itemize by SMTP Server on jtgsml01/servers/cmcc(Release 6.5.6|March 06, 2007) at 2012-07-13 09:41:04, Serialize by Router on jtgsml01/servers/cmcc(Release 6.5.6|March 06, 2007) at 2012-07-13 09:41:05, Serialize complete at 2012-07-13 09:41:05
Content-Type: multipart/alternative; boundary="----=_001_NextPart824084550387_=----"
X-TM-AS-Product-Ver: IMSS-7.0.0.8231-6.8.0.1017-19036.003
X-TM-AS-Result: No--46.915-7.0-31-10
X-imss-scan-details: No--46.915-7.0-31-10;No--46.915-7.0-31-10
X-TM-AS-User-Approved-Sender: No;No
X-TM-AS-User-Blocked-Sender: No;No
Cc: 'Rui Cruz' <rui.cruz@ieee.org>, 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
Reply-To: zhangyunfei <zhangyunfei@chinamobile.com>
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 01:40:37 -0000

Hi Richard and Rui,
    Thanks for the suggestion. I agree with this sub-section idea and plan to add it in next version. 

BR
Yunfei




zhangyunfei

From: Rui Cruz
Date: 2012-07-12 23:56
To: Y. Richard Yang
CC: Rui Cruz; ppsp
Subject: Re: [ppsp] WG Last Call for draft-ietf-ppsp-problem-statement
Hi Richard and Yunfei,


Sub-sections on P2P proxy use case  seems a good idea.


Cumprimentos/Regards,
Rui Cruz


Sent from my iPad2

On 12/07/2012, at 16:34, "Y. Richard Yang" <yry@cs.yale.edu> wrote:


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


IST/INESC-ID/INOV - Lisbon, Portugal
__________________________________________
ppsp mailing list
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
Date: 2012-07-12 17:19
To: stefano previdi
CC: Rui Cruz; ppsp; zhangyunfei Zhang
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


IST/INESC-ID/INOV - Lisbon, Portugal
__________________________________________
ppsp mailing list
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
https://www.ietf.org/mailman/listinfo/ppsp



_______________________________________________
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



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