On Thu, Jul 22, 2021 at 02:47:33AM +0200, Carsten Bormann wrote: > > > >> Now, there is in the COSE header also a parameter paramaeter called > >> "content type" > > > > In my implementation I don't use the 'content type' header in COSE because > > it is duplicate. > > It is not: the REST-level (here CoAP) Content-Type is the media-type of the > whole thing (as packaged in COSE-Sign1), while the COSE content-type is just > the media-type of the payload. > Except in somewhat unlikely cases, these are not the same.
Argh! (as in: why was this not obvious to me until you said so...) So: if we wanted to support the COSE content-type field semantically correctly, we should ask for another registry entry: application/voucher-cbor TBD4 I can not find a single example with content type in https://github.com/cose-wg/Examples crazy.. Cheers Toerless > > For example my servers should also accept content-format 18 just as TBD3. > > No, no, no… You just created busywork for interoperability testing. > Please decide for one option here and stick with that! > > Grüße, Carsten _______________________________________________ Anima mailing list [email protected] https://www.ietf.org/mailman/listinfo/anima
