On Fri, Aug 28, 2015 at 12:54 PM, Juliusz Chroboczek <[email protected]> wrote: >> - publish a DNS Delegated Zone TLV that points to a (local or remote) >> DNS server that responds for that zone. > > Markus, > > Let's please not put per-host state into HNCP, it's not dealing very well > with churn (remember Jin Kaiwen's results?). Let's use HNCP for > bootstrapping the routers, let's leave routing to the routing protocol, > and naming to the naming protocols. You know, nails and hammers. > > Let's also try to avoid having any more elections (per-link or global). > If a protocol doesn't cannot deal with multiple servers, it should provide > its own election mechanism.
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? Henning Rogge _______________________________________________ homenet mailing list [email protected] https://www.ietf.org/mailman/listinfo/homenet
