[155494] in North American Network Operators' Group
Re: IPV6 Anycast for streaming
daemon@ATHENA.MIT.EDU (Jared Mauch)
Mon Aug 13 08:18:27 2012
From: Jared Mauch <jared@puck.nether.net>
In-Reply-To: <BDEA9DA2-2C62-421D-A740-6FDF97283ABC@gmail.com>
Date: Mon, 13 Aug 2012 08:17:40 -0400
To: Ryan Malayter <malayter@gmail.com>
Cc: nanog@nanog.org
Errors-To: nanog-bounces+nanog.discuss=bloom-picayune.mit.edu@nanog.org
On Aug 12, 2012, at 3:15 PM, Ryan Malayter wrote:
> I would recommend looking at CDNs however, as=20
> this is an area where scale does matter and you=20
> will find it very difficult to do this better or cheaper=20
> yourself.
<personal hat on>
I certainly see this as a challenge to compete with the breadth of the =
existing CDN networks. Many cases it is just easier to outsource this =
function and capability. I've found myself starting to lean in the =
direction of minimizing the problems that I need to debug/solve. This =
usually results in a lower cost and more free time to deal with whatever =
else it is.
Building your Anycast/Mini-CDN infrastructure yourself is going to make =
it so you need to re-learn lessons that others have already learned. =
Even if you were formerly at a CDN, I'm sure there is some black magic =
you were unaware of.
It sounds like you have a few servers and are just trying to do IPv6 "on =
the cheap" or similar to HE. It may be worthwhile to avoid the tunneled =
infrastructure to yourself and use a carrier that has native. There are =
numerous carriers with a global footprint that can do this for you.
<personal hat off>
I would be cautious about the complexity and your overall requirements =
of performing a solution like this. Anycast is just a name for a =
technique, there is more to it than that to implement it. (In the same =
way internal combustion engines have various levels of complexity - =
diesel, gasoline, E85, injectors, etc).
- Jared=
