-
Notifications
You must be signed in to change notification settings - Fork 2
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
address #9: match boxing with (Group) OSCORE #36
Conversation
draft-bormann-core-corr-clar.md
Outdated
|
||
This calls for careful design choices and enhancements when developing extensions for CoAP or protocols and methods applicable to CoAP, such as in the following cases: | ||
|
||
* As originally defined in {{-oscore}}, the security protocol Object Security for Constrained RESTful Environments (OSCORE) does not impact the CoAP matching functions based on Message ID or Token. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I'm having a hard time with "does not impact". It sure does, but maybe only in one way and not another? I think we need to be more precise here (maybe even adding an example).
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Largely addressed in d16eb1a
ongoing long exchanges ➔ ongoing active requests
Match boxing when using OSCORE, KUDOS, and Group OSCORE