IETF Logo Mail Archive

Re: [quicwg/base-drafts] MAY send 1 packet entering recovery (#3443)

ianswett <notifications@github.com> Tue, 11 February 2020 23:11 UTC

Return-Path: <noreply@github.com>
X-Original-To: quic-issues@ietfa.amsl.com
Delivered-To: quic-issues@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 3A0D0120826 for <quic-issues@ietfa.amsl.com>; Tue, 11 Feb 2020 15:11:40 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.682
X-Spam-Level:
X-Spam-Status: No, score=-3.682 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_24=1.618, HTML_MESSAGE=0.001, MAILING_LIST_MULTI=-1, RCVD_IN_DNSWL_MED=-2.3, SPF_HELO_NONE=0.001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=github.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id cIYkiawNjnCR for <quic-issues@ietfa.amsl.com>; Tue, 11 Feb 2020 15:11:36 -0800 (PST)
Received: from out-28.smtp.github.com (out-28.smtp.github.com [192.30.252.211]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 2B00912004E for <quic-issues@ietf.org>; Tue, 11 Feb 2020 15:11:36 -0800 (PST)
Received: from github-lowworker-a6a2749.va3-iad.github.net (github-lowworker-a6a2749.va3-iad.github.net [10.48.16.62]) by smtp.github.com (Postfix) with ESMTP id EB3A58C006F for <quic-issues@ietf.org>; Tue, 11 Feb 2020 15:11:34 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1581462694; bh=jMifK8TnyXGq5p/P2u7mIijlguLz9FPqzTWQmclrvVc=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=gbgb/Q2niOu3KdWsl9dlmq+11C7k6oDFbLx/3OiLyGg7ZiS8Sshz6hfcjL+3AMxmL NwVza45BAoBbJtZoyxu0iMVry3Y/t5vcs5TT3XBHIUkD5qRBDOhk+XnmjOhSlT5pUB tDci2UAgF147bhq7aqBAIp7vKoeDeA29+ZgKXGNI=
Date: Tue, 11 Feb 2020 15:11:34 -0800
From: ianswett <notifications@github.com>
Reply-To: quicwg/base-drafts <reply+AFTOJK45WMZW5YQZ35NHKDN4KBTSNEVBNHHCDAQ2C4@reply.github.com>
To: quicwg/base-drafts <base-drafts@noreply.github.com>
Cc: Subscribed <subscribed@noreply.github.com>
Message-ID: <quicwg/base-drafts/pull/3443/c584904542@github.com>
In-Reply-To: <quicwg/base-drafts/pull/3443@github.com>
References: <quicwg/base-drafts/pull/3443@github.com>
Subject: Re: [quicwg/base-drafts] MAY send 1 packet entering recovery (#3443)
Mime-Version: 1.0
Content-Type: multipart/alternative; boundary="--==_mimepart_5e4334a6dc909_42fb3f8dc68cd96071878"; 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
X-GitHub-Recipient-Address: quic-issues@ietf.org
Archived-At: <https://mailarchive.ietf.org/arch/msg/quic-issues/kO-B2hTZIsmQ7PvtKTAt_qEAnYM>
X-BeenThere: quic-issues@ietf.org
X-Mailman-Version: 2.1.29
List-Id: Notification list for GitHub issues related to the QUIC WG <quic-issues.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/quic-issues>, <mailto:quic-issues-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/quic-issues/>
List-Post: <mailto:quic-issues@ietf.org>
List-Help: <mailto:quic-issues-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/quic-issues>, <mailto:quic-issues-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 11 Feb 2020 23:11:40 -0000

Adding language against sending new data or data besides data that's been lost couples the "can I send" with "what should I send" questions more than I would like unless it's absolutely critical.

FYI, to be declared lost, it must be in-flight: https://github.com/quicwg/base-drafts/blob/master/draft-ietf-quic-recovery.md#acknowledgement-based-detection-ack-loss-detection
"A packet is declared lost if it meets all the following conditions:
  * The packet is unacknowledged, in-flight, and was sent prior to an acknowledged packet."

-- 
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/quicwg/base-drafts/pull/3443#issuecomment-584904542

v2.23.0 | Report a Bug | By Email