From: "Livingood, Jason" <Jason_Livingood@comcast.com>
To: Frantisek Borsik <frantisek.borsik@gmail.com>,
Dave Taht via Starlink <starlink@lists.bufferbloat.net>
Subject: [Starlink] Re: Lost in Space: The Limits of Geolocation in a Satellite-Connected World (new article from Geoff Huston)
Date: Wed, 1 Oct 2025 13:18:43 +0000 [thread overview]
Message-ID: <MW4PR11MB71045524AA90D9ACF5DF9982C7E6A@MW4PR11MB7104.namprd11.prod.outlook.com> (raw)
In-Reply-To: <CAJUtOOj5=3BB+A2vfzcww-OWZjbyp-JN1C8o3Oy5ZkK8NuXEWg@mail.gmail.com>
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?
From: Frantisek Borsik via Starlink <starlink@lists.bufferbloat.net>
Date: Wednesday, October 1, 2025 at 01:33
To: Dave Taht via Starlink <starlink@lists.bufferbloat.net>
Subject: [Starlink] Lost in Space: The Limits of Geolocation in a Satellite-Connected World (new article from Geoff Huston)
https://urldefense.com/v3/__https://circleid.com/posts/limits-of-geolocation-in-a-satellite-connected-world__;!!CQl3mcHX2A!EFQL8aw74ccWvN8krJFCWAe6jGUXLywQDRUR_DX7p0sz9VXAb0IJ-o-NUrY106OF9HEQlkGBclyVVUmd3CB6Ef7vTlJ2Y7KKvw$<https://urldefense.com/v3/__https:/circleid.com/posts/limits-of-geolocation-in-a-satellite-connected-world__;!!CQl3mcHX2A!EFQL8aw74ccWvN8krJFCWAe6jGUXLywQDRUR_DX7p0sz9VXAb0IJ-o-NUrY106OF9HEQlkGBclyVVUmd3CB6Ef7vTlJ2Y7KKvw$>
“Where are you?” is not an easy question to answer on the Internet. The
telephone system’s address plan embedded a certain amount of physical
location information in the fixed-line network, and a full E.164 telephone
number indicated your location in terms of your country and your area
within that country. The Internet did not adopt a geographic address plan,
which means that you will need a lot of additional information to map an IP
address to a location at the country or city level."
All the best,
Frank
Frantisek (Frank) Borsik
*In loving memory of Dave Täht: *1965-2025
https://urldefense.com/v3/__https://libreqos.io/2025/04/01/in-loving-memory-of-dave/__;!!CQl3mcHX2A!EFQL8aw74ccWvN8krJFCWAe6jGUXLywQDRUR_DX7p0sz9VXAb0IJ-o-NUrY106OF9HEQlkGBclyVVUmd3CB6Ef7vTlK3wrVjiw$<https://urldefense.com/v3/__https:/libreqos.io/2025/04/01/in-loving-memory-of-dave/__;!!CQl3mcHX2A!EFQL8aw74ccWvN8krJFCWAe6jGUXLywQDRUR_DX7p0sz9VXAb0IJ-o-NUrY106OF9HEQlkGBclyVVUmd3CB6Ef7vTlK3wrVjiw$>
https://urldefense.com/v3/__https://www.linkedin.com/in/frantisekborsik__;!!CQl3mcHX2A!EFQL8aw74ccWvN8krJFCWAe6jGUXLywQDRUR_DX7p0sz9VXAb0IJ-o-NUrY106OF9HEQlkGBclyVVUmd3CB6Ef7vTlJI5d0lSQ$<https://urldefense.com/v3/__https:/www.linkedin.com/in/frantisekborsik__;!!CQl3mcHX2A!EFQL8aw74ccWvN8krJFCWAe6jGUXLywQDRUR_DX7p0sz9VXAb0IJ-o-NUrY106OF9HEQlkGBclyVVUmd3CB6Ef7vTlJI5d0lSQ$>
Signal, Telegram, WhatsApp: +421919416714
iMessage, mobile: +420775230885
Skype: casioa5302ca
frantisek.borsik@gmail.com
_______________________________________________
Starlink mailing list -- starlink@lists.bufferbloat.net
To unsubscribe send an email to starlink-leave@lists.bufferbloat.net
next prev parent reply other threads:[~2025-10-01 13:18 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-10-01 5:34 [Starlink] " Frantisek Borsik
2025-10-01 5:56 ` [Starlink] " J Pan
2025-10-01 16:46 ` Michael Richardson
2025-10-01 17:40 ` J Pan
2025-10-01 21:08 ` Michael Richardson
2025-10-01 22:50 ` J Pan
2025-10-01 13:18 ` Livingood, Jason [this message]
2025-10-01 21:22 ` David Lang
2025-10-01 21:51 ` Spencer Sevilla
2025-10-01 22:48 ` J Pan
2025-10-01 23:05 ` David Lang
2025-10-02 4:34 ` J Pan
[not found] ` <22339.1759337017@obiwan.sandelman.ca>
2025-10-01 16:47 ` Michael Richardson
2025-10-01 21:13 ` David Lang
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://lists.bufferbloat.net/postorius/lists/starlink.lists.bufferbloat.net/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=MW4PR11MB71045524AA90D9ACF5DF9982C7E6A@MW4PR11MB7104.namprd11.prod.outlook.com \
--to=jason_livingood@comcast.com \
--cc=frantisek.borsik@gmail.com \
--cc=starlink@lists.bufferbloat.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox