Re: [quicwg/base-drafts] Clarify ACK sending text in transport (#3480)

Igor Lubashev <notifications@github.com> Sun, 01 March 2020 16:44 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 E2E933A0783 for <quic-issues@ietfa.amsl.com>; Sun, 1 Mar 2020 08:44:58 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.482
X-Spam-Level:
X-Spam-Status: No, score=-1.482 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_IMAGE_ONLY_24=1.618, HTML_MESSAGE=0.001, MAILING_LIST_MULTI=-1, 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 K69Kg36BuHJe for <quic-issues@ietfa.amsl.com>; Sun, 1 Mar 2020 08:44:57 -0800 (PST)
Received: from out-3.smtp.github.com (out-3.smtp.github.com [192.30.252.194]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 4690E3A08E2 for <quic-issues@ietf.org>; Sun, 1 Mar 2020 08:44:57 -0800 (PST)
Received: from github-lowworker-f1f7af9.ash1-iad.github.net (github-lowworker-f1f7af9.ash1-iad.github.net [10.56.111.13]) by smtp.github.com (Postfix) with ESMTP id 0DD442C0A51 for <quic-issues@ietf.org>; Sun, 1 Mar 2020 08:44:56 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1583081096; bh=LhJ2EvvgoWZbB8Lm9EE+TmHHYq14nqorlwVTReQacZQ=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=hHGdKkCtiQpLNG/uqga0wan8egBNha53k42nIiemBOpyWhYR8OACc/BdMDAnKEVpx Vmck8XIt3BW2clBQx2UWLZNa1Dx6JhGkRnwJSRR6XnY8bgI7OAYt4whtDvmcysnVh6 F3CVPeU6nMQT9rTJQNvJy9g3WwlXgTChumi6eXbU=
Date: Sun, 01 Mar 2020 08:44:55 -0800
From: Igor Lubashev <notifications@github.com>
Reply-To: quicwg/base-drafts <reply+AFTOJKYL5ISBZWSTNIXASVF4M7DYPEVBNHHCD6AV3A@reply.github.com>
To: quicwg/base-drafts <base-drafts@noreply.github.com>
Cc: Subscribed <subscribed@noreply.github.com>
Message-ID: <quicwg/base-drafts/issues/3480/593117576@github.com>
In-Reply-To: <quicwg/base-drafts/issues/3480@github.com>
References: <quicwg/base-drafts/issues/3480@github.com>
Subject: Re: [quicwg/base-drafts] Clarify ACK sending text in transport (#3480)
Mime-Version: 1.0
Content-Type: multipart/alternative; boundary="--==_mimepart_5e5be687efe2b_47cc3fb58d8cd96c369631"; charset=UTF-8
Content-Transfer-Encoding: 7bit
Precedence: list
X-GitHub-Sender: igorlord
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/fFE41YK-wCebRfJ_YxHRAqNGDdc>
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: Sun, 01 Mar 2020 16:44:59 -0000

> a sender cannot rely on receiving an acknowledgement of every packet, whether it's ack-eliciting or not, because ACKs get lost.

I do not understand this statement. Yes, packets with ACKs can get lost. But the mechanics of QUIC is that until an ACK-of-the-ACK is received, the sender will continue to acknowledge all packet ranges from the original ACK in every subsequent ACK. So if at least some ACK gets through, everything will get ACKed, despite of some losses of ACKs.

-- 
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/3480#issuecomment-593117576