IETF Logo Mail Archive

Re: [httpstreaming] Current Status and Our Goal

Wenbo Zhu <wenboz@google.com> Mon, 11 October 2010 03:58 UTC

Return-Path: <wenboz@google.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 4EFA53A68BD for <httpstreaming@core3.amsl.com>; Sun, 10 Oct 2010 20:58:46 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.777
X-Spam-Level:
X-Spam-Status: No, score=-106.777 tagged_above=-999 required=5 tests=[AWL=-0.800, BAYES_00=-2.599, FM_FORGED_GMAIL=0.622, RCVD_IN_DNSWL_MED=-4, 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 YnAU0zKhkpjy for <httpstreaming@core3.amsl.com>; Sun, 10 Oct 2010 20:58:44 -0700 (PDT)
Received: from smtp-out.google.com (smtp-out.google.com [216.239.44.51]) by core3.amsl.com (Postfix) with ESMTP id DAB933A68C7 for <httpstreaming@ietf.org>; Sun, 10 Oct 2010 20:58:40 -0700 (PDT)
Received: from wpaz17.hot.corp.google.com (wpaz17.hot.corp.google.com [172.24.198.81]) by smtp-out.google.com with ESMTP id o9B3xpl8004905 for <httpstreaming@ietf.org>; Sun, 10 Oct 2010 20:59:51 -0700
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed/relaxed; d=google.com; s=beta; t=1286769591; bh=m7+sEa3gSUvykqTFVHvQE8F9v40=; h=MIME-Version:In-Reply-To:References:Date:Message-ID:Subject:From: To:Cc:Content-Type; b=FAN18zXr4sug93mszK2Uovei4wmhlyUmeZ3Vc7n9asXG6qym0LtAW+PZBMpVfBXR9 X1lKK+0Cn35cklpCILTLg==
Received: from gxk10 (gxk10.prod.google.com [10.202.11.10]) by wpaz17.hot.corp.google.com with ESMTP id o9B3xoH0018797 for <httpstreaming@ietf.org>; Sun, 10 Oct 2010 20:59:50 -0700
Received: by gxk10 with SMTP id 10so633989gxk.12 for <httpstreaming@ietf.org>; Sun, 10 Oct 2010 20:59:50 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=beta; h=domainkey-signature:mime-version:received:received:in-reply-to :references:date:message-id:subject:from:to:cc:content-type; bh=VCuQotEBqS5opiDzyibUsTp87TFBYe8mK1YBdUj4U1I=; b=rfoHUetzPnvcwpXcT4vlq8hdPnVlSntdrU0upltSRTn/v1B18cfvPl0uPLQpTv9Z+j IAgOnSwCTQt8Vp0xebYA==
DomainKey-Signature: a=rsa-sha1; c=nofws; d=google.com; s=beta; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; b=RynS1r9gf68zdaVzTh/ziUr7Dkwdck/1eL96Qg9wTT14xwSZi1bx/LJaPnKmoTGpil Pq5rCXcTEBEvHF8M5AhQ==
MIME-Version: 1.0
Received: by 10.90.103.5 with SMTP id a5mr2960558agc.97.1286769588143; Sun, 10 Oct 2010 20:59:48 -0700 (PDT)
Received: by 10.91.213.18 with HTTP; Sun, 10 Oct 2010 20:59:48 -0700 (PDT)
In-Reply-To: <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> <E7071E49-4ED8-472A-87D7-B9BB2D8226E2@netflix.com>
Date: Sun, 10 Oct 2010 20:59:48 -0700
Message-ID: <AANLkTi=Rnq0cnOOcVQXyeDdKBKvAoApeZidVjQT1=yPU@mail.gmail.com>
From: Wenbo Zhu <wenboz@google.com>
To: Mark Watson <watsonm@netflix.com>
Content-Type: text/plain; charset="ISO-8859-1"
X-System-Of-Record: true
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: Mon, 11 Oct 2010 03:58:46 -0000

On Sun, Oct 10, 2010 at 2:38 AM, Mark Watson <watsonm@netflix.com> wrote:
>
> 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.
Agreed. I could have worded this differently.

>
> Instead, if there are different behaviors which are considered advantageous for streaming, then these should be considered as general-purpose HTTP enhancements.
There is no need to enhance HTTP! It's about the ability to advise
streaming capabilities so that proxies that do choose to understand
streaming will be able to optimize and honor the streaming behaviors
that are specified on top of HTTP.
>
>>
>>>
>>>>>
>>>>>> 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