[181597] in North American Network Operators' Group
Re: CDNs for carriers
daemon@ATHENA.MIT.EDU (Mike Hammett)
Mon Jun 29 09:59:30 2015
X-Original-To: nanog@nanog.org
Date: Mon, 29 Jun 2015 08:59:22 -0500 (CDT)
From: Mike Hammett <nanog@ics-il.net>
To: nanog list <nanog@nanog.org>
In-Reply-To: <7A5E6370-9856-422F-90B9-7AAF9D35628B@puck.nether.net>
Errors-To: nanog-bounces@nanog.org
Simple flows wouldn't necessarily tell you if you're pulling a bunch from a=
Netflix caching box on your upstream somewhere. You'd think you had a huge=
amount going to your current upstream because technically you do, but a lo=
cal cache or peer could alter that significantly. As we've been starting up=
our IX, we're finding that we can send lists of ASNs and prefixes and the =
various CDNs will tell us how much traffic they see going to our customers.=
Combine that with what flows tell you and I think you've got a good approa=
ch.=20
What are some good approaches to determining traffic levels to not only ASN=
s, but also that ASN's downstream ASNs? You may have ASNs A, B, C, D and E =
in your flows. Say none of them represent more than 5% of your traffic by t=
hemselves. If B, C, D and E all purchase transit from A and you can reasona=
bly peer with A, you actually can move 25% of your traffic over to a peer. =
Maybe there is no good approach at doing that without a bunch of manual wor=
k or paying someone else to do it.=20
Looking at some stats from one of our customers that is also going through =
Equinix Chicago, for their average inbound ~37% of traffic was Netflix, Goo=
gle was 34% and the next highest was Apple at 5%. Note that Akamai had left=
Chicago Equinix by this point, so they wouldn't be reflected in those numb=
ers. Those percentages are percent of all traffic they send to Equinix. I b=
elieve about 2/3s of their total transit went to Equinix when that got turn=
ed up. Their total traffic went up once joining the Equinix IX, presumably =
because they were now bypassing some congestion somewhere.=20
-----=20
Mike Hammett=20
Intelligent Computing Solutions=20
http://www.ics-il.com=20
Midwest Internet Exchange=20
http://www.midwest-ix.com=20
----- Original Message -----
From: "Jared Mauch" <jared@puck.nether.net>=20
To: "Christopher Morrow" <morrowc.lists@gmail.com>=20
Cc: "nanog list" <nanog@nanog.org>, "Ramy Hashish" <ramy.ihashish@gmail.com=
>=20
Sent: Monday, June 29, 2015 8:44:18 AM=20
Subject: Re: CDNs for carriers=20
> On Jun 29, 2015, at 9:33 AM, Christopher Morrow <morrowc.lists@gmail.com>=
wrote:=20
>=20
> On Mon, Jun 29, 2015 at 8:53 AM, Ramy Hashish <ramy.ihashish@gmail.com> w=
rote:=20
>> do you have any figures about how much this=20
>> recommended CDN save from the Internet BW?=20
>=20
> isn't that going to wholey depend on your traffic mix/matrix?=20
> Wouldn't it be helpful to look at where your users send/receive=20
> traffic and then figure out the best next addition?=20
>=20
> Maybe your best bet isn't another CDN, but better/more/wider peering=20
> with folk 2+ AS hops out from your current next-hop-as set?=20
I would say that step 1 is to figure out where your traffic is going. Gener=
ically saying =E2=80=9CCDN=E2=80=9D isn=E2=80=99t enough to know what the r=
esults are.=20
Once you=E2=80=99ve determined where the traffic is going/coming from you c=
an start to make educated decisions vs just =E2=80=9CCDN=E2=80=9D guessing.=
An enterprise profile looks much different than residential for example.=
=20
I recall some companies calling our NOC =E2=80=9Cunder attack=E2=80=9D beca=
use their software update server went down and the machines failed safe and=
were all fetching software updates from =E2=80=9Cthe internet=E2=80=9D vs =
the internal caching proxy.=20
If you have money to spend, there are a few vendors out there from cheap to=
$$$$ that will help you look at the traffic to make these decisions.=20
If you don=E2=80=99t have money to spend, look at NFSen/pmacct. You may be =
able to spin up a low-cost VM at your local cloud provider (e.g.: digital o=
cean).=20
Remember to export both your v6 and v4 (ip classic) flows as these can wide=
ly differ.=20
Look for common ASNs or IP ranges.=20
I=E2=80=99m sure there=E2=80=99s numerous consultants on the list that woul=
d also assist you in this process.=20
Hope this helps.=20
- jared=20
