Script updating gh-pages from ca34aa5. [ci skip]

draft-ietf-quic-transport.html

@@ -1382,7 +1382,7 @@ <h2 id="rfc.section.6.1">
 <a href="#rfc.section.6.1">6.1.</a> <a href="#send-vn" id="send-vn">Sending Version Negotiation Packets</a>
 </h2>
 <p id="rfc.section.6.1.p.1">If the version selected by the client is not acceptable to the server, the server responds with a Version Negotiation packet (see <a href="#packet-version" class="xref">Section 17.2.1</a>).  This includes a list of versions that the server will accept.  An endpoint MUST NOT send a Version Negotiation packet in response to receiving a Version Negotiation packet.</p>
-<p id="rfc.section.6.1.p.2">This system allows a server to process packets with unsupported versions without retaining state.  Though either the Initial packet or the Version Negotiation packet that is sent in response could be lost, the client will send new packets until it successfully receives a response or it abandons the connection attempt.</p>
+<p id="rfc.section.6.1.p.2">This system allows a server to process packets with unsupported versions without retaining state.  Though either the Initial packet or the Version Negotiation packet that is sent in response could be lost, the client will send new packets until it successfully receives a response or it abandons the connection attempt.  As a result, the client discards all state for the connection and does not send any more packets on the connection.</p>
 <p id="rfc.section.6.1.p.3">A server MAY limit the number of Version Negotiation packets it sends.  For instance, a server that is able to recognize packets as 0-RTT might choose not to send Version Negotiation packets in response to 0-RTT packets with the expectation that it will eventually receive an Initial packet.</p>
 <h2 id="rfc.section.6.2">
 <a href="#rfc.section.6.2">6.2.</a> <a href="#handle-vn" id="handle-vn">Handling Version Negotiation Packets</a>

draft-ietf-quic-transport.txt

@@ -1596,7 +1596,9 @@ Internet-Draft           QUIC Transport Protocol                May 2019
    versions without retaining state.  Though either the Initial packet
    or the Version Negotiation packet that is sent in response could be
    lost, the client will send new packets until it successfully receives
-   a response or it abandons the connection attempt.
+   a response or it abandons the connection attempt.  As a result, the
+   client discards all state for the connection and does not send any
+   more packets on the connection.
 
    A server MAY limit the number of Version Negotiation packets it
    sends.  For instance, a server that is able to recognize packets as
@@ -1619,8 +1621,6 @@ Internet-Draft           QUIC Transport Protocol                May 2019
 
 
 
-
-
 Iyengar & Thomson       Expires November 9, 2019               [Page 29]
 
 Internet-Draft           QUIC Transport Protocol                May 2019