> On 14 Dec 2016, at 20:43, Ray Bellis <r...@bellis.me.uk> wrote: > > On 14/12/2016 20:14, Jaap Akkerhuis wrote: >> Any reason why homenet shuld use a TLD? What is wrong with something >> like homenet.arpa (or thuisnet.arpa, or bob.arpa). > > <hat partly-on> > > It's not considered user-friendly enough.
So what? End users are not expected to see this string, far less care about it, are they? Surely this string is primarily, if not exclusively, for CPE firmware? > The historic meaning of ARPA is considered by some to be problematic in > the consumer space that Homenet is targeting. Perhaps the way to resolve that is to tackle those misunderstandings and any FUD around them. The self-same issue was discussed ad nauseam ~15 years ago over ENUM. IMO, the question here for the advocates of a TLD for home networks (for some definition of that term) is “what specifically can you do with .homenet (say) that you can’t do with homenet.arpa (say)?” ie What are the use case(s) and problem statement(s) that need to be addressed? And, as a logical followup, are those issues valid? _______________________________________________ DNSOP mailing list DNSOP@ietf.org https://www.ietf.org/mailman/listinfo/dnsop
