On Jul 31, 2012, at 11:32 , Curtis Villamizar <[email protected]> wrote: > > s/\.local/.sitelocal/ and allow a home network to be routed and then I agree > with 100% of this.
I consider it a minor oversight that I wrote "local." without remembering that recent developments in the effort to standardize mDNS have strengthened the requirement for the "local." TLD to have an officially special usage. I was mired by my habit of thinking about the practical consequences of many actual networks in the wild not respecting this proposed special usage. I suppose HOMENET shouldn't contribute to the ongoing festival of error, so I'm okay with "sitelocal." as the TLD even when home networks are single links. Also, the reason I proposed constraining the scope of a working group task to handling just reverse DNS is that solving that problem properly will necessarily involve solving a critical subset of the problems that need to be solved to handle forward DNS as well. Do the reverse DNS case first, then extending that work to cover the forward DNS case will be much easier. -- james woodyatt <[email protected]> member of technical staff, core os networking _______________________________________________ homenet mailing list [email protected] https://www.ietf.org/mailman/listinfo/homenet
