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

[Mirja Kuehlewind <[e-mail]>]

Hi Gorry,

thanks a lot for your review! Discuss has started on Github and we should also have some time to discuss further at the meeting.

Mirja



On 13.03.23, 10:48, "QUIC on behalf of Gorry Fairhurst" <[e-mail] on behalf of [e-mail]> wrote:

    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, [e-mail] 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 ([e-mail]), 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://protect2.fireeye.com/v1/url?k=31323334-501d5122-313273af-454445555731-65b24f4e97181800&q=1&e=1f78a9ee-97b5-45d0-87ba-654cc36952f2&u=https%3A%2F%2Fgithub.com%2Fquicwg%2Fack-frequency.
    >
    >     Working Group information can be found at https://protect2.fireeye.com/v1/url?k=31323334-501d5122-313273af-454445555731-b46b15bef7d9c539&q=1&e=1f78a9ee-97b5-45d0-87ba-654cc36952f2&u=https%3A%2F%2Fgithub.com%2Fquicwg.
    >
    > 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
    >