From 06d8cf31dc1c323cfa13ec9812beabad5544a3f4 Mon Sep 17 00:00:00 2001 From: Martin Thomson Date: Tue, 7 Mar 2017 15:37:46 +1100 Subject: [PATCH 1/2] Don't ACK the ACK --- draft-ietf-quic-transport.md | 9 +++------ 1 file changed, 3 insertions(+), 6 deletions(-) diff --git a/draft-ietf-quic-transport.md b/draft-ietf-quic-transport.md index 316743060a..481406affc 100644 --- a/draft-ietf-quic-transport.md +++ b/draft-ietf-quic-transport.md @@ -1665,12 +1665,9 @@ The details of loss detection and congestion control are described in {{QUIC-RECOVERY}}. A receiver acknowledges receipt of a received packet by sending one or more ACK -frames containing the packet number of the received packet. To avoid perpetual -acknowledgment between endpoints, a receiver MUST NOT generate an ACK frame in -response to every packet containing only ACK frames. However, since it is -possible that an endpoint might only send packets containing ACK frames (or -other non-retransmittable frames), the receiving peer MAY send an ACK frame -after a reasonable number (currently 20) of such packets have been received. +frames containing the packet number of the received packet. To avoid creating +an indefinite feedback loop, an endpoint MUST NOT generate an ACK frame in +response to a packet containing only ACK and PADDING frames. Strategies and implications of the frequency of generating acknowledgments are discussed in more detail in {{QUIC-RECOVERY}}. From 9704ac7bba64b247377a11331e408c7db1e77f8b Mon Sep 17 00:00:00 2001 From: Martin Thomson Date: Wed, 8 Mar 2017 10:13:22 +1100 Subject: [PATCH 2/2] ACK or PADDING --- draft-ietf-quic-transport.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/draft-ietf-quic-transport.md b/draft-ietf-quic-transport.md index 481406affc..28e3b73438 100644 --- a/draft-ietf-quic-transport.md +++ b/draft-ietf-quic-transport.md @@ -1667,7 +1667,7 @@ The details of loss detection and congestion control are described in A receiver acknowledges receipt of a received packet by sending one or more ACK frames containing the packet number of the received packet. To avoid creating an indefinite feedback loop, an endpoint MUST NOT generate an ACK frame in -response to a packet containing only ACK and PADDING frames. +response to a packet containing only ACK or PADDING frames. Strategies and implications of the frequency of generating acknowledgments are discussed in more detail in {{QUIC-RECOVERY}}.