Re: [httpstreaming] Current Status and Our Goal

Ye-Kui Wang <yekuiwang@huawei.com> Sat, 09 October 2010 23:27 UTC

Return-Path: <yekuiwang@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 D5B4E3A6941 for <httpstreaming@core3.amsl.com>; Sat, 9 Oct 2010 16:27:26 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level:
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599]
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 xTjccXP7u0pg for <httpstreaming@core3.amsl.com>; Sat, 9 Oct 2010 16:27:25 -0700 (PDT)
Received: from usaga03-in.huawei.com (usaga03-in.huawei.com [206.16.17.220]) by core3.amsl.com (Postfix) with ESMTP id D49C53A693E for <httpstreaming@ietf.org>; Sat, 9 Oct 2010 16:27:25 -0700 (PDT)
Received: from huawei.com (usaga03-in [172.18.4.17]) by usaga03-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 2.14 (built Aug 8 2006)) with ESMTP id <0LA10078XQJLS0@usaga03-in.huawei.com> for httpstreaming@ietf.org; Sat, 09 Oct 2010 18:28:33 -0500 (CDT)
Received: from W90946 ([58.249.80.208]) by usaga03-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 2.14 (built Aug 8 2006)) with ESMTPA id <0LA100HDUQJ9N1@usaga03-in.huawei.com> for httpstreaming@ietf.org; Sat, 09 Oct 2010 18:28:33 -0500 (CDT)
Date: Sat, 09 Oct 2010 19:28:10 -0400
From: Ye-Kui Wang <yekuiwang@huawei.com>
In-reply-to: <04CAD96D4C5A3D48B1919248A8FE0D540D5BF35F@xmb-sjc-215.amer.cisco.com>
To: "'Ali C. Begen (abegen)'" <abegen@cisco.com>, 'Lars Eggert' <lars.eggert@nokia.com>, 'Colin Perkins' <csp@csperkins.org>
Message-id: <93771AF96E344580A0ECCCFB32324E5D@china.huawei.com>
MIME-version: 1.0
X-MIMEOLE: Produced By Microsoft MimeOLE V6.00.2900.5579
X-Mailer: Microsoft Office Outlook 11
Content-type: text/plain; charset=us-ascii
Content-transfer-encoding: 7BIT
Thread-index: ActmwTgan48Na+ciRYiI95TewO+0dQBD5E6QAA4gzzA=
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>
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: Sat, 09 Oct 2010 23:27:26 -0000

> I imagine the only work the IETF should do (if we decide to) 
> is the transport and HTTP-layer optimization for better 
> streaming performance.

I second, as one who has been heavily involved HTTP streaming
standardization in 3GPP, MPEG and OIPF.

BR, YK 

> -----Original Message-----
> From: httpstreaming-bounces@ietf.org 
> [mailto:httpstreaming-bounces@ietf.org] On Behalf Of Ali C. 
> Begen (abegen)
> Sent: Saturday, October 09, 2010 12:44 PM
> To: Lars Eggert; Colin Perkins
> Cc: httpstreaming@ietf.org
> Subject: Re: [httpstreaming] Current Status and Our Goal
> 
> 
> 
> > -----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.
> 
> -acbegen
>  
> > Lars
> _______________________________________________
> httpstreaming mailing list
> httpstreaming@ietf.org
> https://www.ietf.org/mailman/listinfo/httpstreaming
>