Two things someone will need to think about:
ICANN is now selling "dotless" names. A name without dots has a defined
behavior in most DNS resolvers; they find a way to further qualify them. Do we
want to humor ICANN, or solve this?
mDNS is crippled, in that it operates on a single LAN. That might describe
Apple networks; per the architecture document it doesn't describe all home
networks. Do we want to provide an admin-scope multicast address for it, and if
so, what do we recommend for routing?
On Mar 9, 2012, at 10:05 AM, Ralph Droms wrote:
> Here's my list of "desired behaviors" for name resolution, proposed for
> inclusion in the architecture document; comments and suggestions welcome:
>
> * Disconnected operation ("fate sharing"): name resolution for reachable
> devices continues if the local network is disconnected from the global
> Internet
> * Relative name resolution: some naming convention that allows name
> resolution while mitigating the need to know an absolute location in the
> global DNS namespace
> * Unmanaged operation
> * Efficient message utilization: for example, keep unwanted traffic off of an
> IEEE802.15.4 network
> * Representation in the global DNS namespace, for access from off-net
>
> - Ralph
>
> _______________________________________________
> homenet mailing list
> [email protected]
> https://www.ietf.org/mailman/listinfo/homenet
_______________________________________________
homenet mailing list
[email protected]
https://www.ietf.org/mailman/listinfo/homenet
