Brian E Carpenter <[email protected]> wrote: > Hi Martin, > > I'm fine with your answers and proposed changes. > > > Hmm, AFAICT, no special config is needed for mDNS to work? So if > > the device supports mDNS, it will be used for .local. names, right? > > I think that's the main point, but RFC6762 does say this: > "The ".local." > suffix could appear in the search list because the user manually > configured it, or because it was received via DHCP [RFC2132] or via > any other mechanism for configuring the DNS search list." > That means it would be quite legitimate to configure it with NETMOD.
Yes that is my understanding as well. > So probably you can ignore my comment ;-). > > (There's also a more general question: what does the host do if it > receives conflicting config via DHCP and NETMOD? I guess you have a > general answer to that.) Yes; so the YANG configuration data models is the "static" or "manual" configuration. Then there are all kinds of other mechanism that can influence what the device is actually using, i.e., influence its operational state. DHCP is one example. RA is another. Exactly how this dynamic influence of the operational state is done depends on the mechanism, on the different parmeters, and maybe on local policy. Sometimes the manually configured value has higher precedence, sometimes the value received over DHCP, and sometimes the values may be both be used. > > Or are you suggesting that this model should support configuration of > > mDNS as well? > > As far as I know, mDNS is intended to be a zero-configuration > mechanism, so I think the answer is "No". It might be worth checking > with somebody in the DNSSD WG though. Ok. /martin _______________________________________________ Gen-art mailing list [email protected] https://www.ietf.org/mailman/listinfo/gen-art
