Brian E Carpenter <[email protected]> wrote:
    > I *really* don't understand this stuff, but how long could the rollover
    > take, for a reasonably large IoT network (presumably thousands of
    > devices)? Are we talking about a few seconds when no new sessions could
    > start, or what?

For sleepy IoT devices that wake up once a day, and run on a slow network?
Could be a few weeks, easily.

But, on such networks, the devices mostly don't talk to each other at all.

Industrial situations like factories aren't doing a lot of device2device
communication (i.e. without involving the control system), but if they did,
then they'd want to schedule the certificate renewal/rollover at a specific 
time.

I think that we could do this by issuing new certificates with a notBefore
date in the future, but to date, I don't think we have a clear specification
that says this.

--
Michael Richardson <[email protected]>   . o O ( IPv6 IøT consulting )
           Sandelman Software Works Inc, Ottawa and Worldwide




Attachment: signature.asc
Description: PGP signature

_______________________________________________
Anima mailing list
[email protected]
https://www.ietf.org/mailman/listinfo/anima

Reply via email to