Script updating gh-pages from 474ba4f. [ci skip]

PieterKas-patch-1/draft-ietf-oauth-transaction-tokens.html

@@ -11,14 +11,14 @@
 <meta content="
        Transaction Tokens (Txn-Tokens) enable workloads in a trusted domain to ensure that user identity and authorization context of an external programmatic request, such as an API invocation, are preserved and available to all workloads that are invoked as part of processing such a request. Txn-Tokens also enable workloads within the trusted domain to optionally immutably assert to downstream workloads that they were invoked in the call chain of the request. 
     " name="description">
-<meta content="xml2rfc 3.25.0" name="generator">
+<meta content="xml2rfc 3.26.0" name="generator">
 <meta content="Microservices" name="keyword">
 <meta content="OAuth" name="keyword">
 <meta content="JWT" name="keyword">
 <meta content="token exchange" name="keyword">
 <meta content="draft-ietf-oauth-transaction-tokens-latest" name="ietf.draft">
 <!-- Generator version information:
-  xml2rfc 3.25.0
+  xml2rfc 3.26.0
     Python 3.12.8
     ConfigArgParse 1.7
     google-i18n-address 3.1.1
@@ -1049,11 +1049,11 @@
 <thead><tr>
 <td class="left">Internet-Draft</td>
 <td class="center">Txn-Tokens</td>
-<td class="right">January 2025</td>
+<td class="right">February 2025</td>
 </tr></thead>
 <tfoot><tr>
 <td class="left">Tulshibagwale, et al.</td>
-<td class="center">Expires 4 August 2025</td>
+<td class="center">Expires 17 August 2025</td>
 <td class="right">[Page]</td>
 </tr></tfoot>
 </table>
@@ -1066,12 +1066,12 @@
 <dd class="internet-draft">draft-ietf-oauth-transaction-tokens-latest</dd>
 <dt class="label-published">Published:</dt>
 <dd class="published">
-<time datetime="2025-01-31" class="published">31 January 2025</time>
+<time datetime="2025-02-13" class="published">13 February 2025</time>
     </dd>
 <dt class="label-intended-status">Intended Status:</dt>
 <dd class="intended-status">Informational</dd>
 <dt class="label-expires">Expires:</dt>
-<dd class="expires"><time datetime="2025-08-04">4 August 2025</time></dd>
+<dd class="expires"><time datetime="2025-08-17">17 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 4 August 2025.<a href="#section-boilerplate.1-4" class="pilcrow">¶</a></p>
+        This Internet-Draft will expire on 17 August 2025.<a href="#section-boilerplate.1-4" class="pilcrow">¶</a></p>
 </section>
 </div>
 <div id="copyright">
@@ -2285,7 +2285,7 @@ <h3 id="name-identifying-call-chains">
         <h3 id="name-transaction-token-service-d">
 <a href="#section-9.8" class="section-number selfRef">9.8. </a><a href="#name-transaction-token-service-d" class="section-name selfRef">Transaction Token Service Discovery</a>
         </h3>
-<p id="section-9.8-1">A workload may use a variety of mechanisms to determine the Transaction Token Service it should interact with. Workloads should only retrieve configuration information indicating which Transaction Token Service it should interact with from a trusted location to  minimize the risk of a threat actor inserting configuration information pointing to a Transaction Token Service under it's control, which it may use to collect Access Tokens sent to it as part of the Txn-Token Request message. The workload should authenticate the service providing the configuration information and verify the integrity of the information to prevent a threat actor from inserting configuration information for a Trust Domain Service under its control. The wokrload may use TLS to authenticate the end-point and protect the request at the transport layer, and may use additional application layer signatures or message authentication codes to detect tampering with the configuration information.<a href="#section-9.8-1" class="pilcrow">¶</a></p>
+<p id="section-9.8-1">A workload may use a variety of mechanisms to determine the Transaction Token Service it should interact with. Workloads should only retrieve configuration information indicating which Transaction Token Service it should interact with from a trusted location to  minimize the risk of a threat actor inserting configuration information pointing to a Transaction Token Service under it's control, which it may use to collect Access Tokens sent to it as part of the Txn-Token Request message. The workload should authenticate the service providing the configuration information and verify the integrity of the information to prevent a threat actor from inserting configuration information for a Trust Domain Service under its control. The workload may use TLS to authenticate the end-point and protect the request at the transport layer, and may use additional application layer signatures or message authentication codes to detect tampering with the configuration information.<a href="#section-9.8-1" class="pilcrow">¶</a></p>
 </section>
 </div>
 <div id="workload-configuration-protection">

PieterKas-patch-1/draft-ietf-oauth-transaction-tokens.txt

@@ -5,10 +5,10 @@
 oauth                                                   A. Tulshibagwale
 Internet-Draft                                                      SGNL
 Intended status: Informational                               G. Fletcher
