issues
search
core-wg
/
oscore-key-limits
Other
0
stars
0
forks
source link
issues
Newest
Newest
Most commented
Recently updated
Oldest
Least commented
Least recently updated
Make informational?
#17
rikard-sics
opened
1 year ago
0
Recommend lifetime for a Security Context?
#16
rikard-sics
opened
1 year ago
0
Reduce scope of the limits section and point more to the CFRG document?
#1
rikard-sics
opened
2 years ago
0
Latest feedback from John on the limits and probabilities
#2
rikard-sics
opened
2 years ago
1
Add note on relevance of 'l' limit
#3
rikard-sics
closed
1 year ago
0
Using clock instead of saving counters
#4
rikard-sics
opened
2 years ago
1
Update content to reflect new version of draft-irtf-cfrg-aead-limits
#5
rikard-sics
opened
2 years ago
6
Say in OSCORE Messages Processing to not send a message with COSE plaintext + MAC + possible padding larger than block size * l
#6
rikard-sics
closed
1 year ago
5
Explain exceptions where l needs to be larger than 2^8
#7
rikard-sics
closed
1 year ago
1
Redefine 'l', 'limit_q', and 'limit_v' specifically for OSCORE
#8
rikard-sics
opened
2 years ago
2
How do the q & v limits and the chosen 'l' affect applications?
#9
rikard-sics
opened
2 years ago
0
Discussion on the lifetime of a Security Context
#15
rikard-sics
closed
1 year ago
2
Sync with EDHOC in LAKE and John's work
#10
rikard-sics
closed
1 year ago
2
Consider different probabilities p_q and p_v for OSCORE specifically?
#11
rikard-sics
opened
2 years ago
2
Each client can count q up to half(?) the q limit as an optimization
#12
rikard-sics
opened
2 years ago
9
Consider raising adding q and v limits already in COSE registry with the algorithms
#13
rikard-sics
opened
2 years ago
2
Consider constrained devices and saving count_q and count_v regularly
#14
rikard-sics
opened
2 years ago
3