Re: [quicwg/base-drafts] Pseudocode fix: Data should be sent on loss-threshold timer (#2604)

Jana Iyengar <> Fri, 12 April 2019 23:48 UTC

Return-Path: <>
Received: from localhost (localhost []) by (Postfix) with ESMTP id 0DC54120348 for <>; Fri, 12 Apr 2019 16:48:46 -0700 (PDT)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: -6.597
X-Spam-Status: No, score=-6.597 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_28=1.404, HTML_MESSAGE=0.001, MAILING_LIST_MULTI=-1, RCVD_IN_DNSWL_HI=-5, 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 DIMSuj_P54va for <>; Fri, 12 Apr 2019 16:48:44 -0700 (PDT)
Received: from ( []) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by (Postfix) with ESMTPS id 69E061201BC for <>; Fri, 12 Apr 2019 16:48:44 -0700 (PDT)
Date: Fri, 12 Apr 2019 16:48:43 -0700
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;; s=pf2014; t=1555112923; bh=i9wUXbXV82WR0EvPCEepG3ALv/ONcedBkwTvd43EeCk=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=nGRuPWrD5daTOgayl9O9fD/N4mSxRFno7qr2fxOBn2bdrKeysTPISqnwqCNElNpG0 9un0NemZ0BU8Lq/eLv+hANbE3H6ctpa6xhDV58OI/Eh4AbdWiBUm1KG1n/+1GReLa+ arS5M78j1nb9nrdTLwkGPq5XNIQvP/X4YUmOQg94=
From: Jana Iyengar <>
Reply-To: quicwg/base-drafts <>
To: quicwg/base-drafts <>
Cc: Subscribed <>
Message-ID: <quicwg/base-drafts/issues/2604/>
In-Reply-To: <quicwg/base-drafts/issues/>
References: <quicwg/base-drafts/issues/>
Subject: Re: [quicwg/base-drafts] Pseudocode fix: Data should be sent on loss-threshold timer (#2604)
Mime-Version: 1.0
Content-Type: multipart/alternative; boundary="--==_mimepart_5cb123db6bc21_53af3ffb564d45b852388"; charset="UTF-8"
Content-Transfer-Encoding: 7bit
Precedence: list
X-GitHub-Sender: janaiyengar
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, 12 Apr 2019 23:48:46 -0000

Yeah, I realized that we don't really talk about PRR. If we want to bring the entire mechanism here, that might be a bit of work. How about we do as you propose above (without PRR in the comment), add some text about how a sender can implement PRR if they want a smoother way out of recovery with a reference to the PRR draft?

Separately, is it worth filing an issue to do PRR for QUIC? Since we don't assume pacing here, it might actually be useful. It will be some work to do it though. WDYT?

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