-Expires: 4 August 2025                                       Capital One
+Expires: 17 August 2025                                      Capital One
                                                             P. Kasselman
                                                                    SPIRL
-                                                         31 January 2025
+                                                        13 February 2025
 
 
                            Transaction Tokens
@@ -52,7 +52,7 @@ 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."
 
-   This Internet-Draft will expire on 4 August 2025.
+   This Internet-Draft will expire on 17 August 2025.
 
 Copyright Notice
 
@@ -1040,8 +1040,8 @@ Table of Contents
 9.6.  Scope and Purpose processing
 
    The authorization model within a trust domain boundary is most often
-   quite different from the authorization model (e.g.  OAuth scopes)
-   used with clients external to the trust domain.  This makes managing
+   quite different from the authorization model (e.g. OAuth scopes) used
+   with clients external to the trust domain.  This makes managing
    unintentional scope increase a critical aspect of the Transaction
    Token Service.  The TTS MUST ensure that the requested purpose
    (scope) of the Txn-Token is equal or less than the scope(s)
@@ -1072,7 +1072,7 @@ Table of Contents
    the service providing the configuration information and verify the
    integrity of the information to prevent a threat actor from inserting
    configuration information for a Trust Domain Service under its
-   control.  The wokrload may use TLS to authenticate the end-point and
+   control.  The workload may use TLS to authenticate the end-point and
    protect the request at the transport layer, and may use additional
    application layer signatures or message authentication codes to
    detect tampering with the configuration information.

index.html

@@ -24,14 +24,6 @@ <h1>Editor's drafts for main branch of <a href="https://github.com/oauth-wg/oaut
         <td></td>
       </tr>
     </table>
-    <h2>Preview for branch <a href="terminology-cleanup">terminology-cleanup</a></h2>
-    <table id="branch-terminology-cleanup">
-      <tr>
-        <td><a href="terminology-cleanup/draft-ietf-oauth-transaction-tokens.html" class="html draft-ietf-oauth-transaction-tokens" title="Transaction Tokens (HTML)">Txn-Tokens</a></td>
-        <td><a href="terminology-cleanup/draft-ietf-oauth-transaction-tokens.txt" class="txt draft-ietf-oauth-transaction-tokens" title="Transaction Tokens (Text)">plain text</a></td>
-        <td><a href="https://author-tools.ietf.org/api/iddiff?url_1=https://oauth-wg.github.io/oauth-transaction-tokens/draft-ietf-oauth-transaction-tokens.txt&amp;url_2=https://oauth-wg.github.io/oauth-transaction-tokens/terminology-cleanup/draft-ietf-oauth-transaction-tokens.txt" class="diff draft-ietf-oauth-transaction-tokens">diff with main</a></td>
-      </tr>
-    </table>
     <h2>Preview for branch <a href="PieterKas-patch-1">PieterKas-patch-1</a></h2>
     <table id="branch-PieterKas-patch-1">
       <tr>
@@ -40,6 +32,14 @@ <h2>Preview for branch <a href="PieterKas-patch-1">PieterKas-patch-1</a></h2>
         <td><a href="https://author-tools.ietf.org/api/iddiff?url_1=https://oauth-wg.github.io/oauth-transaction-tokens/draft-ietf-oauth-transaction-tokens.txt&amp;url_2=https://oauth-wg.github.io/oauth-transaction-tokens/PieterKas-patch-1/draft-ietf-oauth-transaction-tokens.txt" class="diff draft-ietf-oauth-transaction-tokens">diff with main</a></td>
       </tr>
     </table>
+    <h2>Preview for branch <a href="terminology-cleanup">terminology-cleanup</a></h2>
+    <table id="branch-terminology-cleanup">
+      <tr>
+        <td><a href="terminology-cleanup/draft-ietf-oauth-transaction-tokens.html" class="html draft-ietf-oauth-transaction-tokens" title="Transaction Tokens (HTML)">Txn-Tokens</a></td>
+        <td><a href="terminology-cleanup/draft-ietf-oauth-transaction-tokens.txt" class="txt draft-ietf-oauth-transaction-tokens" title="Transaction Tokens (Text)">plain text</a></td>
+        <td><a href="https://author-tools.ietf.org/api/iddiff?url_1=https://oauth-wg.github.io/oauth-transaction-tokens/draft-ietf-oauth-transaction-tokens.txt&amp;url_2=https://oauth-wg.github.io/oauth-transaction-tokens/terminology-cleanup/draft-ietf-oauth-transaction-tokens.txt" class="diff draft-ietf-oauth-transaction-tokens">diff with main</a></td>
+      </tr>
+    </table>
     <h2>Preview for branch <a href="fix-build">fix-build</a></h2>
     <table id="branch-fix-build">
       <tr>