Script updating gh-pages from 51ebe3a. [ci skip]

draft-dekater-scion-pki.html

@@ -16,7 +16,7 @@
 <meta content="draft-dekater-scion-pki-latest" name="ietf.draft">
 <!-- Generator version information:
   xml2rfc 3.18.0
-    Python 3.11.4
+    Python 3.11.5
     ConfigArgParse 1.5.3
     google-i18n-address 3.1.0
     intervaltree 3.1.0
@@ -1049,11 +1049,11 @@
 <thead><tr>
 <td class="left">Internet-Draft</td>
 <td class="center">SCION CP-PKI</td>
-<td class="right">August 2023</td>
+<td class="right">September 2023</td>
 </tr></thead>
 <tfoot><tr>
 <td class="left">de Kater &amp; Rustignoli</td>
-<td class="center">Expires 29 February 2024</td>
+<td class="center">Expires 15 March 2024</td>
 <td class="right">[Page]</td>
 </tr></tfoot>
 </table>
@@ -1066,12 +1066,12 @@
 <dd class="internet-draft">draft-dekater-scion-pki-latest</dd>
 <dt class="label-published">Published:</dt>
 <dd class="published">
-<time datetime="2023-08-28" class="published">28 August 2023</time>
+<time datetime="2023-09-12" class="published">12 September 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-02-29">29 February 2024</time></dd>
+<dd class="expires"><time datetime="2024-03-15">15 March 2024</time></dd>
 <dt class="label-authors">Authors:</dt>
 <dd class="authors">
 <div class="author">
@@ -1121,7 +1121,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 29 February 2024.<a href="#section-boilerplate.1-4" class="pilcrow">¶</a></p>
+        This Internet-Draft will expire on 15 March 2024.<a href="#section-boilerplate.1-4" class="pilcrow">¶</a></p>
 </section>
 </div>
 <div id="copyright">
@@ -2909,7 +2909,7 @@ <h5 id="name-scion-specific-rules">
             <h5 id="name-trc-equality">
 <a href="#section-3.1.3.2" class="section-number selfRef">3.1.3.2. </a><a href="#name-trc-equality" class="section-name selfRef">TRC Equality</a>
             </h5>
-<p id="section-3.1.3.2-1">The signer informations in the signed TRC are part of an unordered set, per <span>[<a href="#RFC5652" class="cite xref">RFC5652</a>]</span>. This implies that the signer informations can be reordered without affecting verification. Certain operations, however, require TRCs to be equal, according to the following equality definition:<a href="#section-3.1.3.2-1" class="pilcrow">¶</a></p>
+<p id="section-3.1.3.2-1">The signer information in the signed TRC is part of an unordered set, per <span>[<a href="#RFC5652" class="cite xref">RFC5652</a>]</span>. This implies that the signer information can be reordered without affecting verification. Certain operations, however, require TRCs to be equal, according to the following equality definition:<a href="#section-3.1.3.2-1" class="pilcrow">¶</a></p>
 <p id="section-3.1.3.2-2"><strong>Two TRCs are equal, if and only if their payloads are byte equal.</strong><a href="#section-3.1.3.2-2" class="pilcrow">¶</a></p>
 <p id="section-3.1.3.2-3">Two TRCs with byte equal payloads can be considered as equal, because the TRC payload exactly defines which signatures must be attached in the signed TRC:<a href="#section-3.1.3.2-3" class="pilcrow">¶</a></p>
 <ul class="normal">
@@ -2928,7 +2928,7 @@ <h4 id="name-certification-path-trust-an">
 <a href="#section-3.1.4" class="section-number selfRef">3.1.4. </a><a href="#name-certification-path-trust-an" class="section-name selfRef">Certification Path - Trust Anchor Pool</a>
           </h4>
 <p id="section-3.1.4-1">The certification path of a control-plane AS certificate starts in a control-plane root certificate. The control-plane root certificates for a given ISD are distributed via the TRC. However, AS certificates and the corresponding signing CA certificates are <strong>not</strong> part of the TRC, but bundled into certificate chains and distributed separately from the corresponding TRC. This separation makes it possible to extend the validity period of the root certificate, and to update the corresponding TRC, without having to modify the certificate chain. To be able to validate a certification path, each AS must build a collection of root certificates from the latest TRC of the relevant ISD. The following section explains how to build a trust anchor pool.<a href="#section-3.1.4-1" class="pilcrow">¶</a></p>
-<p id="section-3.1.4-2"><strong>Note:</strong> Any entity sending information that is secured by the CP-PKI, such as control-plane messages, <span class="bcp14">MUST</span> be able to provide all the necessary trust material, such as certificates, to verify said information. If any cryptographic material is missing in the process, the relying party <span class="bcp14">MUST</span> query the originator of the message for the missing material. If it cannot be resolved, the verification process fails. For more details, see 4.2 "Signing and Verifying Control-Plane Messages".<a href="#section-3.1.4-2" class="pilcrow">¶</a></p>
+<p id="section-3.1.4-2"><strong>Note:</strong> Any entity sending information that is secured by the CP-PKI, such as control-plane messages, <span class="bcp14">MUST</span> be able to provide all the necessary trust material, such as certificates, to verify said information. If any cryptographic material is missing in the process, the relying party <span class="bcp14">MUST</span> query the originator of the message for the missing material. If it cannot be resolved, the verification process fails. For more details, see 4.2 "Signing and Verifying Control-Plane Messages" <a href="#signing-verifying-cp-messages" class="auto internal xref">Section 4.2</a>.<a href="#section-3.1.4-2" class="pilcrow">¶</a></p>
 <div id="trc-selection">
 <section id="section-3.1.4.1">
             <h5 id="name-trc-selection-for-trust-anc">

draft-dekater-scion-pki.txt

@@ -5,7 +5,7 @@
 Network Working Group                                        C. de Kater
 Internet-Draft                                             N. Rustignoli
 Intended status: Informational                         SCION Association
-Expires: 29 February 2024                                 28 August 2023
+Expires: 15 March 2024                                 12 September 2023
 
 
                         SCION Control-Plane PKI
@@ -56,7 +56,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 29 February 2024.
+   This Internet-Draft will expire on 15 March 2024.
 
 Copyright Notice
 
@@ -1833,8 +1833,8 @@ Table of Contents
 
 3.1.3.2.   TRC Equality
 
-   The signer informations in the signed TRC are part of an unordered
-   set, per [RFC5652].  This implies that the signer informations can be
+   The signer information in the signed TRC is part of an unordered set,
+   per [RFC5652].  This implies that the signer information can be
    reordered without affecting verification.  Certain operations,
    however, require TRCs to be equal, according to the following
    equality definition:
@@ -1877,7 +1877,7 @@ Table of Contents
    process, the relying party MUST query the originator of the message
    for the missing material.  If it cannot be resolved, the verification
    process fails.  For more details, see 4.2 "Signing and Verifying
-   Control-Plane Messages".
+   Control-Plane Messages" Section 4.2.
 
 3.1.4.1.   TRC Selection For Trust Anchor Pool