Re: Geolocation data management practices?

[Justin Krejci]

For corrections/updates, what I have found to be generally successful is


1. make sure to advertise the IP blocks into the DFZ from your ASN as soon as 
possible

2. make sure ARIN data is accurate (we use ARIN, you may use one of the other 
registries)

3. update my geofeed, as referenced already in this thread

4. directly contact organizations that have geolocation services but don't 
subscribe to my geofeed


If anyone has any additional geolocation organizations I didn't list, I would 
be happy to hear about them.



Geofeed subscriptions are in place with these organizations


IP Info
https://ipinfo.io/
https://ipinfo.io/faq/article/49-how-can-i-submit-a-correction
https://ipinfo.io/corrections

dbip
https://db-ip.com/
https://db-ip.com/contact/
support  db-ip.com

IPGeolocation
https://ipgeolocation.io/
support  ipgeolocation.io

Maxmind
https://www.maxmind.com/en/geoip-demo
https://support.maxmind.com/geoip-data-correction-request/

Neustar
https://www.home.neustar/resources/tools/ip-geolocation-lookup-tool
https://www.home.neustar/resources/tools/submit-to-global-ip-database
ipintel  support.neustar

BigDataCloud
https://www.bigdatacloud.com/ip-geolocation/

Digital Element
https://www.digitalelement.com/geolocation/
https://www.digitalelement.com/contact-us/
ip-data  digitalelement.com

ip2location
https://www.ip2location.com/demo
support  ip2location.com
Only accepts feeds when all entries have a city defined

Google
https://isp.google.com
Set geofeed URL within their ISP portal




No geofeed subscriptions in place for these organizations and require 
individual contact for corrections/updates


ipstack
https://ipstack.com/
https://ipstack.com/contact

Geo IP View
https://www.geoipview.com/
andrew  geoipview.com
email address is not currently receiving mail, as such I assume not many are 
using this service

IPligence
http://www.ipligence.com/geolocation
https://www.ipligence.com/contact

ipdata
https://ipdata.co/?ref=iplocation
https://ipdata.co/corrections.html
corrections  ipdata.co
working on adding geofeed support

IPIP
https://en.ipip.net/ip.html
sarah  ipip.net

IPHub
https://iphub.info/

IPinsight
https://ipinsight.io/
william  ipinsight.io

Info Sniper
https://infosniper.net/
https://infosniper.net/geoip-data-correction.php

GeoGuard
https://www.geocomply.com/products/geoguard/
ipintelligence  geoguard.com
More of a "are they using a VPN/hiding service" and not so much of a "Where are 
they" service.



From: NANOG  on behalf of Josh 
Luthman 
Sent: Thursday, April 21, 2022 9:24 AM
To: Rubens Kuhl
Cc: Nanog
Subject: Re: Geolocation data management practices?

Go through this list:
https://thebrotherswisp.com/index.php/geo-and-vpn/<https://url-shield.securence.com/?p=1.0=jkre...@usinternet.com=1650551121269-090-00144432=35m2jbep=bqbgig2zy=0.0,0.0,0.0,0.0=https%3A%2F%2Fthebrotherswisp.com%2Findex.php%2Fgeo-and-vpn%2F>

The RFC only works if they're pulling your feed and they'd only know that if 
you contact them in the first place.

On Thu, Apr 21, 2022 at 9:14 AM Rubens Kuhl < 
rube...@gmail.com<mailto:rube...@gmail.com>> wrote:
Besides geofeed, there are also geoidx records in IRRs but whether
geolocation services actually use geofeed or geoidx remains to be
seen. You can see some geoidx: at this IRR entry in TC:
https://bgp.net.br/whois/?q=-s%20TC%20-i%20mnt-by%20MAINT-AS271761<https://url-shield.securence.com/?p=1.0=jkre...@usinternet.com=1650551121269-090-00144432=mkamn44w=bqbgig2zz=0.0,0.0,0.0,0.0=https%3A%2F%2Fbgp.net.br%2Fwhois%2F%3Fq%3D-s%2520TC%2520-i%2520mnt-by%2520MAINT-AS271761>

Regarding LACNIC, what LACNIC, NIC.mx and NIC.br do is to select which
RIR or NIR services requests depending on the organisation's country.


Rubens

