This proposal doesn't satisfy the problem statement. (which nobody wrote. :)
I don't want to tube on writing a formal requirements doc before we finish doing a naming architecture, but I think now that I've taken a stab at this, we should think about our reactions to and see if we can scope the problem we are trying to solve in a bit more detail than just "naming and service discovery on homenets." On Wed, Jul 20, 2016 at 11:27 AM, Juliusz Chroboczek < [email protected]> wrote: > Not proposing this seriously, just attempting to explore the design space. > Some of the ideas are due to Toke. > > Zones and authoritative nameservers are announced over HNCP together with > their set of addresses, which SHOULD include a LUA and MUST include at > least one IPv6 address. There are two bits associated with each > authoritative nameserver: > > - default: set to 1 if the zone is suitable for name registration without > explicit user configuration; > - public: set to 1 if the zone is visible from the public internet. > > When a router joins the homenet, it MAY announce itself as the new > authoritative nameserver for a zone. It SHOULD do so if there is no > default public or private zone. > > If there are two default private zones or two default public zones, we > call an election, Highlander-style. If there are two authoritative > nameservers for the same zone, we call an election. > > There are no secondaries. If there are secondaries, their configuration > is outside the scope of this mail. > > Stateful DHCP servers SHOULD register their clients with the authoritative > nameserver for the default private zone using your favourite unicast > mechanism. Clients MAY register themselves with any zone currently > announced (they learn the server addresses through HNCP snooping or a from > new ND option, I don't care). > > mDNS proxying into the default private zone is allowed. Or recommended, > I'm not sure, only implementation experience will tell. > > Why exactly am I speaking nonsense? > > -- Juliusz > > _______________________________________________ > homenet mailing list > [email protected] > https://www.ietf.org/mailman/listinfo/homenet >
_______________________________________________ homenet mailing list [email protected] https://www.ietf.org/mailman/listinfo/homenet
