nanog mailing list archives
Re: GeoIP database issues and the real world consequences
From: Jean-Francois Mezei <jfmezei_nanog () vaxination ca>
Date: Wed, 13 Apr 2016 11:42:36 -0400
On 2016-04-13 09:11, Valdis.Kletnieks () vt edu wrote:
On Tue, 12 Apr 2016 20:17:03 -0400, Jean-Francois Mezei said:All GeoIP services would be forced toHow?
Fair point. However, considering more and more outfits block content based on IP geolocation, once has to wonder if an outfit such as the FTC could mandate certain standards and disclosure of inaccuracy of IP geolocation. Or the other way around (shudded) mandate that outfits such as ARIN ensure IP blocks are accurately configured/registered to provide accurate geolocation within state/province for instance. By documenting that IP blocks only resolve to state/province, this would set the implicit standard that any IP geolocation service that claims more precise gelocation is bogus. And mandating IP blocks be limited to state/province would be a big enough headache-causing undertaking as large number of ISPs and organisations span this and want to have abilityto move blocks around to cope with demand increasing more in one state than the other etc. So that leaves ARIN mandating and documenting that IP blocks be accurately registered on a country basis within its territory. This would allow proper geolocation/blocking for outfits like Netflix but be documented as being unusable to track an IP down to state, city, street/home. When ARIN makes IP block database available for download, it should have an "agree" button to terms and conditions that would prevent the user of the data from claiming accuracy greater than "countrty". Just an idea.
Current thread:
- Re: GeoIP database issues and the real world consequences, (continued)
- 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)
- Re: GeoIP database issues and the real world consequences John Levine (Apr 12)
- Re: GeoIP database issues and the real world consequences Jeremy Austin (Apr 12)
- RE: GeoIP database issues and the real world consequences frnkblk (Apr 16)
- Re: GeoIP database issues and the real world consequences Owen DeLong (Apr 11)
- Re: GeoIP database issues and the real world consequences Owen DeLong (Apr 11)
- Re: GeoIP database issues and the real world consequences Niels Bakker (Apr 11)
- Re: GeoIP database issues and the real world consequences Owen DeLong (Apr 11)