On Thu, Apr 21, 2022 at 9:53 AM Shawn < 
mailman.nanog@kleinart.net<mailto:mailman.nanog@kleinart.net>> wrote:
>
> Aloha NANOG,
>
> What is the best practice (or peoples preferred methods) to
> update/correct/maintain geolocation data?
> Do most people start with description field info in route/route6 objects?
>
>
> Also, thoughts and considerations on using IPv4 space from one RIR in
> countries belonging to another RIR?
>
> With IPv4 exhaustion and inter-RIR IPv4 transfers, and geolocation data, it
> seems less applicable than it had been (a decade ago).  The IP's will be
> used for CDN, not by end-users/subscribers.
> Context: trying to work through an administrative "challenge" with LACNIC
> regarding an IPv4 transfer, considering transferring to ARIN and then using
> in LACNIC (then once resolved, transfer from ARIN to LACNIC).  Or just using
> existing ARIN space in Brazil.
> LACNIC is making things more difficult than they need to be.  I know this is
> NANOG... but seeking advice, working on a global network, US HQ, currently
> no active "registration" in LACNIC (e

Re: Geolocation data management practices?

[Charles Polisher]

On 4/21/22 06:14, Rubens Kuhl wrote:

Besides geofeed, there are also geoidx records in IRRs but whether
geolocation services actually use geofeed or geoidx remains to be
seen. You can see some geoidx: at this IRR entry in TC:
https://bgp.net.br/whois/?q=-s%20TC%20-i%20mnt-by%20MAINT-AS271761

Regarding LACNIC, what LACNIC, NIC.mx and NIC.br do is to select which
RIR or NIR services requests depending on the organisation's country.


Also:

RFC 3693: Geopriv Requirements 



RFC 5870: A Uniform Resource Identifier for Geographic Locations ('geo' 
URI) 


RFC 6288: URN Namespace for the Defence Geospatial Information Working 
Group (DGIWG) 


RFC 6397: Multi-Threaded Routing Toolkit (MRT) BGP Routing Information 
Export Format with Geo-Location Extensions 



RFC 6772: Geolocation Policy: A Document Format for Expressing Privacy 
Preferences for Location Information 



RFC 7942: The GeoJSON Format 

RFC 8142: GeoJSON Text Sequences 



RFC 8805: A Format for Self-Published IP Geolocation Feeds 



RFC 9092: Finding and Using Geofeed Data 



--
Charles Polisher
(/Pedantic, I?/)

Re: Geolocation data management practices?

[Josh Luthman]

Go through this list:
https://thebrotherswisp.com/index.php/geo-and-vpn/

The RFC only works if they're pulling your feed and they'd only know that
if you contact them in the first place.

On Thu, Apr 21, 2022 at 9:14 AM Rubens Kuhl  wrote:

> Besides geofeed, there are also geoidx records in IRRs but whether
> geolocation services actually use geofeed or geoidx remains to be
> seen. You can see some geoidx: at this IRR entry in TC:
> https://bgp.net.br/whois/?q=-s%20TC%20-i%20mnt-by%20MAINT-AS271761
>
> Regarding LACNIC, what LACNIC, NIC.mx and NIC.br do is to select which
> RIR or NIR services requests depending on the organisation's country.
>
>
> Rubens
>
> On Thu, Apr 21, 2022 at 9:53 AM Shawn 
> wrote:
> >
> > Aloha NANOG,
> >
> > What is the best practice (or peoples preferred methods) to
> > update/correct/maintain geolocation data?
> > Do most people start with description field info in route/route6 objects?
> >
> >
> > Also, thoughts and considerations on using IPv4 space from one RIR in
> > countries belonging to another RIR?
> >
> > With IPv4 exhaustion and inter-RIR IPv4 transfers, and geolocation data,
> it
> > seems less applicable than it had been (a decade ago).  The IP's will be
> > used for CDN, not by end-users/subscribers.
> > Context: trying to work through an administrative "challenge" with LACNIC
> > regarding an IPv4 transfer, considering transferring to ARIN and then
> using
> > in LACNIC (then once resolved, transfer from ARIN to LACNIC).  Or just
> using
> > existing ARIN space in Brazil.
> > LACNIC is making things more difficult than they need to be.  I know
> this is
> > NANOG... but seeking advice, working on a global network, US HQ,
> currently
> > no active "registration" in LACNIC (except Brazil), but we operate in 5
> > countries in the region (data center/colo).  We would use Brazil, but
> very
> > hesitant to use their NIC (nic.br); LACNIC is saying we cannot maintain
> our
> > relationship with them using our Brazil organization (our only formal
> > subsidiary in the region).  LACNIC does not really define the "entity"
> > operating in their region well. We use our US entity with RIPE and APNIC,
> > simply showing documentation (contracts) that we operate in their region.
> > Maybe I am not using the magic word?
> >
> >
>

Re: Geolocation data management practices?

[Rubens Kuhl]

Besides geofeed, there are also geoidx records in IRRs but whether
geolocation services actually use geofeed or geoidx remains to be
seen. You can see some geoidx: at this IRR entry in TC:
https://bgp.net.br/whois/?q=-s%20TC%20-i%20mnt-by%20MAINT-AS271761

Regarding LACNIC, what LACNIC, NIC.mx and NIC.br do is to select which
RIR or NIR services requests depending on the organisation's country.


Rubens

On Thu, Apr 21, 2022 at 9:53 AM Shawn  wrote:
>
> Aloha NANOG,
>
> What is the best practice (or peoples preferred methods) to
> update/correct/maintain geolocation data?
> Do most people start with description field info in route/route6 objects?
>
>
> Also, thoughts and considerations on using IPv4 space from one RIR in
> countries belonging to another RIR?
>
> With IPv4 exhaustion and inter-RIR IPv4 transfers, and geolocation data, it
> seems less applicable than it had been (a decade ago).  The IP's will be
> used for CDN, not by end-users/subscribers.
> Context: trying to work through an administrative "challenge" with LACNIC
> regarding an IPv4 transfer, considering transferring to ARIN and then using
> in LACNIC (then once resolved, transfer from ARIN to LACNIC).  Or just using
> existing ARIN space in Brazil.
> LACNIC is making things more difficult than they need to be.  I know this is
> NANOG... but seeking advice, working on a global network, US HQ, currently
> no active "registration" in LACNIC (except Brazil), but we operate in 5
> countries in the region (data center/colo).  We would use Brazil, but very
> hesitant to use their NIC (nic.br); LACNIC is saying we cannot maintain our
> relationship with them using our Brazil organization (our only formal
> subsidiary in the region).  LACNIC does not really define the "entity"
> operating in their region well. We use our US entity with RIPE and APNIC,
> simply showing documentation (contracts) that we operate in their region.
> Maybe I am not using the magic word?
>
>

Re: Geolocation data management practices?

[Job Snijders via NANOG]

Hi Shawn,

On Wed, Apr 20, 2022 at 01:14:29PM -1000, Shawn wrote:
> What is the best practice (or peoples preferred methods) to
> update/correct/maintain geolocation data?
> Do most people start with description field info in route/route6 objects?
>
> [snip]
> 
> Maybe I am not using the magic word?

The magic word is "geofeed"! :-)

