Re: [httpstreaming] Current Status and Our Goal

"David A. Bryan" <dbryan@ethernot.org> Wed, 29 September 2010 18:58 UTC

Return-Path: <davidbryan@gmail.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 900413A6901 for <httpstreaming@core3.amsl.com>; Wed, 29 Sep 2010 11:58:27 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -101.604
X-Spam-Level:
X-Spam-Status: No, score=-101.604 tagged_above=-999 required=5 tests=[AWL=0.373, BAYES_00=-2.599, FM_FORGED_GMAIL=0.622, 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 wKV00IZ61RRY for <httpstreaming@core3.amsl.com>; Wed, 29 Sep 2010 11:58:26 -0700 (PDT)
Received: from mail-wy0-f172.google.com (mail-wy0-f172.google.com [74.125.82.172]) by core3.amsl.com (Postfix) with ESMTP id 347F23A6C7B for <httpstreaming@ietf.org>; Wed, 29 Sep 2010 11:58:26 -0700 (PDT)
Received: by wyi11 with SMTP id 11so1241330wyi.31 for <httpstreaming@ietf.org>; Wed, 29 Sep 2010 11:59:09 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:sender:received :in-reply-to:references:date:x-google-sender-auth:message-id:subject :from:to:cc:content-type:content-transfer-encoding; bh=t8a9Ciuqebpn1fQy3MoHVeKroz8tNc8/8tfTBDrVG3E=; b=e39ACKY/0JCUW3d2zQQjE4pCmsg98yQOt0VJlqK8xOdFEELWpATjdyyhOEb7eSw/+L /prUUSNfpoxRDEN1UzLAGmrWlRVGIbJ9Atg7ISNAvBOh0px3ICQTlQfoyPjyUDrBxBgZ pm20LoWIGhnesbOchYcYMuXqdUV5+cY45H+Cw=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:sender:in-reply-to:references:date :x-google-sender-auth:message-id:subject:from:to:cc:content-type :content-transfer-encoding; b=tAqyu5dyFZq7VrBzc+HgIeu0AXy4yNECWAUuSmJccaY6PMsV21o0mdtNX+paXi3D8V uSQ7qnHmbLV1jpPdgxT+QxGeJnRTgQGk4oKGMFF1Yn/MpPDCCJQdp4m9HW8MVdTiMb2i NQjffsDK/lJ2e0k6klVapD9VbIIrAPPcpK4fM=
MIME-Version: 1.0
Received: by 10.216.23.4 with SMTP id u4mr1798515weu.96.1285786749447; Wed, 29 Sep 2010 11:59:09 -0700 (PDT)
Sender: davidbryan@gmail.com
Received: by 10.216.86.78 with HTTP; Wed, 29 Sep 2010 11:59:09 -0700 (PDT)
In-Reply-To: <00df01cb5de2$2ac49730$4f548a0a@china.huawei.com>
References: <00df01cb5de2$2ac49730$4f548a0a@china.huawei.com>
Date: Wed, 29 Sep 2010 14:59:09 -0400
X-Google-Sender-Auth: oEwY_DAcGd2G0G3Ta3U-gjC6MxU
Message-ID: <AANLkTimB3-=zWGnT=uq9Qcb-N8Pq+-RR0WMN12BZ9pr4@mail.gmail.com>
From: "David A. Bryan" <dbryan@ethernot.org>
To: Qin Wu <sunseawq@huawei.com>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable
Cc: httpstreaming@ietf.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: Wed, 29 Sep 2010 18:58:27 -0000

So we have had a number of threads, some about possible work, some
about details in the charter, etc. I think it is great to start
thinking about a possible charter if this work turns into a WG, and
some good reference drafts (thanks to Qin and the folks from Apple for
putting these together), but I think another way to look at this might
be to at least initially take a step back and see if the folks on the
list can take a stab at some more basic questions. I think that was
perhaps what Qin was getting at when we started this thread, but it is
always good to refocus.

I'll ask two really basic questions to the folks on list, and let's
see what the opinions may be, and maybe we can move forward from
there. Personally, I think that if we have a bar BoF, focusing just on
these two basic questions (ok, one is a compound question, but one is
basic!) might be a good way to move forward. I expect we'll have some
VERY different answers. Remember that HTTP streaming may mean
different things to people, and might even be the wrong term...but
these are the things we need to try to figure out.

So the two big questions:

1) On the topic of this list/HTTP streaming, what do you think is the
problem/problems/scenario we should be looking at?

2) What other standards body work in this space are you aware of
(including IETF work), and how do you think any new work would fit in
(or not!) with the answer above?

Yep, these are really broad, but to me, they seem to be at the heart
of what we need to figure out to move forward. I think that at the
beginning of this thread these were the basic questions Qin was
looking to answer, and I think they are a great place to start.

David

2010/9/26 Qin Wu <sunseawq@huawei.com>om>:
> 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
>
>