[httpstreaming] Current Status and Our Goal

Qin Wu <sunseawq@huawei.com> Mon, 27 September 2010 01:20 UTC

Return-Path: <sunseawq@huawei.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 E5EC13A6C1B for <httpstreaming@core3.amsl.com>; Sun, 26 Sep 2010 18:20:03 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 1.232
X-Spam-Level: *
X-Spam-Status: No, score=1.232 tagged_above=-999 required=5 tests=[AWL=-0.874, BAYES_50=0.001, FH_RELAY_NODNS=1.451, HELO_MISMATCH_COM=0.553, HTML_MESSAGE=0.001, RDNS_NONE=0.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 m7oGEmWxdN72 for <httpstreaming@core3.amsl.com>; Sun, 26 Sep 2010 18:20:02 -0700 (PDT)
Received: from szxga03-in.huawei.com (unknown [119.145.14.66]) by core3.amsl.com (Postfix) with ESMTP id 3C0593A6A58 for <httpstreaming@ietf.org>; Sun, 26 Sep 2010 18:20:02 -0700 (PDT)
Received: from huawei.com (szxga03-in [172.24.2.9]) by szxga03-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 2.14 (built Aug 8 2006)) with ESMTP id <0L9D00DE1T25NX@szxga03-in.huawei.com> for httpstreaming@ietf.org; Mon, 27 Sep 2010 09:20:29 +0800 (CST)
Received: from huawei.com ([172.24.2.119]) by szxga03-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 2.14 (built Aug 8 2006)) with ESMTP id <0L9D00C2ET25G0@szxga03-in.huawei.com> for httpstreaming@ietf.org; Mon, 27 Sep 2010 09:20:29 +0800 (CST)
Received: from w53375 ([10.138.84.79]) by szxml06-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 2.14 (built Aug 8 2006)) with ESMTPA id <0L9D00JV8T24K5@szxml06-in.huawei.com> for httpstreaming@ietf.org; Mon, 27 Sep 2010 09:20:29 +0800 (CST)
Date: Mon, 27 Sep 2010 09:20:26 +0800
From: Qin Wu <sunseawq@huawei.com>
To: httpstreaming@ietf.org
Message-id: <00df01cb5de2$2ac49730$4f548a0a@china.huawei.com>
MIME-version: 1.0
X-MIMEOLE: Produced By Microsoft MimeOLE V6.00.2900.3664
X-Mailer: Microsoft Outlook Express 6.00.2900.3664
Content-type: multipart/alternative; boundary="Boundary_(ID_fRpvY6N5nJoJ7KX2t9G79Q)"
X-Priority: 3
X-MSMail-priority: Normal
Subject: [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, 27 Sep 2010 01:20:04 -0000

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