search

core-wg / oscore-key-update

Other
0 stars 0 forks source link

Allow a more flexible message flow #94

Closed rikard-sics closed 4 months ago

rikard-sics commented 9 months ago

We can allow KUDOS exchanges to not necessarily be based on request/response pairs, but rather allow for a more flexible message flows.

For instance Christian gave the following example where both KUDOS messages can be requests:

  1. EP -> RD: POST /.well-known/rd - KUDOS message 1
  2. RD -> EP: GET /.well-known/core - KUDOS message 2
  3. EP -> RD: response with payload of .well-known/core
  4. RD -> EP: response to the POST

Another example is where the second KUDOS message is a response to a different request than the first KUDOS message. This could for instance be the case for notifications, where the client sends a request and the server then sends a notification (which is not a response to the initial client request).

See also: https://mailarchive.ietf.org/arch/msg/core/VRpad8f_cSye84txUnuTxYLDczw/

rikard-sics commented 6 months ago

This was raised during IETF 118 and got no objections, so we can go ahead with this