-
Is there any Support for OSCORE planned?
RFC: [Object Security for Constrained RESTful Environments](https://datatracker.ietf.org/doc/html/rfc8613)
I'm mentioning this, because we might need thi…
-
This is a bit wobbly still, but IMO something we should clarify better:
**What are the pieces that go into dereferencing a CoAP URI, especially when OSCORE is involved (which unlike DTLS does not b…
-
OSCORE response for Confirmable request is always sent as Seperate response (ACK first, then response with data). This generates additional traffic on network.
It is caused by following code in coa…
-
Based on @EskoDijk 's review in https://mailarchive.ietf.org/arch/msg/ace/I70MHcCzSfPIy28lDqxEOcllgJw/:
5. HTTP-CoAP Proxy
>> … use of TLS and DTLS is optional …
Use of TLS or DTLS is optional…
-
This is the big tracking issue for all things related to the CoAP+security components that should be part of RIOT-rs.
## The big picture
Having a CoAP server running should be a feature that's a…
-
This issue aims to discuss about Oscore Context lifetime.
In a general way but also mainly what should be targeted for a minimal viable feature.
Here is some information about that : https://git…
-
There are a few places where I think we were too narrow in where we defined new behavior:
* BERT could be useful outside of TCPish transports: https://github.com/core-wg/corrclar/issues/17
* Obser…
-
Right now in the spec, there's a feature called uniqueAuthenticationToken, used to secure a connection and make sure they are who they say they are. This should be adapted to work with a better securi…
-
### How can we help?
1. OneSignal_Core
2. OneSignal_Extension
3. OneSignal_LiveActivities
4. OneSignal_Notifications
5. OneSignal_OSCore
6. OneSignal_Outcomes
7. OneSignal_User
8. OneSignal_XC…
-
> For IoT systems, object security [RFC8613] may be preferable over transport layer security, as it enables intermediaries to cache responses while preserving security.
"Cacheable OSCORE", Christia…