Hi Hank,
On 07/05/2021 07:17, Hank Nussbacher via db-wg wrote:
From RFC8805 section 3.2:
A consumer should only trust geolocation information for IP addresses
or prefixes for which the publisher has been verified as
administratively authoritative.
I am wondering whether others who will implement RFC8805 will also use
BGP routing tables as authoritative for geo-location checks.
You started a good topic. The main goal of RFC8805 is to describe a file
format, the validation of resource ownership is up to the consumer. At
least that's my interpretation. At the moment, this is done in various
ways (including some "original" ones).
However, what we are proposing builds on top of RFC8805 exactly with the
goal to provide a defined and easy way to correctly retrieve such data.
Please, see
https://tools.ietf.org/html/draft-ietf-opsawg-finding-geofeeds-06 Open
implementations, such as [1], will further ease this process.
Ciao,
Massimo
[1] https://github.com/massimocandela/geofeed-finder
