[OAUTH-WG] Re: WG Last Call: draft-ietf-oauth-sd-jwt-vc-14 (Ends 2026-02-19)

[Brian Campbell <[e-mail]>]

I am overall supportive of proceeding with the publication of this
document.

Some threads resulting from the recent DISCUSS ballot on TSL
<https://mailarchive.ietf.org/arch/msg/oauth/tHd5oWIXE8ZZjTaVXPtTmWd8HqE/>
about
it obviously exceeding the current and prospective future scope of this
WG's charter led to some more narrow discussions elsewhere, in one of which
I expressed my discomfort
<https://mailarchive.ietf.org/arch/msg/spice/4xr2I1IX_A4T_cDxlUUufH5QdIM/>with
draft RFCs linking to the product page of an organization with a
non-transparent and access-restricted standards development process and
pay-to-access publication model (at least without some contextualization or
qualification). While expressing that discomfort I was reminded
that draft-ietf-oauth-sd-jwt-vc-14 has a similar, if arguably somewhat
less invasive, product placement that I'd like to see addressed as part of
WGLC. I created issue #393
<https://github.com/oauth-wg/oauth-sd-jwt-vc/issues/393> to track that.

On Thu, Feb 5, 2026 at 12:52 PM Rifaat Shekh-Yusef via Datatracker <
[e-mail]> wrote:

> This message starts a WG Last Call for:
> draft-ietf-oauth-sd-jwt-vc-14
>
> This Working Group Last Call ends on 2026-02-19
>
> Abstract:
>    This specification describes data formats as well as validation and
>    processing rules to express Verifiable Digital Credentials with JSON
>    payloads with and without selective disclosure based on the SD-JWT
>    [RFC9901] format.
>
> File can be retrieved from:
>
> Please review and indicate your support or objection to proceed with the
> publication of this document by replying to this email keeping
> [e-mail]
> in copy. Objections should be explained and suggestions to resolve them are
> highly appreciated.
>
> 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].
>
> Thank you.
>
> [1] https://datatracker.ietf.org/doc/bcp78/
> [2] https://datatracker.ietf.org/doc/bcp79/
> [3] https://datatracker.ietf.org/doc/rfc6701/
>
> The IETF datatracker status page for this Internet-Draft is:
> https://datatracker.ietf.org/doc/draft-ietf-oauth-sd-jwt-vc/
>
> There is also an HTML version available at:
> https://www.ietf.org/archive/id/draft-ietf-oauth-sd-jwt-vc-14.html
>
> A diff from the previous version is available at:
> https://author-tools.ietf.org/iddiff?url2=draft-ietf-oauth-sd-jwt-vc-14
>

-- 
_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._