Closed mcr closed 1 year ago
This has languished because of mediaman discussion.
@mcr Sorry, is this really intended for 8366-bis? We had discussed in the call and in https://github.com/anima-wg/constrained-voucher/pull/268 . Conclusion is that the registration happens in draft-constrained-voucher where the signing method is defined.
If you want to define a content-type for the unsiged CBOR voucher format then it should be in 8366-bis for sure. That needs a different name and CoAP Content-Format number then.
If you want to define a content-type for the unsiged CBOR voucher format then it should be in 8366-bis for sure. That needs a different name and CoAP Content-Format number then.
But, if we can avoid this it is best if we do: having an unsigned format is not secure and could confuse people. Only define if needed for some purpose. Today we use the "plain CBOR" type for anything CBOR e.g. for non-signed CBOR Vouchers that are used in example and test applications.
see also: https://github.com/anima-wg/constrained-voucher/pull/268