3 ms·
While I 100% agree on your critique of DNS, there's two small issues: 1. The protocols you list are not strictly married to DNS in any way. e.g. https://<ip-ad
by lucideer 5y ago
While I 100% agree on your critique of DNS, there's two small issues:
1. The protocols you list are not strictly married to DNS in any way. e.g. https://<ip-address> https://<ip-address> works fine. Granted it's not very practical to use right now but there's nothing in the HTTP spec. preventing things working without DNS.
2. DNS isn't technically married to ICANN either. There are alternative domain name assignment proposals and systems that use the same protocols without ICANN. Again, not super practical today but theoretically possible to use.
So the fact that these systems are all so loosely coupled makes them pretty resilient and very much "built to last". Moving away from ICANN may be hampered by the inertia of a gargantuan network effect, but that's not any bigger than the inertia of moving off HTTP completely.