3 ms·
From a non-expert: is there any reason (other than consumer packaging and polish) that a system like this couldn't be rolled out immediately, with ICANN as the
by pessimizer 4y ago
From a non-expert: is there any reason (other than consumer packaging and polish) that a system like this couldn't be rolled out immediately, with ICANN as the default provider?
- schanzen 4y agoThere are a lot of stakeholders involved and a lot of applications relying on DNS may have problems (browsers). So the migration path is long and winded I guess. Other than that, no. GNS itself could also be realised on top of other DHTs, such as libp2p/IPFS (before anyone mentioned the, eh, maturity issues of the reference implementation in GNUnet.)
- pessimizer 4y agoYou can't shim GNS into looking like DNS to the OS?
- schanzen 4y agoYou can. Either using nsswitch plugins or a local DNS service that resolved the names in GNS. But, browsers are delicate when it comes to TLS certificates, for example. See also https://www.ietf.org/archive/id/draft-schanzen-gns-19.html#name-migration-paths https://www.ietf.org/archive/id/draft-schanzen-gns-19.html#n...
- t-3 4y agoThere's no technical reason it couldn't, but a big non-technical one: it doesn't allow for the rent-seeking behavior that supports ICANN and the internet name industry.
- pessimizer 4y agoBut would it be necessary for ICANN to participate in or consent to someone else (trustworthy) making their registry available over GNS?