[135559] in North American Network Operators' Group

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

Re: Ipv6 for the content provider

daemon@ATHENA.MIT.EDU (Owen DeLong)
Wed Jan 26 15:43:57 2011

From: Owen DeLong <owen@delong.com>
In-Reply-To: <5A6D953473350C4B9995546AFE9939EE0BC13624@RWC-EX1.corp.seven.com>
Date: Wed, 26 Jan 2011 12:40:49 -0800
To: "George Bonser" <gbonser@seven.com>
Cc: nanog@nanog.org
Errors-To: nanog-bounces+nanog.discuss=bloom-picayune.mit.edu@nanog.org


On Jan 26, 2011, at 11:22 AM, George Bonser wrote:

>> And if your servers behind the LB aren't prepared for it, you lose a
>> LOT
>> of logging data, geolocation capabilities, and some other things if
> you
>> go that route.
>> 
>> Owen
> 
> Relying on IP address for geolocation is actually quite ridiculous
> though I do realize that many people seem to believe that you can map an
> IP address to the physical location of the originator of the data, at
> least to the country level, but I suppose some people will sell you
> anything.
> 
> We haven't seen any problem with logging data so far in our testing.
> 

I don't disagree, but, since people like Wells Fargo are using it as a
security check (ask me about my experiences trying to log in from
Rwanda to check on a mortgage payment some time), things that
potentially make it even more broken than it is are worth pointing
out to administrators that may be stuck implementing IPv6 on sites
that may have such dependencies.

Owen



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