On Mar 26, 2022, at 11:57 AM, Michael Richardson <mcr+i...@sandelman.ca> wrote: > I'm gonna quibble with your choice of terms, because there has been some > progress/convergence in the terminology. This is good news, because sharing > terminology is an important leap forward.
That's good. >> reconfiguration - how does a device with an existing configuration >> update it? When / where / why / how? > > Why is this step different than configuration? I put that in, in part because of EAP-CREDS. In part because I'm not sure that updates fall within the bounds of provisioning / onboarding. i.e. I already have something, and I can get onto the network. How often do I refresh those credentials? What happens if my authorization changes? How do I get told if my credentials are withdrawn? Perhaps this could better be described as policies and signalling for refresh and updates of provisioned data. The act of doing the update is just provisioning. Knowing when / where / how / why to do that update isn't quite part of the provisioning process. > There is a plan to unify/contrast the terminology in section 4 of: > draft-irtf-t2trg-secure-bootstrapping/ > > but that section hasn't happened yet. I saw that. :( Alan DeKok. _______________________________________________ Emu mailing list Emu@ietf.org https://www.ietf.org/mailman/listinfo/emu
