docs: ISO/IEC 18013-5 mdoc implementation plan + EU Age Verification profile compliance plan#570
Open
DibranMulder wants to merge 2 commits into
Open
docs: ISO/IEC 18013-5 mdoc implementation plan + EU Age Verification profile compliance plan#570DibranMulder wants to merge 2 commits into
DibranMulder wants to merge 2 commits into
Conversation
This was referenced Jun 10, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Adds two planning documents:
docs/mdoc-implementation-plan.md— the implementation plan for landing themso_mdoccredential format in irmago, covering issuance to the wallet via OpenID4VCI and disclosure via OpenID4VP (DCQL). It covers the current state of theopenid4vcibranch, scope and non-goals, key design decisions (CBOR/COSE dependencies, neweudi/credentials/mdoc/package, device key reuse, theDcqlCredentialQueryHandlerinterface extension, SessionTranscript handover construction), and independently mergeable, automatically tested milestones, using multipaz as the reference implementation.docs/av-profile-compliance-plan.md— a cross-check of the mdoc plan against the EU Age Verification technical specification and its Annex A AV profile, plus a delivery plan for making go-passport-issuer an AV-compliant Attestation Provider issuingeu.europa.ec.av.1proof-of-age mdocs over OpenID4VCI. Key findings: the mdoc plan is largely AV-compatible as-is; the main gaps are the W3C Digital Credentials API presentation path (ISO 18013-7 Annex C, HPKE-encrypted responses — the AV profile's primary channel, added as milestone M8), support for unsigned OpenID4VP requests with theredirect_uriclient-id scheme, MSO timestamp-precision truncation, and ETSI TS 119 612 trusted-list support.Tracking issues
The plans have been converted to issues — one tracking issue with the milestones as sub-issues:
The AV-profile deltas have been appended to the affected milestone issues as "EU AV profile addendum" sections.