Skip to content

Commit

Permalink
Merge pull request #486 from ietf-wg-privacypass/caw/secdir-protocol
Browse files Browse the repository at this point in the history
  • Loading branch information
tfpauly authored Sep 14, 2023
2 parents c02d9d5 + 5f0e43d commit 3064945
Showing 1 changed file with 13 additions and 6 deletions.
19 changes: 13 additions & 6 deletions draft-ietf-privacypass-protocol.md
Original file line number Diff line number Diff line change
Expand Up @@ -710,9 +710,11 @@ based on the VOPRF defined in {{OPRF}} and blind RSA protocol defined in
{{BLINDRSA}}. All security considerations described in the VOPRF and blind RSA
documents also apply in the Privacy Pass use-case. Considerations related to
broader privacy and security concerns in a multi-Client and multi-Issuer
setting are deferred to the Architecture document {{ARCHITECTURE}}. In
particular, {{Section 4 and Section 5 of ARCHITECTURE}} discuss relevant
privacy considerations. Notable considerations include those pertaining to
setting are deferred to the architecture document {{ARCHITECTURE}}. In
particular, {{Section 4 and Section 5 of ARCHITECTURE}} discuss
relevant privacy considerations influenced by the Privacy Pass deployment
model, and {{Section 6 of ARCHITECTURE}} discusses privacy considerations that
apply regardless of deployment model. Notable considerations include those pertaining to
Issuer Public Key rotation and consistency, where consistency is as described
in {{?CONSISTENCY=I-D.ietf-privacypass-key-consistency}}, and Issuer selection.

Expand Down Expand Up @@ -815,7 +817,10 @@ Published specification:

Applications that use this media type:

: N/A
: Services that implement the Privacy Pass issuer role, and client
applications that interact with the issuer for the purposes of
issuing or redeeming tokens.


Fragment identifier considerations:

Expand Down Expand Up @@ -887,7 +892,8 @@ Published specification:

Applications that use this media type:

: N/A
: Applications that want to issue or facilitate issuance of Privacy Pass tokens,
including Privacy Pass issuer applications themselves.

Fragment identifier considerations:

Expand Down Expand Up @@ -959,7 +965,8 @@ Published specification:

Applications that use this media type:

: N/A
: Applications that want to issue or facilitate issuance of Privacy Pass tokens,
including Privacy Pass issuer applications themselves.

Fragment identifier considerations:

Expand Down

0 comments on commit 3064945

Please sign in to comment.