search

core-wg / oscore-key-update

Other
0 stars 0 forks source link

Define a well-known KUDOS resource #72

Closed rikard-sics closed 1 year ago

rikard-sics commented 1 year ago

In the client-initiated version, when the client sends the request to initiate KUDOS it needs to target a resource. Either sending the request to an actual resource existing on the other peer, or sending it to a dedicated resource to be used just for rekeying.

It may be a good idea that we define a well-known KUDOS resource (e.g. /.well-known/kudos) in the draft text, to make it clear what resource the client should use.

rikard-sics commented 1 year ago

Seems cleaner than sending a request to any resource. It a way like the this KUDOS resource corresponds to an "KUDOS application" that takes care of the rekeying.

A normative recommendation can be that a server that supports KUDOS should have this resource available.

Client sending KUDOS requests should target this new resource.

rikard-sics commented 1 year ago

(Based on feedback from Rafa Marin-Lopez)