I believe this specification is ready for publication.  It incorporates 
substantive working group feedback and I believe embodies solid consensus 
decisions.  There are multiple independent interoperable implementations.

It is well aligned with the COSE HPKE specification 
https://datatracker.ietf.org/doc/draft-ietf-cose-hpke/.

Finally, there's demand for this specification for use by other specifications, 
including the OpenID4VC specifications.

Let's get it done!

                                -- Mike

-----Original Message-----
From: Karen O'Donoghue via Datatracker <[email protected]>
Sent: Wednesday, January 21, 2026 12:07 PM
To: [email protected]; [email protected]; [email protected]
Cc: [email protected]
Subject: WGLC: draft-ietf-jose-hpke-encrypt-15 (Ends 2026-02-11)

JOSE WG members,

This message starts a WG Last Call (WGLC) for:
https://datatracker.ietf.org/doc/draft-ietf-jose-hpke-encrypt/

Please review and indicate your support or objection to proceeding with the 
publication of this document by replying to this email keeping [email protected] in 
copy. Please provide rationale for support and explanations or suggestions for 
objections.

Please note there is a parallel call going on in COSE working group for the 
document:
https://datatracker.ietf.org/doc/draft-ietf-cose-hpke/

Please consider reviewing both documents.

This Working Group Last Call ends on 2026-02-11

Regards,
JOSE Chairs

Please note:
Authors, and WG participants in general, are reminded of the Intellectual 
Property Rights (IPR) disclosure obligations described in BCP 79 [1].
Appropriate IPR disclosures required for full conformance with the provisions 
of BCP 78 [1] and BCP 79 [2] must be filed, if you are aware of any.
Sanctions available for application to violators of IETF IPR Policy can be 
found at [3].

[1] https://datatracker.ietf.org/doc/bcp78/
[2] https://datatracker.ietf.org/doc/bcp79/
[3] https://datatracker.ietf.org/doc/rfc6701/

_______________________________________________
jose mailing list -- [email protected]
To unsubscribe send an email to [email protected]

Reply via email to