Alan DeKok <al...@deployingradius.com> wrote:
> I would split this up into:
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.
> bootstrapping - starting from nothing, or almost nothing, how does a
> device get on the network, and get a minimal configuration enabled?
> provisioning - how does a device with some existing network access /
> configuration get onto a new network, perhaps with a new identity?
The term "onboarding" is now used for this step.
(Yes, BRSKI gets it wrong)
I'm a bit unclear about how these steps differ.
The term "provisioning" has come to mean when the "almost nothing" is
provided to the device in the factory. That's come to mean an IDevID, but it
can also mean an (e)SIM, or other long-term shared secret.
The term "commissioning" has come to mean provisioning + configuration.
That is, the device is recognized, it is joined to the network, and it might
be told what it's role in the Superbowl 3000-drone display is.
> reconfiguration - how does a device with an existing configuration
> update it? When / where / why / how?
Why is this step different than configuration?
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.
--
Michael Richardson <mcr+i...@sandelman.ca>, Sandelman Software Works
-= IPv6 IoT consulting =-
signature.asc
Description: PGP signature
_______________________________________________ Emu mailing list Emu@ietf.org https://www.ietf.org/mailman/listinfo/emu
