Re: I-D Action: draft-ietf-quic-ack-frequency-03.txt

Gorry Fairhurst <gorry@erg.abdn.ac.uk> Mon, 13 March 2023 09:48 UTC

Message-ID: <270f6099-01fa-0c60-df96-cbd8fe83e6d6@erg.abdn.ac.uk>
Date: Mon, 13 Mar 2023 09:47:58 +0000
MIME-Version: 1.0
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.13; rv:102.0) Gecko/20100101 Thunderbird/102.7.2
Subject: Re: I-D Action: draft-ietf-quic-ack-frequency-03.txt
To: quic@ietf.org
References: <167846127018.23774.4929014435074001852@ietfa.amsl.com>
From: Gorry Fairhurst <gorry@erg.abdn.ac.uk>
Organization: UNIVERSITY OF ABERDEEN
In-Reply-To: <167846127018.23774.4929014435074001852@ietfa.amsl.com>
Content-Type: text/plain; charset="UTF-8"; format="flowed"
Content-Transfer-Encoding: 8bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/quic/Q3X0sEGL-OTeLUkNezfuX2dB5Hc>
Precedence: list

Thanks editors for making a substantial improvment to this draft.

I have one design issue (#168) that I'd like to see if we can make 
progress on: Section 8.1 makes recommendations that can be used to 
determine how many ACKs/RTT is acceptable. Sending 1 ACK/RTT (as 
discussed) seems sufficient for a perfect return path, but I think this 
is much less robust than we should be when specifying for an Internet 
Transport, because using one ACK/RTT can be too fragile for a return 
that could be congested or more variable than typical.

Best wishes,

Gorry

P.S. I also added a few editorial issues to the github:

  NiT: It would be nice to clarify /it/, #163
  Editorial: Should definitions be followed by colons? #164
  Editorial: What is an /underlying platform/? #165
  What does "MUST however wait until" require? #166
  NiT: Should refer to the *size* of the initial congestion window, #167

On 10/03/2023 15:14, internet-drafts@ietf.org wrote:
> A New Internet-Draft is available from the on-line Internet-Drafts
> directories. This Internet-Draft is a work item of the QUIC (QUIC) WG of the
> IETF.
>
>     Title           : QUIC Acknowledgement Frequency
>     Authors         : Jana Iyengar
>                       Ian Swett
>                       Mirja Kühlewind
>     Filename        : draft-ietf-quic-ack-frequency-03.txt
>     Pages           : 14
>     Date            : 2023-03-10
>
> Abstract:
>     This document describes a QUIC extension for an endpoint to control
>     its peer's delaying of acknowledgements.
>
> Note to Readers
>
>     Discussion of this draft takes place on the QUIC working group
>     mailing list (quic@ietf.org), which is archived at
>     https://mailarchive.ietf.org/arch/search/?email_list=quic.  Source
>     code and issues list for this draft can be found at
>     https://github.com/quicwg/ack-frequency.
>
>     Working Group information can be found at https://github.com/quicwg.
>
> The IETF datatracker status page for this Internet-Draft is:
> https://datatracker.ietf.org/doc/draft-ietf-quic-ack-frequency/
>
> There is also an HTML version available at:
> https://www.ietf.org/archive/id/draft-ietf-quic-ack-frequency-03.html
>
> A diff from the previous version is available at:
> https://author-tools.ietf.org/iddiff?url2=draft-ietf-quic-ack-frequency-03
>
> Internet-Drafts are also available by rsync at rsync.ietf.org::internet-drafts
>

I-D Action: draft-ietf-quic-ack-frequency-03.txt internet-drafts
Re: I-D Action: draft-ietf-quic-ack-frequency-03.… Gorry Fairhurst
Re: I-D Action: draft-ietf-quic-ack-frequency-03.… Mirja Kuehlewind