Script updating gh-pages from 966bb15. [ci skip]

quicwg · Oct 24, 2019 · 891df44 · 891df44
1 parent 910f77f
commit 891df44
Show file tree

Hide file tree

Showing 3 changed files with 1,645 additions and 1,645 deletions.
diff --git a/draft-ietf-quic-transport.html b/draft-ietf-quic-transport.html
@@ -1699,7 +1699,7 @@ <h2 id="rfc.section.8.3">
 <a href="#rfc.section.8.3">8.3.</a> <a href="#initiating-path-validation" id="initiating-path-validation">Initiating Path Validation</a>
 </h2>
 <p id="rfc.section.8.3.p.1">To initiate path validation, an endpoint sends a PATH_CHALLENGE frame containing a random payload on the path to be validated.</p>
-<p id="rfc.section.8.3.p.2">An endpoint MAY send multiple PATH_CHALLENGE frames to guard against packet loss, however an endpoint SHOULD NOT send multiple PATH_CHALLENGE frames in a single packet.  An endpoint SHOULD NOT send a PATH_CHALLENGE more frequently than it would an Initial packet, ensuring that connection migration is no more load on a new path than establishing a new connection.</p>
+<p id="rfc.section.8.3.p.2">An endpoint MAY send multiple PATH_CHALLENGE frames to guard against packet loss. However, an endpoint SHOULD NOT send multiple PATH_CHALLENGE frames in a single packet.  An endpoint SHOULD NOT send a PATH_CHALLENGE more frequently than it would an Initial packet, ensuring that connection migration is no more load on a new path than establishing a new connection.</p>
 <p id="rfc.section.8.3.p.3">The endpoint MUST use unpredictable data in every PATH_CHALLENGE frame so that it can associate the peer&#8217;s response with the corresponding PATH_CHALLENGE.</p>
 <h2 id="rfc.section.8.4">
 <a href="#rfc.section.8.4">8.4.</a> <a href="#path-validation-responses" id="path-validation-responses">Path Validation Responses</a>

diff --git a/draft-ietf-quic-transport.txt b/draft-ietf-quic-transport.txt
@@ -2428,7 +2428,7 @@ Internet-Draft           QUIC Transport Protocol            October 2019
    containing a random payload on the path to be validated.
 
    An endpoint MAY send multiple PATH_CHALLENGE frames to guard against
-   packet loss, however an endpoint SHOULD NOT send multiple
+   packet loss.  However, an endpoint SHOULD NOT send multiple
    PATH_CHALLENGE frames in a single packet.  An endpoint SHOULD NOT
    send a PATH_CHALLENGE more frequently than it would an Initial
    packet, ensuring that connection migration is no more load on a new