Script updating gh-pages from e0d2140. [ci skip]

ietf-tapswg · Nov 9, 2023 · efa1dc4 · efa1dc4
1 parent 27252b5
commit efa1dc4
Show file tree

Hide file tree

Showing 7 changed files with 34 additions and 35 deletions.
diff --git a/mw-api-encryption/draft-ietf-taps-arch.html b/mw-api-encryption/draft-ietf-taps-arch.html
@@ -1033,7 +1033,7 @@
 </tr></thead>
 <tfoot><tr>
 <td class="left">Pauly, et al.</td>
-<td class="center">Expires 4 May 2024</td>
+<td class="center">Expires 12 May 2024</td>
 <td class="right">[Page]</td>
 </tr></tfoot>
 </table>
@@ -1046,12 +1046,12 @@
 <dd class="internet-draft">draft-ietf-taps-arch-latest</dd>
 <dt class="label-published">Published:</dt>
 <dd class="published">
-<time datetime="2023-11-01" class="published">1 November 2023</time>
+<time datetime="2023-11-09" class="published">9 November 2023</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="2024-05-04">4 May 2024</time></dd>
+<dd class="expires"><time datetime="2024-05-12">12 May 2024</time></dd>
 <dt class="label-authors">Authors:</dt>
 <dd class="authors">
 <div class="author">
@@ -1103,7 +1103,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 May 2024.<a href="#section-boilerplate.1-4" class="pilcrow">¶</a></p>
+        This Internet-Draft will expire on 12 May 2024.<a href="#section-boilerplate.1-4" class="pilcrow">¶</a></p>
 </section>
 </div>
 <div id="copyright">

diff --git a/mw-api-encryption/draft-ietf-taps-arch.txt b/mw-api-encryption/draft-ietf-taps-arch.txt
@@ -5,14 +5,14 @@
 TAPS Working Group                                         T. Pauly, Ed.
 Internet-Draft                                                Apple Inc.
 Intended status: Standards Track                        B. Trammell, Ed.
-Expires: 4 May 2024                              Google Switzerland GmbH
+Expires: 12 May 2024                             Google Switzerland GmbH
                                                             A. Brunstrom
                                                      Karlstad University
                                                             G. Fairhurst
                                                   University of Aberdeen
                                                               C. Perkins
                                                    University of Glasgow
-                                                         1 November 2023
+                                                         9 November 2023
 
 
           Architecture and Requirements for Transport Services
@@ -48,7 +48,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 May 2024.
+   This Internet-Draft will expire on 12 May 2024.
 
 Copyright Notice
 

diff --git a/mw-api-encryption/draft-ietf-taps-impl.html b/mw-api-encryption/draft-ietf-taps-impl.html
@@ -1035,7 +1035,7 @@
 </tr></thead>
 <tfoot><tr>
 <td class="left">Brunstrom, et al.</td>
-<td class="center">Expires 4 May 2024</td>
+<td class="center">Expires 12 May 2024</td>
 <td class="right">[Page]</td>
 </tr></tfoot>
 </table>
@@ -1048,12 +1048,12 @@
 <dd class="internet-draft">draft-ietf-taps-impl-latest</dd>
 <dt class="label-published">Published:</dt>
 <dd class="published">
-<time datetime="2023-11-01" class="published">1 November 2023</time>
+<time datetime="2023-11-09" class="published">9 November 2023</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="2024-05-04">4 May 2024</time></dd>
+<dd class="expires"><time datetime="2024-05-12">12 May 2024</time></dd>
 <dt class="label-authors">Authors:</dt>
 <dd class="authors">
 <div class="author">
@@ -1107,7 +1107,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 May 2024.<a href="#section-boilerplate.1-4" class="pilcrow">¶</a></p>
+        This Internet-Draft will expire on 12 May 2024.<a href="#section-boilerplate.1-4" class="pilcrow">¶</a></p>
 </section>
 </div>
 <div id="copyright">
@@ -2819,7 +2819,7 @@ <h3 id="name-informative-references">
 <dl class="references">
 <dt id="I-D.ietf-dnsop-svcb-https">[I-D.ietf-dnsop-svcb-https]</dt>
         <dd>
