Script updating gh-pages from 6520adb. [ci skip]

Author: ID Bot

aurel/problem-statement/draft-brezun-human-continuity-http.html

@@ -2346,7 +2346,7 @@ <h3 id="name-human-continuity-handle-req">
 <a href="#section-10.3" class="section-number selfRef">10.3. </a><a href="#name-human-continuity-handle-req" class="section-name selfRef">Human-Continuity Handle Requirements</a>
         </h3>
 <p id="section-10.3-1">A profile that does not produce a <code>continuity_handle</code> for a valid presentation is not conformant with this specification. A successful verification result for a conforming profile <span class="bcp14">MUST</span> include a verifier-local <code>continuity_handle</code>.<a href="#section-10.3-1" class="pilcrow">¶</a></p>
-<p id="section-10.3-2">While a verified human remains eligible and retains the state required by a profile, the profile <span class="bcp14">MUST</span> support repeated valid presentations by that human within the same continuity scope, including presentations bound to different valid challenge nonces. A successful presentation <span class="bcp14">MUST NOT</span> itself terminate that capability.<a href="#section-10.3-2" class="pilcrow">¶</a></p>
+<p id="section-10.3-2">A profile <span class="bcp14">MUST</span> support repeated valid presentations by the same verified human within the same continuity scope, including presentations bound to different valid challenge nonces. A successful presentation <span class="bcp14">MUST NOT</span> itself terminate that capability.<a href="#section-10.3-2" class="pilcrow">¶</a></p>
 <p id="section-10.3-3">The <code>continuity_handle</code> <span class="bcp14">MUST</span> be opaque and canonically encoded. Under the profile's documented assumptions, prediction, preimage, and second-preimage resistance <span class="bcp14">MUST</span> be at least 112 bits and <span class="bcp14">SHOULD</span> be at least 128 bits. Enumeration and malleation <span class="bcp14">MUST</span> be infeasible, and accidental collisions <span class="bcp14">MUST</span> be negligible at the profile's maximum supported population.<a href="#section-10.3-3" class="pilcrow">¶</a></p>
 <p id="section-10.3-4">The <code>continuity_handle</code> <span class="bcp14">MUST</span> be cryptographically bound to the continuity scope. A conforming profile <span class="bcp14">MUST</span> use domain separation or an equivalent construction so that <code>continuity_handle</code> values for different continuity scopes are not correlatable and cannot be transformed into one another.<a href="#section-10.3-4" class="pilcrow">¶</a></p>
 <p id="section-10.3-5">The core protocol defines continuity scope and <code>continuity_handle</code> comparison semantics. Profiles <span class="bcp14">MUST NOT</span> redefine these semantics.<a href="#section-10.3-5" class="pilcrow">¶</a></p>

aurel/problem-statement/draft-brezun-human-continuity-http.txt

@@ -2033,10 +2033,9 @@ Table of Contents
    verification result for a conforming profile MUST include a verifier-
    local continuity_handle.
 
-   While a verified human remains eligible and retains the state
-   required by a profile, the profile MUST support repeated valid
-   presentations by that human within the same continuity scope,
-   including presentations bound to different valid challenge nonces.  A
+   A profile MUST support repeated valid presentations by the same
+   verified human within the same continuity scope, including
+   presentations bound to different valid challenge nonces.  A
    successful presentation MUST NOT itself terminate that capability.
 
    The continuity_handle MUST be opaque and canonically encoded.  Under