The format is specified in RFC 8805. Finding and using Geofeed data is
described in RFC 9092.

Example in the wild:

$ whois -h whois.ripe.net 146.75.0.0 | fgrep geofeed:
geofeed:https://ip-geolocation.fastly.com/

Another example below, in this instance the geofeed information is
stored in a 'remarks:' attribute. Unfortunately this particular RIR does
not (yet?) properly support the native RPSL geofeed attribute for IPv6
/48 PI blocks.

$ whois -h whois.ripe.net 2001:67c:208c::/48 | grep geofeed
remarks:Geofeed https://sobornost.net/geofeed.csv

Both approaches work.

Kind regards,

Job

Geolocation data management practices?

[Shawn]

Aloha NANOG,

What is the best practice (or peoples preferred methods) to
update/correct/maintain geolocation data?
Do most people start with description field info in route/route6 objects?


Also, thoughts and considerations on using IPv4 space from one RIR in
countries belonging to another RIR?

With IPv4 exhaustion and inter-RIR IPv4 transfers, and geolocation data, it
seems less applicable than it had been (a decade ago).  The IP's will be
used for CDN, not by end-users/subscribers.
Context: trying to work through an administrative "challenge" with LACNIC
regarding an IPv4 transfer, considering transferring to ARIN and then using
in LACNIC (then once resolved, transfer from ARIN to LACNIC).  Or just using
existing ARIN space in Brazil.
LACNIC is making things more difficult than they need to be.  I know this is
NANOG... but seeking advice, working on a global network, US HQ, currently
no active "registration" in LACNIC (except Brazil), but we operate in 5
countries in the region (data center/colo).  We would use Brazil, but very
hesitant to use their NIC (nic.br); LACNIC is saying we cannot maintain our
relationship with them using our Brazil organization (our only formal
subsidiary in the region).  LACNIC does not really define the "entity"
operating in their region well. We use our US entity with RIPE and APNIC,
simply showing documentation (contracts) that we operate in their region.
Maybe I am not using the magic word?