-<span class="refAuthor">Schwartz, B. M.</span>, <span class="refAuthor">Bishop, M.</span>, and <span class="refAuthor">E. Nygren</span>, <span class="refTitle">"Service binding and parameter specification via the DNS (DNS SVCB and HTTPS RRs)"</span>, <span class="refContent">Work in Progress</span>, <span class="seriesInfo">Internet-Draft, draft-ietf-dnsop-svcb-https-12</span>, <time datetime="2023-03-11" class="refDate">11 March 2023</time>, <span>&lt;<a href="https://datatracker.ietf.org/doc/html/draft-ietf-dnsop-svcb-https-12">https://datatracker.ietf.org/doc/html/draft-ietf-dnsop-svcb-https-12</a>&gt;</span>. </dd>
+<span class="refAuthor">Schwartz, B. M.</span>, <span class="refAuthor">Bishop, M.</span>, and <span class="refAuthor">E. Nygren</span>, <span class="refTitle">"Service Binding and Parameter Specification via the DNS (SVCB and HTTPS Resource Records)"</span>, <span class="refContent">Work in Progress</span>, <span class="seriesInfo">Internet-Draft, draft-ietf-dnsop-svcb-https-12</span>, <time datetime="2023-03-11" class="refDate">11 March 2023</time>, <span>&lt;<a href="https://datatracker.ietf.org/doc/html/draft-ietf-dnsop-svcb-https-12">https://datatracker.ietf.org/doc/html/draft-ietf-dnsop-svcb-https-12</a>&gt;</span>. </dd>
 <dd class="break"></dd>
 <dt id="NEAT-flow-mapping">[NEAT-flow-mapping]</dt>
         <dd>

diff --git a/mw-api-encryption/draft-ietf-taps-impl.txt b/mw-api-encryption/draft-ietf-taps-impl.txt
@@ -5,14 +5,14 @@
 TAPS Working Group                                     A. Brunstrom, Ed.
 Internet-Draft                                       Karlstad University
 Intended status: Informational                             T. Pauly, Ed.
-Expires: 4 May 2024                                           Apple Inc.
+Expires: 12 May 2024                                          Apple Inc.
                                                              R. Enghardt
                                                                  Netflix
                                                                P. Tiesel
                                                                   SAP SE
                                                                 M. Welzl
                                                       University of Oslo
-                                                         1 November 2023
+                                                         9 November 2023
 
 
              Implementing Interfaces to Transport Services
@@ -42,7 +42,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 May 2024.
+   This Internet-Draft will expire on 12 May 2024.
 
 Copyright Notice
 
@@ -2261,9 +2261,9 @@ MessageFramer.Deliver(connection, messageContext, messageData, endOfMessage)
 
    [I-D.ietf-dnsop-svcb-https]
               Schwartz, B. M., Bishop, M., and E. Nygren, "Service
-              binding and parameter specification via the DNS (DNS SVCB
-              and HTTPS RRs)", Work in Progress, Internet-Draft, draft-
-              ietf-dnsop-svcb-https-12, 11 March 2023,
+              Binding and Parameter Specification via the DNS (SVCB and
+              HTTPS Resource Records)", Work in Progress, Internet-
+              Draft, draft-ietf-dnsop-svcb-https-12, 11 March 2023,
               <https://datatracker.ietf.org/doc/html/draft-ietf-dnsop-
               svcb-https-12>.
 

diff --git a/mw-api-encryption/draft-ietf-taps-interface.html b/mw-api-encryption/draft-ietf-taps-interface.html
@@ -1044,7 +1044,7 @@
 </tr></thead>
 <tfoot><tr>
 <td class="left">Trammell, et al.</td>
-<td class="center">Expires 4 May 2024</td>
+<td class="center">Expires 12 May 2024</td>
 <td class="right">[Page]</td>
 </tr></tfoot>
 </table>
@@ -1057,12 +1057,12 @@
 <dd class="internet-draft">draft-ietf-taps-interface-latest</dd>
 <dt class="label-published">Published:</dt>
 <dd class="published">
-<time datetime="2023-11-01" class="published">1 November 2023</time>
+<time datetime="2023-11-09" class="published">9 November 2023</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="2024-05-04">4 May 2024</time></dd>
+<dd class="expires"><time datetime="2024-05-12">12 May 2024</time></dd>
 <dt class="label-authors">Authors:</dt>
 <dd class="authors">
 <div class="author">
@@ -1134,7 +1134,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 May 2024.<a href="#section-boilerplate.1-4" class="pilcrow">¶</a></p>
+        This Internet-Draft will expire on 12 May 2024.<a href="#section-boilerplate.1-4" class="pilcrow">¶</a></p>
 </section>
 </div>
 <div id="copyright">
@@ -5769,7 +5769,7 @@ <h2 id="name-privacy-and-security-consid">
 <p id="section-13-4">Of course any communication over a network reveals usage characteristics, because all
 packets, as well as their timing and size, are part of the network-visible wire image <span>[<a href="#RFC8546" class="cite xref">RFC8546</a>]</span>. However,
 the selection of a protocol and its configuration also impacts which information is visible, potentially in
