[160731] in North American Network Operators' Group
Re: The 100 Gbit/s problem in your network
daemon@ATHENA.MIT.EDU (Owen DeLong)
Tue Feb 12 00:09:56 2013
From: Owen DeLong <owen@delong.com>
In-Reply-To: <CAB6yvaHBbKZbunLcR3tt8vPATO7_DRsYhGRuKp8QUeiUeGZXjA@mail.gmail.com>
Date: Mon, 11 Feb 2013 21:07:12 -0800
To: Ryan Malayter <malayter@gmail.com>
Cc: "nanog@nanog.org" <nanog@nanog.org>
Errors-To: nanog-bounces+nanog.discuss=bloom-picayune.mit.edu@nanog.org
That's not the general case, however. That's a set of specialized videos =
where
you know you will have a large number of consumers at each site viewing =
the
same video content.
Owen
On Feb 11, 2013, at 20:46 , Ryan Malayter <malayter@gmail.com> wrote:
> You're missing the entire point: all web caches *already* work with
> DASH and the proprietary HTTP chunking flavors. It's just HTTP =
request/response
> data.
>=20
> My employer's statistics show this to be true; we do video for
> compliance training
> and we see massive benefit from local caches in our customer's
> networks. We send a cache-enabled customer site each video chunk just
> about once on average, and their cache takes care of distribution to
> up to thousands of internal viewers.
>=20
> HTTP chunk streaming works today with Silverlight/Flash/Quicktime
> plugins, and there is a working prototype of the standardized DASH
> that use only an modern web browser and JavaScript with no plug-ins:
> http://dash-mse-test.appspot.com/dash-player.html
