On Dec 14, 2016, at 3:14 PM, Jaap Akkerhuis <j...@nlnetlabs.nl> wrote: > Any reason why homenet shuld use a TLD? What is wrong with something > like homenet.arpa (or thuisnet.arpa, or bob.arpa).
It’s more typing, and is not consistent with ".local". That is to say, a reasonably intelligent and observant user with no mental model of how the DNS works would see ".local" and ".home.arpa" as very different things, when in fact the intention is that they be considered to be very similar things. This is not an absolute requirement, obviously, but there has been a strong sentiment within the working group, from a usability perspective, to try to preserve this appearance. It’s also been pointed out that if you google ARPA, you get a response that ARPA is a military thing. This would probably add to the cognitive dissonance. One way to fix that would be to create a ".lcl" or ".nuq" or something like that domain with a secure delegation that’s then handled the same way ".arpa" is, and that is explicitly designated as a place for putting non-globally-unique names that are meant to be resolved using the DNS. But this option isn’t available to the working group, and isn’t preferred anyway.
_______________________________________________ DNSOP mailing list DNSOP@ietf.org https://www.ietf.org/mailman/listinfo/dnsop
