IETF Logo Mail Archive

Re: [quicwg/base-drafts] Changing the Default QUIC ACK Policy (#3529)

IngJohEricsson <notifications@github.com> Tue, 28 April 2020 13:41 UTC

Return-Path: <noreply@github.com>
X-Original-To: quic-issues@ietfa.amsl.com
Delivered-To: quic-issues@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 9D0F83A153A for <quic-issues@ietfa.amsl.com>; Tue, 28 Apr 2020 06:41:04 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.099
X-Spam-Level:
X-Spam-Status: No, score=-3.099 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIMWL_WL_HIGH=-0.001, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, HTML_MESSAGE=0.001, MAILING_LIST_MULTI=-1, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=github.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 5FxMX4HkgWNE for <quic-issues@ietfa.amsl.com>; Tue, 28 Apr 2020 06:41:02 -0700 (PDT)
Received: from out-25.smtp.github.com (out-25.smtp.github.com [192.30.252.208]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 630CC3A1538 for <quic-issues@ietf.org>; Tue, 28 Apr 2020 06:41:02 -0700 (PDT)
Received: from github-lowworker-1b8c660.ash1-iad.github.net (github-lowworker-1b8c660.ash1-iad.github.net [10.56.18.59]) by smtp.github.com (Postfix) with ESMTP id 569AC282CA6 for <quic-issues@ietf.org>; Tue, 28 Apr 2020 06:41:01 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1588081261; bh=NDgup082/11zO89zgp5BxtedkNFGkMRZron9u2V/m6w=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=qJd7o3gJlrc/PN6fjxL8beJNPodcPw5oJuLjMIOmurfBnoE1pXJHVfqLIRLWRkzdE M4CwsTlXEj82MBLcaIJMw78Xu4czx5x7BHyAoEjMEaqm1zookLJ7XDgOPNo1vpvzV4 WCsXJp6JExPF6QPMcCuBBORL/xJaD8Xr5tgU3PKg=
Date: Tue, 28 Apr 2020 06:41:01 -0700
From: IngJohEricsson <notifications@github.com>
Reply-To: quicwg/base-drafts <reply+AFTOJK5TM4DMHMDQ54WUUVN4WQJW3EVBNHHCFSANWY@reply.github.com>
To: quicwg/base-drafts <base-drafts@noreply.github.com>
Cc: Subscribed <subscribed@noreply.github.com>
Message-ID: <quicwg/base-drafts/issues/3529/620615122@github.com>
In-Reply-To: <quicwg/base-drafts/issues/3529@github.com>
References: <quicwg/base-drafts/issues/3529@github.com>
Subject: Re: [quicwg/base-drafts] Changing the Default QUIC ACK Policy (#3529)
Mime-Version: 1.0
Content-Type: multipart/alternative; boundary="--==_mimepart_5ea8326d43455_11f73fbc68acd96036153f"; charset="UTF-8"
Content-Transfer-Encoding: 7bit
Precedence: list
X-GitHub-Sender: IngJohEricsson
X-GitHub-Recipient: quic-issues
X-GitHub-Reason: subscribed
X-Auto-Response-Suppress: All
X-GitHub-Recipient-Address: quic-issues@ietf.org
Archived-At: <https://mailarchive.ietf.org/arch/msg/quic-issues/pwiNUvyPygtpXtj_bmag-VIjpMM>
X-BeenThere: quic-issues@ietf.org
X-Mailman-Version: 2.1.29
List-Id: Notification list for GitHub issues related to the QUIC WG <quic-issues.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/quic-issues>, <mailto:quic-issues-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/quic-issues/>
List-Post: <mailto:quic-issues@ietf.org>
List-Help: <mailto:quic-issues-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/quic-issues>, <mailto:quic-issues-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 28 Apr 2020 13:41:05 -0000

OK, it sounds like a good idea to use 1:10 after 100 packets or so. 

Just one potentially stupid question, Is there any special treatment necessary after an RTO ?

 

/Ingemar

 

 

From: Gorry Fairhurst <notifications@github.com> 
Sent: den 28 april 2020 15:03
To: quicwg/base-drafts <base-drafts@noreply.github.com>
Cc: Ingemar Johansson S <ingemar.s.johansson@ericsson.com>; Comment <comment@noreply.github.com>
Subject: Re: [quicwg/base-drafts] Changing the Default QUIC ACK Policy (#3529)

 

Yes, our proposal counted ACK-eliciting packets at the receiver (because 
the receiver does not in general know the congestion state, so you need 
a heuristic), and we finally chose the same method in currect QUIC 
Chromium - i.e. for the first 100 packets we do not use ACK 1:10, 
changing only after 100 packets.

Gorry

On 28/04/2020 13:34, IngJohEricsson wrote:
> Hi
>
>
>
> I believe that it is beneficial to use a 1:10 policy, I understand 
> that this means that a 1:2 policy that still be used in the initial 
> phase (flow start) or does the timer mechanisms kick in to avoid that 
> ACKs are transmitted too sparsely in this case ?.
>
>
>
> /Ingemar
>
>
>
> From: Gorry Fairhurst <notifications@github.com <mailto:notifications@github.com> >
> Sent: den 28 april 2020 13:38
> To: quicwg/base-drafts <base-drafts@noreply.github.com <mailto:base-drafts@noreply.github.com> >
> Cc: Ingemar Johansson S <ingemar.s.johansson@ericsson.com <mailto:ingemar.s.johansson@ericsson.com> >; Comment 
> <comment@noreply.github.com <mailto:comment@noreply.github.com> >
> Subject: Re: [quicwg/base-drafts] Changing the Default QUIC ACK Policy 
> (#3529)
>
>
>
> On 27/04/2020 17:19, Lars Eggert wrote:
>
> > Folks who care about a change here need to prioritize progressing this
> > issue. We're close to being able to last-call the specs, and would
> > like this resolved in time.
> >
> > —
> > You are receiving this because you authored the thread.
> > Reply to this email directly, view it on GitHub
> > 
> <https://github.com/quicwg/base-drafts/issues/3529#issuecomment-620088318  <https://github.com/quicwg/base-drafts/issues/3529#issuecomment-620088318 > 
> <https://protect2.fireeye.com/v1/url?k=b82acfbc-e4a36075-b82a8f27-0cc47ad93e1c-7966577c56c12be6 <https://protect2.fireeye.com/v1/url?k=b82acfbc-e4a36075-b82a8f27-0cc47ad93e1c-7966577c56c12be6&q=1&e=3996eab0-a615-40ad-8b7d-b572a1fd4189&u=https%3A%2F%2Fgithub.com%2Fquicwg%2Fbase-drafts%2Fissues%2F3529%23issuecomment-620088318> &q=1&e=3996eab0-a615-40ad-8b7d-b572a1fd4189&u=https%3A%2F%2Fgithub.com%2Fquicwg%2Fbase-drafts%2Fissues%2F3529%23issuecomment-620088318> 
> >,
> > or unsubscribe
> > 
> <https://github.com/notifications/unsubscribe-auth/ABYLLETADUCHE7WAN5IFIWDROWWBNANCNFSM4LOJ4RQA  <https://github.com/notifications/unsubscribe-auth/ABYLLETADUCHE7WAN5IFIWDROWWBNANCNFSM4LOJ4RQA%20%0b> 
> <https://protect2.fireeye.com/v1/url?k=d1f11561-8d78baa8-d1f155fa-0cc47ad93e1c-a2e73379d4d76bf3 <https://protect2.fireeye.com/v1/url?k=d1f11561-8d78baa8-d1f155fa-0cc47ad93e1c-a2e73379d4d76bf3&q=1&e=3996eab0-a615-40ad-8b7d-b572a1fd4189&u=https%3A%2F%2Fgithub.com%2Fnotifications%2Funsubscribe-auth%2FABYLLETADUCHE7WAN5IFIWDROWWBNANCNFSM4LOJ4RQA> &q=1&e=3996eab0-a615-40ad-8b7d-b572a1fd4189&u=https%3A%2F%2Fgithub.com%2Fnotifications%2Funsubscribe-auth%2FABYLLETADUCHE7WAN5IFIWDROWWBNANCNFSM4LOJ4RQA> 
> >.
> >
> We’ve completed a round of updated analysis of the proposed change to
> the QUIC spec, using quicly (changing to a 1:10 policy), and chromium
> (which currently does 1:10 by default). Our hope is that this change to
> the spec, to actually make standard end-to-end QUIC work better than
> TCP over asymmetric paths!
>
> This is a short slide deck about the performance of the proposed change:
> https://erg.abdn.ac.uk/users/gorry/ietf/QUIC/QUIC-ack10-24-april-00.pdf
>
> There have been a number of other change made by the QUIC ID editors
> relating to ACK processing, so we wanted to be sure these results were
> up to date. (These results do not consider additional ACKs after
> re-ordering - reflecting the latest text removing that.)
>
> We also really hope this will motivate a change the practice of forcing
> of QUIC fallback to TCP (with PEP/Thining) over highly asymmetric paths.
> People may also be interested in work for L4S to evaluate the impact of
> ACK Thining for TCP-Prague.
>
> Please do provide feedback, or any questions on this - as Lars notes, we
> think the time is running out for considering new changes, even
> relatively simple ones like this.
>
> Gorry
>
> P.S. First email:
> https://mailarchive.ietf.org/arch/msg/quic/NZBbuY88v0lrVspQE2A5br83asA/
>
>
>
>
> —
> You are receiving this because you commented.
> Reply to this email directly, view it on GitHub 
> <https://protect2.fireeye.com/v1/url?k=9d433096-c1ca9f5f-9d43700d-0cc47ad93e1c-30eb55b8449f0bee <https://protect2.fireeye.com/v1/url?k=9d433096-c1ca9f5f-9d43700d-0cc47ad93e1c-30eb55b8449f0bee&q=1&e=3996eab0-a615-40ad-8b7d-b572a1fd4189&u=https%3A%2F%2Fgithub.com%2Fquicwg%2Fbase-drafts%2Fissues%2F3529%23issuecomment-620551738> &q=1&e=3996eab0-a615-40ad-8b7d-b572a1fd4189&u=https%3A%2F%2Fgithub.com%2Fquicwg%2Fbase-drafts%2Fissues%2F3529%23issuecomment-620551738> 
> , or unsubscribe 
> <https://protect2.fireeye.com/v1/url?k=fbb00142-a739ae8b-fbb041d9-0cc47ad93e1c-d874a6a9da42014c <https://protect2.fireeye.com/v1/url?k=fbb00142-a739ae8b-fbb041d9-0cc47ad93e1c-d874a6a9da42014c&q=1&e=3996eab0-a615-40ad-8b7d-b572a1fd4189&u=https%3A%2F%2Fgithub.com%2Fnotifications%2Funsubscribe-auth%2FACRZ2GD2F3JDT6LI5Q4A2NTRO25YTANCNFSM4LOJ4RQA> &q=1&e=3996eab0-a615-40ad-8b7d-b572a1fd4189&u=https%3A%2F%2Fgithub.com%2Fnotifications%2Funsubscribe-auth%2FACRZ2GD2F3JDT6LI5Q4A2NTRO25YTANCNFSM4LOJ4RQA> 
> . 
> <https://github.com/notifications/beacon/ACRZ2GETA2BOY6L5IISTQD3RO25YTA5CNFSM4LOJ4RQKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOET6N4OQ.gif <https://protect2.fireeye.com/v1/url?k=5161f97a-0fc2dd89-5161b9e1-0cc47a696e38-a39dc657fd9acc80&q=1&e=cb617aa2-a952-4ce5-b68f-a420cb5683d3&u=https%3A%2F%2Fgithub.com%2Fnotifications%2Fbeacon%2FACRZ2GETA2BOY6L5IISTQD3RO25YTA5CNFSM4LOJ4RQKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOET6N4OQ.gif> > 
>
>
> —
> You are receiving this because you authored the thread.
> Reply to this email directly, view it on GitHub 
> <https://github.com/quicwg/base-drafts/issues/3529#issuecomment-620577062 <https://protect2.fireeye.com/v1/url?k=b6170f3e-e8b42bcd-b6174fa5-0cc47a696e38-8f37a865b0e1011b&q=1&e=cb617aa2-a952-4ce5-b68f-a420cb5683d3&u=https%3A%2F%2Fgithub.com%2Fquicwg%2Fbase-drafts%2Fissues%2F3529%23issuecomment-620577062> >, 
> or unsubscribe 
> <https://github.com/notifications/unsubscribe-auth/ABYLLEQBOCAEWPFNFDLHIRLRO3EMFANCNFSM4LOJ4RQA <https://protect2.fireeye.com/v1/url?k=5532145a-0b9130a9-553254c1-0cc47a696e38-eb496219e9f8d14b&q=1&e=cb617aa2-a952-4ce5-b68f-a420cb5683d3&u=https%3A%2F%2Fgithub.com%2Fnotifications%2Funsubscribe-auth%2FABYLLEQBOCAEWPFNFDLHIRLRO3EMFANCNFSM4LOJ4RQA> >.
>
-- 
G. Fairhurst, School of Engineering




—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub <https://protect2.fireeye.com/v1/url?k=077a043e-59d920cd-077a44a5-0cc47a696e38-805ecde7097ea8aa&q=1&e=cb617aa2-a952-4ce5-b68f-a420cb5683d3&u=https%3A%2F%2Fgithub.com%2Fquicwg%2Fbase-drafts%2Fissues%2F3529%23issuecomment-620592559> , or unsubscribe <https://protect2.fireeye.com/v1/url?k=130f3f99-4dac1b6a-130f7f02-0cc47a696e38-30f82de726554d52&q=1&e=cb617aa2-a952-4ce5-b68f-a420cb5683d3&u=https%3A%2F%2Fgithub.com%2Fnotifications%2Funsubscribe-auth%2FACRZ2GAPBJIBIQTIMIVZ2ULRO3HZRANCNFSM4LOJ4RQA> .  <https://github.com/notifications/beacon/ACRZ2GCEHJ36MZSD3LU5MGDRO3HZRA5CNFSM4LOJ4RQKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOET6X3LY.gif> 



-- 
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/quicwg/base-drafts/issues/3529#issuecomment-620615122

v2.23.0 | Report a Bug | By Email