-clear text, and which other entities can access it. How Transport Services systems ought to choose protocols depending on the needed level or type of security is out of scope of the present document as well as <span>[<a href="#I-D.ietf-taps-impl" class="cite xref">I-D.ietf-taps-impl</a>]</span>, because the current documents are limited to transport protocols. The choice of a security protocol can be informed by the survey provided in <span>[<a href="#RFC8922" class="cite xref">RFC8922</a>]</span>.<a href="#section-13-4" class="pilcrow">¶</a></p>
+clear text, and which other entities can access it. How Transport Services systems ought to choose protocols depending on the security properties required is out of scope of this specification, as it is limited to transport protocols. The choice of a security protocol can be informed by the survey provided in <span>[<a href="#RFC8922" class="cite xref">RFC8922</a>]</span>.<a href="#section-13-4" class="pilcrow">¶</a></p>
 <p id="section-13-5">In most cases, information provided for protocol and path selection
 does not directly translate to information that can be observed by network devices on the path.
 However, there might be specific configuration

diff --git a/mw-api-encryption/draft-ietf-taps-interface.txt b/mw-api-encryption/draft-ietf-taps-interface.txt
@@ -5,7 +5,7 @@
 TAPS Working Group                                      B. Trammell, Ed.
 Internet-Draft                                   Google Switzerland GmbH
 Intended status: Standards Track                           M. Welzl, Ed.
-Expires: 4 May 2024                                   University of Oslo
+Expires: 12 May 2024                                  University of Oslo
                                                              R. Enghardt
                                                                  Netflix
                                                             G. Fairhurst
@@ -18,7 +18,7 @@ Expires: 4 May 2024                                   University of Oslo
                                                                   SAP SE
                                                                 T. Pauly
                                                               Apple Inc.
-                                                         1 November 2023
+                                                         9 November 2023
 
 
      An Abstract Application Layer Interface to Transport Services
@@ -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 May 2024.
+   This Internet-Draft will expire on 12 May 2024.
 
 Copyright Notice
 
@@ -3643,11 +3643,10 @@ Table of Contents
    the selection of a protocol and its configuration also impacts which
    information is visible, potentially in clear text, and which other
    entities can access it.  How Transport Services systems ought to
-   choose protocols depending on the needed level or type of security is
-   out of scope of the present document as well as [I-D.ietf-taps-impl],
-   because the current documents are limited to transport protocols.
-   The choice of a security protocol can be informed by the survey
-   provided in [RFC8922].
+   choose protocols depending on the security properties required is out
+   of scope of this specification, as it is limited to transport
+   protocols.  The choice of a security protocol can be informed by the
+   survey provided in [RFC8922].
 
    In most cases, information provided for protocol and path selection
    does not directly translate to information that can be observed by

diff --git a/mw-api-encryption/index.html b/mw-api-encryption/index.html
@@ -16,13 +16,13 @@
     <h1>Editor's drafts for mw-api-encryption branch of <a href="https://github.com/ietf-tapswg/api-drafts/tree/mw-api-encryption">ietf-tapswg/api-drafts</a></h1>
     <table id="branch-mw-api-encryption">
       <tr>
-        <td><a href="./draft-ietf-taps-interface.html" class="html draft-ietf-taps-interface" title="An Abstract Application Layer Interface to Transport Services (HTML)">TAPS Interface</a></td>
-        <td><a href="./draft-ietf-taps-interface.txt" class="txt draft-ietf-taps-interface" title="An Abstract Application Layer Interface to Transport Services (Text)">plain text</a></td>
+        <td><a href="./draft-ietf-taps-arch.html" class="html draft-ietf-taps-arch" title="Architecture and Requirements for Transport Services (HTML)">TAPS Architecture</a></td>
+        <td><a href="./draft-ietf-taps-arch.txt" class="txt draft-ietf-taps-arch" title="Architecture and Requirements for Transport Services (Text)">plain text</a></td>
         <td>same as master</td>
       </tr>
       <tr>
-        <td><a href="./draft-ietf-taps-arch.html" class="html draft-ietf-taps-arch" title="Architecture and Requirements for Transport Services (HTML)">TAPS Architecture</a></td>
-        <td><a href="./draft-ietf-taps-arch.txt" class="txt draft-ietf-taps-arch" title="Architecture and Requirements for Transport Services (Text)">plain text</a></td>
+        <td><a href="./draft-ietf-taps-interface.html" class="html draft-ietf-taps-interface" title="An Abstract Application Layer Interface to Transport Services (HTML)">TAPS Interface</a></td>
+        <td><a href="./draft-ietf-taps-interface.txt" class="txt draft-ietf-taps-interface" title="An Abstract Application Layer Interface to Transport Services (Text)">plain text</a></td>
         <td>same as master</td>
       </tr>
       <tr>