Skip to content

Privacy Considerations: proposed privacy and security requirements for presentation protocols - #544

Draft
marcoscaceres wants to merge 2 commits into
mainfrom
privacy-protocol-requirements
Draft

Privacy Considerations: proposed privacy and security requirements for presentation protocols#544
marcoscaceres wants to merge 2 commits into
mainfrom
privacy-protocol-requirements

Conversation

@marcoscaceres

@marcoscaceres marcoscaceres commented Jun 17, 2026

Copy link
Copy Markdown
Collaborator

This is a DRAFT for Working Group discussion — please do not merge.

This proposes a concrete set of privacy and security requirements for the presentation protocols the specification lists, as a consolidated "Privacy and security requirements for presentation protocols" subsection in the Privacy Considerations. It promotes the existing, largely non-normative considerations into conditional RFC 2119 requirements: a MUST for selective disclosure (scoped to the protocol mechanism), and SHOULD-level requirements for unlinkable presentations, avoiding "phone home" at presentation time, unlinkable revocation, transparency and consent, and verifier authorization.

The requirements are deliberately scoped so that the protocols currently listed in the spec can satisfy them. Only selective disclosure is a MUST (both OpenID4VP and mdoc provide the mechanism); the rest are SHOULD with conditions, because neither listed protocol provides inherent unlinkability, both have a path that avoids contacting the issuer at presentation time, and an unsigned OpenID4VP request or a baseline mdoc would fail a MUST on verifier authentication.

This is opened as a draft because the Working Group has not agreed whether these belong in the specification as normative requirements or in a separate document.

Opened for discussion. Happy to reshape these, split them across the individual consideration subsections, or move them to a separate document per the group's direction.

The following tasks have been completed:

  • Modified Web platform tests (link) — N/A at draft stage; normative shape is TBD by the WG.

Implementation commitment:

  • WebKit (link to issue) — N/A at draft stage.
  • Chromium (link to issue) — N/A at draft stage.
  • Gecko (link to issue) — N/A at draft stage.

Documentation and checks

  • Affects privacy
  • Affects security
  • Pinged MDN — N/A
  • Updated Explainer — N/A
  • Updated digitalcredentials.dev — N/A

Preview | Diff

… protocols

Adds a consolidated, conditional-normative subsection (RFC 2119) proposing
privacy and security requirements for the listed presentation protocols,
scoped so the currently listed protocols can satisfy them.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant