> On Mar 21, 2017, at 10:12 AM, Paul Wouters <p...@nohats.ca> wrote: > > On Tue, 21 Mar 2017, Ralph Droms wrote: > >> If draft-ietf-homenet-dot-03 specified homenet.arpa, the IETF could assign >> as many different names as wanted for different scoping scenarios, without >> interacting with ICANN for each assignment. > > arpa is a loaded name for some non-US citizens.
RFC 3172 was written in 2001….which predates the vast majority of internet availability and use, and in fact quite a large number of internet users. Respectfully, I’ve always wondered who has this problem (US or non-US) besides network infrastructure geeks Of a Certain Age (yes, including myself, and many IETF participants). > localnet.ietf ? :P For DNSOP participants, I hope this discussion is suggesting some possible ways forward now that we have a problem statement; it’s not clear whether such work will occur in DNSOP, but if work is needed, we should be thinking about how to do it. Suzanne _______________________________________________ DNSOP mailing list DNSOP@ietf.org https://www.ietf.org/mailman/listinfo/dnsop
