Re: [quicwg/base-drafts] Suggest endpoints may recognize acks after loss is declared (#3956)

Martin Thomson <notifications@github.com> Mon, 27 July 2020 04:11 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 27AE03A1686 for <quic-issues@ietfa.amsl.com>; Sun, 26 Jul 2020 21:11:20 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.009
X-Spam-Level:
X-Spam-Status: No, score=-2.009 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_16=1.092, HTML_MESSAGE=0.001, MAILING_LIST_MULTI=-1, RCVD_IN_MSPIKE_H2=-0.001, 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 yFGSX17PKw7K for <quic-issues@ietfa.amsl.com>; Sun, 26 Jul 2020 21:11:19 -0700 (PDT)
Received: from out-18.smtp.github.com (out-18.smtp.github.com [192.30.252.201]) (using TLSv1.2 with cipher ADH-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 03B623A1683 for <quic-issues@ietf.org>; Sun, 26 Jul 2020 21:11:18 -0700 (PDT)
Received: from github-lowworker-a27607f.ash1-iad.github.net (github-lowworker-a27607f.ash1-iad.github.net [10.56.18.61]) by smtp.github.com (Postfix) with ESMTP id 4577F340E08 for <quic-issues@ietf.org>; Sun, 26 Jul 2020 21:11:18 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1595823078; bh=wKvnkdjayUmtt3ngOMWcsaLChJc+L05JNgWWgqHHf4U=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=P1O0r3CSmMjDawXcFoOExcRKZCaJVoaRc51iotsBZd9iypMNGKXbHPg2xV2+9HFrN /JYplA4DlkGpO0xJ72/wW8MOQsuHanBwl82KsjfQBxaGqUOafAEMU5cKlRhmvJ6idV YYr7VL0qGk+ysyM/5YCQSioS7JN7/HnI4mI3RW3M=
Date: Sun, 26 Jul 2020 21:11:18 -0700
From: Martin Thomson <notifications@github.com>
Reply-To: quicwg/base-drafts <reply+AFTOJKYYJ5XRKC3WUEJ5GGN5FI2ONEVBNHHCPIHZLY@reply.github.com>
To: quicwg/base-drafts <base-drafts@noreply.github.com>
Cc: Subscribed <subscribed@noreply.github.com>
Message-ID: <quicwg/base-drafts/issues/3956/664108552@github.com>
In-Reply-To: <quicwg/base-drafts/issues/3956@github.com>
References: <quicwg/base-drafts/issues/3956@github.com>
Subject: Re: [quicwg/base-drafts] Suggest endpoints may recognize acks after loss is declared (#3956)
Mime-Version: 1.0
Content-Type: multipart/alternative; boundary="--==_mimepart_5f1e53e6354a7_3c133f89b2acd96c735743"; charset="UTF-8"
Content-Transfer-Encoding: 7bit
Precedence: list
X-GitHub-Sender: martinthomson
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/yN44hZRztAMKcngdzuFZDA1lipo>
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: Mon, 27 Jul 2020 04:11:20 -0000

FWIW, our implementation, as of a little while ago, tracks for `>` the current PTO.  If everything is working nicely, that limits our commitment.  As we are sending probes, the time lengthens so that we send a probe before discarding state.  If it takes two probes to get an ACK, we won't recognize that, but we will always catch an ACK for the last set of probes.  And the state commitment is minimal unless we're forced to probe.

-- 
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/3956#issuecomment-664108552