Hi all, Just to add some information to the geofeed discussion, I found could be valuable:
At LACNIC, there is already +5 years of operational support for geofeeds aligned with the IETF work in this space. RFC 8805 ( https://datatracker.ietf.org/doc/html/rfc8805 ) defines the standard CSV format for geofeeds, and RFC 9632 (https://www.rfc-editor.org/rfc/rfc9632.html) specifies the use of the geofeed: attribute in RPSL objects (e.g., inetnum / inet6num) so that operators can reference their geofeed directly from WHOIS/RDAP data. * Within the LACNIC region, members can: * Publish geofeed information through MiLACNIC. * Associate geolocation data with their IP resources. * Make this information publicly available in a structured and machine-readable way. By the way, there is a raw file you can download here: https://milacnic.lacnic.net/lacnic/geofeeds This allows operators to provide first-party location data in a standards-based manner, without relying solely on third-party inference. Of course, adoption and operational practices vary (clear low adoption), but the important is that functionality is available and aligned with the relevant RFCs. I thought this might be useful context for the ongoing discussion around trust, verification, and the role of RIRs in facilitating accurate geolocation data. Best regards, Nicolás Fiumarelli _______________________________________________ NANOG mailing list https://lists.nanog.org/archives/list/[email protected]/message/YVI6JZ2Z62B3VYFRARM7Y663Z32S3ZP3/
