Re: [homenet] Support for RFC 7084 on shipping devices...

Ted Lemon <> Fri, 04 October 2019 13:06 UTC

Return-Path: <>
Received: from localhost (localhost []) by (Postfix) with ESMTP id 4E84412011E for <>; Fri, 4 Oct 2019 06:06:15 -0700 (PDT)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: -1.899
X-Spam-Status: No, score=-1.899 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: (amavisd-new); dkim=pass (2048-bit key)
Received: from ([]) by localhost ( []) (amavisd-new, port 10024) with ESMTP id 7OAA9BlQXrqf for <>; Fri, 4 Oct 2019 06:06:13 -0700 (PDT)
Received: from ( [IPv6:2607:f8b0:4864:20::534]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by (Postfix) with ESMTPS id 1491312011A for <>; Fri, 4 Oct 2019 06:06:13 -0700 (PDT)
Received: by with SMTP id q7so3711925pgi.12 for <>; Fri, 04 Oct 2019 06:06:13 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;; s=20150623; h=from:message-id:mime-version:subject:date:in-reply-to:cc:to :references; bh=mPSQWmPk5aVefE1U1btiiLPoffh7X/s8bwMs4r8tZu8=; b=SwDUb912uNjOc7OVNu2MOEfVUWgMXxWoyJlpWiLqCu0SUKRTng7vJwNf/faShAOX57 6vyJVCoKRQJeE27hKItTqd7GPj2/TKShDCPpSP+1T/ccptaBlVLztD2Mvzzy99MMgPoh RgzXTigZkdq3exl+kemjr8nP0v57oF72SSHBh8sAsysRLaM0AMY6QzhdGgdeDnS5nAc8 2KnAKYwZXc5h/en/J1k7JqTgSpHyyKf44o4jMCpclC+/ttaWd0BK/uIQWuk3/rULRyN/ 7YEPHgbh/ctbWjclNqVKOgyCR27bQ53z0KKHkDN0njBLUbvJSTbGIkkqsysERv14p3nS tZGw==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;; s=20161025; h=x-gm-message-state:from:message-id:mime-version:subject:date :in-reply-to:cc:to:references; bh=mPSQWmPk5aVefE1U1btiiLPoffh7X/s8bwMs4r8tZu8=; b=eIbCVlpKN2lVpu1uouO6COv7C0U4aaRZYNUAu716xTyw2tR7wykfTUYe6SvYrYM9gs SCmUd1KCkcI/AbfR6N72OyX4I467Cz4iPHccyb9QMcj0wqceMYT2/osm3ImkcRPuiwqa du9K2cCfbM+k0bH3a6HWGlrHf/MA74jIdRKagOwbd9bN9vhylMJONREwv3KLQnasnIm6 bmoIaCBazg227eyDfRCUN5ZZ3Q9qdWuFbuFt18ML9BM6iL4oz8Y4JUW+tDhAsvIFiOi+ 0bDeyDgwqah1WAAEjinV+dws/pFLe6xgXWhP7gPRmEjvOlLbrMv8vxvbKVpHstl5BQXw zJag==
X-Gm-Message-State: APjAAAUhKodjRTYLtGgfitSp2SJby7UuzUcZppVyIm1u259l5uR0CvxY 9rxS4hNxcBu9/XqwJeAVnwZ0Ge8CoiE=
X-Google-Smtp-Source: APXvYqyL6xnWYffPiYX4PSH7V6dSVjQ/qXddrg1/lqMOTBHMGTkSQr6NkRUviuAYvK15iBt9QWPTQg==
X-Received: by 2002:a62:7d81:: with SMTP id y123mr17214398pfc.133.1570194372399; Fri, 04 Oct 2019 06:06:12 -0700 (PDT)
Received: from [] ([]) by with ESMTPSA id s97sm7919059pjc.4.2019. (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Fri, 04 Oct 2019 06:06:10 -0700 (PDT)
From: Ted Lemon <>
Message-Id: <>
Content-Type: multipart/alternative; boundary="Apple-Mail=_6FE27B12-6E93-40D2-88D0-65310032DC42"
Mime-Version: 1.0 (Mac OS X Mail 13.0 \(3600\))
Date: Fri, 4 Oct 2019 06:06:09 -0700
In-Reply-To: <>
Cc: Mikael Abrahamsson <>, Markus Stenberg <>, 6MAN <>
To: Ole Troan <>
References: <> <> <> <>
X-Mailer: Apple Mail (2.3600)
Archived-At: <>
Subject: Re: [homenet] Support for RFC 7084 on shipping devices...
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: IETF Homenet WG mailing list <>
List-Unsubscribe: <>, <>
List-Archive: <>
List-Post: <>
List-Help: <>
List-Subscribe: <>, <>
X-List-Received-Date: Fri, 04 Oct 2019 13:06:15 -0000

On Oct 4, 2019, at 5:10 AM, Ole Troan <> wrote:
> Homenet has solved the problem of self-configuring networks in arbitrary topologies.

If that were true, I wouldn’t be asking this question.  We’re still chugging along, but we don’t have something that nay router vender could even consider shipping right now.  There isn’t enough participation in homenet anymore for us to really iron out the kinks.  Certainly if I could count o homenet being present in routers in the home, we wouldn’t be having this conversation! :)

> Unless someone goes to lengths describing exactly how this is supposed to work, the idea of "simplifying" the homenet solution sounds like a recipe for failure.

I tend to agree, but wasn’t proposing that.   I was really just trying to solve the very specific problem of how I do IPv6 routing in the case I described, given the hardware that is likely to be present in the home.

> How are you going to tell the customers that you can only plug in devices in particular topologies and in particular ways.

The customer already has a router.   Suppose I want to add a router with a bunch of devices behind it, and  I know the router I’m adding will never have a second layer behind it.   Can I get it to work?   That’s the problem.

> - single router and bridging (7084)

If it doesn’t filter RA, and I control the second router, I’m okay, right?

> - arbitrary topology plug and play (homenet)

Yes, that’s homenet.   It would really help if folks who think homenet is done would try to deploy it in their home using OpenWRT and see how it goes.   Seriously.   This is not a solved problem.   We’re maybe 50-60% of the way there at this point.   I’ve been trying to make progress on this ever since HNCP was declared done, and occasionally get collaboration, and indeed we may be begining to make progress agan, but we could definitely use more participation if there are folks in 6man who want this to work and imagine that it already does.

> - manually configured (meaning ansible, scripts or whatever automation solution external to the routers themselves).

Yech.   That’s not an option.  :]