Re: [httpstreaming] Current Status and Our Goal

Roni Even <Even.roni@huawei.com> Wed, 06 October 2010 21:57 UTC

Return-Path: <Even.roni@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 6BBCA3A7053 for <httpstreaming@core3.amsl.com>; Wed, 6 Oct 2010 14:57:59 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -99.785
X-Spam-Level:
X-Spam-Status: No, score=-99.785 tagged_above=-999 required=5 tests=[AWL=-0.779, BAYES_05=-1.11, FH_RELAY_NODNS=1.451, HELO_MISMATCH_COM=0.553, RDNS_NONE=0.1, 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 xXdrebNBRurJ for <httpstreaming@core3.amsl.com>; Wed, 6 Oct 2010 14:57:57 -0700 (PDT)
Received: from szxga05-in.huawei.com (unknown [119.145.14.67]) by core3.amsl.com (Postfix) with ESMTP id 9AA693A6FA2 for <httpstreaming@ietf.org>; Wed, 6 Oct 2010 14:57:57 -0700 (PDT)
Received: from huawei.com (szxga05-in [172.24.2.49]) by szxga05-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 2.14 (built Aug 8 2006)) with ESMTP id <0L9W00FEV2E0B2@szxga05-in.huawei.com> for httpstreaming@ietf.org; Thu, 07 Oct 2010 05:58:48 +0800 (CST)
Received: from huawei.com ([172.24.2.119]) by szxga05-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 2.14 (built Aug 8 2006)) with ESMTP id <0L9W0073I2DZDZ@szxga05-in.huawei.com> for httpstreaming@ietf.org; Thu, 07 Oct 2010 05:58:48 +0800 (CST)
Received: from windows8d787f9 (bzq-79-183-35-90.red.bezeqint.net [79.183.35.90]) by szxml02-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 2.14 (built Aug 8 2006)) with ESMTPA id <0L9W000JX2DQ1L@szxml02-in.huawei.com>; Thu, 07 Oct 2010 05:58:47 +0800 (CST)
Date: Wed, 06 Oct 2010 23:56:12 +0200
From: Roni Even <Even.roni@huawei.com>
In-reply-to: <AANLkTimB3-=zWGnT=uq9Qcb-N8Pq+-RR0WMN12BZ9pr4@mail.gmail.com>
To: "'David A. Bryan'" <dbryan@ethernot.org>, 'Qin Wu' <sunseawq@huawei.com>
Message-id: <03f501cb65a1$50699d70$f13cd850$%roni@huawei.com>
MIME-version: 1.0
X-Mailer: Microsoft Office Outlook 12.0
Content-type: text/plain; charset=us-ascii
Content-language: en-us
Content-transfer-encoding: 7BIT
Thread-index: ActgCGuD1NnF29rfRjaXK8fG462/2gFlt4Pw
References: <00df01cb5de2$2ac49730$4f548a0a@china.huawei.com> <AANLkTimB3-=zWGnT=uq9Qcb-N8Pq+-RR0WMN12BZ9pr4@mail.gmail.com>
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, 06 Oct 2010 21:57:59 -0000

Hi,
I think that David first question is important and here is my view

Roni Even

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

My view is that we are trying to address the transport of media in HTTP both
pre-recorded and live. The major issues I see are

1. Address the issue of allowing both push and pull models (addressing the
use cases and concerns from Qin draft) 
2. Address the startup issue, we have worked in AVT on fast channel/content
change and I think this is relevant also in this case.
3. Look at the scaling problem when there is no multicast or broadcast
support.

In general I think that by having a use cases document that covers the
scenarios that look important to the group we can achieve a better
understanding of what is the charter of the work. 


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