Related reminder that the IAB is holding a workshop on IP Geolocation – with
statements of interested due at the end of this week. For more info:
https://www.iab.org/announcements/call-for-papers-iab-workshop-on-ip-address-geolocation-ip-geo/
Call for Papers: IAB Workshop on IP Address Geolocation (ip-geo)
17 Jul 2025, 6:42 p.m.
This workshop aims to understand the current use cases for publishing,
discovering, and consuming IP address geolocation data.
Workshop Description
This workshop aims to understand the current use cases for publishing,
discovering, and consuming IP address geolocation data ('IP-geo' hereafter). It
will also explore areas for improvement, both in ways to update or replace IP
geolocation mechanisms, and to consider mechanisms that satisfy the use cases
without relying on IP addresses.
The IAB seeks short position papers on the topics listed below. This list is
non-exhaustive and should be interpreted broadly.
* Today's Use Cases: How is IP-geo data used today? In particular, what are
the root challenges, technical needs, or business needs that IP-geo data is
being leveraged to address?
* Gaps and Problems: What are gaps or problems with the current approaches
being used by industry? Are there preferences for particular file types? How
effective are current approaches? What are the impacts on user privacy?
* Future Opportunities: If we re-designed technical solutions to address
the motivating use cases, what would those solutions look like? Are there
alternative approaches that can avoid the gaps and problems we have today? Is
there value in conveying other information in addition to or instead of
geography, such as type of last mile network connection?
All inputs submitted and considered relevant will be published on the workshop
website. The organizers will issue invitations based on the submissions
received. Sessions will be organized according to content, and not every
accepted submission or invited attendee will have an opportunity to present;
the intent is to foster an active discussion and not simply to have a sequence
of presentations. A workshop report covering all submissions and the workshop
discussion will be published afterwards.
From: Justin Krejci via NANOG <[email protected]>
Date: Tuesday, September 30, 2025 at 11:52
To: [email protected] <[email protected]>
Cc: Justin Krejci <[email protected]>
Subject: Re: RFC8805 geofeed validation
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://urldefense.com/v3/__https://lists.nanog.org/archives/list/[email protected]/message/SOJQ3ISXLYM6R7N7WMOR5QEF66UICAUK/__;!!CQl3mcHX2A!EWKzhuFJjqKZrA9JvsdK4mEcnCjYL_cGrIrdgY3flRLN8CLcQTudGC4BQe5Y1SI4Wv-7St1xhCK62725ucdmQQdDog$<https://urldefense.com/v3/__https:/lists.nanog.org/archives/list/[email protected]/message/SOJQ3ISXLYM6R7N7WMOR5QEF66UICAUK/__;!!CQl3mcHX2A!EWKzhuFJjqKZrA9JvsdK4mEcnCjYL_cGrIrdgY3flRLN8CLcQTudGC4BQe5Y1SI4Wv-7St1xhCK62725ucdmQQdDog$>
_______________________________________________
NANOG mailing list
https://urldefense.com/v3/__https://lists.nanog.org/archives/list/[email protected]/message/D3FEYWJLOFB25DWT25IECLHOAHK54OVC/__;!!CQl3mcHX2A!EWKzhuFJjqKZrA9JvsdK4mEcnCjYL_cGrIrdgY3flRLN8CLcQTudGC4BQe5Y1SI4Wv-7St1xhCK62725ucfXPSwsIg$<https://urldefense.com/v3/__https:/lists.nanog.org/archives/list/[email protected]/message/D3FEYWJLOFB25DWT25IECLHOAHK54OVC/__;!!CQl3mcHX2A!EWKzhuFJjqKZrA9JvsdK4mEcnCjYL_cGrIrdgY3flRLN8CLcQTudGC4BQe5Y1SI4Wv-7St1xhCK62725ucfXPSwsIg$>
_______________________________________________
NANOG mailing list
https://lists.nanog.org/archives/list/[email protected]/message/BVQ3U2F3E535TJCPFAZ47WS7XFP46P7J/
