Jon Shallow

Added in Appendix B.1.1 support. OSCORE specific API has been updated.

@kkrentz Interesting question > Does OSCORE specify what should happen when an RST is being received? Not that I can find, even under the security considetations. However, RFC7252 https://datatracker.ietf.org/doc/html/rfc7252#section-11.4 does...

Added in configurable support for RFC8613 Appendix B.1.2 and Appendix B.2

Thanks for doing all this testing etc. > Besides, it was strange that server configs also must set a recipient_id. I was following [RFC8613 3.2](https://datatracker.ietf.org/doc/html/rfc8613#section-3.2) where Recipient ID shall be...

> https://github.com/kkrentz/libcoap/commit/686d9f4af1b6e56a81d4969106477cef90fe1644 The Contiki change is specific to your Contiki PR #760, so cannot be a part of this PR. The challenge I am currently having is that `coap_oscore_overhead()` does...

Suggestions apart from the Contiki change have now been pushed.

Code changes pushed. > Thank you. The RAM consumption has gotten better. On Contiki it continues to be problematic ... Open to suggestions. > As for recipient_ids, my implementation does...

> In my implementation, I derive AEAD keys on demand, which saves some RAM. This could be CPU intensive, but understand why you may want to do that. I would...

Reverted out change https://github.com/obgm/libcoap/pull/764#discussion_r876338502 where the sequence number is updated every re-transmission. See discussion at [core-wg/corrclar](https://github.com/core-wg/corrclar/issues/24).

Added in a separate commit for interoperability tests as per https://core-wg.github.io/oscore/test-spec5.html