Hi all, I support the publication of this document.
Please find a few editorial comments below. Best, /Marco * Title: s/CBOR Encoded/CBOR-Encoded * Section 1.0: s/examples of X.509 certificates/examples of CBOR-encoded X.509 (C509) certificates * Section 1.0: the Editor's note at the end can be simply removed, or instead replaced by final text that mentions a possible separate document. * Section 1.1: s/with C509/with C509 certificates * Section 2 says: > The CA uses an Ed25519 public key because the resulting signature is compact. An additional reason is that, unlike ECDSA, it ensures deterministic signatures, which makes it feasible to have signatures for reproducible test vectors. It could be worth to point it out as a second reason. ________________________________ From: Michael Jones <[email protected]> Sent: Wednesday, June 17, 2026 12:46 AM To: [email protected] <[email protected]> Subject: [COSE] WGLC for draft-ietf-cose-c509-test-vectors This note starts a two-week Working Group Last Call (WGLC) for the Test Vectors for CBOR Encoded X.509 (C509) Certificates specification https://datatracker.ietf.org/doc/draft-ietf-cose-c509-test-vectors/<https://www.ietf.org/archive/id/draft-ietf-cose-hpke-13.html>. The WGLC will run for two weeks, ending on Tuesday, June 30, 2026. Please review and send any comments or feedback to the COSE working group at [email protected]<mailto:[email protected]>. Even if your feedback is “this is ready for publication”, please let us know. Note that the CBOR Encoded X.509 Certificates (C509 Certificates) specification https://datatracker.ietf.org/doc/draft-ietf-cose-cbor-encoded-cert/, which this tests, is in IESG review. Thank you, -- Ivo and Mike, COSE Co-Chairs
_______________________________________________ COSE mailing list -- [email protected] To unsubscribe send an email to [email protected]
