Skip to content

Commit 9ac2c70

Browse files
author
ID Bot
committed
Script updating gh-pages from 660506d. [ci skip]
1 parent 6d9ed3b commit 9ac2c70

2 files changed

Lines changed: 11 additions & 4 deletions

File tree

pb/ref_sd_jwt_instead_of_vc/draft-ietf-oauth-status-list.html

Lines changed: 4 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -2313,7 +2313,7 @@ <h3 id="name-status-list-response">
23132313
<h3 id="name-validation-rules">
23142314
<a href="#section-8.3" class="section-number selfRef">8.3. </a><a href="#name-validation-rules" class="section-name selfRef">Validation Rules</a>
23152315
</h3>
2316-
<p id="section-8.3-1">Upon receiving a Referenced Token, a Relying Party <span class="bcp14">MUST</span> first perform the validation of the Referenced Token - e.g., checking for expected attributes, valid signature and expiration time. The processing rules for Referenced Tokens (such as JWT or CWT) <span class="bcp14">MUST</span> precede any evaluation of a Referenced Token's status. For example, if a token is evaluated as being expired through the "exp" (Expiration Time) but also has a status of 0x00 ("VALID"), the token is considered expired. As this is out of scope for this document, this validation is not described here, but is expected to be done according to the format of the Referenced Token.<a href="#section-8.3-1" class="pilcrow"></a></p>
2316+
<p id="section-8.3-1">Upon receiving a Referenced Token, a Relying Party <span class="bcp14">MUST</span> first perform the validation of the Referenced Token - e.g., checking for expected attributes, valid signature and expiration time. The processing rules for Referenced Tokens (such as JWT or CWT) <span class="bcp14">MUST</span> precede any evaluation of a Referenced Token's status. For example, if a token is evaluated as being expired through the "exp" (Expiration Time) but also has a status of 0x00 ("VALID"), the token is considered expired. If the validation procedures for the Referenced Token determine it is invalid, no further procedures regarding Status List <span class="bcp14">MUST</span> be performed, e.g. fetching a Status List Token, unless the Referenced Token procedures or the use case require further evaluation.<a href="#section-8.3-1" class="pilcrow"></a></p>
23172317
<p id="section-8.3-2">If this validation is not successful, the Referenced Token <span class="bcp14">MUST</span> be rejected. If the validation was successful, the Relying Party <span class="bcp14">MUST</span> perform the following validation steps to evaluate the status of the Referenced Token:<a href="#section-8.3-2" class="pilcrow"></a></p>
23182318
<ol start="1" type="1" class="normal type-1" id="section-8.3-3">
23192319
<li id="section-8.3-3.1">
@@ -4521,6 +4521,9 @@ <h2 id="name-document-history">
45214521
<ul class="normal">
45224522
<li class="normal" id="appendix-D-3.1">
45234523
<p id="appendix-D-3.1.1">change SD-JWT VC reference to SD-JWT<a href="#appendix-D-3.1.1" class="pilcrow"></a></p>
4524+
</li>
4525+
<li class="normal" id="appendix-D-3.2">
4526+
<p id="appendix-D-3.2.1">clarify that Status List validation <span class="bcp14">MUST</span> not be performed if Referenced Token validation is deemed invalid already<a href="#appendix-D-3.2.1" class="pilcrow"></a></p>
45244527
</li>
45254528
</ul>
45264529
<p id="appendix-D-4">-16<a href="#appendix-D-4" class="pilcrow"></a></p>

pb/ref_sd_jwt_instead_of_vc/draft-ietf-oauth-status-list.txt

Lines changed: 7 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -1093,9 +1093,10 @@ d2 # tag(18)
10931093
evaluation of a Referenced Token's status. For example, if a token
10941094
is evaluated as being expired through the "exp" (Expiration Time) but
10951095
also has a status of 0x00 ("VALID"), the token is considered expired.
1096-
As this is out of scope for this document, this validation is not
1097-
described here, but is expected to be done according to the format of
1098-
the Referenced Token.
1096+
If the validation procedures for the Referenced Token determine it is
1097+
invalid, no further procedures regarding Status List MUST be
1098+
performed, e.g. fetching a Status List Token, unless the Referenced
1099+
Token procedures or the use case require further evaluation.
10991100

11001101
If this validation is not successful, the Referenced Token MUST be
11011102
rejected. If the validation was successful, the Relying Party MUST
@@ -3107,6 +3108,9 @@ Document History
31073108

31083109
* change SD-JWT VC reference to SD-JWT
31093110

3111+
* clarify that Status List validation MUST not be performed if
3112+
Referenced Token validation is deemed invalid already
3113+
31103114
-16
31113115

31123116
* change http status codes & query parameter wording for the

0 commit comments

Comments
 (0)