Re: [httpstreaming] Current Status and Our Goal

Kathy McEwen <kathy@iridescentnetworks.com> Wed, 06 October 2010 22:47 UTC

Return-Path: <kathy@iridescentnetworks.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 946913A6F50 for <httpstreaming@core3.amsl.com>; Wed, 6 Oct 2010 15:47:28 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.203
X-Spam-Level:
X-Spam-Status: No, score=-1.203 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, MIME_QP_LONG_LINE=1.396]
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 BcGixg8RFJYc for <httpstreaming@core3.amsl.com>; Wed, 6 Oct 2010 15:47:27 -0700 (PDT)
Received: from smtp104-mob.biz.mail.gq1.yahoo.com (smtp104-mob.biz.mail.gq1.yahoo.com [98.136.185.195]) by core3.amsl.com (Postfix) with SMTP id AD9903A6D8A for <httpstreaming@ietf.org>; Wed, 6 Oct 2010 15:47:27 -0700 (PDT)
Received: (qmail 89674 invoked from network); 6 Oct 2010 22:48:28 -0000
Received: from [10.77.158.135] (kathy@166.205.137.87 with xymcookie) by smtp104-mob.biz.mail.gq1.yahoo.com with SMTP; 06 Oct 2010 15:48:27 -0700 PDT
X-Yahoo-SMTP: 0oTc.aiswBATml9UvnuZnOzzTXTzZTa6NV7Bbr9Wm3OL
X-YMail-OSG: 4vpxCT0VM1nK_mdkdfYveJPMTKiR49nGvGuu0Y42hlnePBH iAgKBk3YUh489F1Sv8Fvbw8NoqB1Me05oFKNs1AWMn8mhL.JcpS.v4CyN1ES hgkNbEax3QuU4_xb9nfJ1u41TunEluirgyrWKu.fkEqa3mtFAYaQlDFJdF_N 48hlspya7cJYvGLf9pjqEoPfMGJJiFiztS2LGzvJWOFSdE5dCmmPiOpI049q dhXvsQFezkS_YQwvNNqOU_hsAyqayNruCGP1rzuPllIFYgtRDD9ouz9U.J1Q B..mmJ2HoyVMVUg33CMiAd3WXy2oS3MMdeNOni7BRMISBpZLSMSg0krcRzA- -
X-Yahoo-Newman-Property: ymail-3
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>
Mime-Version: 1.0 (iPhone Mail 8B117)
In-Reply-To: <04CAD96D4C5A3D48B1919248A8FE0D540D5BEB08@xmb-sjc-215.amer.cisco.com>
X-Apple-Yahoo-Original-Message-Folder: Inbox
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Message-Id: <21A8E503-D640-4947-BFF1-EE5A5D3643E9@iridescentnetworks.com>
X-Mailer: iPhone Mail (8B117)
From: Kathy McEwen <kathy@iridescentnetworks.com>
X-Apple-Yahoo-Replied-Msgid: 1_329534_ALjHjkQAANX0TKz66gClYz+sSTQ
Date: Wed, 06 Oct 2010 15:47:50 -0700
To: "Ali C. Begen (abegen)" <abegen@cisco.com>
Cc: "httpstreaming@ietf.org" <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 22:47:28 -0000

Content does not have to be pushed from broadcaster to a source server and then to a CDN to make it out to users devices.  We are working directly with very large national broadcasters in north america and Europe who want to push multicast broadcast real time event content on to the web directly from their sites to users much like they do with content pushed to cable and satellite distribution networks. 

.../Kathy 

Sent from my mobile

On Oct 6, 2010, at 3:40 PM, "Ali C. Begen (abegen)" <abegen@cisco.com> wrote:

> 
> 
>> -----Original Message-----
>> From: Roni Even [mailto:Even.roni@huawei.com]
>> Sent: Thursday, October 07, 2010 6:26 AM
>> To: Ali C. Begen (abegen); 'David A. Bryan'; 'Qin Wu'
>> Cc: httpstreaming@ietf.org
>> Subject: RE: [httpstreaming] Current Status and Our Goal
>> 
>> Ali,
>> It is not the same as multicast but is still a problem for live streaming
>> when buffering is used on the server that  may delay the data and there is
> 
> Sure, http streaming or streaming over another protocol will always be delayed. The content generation, pushing it to the source servers and CDN and then getting them to the clients plus the playout buffers will add up a delay of 20-30 seconds compared to regular over-the-air broadcast. 
> 
> I don't think there is much we can do about this, especially in the IETF.
> 
>> 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.
> 
>> 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.
> 
> -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
> 
> _______________________________________________
> httpstreaming mailing list
> httpstreaming@ietf.org
> https://www.ietf.org/mailman/listinfo/httpstreaming