Yes also taking on that point it's interesting that the growing distribution of virtual spaces for code, data and models are likely to be cryptographically demarcated and abstracted from hosting physical infrastructures. In that environment routing proof is cryptographically intrinsic and that may stimulate fresh thinking about the role of naming and also techniques for indirection mapping layers you mentioned before. That doesn't kill DNS but it may focus future best practices and suitability as host for carbuncle protocol developments. C Karl Auerbach via At-Large <at-large@icann.org> writes:
In our internet naming system "host names" are synonyms for IP addresses which are labels on network interfaces on host machines.
In our evolving internet of applications - typically floating in a conceptual "cloud" - the binding between a specific instance of an application service and a host/network interface is something that is rather dynamic and changeable, even during the existence of a client-to-service session.
DNS is sort of becoming like MAC addresses - it is becoming less and less visible to users who are getting more used to dealing with other sorts of naming systems, often application specific naming systems.
DNS can well be (and usually ought to be) underneath. But DNS isn't designed for the kind of dynamics that can occur with the increased rates of user-to-service binding (and changes to those bindings) that are becoming more typical.
Much of the magic of DNS comes from caching. And caching is troublesome in a world where client and service relationships are potentially changeable, even within a few seconds.
I am not sure that any single higher-than-DNS name (or attribute) lookup system will be right for all applications, so we may end up with several of these higher level systems. This would largely be as visible to users as are the lookups inside AWS, Facebook, or other systems that are evolving their own notion of "names".
In the old ISO/OSI world they had a concept of "application titles" which are distinct from network addresses. But even that is perhaps too static for they way our internet is becoming more a world of pieces of code that may run in many places - or may be started or moved as loads and connectivity and location change.
--karl--
On 10/25/25 1:14 PM, bzs@theworld.com wrote:
On October 24, 2025 at 15:54 at-large@icann.org (Karl Auerbach via At-Large) wrote:
Oh, by-the-way, I don't mean, in the text below, that DNS is no longer usable. Rather than we need an additional naming system (perhaps based on attributes) that can lead to stable DNS names (thus obviating a need for the kind of short-lived DNS name-mapping juggling that goes on now.)
As has been oft said in computer science - and networking - one can solve many problems by adding an additional layer of indirection.
--karl--
Isn't that what host names are?
_______________________________________________ At-Large mailing list -- at-large@icann.org To unsubscribe send an email to at-large-leave@icann.org
At-Large Official Site: http://atlarge.icann.org _______________________________________________ By submitting your personal data, you consent to the processing of your personal data for purposes of subscribing to this mailing list accordance with the ICANN Privacy Policy (https://www.icann.org/privacy/policy) and the website Terms of Service (https://www.icann.org/privacy/tos). You can visit the Mailman link above to change your membership status or configuration, including unsubscribing, setting digest-style delivery or disabling delivery altogether (e.g., for a vacation), and so on.
-- Christian de Larrinaga