Re: [quicwg/base-drafts] Clarify out of order acking (#2954)

Rui Paulo <> Tue, 06 August 2019 02:51 UTC

Return-Path: <>
Received: from localhost (localhost []) by (Postfix) with ESMTP id C2E8D120112 for <>; Mon, 5 Aug 2019 19:51:55 -0700 (PDT)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: -6.382
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: (amavisd-new); dkim=pass (1024-bit key)
Received: from ([]) by localhost ( []) (amavisd-new, port 10024) with ESMTP id etpAnxlDs4Op for <>; Mon, 5 Aug 2019 19:51:54 -0700 (PDT)
Received: from ( []) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by (Postfix) with ESMTPS id 7E021120111 for <>; Mon, 5 Aug 2019 19:51:54 -0700 (PDT)
Date: Mon, 05 Aug 2019 19:51:53 -0700
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;; s=pf2014; t=1565059913; bh=QdYHHdt0bBdv+A6QVIasNhgrMk0hT8ML5673gvF9ipI=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=fzoAXrZHv+ysJBgLgit8fShBDNr3r+a6O2mwEWTJYNgw080jTsDFqSN7dNBiB2lsh F8O4avfTrmY3vpKY/oDOHT6h9B2Ty1PVSPSgmc2kEZuFer4m48kEs+eV0mofGkG2ju 6t6+k+gFI2+GgxS+FbUU5HCL3h5ZET3WHJ+yPFPQ=
From: Rui Paulo <>
Reply-To: quicwg/base-drafts <>
To: quicwg/base-drafts <>
Cc: Subscribed <>
Message-ID: <quicwg/base-drafts/pull/2954/>
In-Reply-To: <quicwg/base-drafts/pull/>
References: <quicwg/base-drafts/pull/>
Subject: Re: [quicwg/base-drafts] Clarify out of order acking (#2954)
Mime-Version: 1.0
Content-Type: multipart/alternative; boundary="--==_mimepart_5d48eb49abdc5_7db83f90358cd96c3342d8"; charset="UTF-8"
Content-Transfer-Encoding: 7bit
Precedence: list
X-GitHub-Sender: rpaulo
X-GitHub-Recipient: quic-issues
X-GitHub-Reason: subscribed
X-Auto-Response-Suppress: All
Archived-At: <>
X-Mailman-Version: 2.1.29
List-Id: Notification list for GitHub issues related to the QUIC WG <>
List-Unsubscribe: <>, <>
List-Archive: <>
List-Post: <>
List-Help: <>
List-Subscribe: <>, <>
X-List-Received-Date: Tue, 06 Aug 2019 02:51:56 -0000

> What about the case where you receive an in order ack eliciting packet and then an out of order ack only packet? Should you still rely on delayed ack timer or send an ack immediately?

Yes, this was going to be my follow up question.

Also @janaiyengar what about the ECN paragraph just below it?

You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub: