[quicwg/base-drafts] Starting persistent congestion on a ack-eliciting packet (#3941)
Martin Thomson <notifications@github.com> Wed, 22 July 2020 12:13 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 8343A3A0AD8 for <quic-issues@ietfa.amsl.com>; Wed, 22 Jul 2020 05:13:40 -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 P0GSh2W692Dy for <quic-issues@ietfa.amsl.com>; Wed, 22 Jul 2020 05:13:39 -0700 (PDT)
Received: from out-21.smtp.github.com (out-21.smtp.github.com [192.30.252.204]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 4DEFD3A0AD7 for <quic-issues@ietf.org>; Wed, 22 Jul 2020 05:13:39 -0700 (PDT)
Received: from github-lowworker-56fcc46.va3-iad.github.net (github-lowworker-56fcc46.va3-iad.github.net [10.48.102.32]) by smtp.github.com (Postfix) with ESMTP id 4D91FA1F83 for <quic-issues@ietf.org>; Wed, 22 Jul 2020 05:13:38 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1595420018; bh=APuGwfkqznHz7DGf9Qn+K6cTH/GDHvNRHYU4gFztqns=; h=Date:From:Reply-To:To:Cc:Subject:List-ID:List-Archive:List-Post: List-Unsubscribe:From; b=l/28kDn7g1JngBc/o71iZjIs5Lm5IdnJ+DwJRbcO8Voi08ES83ykRFkOk9Oe7zVe+ 4wc//OlMBzCvB6ctSDQ4fKj1tUPA/V6UtkvLHEaH/bv6v0s7ZDmDbFL0po3Sk9iZdo Mf7VcHGlFW1w2ncMUmT+PxJWyQl+6Dg94KKI6RpA=
Date: Wed, 22 Jul 2020 05:13:38 -0700
From: Martin Thomson <notifications@github.com>
Reply-To: quicwg/base-drafts <reply+AFTOJK7LP7CA7ZCYRVR627V5EQHHFEVBNHHCPD33TU@reply.github.com>
To: quicwg/base-drafts <base-drafts@noreply.github.com>
Cc: Subscribed <subscribed@noreply.github.com>
Message-ID: <quicwg/base-drafts/issues/3941@github.com>
Subject: [quicwg/base-drafts] Starting persistent congestion on a ack-eliciting packet (#3941)
Mime-Version: 1.0
Content-Type: multipart/alternative; boundary="--==_mimepart_5f182d723d797_7a9c3fa8df2cd9645530ae"; charset="UTF-8"
Content-Transfer-Encoding: 7bit
Precedence: list
X-GitHub-Sender: martinthomson
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/-zjE-6dZWr1wlZnv8zv2XHr8RKU>
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 12:13:41 -0000
Persistent congestion has to start with an ack-eliciting packet. The section on persistent congestion isn't very clear about this point. This is because a non-ack-eliciting packet won't be followed up with any probes. It is therefore possible to send one packet and then not send anything else for an extended period. After this, the loss of just the next packet will cause persistent congestion. Note that persistent congestion can be caused by the loss of just two packets after multiple PTOs have occurred, but the common case is that you have at least three packet, or four if you send two packets on PTO. -- 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/3941
- [quicwg/base-drafts] Starting persistent congesti… Martin Thomson
- Re: [quicwg/base-drafts] Starting persistent cong… Marten Seemann
- Re: [quicwg/base-drafts] Starting persistent cong… Kazuho Oku
- Re: [quicwg/base-drafts] Starting persistent cong… Martin Thomson
- Re: [quicwg/base-drafts] Starting persistent cong… Jana Iyengar
- Re: [quicwg/base-drafts] Starting persistent cong… Jana Iyengar