Re: RFC8805 geofeed validation

[Justin Krejci via NANOG <nanog () lists nanog org>]

I have found some Geolocation service providers will ignore entries that are missing certain fields.
With this real but anecdotal data point, I would suggest the results of having various non-ASCII or absent fields will 
vary by organization that ingests your 8805 feed.

Beyond that, I have no solid data.


-----Original Message-----
From: Yang Yu via NANOG <nanog () lists nanog org<mailto:Yang%20Yu%20via%20NANOG%20%3cnanog () lists nanog org%3e>>
Reply-To: North American Network Operators Group <nanog () lists nanog 
org<mailto:North%20American%20Network%20Operators%20Group%20%3cnanog () lists nanog org%3e>>
To: North American Network Operators Group <nanog () lists nanog 
org<mailto:North%20American%20Network%20Operators%20Group%20%3cnanog () lists nanog org%3e>>
Cc: Yang Yu <yang.yu.list () gmail com<mailto:Yang%20Yu%20%3cyang.yu.list () gmail com%3e>>
Subject: RFC8805 geofeed validation
Date: Thu, 25 Sep 2025 12:43:42 -0500

Questions for folks ingesting geofeed,

what do you use for address validation?
Are non-ASCII characters supported, especially in City field? e.g. 부산 vs Busan
What happens when Region field is empty? discard the line / use
Country only / try to use Country + City (which may not be unique)
Common parsing / validation errors?



Thanks,

Yang
_______________________________________________
NANOG mailing list
https://lists.nanog.org/archives/list/nanog () lists nanog org/message/SOJQ3ISXLYM6R7N7WMOR5QEF66UICAUK/
_______________________________________________
NANOG mailing list 
https://lists.nanog.org/archives/list/nanog () lists nanog org/message/D3FEYWJLOFB25DWT25IECLHOAHK54OVC/