Re: [httpstreaming] Current Status and Our Goal

Qin Wu <sunseawq@huawei.com> Fri, 08 October 2010 08:15 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 4B9B83A6855 for <httpstreaming@core3.amsl.com>; Fri, 8 Oct 2010 01:15:36 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.089
X-Spam-Level:
X-Spam-Status: No, score=0.089 tagged_above=-999 required=5 tests=[AWL=0.584, BAYES_00=-2.599, FH_RELAY_NODNS=1.451, HELO_MISMATCH_COM=0.553, 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 G+99WjqKapdG for <httpstreaming@core3.amsl.com>; Fri, 8 Oct 2010 01:15:34 -0700 (PDT)
Received: from szxga03-in.huawei.com (unknown [119.145.14.66]) by core3.amsl.com (Postfix) with ESMTP id E1EDD3A6853 for <httpstreaming@ietf.org>; Fri, 8 Oct 2010 01:15:33 -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 <0L9Y00F1FPNFVW@szxga03-in.huawei.com> for httpstreaming@ietf.org; Fri, 08 Oct 2010 16:16:27 +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 <0L9Y00FUBPNFZD@szxga03-in.huawei.com> for httpstreaming@ietf.org; Fri, 08 Oct 2010 16:16:27 +0800 (CST)
Received: from w53375 ([10.138.84.79]) by szxml04-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 2.14 (built Aug 8 2006)) with ESMTPA id <0L9Y00A41PNE1G@szxml04-in.huawei.com> for httpstreaming@ietf.org; Fri, 08 Oct 2010 16:16:27 +0800 (CST)
Date: Fri, 08 Oct 2010 16:16:25 +0800
From: Qin Wu <sunseawq@huawei.com>
To: "Ali C. Begen (abegen)" <abegen@cisco.com>, Roni Even <Even.roni@huawei.com>, "David A. Bryan" <dbryan@ethernot.org>
Message-id: <074201cb66c1$1a192d50$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: text/plain; charset="windows-1252"
Content-transfer-encoding: 7bit
X-Priority: 3
X-MSMail-priority: Normal
References: <00df01cb5de2$2ac49730$4f548a0a@china.huawei.com> <AANLkTimB3-=zWGnT=uq9Qcb-N8Pq+-RR0WMN12BZ9pr4@mail.gmail.com> <03f501cb65a1$50699d70$f13cd850$%roni@huawei.com> <04CAD96D4C5A3D48B1919248A8FE0D540D5BEADB@xmb-sjc-215.amer.cisco.com> <03f901cb65a5$7ee4bc80$7cae3580$%roni@huawei.com> <04CAD96D4C5A3D48B1919248A8FE0D540D5BEB08@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: Fri, 08 Oct 2010 08:15:36 -0000

> also a need for video synchronization to start rendering.

Synchronization among the viewers you mean? That could be a concern but seriously, since client implementations will differ, network capacities will differ, i.e., pretty much everything will differ for different clients, I don't think there is a solution to this. Better said, I don't think there is a problem.

[Qin] I think Synchronization between the server and the client is one issue we may look at. Since the server has buffer for encoding, the client has a buffer for playout, we definitely need one streaming media synchronization mechanism which may help reduce delay.

> For pre-recorded video this may be due to distance between synchronization
> points and the size of a chunk sent.

Those things are all implementation specific IMO, they are not protocol issues.

[Qin] I think two synchronizaton points are refering to the server and client rather than two clients as viewers.

-acbegen

> Roni Even
> 
> > -----Original Message-----
> > From: Ali C. Begen (abegen) [mailto:abegen@cisco.com]
> > Sent: Thursday, October 07, 2010 12:15 AM
> > To: Roni Even; David A. Bryan; Qin Wu
> > Cc: httpstreaming@ietf.org
> > Subject: RE: [httpstreaming] Current Status and Our Goal
> >
> > > 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.
> >
> > Are you assuming a multicast environment for http streaming? Ow, the
> > startup issue is not an issue in unicast connections.
> >
> > -acbegen