> STARK, BARBARA H <[email protected]> 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, it doesn’t fall within my interpretation > > of the charter. > > I don't think that management requires somebody who knows what they > they are doing... :-) > > I'm thinking along the lines of being able to *backup* the configuration and > restore it. You may be right that it's out of charter regardless. > > I think that the developers of homenet products need to be able to get > telemetry about what went wrong: so at the least, *we* need to be able to > debug what went wrong.
I think we could do something for config backup (and restoration) and supplying logs and statistics in a way that would not give me the heebie-jeebies (by enabling a fully-functional management interface). I still really like NetJSON (netjson.org) as a mechanism for supplying read-only statistics, logs, and config info. I think if we creating some custom NetJSON modules and getting a DNS-SD service name would be really simple and pretty flexible. For backup, I think a device could create, name, and encrypt its own backup file, and would just need some place to put it. That backup store wouldn't need to be able to log into the device, otherwise configure the device, or be responsible for pulling these backups. Barbara _______________________________________________ homenet mailing list [email protected] https://www.ietf.org/mailman/listinfo/homenet
