[181598] in North American Network Operators' Group
Re: CDNs for carriers
daemon@ATHENA.MIT.EDU (Christopher Morrow)
Mon Jun 29 10:16:04 2015
X-Original-To: nanog@nanog.org
In-Reply-To: <1045686261.870.1435586395880.JavaMail.mhammett@ThunderFuck>
Date: Mon, 29 Jun 2015 10:16:01 -0400
From: Christopher Morrow <morrowc.lists@gmail.com>
To: Mike Hammett <nanog@ics-il.net>
Cc: nanog list <nanog@nanog.org>
Errors-To: nanog-bounces@nanog.org
On Mon, Jun 29, 2015 at 9:59 AM, Mike Hammett <nanog@ics-il.net> wrote:
> 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 hu=
ge amount going to your current upstream because technically you do, but a =
local cache or peer could alter that significantly.
probably dns and flow gets you some more traction, right?
meaning: "gosh 1.2.3.0/26 is sending us LOTS of traffic... oh:
nslookup 1.2.3.4 =3D=3D hosta.networkb.netflix.com, ah-ha!"
where ptr records are generated I suppose like:
$ host 63.88.73.108
108.73.88.63.in-addr.arpa domain name pointer
108.73.88.63.ashburn.google-ggc.verizon.com.
Also, often just port/protocol are helpful enough... you won't know
without looking (at the OP's traffic I mean), which it sounds like
hasn't really been done yet?
