Re: [homenet] standard way of configuring homenets

On 25/07/2018 14:59, STARK, BARBARA H wrote:
> <individual hat> Since homenet is supposed to be about an unmanaged network, and configuration via a management protocol requires somebody who knows what they’re doing, 

Traditionally, yes, but we do actually want to get away from that.
(It's our explicit goal to do that in ANIMA, for which homenets are
out of scope, but we assume that the starting point is a NOC staffed
by people who know what they are doing.)

The idea of capturing a homenet config and saving it for future use
doesn't seem outlandish to me, and using tools developed for
managed networks, but operated robotically instead of manually, doesn't
seem crazy either. But it might be a big effort and a distraction.

   Brian

> it doesn’t fall within my interpretation of the charter.
> Barbara
> 
> From: homenet <homenet-bounces@ietf.org> On Behalf Of Ted Lemon
> Sent: Tuesday, July 24, 2018 5:57 PM
> To: Michael Richardson <mcr+ietf@sandelman.ca>
> Cc: homenet <homenet@ietf.org>
> Subject: Re: [homenet] standard way of configuring homenets
> 
> 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<mailto: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<mailto:mcr@sandelman.ca>  http://www.sandelman.ca/<https://urldefense.proofpoint.com/v2/url?u=http-3A__www.sandelman.ca_&d=DwMFaQ&c=LFYZ-o9_HUMeMTSQicvjIg&r=LoGzhC-8sc8SY8Tq4vrfog&m=uuWiihYmTZHdlSwLjIDnf8fDYcahci1jFrEDQVRDWBM&s=frhxrsM8yiLM3JkOyRI0HavzzN3k4XrwesIkggWuR0E&e=>        |   ruby on rails    [
> 
> 
> 
> _______________________________________________
> homenet mailing list
> homenet@ietf.org<mailto:homenet@ietf.org>
> https://www.ietf.org/mailman/listinfo/homenet<https://urldefense.proofpoint.com/v2/url?u=https-3A__www.ietf.org_mailman_listinfo_homenet&d=DwMFaQ&c=LFYZ-o9_HUMeMTSQicvjIg&r=LoGzhC-8sc8SY8Tq4vrfog&m=uuWiihYmTZHdlSwLjIDnf8fDYcahci1jFrEDQVRDWBM&s=XnYMQ-A87X4UomP-wRjfJITHsZ87UoWghSpiPrGTNy8&e=>
> 
> 
> 
> _______________________________________________
> homenet mailing list
> homenet@ietf.org
> https://www.ietf.org/mailman/listinfo/homenet
> 