3 ms·

In case people wonder why .home was not picked. One of the many issues here is that the current policy for the root DNS zone is that all new delegations from th

by phicoh 8y ago

In case people wonder why .home was not picked. One of the many issues here is that the current policy for the root DNS zone is that all new delegations from the root zone have to support DNSSEC. So they have to have DS records. Given that the IETF specifically needed to "home" zone to be unsigned, that would result in lengthy process to change the policy for the root zone. The root zone is managed by ICANN who implement the IANA function. And then operationally managed by Verisign. In the end using something under .arpa, solved a lot of issues. It is quite possible that the IETF could have allocated .home because it is currently unused. But that would still require solving the technical issues. At the same time, as long as there is wide spread use of .home, ICANN cannot really allocate that as a new gTLD. So it should be sort of safe to continue to use that. But "homenet" compliant routers should come with home.arpa preconfigured.

forapurpose 8y ago
Why not just reserve .home permanently so that it won't be allocated and tell people to use it? Does that somehow result in more bogus traffic to root and other DNS servers? Between the lines, I read that ICANN doesn't give a f- about home users. Home users are not on the ICANN board (they've never heard of ICANN), don't give presentations at conferences or write papers, don't talk shop over lunch with ICANN members ... home users are invisible and have no voice. 'So here's this kludge that requires zero effort from us, is probably a little confusing for you[0] - we hope you like it because we're not doing anything more.'
- phicoh 8y ago
  The question is then who should reserve it? The IETF can ask for domain names for technical reasons, i.e. as part of internet standards. ICANN can allocate domains as gTLDs but doesn't have mandate/policy to reserve names without using them. Effectively .home is reserved because there is too much use to safely allocate it. Finally, IETF can recognise .home as a special domain that is used locally. But that didn't work out because an insecure delegation is needed for DNSSEC. Purely formally, ICANN has 'at large' structures that represent the interests of users.

by phicoh 8y ago

forapurpose 8y ago

Why not just reserve .home permanently so that it won't be allocated and tell people to use it? Does that somehow result in more bogus traffic to root and other DNS servers? Between the lines, I read that ICANN doesn't give a f- about home users. Home users are not on the ICANN board (they've never heard of ICANN), don't give presentations at conferences or write papers, don't talk shop over lunch with ICANN members ... home users are invisible and have no voice. 'So here's this kludge that requires zero effort from us, is probably a little confusing for you[0] - we hope you like it because we're not doing anything more.'

phicoh 8y ago
The question is then who should reserve it? The IETF can ask for domain names for technical reasons, i.e. as part of internet standards. ICANN can allocate domains as gTLDs but doesn't have mandate/policy to reserve names without using them. Effectively .home is reserved because there is too much use to safely allocate it. Finally, IETF can recognise .home as a special domain that is used locally. But that didn't work out because an insecure delegation is needed for DNSSEC. Purely formally, ICANN has 'at large' structures that represent the interests of users.