Skip to content

Update PVT registration doc to align with RFC9578 - #60

Open
ekovac wants to merge 1 commit into
GoogleChrome:mainfrom
ekovac:main
Open

Update PVT registration doc to align with RFC9578#60
ekovac wants to merge 1 commit into
GoogleChrome:mainfrom
ekovac:main

Conversation

@ekovac

@ekovac ekovac commented Jul 28, 2026

Copy link
Copy Markdown
Collaborator

Update PVT-Registration.md to describe the key commitment endpoint format in line with Privacy Pass Issuer Configuration (RFC 9578 Section 4), including issuer-request-uri, token-keys (with token-type, token-key, and optional not-before), Cache-Control header caching, and PVT extensions (version, batch-size, and redeemer-origins).

TAG=agy
CONV=54e39f25-ca42-4f81-90ba-5e1393f4bd1a

… 9578

Update PVT-Registration.md to describe the key commitment endpoint format in line with Privacy Pass Issuer Configuration (RFC 9578 Section 4), including application/private-token-issuer-directory MIME type, issuer-request-uri, token-keys (with token-type, token-key, and optional not-before), Cache-Control header caching, and PVT extensions (version, batch-size, and redeemer-origins).

TAG=agy
CONV=54e39f25-ca42-4f81-90ba-5e1393f4bd1a
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