A -09 draft with the changes noted below has been published in order to ward off this impending expiration.
* Use SD-JWT KB in place of SD-JWT with Key Binding JWT * Editorial changes * Document reasons for not using JSON Pointer or JSON Path (Issue #267) * Clarify that private claim names MAY be used * Update PID Example * Fix section numbering in a few SD-JWT references ---------- Forwarded message --------- From: IETF Secretariat <ietf-secretariat-re...@ietf.org> Date: Sun, May 25, 2025 at 1:00 AM Subject: Expiration impending: <draft-ietf-oauth-sd-jwt-vc-08.txt> To: <draft-ietf-oauth-sd-jwt...@ietf.org> Cc: <debcool...@gmail.com>, <oauth-cha...@ietf.org> The following Internet-Draft will expire soon: Name: draft-ietf-oauth-sd-jwt-vc Title: SD-JWT-based Verifiable Credentials (SD-JWT VC) State: I-D Exists Expires: 2025-06-06 (in 1 week, 4 days) -- _CONFIDENTIALITY NOTICE: This email may contain confidential and privileged material for the sole use of the intended recipient(s). Any review, use, distribution or disclosure by others is strictly prohibited. If you have received this communication in error, please notify the sender immediately by e-mail and delete the message and any file attachments from your computer. Thank you._
_______________________________________________ OAuth mailing list -- oauth@ietf.org To unsubscribe send an email to oauth-le...@ietf.org
