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

Sorry, it’s taking longer than I’d hoped. Will be done before deadline, probably later today. > On Jun 30, 2017, at 5:14 AM, Toke Høiland-Jørgensen wrote: > > Ping? ___ homenet mailing list homenet@ietf.org https://www.ietf.org/mailman/listinfo/home

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

> On 30 Jun 2017, at 10:14, Toke Høiland-Jørgensen wrote: > > Toke Høiland-Jørgensen writes: > >> Ted Lemon writes: >> >>> I think it would be worth presenting your work, yes. In addition to this, >>> I've >>> been working with Stuart Cheshire on an enhancement to the hybrid proxy >>> that

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

Toke Høiland-Jørgensen writes: > Ted Lemon writes: > >> I think it would be worth presenting your work, yes. In addition to this, >> I've >> been working with Stuart Cheshire on an enhancement to the hybrid proxy that >> I >> expect to present in Prague. It would be interesting to tie your wor

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

Ted Lemon writes: > I think it would be worth presenting your work, yes. In addition to this, I've > been working with Stuart Cheshire on an enhancement to the hybrid proxy that I > expect to present in Prague. It would be interesting to tie your work in with > that. I'm going to write up some in

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

I think it would be worth presenting your work, yes. In addition to this, I've been working with Stuart Cheshire on an enhancement to the hybrid proxy that I expect to present in Prague. It would be interesting to tie your work in with that. I'm going to write up some initial documents tha

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

Toke Høiland-Jørgensen writes: > Ted Lemon writes: > >> On Apr 17, 2017, at 3:16 PM, Toke Høiland-Jørgensen wrote: >> >> Hmm, turns out RFC6763 already defines a way to do this (in section 11). >> r._dns-sd._udp.. where is either the in-addr.arpa zone >> derived from the network address of

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

Ted Lemon writes: > On Apr 17, 2017, at 3:16 PM, Toke Høiland-Jørgensen wrote: > > Hmm, turns out RFC6763 already defines a way to do this (in section 11). > r._dns-sd._udp.. where is either the in-addr.arpa zone > derived from the network address of a host address, or "local.". I guess > I

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

On Apr 17, 2017, at 3:16 PM, Toke Høiland-Jørgensen wrote: > Hmm, turns out RFC6763 already defines a way to do this (in section 11). > r._dns-sd._udp.. where is either the in-addr.arpa zone > derived from the network address of a host address, or "local.". I guess > I'll teach the nsregc client

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

Toke Høiland-Jørgensen writes: >> Or put it in DNS under dot-home? Since the client already knows how to >> speak DNS, this avoids yet another coupling between protocols. > > Ah yes, that makes sense; since we have a domain that always refers to > the homenet, just define a name under that that w

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

Juliusz Chroboczek writes: >> In the current implementation, a single daemon per registration zone. > > Right. Either it could be elected by HNCP, or the daemons could run an > election among themselves. Yeah, this makes sense if this mechanism is also used inside the homenet (to register under

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

Andrew Sullivan writes: > I really like this idea. Thanks! > Obviously, it's the sort of thing whose scope had better be pretty > limited (e.g. you better know what network those TOFU requests are > coming from), but apart from that it seems quite useful. Yeah. The daemon will only allow new r

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

> In the current implementation, a single daemon per registration zone. Right. Either it could be elected by HNCP, or the daemons could run an election among themselves. > The client will query for a SRV at _nsreg._tcp. to find the > daemon, which can be anywhere, in principle (the daemon will o

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

I really like this idea. Obviously, it's the sort of thing whose scope had better be pretty limited (e.g. you better know what network those TOFU requests are coming from), but apart from that it seems quite useful. A On Fri, Apr 14, 2017 at 02:38:46AM +0200, Toke Høiland-Jørgensen wrote: > Hey

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

Juliusz Chroboczek 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 >

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

Simple and elegant, solves a real problem without too much ideology. > This daemon will allow a client to claim a name on a Trust On First Use > (TOFU) basis Cool. > 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

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

Ted Lemon 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

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

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-

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

Hey everyone While following the naming discussions, I have been thinking about how to do one of the things that the current naming architecture draft excludes: Allowing devices on the homenet to register in (public) DNS so that one may find them. And since I also wanted to learn the Go programmin