Script updating gh-pages from 893029c. [ci skip]

Author: ID Bot

262-cwt-typ/draft-ietf-oauth-status-list.html

@@ -1049,7 +1049,7 @@
 </tr></thead>
 <tfoot><tr>
 <td class="left">Looker, et al.</td>
-<td class="center">Expires 13 August 2025</td>
+<td class="center">Expires 18 August 2025</td>
 <td class="right">[Page]</td>
 </tr></tfoot>
 </table>
@@ -1062,12 +1062,12 @@
 <dd class="internet-draft">draft-ietf-oauth-status-list-latest</dd>
 <dt class="label-published">Published:</dt>
 <dd class="published">
-<time datetime="2025-02-09" class="published">9 February 2025</time>
+<time datetime="2025-02-14" class="published">14 February 2025</time>
     </dd>
 <dt class="label-intended-status">Intended Status:</dt>
 <dd class="intended-status">Standards Track</dd>
 <dt class="label-expires">Expires:</dt>
-<dd class="expires"><time datetime="2025-08-13">13 August 2025</time></dd>
+<dd class="expires"><time datetime="2025-08-18">18 August 2025</time></dd>
 <dt class="label-authors">Authors:</dt>
 <dd class="authors">
 <div class="author">
@@ -1124,7 +1124,7 @@ <h2 id="name-status-of-this-memo">
         time. It is inappropriate to use Internet-Drafts as reference
         material or to cite them other than as "work in progress."<a href="#section-boilerplate.1-3" class="pilcrow">¶</a></p>
 <p id="section-boilerplate.1-4">
-        This Internet-Draft will expire on 13 August 2025.<a href="#section-boilerplate.1-4" class="pilcrow">¶</a></p>
+        This Internet-Draft will expire on 18 August 2025.<a href="#section-boilerplate.1-4" class="pilcrow">¶</a></p>
 </section>
 </div>
 <div id="copyright">
@@ -1320,7 +1320,7 @@ <h2 id="name-copyright-notice">
             <p id="section-toc.1-1.13.1"><a href="#section-13" class="auto internal xref">13</a>. <a href="#name-implementation-consideratio" class="internal xref">Implementation Considerations</a></p>
 <ul class="compact toc ulBare ulEmpty">
 <li class="compact toc ulBare ulEmpty" id="section-toc.1-1.13.2.1">
-                <p id="section-toc.1-1.13.2.1.1"><a href="#section-13.1" class="auto internal xref">13.1</a>.  <a href="#name-referenced-token-lifecycle" class="internal xref">Referenced Token Lifecycle</a></p>
+                <p id="section-toc.1-1.13.2.1.1"><a href="#section-13.1" class="auto internal xref">13.1</a>.  <a href="#name-token-lifecycle" class="internal xref">Token Lifecycle</a></p>
 </li>
               <li class="compact toc ulBare ulEmpty" id="section-toc.1-1.13.2.2">
                 <p id="section-toc.1-1.13.2.2.1"><a href="#section-13.2" class="auto internal xref">13.2</a>.  <a href="#name-default-values-and-double-a" class="internal xref">Default Values and Double Allocation</a></p>
@@ -1612,12 +1612,12 @@ <h2 id="name-terminology">
         <dd class="break"></dd>
 <dt id="section-3-1.13">Status List Token:</dt>
         <dd style="margin-left: 1.5em" id="section-3-1.14">
-          <p id="section-3-1.14.1">A token in JWT or CWT representation that contains a cryptographically secured Status List.<a href="#section-3-1.14.1" class="pilcrow">¶</a></p>
+          <p id="section-3-1.14.1">A token in JWT (as defined in <span>[<a href="#RFC7519" class="cite xref">RFC7519</a>]</span>) or CWT (as defined in <span>[<a href="#RFC8392" class="cite xref">RFC8392</a>]</span>) representation that contains a cryptographically secured Status List.<a href="#section-3-1.14.1" class="pilcrow">¶</a></p>
 </dd>
         <dd class="break"></dd>
 <dt id="section-3-1.15">Referenced Token:</dt>
         <dd style="margin-left: 1.5em" id="section-3-1.16">
