Re: [quicwg/base-drafts] Up to two full-sized datagrams, not packets (#2915)

MikkelFJ <> Sun, 21 July 2019 13:59 UTC

Return-Path: <>
Received: from localhost (localhost []) by (Postfix) with ESMTP id 0EA39120020 for <>; Sun, 21 Jul 2019 06:59:17 -0700 (PDT)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: -7.999
X-Spam-Status: No, score=-7.999 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, HTML_IMAGE_ONLY_32=0.001, HTML_MESSAGE=0.001, MAILING_LIST_MULTI=-1, RCVD_IN_DNSWL_HI=-5, 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 5JNjQtwhlqZ6 for <>; Sun, 21 Jul 2019 06:59:15 -0700 (PDT)
Received: from ( []) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by (Postfix) with ESMTPS id 367F4120134 for <>; Sun, 21 Jul 2019 06:59:15 -0700 (PDT)
Date: Sun, 21 Jul 2019 06:59:14 -0700
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;; s=pf2014; t=1563717554; bh=oq/9+R2JYg8eepgrmUtHrSE2Dln5nYfMs9BRZl1vG7o=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=Kd10Ap6wx8af3KFJEV9QDVKTfRkpdQgiUBEtMPorMv9edPCb7W54dg/GRAjnRXQk9 LiR9VtFGZGuMWRx6xzLJGOyzc067CFeFK85kE/91it3WGcSSXzqmqkopzuMqU3gwQQ wT3qtk00DvDXFKpu/e8rGeq8UGZut4+T2uVupKcU=
From: MikkelFJ <>
Reply-To: quicwg/base-drafts <>
To: quicwg/base-drafts <>
Cc: Subscribed <>
Message-ID: <quicwg/base-drafts/pull/2915/review/>
In-Reply-To: <quicwg/base-drafts/pull/>
References: <quicwg/base-drafts/pull/>
Subject: Re: [quicwg/base-drafts] Up to two full-sized datagrams, not packets (#2915)
Mime-Version: 1.0
Content-Type: multipart/alternative; boundary="--==_mimepart_5d346fb2a1bfd_4e803f8c3d6cd960121614"; charset="UTF-8"
Content-Transfer-Encoding: 7bit
Precedence: list
X-GitHub-Sender: mikkelfj
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: Sun, 21 Jul 2019 13:59:17 -0000

mikkelfj commented on this pull request.

> @@ -514,7 +514,7 @@ and larger thresholds increase loss detection delay.
 ## Probe Timeout {#pto}
-A Probe Timeout (PTO) triggers sending one or two probe packets when
+A Probe Timeout (PTO) triggers sending one or two probe datagrams when
 ack-eliciting packets are not acknowledged within the expected period of
 time or the handshake has not been completed.  A PTO enables a connection to
 recover from loss of tail packets or acks. The PTO algorithm used in QUIC

recover from loss of tail packets or ACKs. The PTO algorithm used in QUIC

> @@ -598,8 +598,8 @@ discarded.
 When a PTO timer expires, a sender MUST send at least one ack-eliciting packet
 as a probe, unless there is no data available to send.  An endpoint MAY send up
-to two ack-eliciting packets, to avoid an expensive consecutive PTO expiration
-due to a single packet loss.
+to two full sized datagrams containing ack-eliciting packets, to avoid an
+expensive consecutive PTO expiration due to a single lost datagram.

Where is that limit of two specified? Here? Why?

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