search

core-wg / oscore-key-update

Other
0 stars 0 forks source link

Corner case with server-only endpoint which reached its 'v' limit #68

Closed rikard-sics closed 3 months ago

rikard-sics commented 1 year ago

How should an endpoint supporting KUDOS, but which can only act as CoAP server (meaning it cannot send requests), act in the case it receives an OSCORE protected message but its 'v' limit has been reached? (Thus it cannot safely decrypt the incoming request).

rikard-sics commented 1 year ago

We can present the 2 alternatives we came up with during a future CoRE session and see what feedback we get.

rikard-sics commented 1 year ago

Alternative 1: Either don't decrypt the request at all, but respond with encrypted response. Alternative 2: Do in fact decrypt the request, thus making exception and use the Recipient Key even though the limits are reached.

rikard-sics commented 1 year ago

This could be raised during a future meeting

rikard-sics commented 3 months ago

Added tentative text to be discussed early in section "Key Update with Forward Secrecy".