Hi,

I support the publication of this document.

Best Regards,
Martin Furuhed

Från: Michael Jones <[email protected]>
Datum: onsdag, 17 juni 2026 00:48
Till: [email protected] <[email protected]>
Ämne: [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://m365.eu.vadesecure.com/safeproxy/v4?f=F-NagFliK2mv0u1osPC6L-pkTYCqa1orONbsZtaRhKGvnTvRJFfrfHRzblqj9sdA&i=R_hgowhUFhMQ5Px21B2gQHU_XciIquhTle53QLDa5s0lm_KI4Ej9vRP-9EcdbJLXDObWEqqcSKzVgmxRfslU_w&k=DE54&r=ROHWK4Q7VI49R_D3ykGuyWzYZ977zmZHjyxSzIWhnyc01MsLrprEENIE5cq4shoy&s=74bfd6f027baceb2a2c669ccdfc489056f1612050baea49fc2e6cc55479c047e&u=https%3A%2F%2Fdatatracker.ietf.org%2Fdoc%2Fdraft-ietf-cose-c509-test-vectors%2F>.
  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/<https://m365.eu.vadesecure.com/safeproxy/v4?f=ZdKIZF_INvtaVa6tYtvXLy65yZQdnnT_aetzoaXZJEKuF9UWD0QIWIPDOCEpRsA0&i=P7eWZrQUI6Seu3HaWXjzfTjde61H3GXQPc41nrChYJsIZ_yw9JZ2VyvOtILyhIAKObbbrCAY-xZ1DAxO5Ziqjg&k=1Nto&r=94aQPVKA3LBJRAJ1xQAqkebsllymMXXOpFJY8e2rvrdnZi-2i87b0JcfNnzpYNCs&s=d3e5ff663b5eb04e9e30272cf12621dd023e3e3757d215f8d82b3340aa994f45&u=https%3A%2F%2Fdatatracker.ietf.org%2Fdoc%2Fdraft-ietf-cose-cbor-encoded-cert%2F>,
 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]

Reply via email to