Re: [quicwg/base-drafts] Add details of marking packets lost on PTO (#2624)

ianswett <> Tue, 16 April 2019 01:43 UTC

Return-Path: <>
Received: from localhost (localhost []) by (Postfix) with ESMTP id 33B36120222 for <>; Mon, 15 Apr 2019 18:43:13 -0700 (PDT)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: -8.002
X-Spam-Status: No, score=-8.002 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_MESSAGE=0.001, MAILING_LIST_MULTI=-1, RCVD_IN_DNSWL_HI=-5, RCVD_IN_MSPIKE_H2=-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 P_R8BleisbNV for <>; Mon, 15 Apr 2019 18:43:11 -0700 (PDT)
Received: from ( []) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by (Postfix) with ESMTPS id 57B6D1201C0 for <>; Mon, 15 Apr 2019 18:43:11 -0700 (PDT)
Date: Mon, 15 Apr 2019 18:43:10 -0700
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;; s=pf2014; t=1555378990; bh=/RZeYAI4Lk9S+Qtzhx2VLarPOmdXAw8i4iJqK0xXHI8=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=gCBmst1fWPJ723p4khXHX1evaqzCKZvQx2Kj/doIDqsipY6DxkPExAoQ9liu+pgF3 OPTWdjEI9ukEDrz+xW806KLzVh/rnNVtvB5AGTEIhyEPiOyAJzgyvRxOTB97eHjwFX fv0ZN/QngVmqK/i8ElWiuankmO6rrFSSEfgQqL1A=
From: ianswett <>
Reply-To: quicwg/base-drafts <>
To: quicwg/base-drafts <>
Cc: Subscribed <>
Message-ID: <quicwg/base-drafts/pull/2624/review/>
In-Reply-To: <quicwg/base-drafts/pull/>
References: <quicwg/base-drafts/pull/>
Subject: Re: [quicwg/base-drafts] Add details of marking packets lost on PTO (#2624)
Mime-Version: 1.0
Content-Type: multipart/alternative; boundary="--==_mimepart_5cb5332e151ff_7573fa79c8d45b81405ed"; 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
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: Tue, 16 Apr 2019 01:43:13 -0000

ianswett requested changes on this pull request.

Two things.  If we want to change sender to endpoint in this draft, which I'm not a big fan of, I'd prefer to do so consistently in a single CL.  Also, the more I look at this issue, I think we have our SHOULD/MAY backwards and we SHOULD recommend always sending something, even if the only purpose is to establish loss of outstanding packets.

> @@ -592,7 +592,7 @@ TCP's retransmission timeout period {{?RFC6298}}.
 ### Computing PTO
-When an ack-eliciting packet is transmitted, the sender schedules a timer for

Can you undo the editorializing about sender/endpoint for this PR?  I prefer sender in this context, but I'd prefer to separate that question out.

 ### Sending Probe Packets
-When a PTO timer expires, the sender MUST send one ack-eliciting packet as a
-probe, unless there is nothing to send. A sender MAY send up to two
-ack-eliciting packets, to avoid an expensive consecutive PTO expiration due
-to a single packet loss.
+When a PTO timer expires, an endpoint MUST send at least one ack-eliciting
+packet as a probe, unless there are no ack-eliciting frames 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.
+It is possible that the endpoint has no new or previously-sent data or other
+ack-eliciting frames to send.  This can happen for example when there is no new

ack-eliciting frames to send.  For example, this can happen when there is no new

>      pto_count++
+    if (any ack-eliciting frames available to send):
+      SendOneOrTwoPackets()
+    else:
+      // Mark all packets in flight as lost

This pseudocode makes an excellent argument that we should recommend sending a PING to establish loss.

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