Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Mark uses of SD-JWT-VC as being at risk #251

Merged
merged 2 commits into from
Mar 6, 2024
Merged

Mark uses of SD-JWT-VC as being at risk #251

Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
2bd7e63
Mark uses of SD-JWT-VC as being at risk
selfissued Feb 29, 2024
f682c85
Well Known -> Well-Known
selfissued Feb 29, 2024
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
12 changes: 9 additions & 3 deletions index.html
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -760,8 +760,8 @@ <h2>Key Discovery</h2>
as described in [[SD-JWT-VC]].
</p>

<p class="issue" title="(AT RISK) Feature depends on demonstration of independent implementations" data-number="160">
This normative statement depends on the IETF OAUTH working group adopted draft [[SD-JWT-VC]].
<p class="issue" title="(AT RISK) Feature depends on demonstration of independent implementations">
This normative statement depends on the IETF OAuth working group draft [[SD-JWT-VC]].
This feature is at risk and will be removed from the specification if at least
two independent, interoperable implementations are not demonstrated.
</p>
Expand Down Expand Up @@ -832,7 +832,7 @@ <h2>cnf</h2>
</section>

<section>
<h2>Well Known URIs</h2>
<h2>Well-Known URIs</h2>
<p class="issue" data-number="160">
The working group is currently exploring how
<a data-cite="RFC5785#section-3">Defining Well-Known Uniform Resource Identifiers (URIs)</a>
Expand All @@ -848,6 +848,12 @@ <h2>JWT Issuer</h2>
issuer metadata including the issuer's public keys can be retrieved using the mechanism
defined in [[SD-JWT-VC]].
</p>

<p class="issue" title="(AT RISK) Feature depends on demonstration of independent implementations">
This normative statement depends on the IETF OAuth working group draft [[SD-JWT-VC]].
This feature is at risk and will be removed from the specification if at least
two independent, interoperable implementations are not demonstrated.
</p>
</section>
</section>
<section>
Expand Down
Loading