Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Consider constrained devices and saving count_q and count_v regularly #14

Open
rikard-sics opened this issue Mar 1, 2022 · 3 comments

Comments

@rikard-sics
Copy link
Member

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

@rikard-sics
Copy link
Member Author

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

@rikard-sics
Copy link
Member Author

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

@rikard-sics
Copy link
Member Author

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 rikard-sics transferred this issue from core-wg/oscore-key-update Apr 7, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant