Michael, Reviving the discussion on the rekeying mechanism. See below.
Mališa >> On Sat, Mar 24, 2018 at 11:36 PM, Michael Richardson < >> [email protected]> wrote: >> >>> >>> >>> I'd say that you always do this with any new key if you have no keys. >>> I don't think we need a flag. >>> >>> In fact, even for the "0th key", you would start using it as soon as you >>> see >>> something that passes with that key, such as authenticating the Beacon >>> that >>> you used to find the Proxy in the first place.... >>> >> Authenticating a beacon that was received long time ago would require the pledge to store the beacon(s) for potentially an extensive period... I don't think we need to do that. But, you are right, we do not need a flag in the response, just to specify the special handling for different roles: Essentially: - 6LBR: installs the new key, starts using it for outgoing traffic *immediately*, removing old keys, if any. - joined node and pledge: installs the new key, keeps using the old keys for outgoing traffic until it receives incoming traffic secured with the new key, with all L2 security checks passed. In the special case of a pledge, there shouldn't be any outgoing traffic before it decrypts DIO(s) and selects a preferred parent.
_______________________________________________ 6tisch mailing list [email protected] https://www.ietf.org/mailman/listinfo/6tisch
