Re: Two Notable Ack Frequency Issues
Ian Swett <ianswett@google.com> Tue, 14 September 2021 02:04 UTC
Return-Path: <ianswett@google.com>
X-Original-To: quic@ietfa.amsl.com
Delivered-To: quic@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 2F1443A0B89 for <quic@ietfa.amsl.com>; Mon, 13 Sep 2021 19:04:18 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -18.098
X-Spam-Level:
X-Spam-Status: No, score=-18.098 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIMWL_WL_MED=-0.499, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, ENV_AND_HDR_SPF_MATCH=-0.5, HTML_MESSAGE=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, USER_IN_DEF_DKIM_WL=-7.5, USER_IN_DEF_SPF_WL=-7.5] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=google.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id L-PaFq3ENCei for <quic@ietfa.amsl.com>; Mon, 13 Sep 2021 19:04:14 -0700 (PDT)
Received: from mail-yb1-xb2e.google.com (mail-yb1-xb2e.google.com [IPv6:2607:f8b0:4864:20::b2e]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 422FB3A0B88 for <quic@ietf.org>; Mon, 13 Sep 2021 19:04:14 -0700 (PDT)
Received: by mail-yb1-xb2e.google.com with SMTP id s16so24805068ybe.0 for <quic@ietf.org>; Mon, 13 Sep 2021 19:04:14 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20210112; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=WwF0VkDu8ZJJ7dRMrns3BvZqTM22GvlLoOhA5hxGUq8=; b=LixYxscc6OCnykZfw7/tI6KcudfSVQp8MWlWo5sBBjksrix2iSPC5GB1qh1c90DO5+ MGq8lP5GmjPm//eIMSanphD7cN/xuevfVcvSHwpOGZB69XvdhtDWIbz1v91wTweddvjy G8+c90s3Gz+2/XV7RtMm9jSVCWMrYe1iIF9XP+GFgHa9RkOeAuqjUmrKPeh1YP9u18p7 86c2HM8OfdX2PYw/qVBDbhvQqXOACkNhtP8c1DUdHevO9pA/eRC5Peeujby/IcvwQJMK AmGtKviPwLVLXNPnDnFsaCN4Fp5v8J5VnsPp7dZdLxM5LG2bSDQbCtL8fNh+f6wGkjlC W2sQ==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=WwF0VkDu8ZJJ7dRMrns3BvZqTM22GvlLoOhA5hxGUq8=; b=0KKB5VW+GwpkfftO5L1PBB564JrKxDo0zf+XeVgqkvVYIDymeF2BRZ5YWbsUilSWhy Em5K3lbNBYXbb13aRVsRqqiLDTzdjrA+/Q4lEmS0Ube+i68nfeN5kl808xJHZXIqEhhD TpbxRg15/6odGu6M3LaxN3HJP0qv3e8X2e/c6WWf10EgdXwgsM8sW9qfjPUuHAwj3MXQ owb6c36uQotYt4XveVepkR1aeGyrWa12HZHZ1m5Rlq0A2//svjXswX2Bpj7u3gRdlkzh 40rdPI+iRQ5lJXWYoVFkBfwg3RlPgY39PiB7A8FBFbHKbEh0wy5w1fnIZo+itFU3u8wW mOSQ==
X-Gm-Message-State: AOAM530XOpyKzhtIInpEbMLGx5WQDpflH321iFR4XsfLTF2X+uMs5kCj aGGHtpMVMHiinnhr4PrJEOnZyqZLpIH2ptafjj8rLK3ftW0=
X-Google-Smtp-Source: ABdhPJyA9Et6gOWUyzC/oVq9qzBojPEkNiTwU1oU/pB+ZPb0wMr9VebuS11iYVnLcZYVTNwKA+fPNJ5azNZCCjjGTds=
X-Received: by 2002:a25:3002:: with SMTP id w2mr17846886ybw.76.1631585052267; Mon, 13 Sep 2021 19:04:12 -0700 (PDT)
MIME-Version: 1.0
References: <CAKcm_gPe_0E3Yje=qT07hC2uSt+srWT7EwbhiYNsPq8Q+pFFiw@mail.gmail.com> <d17cbbc0-a35c-45ba-afee-11e92b08b373@www.fastmail.com> <CADdTf+hWM6UCQZkSbKxN3KARLxGmASxBnEg8VAjb6=xSFNyWLA@mail.gmail.com> <2eff1b46-65cb-4822-a498-11357ac4cd23@www.fastmail.com> <5021E5FE-F19E-44BA-BA50-F9807CF30FCB@fb.com>
In-Reply-To: <5021E5FE-F19E-44BA-BA50-F9807CF30FCB@fb.com>
From: Ian Swett <ianswett@google.com>
Date: Mon, 13 Sep 2021 22:04:01 -0400
Message-ID: <CAKcm_gM0nbBB8y+jjSh7ZwnL9zvkkZUeYMinkQetmwNjRSORuA@mail.gmail.com>
Subject: Re: Two Notable Ack Frequency Issues
To: Roberto Peon <fenix=40fb.com@dmarc.ietf.org>
Cc: Martin Thomson <mt@lowentropy.net>, "quic@ietf.org" <quic@ietf.org>
Content-Type: multipart/alternative; boundary="0000000000007685ee05cbeaff8e"
Archived-At: <https://mailarchive.ietf.org/arch/msg/quic/Nz9cKqXJqfuOFU8HC1R747br17A>
X-BeenThere: quic@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Main mailing list of the IETF QUIC working group <quic.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/quic>, <mailto:quic-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/quic/>
List-Post: <mailto:quic@ietf.org>
List-Help: <mailto:quic-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/quic>, <mailto:quic-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 14 Sep 2021 02:04:19 -0000
Thanks for all the feedback, I've substantially changed my PR on NO_ACK to be DELAY_ACK. I already have a use case for DELAY_ACK, so I think it's potentially quite useful. I'd also like to change how peers ACK(or rather do not ACK) PADDING only packets, but I have not done that in this <https://github.com/quicwg/ack-frequency/pull/67> PR. I also left a recent comment <https://github.com/quicwg/ack-frequency/issues/48#issuecomment-918692616> on the ECN issue, since I'm not 100% sure all endpoints that use ECN will want the Accurate ECN response. I'm not sure we're in a good place to redesign ECN response, but I suggested what I thought were the 3 most straightforward options. On IMMEDIATE_ACK, it both solves a clear problem(PN skipping no longer elicits an immediate ACK when 'Ignore Order' is true) as well as following in the footsteps of the TCP drafts. Additionally, it was discussed at the last IETF, and the only outstanding question I am aware of from that discussion was what to name the frame ( https://github.com/quicwg/ack-frequency/issues/34#issuecomment-890272310) Slides 7 to 11 <https://github.com/quicwg/wg-materials/blob/main/ietf111/ack-frequency.pdf> are the relevant slides. >From the minutes on IMMEDIATE_ACK, the last two points are: *Matt:* seems like most people are in favor of option 2, 1-byte frame (or semi-PING frame, see jabber). Doing option 1 (header bit) is probably not realistic. *Jana:* will go ahead with option 2. If strong disagreement, please comment on issue <https://github.com/quicwg/ack-frequency/issues/34>. Thanks, Ian
- Two Notable Ack Frequency Issues Ian Swett
- Re: Two Notable Ack Frequency Issues Martin Thomson
- Re: Two Notable Ack Frequency Issues Vidhi Goel
- Re: Two Notable Ack Frequency Issues Christian Huitema
- Re: Two Notable Ack Frequency Issues Matt Joras
- Re: Two Notable Ack Frequency Issues Martin Thomson
- Re: Two Notable Ack Frequency Issues Roberto Peon
- Re: Two Notable Ack Frequency Issues Ian Swett
- Re: Two Notable Ack Frequency Issues Martin Thomson
- Re: Two Notable Ack Frequency Issues Ian Swett