Re: [quicwg/base-drafts] pto_count should be reset when dropping a packet number space (#3272)

ianswett <> Tue, 04 February 2020 14:46 UTC

Return-Path: <>
Received: from localhost (localhost []) by (Postfix) with ESMTP id 07D33120105 for <>; Tue, 4 Feb 2020 06:46:29 -0800 (PST)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: -6.454
X-Spam-Status: No, score=-6.454 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_20=1.546, 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 92mwHmsLhszM for <>; Tue, 4 Feb 2020 06:46:27 -0800 (PST)
Received: from ( []) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by (Postfix) with ESMTPS id 82F1A12008F for <>; Tue, 4 Feb 2020 06:46:27 -0800 (PST)
Received: from ( []) by (Postfix) with ESMTP id C62B16A03AA for <>; Tue, 4 Feb 2020 06:46:26 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;; s=pf2014; t=1580827586; bh=iJSNuLXjgMkVmbBezE4KvFAOyeKCtgFtkUkdS95GBVM=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=UUKoAiJZ7j70lSEiOPuWwpE/YFiztjpp85E2D62HBghiT/DoMD7VRD2Ot/8F3hYGb JejHEuex9O9gldWsRK9/5k/mZhRjUUnbnz66/m8AVKMwU1KSV0JQ1keppq5b50DmvM NWP3fBvI07Cwzo6br9+/IVqEFkAx5lT4sldWpHGk=
Date: Tue, 04 Feb 2020 06:46:26 -0800
From: ianswett <>
Reply-To: quicwg/base-drafts <>
To: quicwg/base-drafts <>
Cc: Subscribed <>
Message-ID: <quicwg/base-drafts/issues/3272/>
In-Reply-To: <quicwg/base-drafts/issues/>
References: <quicwg/base-drafts/issues/>
Subject: Re: [quicwg/base-drafts] pto_count should be reset when dropping a packet number space (#3272)
Mime-Version: 1.0
Content-Type: multipart/alternative; boundary="--==_mimepart_5e3983c2b6ced_a093fe3130cd95c109965"; 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, 04 Feb 2020 14:46:29 -0000

My plan is:
1) Keep a single pto_count.
2) Reset it when a packet number space is dropped, since that is an indication of forward progress.
3) Re-arm the loss detection timer when dropping a packet number space in case it was armed for the space being dropped.
4) Add some more explanatory text about how pto_count and multiple packet number spaces interact.

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