IETF Logo Mail Archive

Re: [quicwg/base-drafts] Proposed fix for #3987 (#4071)

ianswett <notifications@github.com> Mon, 07 September 2020 23:04 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 AE4733A0D06 for <quic-issues@ietfa.amsl.com>; Mon, 7 Sep 2020 16:04:49 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.555
X-Spam-Level:
X-Spam-Status: No, score=-1.555 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_20=1.546, 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 5ClB1e0ssK7F for <quic-issues@ietfa.amsl.com>; Mon, 7 Sep 2020 16:04:48 -0700 (PDT)
Received: from out-26.smtp.github.com (out-26.smtp.github.com [192.30.252.209]) (using TLSv1.2 with cipher ADH-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id D7A443A0D05 for <quic-issues@ietf.org>; Mon, 7 Sep 2020 16:04:44 -0700 (PDT)
Received: from github-lowworker-a6a2749.va3-iad.github.net (github-lowworker-a6a2749.va3-iad.github.net [10.48.16.62]) by smtp.github.com (Postfix) with ESMTP id E6FC25E0403 for <quic-issues@ietf.org>; Mon, 7 Sep 2020 16:04:43 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1599519883; bh=kwlIrcveGQ+/fD7WsCjePFYvkTPurztgVIg0MZ6/QFI=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=mrEDbVBU0yzqmwzNHhfDwg8nGWx1XMO+qhurLS/XdtRJKm/HAxIZA4RrHzLwMCq+Q ndlC4iaNMqFNyvRt8FEZMZnURbxI6oY/BB8FFrQ7U+umbLqaCiT244/m/QEFbzHHoj LdtnO49A3wdmju9MXS76o0Sn/gg1TDxUu0e+pXPY=
Date: Mon, 07 Sep 2020 16:04:43 -0700
From: ianswett <notifications@github.com>
Reply-To: quicwg/base-drafts <reply+AFTOJK235J646LROSKJ6ALF5MKOYXEVBNHHCSPRX6E@reply.github.com>
To: quicwg/base-drafts <base-drafts@noreply.github.com>
Cc: Subscribed <subscribed@noreply.github.com>
Message-ID: <quicwg/base-drafts/pull/4071/c688534747@github.com>
In-Reply-To: <quicwg/base-drafts/pull/4071@github.com>
References: <quicwg/base-drafts/pull/4071@github.com>
Subject: Re: [quicwg/base-drafts] Proposed fix for #3987 (#4071)
Mime-Version: 1.0
Content-Type: multipart/alternative; boundary="--==_mimepart_5f56bc8bd7007_7c7b19f047717"; charset="UTF-8"
Content-Transfer-Encoding: 7bit
Precedence: list
X-GitHub-Sender: ianswett
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/nWKWVaxku43xVuP3jdDCcD97FIU>
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, 07 Sep 2020 23:04:50 -0000

@larseggert in some cases, the reason for using PTO is to ensure there's time to PTO retransmit, so I don't think this change currently captures that reason in this cases.

I agree that's the basis of the issue as it stands, but I think the better question is why use PTO in different cases.  I think the max_ack_delay is not particularly interesting in any of these cases.

-- 
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/4071#issuecomment-688534747

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