-
Consistently with draft-ietf-ace-key-groupcomm-18, REQ21 in Appendix A.1 should be updated as follows:
OLD
> REQ21 - Specify the approaches used to compute and verify the PoP evidence to include i…
-
Consistently with draft-ietf-ace-key-groupcomm-18, REQ17 in Appendix A.1 should be updated as follows:
OLD
> REQ17 - Specify the format of the 'key' parameter: see Section 6.3.
NEW
> REQ17 - S…
-
Consistently with draft-ietf-ace-key-groupcomm-18, REQ10 in Appendix A.1 should be updated as follows:
OLD
> REQ10 - Register a Resource Type for the root url-path, which is used to discover the c…
-
The SixLabors.ImageSharp version used in the current Oscore.QrCodes.ImageSharp package version 1.0.4 has several high and medium vulnerabilities.
The dependency is already updated in the current ma…
-
Idea from Carsten from previous IETF meeting: "Use clock instead of saving counters"
-
How often must they be stored? Consider Appendix B.1 and saving the SSN.
-
How are we sure that Leshan project is properly implemented with standards? Do you execute some periodically external tests or compliance is checked only while code reviewing?
-
#### Description
In order to finish #14095, I need to be able to get the IPv6 destination address of a incoming packet in a coap handler. As field in `coap_pkt_t` for example.
### Useful links
No…
-
Dealing with the implementation of the defined SecuritySchemes, I noticed that the fields `name` and `in` for both the`DigestSecurityScheme` and `BasicSecurityScheme` seem to not correspond to [RFC 76…
JKRhb updated
9 months ago
-
As suggested during the CoRE interim. This works fine with responses with no partial IV since they will be counted in that senders q counter. Each request can only have max one response without PIV. F…