IETF Logo Mail Archive

Re: [httpstreaming] Current Status and Our Goal

Mark Watson <watsonm@netflix.com> Sun, 10 October 2010 09:37 UTC

Return-Path: <watsonm@netflix.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 A4DCB3A67A8 for <httpstreaming@core3.amsl.com>; Sun, 10 Oct 2010 02:37:25 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.599
X-Spam-Level:
X-Spam-Status: No, score=-3.599 tagged_above=-999 required=5 tests=[AWL=0.000, BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-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 toCnxXMgxuot for <httpstreaming@core3.amsl.com>; Sun, 10 Oct 2010 02:37:23 -0700 (PDT)
Received: from mx2.netflix.com (mx2.netflix.com [208.75.77.145]) by core3.amsl.com (Postfix) with ESMTP id 3889A3A67A6 for <httpstreaming@ietf.org>; Sun, 10 Oct 2010 02:37:23 -0700 (PDT)
Received: from ExchFE102.netflix.com (exchfe102.netflix.com [10.64.32.102]) by mx2.netflix.com (8.12.11.20060308/8.12.11) with ESMTP id o9A9c3v5012103; Sun, 10 Oct 2010 02:38:03 -0700
Received: from EXCHMBX103.netflix.com ([fe80::c8e2:ac0e:d177:53c6]) by ExchFE102.netflix.com ([fe80::416e:22e0:ebdf:14b0%14]) with mapi; Sun, 10 Oct 2010 02:38:02 -0700
From: Mark Watson <watsonm@netflix.com>
To: Wenbo Zhu <wenboz@google.com>
Date: Sun, 10 Oct 2010 02:38:00 -0700
Thread-Topic: [httpstreaming] Current Status and Our Goal
Thread-Index: ActoXtSrlSdaGnzWTHOGXpIMITVk8w==
Message-ID: <E7071E49-4ED8-472A-87D7-B9BB2D8226E2@netflix.com>
References: <00df01cb5de2$2ac49730$4f548a0a@china.huawei.com> <AANLkTimB3-=zWGnT=uq9Qcb-N8Pq+-RR0WMN12BZ9pr4@mail.gmail.com> <03f501cb65a1$50699d70$f13cd850$%roni@huawei.com> <B1C30D3B-6D5C-46B9-848D-3AE0C8B6058C@csperkins.org> <9690AB8A-315E-4730-ABD8-78F4BB3E4CB6@nokia.com> <04CAD96D4C5A3D48B1919248A8FE0D540D5BF35F@xmb-sjc-215.amer.cisco.com> <AANLkTimc=72t59x-N+xDzL+AYc_g8Noa0=H8cHYZsrFs@mail.gmail.com> <04CAD96D4C5A3D48B1919248A8FE0D540D5BF3A0@xmb-sjc-215.amer.cisco.com> <AANLkTim1dPg-TtQ6Jm0y+pKdvvLbU1Xq4Q4d7w+aMeG9@mail.gmail.com> <04CAD96D4C5A3D48B1919248A8FE0D540D5BF3A1@xmb-sjc-215.amer.cisco.com> <AANLkTi=bPEOQku1bLLLEfOKb81dM3PWFeSmuURANP5sU@mail.gmail.com>
In-Reply-To: <AANLkTi=bPEOQku1bLLLEfOKb81dM3PWFeSmuURANP5sU@mail.gmail.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
acceptlanguage: en-US
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Cc: "httpstreaming@ietf.org" <httpstreaming@ietf.org>, Colin Perkins <csp@csperkins.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: Sun, 10 Oct 2010 09:37:26 -0000

On Oct 10, 2010, at 5:17 PM, Wenbo Zhu wrote:

> On Sun, Oct 10, 2010 at 12:45 AM, Ali C. Begen (abegen)
> <abegen@cisco.com> wrote:
>>>> Wanna give a specific example for "intermediaries"? I think you are referring to something besides the http caches.
>>> proxies.
>> 
>> What should a proxy support for streaming?
> Proxies don't know anything about streaming, and they only understand
> HTTP. If the goal is to optimize the transport, then clearly defined
> protocol semantics would be necessary for proxies to distinguish
> streaming traffic from regular HTTP traffic.

One of the great advantages of HTTP streaming as a technique is that the infrastructure is exactly common with that of the web. Requiring proxies to distinguish between "streaming" and "regular" traffic would break that.

Instead, if there are different behaviors which are considered advantageous for streaming, then these should be considered as general-purpose HTTP enhancements.

> 
>> 
>>>> 
>>>>> to offer direct support for streaming traffic, and different client
>>>>> platforms will also be able to improve end-user experience
>>>>> independently of vendor or media-protocol specific solutions.
>>>> 
>>>> Sure but is not that all client implementation, which is mostly left for product differentiation?
>>> I am interested to find out whether existing implementations (that
>>> have successfully deployed HTTP-based streaming over internet) expose
>>> streaming resource via open protocols or API's?
>> 
>> There are source codes floating around (with different licenses of course). Have you looked at OSMF and OVP?
>> http://openvideoplayer.sourceforge.net/
>> http://opensource.adobe.com/wiki/display/osmf/Open+Source+Media+Framework
> Thanks for the info.
> 
> - Wenbo
> 
>> 
>> -acbegen
>> 
>> 
> _______________________________________________
> httpstreaming mailing list
> httpstreaming@ietf.org
> https://www.ietf.org/mailman/listinfo/httpstreaming
>

v2.23.0 | Report a Bug | By Email