Re: [quicwg/base-drafts] PTO probes are sent too frequently (#3546)

Tatsuhiro Tsujikawa <> Fri, 27 March 2020 13:09 UTC

Return-Path: <>
Received: from localhost (localhost []) by (Postfix) with ESMTP id 5DFFC3A0883 for <>; Fri, 27 Mar 2020 06:09:06 -0700 (PDT)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: -1.554
X-Spam-Status: No, score=-1.554 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, SPF_HELO_NONE=0.001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: (amavisd-new); dkim=pass (1024-bit key)
Received: from ([]) by localhost ( []) (amavisd-new, port 10024) with ESMTP id RFeroH7MYVbr for <>; Fri, 27 Mar 2020 06:09:05 -0700 (PDT)
Received: from ( []) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by (Postfix) with ESMTPS id 10FD63A0875 for <>; Fri, 27 Mar 2020 06:09:04 -0700 (PDT)
Received: from ( []) by (Postfix) with ESMTP id 2AA4F1C0A0A for <>; Fri, 27 Mar 2020 06:09:04 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;; s=pf2014; t=1585314544; bh=Vdat4hnLOPVWuMZ4ausp2LoQmGSBhf4upqxfsWpnOWc=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=rdF2KY7Tas6713AH26+yVkf1iweFSy1Wyv2PIm6sMB+qbMArhU0cMhmYHVMxc2VNs ReMM+WrpRuBVI+WHZuw02Tn+KxR0JZAzsTzVCpTLV3nHg9+TWNcjVhXWAiYiVm6KU6 KIW8/gPKDNFJnw/zCAL9kptzN/CGehRvru2+PvNo=
Date: Fri, 27 Mar 2020 06:09:04 -0700
From: Tatsuhiro Tsujikawa <>
Reply-To: quicwg/base-drafts <>
To: quicwg/base-drafts <>
Cc: Subscribed <>
Message-ID: <quicwg/base-drafts/issues/3546/>
In-Reply-To: <quicwg/base-drafts/issues/>
References: <quicwg/base-drafts/issues/>
Subject: Re: [quicwg/base-drafts] PTO probes are sent too frequently (#3546)
Mime-Version: 1.0
Content-Type: multipart/alternative; boundary="--==_mimepart_5e7dfaf019789_6d5b3faf112cd9682303c1"; charset="UTF-8"
Content-Transfer-Encoding: 7bit
Precedence: list
X-GitHub-Sender: tatsuhiro-t
X-GitHub-Recipient: quic-issues
X-GitHub-Reason: subscribed
X-Auto-Response-Suppress: All
Archived-At: <>
X-Mailman-Version: 2.1.29
List-Id: Notification list for GitHub issues related to the QUIC WG <>
List-Unsubscribe: <>, <>
List-Archive: <>
List-Post: <>
List-Help: <>
List-Subscribe: <>, <>
X-List-Received-Date: Fri, 27 Mar 2020 13:09:07 -0000

Does it make simpler if we reset pto_count only when ack-eliciting not pure probe packet (which includes lost data or new data, not just PING) is received without special casing for anti-deadlock packet?   This ensures that pto_count is reset only when endpoint has made a progress and delaying consecutive PTO if it only receives ACK for pure probe packet.  Server might be in the same situation if client somehow only sends ACK frame in Initial and server keeps sending Initial packet in PTO

You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub: