Script updating gh-pages from 5a6969d. [ci skip]

ietf-wg-wimse · Oct 14, 2024 · 759fddb · 759fddb
1 parent 3feb94c
commit 759fddb
Show file tree

Hide file tree

Showing 2 changed files with 13 additions and 13 deletions.
diff --git a/arndt/add_wit_binding/draft-ietf-wimse-s2s-protocol.html b/arndt/add_wit_binding/draft-ietf-wimse-s2s-protocol.html
@@ -1043,7 +1043,7 @@
 </tr></thead>
 <tfoot><tr>
 <td class="left">Campbell, et al.</td>
-<td class="center">Expires 14 April 2025</td>
+<td class="center">Expires 17 April 2025</td>
 <td class="right">[Page]</td>
 </tr></tfoot>
 </table>
@@ -1056,12 +1056,12 @@
 <dd class="internet-draft">draft-ietf-wimse-s2s-protocol-latest</dd>
 <dt class="label-published">Published:</dt>
 <dd class="published">
-<time datetime="2024-10-11" class="published">11 October 2024</time>
+<time datetime="2024-10-14" class="published">14 October 2024</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-04-14">14 April 2025</time></dd>
+<dd class="expires"><time datetime="2025-04-17">17 April 2025</time></dd>
 <dt class="label-authors">Authors:</dt>
 <dd class="authors">
 <div class="author">
@@ -1137,7 +1137,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 14 April 2025.<a href="#section-boilerplate.1-4" class="pilcrow">¶</a></p>
+        This Internet-Draft will expire on 17 April 2025.<a href="#section-boilerplate.1-4" class="pilcrow">¶</a></p>
 </section>
 </div>
 <div id="copyright">
@@ -1649,8 +1649,8 @@ <h3 id="name-option-1-dpop-inspired-auth">
                 <p id="section-4.2-2.2.2.4.1"><code>jti</code>: A unique identifier for the token.<a href="#section-4.2-2.2.2.4.1" class="pilcrow">¶</a></p>
 </li>
               <li class="normal" id="section-4.2-2.2.2.5">
-                <p id="section-4.2-2.2.2.5.1"><code>wth</code>: Hash of the Workload Identity Token. The value, as defined in <a href="#to-wit" class="auto internal xref">Section 4.1</a>, is the base64url encoding of the SHA-256
-   hash of the ASCII encoding of the token's value.<a href="#section-4.2-2.2.2.5.1" class="pilcrow">¶</a></p>
+                <p id="section-4.2-2.2.2.5.1"><code>wth</code>: Hash of the Workload Identity Token, defined in <a href="#to-wit" class="auto internal xref">Section 4.1</a>. The value is the base64url encoding of the
+   SHA-256 hash of the ASCII encoding of the token's value.<a href="#section-4.2-2.2.2.5.1" class="pilcrow">¶</a></p>
 </li>
               <li class="normal" id="section-4.2-2.2.2.6">
                 <p id="section-4.2-2.2.2.6.1"><code>ath</code>: Hash of the OAuth access token, if present in the request, which might convey end-user identity and
@@ -2053,7 +2053,7 @@ <h2 id="name-iana-considerations">
 <a href="#section-7" class="section-number selfRef">7. </a><a href="#name-iana-considerations" class="section-name selfRef">IANA Considerations</a>
       </h2>
 <p id="section-7-1">TODO: maybe a URI Scheme registration of <code>wimse</code> in <a href="https://www.iana.org/assignments/uri-schemes/uri-schemes.xhtml">URI schemes</a> per <span>[<a href="#RFC7595" class="cite xref">RFC7595</a>]</span> but it's only being used in an example right now and might not even be appropriate. Or maybe use an ietf URI scheme a la <a href="https://www.iana.org/assignments/params/params.xhtml">URN Namespace for IETF Use</a> somehow. Or maybe nothing. Or maybe something else.<a href="#section-7-1" class="pilcrow">¶</a></p>
-<p id="section-7-2">TODO: <code>tth</code> and maybe <code>oth</code> claim in <a href="https://www.iana.org/assignments/jwt/jwt.xhtml">JSON Web Token Claims Registry</a><a href="#section-7-2" class="pilcrow">¶</a></p>
+<p id="section-7-2">TODO: <code>tth</code>, <code>wth</code> and maybe <code>oth</code> claim in <a href="https://www.iana.org/assignments/jwt/jwt.xhtml">JSON Web Token Claims Registry</a><a href="#section-7-2" class="pilcrow">¶</a></p>
 <div id="media-type-registration">
 <section id="section-7.1">
         <h3 id="name-media-type-registration">

diff --git a/arndt/add_wit_binding/draft-ietf-wimse-s2s-protocol.txt b/arndt/add_wit_binding/draft-ietf-wimse-s2s-protocol.txt
@@ -5,14 +5,14 @@
 Workload Identity in Multi System Environments               B. Campbell
 Internet-Draft                                             Ping Identity
 Intended status: Standards Track                              D. Feldman
-Expires: 14 April 2025                                       Independent
+Expires: 17 April 2025                                       Independent
                                                               J. Salowey
                                                                   Venafi
                                                       A. Schwenkschuster
                                                                Microsoft
                                                               Y. Sheffer
                                                                   Intuit
-                                                         11 October 2024
+                                                         14 October 2024
 
 
                 WIMSE Service to Service Authentication
@@ -68,7 +68,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 14 April 2025.
+   This Internet-Draft will expire on 17 April 2025.
 
 Copyright Notice
 
@@ -448,8 +448,8 @@ Table of Contents
 
       -  jti: A unique identifier for the token.
 
-      -  wth: Hash of the Workload Identity Token.  The value, as
-         defined in Section 4.1, is the base64url encoding of the
+      -  wth: Hash of the Workload Identity Token, defined in
+         Section 4.1.  The value is the base64url encoding of the
          SHA-256 hash of the ASCII encoding of the token's value.
 
       -  ath: Hash of the OAuth access token, if present in the request,
@@ -871,7 +871,7 @@ Table of Contents
    Namespace for IETF Use (https://www.iana.org/assignments/params/
    params.xhtml) somehow.  Or maybe nothing.  Or maybe something else.
 
-   TODO: tth and maybe oth claim in JSON Web Token Claims Registry
+   TODO: tth, wth and maybe oth claim in JSON Web Token Claims Registry
    (https://www.iana.org/assignments/jwt/jwt.xhtml)
 
 7.1.  Media Type Registration