Skip to main content
Agent Identity

IETF · 31 October 2026 (IESG Evaluation; 5 November 2026 telechat)

SD-JWT-based Verifiable Digital Credentials (SD-JWT VC)

draft-ietf-oauth-sd-jwt-vc-23

WG draftDraft — expect changeIdentityAdjacent

SD-JWT-based Verifiable Digital Credentials (SD-JWT VC) (draft-ietf-oauth-sd-jwt-vc-23) is WG draft, 31 October 2026 (IESG Evaluation; 5 November 2026 telechat). Likely credential format if you bind an agent to an organization with selective disclosure (show role, hide home address).

ShareLinkedInX

At a glance

Problem
Need a JWT-shaped verifiable credential that supports selective disclosure, usable with OpenID4VP/VCI.
Identity / authn / authz
Credential format for identity (and other) claims.

Actors

  • Issuer
  • Holder
  • Verifier

When this matters for agents

When this matters for agents: likely credential format if you bind an agent to an organization with selective disclosure (show role, hide home address). IETF Last Call ended 15 September 2026. As of 1 November 2026 the IESG state is IESG Evaluation on draft-23, on the 5 November 2026 telechat agenda — not an RFC yet. Not an OAuth access token.

Flow in plain language

Issuer creates an SD-JWT with salted disclosures. Holder presents a subset. Verifier checks signature and digests.

Key tokens and claims

SD-JWT + disclosures
Combined presentation format; not an OAuth access token.

Implementer notes

IETF Last Call ended 15 September 2026. As of 1 November 2026 the IESG state is IESG Evaluation on draft-23 (31 October 2026, expires 4 May 2027), on the 5 November 2026 telechat agenda — not an RFC. Revisions -20 through -23 answer directorate and ballot comments; the presentation model is unchanged. Related RFC 9901 covers generic SD-JWT.

Related

Primary sources

  • Datatrackerhttps://datatracker.ietf.org/doc/draft-ietf-oauth-sd-jwt-vc/