> If you don't like the idea using the NODE NAME TLV to announce DNS > information of the local hosts, how would you do it without a central > server configured by a network admin?
What we currently have defined and implemented is this: Each HNCP router SHOULD provide and announce an auto-generated or user-configured name for each internal Common Link (Section 6.1) for which it is the designated DHCPv4, stateful DHCPv6 server, MDNS proxy, or for which it provides forward or reverse DNS services on behalf of connected devices. This means that we don't use a central server, but each HNCP router (or well one per link) SHOULD offer name resolution for that link and announce a name (e.g. lan1.router1.home) using an HNCP TLV. Under that zone it places hostnames acquired via DHCPv4, DHCPv6 (or other methods). If it runs an MDNS hybrid proxy (dns->mdns querier) it also announces the zone as DNS-SD browsable using a flag in the TLV. The hybrid proxy itself issues an MDNS-request for each DNS-request it receives for the specific link and collects and aggregates all MDNS-replies and sends them back to the originator of the DNS-request. Each HNCP router SHOULD provide a recursive name resolution server which honors the announcements made in Delegated Zone TLVs (Section 10.5), Domain Name TLVs (Section 10.6) and Node Name TLVs (Section 10.7) Now this finally ensures that if you - as a client - are connected to an HNCP router you can resolve all client hostnames (laptop.lan1.router1.home), HNCP hostnames (router1.home), and enumerate all DNS-SD domains announced by any HNCP routers. DNS-SD clients already send requests to all DNS-SD browsable domains (i.e. all hybrid proxies in your homenet) on their own. If you client speaks DNS-SD, like most Linux, Android & Apple devices do (and Windows with additional software), you can thereby enumerate MDNS-capable devices and services on links which announce a hybrid proxy. So this is all zero-conf basically but your implementation should let you fine-tune it, e.g. change link and router names to something more elegant so your hostnames are like printer.lan.office.home, or tv.wifi.bedroom.home) and should let you add manual hostnames (using Node Name TLVs) like nas.home. _______________________________________________ homenet mailing list [email protected] https://www.ietf.org/mailman/listinfo/homenet
