Script updating gh-pages from 8dff718. [ci skip]

Author: ID Bot

draft-ietf-anima-rfc8366bis.html

@@ -1961,12 +1961,12 @@ <h2 id="name-voucher-artifact">
 <p id="section-8-6">Only the format of Voucher that is expected is signaled in the form of a (MIME) media
 type in the HTTP "Accept" header <span>[<a href="#RFC9110" class="cite xref">RFC9110</a>]</span>.<a href="#section-8-6" class="pilcrow">¶</a></p>
 <p id="section-8-7">For Vouchers stored/transferred via methods like a USB storage device (USB key), the Voucher format is usually signaled by a filename extension.<a href="#section-8-7" class="pilcrow">¶</a></p>
-<p id="section-8-8">In the constrained versions of the voucher and voucher-request (as used by <span>[<a href="#cBRSKI" class="cite xref">cBRSKI</a>]</span>), the fields <code>pinned-domain-pubk</code> (<code>proximity-registrar-pubk</code> for requests) and <code>pinned-domain-pubk-sha256</code> (<code>proximity-registrar-pubk-sha256</code> for requests) can be used to pin the raw public key, or just the SHA256 hash of the raw public key.
+<p id="section-8-8">In the constrained versions of the voucher and voucher-request (as used by <span>[<a href="#cBRSKI" class="cite xref">cBRSKI</a>]</span>), the attributes <code>pinned-domain-pubk</code> (<code>proximity-registrar-pubk</code> for requests) and <code>pinned-domain-pubk-sha256</code> (<code>proximity-registrar-pubk-sha256</code> for requests) are involved in the process of pinning a raw public key.
 The public keys are to be encoded according to <span>[<a href="#RFC7250" class="cite xref">RFC7250</a>], <a href="https://rfc-editor.org/rfc/rfc7250#section-3" class="relref">Section 3</a></span> for RSA and EcDSA keys, noting that <span>[<a href="#RFC8032" class="cite xref">RFC8032</a>]</span> extends this to include an OID for EdDSA.
 The old (1024-bit) DSA algorithm is not supported.<a href="#section-8-8" class="pilcrow">¶</a></p>
 <p id="section-8-9">When EcDSA is supported, curves secp256r1 and secp384r1 <span class="bcp14">SHOULD</span> be supported.
 When EdDSA is supported, curves Ed25519 and Ed448 <span class="bcp14">SHOULD</span> be supported.
-When RSA is supported, sizes of at least 2048 bits <span class="bcp14">SHOULD</span> be supported, with support for sizes up to 4096 bits as <span class="bcp14">RECOMMENDED</span>.<a href="#section-8-9" class="pilcrow">¶</a></p>
+When RSA is supported by an implementation, it <span class="bcp14">SHOULD</span> support key lengths between 2048 and 4096 bits.<a href="#section-8-9" class="pilcrow">¶</a></p>
 <p id="section-8-10">Of the above, EcDSA <span class="bcp14">SHOULD</span> be supported by all implementations, until some quantum-safe variant is standardized.<a href="#section-8-10" class="pilcrow">¶</a></p>
 <p id="section-8-11">Should SHA256 need to be replaced, then a new YANG module will be published with a new leaf, obsoleting <code>pinned-domain-pubk-sha256</code> and <code>proximity-registrar-pubk-sha256</code>.<a href="#section-8-11" class="pilcrow">¶</a></p>
 <div id="voucher-tree-diagram">

draft-ietf-anima-rfc8366bis.txt

@@ -712,19 +712,18 @@ Table of Contents
    extension.
 
    In the constrained versions of the voucher and voucher-request (as
-   used by [cBRSKI]), the fields pinned-domain-pubk (proximity-
+   used by [cBRSKI]), the attributes pinned-domain-pubk (proximity-
    registrar-pubk for requests) and pinned-domain-pubk-sha256
-   (proximity-registrar-pubk-sha256 for requests) can be used to pin the
-   raw public key, or just the SHA256 hash of the raw public key.  The
-   public keys are to be encoded according to [RFC7250], Section 3 for
-   RSA and EcDSA keys, noting that [RFC8032] extends this to include an
-   OID for EdDSA.  The old (1024-bit) DSA algorithm is not supported.
+   (proximity-registrar-pubk-sha256 for requests) are involved in the
+   process of pinning a raw public key.  The public keys are to be
+   encoded according to [RFC7250], Section 3 for RSA and EcDSA keys,
+   noting that [RFC8032] extends this to include an OID for EdDSA.  The
+   old (1024-bit) DSA algorithm is not supported.
 
    When EcDSA is supported, curves secp256r1 and secp384r1 SHOULD be
    supported.  When EdDSA is supported, curves Ed25519 and Ed448 SHOULD
-   be supported.  When RSA is supported, sizes of at least 2048 bits
-   SHOULD be supported, with support for sizes up to 4096 bits as
-   RECOMMENDED.
+   be supported.  When RSA is supported by an implementation, it SHOULD
+   support key lengths between 2048 and 4096 bits.
 
    Of the above, EcDSA SHOULD be supported by all implementations, until
    some quantum-safe variant is standardized.