Re: [multrans] [MBONED] Carriers' IPTV uses multicast vs unicast, OTT/HTTP

Susan Hares <susan.hares@huawei.com> Thu, 22 December 2011 23:24 UTC

Return-Path: <susan.hares@huawei.com>
X-Original-To: multrans@ietfa.amsl.com
Delivered-To: multrans@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 4530E21F84B8; Thu, 22 Dec 2011 15:24:33 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.549
X-Spam-Level:
X-Spam-Status: No, score=-2.549 tagged_above=-999 required=5 tests=[AWL=0.050, BAYES_00=-2.599]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id UvfJGin62OtK; Thu, 22 Dec 2011 15:24:32 -0800 (PST)
Received: from dfwrgout.huawei.com (dfwrgout.huawei.com [206.16.17.72]) by ietfa.amsl.com (Postfix) with ESMTP id 5D4B021F84B4; Thu, 22 Dec 2011 15:24:32 -0800 (PST)
Received: from 172.18.9.243 (EHLO dfweml202-edg.china.huawei.com) ([172.18.9.243]) by dfwrg02-dlp.huawei.com (MOS 4.2.3-GA FastPath) with ESMTP id ABT64694; Thu, 22 Dec 2011 18:24:32 -0500 (EST)
Received: from DFWEML403-HUB.china.huawei.com (10.193.5.151) by dfweml202-edg.china.huawei.com (172.18.9.108) with Microsoft SMTP Server (TLS) id 14.1.323.3; Thu, 22 Dec 2011 15:23:03 -0800
Received: from DFWEML504-MBX.china.huawei.com ([10.124.31.30]) by dfweml403-hub.china.huawei.com ([10.193.5.151]) with mapi id 14.01.0270.001; Thu, 22 Dec 2011 15:22:52 -0800
From: Susan Hares <susan.hares@huawei.com>
To: "Lee, Yiu" <Yiu_Lee@Cable.Comcast.com>, Tina TSOU <Tina.Tsou.Zouting@huawei.com>, "mboned@ietf.org" <mboned@ietf.org>, "multrans@ietf.org" <multrans@ietf.org>
Thread-Topic: [MBONED] Carriers' IPTV uses multicast vs unicast, OTT/HTTP
Thread-Index: AQHMwQBdmoLJV3pISzqQ/pwXEhM9kZXofuoA
Date: Thu, 22 Dec 2011 23:22:52 +0000
Message-ID: <728F9B956B2C48439CA9294B1723B14616C1D32F@dfweml504-mbx>
References: <728F9B956B2C48439CA9294B1723B14616C1D308@dfweml504-mbx> <CB192503.1A2A9%yiu_lee@cable.comcast.com>
In-Reply-To: <CB192503.1A2A9%yiu_lee@cable.comcast.com>
Accept-Language: zh-CN, en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [10.47.145.112]
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-CFilter-Loop: Reflected
X-Mailman-Approved-At: Fri, 23 Dec 2011 13:53:48 -0800
Subject: Re: [multrans] [MBONED] Carriers' IPTV uses multicast vs unicast, OTT/HTTP
X-BeenThere: multrans@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "Discuss the work of IPv4-IPv6 multicast." <multrans.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/multrans>, <mailto:multrans-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/multrans>
List-Post: <mailto:multrans@ietf.org>
List-Help: <mailto:multrans-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/multrans>, <mailto:multrans-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 22 Dec 2011 23:24:33 -0000

Yiu:

My understanding is that the buffering of the live event is at the source - just like a video would be recorded. The actual deliver uses the multicast infrastructure to be efficient. 

Am I clearer this time?  Maybe I need to drink more coffee.

Cheers,

Sue  

-----Original Message-----
From: Lee, Yiu [mailto:Yiu_Lee@Cable.Comcast.com] 
Sent: Thursday, December 22, 2011 6:21 PM
To: Susan Hares; Tina TSOU; mboned@ietf.org; multrans@ietf.org
Subject: Re: [MBONED] Carriers' IPTV uses multicast vs unicast, OTT/HTTP

AFAIK, the major push to use multicast is to preserve bandwidth. I don't see how buffering would make multicast even more favorable. If so, I would like to know why.


On 12/22/11 6:16 PM, "Susan Hares" <susan.hares@huawei.com> wrote:

> Yiu:
>
>Wow! Thanks for the quick response. I was a bit unclear.
>
>My understanding is that the buffering actually pushes things toward 
>the multicast model.
>
>Sue
>
>-----Original Message-----
>From: Lee, Yiu [mailto:Yiu_Lee@Cable.Comcast.com]
>Sent: Thursday, December 22, 2011 6:12 PM
>To: Susan Hares; Tina TSOU; mboned@ietf.org; multrans@ietf.org
>Subject: Re: [MBONED] Carriers' IPTV uses multicast vs unicast, 
>OTT/HTTP
>
>Hi Sue,
>
>I think it really depends whom you speak to. Buffering can be done in 
>different places (e.g., broadcast stations put 5 sec delay in their 
>live streams). This requirement alone won't require unicast streaming.
>
>Cheers,
>Yiu
>
>
>On 12/22/11 6:07 PM, "Susan Hares" <susan.hares@huawei.com> wrote:
>
>> Yiu Lee:
>>
>>Many people who I asked about live feeds, said the live feeds were 
>>often shifted 5-20 minutes and then done as normal video streaming.
>>
>>Is this true? 
>>
>>Thanks, and If I don't hear from you.. Merry Christmas,
>>
>>Sue
>>
>>-----Original Message-----
>>From: Tina TSOU
>>Sent: Thursday, December 22, 2011 6:05 PM
>>To: Lee, Yiu; mboned@ietf.org; multrans@ietf.org
>>Subject: RE: [MBONED] Carriers' IPTV uses multicast vs unicast, 
>>OTT/HTTP
>>
>>Yiu,
>>You address my puzzle. Thanks and Merry X'mas!
>>
>>
>>Best Regards,
>>Tina TSOU
>>http://tinatsou.weebly.com/contact.html
>>
>>
>>-----Original Message-----
>>From: Lee, Yiu [mailto:Yiu_Lee@Cable.Comcast.com]
>>Sent: Thursday, December 22, 2011 2:50 PM
>>To: Tina TSOU; mboned@ietf.org; multrans@ietf.org
>>Subject: Re: [MBONED] Carriers' IPTV uses multicast vs unicast, 
>>OTT/HTTP
>>
>>For OTT providers, unicast is the current option to deliver live 
>>content because inter-domain multicast is uncommon. Speaking of trend, 
>>using unicast for broadcasting is inefficient IMHO, so I don't see why 
>>using http to deliver live content is the trend.
>>
>>My 2 cents.
>>
>>
>>On 12/22/11 2:52 AM, "Tina TSOU" <Tina.Tsou.Zouting@huawei.com> wrote:
>>
>>>Hi,
>>>Someone mentioned that it seems the trend that carriers' IPTV uses 
>>>unicast, OTT/HTTP, rather than multicast.
>>>Thoughts?
>>>
>>>Sent from my iPad
>>>_______________________________________________
>>>MBONED mailing list
>>>MBONED@ietf.org
>>>https://www.ietf.org/mailman/listinfo/mboned
>>
>