-
AP10: (Section 4.2) Move the negotiation of public key type/parameter that is now defined in the ace-key-groupcomm-oscore (see for example 4.1 paragraph 2) to this document, to make it more general.
-
I am continuing an implementation of Group OSCORE in Java. I have been working with further details regarding the countersignatures and keys.
I believe the line referenced below should rather be:
…
-
In the example in section 4.1.3.3. there is an Uri-Port given in the Proxi-Uri decomposition. This disappears in the resulting OSCORE Uri-* and Proxy-Uri options.
Although this is the default CoAP po…
-
I was working on creating JUnit tests for the external AAD (among other things) for the Java OSCORE implementation in Californium.
During this work I noticed the following. In [section 5.4](https:/…
-
This applies to 2.0.x branch M14.
The pom file of cf-oscore has a dependency on both californium-core and scandium. I don't think that should be that way (e.g. scandium has no dependency on califor…
-
Currently the framework's intention is that the access token is sent to the authz-info endpoint without any "wrapper". Section 4.1 here requires the client to wrap the access token into a map and use …
-
@jimsch In section 3.2, the following requirements are imposed:
* The AS MAY assign an identifier to the client
* The AS MUST assign an identifier to the RS
* The client identifiers MUST be uniq…
-
A bit late in the process, but triggered by implemenatation experience.
At the end of section 3.1:
For clarification, consider a client and server equipped with identical common- sender- and reci…
-
Branch 2.0.x:
In the meantime californium has a central implementation for byte array based ids:
https://github.com/eclipse/californium/blob/2.0.x/element-connector/src/main/java/org/eclipse/cal…
boaks updated
5 years ago
-
Rikard noted: in certain cases clients cannot distinguish between error messages from OSCORE processing and from CoAP processing; e.g. a 4.02 error message could be caused by "failure to decompress" o…