search

ace-wg / est-oscore

Other
0 stars 0 forks source link

Consider future Content-Format identifier when responding to /skg #72

Open malishav opened 2 months ago

malishav commented 2 months ago

Based on @EskoDijk 's review in https://mailarchive.ietf.org/arch/msg/ace/I70MHcCzSfPIy28lDqxEOcllgJw/:

4.3.2 CBOR-encoded Objects

In the case of CBOR-encoded request … also CBOR encoded. There’s also the client’s Accept option that comes into play. There could be a future content-format that the client would specify in the Accept option; in which case the response could be another format than 62. But agree that when no Accept option is specified, then 62 is returned with CBOR-encoded contents.

malishav commented 4 days ago

There is an issue in current Table 5 in that Content-Format 101 is used instead of TBD10 (application/cose-c509-privkey).

malishav commented 4 days ago

Rewrite Section 4.3.2 in order to have analog paragraphs to Section 4.3.1 and particularly make sure that the text is compatible with the negotiation through the Accept option.