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

Ben Niven-Jenkins <ben@niven-jenkins.co.uk> Sun, 07 November 2010 16:15 UTC

Return-Path: <ben@niven-jenkins.co.uk>
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 DCD573A67CC for <httpstreaming@core3.amsl.com>; Sun, 7 Nov 2010 08:15:23 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -105.349
X-Spam-Level:
X-Spam-Status: No, score=-105.349 tagged_above=-999 required=5 tests=[AWL=-1.750, BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1, USER_IN_WHITELIST=-100]
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 Pca9N6hY3SuQ for <httpstreaming@core3.amsl.com>; Sun, 7 Nov 2010 08:15:23 -0800 (PST)
Received: from mailex.mailcore.me (mailex.mailcore.me [94.136.40.61]) by core3.amsl.com (Postfix) with ESMTP id D5FC63A679C for <httpstreaming@ietf.org>; Sun, 7 Nov 2010 08:15:22 -0800 (PST)
Received: from [222.128.202.2] (helo=[10.40.78.199]) by mail11.atlas.pipex.net with esmtpa (Exim 4.71) (envelope-from <ben@niven-jenkins.co.uk>) id 1PF7u7-0001av-Ok; Sun, 07 Nov 2010 16:15:41 +0000
Mime-Version: 1.0 (Apple Message framework v1081)
Content-Type: text/plain; charset=windows-1252
From: Ben Niven-Jenkins <ben@niven-jenkins.co.uk>
In-Reply-To: <04CAD96D4C5A3D48B1919248A8FE0D540D9B4260@xmb-sjc-215.amer.cisco.com>
Date: Sun, 7 Nov 2010 16:15:35 +0000
Content-Transfer-Encoding: quoted-printable
Message-Id: <3151D5E6-E534-4C1D-978E-7F214B31DFB2@niven-jenkins.co.uk>
References: <249792B19B4845578D9BDC3F77C12D68@china.huawei.com> <58D167AC-E817-4256-88D0-42E36492C562@niven-jenkins.co.uk> <04CAD96D4C5A3D48B1919248A8FE0D540D9B4260@xmb-sjc-215.amer.cisco.com>
To: "Ali C. Begen (abegen)" <abegen@cisco.com>
X-Mailer: Apple Mail (2.1081)
X-Mailcore-Auth: 9600544
X-Mailcore-Domain: 172912
Cc: httpstreaming@ietf.org
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: Sun, 07 Nov 2010 16:15:24 -0000

On 7 Nov 2010, at 16:04, Ali C. Begen (abegen) wrote:

> Interestingly, several other lists were copied to this email but not the main httpstreaming list. I would recommend dropping other lists. One comment inline.
> 

Ah! I just replied to the original e-mail which appears not to have included the httpstreaming@ietf.org list, thanks for including it & snipping the other lists.

>> From: avt-bounces@ietf.org [mailto:avt-bounces@ietf.org] On Behalf Of Ben Niven-Jenkins
>> 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.
> 
> If the network will not respect to these code points (which is the case in the open Internet), this won’t help but the servers themselves can prioritize anything they want to in their scheduling or processing. But, I am having difficulty in understanding why this is relevant to a standardization work. It looks to me as a product feature differentiation.

Agreed. IMO this is purely a deployment/implementation issue and not something that needs any standardisation.

Ben