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

Ted Lemon <mellon@fugue.com> Sun, 06 October 2019 23:22 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 EDA941200D8 for <homenet@ietfa.amsl.com>; Sun, 6 Oct 2019 16:22:50 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.898
X-Spam-Level:
X-Spam-Status: No, score=-1.898 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, HTML_MESSAGE=0.001, MIME_QP_LONG_LINE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_HELO_NONE=0.001, SPF_PASS=-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 jqPcqgKbmJQr for <homenet@ietfa.amsl.com>; Sun, 6 Oct 2019 16:22:49 -0700 (PDT)
Received: from mail-ot1-x343.google.com (mail-ot1-x343.google.com [IPv6:2607:f8b0:4864:20::343]) (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 2A26A120025 for <homenet@ietf.org>; Sun, 6 Oct 2019 16:22:49 -0700 (PDT)
Received: by mail-ot1-x343.google.com with SMTP id 67so9506823oto.3 for <homenet@ietf.org>; Sun, 06 Oct 2019 16:22:49 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=fugue-com.20150623.gappssmtp.com; s=20150623; h=content-transfer-encoding:from:mime-version:subject:date:message-id :references:cc:in-reply-to:to; bh=U1UYf59ta5hoPK8banjMoGKTW3QZ5zQfA+gS4XYfyhY=; b=Y24K3qewqSbQLMwmhlLAWb5yVBsYLwpHjmD0ldPl3zVI86rXg+zD7f8z2dDA9i2sE/ MbZ5hkfQcYqZUQzDrkZH4eLjgPm64Er0A1Bs2VgJhvdshcb5gT8WRJsW13QYlzpvOwgC 8l2v1ivtxMPuMPvtJj2JUf8+r6Qz2TN3zOE+olYexK2ljMdwNSj0qx/3+kWsNItf9JPC jmJ+ym0cREHyu+mtHM2VHDlkL9HCwbCSP9fQNfm7T6zplTi5knTqZApUyBZn0vPAs0mT /jWvNHF+W4qdZ6ZFRB0eX/u9wTPU9EWVaTTUg6l4lfbK2XRZ0lSk4tIeetVCei6zXQmP wxyQ==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:content-transfer-encoding:from:mime-version :subject:date:message-id:references:cc:in-reply-to:to; bh=U1UYf59ta5hoPK8banjMoGKTW3QZ5zQfA+gS4XYfyhY=; b=aXEQxg5r5tUjXF0Pp26klWzZ9VyuqIHpdQgIt1I1TnYgVcRDiryKV3lcGXRYsCK9x5 c4wUs9rLHM/T3DYL+JRAFjcqY5Ehk0I1qeC4F2YOHOQSXQz3gyCMok9TSesr1nRvTsXi itA7hzzJFnyk70MlmGn8wiRq2Ppp2Wify6x9YvN0ZBBQBDlRfsTpCSauQkNfvcWHkENJ qCwRyvhzu2h3aUr57C2SeA4gE/Dsa7pk+8brBHl8XpsrNUosPPgNT81PdtqIQr7iGjl5 sAJIOlsOy82GBsnpOtlpk7bP+yc8LvLV3CXRcvGlRfpg8q7/f7Jgy3TNqv2Ac8b0FUyC 35nw==
X-Gm-Message-State: APjAAAU/+V97nyykVApjIMbqXFKOF//Hv6gUtgk6YBjujJMDt9odNMYS mk6LPz8HHtbsHzLClgjwXsc2JaYvRtA=
X-Google-Smtp-Source: APXvYqxQN36Cq+8310wEYk6NkpVPNy56V1jGsryUTuMndEeOART/Umf4VrAwsag1wLTco54Iq8ZoTg==
X-Received: by 2002:a9d:4102:: with SMTP id o2mr19446171ote.187.1570404168314; Sun, 06 Oct 2019 16:22:48 -0700 (PDT)
Received: from [10.10.9.27] (cpe-24-243-152-218.rgv.res.rr.com. [24.243.152.218]) by smtp.gmail.com with ESMTPSA id h5sm3974570oth.29.2019.10.06.16.22.46 (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128); Sun, 06 Oct 2019 16:22:47 -0700 (PDT)
Content-Type: multipart/alternative; boundary=Apple-Mail-E0F1BC47-27DC-41E6-AACB-0114B6B40264
Content-Transfer-Encoding: 7bit
From: Ted Lemon <mellon@fugue.com>
Mime-Version: 1.0 (1.0)
Date: Sun, 6 Oct 2019 18:22:46 -0500
Message-Id: <E7A948E0-F4E0-4008-B245-C516075D8928@fugue.com>
References: <79ca7111-8701-bb3e-58db-0688da8311b9@mtcc.com>
Cc: homenet@ietf.org
In-Reply-To: <79ca7111-8701-bb3e-58db-0688da8311b9@mtcc.com>
To: Michael Thomas <mike@mtcc.com>
X-Mailer: iPhone Mail (17A850)
Archived-At: <https://mailarchive.ietf.org/arch/msg/homenet/q74i1Ta7qneOoN0oJGdQ4KcNPE8>
Subject: Re: [homenet] Support for RFC 7084 on shipping devices...
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: Sun, 06 Oct 2019 23:22:51 -0000

On Oct 6, 2019, at 17:46, Michael Thomas <mike@mtcc.com> wrote:
> If the protocol is not truly plug and play in reality... wasn't that the entire premise? That doesn't sound like an ops problem. I understand that openwrt is a wonk box, but still if there isn't default configuration that would make it truly plug and play for most situations, that sounds really problematic.
> Can you confirm or not that openwrt could be set up by default in a way that met the charter's requirements for operations (ie, like what you might expect in a commercial home router)?
> 

I think it can be, but the openwrt work never went that far.  We’re working on it again now, but even if we get it working nicely in openwrt, that doesn’t get it to where I can assume it will be working on some arbitrary home network anytime in the next five years.