Re: [httpstreaming] Current Status and Our Goal

Qin Wu <sunseawq@huawei.com> Thu, 14 October 2010 06:48 UTC

Return-Path: <sunseawq@huawei.com>
X-Original-To: httpstreaming@core3.amsl.com
Delivered-To: httpstreaming@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id E9F783A6822 for <httpstreaming@core3.amsl.com>; Wed, 13 Oct 2010 23:48:51 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 3.48
X-Spam-Level: ***
X-Spam-Status: No, score=3.48 tagged_above=-999 required=5 tests=[AWL=-2.828, BAYES_50=0.001, FH_RELAY_NODNS=1.451, HELO_MISMATCH_COM=0.553, MIME_BASE64_TEXT=1.753, MIME_CHARSET_FARAWAY=2.45, RDNS_NONE=0.1]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id jPar+GQQza64 for <httpstreaming@core3.amsl.com>; Wed, 13 Oct 2010 23:48:48 -0700 (PDT)
Received: from szxga05-in.huawei.com (unknown [119.145.14.67]) by core3.amsl.com (Postfix) with ESMTP id 81C5B3A6868 for <httpstreaming@ietf.org>; Wed, 13 Oct 2010 23:48:48 -0700 (PDT)
Received: from huawei.com (szxga05-in [172.24.2.49]) by szxga05-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 2.14 (built Aug 8 2006)) with ESMTP id <0LA900GI0PKH3Z@szxga05-in.huawei.com> for httpstreaming@ietf.org; Thu, 14 Oct 2010 14:48:17 +0800 (CST)
Received: from huawei.com ([172.24.2.119]) by szxga05-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 2.14 (built Aug 8 2006)) with ESMTP id <0LA900DCKPKGMM@szxga05-in.huawei.com> for httpstreaming@ietf.org; Thu, 14 Oct 2010 14:48:16 +0800 (CST)
Received: from w53375 ([10.138.41.48]) by szxml06-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 2.14 (built Aug 8 2006)) with ESMTPA id <0LA900JK3PKF1Y@szxml06-in.huawei.com> for httpstreaming@ietf.org; Thu, 14 Oct 2010 14:48:16 +0800 (CST)
Date: Thu, 14 Oct 2010 14:48:15 +0800
From: Qin Wu <sunseawq@huawei.com>
To: luzhihui <lzh@fudan.edu.cn>, Roni Even <Even.roni@huawei.com>, "'David A. Bryan'" <dbryan@ethernot.org>
Message-id: <03f801cb6b6b$c75e7480$30298a0a@china.huawei.com>
MIME-version: 1.0
X-MIMEOLE: Produced By Microsoft MimeOLE V6.00.2900.3664
X-Mailer: Microsoft Outlook Express 6.00.2900.3664
Content-type: text/plain; charset="gb2312"
Content-transfer-encoding: base64
X-Priority: 3
X-MSMail-priority: Normal
References: <00df01cb5de2$2ac49730$4f548a0a@china.huawei.com> <AANLkTimB3-=zWGnT=uq9Qcb-N8Pq+-RR0WMN12BZ9pr4@mail.gmail.com> <03f501cb65a1$50699d70$f13cd850$%roni@huawei.com> <201010121253579157105@fudan.edu.cn>
Cc: httpstreaming@ietf.org
Subject: Re: [httpstreaming] Current Status and Our Goal
X-BeenThere: httpstreaming@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Network based HTTP Streaming discussion list <httpstreaming.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/httpstreaming>, <mailto:httpstreaming-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/httpstreaming>
List-Post: <mailto:httpstreaming@ietf.org>
List-Help: <mailto:httpstreaming-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/httpstreaming>, <mailto:httpstreaming-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 14 Oct 2010 06:48:52 -0000

Hi,
----- Original Message ----- 
From: "luzhihui" <lzh@fudan.edu.cn>
To: "Qin Wu" <sunseawq@huawei.com>; "Roni Even" <Even.roni@huawei.com>; "'David A. Bryan'" <dbryan@ethernot.org>
Cc: <httpstreaming@ietf.org>
Sent: Wednesday, October 13, 2010 12:54 AM
Subject: Re: Re: [httpstreaming] Current Status and Our Goal


> 
> 
> ======= 2010-10-08 03:23:04 您在来信中写道:=======
> 
>>> In general I think that by having a use cases document that covers the
>>> scenarios that look important to the group we can achieve a better
>>> understanding of what is the charter of the work. 
>>
>>[Qin]: Good point, we do have some use cases which hasn't been taken out from 
>>HTTP Streaming Problem Statement draft (http://www.ietf.org/id/draft-wu-http-streaming-optimization-ps-02.txt).
>>Four typical use cases in my mind would be:
>>case 1: Live Streaming Media broadcast
>>case 2: RTP to HTTP Gateway, which is possible case to address multicast support.
> [ZhiHui] Qin, we know http is web content-oriented at begining, so we have Real Time Streaming Protocol (RTSP) and MMS (Microsoft Media Server protocol) 
> oriented for streaming,RTSP and MMS are based on RTP, they are popular for streaming content delivery. But now because of simplicity of HTTP, HTTP come 
> again for streaming.  We know this is HTTP "Second Spring"
> So Flash player now become more popular than Real player and Media Player.  But we know RTP protocol is very friendly to streaming content chunk.
> So, If we design  RTP to HTTP Gateway, we should consider how to utilize the existing advantages of RTP over TCP.

[Qin]: I am not sure we need to build such Gateway. The motivation to look deep into it is how to introduce multicast support for HTTP streaming.
One existing protocol we may look at is RTMP, one of features in RTMP is multicast support.

>>case 3: "Multi-Screen" Service Delivery
>>case 4:  Heterogeneous Handover
>>Hope it helps get a better understanding what the scenarios may may look like. If anybody would like to contribute to use case document
>>or provide more input, that will be great.
>>_______________________________________________
>>httpstreaming mailing list
>>httpstreaming@ietf.org
>>https://www.ietf.org/mailman/listinfo/httpstreaming
> 
> = = = = = = = = = = = = = = = = = = = =
> 
> 
> 
>      ZhiHui
>    
> Tel:021-65107607,65643187
> Fax:021-65647894
> Mob:13818168919
>           2010-10-12
>