COSE key thumbprints need canonical members, not a hash of the serialized key
A key identifier is easy to add at the edge of a protocol and surprisingly difficult to define consistently. If two systems hash different encodings of the same public key, they create two identifiers for one credential. If they include optional metadata, a harmless key update can change the identifier and break trust. RFC 9679 defines a COSE Key Thumbprint to avoid those outcomes by specifying the key members that participate in the hash and the canonical encoding used to compute it.
The distinction between a key and its representation is central. A COSE key can contain optional fields such as a key identifier, algorithm hint, operations, or trusted issuer data. Those fields can help routing or policy, but they are not all part of the cryptographic identity.…