[188693] in North American Network Operators' Group

home help back first fref pref prev next nref lref last post

Re: GeoIP database issues and the real world consequences

daemon@ATHENA.MIT.EDU (Larry Sheldon)
Tue Apr 12 18:41:48 2016

X-Original-To: nanog@nanog.org
To: nanog@nanog.org
From: Larry Sheldon <larrysheldon@cox.net>
Date: Tue, 12 Apr 2016 17:41:39 -0500
In-Reply-To: <20160412133147.GA90286@ussenterprise.ufp.org>
Errors-To: nanog-bounces@nanog.org

On 4/12/2016 08:31, Leo Bicknell wrote:
> In a message written on Mon, Apr 11, 2016 at 03:10:44PM -0400, Sean Donelan wrote:
>> If GeoIP insists on giving a specific lon/lat, instead of an uncertaintity
>> how about using locations such as the followign as the "default I don't
>> know where it is"
>>
>> United States: 38.8899 N, 77.0091 W (U.S. Capital Building)
>> Missouri: 38.5792 N, 92.1729 W (Missouri State Capital Building)
>>
>> After the legislators get tired of the police raiding the capital
>> buildings, they will probably do something to fix it.
>
> Massachusetts: 42.376702 N, 71.239076 W (MaxMind Corporate HQ)
>
> Maybe after seeing what it's like to be on the receiving end of their
> own inaccuracy they will be a bit more motivated to fix it.


BINGO!!!
-- 
sed quis custodiet ipsos custodes? (Juvenal)

home help back first fref pref prev next nref lref last post