Ray Bellis <[email protected]> wrote: >> In my opinion, it is important for the exact requirements and >> semantics for the default domain be defined, perhaps even before the >> default domain itself is selected. It's not clear to me whether the >> domain carried in the Domain-Name TLV can be a delegated domain or it >> has to be a special use domain name for location-relative name >> resolution like .local, or if either type of name is OK.
> It's my understanding (albeit this may change depending on Ted's work)
> that it may be either.
> The particular point of ".home" (or whatever) would be to provide a
> "special use" domain that is known to have "homenet site local"
> semantics that should leak as little as possible outside of that.
Yes, agreed. When you as for printer.home, you expect a ULA that you can reach.
When you ask for printer.delegatedomain.isp.example.net, you could get a
number of things: GUAs, or even ULAs that you can't reach (because they are
in my home, or because they are in your *other* home [and the VPN is down?]...)
> I think it would also be appropriate to add whatever name is chosen to
> the BCP 163 list of "Locally Server DNS Zones" such that any queries
> that do happen to leak beyond the site get sunk by the recursive
> resolver that receives them.
Agreed... and AS112?
--
Michael Richardson <[email protected]>, Sandelman Software Works
-= IPv6 IoT consulting =-
signature.asc
Description: PGP signature
_______________________________________________ homenet mailing list [email protected] https://www.ietf.org/mailman/listinfo/homenet
