References

Normative

• RFC 9052 — Schaad, J. “CBOR Object Signing and Encryption (COSE): Structures and Process.” STD 96, RFC 9052. The COSE_Sign1 container the signature profile admits.
• RFC 9053 — Schaad, J. “CBOR Object Signing and Encryption (COSE): Initial Algorithms.” RFC 9053. Defines ES256 and its fixed-width signature encoding.
• RFC 8949 — Bormann, C., Hoffman, P. “Concise Binary Object Representation (CBOR).” STD 94, RFC 8949. Section 4.2.1 supplies the deterministic encoding every signed structure is canonicalised under.
• RFC 6979 — Pornin, T. “Deterministic Usage of the Digital Signature Algorithm (DSA) and Elliptic Curve Digital Signature Algorithm (ECDSA).” RFC 6979. Normative for software signers; a secure element cannot be held to it, which is why signatures are not reproducible across signers.
• SEC 1 — Standards for Efficient Cryptography Group. “SEC 1: Elliptic Curve Cryptography.” Version 2.0. Supplies the 33-byte compressed point encoding every root public key is pinned to.
• NIST SP 800-186 — Chen, L., Moody, D., Regenscheid, A., Robinson, A., Randall, K. “Recommendations for Discrete Logarithm-based Cryptography: Elliptic Curve Domain Parameters.” NIST SP 800-186. Defines secp256r1.
• BLAKE3 — O’Connor, J., Aumasson, J-P., Neves, S., Wilcox-O’Hearn, Z. “BLAKE3: One Function, Fast Everywhere.” The single hash convention.
• PADME — Nikitin, K., Barman, L., Lueks, W., Underwood, M., Hubaux, J-P., Troncoso, C. “Reducing Metadata Leakage from Encrypted Files and Communication with PURBs.” PoPETs 2019(4). Section 4.4 defines the padding function.

Informative

• RFC 7250 — Wouters, P., Tschofenig, H., Gilmore, J., Weiler, S., Kivinen, T. “Using Raw Public Keys in Transport Layer Security (TLS) and Datagram Transport Layer Security (DTLS).” RFC 7250. The shape of the transport channel key, which the signature profile does not govern.