EUDI December checkpoint: SD-JWT VC RFC, HAIP 1.1 and the wallet deadline (2026-12)

[luisgf]

Horizon: mid (dated: 2026-12-21 → 2027-01) · Effort: M · 2026-07-17 roadmap analysis (round 3)

Three EUDI-relevant events cluster in one week, per the published calendars:

• 2026-12-21 — SD-JWT VC (draft-ietf-oauth-sd-jwt-vc, at draft-17, WG work complete, in IESG review) is expected to publish as an RFC
• 2026-12-21 — HAIP 1.1 is the adopted OIDF work-item date ("updates per feedback to 1.0"; HAIP 1.0 Final since 2025-12-29 pins the ES256 floor)
• 2026-12-24 — the eIDAS2 deadline for every Member State to offer an EUDI Wallet

When they land (timeboxed checkpoint work, not an open-ended project):

• diff draft-17 → the final RFC for anything affecting ob3/eudi.py (claim names, typ, disclosure rules, key binding) and update pins/tests accordingly
• review HAIP 1.1 for algorithm/format changes touching the SD-JWT track — today the ES256 family is the floor, which the track already prefers; no Ed25519 mandate is on record (RFC 9864 stays absorbed upstream, see Quarterly spec radar: vc-di-bbs, ELM/Europass, OB Future-Version candidates (watch, don't build) #173)
• re-check the EUDI ARF (v2.9.0 as of 2026-05-21) for verifier-side requirements relevant to badges
• update the Security Model wiki page and, if the delegate's behavior shifts, the openvc-core floor/latest boundary tests (Independently monitor and document the x5c / eIDAS trust boundary with openvc-core #236)
• feed the outcome into the gated Token Status List issue (SD-JWT VC revocation via IETF Token Status List (gated: RFC + openvc-core + demand) #245) and the OpenID4VP go/no-go (go/no-go: verify OpenID4VP / DC-API wallet presentations by delegating to openvc-core #246)

This absorbs the HAIP watch item that previously lived in the quarterly radar (#173).