Re: [quicwg/base-drafts] Limit sending while in RTO (#2162)
ianswett <notifications@github.com> Mon, 24 December 2018 18:25 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 3ED22131045 for <quic-issues@ietfa.amsl.com>; Mon, 24 Dec 2018 10:25:06 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.661
X-Spam-Level:
X-Spam-Status: No, score=-6.661 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIMWL_WL_HIGH=-0.065, 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: 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 lupyX_qhjZSz for <quic-issues@ietfa.amsl.com>; Mon, 24 Dec 2018 10:25:04 -0800 (PST)
Received: from out-5.smtp.github.com (out-5.smtp.github.com [192.30.252.196]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 899DA13103C for <quic-issues@ietf.org>; Mon, 24 Dec 2018 10:25:04 -0800 (PST)
Date: Mon, 24 Dec 2018 10:25:03 -0800
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1545675903; bh=MPHBQSam047SR0p1SFAeG/cOvAs7UoeiZROMtbWLV00=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=EWaN2RbjJefVCGB7rpbOIak52C8c5jGBtUHtYYQ3bMUXQPOYrcE9GuvJG3PAoBCtW IcDJ0c27XRi9vluIawgCtMrMFYNFUSzgrfJCBJ+Vm99M8FXuTLJjWnY4WFvBUuPH6L zw8bqo6KpRnxysA5V5EPkz8g+1FwqncyGAjyElpk=
From: ianswett <notifications@github.com>
Reply-To: quicwg/base-drafts <reply+0166e4ab1e5f11d7cefd68848417b671c8e6facbb858d4e792cf000000011838e67f92a169ce174c44df@reply.github.com>
To: quicwg/base-drafts <base-drafts@noreply.github.com>
Cc: Subscribed <subscribed@noreply.github.com>
Message-ID: <quicwg/base-drafts/issues/2162/449761566@github.com>
In-Reply-To: <quicwg/base-drafts/issues/2162@github.com>
References: <quicwg/base-drafts/issues/2162@github.com>
Subject: Re: [quicwg/base-drafts] Limit sending while in RTO (#2162)
Mime-Version: 1.0
Content-Type: multipart/alternative; boundary="--==_mimepart_5c21247fae4a8_f933fca0fed45b83562f6"; 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/6npUBS3I89jIpw6VJOeKF2jme8U>
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: Mon, 24 Dec 2018 18:25:06 -0000
Personally, I haven't seen many cases in traces where this is a problem, so I'd be inclined to leave the text as is. One could validly use this CWND to be more aggressive about PTO, as you've previously suggested to me, and I wouldn't want to prevent that use case. We could add text that allows more aggressive PTOs than described when CWND is available, but prevent using this CWND after the first full PTO is sent? -- 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/2162#issuecomment-449761566
- [quicwg/base-drafts] Limit sending while in RTO (… janaiyengar
- Re: [quicwg/base-drafts] Limit sending while in R… ianswett
- Re: [quicwg/base-drafts] Limit sending while in R… janaiyengar
- Re: [quicwg/base-drafts] Limit sending while in R… ianswett
- Re: [quicwg/base-drafts] Limit sending while in R… ianswett