[187149] in North American Network Operators' Group
Re: IPv6 traffic percentages?
daemon@ATHENA.MIT.EDU (Job Snijders)
Thu Jan 21 08:56:54 2016
X-Original-To: nanog@nanog.org
Date: Thu, 21 Jan 2016 14:56:46 +0100
From: Job Snijders <job@instituut.net>
To: Randy Bush <randy@psg.com>
In-Reply-To: <m2lh7jwyek.wl%randy@psg.com>
Cc: North American Network Operators' Group <nanog@nanog.org>
Errors-To: nanog-bounces@nanog.org
On Thu, Jan 21, 2016 at 09:48:19AM +0900, Randy Bush wrote:
> > jokes aside, Its a hypothesis worth testing. It has qualities which
> > make it plausible.
> >
> > So please, between you, find a way to specify and test it!
>
> although the hypothesis has some intuitive appeal, how to test it is far
> from obvious. and i note that, as a senior member of the measurement
> community, you're saying "you guys do it." thanks a lot. :)
>
> i considered rtt from a service such as goog to their querriers. there
> are the problems of their distributed caches, the politics of getting
> their data, and the eyeball bias. maybe find a platform with less of
> those biases. dns is far too biased in all sorts of dimensions. your
> add clicks? i have found no usable coffee here in nagoya, so i may be
> missing something obvious.
Looking at my employers network...
We know the GPS coordinates for each BGP next-hop in the network, and
traffic is sampled on ingress at the edge of the network and reported to
pmacct (*flow), which also receives a RR-style BGP feed for correlation.
We can know where (geographically) a packet enters the network, where it
leaves the network and to what address family it belongs.
However, this would be just one network's (biased) view on things.
