Re: [Anima-bootstrap] anima-bootstrap: Bootstrap proxy discovery options

[Michael Richardson <[e-mail]>]

Toerless Eckert (eckert) <[e-mail]> wrote:
    > Lets assume we replace EST bootstraap with "a guy with a USB stick feeding
    > manually domain certs to greenfield devices".

Yes, I've no problem with that.

    > a) I agree that we would want to make sure our protocols are set up so that even such
    > a device could perfectly bring up ACP afterwards and continue with the rest
    > of autonomic functions (GRASP inside ACP, agents,...).

I don't see a problem here.

    > b) I don't think we would want to call such a device "autonomic". It's partial
    > autonomic at best. But yes, it may be perfectly valid and relevant to some
    > industries.

It's part of the ACP, and it could participate in lots of self-healing
efforts.  So, it's autonomic.   What it isn't is *zero-touch*.

    > If you agree, then the problem is IMHO primarily in the reference model calling
    > out that devices that for one reason or the other can not / want-not implement
    > the whole ANIMA suite can perfectly well implement just parts of it, because
    > ANIMA is defined such that the different building blocks are modular. Just that
    > such a device is only "partial-autonomic" (or  whatever you think is a good
    > naming to distinguish it from a truely autonomic device).

    > Btw: This also goes the other way, eg: it would IHO make sense that the bootstrap
    > spec can be deplpoyed on devices that do not want any further AN functions after
    > the certificates are enrolled. I think that option is also something we want to
    > explain in the bootstrap draft.

Yes.  That's how I view IoT devices (such as in the 6tisch space) --- they
will do much of the bootstrap mechanism, but they won't build an ACP, and
won't run GRASP.

Perhaps, ditto HomeNet devices.


--
Michael Richardson <[e-mail]>, Sandelman Software Works
 -= IPv6 IoT consulting =-