Re: [homenet] A TOFU approach to naming things in the homenet (with code!)

[Toke Høiland-Jørgensen <[e-mail]>]

Juliusz Chroboczek <[e-mail]> writes:

> Simple and elegant, solves a real problem without too much ideology.

Thank you! That is high praise, coming from you :)

>> If the name in a claim is not already taken by another nclient, the
>> client's claim will be successful and the daemon will cache the public
>> key and use it to verify subsequent update requests.
>
> Does this imply there's a single daemon in the Homenet?  How does the
> network elect it in case there are multiple claimants?  How does the
> client learn the address of the daemon?

In the current implementation, a single daemon per registration zone.
The client will query for a SRV at _nsreg._tcp.<zone> to find the
daemon, which can be anywhere, in principle (the daemon will only speak
TCP and limits initial registration to a list of configured subnets; I'm
currently running mine on a separate server rather than on my router).
For the multi-homed homenet case, I suppose each uplink could have a
separate zone?

I punted somewhat on how to discover the zone; the client will currently
take it as a command line parameter. But figure that can be distributed
via DHCP/RA?

In principle, there's nothing preventing the daemon state from being
replicated across the homenet routers, I suppose...

-Toke