search

core-wg / oscore-key-update

Other
0 stars 0 forks source link

Must be able to keep track of used IDs for being able to use the ID update method #47

Closed rikard-sics closed 1 year ago

rikard-sics commented 1 year ago

For how long / to which event do you need to remember the IDs?

For standalone ID update: Abort an ID update happening if you or the other peer are going to get the same ID used before by you or the other peer.

Before running KUDOS check the size of the list of saved IDs, if it is longer than your own and the other peers (meaning 2), do not preserver the observations. If you run KUDOS you can clean up the list of IDs (regardless of updating IDs or not at the same time), install the current IDs (your and the other peer's).

The idea is to prioritize being able to perform ID update over preservation of observations.

rikard-sics commented 1 year ago

The list of IDs can never be cleared unless the context is destroyed, or e.g. KUDOS or EDHOC is ran.

rikard-sics commented 1 year ago

If the list of IDs is full, the peer needs to update ID, and KUDOS is not supported: Destroy the context.

Any other case, don't update your ID and reject if the other party wants to update ID.

rikard-sics commented 1 year ago

Never reuse ID for same Master Secret/Master Salt/ID Context.

rikard-sics commented 1 year ago

We discussed further and can close this issue.

Text about keeping old ideas was already added in the draft. The other points in this issue seem fine after discussion.