nanog mailing list archives
Re: GeoIP database issues and the real world consequences
From: Christian de Larrinaga <cdel () firsthand net>
Date: Wed, 13 Apr 2016 10:50:38 +0100
Really? - You want RIRs to now perpetuate an application of IPs they are not designed for? The activities of MaxMind and similar need to be exposed so people understand the problem. No matter how Geo IP businesses might back peddle and say they never intended their services to be considered as authoritative etc the fact is people including law enforcement and presumably General Hayden and friends are buying into the fallacy that IP addresses are fit for the purpose of geo location. Let's put this another way. How many LIRs accounting systems use IPs as billing / account identifiers? No? I wonder why not..... C Todd Crane <mailto:todd.crane () n5tech com>
13 April 2016 at 06:57 I like (sarcasm) how everybody here either wants to point fingers at MaxMind or offer up coordinates to random places knowing that it will never happen. What ever happened to holding people responsible for being stupid. When did it start becoming ((fill in the blank)) coffee shop’s for you burning your tongue on your coffee, etc. I’ve seen/used all sorts of geolocation solutions and never once thought to myself that when a map pin was in the middle of a political boundary, that the software was telling me anything other than the place was somewhere within the boundary. Furthermore, most geolocation services will also show a zoomed-out/in map based on certainty. So if you can see more than a few hundred miles in the map that only measures 200x200 pixels, then it probably isn’t that accurate. As to a solution, why don’t we just register the locations (more or less) with ARIN? Hell, with the amount of money we all pay them in annual fees, I can’t imagine it would be too hard for them to maintain. They could offer it as part of their public whois service or even just make raw data files public. Just a though —Todd Jean-Francois Mezei <mailto:jfmezei_nanog () vaxination ca> 13 April 2016 at 01:17 All GeoIP services would be forced to document their default lat/long values so that users know that when these values, they know it is a generic one for that country. (or supply +181.0000 +91.00000 which is an invalid value indicating that there is no lat/long, look at country code given).
-- Christian de Larrinaga FBCS, CITP, ------------------------- @ FirstHand ------------------------- +44 7989 386778 cdel () firsthand net -------------------------
Current thread:
- Re: GeoIP database issues and the real world consequences, (continued)
- Re: GeoIP database issues and the real world consequences Steve Atkins (Apr 11)
- Re: GeoIP database issues and the real world consequences John Levine (Apr 11)
- Re: GeoIP database issues and the real world consequences Laszlo Hanyecz (Apr 11)
- Re: GeoIP database issues and the real world consequences Sean Donelan (Apr 11)
- Re: GeoIP database issues and the real world consequences Leo Bicknell (Apr 12)
- Re: GeoIP database issues and the real world consequences Larry Sheldon (Apr 12)
- Re: GeoIP database issues and the real world consequences Jean-Francois Mezei (Apr 12)
- Re: GeoIP database issues and the real world consequences Todd Crane (Apr 12)
- RE: GeoIP database issues and the real world consequences Nathan Anderson (Apr 13)
- RE: GeoIP database issues and the real world consequences Sven-Haegar Koch (Apr 13)
- Re: GeoIP database issues and the real world consequences Christian de Larrinaga (Apr 13)
- Re: GeoIP database issues and the real world consequences Laszlo Hanyecz (Apr 13)
- Re: GeoIP database issues and the real world consequences Valdis . Kletnieks (Apr 13)
- Re: GeoIP database issues and the real world consequences Todd Crane (Apr 14)
- Re: GeoIP database issues and the real world consequences Valdis . Kletnieks (Apr 15)
- Re: GeoIP database issues and the real world consequences Jay Hennigan (Apr 14)
- Re: GeoIP database issues and the real world consequences Valdis . Kletnieks (Apr 13)
- Re: GeoIP database issues and the real world consequences Jean-Francois Mezei (Apr 13)
- Re: GeoIP database issues and the real world consequences Baldur Norddahl (Apr 11)
- Re: GeoIP database issues and the real world consequences Niels Bakker (Apr 11)
- Re: GeoIP database issues and the real world consequences Valdis . Kletnieks (Apr 11)