Mohit Sethi <[email protected]> wrote: > As far as I can tell, we will not be the first ones using such a > scheme. ".home.arpa." defined in RFC 8375 > (https://www.rfc-editor.org/rfc/rfc8375.html) allows sub domains. It says: > "For an administrative domain that uses subdomains of 'home.arpa.', such as a > homenet, the recursive resolvers provided by that domain will be able to > answer queries for subdomains of 'home.arpa.'"
It's not at all the same thing :-)
home.arpa is a real anchor which home routers can serve names into using DNS.
(Replacing ".local" [which implies mDNS], and .lan, which some home routers use)
> We are taking a more conservative approach where subdomains need expert
> review and registration before they are allocated and can be used in
> deployments.
I would not characterize it this way at all.
I suspect we can have what we want, we just need to explain it to the IAB
well enough. Unfortunately too late in the week for a hallway conversation.
I found some IESG to talk to at the last break, but no IAB.
--
Michael Richardson <[email protected]>, Sandelman Software Works
-= IPv6 IoT consulting =- *I*LIKE*TRAINS*
signature.asc
Description: PGP signature
_______________________________________________ Emu mailing list [email protected] https://www.ietf.org/mailman/listinfo/emu
