-
Notifications
You must be signed in to change notification settings - Fork 0
Issues: core-wg/oscore-key-limits
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
Author
Label
Projects
Milestones
Assignee
Sort
Issues list
Reduce scope of the limits section and point more to the CFRG document?
cfrg-aead-limits
#1
opened Jul 27, 2022 by
rikard-sics
Latest feedback from John on the limits and probabilities
limits
#2
opened Mar 1, 2022 by
rikard-sics
Update content to reflect new version of draft-irtf-cfrg-aead-limits
cfrg-aead-limits
#5
opened Mar 1, 2022 by
rikard-sics
Redefine 'l', 'limit_q', and 'limit_v' specifically for OSCORE
limits
#8
opened Mar 1, 2022 by
rikard-sics
How do the q & v limits and the chosen 'l' affect applications?
limits
#9
opened Mar 1, 2022 by
rikard-sics
Consider different probabilities p_q and p_v for OSCORE specifically?
limits
#11
opened Mar 1, 2022 by
rikard-sics
Each client can count q up to half(?) the q limit as an optimization
optimization
#12
opened Mar 1, 2022 by
rikard-sics
Consider raising adding q and v limits already in COSE registry with the algorithms
limits
#13
opened Mar 1, 2022 by
rikard-sics
Consider constrained devices and saving count_q and count_v regularly
optimization
#14
opened Mar 1, 2022 by
rikard-sics
ProTip!
Mix and match filters to narrow down what you’re looking for.