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

Ted Lemon <mellon@fugue.com> Fri, 01 March 2019 22:25 UTC

Return-Path: <mellon@fugue.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 CF952130EE6 for <homenet@ietfa.amsl.com>; Fri, 1 Mar 2019 14:25:34 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.9
X-Spam-Level:
X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIMWL_WL_MED=-0.001, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=fugue-com.20150623.gappssmtp.com
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 BC3_xKRdBVKe for <homenet@ietfa.amsl.com>; Fri, 1 Mar 2019 14:25:32 -0800 (PST)
Received: from mail-qk1-x729.google.com (mail-qk1-x729.google.com [IPv6:2607:f8b0:4864:20::729]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 603FE130EE1 for <homenet@ietf.org>; Fri, 1 Mar 2019 14:25:29 -0800 (PST)
Received: by mail-qk1-x729.google.com with SMTP id y140so15282542qkb.9 for <homenet@ietf.org>; Fri, 01 Mar 2019 14:25:29 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=fugue-com.20150623.gappssmtp.com; s=20150623; h=from:message-id:mime-version:subject:date:in-reply-to:cc:to :references; bh=kL2qcIAuRjkKLzo8Mo1stRR4SW31Lj616QdGKWPqKIo=; b=cnPY9SRg5uL74AF0xLvaRSQHJ5F4XLpX4Ta6wQvb7RYbkUVtrd8HS3f4zc7vtrhTCp CzneC6SNQIBtCbD8bcbnakSOL38fJul69rlJ9DqypKMR4kqxtJL4Ygvh33OOAME6WZZQ C92rVdDitUTub0FIM6PNC+QFFzJOdSluQ56ApHybv5epPIkpBpGxGlBlDtHVvkNT1LKM KPpbF1wCN3IASZy2DbO6lWMmbSKNH58vv5yQPa2V1SqUQanwh2pUxdPhDb98xct0VRaE MdptJoTfAqWfC+JkjBFTbwD+UFgl/KdVyofkzmFTQN+iRLZA4sbCEklPe4hJfN3y1OMq 6p5g==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:from:message-id:mime-version:subject:date :in-reply-to:cc:to:references; bh=kL2qcIAuRjkKLzo8Mo1stRR4SW31Lj616QdGKWPqKIo=; b=LAn7bwc+msC4fJuKKjDVKz/0AcNOzB7NzhEnzSjJ8RIOHPHV/ctQvhQYQE/Yer1ib6 mYmGryhrcBhJMoSwIFzH9WozbsNHWJBRbV6IfUT01ocHEQfx4fOgg3g9PQx7wiDK8TLZ j6OcneE27vzIFONNP6Q7naq0iAvZl+7HCu6ZvJP/QKp7OMObExge+uZOq7T+XcQ/aFcE u2bqTgxSn2Rcmmi6BPMmhRgDpQGLBvp274DreXFKz/PC2ygdKEe61o45/kh/BwS27ZRw pOB+WVBo5F4urMWdO+35VneIGdHDrvxGQQeKsvjKhrGDuXkq9+EKZkSCvrSnRJSOGTsd vLvg==
X-Gm-Message-State: APjAAAWHfrpZQC6ViB/OnJM6HwrDKe84q0Eu6xNNO3epPPsTEGhVx/3y rydvGFIMKJuPuZTSgdn/ta763Rl+RmDntw==
X-Google-Smtp-Source: APXvYqy+WqZeXVBSMD3Zrt+GwT0aJ/7/4Qpiz/iWRX8hQ9O4Zx1AbE81t7oFVkhWJfGlWMa86FzTsw==
X-Received: by 2002:a37:4ec2:: with SMTP id c185mr5847854qkb.244.1551479128050; Fri, 01 Mar 2019 14:25:28 -0800 (PST)
Received: from [10.0.100.12] (c-73-186-137-119.hsd1.ma.comcast.net. [73.186.137.119]) by smtp.gmail.com with ESMTPSA id r9sm10257485qkl.1.2019.03.01.14.25.26 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Fri, 01 Mar 2019 14:25:27 -0800 (PST)
From: Ted Lemon <mellon@fugue.com>
Message-Id: <90A48EC1-C13D-4B9B-9F04-252C0CC87084@fugue.com>
Content-Type: multipart/alternative; boundary="Apple-Mail=_6BAB4F6B-4167-43AD-95E8-DCC56BB068BF"
Mime-Version: 1.0 (Mac OS X Mail 12.4 \(3445.104.2\))
Date: Fri, 01 Mar 2019 17:25:25 -0500
In-Reply-To: <894b4181-c4ca-5cf1-adba-1c5fcab0d355@cs.tcd.ie>
Cc: "homenet@ietf.org" <homenet@ietf.org>
To: Stephen Farrell <stephen.farrell@cs.tcd.ie>
References: <894b4181-c4ca-5cf1-adba-1c5fcab0d355@cs.tcd.ie>
X-Mailer: Apple Mail (2.3445.104.2)
Archived-At: <https://mailarchive.ietf.org/arch/msg/homenet/Hytpd7oj1TLJ2EcQ9BRHCTBqpZE>
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:25:35 -0000

On Mar 1, 2019, at 4:21 PM, Stephen Farrell <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.

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.