core-wg oscore-key-update issues

core-wg / oscore-key-update

Other

0 stars 0 forks source link

issues

Newest

Newest Most commented Recently updated Oldest Least commented Least recently updated

Addition to section about updated protection of CoAP responses with OSCORE

#104 rikard-sics opened 3 weeks ago
0
Update according to IANA early review

#103 rikard-sics opened 4 weeks ago
0
Christian's review of v-08

#102 rikard-sics closed 1 month ago
0
Cover usage of KUDOS with servers that use ACE (e.g. EDHOC profile)

#101 rikard-sics opened 1 month ago
0
Officially update OSCORE wrt. uninitialization of Notification Numbers for new OSCORE Security Contexts

#100 rikard-sics closed 4 months ago
1
Editorial: Split main section describing KUDOS into subsections

#99 rikard-sics closed 4 months ago
0
Consider 2 papers relevant for KUDOS

#98 rikard-sics closed 4 months ago
1
Handle situation with two simultaneously started key updates

#97 rikard-sics closed 4 months ago
0
Add considerations on usage of no-response option

#96 rikard-sics closed 5 months ago
0
Allow larger nonce lengths

#95 chrysn closed 9 months ago
2
Allow a more flexible message flow

#94 rikard-sics closed 9 months ago
1
Let KUDOS messages be regular application messages

#93 rikard-sics closed 9 months ago
2
Mention EDHOC and OSCORE profile of ACE

#92 rikard-sics closed 1 year ago
1
Language issues

#91 rikard-sics closed 1 year ago
1
FS after non-FS

#90 chrysn closed 4 months ago
1
Check whether non-random nonces are allowed

#89 chrysn closed 9 months ago
5
non-FS mode: Spell out practical consequences

#88 chrysn closed 1 year ago
1
MUST discard CTX_OLD

#87 chrysn closed 1 year ago
2
Cite the document that creates the EDHOC External Authorization Data Registry

#86 rikard-sics closed 1 year ago
0
Mandate implementation of both flows in both direction?

#85 rikard-sics closed 1 year ago
3
Change name of 'x' byte?

#84 rikard-sics closed 4 months ago
1
Does Request #1 need to target a KUDOS resource, or any resource (forward flow)

#83 rikard-sics closed 9 months ago
4
Add privacy considerations section

#82 rikard-sics closed 4 months ago
2
Add note to set Notification Number to be uninitialized when creating new Security Contexts

#81 rikard-sics closed 4 months ago
3
Split section about Update of OSCORE Sender/Recipient IDs to new document

#80 rikard-sics closed 9 months ago
4
Add reference to new limits document

#79 rikard-sics closed 1 year ago
4
Make sure to state that CTX_OLD should not be used for sending messages

#78 rikard-sics closed 1 year ago
0
Change from Client/Server-Initiated to Forward/Reverse message flow

#77 rikard-sics closed 1 year ago
1
Considerations on nonce lengths

#76 rikard-sics closed 1 year ago
2
Provide examples for KUDOS messages sizes (added overhead)

#75 rikard-sics closed 1 year ago
1
Mention EDHOC-KeyUpdate as way of rekeying

#74 rikard-sics closed 1 year ago
0
Considerations on "active rekeying"

#73 rikard-sics closed 1 year ago
1
Define a well-known KUDOS resource

#72 rikard-sics closed 1 year ago
2
Make it more clear that requests/responses are specifically CoAP requests/responses

#71 rikard-sics closed 1 year ago
1
Register bits for extension

#70 rikard-sics closed 1 year ago
2
Considerations on use of SCHC

#69 rikard-sics closed 1 year ago
0
Corner case with server-only endpoint which reached its 'v' limit

#68 rikard-sics closed 4 months ago
4
Necessity of EAD items for signaling KUDOS support

#67 rikard-sics closed 1 year ago
1
Clarifications on if the limits and 'exp' are "hard" or "soft"

#66 rikard-sics closed 1 year ago
1
Preserve observations following an update of updating OSCORE IDs alone

#65 rikard-sics closed 1 year ago
3
Add textual description for examples on OSCORE ID updating

#64 rikard-sics closed 1 year ago
1
Enforce including Partial IV in KUDOS message 2 for client-initiated version (and general considerations for OSCORE)

#63 rikard-sics closed 1 year ago
4
Raise what should be mandatory and not regarding the limits

#62 rikard-sics closed 1 year ago
2
Make reason for rekeying in section "Current methods for Rekeying OSCORE" more generic

#61 rikard-sics closed 2 years ago
0
Update text describing bit 15

#60 rikard-sics closed 2 years ago
0
Retain same flexibility as in OSCORE, don't lock user into HKDF-Expand hash function

#59 rikard-sics closed 2 years ago
2
Case when Different Security Context is used for request decryption and response encryption

#58 rikard-sics closed 1 year ago
2
Add text indicating what a CAPABLE and non-CAPABLE device must support

#57 rikard-sics closed 2 years ago
0
Considerations on bits (bit 0 to signal extension). Make bit 1 unassigned.

#56 rikard-sics closed 2 years ago
2
Register EDHOC EAD items for signaling KUDOS support

#55 rikard-sics closed 2 years ago
5