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

[Ben Niven-Jenkins <[e-mail]>]

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 [e-mail] list, thanks for including it & snipping the other lists.

>> From: [e-mail] [mailto:[e-mail]] 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