Script updating gh-pages from 63af06f. [ci skip]

Author: ID Bot

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

@@ -9,7 +9,7 @@
 <meta content="Paul Bastian" name="author">
 <meta content="Christian Bormann" name="author">
 <meta content="
-       This specification defines a status mechanism called Token Status List (TSL), data structures and processing rules for representing the status of tokens secured by JSON Object Signing and Encryption (JOSE) or CBOR Object Signing and Encryption (COSE), such as JWT, SD-JWT VC, CBOR Web Token, and ISO mdoc. It also defines an extension point and a registry for future status mechanisms. 
+       This specification defines a status mechanism called Token Status List (TSL), data structures and processing rules for representing the status of tokens secured by JSON Object Signing and Encryption (JOSE) or CBOR Object Signing and Encryption (COSE), such as JWT, SD-JWT, CBOR Web Token, and ISO mdoc. It also defines an extension point and a registry for future status mechanisms. 
     " name="description">
 <meta content="xml2rfc 3.31.0" name="generator">
 <meta content="draft-ietf-oauth-status-list-latest" name="ietf.draft">
@@ -1088,7 +1088,7 @@
 <h1 id="title">Token Status List (TSL)</h1>
 <section id="section-abstract">
       <h2 id="abstract"><a href="#abstract" class="selfRef">Abstract</a></h2>
-<p id="section-abstract-1">This specification defines a status mechanism called Token Status List (TSL), data structures and processing rules for representing the status of tokens secured by JSON Object Signing and Encryption (JOSE) or CBOR Object Signing and Encryption (COSE), such as JWT, SD-JWT VC, CBOR Web Token, and ISO mdoc. It also defines an extension point and a registry for future status mechanisms.<a href="#section-abstract-1" class="pilcrow">¶</a></p>
+<p id="section-abstract-1">This specification defines a status mechanism called Token Status List (TSL), data structures and processing rules for representing the status of tokens secured by JSON Object Signing and Encryption (JOSE) or CBOR Object Signing and Encryption (COSE), such as JWT, SD-JWT, CBOR Web Token, and ISO mdoc. It also defines an extension point and a registry for future status mechanisms.<a href="#section-abstract-1" class="pilcrow">¶</a></p>
 </section>
 <section class="note rfcEditorRemove" id="section-note.1">
       <h2 id="name-about-this-document">
@@ -1645,7 +1645,7 @@ <h2 id="name-terminology">
         <dd class="break"></dd>
 <dt id="section-3-1.17">Referenced Token:</dt>
         <dd style="margin-left: 1.5em" id="section-3-1.18">
-          <p id="section-3-1.18.1">A cryptographically secured data structure that contains a "status" claim that references 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.18.1" class="pilcrow">¶</a></p>
+          <p id="section-3-1.18.1">A cryptographically secured data structure that contains a "status" claim that references 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 and ISO mdoc.<a href="#section-3-1.18.1" class="pilcrow">¶</a></p>
 </dd>
         <dd class="break"></dd>
 <dt id="section-3-1.19">Client:</dt>

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

@@ -19,7 +19,7 @@ Abstract
    This specification defines a status mechanism called Token Status
    List (TSL), data structures and processing rules for representing the
    status of tokens secured by JSON Object Signing and Encryption (JOSE)
-   or CBOR Object Signing and Encryption (COSE), such as JWT, SD-JWT VC,
+   or CBOR Object Signing and Encryption (COSE), such as JWT, SD-JWT,
    CBOR Web Token, and ISO mdoc.  It also defines an extension point and
    a registry for future status mechanisms.
 
@@ -386,7 +386,7 @@ Table of Contents
       Token contains a reference to an entry in a Status List Token.  It
       is RECOMMENDED to use JSON [RFC8259] with JOSE as defined in
       [RFC7515] or CBOR [RFC8949] with COSE as defined in [RFC9052].
-      Examples for Referenced Tokens are SD-JWT VC and ISO mdoc.
+      Examples for Referenced Tokens are SD-JWT and ISO mdoc.
 
    Client:  An application that fetches information, such as a Status
       List Token, from the Status List Provider on behalf of the Holder