[opendtv] Re: Punching Above Its Weight, Upstart Netflix Pokes at HBO - NYTimes.com

  • From: "Manfredi, Albert E" <albert.e.manfredi@xxxxxxxxxx>
  • To: "opendtv@xxxxxxxxxxxxx" <opendtv@xxxxxxxxxxxxx>
  • Date: Sun, 23 Feb 2014 23:38:02 +0000

Jim Cole wrote:

> See the response to John's message and articles I posted therein. The
> need to move VOD to the IP side of the business because they do not
> have the bandwidth on the live video side, and they have enhanced
> capabilities when they move to IP. But remember, this stuff is still
> INSIDE their walled garden.

For a service like this hypothetical Netflix-to-in-home-TWC-STB, I would expect 
it would be entirely VOD regardless. The Netflix scheme doesn't include live 
streams, right? So they wouldn't be using the "live video" bandwidth, aka 
MPEG-2 TS broadcast streams, *unless* TWC only offers VOD by means of in-home 
PVRs. I doubt they do that.

So, whatever bandwidth TWC uses for their own existing VOD service is the same 
bandwidth a Netflix VOD service would use. I assume that even the legacy TWC 
VOD service is provided by servers at the edges of their walled garden network 
(don't know if it uses IP or other).

My colleague at work had Verizon FiOS installed some time ago. They have been 
using IP (unicast, obviously) for all of their VOD, from the start. It makes 
sense. Why reinvent the wheel?

Anyway, if TWC already uses IP for their VOD, as Verizon FiOS does, then it 
seems to me that the protocol and the "bandwidth" problems are already solved. 
VOD can't use MPEG-2 TS broadcast bandwidth unless the VOD is provided only by 
in-home PVRs.


You can UNSUBSCRIBE from the OpenDTV list in two ways:

- Using the UNSUBSCRIBE command in your user configuration settings at 

- By sending a message to: opendtv-request@xxxxxxxxxxxxx with the word 
unsubscribe in the subject line.

Other related posts: