search

core-wg / oscore-key-limits

Other
0 stars 0 forks source link

Consider constrained devices and saving count_q and count_v regularly #14

Closed rikard-sics closed 1 month ago

rikard-sics commented 2 years ago

How often must they be stored? Consider Appendix B.1 and saving the SSN.

rikard-sics commented 2 years ago

See Appendix B.1 for OSCORE: https://tools.ietf.org/html/rfc8613#appendix-B.1

rikard-sics commented 2 years ago

This can wait until issue "Each client can count q up to half(?) the q limit as an optimization" is closed.

rikard-sics commented 2 years ago

Explore further the idea from Carsten mentioned during the CoRE interim on April 28. This was about utilizing the clock (on devices which have one) to not have to save count_q and count_v in some situations.

We can also clarify that saving the counters every N is just a suggestion for implementers. Different solutions may be acceptable. The key point is making sure to not lose or underestimate the counters after reboot (while overestimating them can be fine to some extent).

rikard-sics commented 1 month ago

Summarized and added in new issue about optimizations: https://github.com/core-wg/oscore-key-limits/issues/19