File tree Expand file tree Collapse file tree 1 file changed +10
-4
lines changed Expand file tree Collapse file tree 1 file changed +10
-4
lines changed Original file line number Diff line number Diff line change 967
967
< h4 >
968
968
Exchange Protocol Considerations for User Privacy
969
969
</ h4 >
970
+ < aside class ="issue " data-number ="255 "> </ aside >
970
971
< h5 >
971
972
Selective disclosure
972
973
</ h5 >
@@ -1057,7 +1058,7 @@ <h5>
1057
1058
< h5 >
1058
1059
Unlinkable revocation
1059
1060
</ h5 >
1060
- < p class =" issue " data-number =" 280 " >
1061
+ < p >
1061
1062
A common instance of issuer involvement in a credential exchange is
1062
1063
for credential revocation checks. This is particularly challenging
1063
1064
when presentations are intended to be verifier-issuer unlinkable.
@@ -1114,9 +1115,7 @@ <h5>
1114
1115
protocols are required to support and mandate encrypted responses in
1115
1116
a credential exchange.
1116
1117
</ 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 >
1120
1119
</ section >
1121
1120
< section >
1122
1121
< h3 >
@@ -1234,6 +1233,13 @@ <h3>
1234
1233
Should the API be designed so the site can provide in-context
1235
1234
explanations?
1236
1235
</ 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 >
1237
1243
< h4 id ="multiple-user-agents ">
1238
1244
Integrating Multiple User Agents
1239
1245
</ h4 >
You can’t perform that action at this time.
0 commit comments