On 6/16/2016 6:04 PM, Andrew Sullivan wrote: > On Thu, Jun 16, 2016 at 01:26:29PM -0700, Joe Touch wrote: >> See RFC3172. >> >> I don't think .arpa is the correct place for this sort of stuff. > Why? "[T]his domain name undertakes a role as a limited use domain > for Internet infrastructure applications," and > > This domain is termed an "infrastructure domain", as its role is to > support the operating infrastructure of the Internet. In particular, > the "arpa" domain is not to be used in the same manner (e.g., for > naming hosts) as other generic Top Level Domains are commonly used. The use of .home is a lot more like a conventional TLD than it is like any other use in .arpa (e.g., reverse lookups based on IP addresses, telephone number mapping, etc.).
> If the names beneath this special-use name are supposed to cause > software to do something differently than it would with any other > domain name, then that sounds like "infrastructure" to me. That's why > we used it for the special IPv4 only name in dns64, for instance. The software does exactly the same thing. Having a response is based on a local database, such that the same query in different places gives different results, is not uncommon in other TLD lookups. Joe _______________________________________________ homenet mailing list [email protected] https://www.ietf.org/mailman/listinfo/homenet