-          <p id="section-3-1.16.1">A cryptographically secured data structure that contains a reference to a Status List Token. It is <span class="bcp14">RECOMMENDED</span> to use JSON <span>[<a href="#RFC8259" class="cite xref">RFC8259</a>]</span> with JOSE as defined in <span>[<a href="#RFC7515" class="cite xref">RFC7515</a>]</span> or CBOR <span>[<a href="#RFC8949" class="cite xref">RFC8949</a>]</span> with COSE as defined in <span>[<a href="#RFC9052" class="cite xref">RFC9052</a>]</span>. The information from the contained Status List gives the Relying Party additional information about the current status of the Referenced Token. Examples for Referenced Tokens are SD-JWT VC and ISO mdoc.<a href="#section-3-1.16.1" class="pilcrow">¶</a></p>
+          <p id="section-3-1.16.1">A cryptographically secured data structure that contains a "status" claim that is referencing a mechanism to retrieve status information about this Referenced Token. This document defines the Status List mechanism in which case the Referenced Token contains a reference to an entry in a Status List Token. It is <span class="bcp14">RECOMMENDED</span> to use JSON <span>[<a href="#RFC8259" class="cite xref">RFC8259</a>]</span> with JOSE as defined in <span>[<a href="#RFC7515" class="cite xref">RFC7515</a>]</span> or CBOR <span>[<a href="#RFC8949" class="cite xref">RFC8949</a>]</span> with COSE as defined in <span>[<a href="#RFC9052" class="cite xref">RFC9052</a>]</span>. Examples for Referenced Tokens are SD-JWT VC and ISO mdoc.<a href="#section-3-1.16.1" class="pilcrow">¶</a></p>
 </dd>
         <dd class="break"></dd>
 <dt id="section-3-1.17">base64url:</dt>
@@ -1935,9 +1935,9 @@ <h3 id="name-status-list-token-in-cwt-fo">
 d2845820a2012610781a6170706c69636174696f6e2f7374617475736c6973742b63
 7774a1044231325850a502782168747470733a2f2f6578616d706c652e636f6d2f73
 74617475736c697374732f31061a648c5bea041a8898dfea19fffe19a8c019fffda2
-646269747301636c73744a78dadbb918000217015d58406cee0a2e87f2c486b167fa
-2fbf59bd7a90dee1e35b3b227f3e041c7b97aa22a988271ee0da66475bc64bf52fb1
-31be57aa37bf46df3d8d1f91037ec58f48fefb
+646269747301636c73744a78dadbb918000217015d5840989ac537851f95d8413252
+951412078b683ee84ad85d2528164955c99f4d5d9252a0ee6f9510506f737f288c9e
+6859e2f4d88bc22f82e04754436455c9f099b8
 </pre><a href="#section-5.2-9" class="pilcrow">¶</a>
 </div>
 <p id="section-5.2-10">The following is the CBOR Annotated Hex output of the example above:<a href="#section-5.2-10" class="pilcrow">¶</a></p>
@@ -1962,12 +1962,12 @@ <h3 id="name-status-list-token-in-cwt-fo">
       6269747301636c73744a78da  #       "bits\x01clstJxÚ"
       dbb918000217015d          #       "Û¹\x18\x00\x02\x17\x01]"
     58 40                       #     bytes(64)
-      6cee0a2e87f2c486b167fa2f  #       "lî\x0a.\x87òÄ\x86±gú/"
-      bf59bd7a90dee1e35b3b227f  #       "¿Y½z\x90Þáã[;"\x7f"
-      3e041c7b97aa22a988271ee0  #       "&gt;\x04\x1c{\x97ª"©\x88'\x1eà"
-      da66475bc64bf52fb131be57  #       "ÚfG[ÆKõ/±1¾W"
-      aa37bf46df3d8d1f91037ec5  #       "ª7¿Fß=\x8d\x1f\x91\x03~Å"
-      8f48fefb                  #       "\x8fHþû"
+      989ac537851f95d841325295  #       "\x98\x9aÅ7\x85\x1f\x95ØA2R\x95"
+      1412078b683ee84ad85d2528  #       "\x14\x12\x07\x8bh&gt;èJØ]%("
+      164955c99f4d5d9252a0ee6f  #       "\x16IUÉ\x9fM]\x92R\xa0îo"
+      9510506f737f288c9e6859e2  #       "\x95\x10Pos\x7f(\x8c\x9ehYâ"
+      f4d88bc22f82e04754436455  #       "ôØ\x8bÂ/\x82àGTCdU"
+      c9f099b8                  #       "Éð\x99¸"
 </pre><a href="#section-5.2-11" class="pilcrow">¶</a>
 </div>
 </section>
