> On Mar 21, 2017, at 10:05 AM, Philip Homburg <pch-dnso...@u-1.phicoh.com> > wrote: > >> This .home / .homenet issue has already been going on for a very >> long time. The longer we wait with resolving this issue, the worse >> the deployment situation will be of software mixing .home vs >>> homenet. > > Do we really expect homenet to be only ever used in a 'home'? It seems to > me that homenet is an interesting technology that would work in any small > IPv6 network, i.e. a small office. > > In that context, using the string 'homenet' would be very confusing to users > outside a home context. Maybe reserving a name that has less context would > be better.
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. Just sayin' - Ralph > > _______________________________________________ > DNSOP mailing list > DNSOP@ietf.org > https://www.ietf.org/mailman/listinfo/dnsop _______________________________________________ DNSOP mailing list DNSOP@ietf.org https://www.ietf.org/mailman/listinfo/dnsop
