nanog mailing list archives
Re: Geolocation data management practices?
From: Job Snijders via NANOG <nanog () nanog org>
Date: Thu, 21 Apr 2022 15:01:47 +0200
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
Current thread:
- Geolocation data management practices? Shawn (Apr 21)
- Re: Geolocation data management practices? Job Snijders via NANOG (Apr 21)
- Re: Geolocation data management practices? Rubens Kuhl (Apr 21)
- Re: Geolocation data management practices? Josh Luthman (Apr 21)
- Re: Geolocation data management practices? Charles Polisher (Apr 21)
- Message not available
- Re: Geolocation data management practices? Justin Krejci (Apr 21)