@@ -2109,9 +2109,9 @@ <h3 id="name-referenced-token-in-cose">
 d28443a10126a1044231325866a502653132333435017368747470733a2f2f657861
 6d706c652e636f6d061a648c5bea041a8898dfea19ffffa16b7374617475735f6c69
 7374a2636964780063757269782168747470733a2f2f6578616d706c652e636f6d2f
-7374617475736c697374732f315840311c403a1882d16ae6399e6e69ce49b55e27dd
-6df1b19e49b9b01b15a80ad845605fff2750b502590854966056a5fc0429a758bf7c
-df85595a4208f5c56ddafe
+7374617475736c697374732f3158406661cdb35f3c8993ca53d1d9dc517e8f4cd869
+e302bfd4bba04da51073ad7e25bf255e3fb1c7d11801dee0ec2ec7f908c73bf8b761
+26717f7e9a3c592217aa6b
 </pre><a href="#section-6.3-6" class="pilcrow">¶</a>
 </div>
 <p id="section-6.3-7">The following is the CBOR Annotated Hex output of the example above:<a href="#section-6.3-7" class="pilcrow">¶</a></p>
@@ -2136,12 +2136,12 @@ <h3 id="name-referenced-token-in-cose">
       2e636f6d2f7374617475736c  #       ".com/statusl"
       697374732f31              #       "ists/1"
     58 40                       #     bytes(64)
-      311c403a1882d16ae6399e6e  #       "1\x1c@:\x18\x82Ñjæ9\x9en"
-      69ce49b55e27dd6df1b19e49  #       "iÎIµ^'Ýmñ±\x9eI"
-      b9b01b15a80ad845605fff27  #       "¹°\x1b\x15¨\x0aØE`_ÿ'"
-      50b502590854966056a5fc04  #       "Pµ\x02Y\x08T\x96`V¥ü\x04"
-      29a758bf7cdf85595a4208f5  #       ")§X¿|ß\x85YZB\x08õ"
-      c56ddafe                  #       "ÅmÚþ"
+      6661cdb35f3c8993ca53d1d9  #       "faͳ_&lt;\x89\x93ÊSÑÙ"
+      dc517e8f4cd869e302bfd4bb  #       "ÜQ~\x8fLØiã\x02¿Ô»"
+      a04da51073ad7e25bf255e3f  #       "\xa0M¥\x10s\xad~%¿%^?"
+      b1c7d11801dee0ec2ec7f908  #       "±ÇÑ\x18\x01Þàì.Çù\x08"
+      c73bf8b76126717f7e9a3c59  #       "Ç;ø·a&amp;q\x7f~\x9a&lt;Y"
+      2217aa6b                  #       ""\x17ªk"
 </pre><a href="#section-6.3-8" class="pilcrow">¶</a>
 </div>
 <p id="section-6.3-9">ISO mdoc <span>[<a href="#ISO.mdoc" class="cite xref">ISO.mdoc</a>]</span> may utilize the Status List mechanism by introducing the <code>status</code> parameter in the Mobile Security Object (MSO) as specified in Section 9.1.2. The <code>status</code> parameter uses the same encoding as a CWT as defined in <a href="#referenced-token-cose" class="auto internal xref">Section 6.3</a>.<a href="#section-6.3-9" class="pilcrow">¶</a></p>
@@ -2354,8 +2354,8 @@ <h3 id="name-status-list-request">
 yJleHAiOjIyOTE3MjAxNzAsImlhdCI6MTY4NjkyMDE3MCwiaXNzIjoiaHR0cHM6Ly9le
 GFtcGxlLmNvbSIsInN0YXR1c19saXN0Ijp7ImJpdHMiOjEsImxzdCI6ImVOcmJ1UmdBQ
 WhjQlhRIn0sInN1YiI6Imh0dHBzOi8vZXhhbXBsZS5jb20vc3RhdHVzbGlzdHMvMSIsI
