IETF Logo Mail Archive

[homenet] standard way of configuring homenets

Michael Richardson <mcr+ietf@sandelman.ca> Tue, 24 July 2018 21:48 UTC

Return-Path: <mcr+ietf@sandelman.ca>
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 C6EC71311EB for <homenet@ietfa.amsl.com>; Tue, 24 Jul 2018 14:48:33 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.2
X-Spam-Level:
X-Spam-Status: No, score=-4.2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, 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 eXyHuEYoH6WY for <homenet@ietfa.amsl.com>; Tue, 24 Jul 2018 14:48:32 -0700 (PDT)
Received: from tuna.sandelman.ca (tuna.sandelman.ca [209.87.249.19]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id E9B23130F44 for <homenet@ietf.org>; Tue, 24 Jul 2018 14:48:31 -0700 (PDT)
Received: from sandelman.ca (obiwan.sandelman.ca [209.87.249.21]) by tuna.sandelman.ca (Postfix) with ESMTP id C09EE20090 for <homenet@ietf.org>; Tue, 24 Jul 2018 18:04:41 -0400 (EDT)
Received: by sandelman.ca (Postfix, from userid 179) id 4B45917FB; Tue, 24 Jul 2018 17:48:31 -0400 (EDT)
Received: from sandelman.ca (localhost [127.0.0.1]) by sandelman.ca (Postfix) with ESMTP id 481BB17F8 for <homenet@ietf.org>; Tue, 24 Jul 2018 17:48:31 -0400 (EDT)
From: Michael Richardson <mcr+ietf@sandelman.ca>
To: homenet <homenet@ietf.org>
X-Attribution: mcr
X-Mailer: MH-E 8.6; nmh 1.7+dev; GNU Emacs 24.5.1
X-Face: $\n1pF)h^`}$H>Hk{L"x@)JS7<%Az}5RyS@k9X%29-lHB$Ti.V>2bi.~ehC0; <'$9xN5Ub# z!G,p`nR&p7Fz@^UXIn156S8.~^@MJ*mMsD7=QFeq%AL4m<nPbLgmtKK-5dC@#:k
MIME-Version: 1.0
Content-Type: multipart/signed; boundary="=-=-="; micalg="pgp-sha1"; protocol="application/pgp-signature"
Date: Tue, 24 Jul 2018 17:48:31 -0400
Message-ID: <27765.1532468911@localhost>
Archived-At: <https://mailarchive.ietf.org/arch/msg/homenet/EBhUadQ4NwbpYIz3lYrwfow2YuY>
Subject: [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:48:34 -0000

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    [

v2.23.0 | Report a Bug | By Email