Re: [quicwg/base-drafts] Persistent congestion period: text and pseudo-code don't agree (#3972)

Jana Iyengar <notifications@github.com> Wed, 29 July 2020 16:48 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 3EB6E3A0C97 for <quic-issues@ietfa.amsl.com>; Wed, 29 Jul 2020 09:48:38 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.555
X-Spam-Level:
X-Spam-Status: No, score=-1.555 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, DKIM_VALID_EF=-0.1, HTML_IMAGE_ONLY_20=1.546, HTML_MESSAGE=0.001, MAILING_LIST_MULTI=-1, RCVD_IN_MSPIKE_H2=-0.001, 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 0T_ebvhplgob for <quic-issues@ietfa.amsl.com>; Wed, 29 Jul 2020 09:48:36 -0700 (PDT)
Received: from out-25.smtp.github.com (out-25.smtp.github.com [192.30.252.208]) (using TLSv1.2 with cipher ADH-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 3E0333A0C94 for <quic-issues@ietf.org>; Wed, 29 Jul 2020 09:48:36 -0700 (PDT)
Received: from github-lowworker-1ac52d7.ash1-iad.github.net (github-lowworker-1ac52d7.ash1-iad.github.net [10.56.25.52]) by smtp.github.com (Postfix) with ESMTP id 314CD840E4A for <quic-issues@ietf.org>; Wed, 29 Jul 2020 09:48:35 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1596041315; bh=4F8e7s7j4I9jgkQ7eqkvabQ7rtKQpFg9HP2LILcg0HQ=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=FJZmprar8neWxmv2tRqf/xipn38gllgAHHE4q6U07Y5dWfYEN6cC2X5Ag1FrtPxm7 noIPSAtAxdK5WhbJc/xXZuws3ybEom+LZTqSqNHr8I4t/u9YqR2/r0M4+CJJIvFVzC 5HVD3XbqD2jDM+4dIYiyz2D0n6J0SoSU7l3vsu+Y=
Date: Wed, 29 Jul 2020 09:48:35 -0700
From: Jana Iyengar <notifications@github.com>
Reply-To: quicwg/base-drafts <reply+AFTOJK5TQYROOF2GFMRD3HF5FWEWHEVBNHHCPUC7GA@reply.github.com>
To: quicwg/base-drafts <base-drafts@noreply.github.com>
Cc: Subscribed <subscribed@noreply.github.com>
Message-ID: <quicwg/base-drafts/issues/3972/665777673@github.com>
In-Reply-To: <quicwg/base-drafts/issues/3972@github.com>
References: <quicwg/base-drafts/issues/3972@github.com>
Subject: Re: [quicwg/base-drafts] Persistent congestion period: text and pseudo-code don't agree (#3972)
Mime-Version: 1.0
Content-Type: multipart/alternative; boundary="--==_mimepart_5f21a86322bc6_1a6c16f830048e"; 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
X-GitHub-Recipient-Address: quic-issues@ietf.org
Archived-At: <https://mailarchive.ietf.org/arch/msg/quic-issues/c9Xr5Ync5m7TU3TkDhcP-VjpkIc>
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: Wed, 29 Jul 2020 16:48:39 -0000

Option 1 and 2 have a behavior difference with the following implication:

With option 2, a sender might mark persistent congestion with fewer PTOs than if the sender had a more accurate RTT estimate. This is arguably not a significant concern, since:
- the sender will still have sent at least two packets in that duration and marked them lost, since you need two ack-eliciting packets to be lost to declare persistent congestion; and
- the number of packets sent is also sensitive to how the application sends, and a sender cannot rely on that anyway.

Option 2 has the benefit that it is simpler to implement.

On balance, I think Option 2 is better, though it does make this a design change.

-- 
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/issues/3972#issuecomment-665777673