-nR0bCI6NDMyMDB9.6-TiBppmYgdecRZRpUYuG7rQ2hp823aogERrJYPfpByumN4nlSDG
-LDqCMtKPMlIO_His7e7OIdKDcr4nFJ50AA
+nR0bCI6NDMyMDB9.i2eAFqDt1Yi1zK4uLV19HfcfInxQhmwFoMS1KmWnl4E0d-VOAfpi
+D6pPPL8Tjf2u3zE5446KJRfehz1T70iThg
 </pre><a href="#section-8.1-10" class="pilcrow">¶</a>
 </div>
 </section>
@@ -2461,8 +2461,8 @@ <h3 id="name-historical-resolution">
 yJleHAiOjIyOTE3MjAxNzAsImlhdCI6MTY4NjkyMDE3MCwiaXNzIjoiaHR0cHM6Ly9le
 GFtcGxlLmNvbSIsInN0YXR1c19saXN0Ijp7ImJpdHMiOjEsImxzdCI6ImVOcmJ1UmdBQ
 WhjQlhRIn0sInN1YiI6Imh0dHBzOi8vZXhhbXBsZS5jb20vc3RhdHVzbGlzdHMvMSIsI
-nR0bCI6NDMyMDB9.6-TiBppmYgdecRZRpUYuG7rQ2hp823aogERrJYPfpByumN4nlSDG
-LDqCMtKPMlIO_His7e7OIdKDcr4nFJ50AA
+nR0bCI6NDMyMDB9.i2eAFqDt1Yi1zK4uLV19HfcfInxQhmwFoMS1KmWnl4E0d-VOAfpi
+D6pPPL8Tjf2u3zE5446KJRfehz1T70iThg
 </pre><a href="#section-8.4-7" class="pilcrow">¶</a>
 </div>
 </section>
@@ -2806,12 +2806,12 @@ <h2 id="name-implementation-consideratio">
       </h2>
 <div id="implementation-lifecycle">
 <section id="section-13.1">
-        <h3 id="name-referenced-token-lifecycle">
-<a href="#section-13.1" class="section-number selfRef">13.1. </a><a href="#name-referenced-token-lifecycle" class="section-name selfRef">Referenced Token Lifecycle</a>
+        <h3 id="name-token-lifecycle">
+<a href="#section-13.1" class="section-number selfRef">13.1. </a><a href="#name-token-lifecycle" class="section-name selfRef">Token Lifecycle</a>
         </h3>
 <p id="section-13.1-1">The lifetime of a Status List Token depends on the lifetime of its Referenced Tokens. Once all Referenced Tokens are expired, the Issuer may stop serving the Status List Token.<a href="#section-13.1-1" class="pilcrow">¶</a></p>
 <p id="section-13.1-2">Referenced Tokens may be regularly re-issued to mitigate the linkability of presentations to Relying Parties. In this case, every re-issued Referenced Token <span class="bcp14">MUST</span> have a fresh Status List entry in order to prevent this from becoming a possible source of correlation.<a href="#section-13.1-2" class="pilcrow">¶</a></p>
-<p id="section-13.1-3">Referenced Tokens may also be issued in batches, such that Holders can use individual tokens for every transaction. In this case, every Referenced Token <span class="bcp14">MUST</span> have a dedicated Status List entry. Revoking batch-issued Referenced Tokens might reveal this correlation later on.<a href="#section-13.1-3" class="pilcrow">¶</a></p>
+<p id="section-13.1-3">Referenced Tokens may also be issued in batches and be presented by Holders in a one-time-use policy to avoid linkability. In this case, every Referenced Token <span class="bcp14">MUST</span> have a dedicated Status List entry and <span class="bcp14">MAY</span> be spread across multiple Status Lists. Revoking batch-issued Referenced Tokens might reveal this correlation later on.<a href="#section-13.1-3" class="pilcrow">¶</a></p>
 </section>
 </div>
 <div id="default-values-and-double-allocation">
@@ -4246,6 +4246,9 @@ <h2 id="name-document-history">
 <ul class="normal">
 <li class="normal" id="appendix-C-2.1">
           <p id="appendix-C-2.1.1">Fix cwt typ value to full media type<a href="#appendix-C-2.1.1" class="pilcrow">¶</a></p>
+</li>
+        <li class="normal" id="appendix-C-2.2">
+          <p id="appendix-C-2.2.1">Update terminology for referenced token and Status List Token<a href="#appendix-C-2.2.1" class="pilcrow">¶</a></p>
 </li>
       </ul>
 <p id="appendix-C-3">-07<a href="#appendix-C-3" class="pilcrow">¶</a></p>