Closed rikard-sics closed 4 months ago
Option 1: Go for Appendix B.2 approach: Meaning the client can target any existing resource. But then the server cannot act on this request, and should respond with a 4.01, with no payload. Client must ignore any payload in response.
Option 2: Enforce that the client must send the request to a dedicated KUDOS resource, that doesn't produce a payload or act on requests. This may require that the KUDOS resource interacts with methods within the OSCORE-related code. Alternatively the OSCORE-related code can be aware of which resources are "KUDOS resources".
We can present what Appendix B.2 does and present Option 2 as the alternative.
[1] mentions this topic and puts it in relation with issue #85
[1] https://mailarchive.ietf.org/arch/msg/core/vSF5Mqo9LAioEM0AUEfoxxl7Zv4/
This should now be taken care of with commit ffe05281f3d74fd464643056dd3ad88256db5c73 for closing issue #93
Meaning can the Request #1 be actionable? (Possibly only if idempotent)