Dear Authors/Chairs/ADs, Please see below for non-blocking comments from the expert. We have noted that you had already discussed this, but forwarding their remarks for completeness.
We have updated the Datatracker to IANA OK; thank you. Best regards, David Dong IANA Services Sr. Specialist -- the parameter registration is fundamentally OK. It is a bit lacking in the description of how the text string values are created. Since the Content-Type includes parameters, it is not quite correct to say that [IANA.MediaTypes] is the full source of information about this. While I don’t think implementers will generally have problems inferring what is not said, an explicit reference to a Content-Type definition could help with the fine points. RFC 9110 provides one; RFC 9193 also provides one that is more tightly defined (instead of using OWS, it just allows spaces); more tightly defined is usually preferable in a security-related specification. Grüße, Carsten _______________________________________________ COSE mailing list [email protected] https://www.ietf.org/mailman/listinfo/cose
