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

Rui Cruz <rui.cruz@ieee-pt.org> Thu, 12 July 2012 15:55 UTC

Return-Path: <rui.cruz@ieee-pt.org>
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 8AB9911E8073 for <ppsp@ietfa.amsl.com>; Thu, 12 Jul 2012 08:55:09 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.202
X-Spam-Level:
X-Spam-Status: No, score=-2.202 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HTML_MESSAGE=0.001, MIME_QP_LONG_LINE=1.396, RCVD_IN_DNSWL_LOW=-1]
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 mwvxVg8pbEgr for <ppsp@ietfa.amsl.com>; Thu, 12 Jul 2012 08:55:08 -0700 (PDT)
Received: from mail-wg0-f44.google.com (mail-wg0-f44.google.com [74.125.82.44]) by ietfa.amsl.com (Postfix) with ESMTP id 74E3D21F85C6 for <ppsp@ietf.org>; Thu, 12 Jul 2012 08:55:07 -0700 (PDT)
Received: by wgbdr13 with SMTP id dr13so1589041wgb.13 for <ppsp@ietf.org>; Thu, 12 Jul 2012 08:55:39 -0700 (PDT)
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=references:in-reply-to:mime-version:content-type:message-id :content-transfer-encoding:cc:x-mailer:from:subject:date:to :x-gm-message-state; bh=oAORKlnYuwp6ve4tx5+1vA9tim8VZftgJ2CbXIPmQ4U=; b=S1I+MAUAYO4CVI1gPArwVr3g8MZzg4Nws74uJW/je0X1kS+XNm9NaDhsKFjESr5AeA 2wC8p/Sc5HtE47KIVTnt8t4kRj0da+APdil1/yabV6xC1+DiDvENQ1O2Y/PW9lVWNEnl ObQqpcY3c3W7KdPPeMRDO3hBFxJuSEY+4oDRB1/1FE2C1KdoQUWCJzSXLYk82TG8Xilc +TtaCvGrAOp7qo2zscVwZ0Oqge8Lb3aboVaNTB7g6ObeRQFTsPqgMmmEc9oBRsbx2W4l /UuDgiuMnXiXOs15ciC3n4tnYUT/WZeiEa1yC4+zBkr4ToHVEsqPIxIWiyovGahIXwI5 21VQ==
Received: by 10.180.81.193 with SMTP id c1mr29620324wiy.12.1342108539443; Thu, 12 Jul 2012 08:55:39 -0700 (PDT)
Received: from [192.168.1.101] (62.169.125.218.rev.optimus.pt. [62.169.125.218]) by mx.google.com with ESMTPS id t7sm14245159wix.6.2012.07.12.08.55.35 (version=TLSv1/SSLv3 cipher=OTHER); Thu, 12 Jul 2012 08:55:38 -0700 (PDT)
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>
Mime-Version: 1.0 (1.0)
Content-Type: multipart/alternative; boundary=Apple-Mail-8433DB63-DC4E-4776-A141-2678D4A1829C
Message-Id: <43DD5F3C-FCA8-4EBB-9157-980F6E9A38A2@ieee-pt.org>
Content-Transfer-Encoding: 7bit
X-Mailer: iPad Mail (9B206)
From: Rui Cruz <rui.cruz@ieee-pt.org>
Date: Thu, 12 Jul 2012 16:56:48 +0100
To: "Y. Richard Yang" <yry@cs.yale.edu>
X-Gm-Message-State: ALoCoQnxILAU8oXoKo2UW01489mK9nwkF4/MEk+DsEiBOE7WYmlX//jmhmzul45A+iFtuAl/oj0n
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
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: Thu, 12 Jul 2012 15:55:09 -0000

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