Re: [quicwg/base-drafts] Remove 1 RTT delayed ack requirement (#3055)

mirjak <notifications@github.com> Wed, 16 October 2019 18:06 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 A9D4412080C for <quic-issues@ietfa.amsl.com>; Wed, 16 Oct 2019 11:06:40 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.382
X-Spam-Level:
X-Spam-Status: No, score=-6.382 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, HTML_IMAGE_ONLY_24=1.618, HTML_MESSAGE=0.001, MAILING_LIST_MULTI=-1, RCVD_IN_DNSWL_HI=-5, SPF_HELO_NONE=0.001, SPF_PASS=-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 zph3zRUzT-yj for <quic-issues@ietfa.amsl.com>; Wed, 16 Oct 2019 11:06:39 -0700 (PDT)
Received: from out-22.smtp.github.com (out-22.smtp.github.com [192.30.252.205]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 36F711200F3 for <quic-issues@ietf.org>; Wed, 16 Oct 2019 11:06:39 -0700 (PDT)
Received: from github-lowworker-ca5950c.va3-iad.github.net (github-lowworker-ca5950c.va3-iad.github.net [10.48.17.57]) by smtp.github.com (Postfix) with ESMTP id 943FCA0855 for <quic-issues@ietf.org>; Wed, 16 Oct 2019 11:06:38 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1571249198; bh=VtdA7redOdXJShyZntxI9ynpD6KbYvaL6pWS/ZFzeLE=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=LbaMRnq/00ebU6rT1xKcgTHVOjbvPA6qTcvZ0nlh4T1RS2xmVhpjVs+EJ46hH8m4F 2PVoeECgbTLxFRVO7NHB/6MC2dlyVy2yFSomwHKASVyv4cr6z7VkqXxHpbxwcX7n0O TBe5YnUBk/EYLWu0S/ZqlihdwAz91wpoPHOao5Zw=
Date: Wed, 16 Oct 2019 11:06:38 -0700
From: mirjak <notifications@github.com>
Reply-To: quicwg/base-drafts <reply+AFTOJK3YIIEUXC2PRMJBADF3WSOL5EVBNHHB3FVVWY@reply.github.com>
To: quicwg/base-drafts <base-drafts@noreply.github.com>
Cc: Subscribed <subscribed@noreply.github.com>
Message-ID: <quicwg/base-drafts/pull/3055/c542823631@github.com>
In-Reply-To: <quicwg/base-drafts/pull/3055@github.com>
References: <quicwg/base-drafts/pull/3055@github.com>
Subject: Re: [quicwg/base-drafts] Remove 1 RTT delayed ack requirement (#3055)
Mime-Version: 1.0
Content-Type: multipart/alternative; boundary="--==_mimepart_5da75c2e84e92_44c33fd6034cd95c768bc"; charset=UTF-8
Content-Transfer-Encoding: 7bit
Precedence: list
X-GitHub-Sender: mirjak
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/Dr_30tkcTWsIZyw63EmG91P708E>
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: Wed, 16 Oct 2019 18:06:41 -0000

Sorry I'm late here but I think it would still be good to mention that congestion control usually is supposed to work on a RTT granularity and if you send less ACKs than one per RTT that can have an impact on cc. I don't think this has to be a normative requirement given you have normative requirements on max_ack_delay and a reasonable default value but it would still be good to mention this dependency as cc is done on sender and ACKing on  receiver and therefore it might not always that obvious.

-- 
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/pull/3055#issuecomment-542823631