Re: [httpstreaming] Current Status and Our Goal

Wenbo Zhu <wenboz@google.com> Tue, 28 September 2010 08:03 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 A49473A6D78 for <httpstreaming@core3.amsl.com>; Tue, 28 Sep 2010 01:03:20 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.643
X-Spam-Level:
X-Spam-Status: No, score=-106.643 tagged_above=-999 required=5 tests=[AWL=-0.667, BAYES_00=-2.599, FM_FORGED_GMAIL=0.622, HTML_MESSAGE=0.001, 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 zrqjSrGid3ih for <httpstreaming@core3.amsl.com>; Tue, 28 Sep 2010 01:03:19 -0700 (PDT)
Received: from smtp-out.google.com (smtp-out.google.com [74.125.121.35]) by core3.amsl.com (Postfix) with ESMTP id 05FB93A6D5D for <httpstreaming@ietf.org>; Tue, 28 Sep 2010 01:03:18 -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 o8S83wW3017531 for <httpstreaming@ietf.org>; Tue, 28 Sep 2010 01:03:58 -0700
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed/relaxed; d=google.com; s=beta; t=1285661039; bh=oIPHFDpr1yOrcUZCVavvxcqsbMQ=; h=MIME-Version:In-Reply-To:References:Date:Message-ID:Subject:From: To:Content-Type; b=FNAp4UE/8QuaIf/sUs2nBVrlyD9QoWhcTQf/Dli4aOkOzDKssmvJR4NtfkXoikMwp 2W2ZWq5AcSRYWTCiPvEtg==
Received: from yxd5 (yxd5.prod.google.com [10.190.1.197]) by wpaz17.hot.corp.google.com with ESMTP id o8S83vuP012922 for <httpstreaming@ietf.org>; Tue, 28 Sep 2010 01:03:57 -0700
Received: by yxd5 with SMTP id 5so1866271yxd.9 for <httpstreaming@ietf.org>; Tue, 28 Sep 2010 01:03:57 -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:content-type; bh=d91xWeA3UQI51DeistVzwVX8UdWqrv/QFZjd03//dmY=; b=RPRyZWTiu82IZZ55Rv1AjnauhKiWchxgst1T6XFRW0ezmzDIbZK6tnxRh9znPC5T0n AARfzKG7FJmVWwdRvYsQ==
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 :content-type; b=ttdXlS7CYp+sieC8jsOaRwUdDYG91N67gLsHTRo2ITYQl5sRlQ2ygjI1wzDTOEAgJO fTtef3Vj8ZQ8+MTkPCzw==
MIME-Version: 1.0
Received: by 10.90.27.2 with SMTP id a2mr6258706aga.56.1285661035531; Tue, 28 Sep 2010 01:03:55 -0700 (PDT)
Received: by 10.91.213.18 with HTTP; Tue, 28 Sep 2010 01:03:55 -0700 (PDT)
In-Reply-To: <00df01cb5de2$2ac49730$4f548a0a@china.huawei.com>
References: <00df01cb5de2$2ac49730$4f548a0a@china.huawei.com>
Date: Tue, 28 Sep 2010 01:03:55 -0700
Message-ID: <AANLkTinrHhAJEXg=ev0=Z+rfxJx2mf_=xCXVr4ue_fiG@mail.gmail.com>
From: Wenbo Zhu <wenboz@google.com>
To: httpstreaming@ietf.org
Content-Type: multipart/alternative; boundary=0016e6509cca530c6804914d4947
X-System-Of-Record: true
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: Tue, 28 Sep 2010 08:03:20 -0000

Thanks for putting all these together, and I definitely see the value in
standardizing media streaming semantics on top of HTTP.

A few meta-comments related to the subject of "HTTP streaming"
1. focus on HTTP and exclude any ambiguity that a different transport may be
considered;
2. make it clear that this work is agnostic to emerging Web protocols/specs
that are fundamentally browser-oriented;
3. avoid any attempt to extend the basic HTTP semantics (e.g. in conflict
with httpbis)

- Wenbo


On Sun, Sep 26, 2010 at 6:20 PM, Qin Wu <sunseawq@huawei.com> wrote:

>  Hi, folks:
> We have planned to have a BarBOF in time for Beijing IETF meeting.
>
> The primary goal of this BarBOF is to making sure that people agree on what
> problem (or problems) need to be solved;
> Some of these problems or interesting issues are summarized in my previous
> email available at
> (http://www.ietf.org/mail-archive/web/httpstreaming/current/msg00002.html)
> which was raised by people who are interested
> in HTTP Streaming in the  DISPATCH mailing list before we move to this new
> discussion list.
> The other problems come from HTTP streaming Problem statement
> draft which I have updated recently
> (
> http://www.ietf.org/internet-drafts/draft-wu-http-streaming-optimization-ps-01.txt
> ).
>
> Another goal is to make sure we have not any overlapping with other SDO.
>
> In order to stimulate the discussion toward these two goals, I have crafted
> intial charter skeleton.
> http://www.ietf.org/mail-archive/web/httpstreaming/current/msg00003.html
>
> I would like us to center around these problems we listed and the intial
> charter skeleton I drafted to figure out
> (a) what kind of use cases can we  have
> (b) and how many problems are worth being discussed
> (c) Is there any challenging issues we missed or neglected?
> (d) and what kind of concrete protocol/mechanism/scheme can we  come up
> with?
>
> Also I would like to point out some related works in IETF for your
> references. Curretly what we have on the table includes:
> Apples' HTTP live streaming
> http://tools.ietf.org/html/draft-pantos-http-live-streaming-04
> HTTP Streaming Problem Statement
> http://tools.ietf.org/html/draft-wu-http-streaming-optimization-ps-001
> Implications of Full-Duplex HTTP
> http://tools.ietf.org/html/draft-zhu-http-fullduplex-01
> If there is any related work missing or wrong, please let me know. Also I
> would like to encourage people to bring your contributions
> and thoughts in draft to this discussion list.
>
> Regards!
> -Qin
>
>
> _______________________________________________
> httpstreaming mailing list
> httpstreaming@ietf.org
> https://www.ietf.org/mailman/listinfo/httpstreaming
>
>