3 ms·
Two nitpicks: 1. `/robots.txt` is here to stay, but everything else should use the `/.well-known/` prefix so that they do not squat the root URI: <http://tool
by gioele 15y ago
Two nitpicks:
1. `/robots.txt` is here to stay, but everything else should use the `/.well-known/` prefix so that they do not squat the root URI: <http://tools.ietf.org/html/rfc5785> http://tools.ietf.org/html/rfc5785>.
From the RFC:
> To address this, this memo defines a path prefix in HTTP(S) URIs for these "well-known locations", "/.well-known/". Future specifications that need to define a resource for such site-wide metadata can register their use to avoid collisions and minimise impingement upon sites' URI space.
2. alternative DNS root systems have been tried in the past [1] and the IETF has always spoken about them on technical and political grounds. The ORSN was probably the most autoritative alternative DNS root, backed by Vixie and others, and stopped operating few years ago.
From the Wikipedia article
> The founders of ORSN are concerned that ICANN is ultimately controlled by the government of the United States. Their aim was to limit the control over the Internet that this gives, while ensuring that domain names remain unambiguous. They also expected their network to make name resolutions faster for everyone.
[1] http://en.wikipedia.org/wiki/Alternative_DNS_root http://en.wikipedia.org/wiki/Alternative_DNS_root
[2] http://en.wikipedia.org/wiki/Open_Root_Server_Network http://en.wikipedia.org/wiki/Open_Root_Server_Network
- zeppelin_7 15y agoMuch like /robots.txt and /humans.txt I think this belongs on root. I understand that we do not want to trash the root URI. Perhaps this can be merged with the humans.txt instead? It can be a separate section in it. I also dont think this is necessarily an alternative DNS. Much like the hosts file that circulated the internet, this is is just a way to track some major IP addresses, that can be queried when the world ends.