Esko Dijk <[email protected]> wrote: > 3) address of renewal server could be pushed into the device via a > higher-layer communication i.e. the application layer. This "push" > could happen at the moment that the device is requested to re-enroll > itself, in some application-specific way. There's currently no > standard protocol message defined AFAIK to trigger a client to start > the re-enrollment process.
It's probably a bug. BRSKI-AE could support a push, and I think that each of OPC UA, and MATTER also support a push operation. CoJP (RFC9031) includes a mechanism to rekey the network that is push. The problem/reason we have no push mechanism is that we (the IETF) don't really have a standard datamodel/interface-to-device, while other SDO verticals do. So adding a new push mechanism is not a big deal. -- Michael Richardson <[email protected]>, Sandelman Software Works -= IPv6 IoT consulting =- *I*LIKE*TRAINS*
signature.asc
Description: PGP signature
_______________________________________________ Anima mailing list [email protected] https://www.ietf.org/mailman/listinfo/anima
