[172973] in North American Network Operators' Group

home help back first fref pref prev next nref lref last post

Re: Verizon Public Policy on Netflix

daemon@ATHENA.MIT.EDU (Jared Mauch)
Mon Jul 14 09:03:14 2014

X-Original-To: nanog@nanog.org
From: Jared Mauch <jared@puck.nether.net>
In-Reply-To: <CACQ0XpJ+1EyToycpqXD3YL7OxjMsAe5NX8Jq1ubWvHQD8w+qGg@mail.gmail.com>
Date: Mon, 14 Jul 2014 09:03:39 -0400
To: Daniel Ankers <md1clv@md1clv.com>
Cc: "nanog@nanog.org" <nanog@nanog.org>
Errors-To: nanog-bounces@nanog.org


On Jul 14, 2014, at 8:58 AM, Daniel Ankers <md1clv@md1clv.com> wrote:

> On 14 July 2014 13:44, Dave Temkin <dave@temk.in> wrote:
>=20
>> With multiple different encodes (driven by
>> differing DRM and device types) the odds of two people watching the =
exact
>> same thing are relatively low. The law of large numbers rules the =
game.
>>=20
>> -Dave
>=20
>=20
> What are the chances of performing transcoding on the device rather =
than
> sending multiple copies to it?
>=20
> It seems that would save bandwidth without risking any licensing =
issues.

In my experience the bandwidth is typically the lowest part of the cost =
equation.

Why transcode on 1k nodes when you can do it once and distribute it at =
lower cost,
including in electricity to run the host CPU.

Centralized transcoding on dedicated hardware makes sense.

- Jared=

home help back first fref pref prev next nref lref last post