Based on Jim's comment regarding support of GeneralizedTime, I seems like the CBOR encoding might support RFC 5280 features that are not in RFC 7925. The charter should be written so that it allows this. E.g. something like
"A CBOR encoding based of the certificate profile defined in RFC 7925. It is expected that the encoding works with a large subset of RFC 7925. The encoding might support additional RFC 5280 options like GeneralizedTime and shall take into consideration any updates in draft-ietf-uta-tls13-iot-profile. The compression may also include other important IoT certificate profiles like IEEE 802.11AR." _______________________________________________ COSE mailing list [email protected] https://www.ietf.org/mailman/listinfo/cose
