Script updating gh-pages from 839bd82. [ci skip]

draft-ietf-sedate-datetime-extended.html

@@ -18,11 +18,11 @@
 The present version (-09) addresses comments received during IETF
 last call. 
     ' name="description">
-<meta content="xml2rfc 3.18.1" name="generator">
+<meta content="xml2rfc 3.18.2" name="generator">
 <meta content="draft-ietf-sedate-datetime-extended-latest" name="ietf.draft">
 <!-- Generator version information:
-  xml2rfc 3.18.1
-    Python 3.11.5
+  xml2rfc 3.18.2
+    Python 3.11.6
     ConfigArgParse 1.5.3
     google-i18n-address 3.1.0
     intervaltree 3.1.0
@@ -1037,7 +1037,7 @@
 </tr></thead>
 <tfoot><tr>
 <td class="left">Sharma &amp; Bormann</td>
-<td class="center">Expires 20 April 2024</td>
+<td class="center">Expires 21 April 2024</td>
 <td class="right">[Page]</td>
 </tr></tfoot>
 </table>
@@ -1053,12 +1053,12 @@
 <a href="https://www.rfc-editor.org/rfc/rfc3339" class="eref">3339</a> (if approved)</dd>
 <dt class="label-published">Published:</dt>
 <dd class="published">
-<time datetime="2023-10-18" class="published">18 October 2023</time>
+<time datetime="2023-10-19" class="published">19 October 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-04-20">20 April 2024</time></dd>
+<dd class="expires"><time datetime="2024-04-21">21 April 2024</time></dd>
 <dt class="label-authors">Authors:</dt>
 <dd class="authors">
 <div class="author">
@@ -1119,7 +1119,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 20 April 2024.<a href="#section-boilerplate.1-4" class="pilcrow">¶</a></p>
+        This Internet-Draft will expire on 21 April 2024.<a href="#section-boilerplate.1-4" class="pilcrow">¶</a></p>
 </section>
 </div>
 <div id="copyright">
@@ -1618,7 +1618,7 @@ <h3 id="name-registering-keys-for-extend">
 in controlled environments and cannot be registered; such keys <span class="bcp14">MUST NOT</span> be used for interchange and <span class="bcp14">MUST</span> be rejected by implementations
 not specifically configured to take part in such an experiment.
 See <span>[<a href="#BCP178" class="cite xref">BCP178</a>]</span> for a discussion about the danger of experimental keys
-leaking out to general production and why that <span class="bcp14">MUST</span> be prevented.<a href="#section-3.2-3" class="pilcrow">¶</a></p>
+leaking out to general production and why that must be prevented.<a href="#section-3.2-3" class="pilcrow">¶</a></p>
 </section>
 </div>
 <div id="optionally-critical">
@@ -1741,7 +1741,10 @@ <h3 id="name-inconsistent-time-offset-ti">
 <p id="section-3.4-5">For example, the IXDTF timestamps in <a href="#example-inconsistent" class="auto internal xref">Figure 1</a> represent
 00:14:07 UTC, indicating a local time with a <code>time-offset</code> of +00:00.
 However, because Europe/London used offset +01:00 in July 2022, the
-timestamps are inconsistent:<a href="#section-3.4-5" class="pilcrow">¶</a></p>
+timestamps are inconsistent in <a href="#example-inconsistent" class="auto internal xref">Figure 1</a>, where the first
+case is one where the application <span class="bcp14">MUST</span> act on the inconsistency (the
+time zone suffix is marked critical), and the second case is one where
+it <span class="bcp14">MAY</span> act on it (time zone suffix is elective).<a href="#section-3.4-5" class="pilcrow">¶</a></p>
 <span id="name-inconsistent-ixdtf-timestam"></span><div id="example-inconsistent">
 <figure id="figure-1">
           <div class="alignLeft art-text artwork" id="section-3.4-6.1">
@@ -1763,7 +1766,11 @@ <h3 id="name-inconsistent-time-offset-ti">
 local offset in their <span>[<a href="#RFC3339" class="cite xref">RFC3339</a>]</span> part.
 Instead, applications that receive these strings can calculate the
 local offset and local time using the rules of the time zone suffix,
