Re: TPAC breakout, October 28: Evolving the web browser for spatial computing, digital twins, physical AI and robotics

Sean, Neil, colleagues,
Thank you for the invitation, and for the explicit offer to reply with questions — I will not be able to join in Dublin, so I am taking you up on it here.
The part of the proposal I find most interesting is the arrival model: "a device would find what's published at a location as a person or robot arrives, without anyone typing a URL." At that moment, discovery is simultaneously three problems — an addressing problem (what names the thing just found), a freshness problem (how old is what was found), and a trust problem (who vouches that it belongs where it claims). One question on each, all asked from the arriving device's point of view.
1. Naming what is published at a place. When nobody types a URL, the arriving device still needs names it can act on. What is the intended name space for location-anchored services — names issued by a registry (DNS- or DID-style), or names that can be derived from the publisher or the content itself, so that discovery keeps working when no registry is reachable from the arrival point?
2. Freshness at the arrival point. Arrival points are precisely where networks are least reliable — plant basements, disaster sites, inside a gated perimeter. Does the session's model assume online verification at discovery time, or can published claims carry their own locally checkable time boundaries — an issue time, a validity window, or a standing lease — so that a device can judge how old what it found is, offline?
3. Binding a twin to its building. Many independent publishers compose one scene, and an arriving robot must decide whether the twin it found actually describes the building in front of it. What establishes that binding, and what lets the arriving party verify it on its own — a registry lookup, or an attestation the publisher carries and the arrival can check without contacting anyone?
No agenda push intended — these are simply the three questions we would bring to the floor tomorrow. If they get airtime in the session, I would be glad to read the summary here; and I am happy to elaborate any of them asynchronously.
Best regards,
Lee
lee@aicent.com
Author, draft-li-rttp-iqa-addressing-00 (ISE review)
Resonant Time Transfer Protocol (RTTP, CRI 27)
Identity Quality Assurance (IQA, CRI 28)
Sites: https://rttp.com · https://iqa.org
Blog: https://blog.aicent.com/

Received on Monday, 26 October 2026 20:23:30 UTC