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
<https://datatracker.ietf.org/doc/html/rfc3693>
RFC 5870: A Uniform Resource Identifier for Geographic Locations ('geo'
URI) <https://datatracker.ietf.org/doc/html/rfc5870>
RFC 6288: URN Namespace for the Defence Geospatial Information Working
Group (DGIWG) <https://datatracker.ietf.org/doc/html/rfc6288>
RFC 6397: Multi-Threaded Routing Toolkit (MRT) BGP Routing Information
Export Format with Geo-Location Extensions
<https://datatracker.ietf.org/doc/html/rfc6397>
RFC 6772: Geolocation Policy: A Document Format for Expressing Privacy
Preferences for Location Information
<https://datatracker.ietf.org/doc/html/rfc6772>
RFC 7942: The GeoJSON Format <https://datatracker.ietf.org/doc/html/rfc7942>
RFC 8142: GeoJSON Text Sequences
<https://datatracker.ietf.org/doc/html/rfc8142>
RFC 8805: A Format for Self-Published IP Geolocation Feeds
<https://datatracker.ietf.org/doc/html/rfc8805>
RFC 9092: Finding and Using Geofeed Data
<https://datatracker.ietf.org/doc/html/rfc9092>
--
Charles Polisher
(/Pedantic, I?/)