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 <[email protected]<mailto:yang%20yu%20via%20nanog%20%[email protected]%3e>> Reply-To: North American Network Operators Group <[email protected]<mailto:north%20american%20network%20operators%20group%20%[email protected]%3e>> To: North American Network Operators Group <[email protected]<mailto:north%20american%20network%20operators%20group%20%[email protected]%3e>> Cc: Yang Yu <[email protected]<mailto:yang%20yu%20%[email protected]%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/[email protected]/message/SOJQ3ISXLYM6R7N7WMOR5QEF66UICAUK/ _______________________________________________ NANOG mailing list https://lists.nanog.org/archives/list/[email protected]/message/D3FEYWJLOFB25DWT25IECLHOAHK54OVC/
