IETF Logo Mail Archive

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

Kazuho Oku <notifications@github.com> Mon, 27 July 2020 16:58 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 116293A1B60 for <quic-issues@ietfa.amsl.com>; Mon, 27 Jul 2020 09:58:44 -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 XOgE578XFq0z for <quic-issues@ietfa.amsl.com>; Mon, 27 Jul 2020 09:58:42 -0700 (PDT)
Received: from out-21.smtp.github.com (out-21.smtp.github.com [192.30.252.204]) (using TLSv1.2 with cipher ADH-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id E39543A1B45 for <quic-issues@ietf.org>; Mon, 27 Jul 2020 09:58:41 -0700 (PDT)
Received: from github-lowworker-9bcb4a1.ac4-iad.github.net (github-lowworker-9bcb4a1.ac4-iad.github.net [10.52.25.84]) by smtp.github.com (Postfix) with ESMTP id A8358520E94 for <quic-issues@ietf.org>; Mon, 27 Jul 2020 09:58:40 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1595869120; bh=L4SlDtLxjRzkz+b60BH52MdZlq0amGdqAHgr6J9mUaI=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=ZaIL3dqOdcUYI6UacPzGoLIS6Tt+3i7I7eBC3S6AtWaBX0jBsBG/CkJnUVyONIbne 9eQx0eh3+80BYKqQuLnVT9Yx4LggJShGtB0xbWKWxxZ1vWhTxT/KjUWfu3B4uMv3EY +mf5cQaOaT5tnF7U+UDks4FH2Jt7HsrgpJO+b2m8=
Date: Mon, 27 Jul 2020 09:58:40 -0700
From: Kazuho Oku <notifications@github.com>
Reply-To: quicwg/base-drafts <reply+AFTOJKZHDJ4HZ3EMTRYBTWN5FLUMBEVBNHHCPIHZLY@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/664516741@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_5f1f07c099930_54503fee76ecd96c7188d"; charset="UTF-8"
Content-Transfer-Encoding: 7bit
Precedence: list
X-GitHub-Sender: kazuho
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/sMKcPtqVm7Ou0aJ2CjZ_TVh3sAg>
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 16:58:48 -0000

I'm fine with PTO, and I prefer PTO above RTT.

There could be reasons where there are some packet reordering due to multiple paths being used (e.g., ECMP, clustered endpoint). In such case, the variance of latency becomes more like a constant independent of RTT.

I think it is a good idea to recommend a value (i.e. PTO) that can cover such constant even if RTT is very small. PTO has `max_ack_delay` that would cover that constant.

-- 
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-664516741

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