-such as Europe/London in the example below.<a href="#section-3.4-7" class="pilcrow">¶</a></p>
+such as Europe/London in the example in <a href="#example-consistent" class="auto internal xref">Figure 2</a>, which
+like <a href="#example-inconsistent" class="auto internal xref">Figure 1</a> has a case with a time zone suffix marked
+critical, i.e., the intention is that the application must understand
+the time zone information, and one marked elective, which then only is
+provided as additional information.<a href="#section-3.4-7" class="pilcrow">¶</a></p>
 <span id="name-no-inconsistency-in-ixdtf-t"></span><div id="example-consistent">
 <figure id="figure-2">
           <div class="alignLeft art-text artwork" id="section-3.4-8.1">

draft-ietf-sedate-datetime-extended.txt

@@ -6,7 +6,7 @@ Serialising Extended Data About Times and Events               U. Sharma
 Internet-Draft                                              Igalia, S.L.
 Updates: 3339 (if approved)                                   C. Bormann
 Intended status: Standards Track                  Universität Bremen TZI
-Expires: 20 April 2024                                   18 October 2023
+Expires: 21 April 2024                                   19 October 2023
 
 
  Date and Time on the Internet: Timestamps with additional information
@@ -60,7 +60,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 20 April 2024.
+   This Internet-Draft will expire on 21 April 2024.
 
 Copyright Notice
 
@@ -392,7 +392,7 @@ Table of Contents
    NOT be used for interchange and MUST be rejected by implementations
    not specifically configured to take part in such an experiment.  See
    [BCP178] for a discussion about the danger of experimental keys
-   leaking out to general production and why that MUST be prevented.
+   leaking out to general production and why that must be prevented.
 
 3.3.  Optional Generation, Elective vs. Critical Consumption
 
@@ -502,7 +502,10 @@ Table of Contents
    For example, the IXDTF timestamps in Figure 1 represent 00:14:07 UTC,
    indicating a local time with a time-offset of +00:00.  However,
    because Europe/London used offset +01:00 in July 2022, the timestamps
-   are inconsistent:
+   are inconsistent in Figure 1, where the first case is one where the
+   application MUST act on the inconsistency (the time zone suffix is
+   marked critical), and the second case is one where it MAY act on it
+   (time zone suffix is elective).
 
    2022-07-08T00:14:07+00:00[!Europe/London]
    2022-07-08T00:14:07+00:00[Europe/London]
@@ -517,7 +520,11 @@ Table of Contents
    not assert any particular local time nor local offset in their
    [RFC3339] part.  Instead, applications that receive these strings can
    calculate the local offset and local time using the rules of the time
-   zone suffix, such as Europe/London in the example below.
+   zone suffix, such as Europe/London in the example in Figure 2, which
+   like Figure 1 has a case with a time zone suffix marked critical,
+   i.e., the intention is that the application must understand the time
+   zone information, and one marked elective, which then only is
+   provided as additional information.
 
    2022-07-08T00:14:07Z[!Europe/London]
    2022-07-08T00:14:07Z[Europe/London]

index.html

@@ -69,7 +69,7 @@ <h2>Preview for branch <a href="js-iesg-review-1">js-iesg-review-1</a></h2>
       <tr>
         <td><a href="js-iesg-review-1/draft-ietf-sedate-datetime-extended.html" class="html draft-ietf-sedate-datetime-extended" title="Date and Time on the Internet: Timestamps with additional information (HTML)">Internet Extended Date/Time Fmt (IXDTF)</a></td>
         <td><a href="js-iesg-review-1/draft-ietf-sedate-datetime-extended.txt" class="txt draft-ietf-sedate-datetime-extended" title="Date and Time on the Internet: Timestamps with additional information (Text)">plain text</a></td>
-        <td><a href="https://author-tools.ietf.org/api/iddiff?url_1=https://ietf-wg-sedate.github.io/draft-ietf-sedate-datetime-extended/draft-ietf-sedate-datetime-extended.txt&amp;url_2=https://ietf-wg-sedate.github.io/draft-ietf-sedate-datetime-extended/js-iesg-review-1/draft-ietf-sedate-datetime-extended.txt" class="diff draft-ietf-sedate-datetime-extended">diff with main</a></td>
+        <td>same as main</td>
       </tr>
     </table>
     <h2>Preview for branch <a href="ev-iesg-review">ev-iesg-review</a></h2>