Re: [httpstreaming] [AVT] Fw: Agenda and Slides

Qin Wu <sunseawq@huawei.com> Mon, 08 November 2010 01:50 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 2F99328C113 for <httpstreaming@core3.amsl.com>; Sun, 7 Nov 2010 17:50:04 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.211
X-Spam-Level:
X-Spam-Status: No, score=-0.211 tagged_above=-999 required=5 tests=[AWL=-1.728, BAYES_00=-2.599, FAKE_REPLY_C=2.012, FH_RELAY_NODNS=1.451, HELO_MISMATCH_COM=0.553, 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 2BeMgyvfxj5W for <httpstreaming@core3.amsl.com>; Sun, 7 Nov 2010 17:50:03 -0800 (PST)
Received: from szxga03-in.huawei.com (unknown [119.145.14.66]) by core3.amsl.com (Postfix) with ESMTP id 3D18228C110 for <httpstreaming@ietf.org>; Sun, 7 Nov 2010 17:50:03 -0800 (PST)
Received: from huawei.com (szxga03-in [172.24.2.9]) by szxga03-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 2.14 (built Aug 8 2006)) with ESMTP id <0LBJ00KERMFOP0@szxga03-in.huawei.com> for httpstreaming@ietf.org; Mon, 08 Nov 2010 09:50:12 +0800 (CST)
Received: from huawei.com ([172.24.2.119]) by szxga03-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 2.14 (built Aug 8 2006)) with ESMTP id <0LBJ000HFMFO4V@szxga03-in.huawei.com> for httpstreaming@ietf.org; Mon, 08 Nov 2010 09:50:12 +0800 (CST)
Received: from jys1037603 ([125.35.86.138]) by szxml01-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 2.14 (built Aug 8 2006)) with ESMTPA id <0LBJ00K0NMFNHG@szxml01-in.huawei.com> for httpstreaming@ietf.org; Mon, 08 Nov 2010 09:50:12 +0800 (CST)
Date: Mon, 08 Nov 2010 09:50:21 +0800
From: Qin Wu <sunseawq@huawei.com>
To: httpstreaming <httpstreaming@ietf.org>
Message-id: <86E9B4F52CCD45C7877A2152517D8E9C@china.huawei.com>
MIME-version: 1.0
X-MIMEOLE: Produced By Microsoft MimeOLE V6.00.2900.5579
X-Mailer: Microsoft Outlook Express 6.00.2900.5843
Content-type: text/plain; charset=iso-8859-1
Content-transfer-encoding: 7BIT
X-Priority: 3
X-MSMail-priority: Normal
Subject: Re: [httpstreaming] [AVT] Fw: Agenda and Slides
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: Mon, 08 Nov 2010 01:50:04 -0000

Sorry, I forgot to drop other lists.
> ----- Original Message ----- 
> From: "Ben Niven-Jenkins" <ben@niven-jenkins.co.uk>
> To: "Qin Wu" <sunseawq@huawei.com>
> Cc: <avt@ietf.org>rg>; <fecframe@ietf.org>rg>; <ietf-http-wg@w3.org>rg>; <hybi@ietf.org>
> Sent: Sunday, November 07, 2010 11:54 PM
> Subject: Re: [AVT] Fw: [httpstreaming] Agenda and Slides
> 
> 
> Colleagues,
> 
> Reading the slides I'd like to make some comments in advance of the bar-bof, we can discuss them more via the mailing list or in the bar-BoF itself.
> 
> HTTP_Stream_1.ppt Slide 14:
> 
> "
> No distinction regular HTTP traffic from HTTP Streaming traffic
>  Disadvantage:
>   Transport streaming media in the same way as web page
>   transport Streaming media has no priority to be delivered/processed first
> "
> 
> This is not correct, it is possible to apply different treatment to HTTP Streaming traffic Vs "regular" web page traffic, e.g. by the server setting different TOS/DSCP for streaming Vs "web" traffic.

[Qin]: There are two different levels for service differential
 1evel 1: How to separate HTTP streaming service from High Speed Internet Service(HSI) Since HTTP streaming service and HSI share the same channel and HTTP Streaming service may require more bandwidth or other resource to support high quality content delivery. If the serve can do some mark in the HTTP header and there is some smart cache with intelligence to understand this mark situated between the server and client, the smart cache can treat HTTP streaming traffic in the different way as web traffic.
 
 level2:   How to treat different HTTP streaming traffic with different priorities.
 This is more precise granularity of service differential. If there is way to do this, HD HTTP streaming can be treated in the different way as SD HTTP Streaming. 
 Smart cache is one way to do this.
 
 As for these two levels of service differential, I agree there is other ways to deal with it, I just think it is quite interesting issue to me, when I dig this problem out 
> 
> On 7 Nov 2010, at 07:11, Qin Wu wrote:
> 
>> FYI.
>> ----- Original Message ----- 
>> From: "David A. Bryan" <dbryan@ethernot.org>
>> To: "httpstreaming" <httpstreaming@ietf.org>
>> Sent: Sunday, November 07, 2010 2:37 PM
>> Subject: [httpstreaming] Agenda and Slides
>> 
>> 
>>> I just uploaded an agenda and the current slides from the
>>> participants. The slides are available as links from the agenda, which
>>> I have uploaded here:
>>> 
>>> http://www.p2psip.org/httpstream/79/Agenda.html
>>> 
>>> I still don't know which room is the IESG room, but I will find out
>>> and post here shortly.
>>> 
>>> Thanks, and see you all on Wed.
>>> 
>>> David
>>> _______________________________________________
>>> httpstreaming mailing list
>>> httpstreaming@ietf.org
>>> https://www.ietf.org/mailman/listinfo/httpstreaming
>>> 
>> _______________________________________________
>> Audio/Video Transport Working Group
>> avt@ietf.org
>> https://www.ietf.org/mailman/listinfo/avt
> 
>