Abhayakara
commented
7 years ago This feels like a protocol specification, not an architecture. I don't think this is completely the wrong thing to do, but I think the focus and level of detail is wrong for the architecture document.
Action item: Ted writes up a counterproposal, we discuss
mglt
I believe it would be appropriated the document describes how the naming architecture behaves at least for the most common actions performed by the end user.
The action I believe should be considered what is happening when:
The intent is clearly to provide a high level view of how things are working. The current section 3 is providing more details on how to set the functions. Maybe that can be organized otherwise.
I am proposing the following text for these actions. At the bottom I have question that needs to be clarified.
The principle of the simple home network naming architecture is as follows.
When a new host is joining the network
It is being provisioned with an IP address, and DNS Proxy via DHCPv6 option DNS Recursive Name Server option described in [4] or the Neighbor Discovery Extension Recursive DNS Server Option described in [5]. The DNS Proxy is always on the link so DNS Updates to the destination of the Advertising Proxies can be controlled.
If the host or service is not homenet-aware, it MAY perform service discovery using mDNS on the link it is hosted, and sends DNS queries to the DNS Proxy.
If the host/service is homenet aware, it performs service discovery using unicast DNS. These DNS queries as well as those associated to the Global DNS are sent to the DNS Proxy. The DNS Proxy is responsible to proceed to the appropriated resolution. The distinction between the different resolution is based on the "home.arpa" suffix.
When a new link is created
The HNR involved needs to extend the Discovery mechanism to that link. Either the HNR implements a Discovery Proxy or a Discovery Relay. The HNR MAY act as a Discovery Proxy, in which case it needs to discover the Discovery Broker and provides the necessary information so the Discovery Broker adds the new link domain - typically "linkxxx.home.arpa". The name of the link is automatically configured from the IP prefix of the new link. If there is no Discovery Broker, the HNR MUST be ready to play as a Discovery Broker in addition to the Discovery Proxy. If the HNR is informed of the existence of a Discovery Discovery, the HNR may prefer to act as a Discovery Relay and attempt to associate with the Discovery Proxy. In case the association fails, the HNR MUST fall back to instantiate a Discovery Proxy.
The HNR also needs to extends the Advertising Proxy to its link and is expected to instantiate a Advertising Proxy.
Lemon & Migault Expires January 2, 2018 [Page 7] Internet-Draft Simple Homenet Naming/SD Arch July 2017
The HNR MUST also be able to provides the necessary information so the hosts and nodes attached to the link can perform the resolution via the DNS Proxy.
When the no DNS Proxy is found inside the homenet work, that is instantiated with a non local scope IP address, the HNR MUST instantiate a DNS Proxy.
When a host performs a DNS resolution or a service discovery lookup:
A hosts that is not homenet-aware sends mDNS queries on its LAN and DNS queries on the DNS Proxy.
A host that is homenet aware sends all DNS unicast queries to the DNS Proxy.
The requests that are not intended for the Global DNS are identified by the "home.arpa" suffix. These requests are sent to the Discovery Broker. The Discovery Broker performs two resolutions one against the Advertising Proxies and one against the Discovery Proxies. Results are aggregated back to the NDS Proxy.
Global DNS resolutions are forwarded to the resolver by the DNS Proxy. The DNS Proxy may use different rules to select the appropriated resolver. When the DNS requested is performed with a non local IP address, the DNS Proxy may use that IP address to identify the appropriated resolver. When the IP address is of local scope, the DNS Proxy may partition the naming space between the resolvers.
How the Discovery Proxy identifies the Discovery Broker.
How the Advertising Proxies identifies the Discovery Broker.
DNS Proxy can be instantiated on each HNR to control the Updates, the other way around may also to have Advertising Proxies on each HNR and a single DNS Proxy.