Subject: [COSE] [cose-issues] Remove “counter signature” header parameter (#12)

From: Mike Jones <[email-masked]>
Date: Sun, 1 Nov 2015 10:43:21 +0000

The “counter signature” header parameter in Section 3.1 seems like an unnecessary feature in a spec that should aspire to be minimal and light-weight. If the spec needs to talk about counter-signatures at all, it should do so by recommending that applications take the original COSE object and use it as a payload in another one to implement a counter-signature. I haven’t seen a common use case for this discussed on the list, and it certainly doesn’t seem to satisfy the 80/20 rule for whether it merits inclusion. Section 4.3 (Counter Signatures) also either needs to be deleted as part of this edit or modified to say that you compute a counter signature by using a COSE object as a signature payload.

View it on GitHub at https://github.com/cose-wg/cose-issues/issues/12