On Tue, 7 Oct 2025 at 18:18, Carsten Bormann <[email protected]> wrote: > > On 2025-10-07, at 18:10, Thomas Fossati <[email protected]> wrote: > > > > Sure, that's one option (new media type). > > Another option is to extend the existing (and already parameterised) > > application/cose-x509. > > I believe that the required procedural work should be roughly the same. > > I’ll leave the question of what the procedural work for adding a parameter to > a media type would be to the media-type experts
For completeness, see the feedback we got from the media types experts [1]. [1] https://mailarchive.ietf.org/arch/msg/media-types/ypYevlqM9zc9vLK3m17eH48j8Xc/ > (my short summary would be it is not meant to be done, see last three > paragraphs of Section 4.3 of RFC 6838 [1]). I agree with you in the general case, but in this specific instance, it seems that we fall into the MAY branch: [...] MAY be added convey additional information that does not otherwise change existing functionality because the change is purely additive. Besides, the fate of a parameter named "usage" was sealed from the outset, wasn't it? :-) > If you want to minimize delay-introducing dependencies, setting up a new > media type is the way to go. Thanks for the advice! _______________________________________________ COSE mailing list -- [email protected] To unsubscribe send an email to [email protected]
