IETF Logo Mail Archive

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

Nick Banks <notifications@github.com> Tue, 06 August 2019 02:15 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 36F4F1200E9 for <quic-issues@ietfa.amsl.com>; Mon, 5 Aug 2019 19:15:59 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.454
X-Spam-Level:
X-Spam-Status: No, score=-6.454 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_20=1.546, 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 lOf-8RozXJY6 for <quic-issues@ietfa.amsl.com>; Mon, 5 Aug 2019 19:15:58 -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 E75BF1200DE for <quic-issues@ietf.org>; Mon, 5 Aug 2019 19:15:57 -0700 (PDT)
Date: Mon, 05 Aug 2019 19:15:56 -0700
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1565057756; bh=9OnIiTave3xOcLuoRmKVZHUHypz9CPJJrO48BorOVoE=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=d3FQ7ZSENyU0J9ISACQGyh8opAoBBoHkdh4twaaC97n/Vb4lKKMWsb7DEqqxMHjxu uFNpurmS1H0ag8SlExseKiBuOooTJub7dGF5XEq1A8Pe5Ubnl0PmmRI2VreeWKE5Me f63Y8jw7zfgQt3HR9p3lIhJVrkszuUMPGs3SCMrc=
From: Nick Banks <notifications@github.com>
Reply-To: quicwg/base-drafts <reply+AFTOJKYY2ASPDHGPN3RQULV3KYKVZEVBNHHBY4DNAQ@reply.github.com>
To: quicwg/base-drafts <base-drafts@noreply.github.com>
Cc: Subscribed <subscribed@noreply.github.com>
Message-ID: <quicwg/base-drafts/pull/2954/review/271085979@github.com>
In-Reply-To: <quicwg/base-drafts/pull/2954@github.com>
References: <quicwg/base-drafts/pull/2954@github.com>
Subject: Re: [quicwg/base-drafts] Clarify out of order acking (#2954)
Mime-Version: 1.0
Content-Type: multipart/alternative; boundary="--==_mimepart_5d48e2dcbb792_76733ff6ac6cd96842644c"; charset="UTF-8"
Content-Transfer-Encoding: 7bit
Precedence: list
X-GitHub-Sender: nibanks
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/L6L2QDv8QsfMujL32Xfq5Hy9zB0>
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, 06 Aug 2019 02:15:59 -0000

nibanks approved this pull request.

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?



-- 
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/2954#pullrequestreview-271085979

v2.29.0 | Report a Bug | By Email | System Status