Skip to content

Commit 93634a3

Browse files
authored
Add additional issues to privacy considerations (#287)
1 parent 0c0ca7a commit 93634a3

File tree

1 file changed

+10
-4
lines changed

1 file changed

+10
-4
lines changed

index.html

Lines changed: 10 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -967,6 +967,7 @@ <h3>
967967
<h4>
968968
Exchange Protocol Considerations for User Privacy
969969
</h4>
970+
<aside class="issue" data-number="255"></aside>
970971
<h5>
971972
Selective disclosure
972973
</h5>
@@ -1057,7 +1058,7 @@ <h5>
10571058
<h5>
10581059
Unlinkable revocation
10591060
</h5>
1060-
<p class="issue" data-number="280">
1061+
<p>
10611062
A common instance of issuer involvement in a credential exchange is
10621063
for credential revocation checks. This is particularly challenging
10631064
when presentations are intended to be verifier-issuer unlinkable.
@@ -1114,9 +1115,7 @@ <h5>
11141115
protocols are required to support and mandate encrypted responses in
11151116
a credential exchange.
11161117
</p>
1117-
<p class="issue" data-number="255">
1118-
Actually write these in the protocol requirements
1119-
</p>
1118+
<p class="issue" data-number="109"></p>
11201119
</section>
11211120
<section>
11221121
<h3>
@@ -1234,6 +1233,13 @@ <h3>
12341233
Should the API be designed so the site can provide in-context
12351234
explanations?
12361235
</p>
1236+
<h4>
1237+
Handling multiple credential requests
1238+
</h4>
1239+
<p class="issue" data-number="286">
1240+
We need to describe concerns, tradeoffs and possible mitigations of
1241+
handling multiple requests and responses for credential presentation.
1242+
</p>
12371243
<h4 id="multiple-user-agents">
12381244
Integrating Multiple User Agents
12391245
</h4>

0 commit comments

Comments
 (0)