[quicwg/base-drafts] unclear definition of persistent congestion (#3937)

Marten Seemann <notifications@github.com> Wed, 22 July 2020 02:06 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 374533A086C for <quic-issues@ietfa.amsl.com>; Tue, 21 Jul 2020 19:06:45 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.483
X-Spam-Level:
X-Spam-Status: No, score=-1.483 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_24=1.618, 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 lxpkMZrqbsrJ for <quic-issues@ietfa.amsl.com>; Tue, 21 Jul 2020 19:06:44 -0700 (PDT)
Received: from out-14.smtp.github.com (out-14.smtp.github.com [192.30.254.197]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id F24063A0869 for <quic-issues@ietf.org>; Tue, 21 Jul 2020 19:06:43 -0700 (PDT)
Received: from github-lowworker-d1d6e31.ash1-iad.github.net (github-lowworker-d1d6e31.ash1-iad.github.net [10.56.105.50]) by smtp.github.com (Postfix) with ESMTP id 4FFFA121244 for <quic-issues@ietf.org>; Tue, 21 Jul 2020 19:06:43 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1595383603; bh=6kUlIXg/LZ0JnvXpsw+PK8cKU2sXYg0O7U3I1nHRh8c=; h=Date:From:Reply-To:To:Cc:Subject:List-ID:List-Archive:List-Post: List-Unsubscribe:From; b=p33H8lmwwCcCzbVfeqoVJ38ZPYfMn3S6jFTgewO88fxjhBRVspWooaR3bIUECHSGK vfhyu1+YZ2iPusPLQqouAV1ZDtnVn/MFfTsLA+gjY1mQ8RKw08XfeLgQnCw0m6dym4 sainshLj0donBl/L8fEiaPIVMlGrkEVMXX4vhQjo=
Date: Tue, 21 Jul 2020 19:06:43 -0700
From: Marten Seemann <notifications@github.com>
Reply-To: quicwg/base-drafts <reply+AFTOJK65ILS7URS35OXYWHF5EOADHEVBNHHCPCXWJY@reply.github.com>
To: quicwg/base-drafts <base-drafts@noreply.github.com>
Cc: Subscribed <subscribed@noreply.github.com>
Message-ID: <quicwg/base-drafts/issues/3937@github.com>
Subject: [quicwg/base-drafts] unclear definition of persistent congestion (#3937)
Mime-Version: 1.0
Content-Type: multipart/alternative; boundary="--==_mimepart_5f179f33aef3_7ba13f7fd8ccd96c16562b"; charset="UTF-8"
Content-Transfer-Encoding: 7bit
Precedence: list
X-GitHub-Sender: marten-seemann
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/LE59guIlhoIKqRup5HT6l-GsjUU>
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, 22 Jul 2020 02:06:45 -0000

A sender sends a tail of 10 packets, packet number 1 to 10. It now receives an acknowledgement for packets 5 and 10, which establishes the loss of all other packets.

It's not clear how to perform the check for persistent congestion now. Several options come to mind:

1. check if the period between 6 and 9 is longer than 3*PTO
2. check if either the period between packet 1 and 4 or the period between packet 6 and 9 is longer than 3*PTO
3. The ACK doesn't establish loss of *all* tail packets, so there's no persistent congestion.

In an offline discussion, both @mjoras and @goelvidhi expressed preferences for different options here. I'm not sure what the right thing to do is here, but at least the draft should be clearer on what exactly establishes persistent congestion and what doesn't.


-- 
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/3937