On Fri, Jul 23, 2021 at 08:38:31AM -0400, Michael Richardson wrote:
> > My sugestion for the constrained voucher text is:
>
> > Constrained vouchers (application-type/voucher-cose+cbor, TBD3)
> > SHOULD NOT use the COSE header "content type" field because the
> > encoding is never "ambiguous" according to RFC8152 Section 3.1. If a
> > constrained voucher contains this field, it MUST be ignored by the
> > processing described in this document.
>
> I don't think that this is useful to add.
> "Unknown headers are ignored"
I disagree. Headers for which we do not specify behavior will be handled
however implementers like. Especially when there is a reference (rfc8152/bis)
that does describe something potentially confusing about this header.
Cheers
Toerless
_______________________________________________
Anima mailing list
Anima@ietf.org
https://www.ietf.org/mailman/listinfo/anima
