Re: [httpstreaming] Current Status and Our Goal

Wenbo Zhu <wenboz@google.com> Sun, 10 October 2010 07:37 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 E92693A67D9 for <httpstreaming@core3.amsl.com>; Sun, 10 Oct 2010 00:37:57 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -107.31
X-Spam-Level:
X-Spam-Status: No, score=-107.31 tagged_above=-999 required=5 tests=[AWL=-1.333, 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 6mWwAWR7DYpk for <httpstreaming@core3.amsl.com>; Sun, 10 Oct 2010 00:37:56 -0700 (PDT)
Received: from smtp-out.google.com (smtp-out.google.com [216.239.44.51]) by core3.amsl.com (Postfix) with ESMTP id 83BAF3A67D6 for <httpstreaming@ietf.org>; Sun, 10 Oct 2010 00:37:56 -0700 (PDT)
Received: from kpbe19.cbf.corp.google.com (kpbe19.cbf.corp.google.com [172.25.105.83]) by smtp-out.google.com with ESMTP id o9A7d5p0021617 for <httpstreaming@ietf.org>; Sun, 10 Oct 2010 00:39:05 -0700
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed/relaxed; d=google.com; s=beta; t=1286696345; bh=eRTKPl6vPQt+QupeMc7p0Lfj1pk=; h=MIME-Version:In-Reply-To:References:Date:Message-ID:Subject:From: To:Cc:Content-Type; b=ReCDOc12eBF8MYtv3uJkUXDi3FvXm2Bp047ygrGz/aGpNOEf6sIsOqPn/xl3gVZTr IG0I3c04f26VCiCL/J7tw==
Received: from gxk19 (gxk19.prod.google.com [10.202.11.19]) by kpbe19.cbf.corp.google.com with ESMTP id o9A7d3fg032058 for <httpstreaming@ietf.org>; Sun, 10 Oct 2010 00:39:04 -0700
Received: by gxk19 with SMTP id 19so215972gxk.36 for <httpstreaming@ietf.org>; Sun, 10 Oct 2010 00:39:03 -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=Rvs9naadIB3+KgHNl9bqhYlWJiNOnnrq4zIbpQXm0/k=; b=w8wamUk8ap3bzvA15sjXCnxdRUNydXRhGkbqrYFOzYxHwJOu21h2An1XIRP0fD++aL mtxJGm2hHhLYLgoYe7fQ==
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=gar+xB3w64/7jYb/h8kwv+EPqtrcobJb1s1OvSstzkUBC6V+x6i0ne38MWYsoyBKh7 vhBtHQLBdHJlUadigKnw==
MIME-Version: 1.0
Received: by 10.90.83.13 with SMTP id g13mr2429263agb.34.1286696340984; Sun, 10 Oct 2010 00:39:00 -0700 (PDT)
Received: by 10.91.213.18 with HTTP; Sun, 10 Oct 2010 00:39:00 -0700 (PDT)
In-Reply-To: <04CAD96D4C5A3D48B1919248A8FE0D540D5BF3A0@xmb-sjc-215.amer.cisco.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>
Date: Sun, 10 Oct 2010 00:39:00 -0700
Message-ID: <AANLkTim1dPg-TtQ6Jm0y+pKdvvLbU1Xq4Q4d7w+aMeG9@mail.gmail.com>
From: Wenbo Zhu <wenboz@google.com>
To: "Ali C. Begen (abegen)" <abegen@cisco.com>
Content-Type: text/plain; charset="ISO-8859-1"
X-System-Of-Record: true
Cc: 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 07:37:58 -0000

On Sun, Oct 10, 2010 at 12:32 AM, Ali C. Begen (abegen)
<abegen@cisco.com> wrote:
>
>
>> -----Original Message-----
>> From: Wenbo Zhu [mailto:wenboz@google.com]
>> Sent: Sunday, October 10, 2010 3:27 PM
>> To: Ali C. Begen (abegen)
>> Cc: Lars Eggert; Colin Perkins; httpstreaming@ietf.org
>> Subject: Re: [httpstreaming] Current Status and Our Goal
>>
>> On Sat, Oct 9, 2010 at 9:43 AM, Ali C. Begen (abegen) <abegen@cisco.com> wrote:
>> >
>> >
>> >> -----Original Message-----
>> >> From: httpstreaming-bounces@ietf.org [mailto:httpstreaming-bounces@ietf.org] On Behalf Of Lars Eggert
>> >> Sent: Friday, October 08, 2010 4:17 PM
>> >> To: Colin Perkins
>> >> Cc: httpstreaming@ietf.org
>> >> Subject: Re: [httpstreaming] Current Status and Our Goal
>> >>
>> >> On 2010-10-7, at 14:16, Colin Perkins wrote:
>> >> > There are clearly some issues to consider here. What seems to be
>> >> > missing from the discussion to me though, is some identification of
>> >> > the concrete problems. What protocol pieces do we need, but not have?
>> >> > What protocols are problematic, and need enhancement? Is there
>> >> > protocol work to do in IETF, or should we be documenting best current
>> >> > practices for using the existing protocols and/or relying on other
>> >> > bodies to fill the gaps?
>> >> >
>> >> > The draft-wu-http-streaming-optimization-ps is a good start at such an
>> >> > analysis, but doesn't go deep enough to let us decide what work IETF
>> >> > should do.
>> >>
>> >> +1
>> >>
>> >> The key question really is "what do you think the IETF needs to do?"
>> >
>> > I imagine the only work the IETF should do (if we decide to) is the transport and HTTP-layer optimization for better
>> streaming performance.
>> Or more importantly to standardize existing or proposed optimizations
>> for improved interoperability, with which intermediaries will be able
>
> Wanna give a specific example for "intermediaries"? I think you are referring to something besides the http caches.
proxies.

>
>> 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?

- Wenbo

>
> -acbegen
>
>> - Wenbo
>>
>>
>> >
>> > -acbegen
>> >
>> >> Lars
>> > _______________________________________________
>> > httpstreaming mailing list
>> > httpstreaming@ietf.org
>> > https://www.ietf.org/mailman/listinfo/httpstreaming
>> >
>