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

ianswett-ack-ack/draft-ietf-quic-transport.html

@@ -2073,7 +2073,7 @@ <h3 id="rfc.section.13.1.1">
 <a href="#rfc.section.13.1.1">13.1.1.</a> <a href="#sending-ack-frames" id="sending-ack-frames">Sending ACK Frames</a>
 </h3>
 <p id="rfc.section.13.1.1.p.1">An endpoint sends ACK frames to acknowledge packets it has received and processed.</p>
-<p id="rfc.section.13.1.1.p.2">Packets containing only ACK frames are not congestion controlled, so there are limits on how frequently they can be sent.  An endpoint MUST NOT send more than one packet containing only an ACK frame per received ACK-eliciting packet (one containing frames other than ACK and/or PADDING).  An endpoint MUST NOT send a packet containing only an ACK frame in response to a non-ACK-eliciting packet (one containing only ACK and/or PADDING frames), even if there are packet gaps which precede the received packet. Limiting the sending of ACK frames avoids an infinite feedback loop of acknowledgements, which could prevent the connection from ever becoming idle. The endpoint MUST however acknowledge non-ACK-eliciting packets when sending ACK frames in response to ACK-eliciting packets.</p>
+<p id="rfc.section.13.1.1.p.2">Packets containing only ACK frames are not congestion controlled, so there are limits on how frequently they can be sent.  An endpoint MUST NOT send more than one ACK-frame-only packet in response to receiving an ACK-eliciting packet (one containing frames other than ACK and/or PADDING).  An endpoint MUST NOT send a packet containing only an ACK frame in response to a non-ACK-eliciting packet (one containing only ACK and/or PADDING frames), even if there are packet gaps which precede the received packet. Limiting the sending of ACK frames avoids an infinite feedback loop of acknowledgements, which could prevent the connection from ever becoming idle. The endpoint MUST however acknowledge non-ACK-eliciting packets when sending ACK frames in response to ACK-eliciting packets.</p>
 <p id="rfc.section.13.1.1.p.3">Packets containing PADDING frames are considered to be in flight for congestion control purposes <a href="#QUIC-RECOVERY" class="xref">[QUIC-RECOVERY]</a>. Sending only PADDING frames might cause the sender to become limited by the congestion controller (as described in <a href="#QUIC-RECOVERY" class="xref">[QUIC-RECOVERY]</a>) with no acknowledgments forthcoming from the receiver. Therefore, a sender SHOULD ensure that other frames are sent in addition to PADDING frames to elicit acknowledgments from the receiver.</p>
 <p id="rfc.section.13.1.1.p.4">An endpoint that is only sending acknowledgements will not receive acknowledgments from its peer unless those acknowledgements are included in packets with ACK-eliciting frames.  A sender SHOULD bundle ACK frames with other frames when there are new ACK-eliciting packets to acknowledge.  When only non-ACK-eliciting packets need to be acknowledged, the sender MAY wait until an ACK-eliciting packet has been received to bundle an ACK frame with outgoing frames.</p>
 <p id="rfc.section.13.1.1.p.5">An endpoint SHOULD treat receipt of an acknowledgment for a packet it did not send as a connection error of type PROTOCOL_VIOLATION, if it is able to detect the condition.</p>

ianswett-ack-ack/draft-ietf-quic-transport.txt

@@ -3829,10 +3829,10 @@ Internet-Draft           QUIC Transport Protocol               July 2019
 
    Packets containing only ACK frames are not congestion controlled, so
    there are limits on how frequently they can be sent.  An endpoint
-   MUST NOT send more than one packet containing only an ACK frame per
-   received ACK-eliciting packet (one containing frames other than ACK
-   and/or PADDING).  An endpoint MUST NOT send a packet containing only
-   an ACK frame in response to a non-ACK-eliciting packet (one
+   MUST NOT send more than one ACK-frame-only packet in response to
+   receiving an ACK-eliciting packet (one containing frames other than
+   ACK and/or PADDING).  An endpoint MUST NOT send a packet containing
+   only an ACK frame in response to a non-ACK-eliciting packet (one
    containing only ACK and/or PADDING frames), even if there are packet
    gaps which precede the received packet.  Limiting the sending of ACK
    frames avoids an infinite feedback loop of acknowledgements, which