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

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

Ted Lemon <[e-mail]> writes:

> Thanks for doing this! Did you come up with this on your own, or were
> inspired by
> https://tools.ietf.org/html/draft-lemon-homenet-naming-architecture-01
> section 3.4.2 and
> https://tools.ietf.org/html/draft-lemon-stateful-dnssd-00 section 4.2?

Well, I would by no means claim to have come up with the idea in a
vacuum. As I said, I have been following the naming discussions on this
list. I think I read the -00 of the naming architecture, but I have not
read the latest version, nor have I read the stateful-dnssd draft
before.

Looking at it now, what I have implemented looks like a hybrid of the
two halves of section 3.4.2. I.e., clients generate a KEY and use it to
sign updates, and they use that to remove records as well (i.e., there
is no support for unauthenticated updates in nsregd). But the records
are not permanent; the daemon will expire records that the client does
not maintain (since if a client drops off the network it has no way of
retiring its record).

> I ask both because I'm curious of you're proposing that the previous
> naming architecture document is more in line with what you think
> should be on a homenet, and also because I'm curious whether you are
> interested in working on the documents.

Hmm, well, I have first and foremost been trying to scratch my own itch
here. I was looking for something to replace dnsmasq's slaac address guessing
(https://tools.ietf.org/id/draft-taht-kelley-hunt-dhcpv4-to-slaac-naming-00.html),
and since no good solutions were forthcoming, I decided to roll my own.

That being said, I do believe this mechanism could be useful as part of
the homenet architecture, which is why I posted it here. And I wouldn't
mind spending some time fleshing out the mechanism and putting it into a
draft, if that is what you mean by "working on the documents"?

-Toke