Or you can go the other way around, go for tag 18, put a content-format number that you registered (along a media-type) for an *unprotected* voucher (payload) into the protected header. (You might still want a content-format number/media type for the entire voucher, but you may not need a tag.)
Grüße, Carsten > On 2021-07-21, at 14:04, Carsten Bormann <c...@tzi.org> wrote: > > On 2021-07-21, at 09:58, Esko Dijk <esko.d...@iotconsultancy.nl> wrote: >> >> If the object is created to be transported over other ways (e.g. email, USB >> stick, etc) then I would opt for including that 'content type' possibly. > > Probably not needed: > > https://www.ietf.org/archive/id/draft-ietf-cbor-file-magic-02.html#name-cbor-tags-for-coap-content-f > > So once you have a content-format number, you can use file-magic and that > pre-registered tag to package the voucher in a file(1) compatible wrapper. > _______________________________________________ Anima mailing list Anima@ietf.org https://www.ietf.org/mailman/listinfo/anima
