Re: [homenet] homenet: what now? ... next?

Michael Thomas <mike@mtcc.com> Fri, 01 March 2019 22:36 UTC

Return-Path: <mike@mtcc.com>
X-Original-To: homenet@ietfa.amsl.com
Delivered-To: homenet@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 31601130EE7 for <homenet@ietfa.amsl.com>; Fri, 1 Mar 2019 14:36:40 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.899
X-Spam-Level:
X-Spam-Status: No, score=-1.899 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id lqInrJcKKNZQ for <homenet@ietfa.amsl.com>; Fri, 1 Mar 2019 14:36:37 -0800 (PST)
Received: from mtcc.com (mtcc.com [50.0.18.224]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 5A219127AC2 for <homenet@ietf.org>; Fri, 1 Mar 2019 14:36:37 -0800 (PST)
Received: from Michaels-MacBook.local (170-75-133-42.volcanocom.com [170.75.133.42] (may be forged)) (authenticated bits=0) by mtcc.com (8.15.2/8.15.2/Debian-3) with ESMTPSA id x21MaYRl002050 (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128 verify=NO) for <homenet@ietf.org>; Fri, 1 Mar 2019 14:36:35 -0800
To: homenet@ietf.org
References: <894b4181-c4ca-5cf1-adba-1c5fcab0d355@cs.tcd.ie> <90A48EC1-C13D-4B9B-9F04-252C0CC87084@fugue.com>
From: Michael Thomas <mike@mtcc.com>
Message-ID: <dbe6e19f-84c2-f2eb-b9ab-d085de7c299c@mtcc.com>
Date: Fri, 01 Mar 2019 14:36:29 -0800
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.14; rv:60.0) Gecko/20100101 Thunderbird/60.5.0
MIME-Version: 1.0
In-Reply-To: <90A48EC1-C13D-4B9B-9F04-252C0CC87084@fugue.com>
Content-Type: multipart/alternative; boundary="------------BBDD5CB5FAC6492CBC8D96C4"
Content-Language: en-US
Archived-At: <https://mailarchive.ietf.org/arch/msg/homenet/YJ3OEVLBWe5PGHQNRW_fo4MEia0>
Subject: Re: [homenet] homenet: what now? ... next?
X-BeenThere: homenet@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: IETF Homenet WG mailing list <homenet.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/homenet>, <mailto:homenet-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/homenet/>
List-Post: <mailto:homenet@ietf.org>
List-Help: <mailto:homenet-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/homenet>, <mailto:homenet-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 01 Mar 2019 22:36:40 -0000

On 3/1/19 2:25 PM, Ted Lemon wrote:
> On Mar 1, 2019, at 4:21 PM, Stephen Farrell <stephen.farrell@cs.tcd.ie 
> <mailto:stephen.farrell@cs.tcd.ie>> 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
> homenet@ietf.org
> https://www.ietf.org/mailman/listinfo/homenet