On 3/1/19 2:25 PM, Ted Lemon wrote:
On Mar 1, 2019, at 4:21 PM, Stephen Farrell <[email protected]
<mailto:[email protected]>> wrote:
If one of those positions captures your opinion, feel free to respond
in shorthand. Otherwise, please tell us where you think we ought be
going, as a WG, with (a), (b) and/or (c).
For me it’s (1) and (2).
I think there are a few reasons why homenet feels stalled right now.
I would guess that even after 5 years, we still don't have much v6
deployment into homes and that's a pretty big problem. Router vendors
are not much motivated by that which doesn't have a market.
Sigh.
Mike
* We are tracking a moving target, and we haven’t adjusted our
goals. This is the conclusion I came to as a result of working
on the presentation I did in Bangkok on Homenet Marketing. I
don’t think this is bad.
* I conjecture that one of the reasons that there is good attendance
at homenet but relatively limited participation is in fact that we
are developing technology that is interesting to the people who
are showing up, but not quite addressing their needs.
* I don’t actually know what the applicability is for the hidden
primary stuff. I’ve gotten feedback that there are people who
want this, but I have no idea what to do with it, given that we
don’t want to expose internal DNS to external nodes.
* No hardware that does homenet. We have homenet stuff in OpenWRT,
but making it work in a home isn’t a turnkey operation, and that
is, after all, the goal of Homenet: a real network that sets
itself up without the user having to grok how it works.
* One of the applications of Homenet that we keep hearing about is
the SOHO market. We should target that explicitly and see what
gaps exist in addressing it.
So I think spending some time re-targeting would be worthwhile, and
it’s my intention to present a draft that talks about that in Prague.
I also would really like to see if anybody is willing to actually hack
on Homenet in the hackathon. There are a couple of projects I’d like
to see us work on:
* Turnkey homenet build of OpenWRT
* If the Turris folks are down, it would be nice if they could join
us and make it work in Turris OS as well.
* Homenet-wide service discovery using the DNSSD Discovery proxy
we’ve been working on, which is fully functional at this point.
* Support for DNSSD SRP (this would involve finishing the SRP
gateway I’ve been working on, and getting it to update Unbound or
BIND).
* Joining constrained-network edge routers to homenet routing and
service discovery infrastructure
* MUD support for devices that are not on a separate link, but are
isolated from nodes that don’t have permission to talk to them.
This should be doable in OpenWRT.
* Automatic IKEv2 tunnels on OpenWRT that use the new split DNS
stuff being published in IPSECME to allow us to serve home.arpa to
VPN clients.
This is an ambitious set of goals, and I don’t expect we’ll work on
all of them, but these are things that need work, so if there is
energy to work on any of them, it would be nice to see that happen at
hackathon.
_______________________________________________
homenet mailing list
[email protected]
https://www.ietf.org/mailman/listinfo/homenet
_______________________________________________
homenet mailing list
[email protected]
https://www.ietf.org/mailman/listinfo/homenet
