IETF Logo Mail Archive

Re: [homenet] standard way of configuring homenets

Ted Lemon <mellon@fugue.com> Tue, 24 July 2018 21:57 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 CD95F130F88 for <homenet@ietfa.amsl.com>; Tue, 24 Jul 2018 14:57:26 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.909
X-Spam-Level:
X-Spam-Status: No, score=-1.909 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_PASS=-0.001, T_DKIMWL_WL_MED=-0.01, 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 oF2FTivsLSPS for <homenet@ietfa.amsl.com>; Tue, 24 Jul 2018 14:57:24 -0700 (PDT)
Received: from mail-it0-x22e.google.com (mail-it0-x22e.google.com [IPv6:2607:f8b0:4001:c0b::22e]) (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 857DC130F3A for <homenet@ietf.org>; Tue, 24 Jul 2018 14:57:24 -0700 (PDT)
Received: by mail-it0-x22e.google.com with SMTP id 72-v6so5929368itw.3 for <homenet@ietf.org>; Tue, 24 Jul 2018 14:57:24 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=fugue-com.20150623.gappssmtp.com; s=20150623; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=BuXdgHAodwO+ffiLR+Ti3BW0V4Fwh+ucFDv6LEOs/4k=; b=G88eUZLBew9IGO0RpQKAQ8fIdGMnglebce9Ep57W3UGjDO2xk+lQYK9cP2O4AF26iC KrOhGYFrB2oDUftF/3C0m5msltnwYa49aiicrQnfPC+qnVwQMK6N7Dr9K2qhWTimX3Qb trPFWK1ltyW8QX34CWwh/wH5cirzcy6SeNWkipxl1ROoYqJFfVwYZVGC0/D+V4UyKbV2 RkRdgfAxLrwZQmUbOw7sjAhWwpsa6Lfi626JFmbrZFDjFCDCwVTL9CYpVVDFKBIfp1vb taEXJQtTusX3NkXd+/w+zLV9UOywFWHavgBZJgS77VgUqKiKKeDU3Kk3iR6j6sAMjXwS UMLw==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc; bh=BuXdgHAodwO+ffiLR+Ti3BW0V4Fwh+ucFDv6LEOs/4k=; b=Ap7r4TriSfNAwoARz24zmA1qdFIi9J6TL1UJMe1hRxW4UXkvChaNytCzzVlOtGqg5g WUyNvXdEwV+snN0j32Me07NgVFs8/sl0LQ8wXZAjlhYczMuKWYo/UwtXYoI4wdNdOe/3 qZ2s5aaHGMjIH7Rpj3HhGc5l7ZuKDxh9udfrbLRDmnfB72/YjIvvilfn40qoHMuoXM79 J8iCDUQ9GhosiUJmL2OlX1X+suqiSjYTktS1lSvHSp1XfbaTEGd/v+EwV8+7TkVkEYW6 77SqX/F7cyZ4D/NJ4gzF673UIYnCSGOrFbwYE+zZdNUpMHsb28UGqFcpPJYTEeTrFcK5 RYlg==
X-Gm-Message-State: AOUpUlHdi/X+LRFKvmqELc7M1sM147QCn1smLsmUx+LxPo7tv+kZRwP6 iO1fsK0DYm2NK/dJBEt+67EuLbcNJqH25usJolWkxdXf
X-Google-Smtp-Source: AAOMgpe8fvaBKht1T6gSoxswJDXVMJkRGpYpyvWun8e6OBiPD6eEnLRNkqSs3wRm3l4fF1F1nZadYUN+7QBnLUdPrrA=
X-Received: by 2002:a02:b70b:: with SMTP id g11-v6mr17705746jam.34.1532469443705; Tue, 24 Jul 2018 14:57:23 -0700 (PDT)
MIME-Version: 1.0
Received: by 2002:a4f:b442:0:0:0:0:0 with HTTP; Tue, 24 Jul 2018 14:56:43 -0700 (PDT)
In-Reply-To: <27765.1532468911@localhost>
References: <27765.1532468911@localhost>
From: Ted Lemon <mellon@fugue.com>
Date: Tue, 24 Jul 2018 17:56:43 -0400
Message-ID: <CAPt1N1mO8KFH+M-bq7LKqQcjtyigUPwdchMA11U_vPXYTzcNSw@mail.gmail.com>
To: Michael Richardson <mcr+ietf@sandelman.ca>
Cc: homenet <homenet@ietf.org>
Content-Type: multipart/alternative; boundary="000000000000d2536d0571c5d875"
Archived-At: <https://mailarchive.ietf.org/arch/msg/homenet/aQ2pCxmOe0xMNECn2x2tQVbUFAk>
Subject: Re: [homenet] standard way of configuring homenets
X-BeenThere: homenet@ietf.org
X-Mailman-Version: 2.1.27
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: Tue, 24 Jul 2018 21:57:27 -0000

I don't think using HNCP in that particular way is a great plan, but I'm
willing to be convinced.   I would hope that this is in charter.

On Tue, Jul 24, 2018 at 5:48 PM, Michael Richardson <mcr+ietf@sandelman.ca>
wrote:

>
> I very much like the idea of having a standard way to configure homenets.
> There is the YANG/NETCONF method, and I think that we should go in that
> direction.
>
> A thought I had though.... could a HOMENET configuration be recorded by
> capturing just HNCP traffic?  Could a network configuration be restored
> by essentially playing back that stuff?  I'm pretty sure that this won't
> work, but the question is... should it?
>
> Does this work fit into the charter?
>
> --
> ]               Never tell me the odds!                 | ipv6 mesh
> networks [
> ]   Michael Richardson, Sandelman Software Works        | network
> architect  [
> ]     mcr@sandelman.ca  http://www.sandelman.ca/        |   ruby on
> rails    [
>
>
>
> _______________________________________________
> homenet mailing list
> homenet@ietf.org
> https://www.ietf.org/mailman/listinfo/homenet
>
>

v2.23.0 | Report a Bug | By Email