Re: [quicwg/base-drafts] kInitialRtt of 100 msec is too aggressive (#2184)

Martin Thomson <notifications@github.com> Mon, 17 December 2018 06:46 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 32C4B128CE4 for <quic-issues@ietfa.amsl.com>; Sun, 16 Dec 2018 22:46:28 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -9.459
X-Spam-Level:
X-Spam-Status: No, score=-9.459 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIMWL_WL_HIGH=-1.46, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_IMAGE_ONLY_32=0.001, 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 78FavO3-4XIP for <quic-issues@ietfa.amsl.com>; Sun, 16 Dec 2018 22:46:26 -0800 (PST)
Received: from out-6.smtp.github.com (out-6.smtp.github.com [192.30.252.197]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 593901294D7 for <quic-issues@ietf.org>; Sun, 16 Dec 2018 22:46:26 -0800 (PST)
Date: Sun, 16 Dec 2018 22:46:25 -0800
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1545029185; bh=DTiywIyi4TnI2jpAdktor8DBx9A4fEiWS6bkr8pvPhc=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=vNhRcKkIZ4YG/TXqKj6Jw/eNR20jwHQRRu6LHRv+5BCwaU7UE8MH9GNuWaLF/nD48 nIsY8hlwmihDXsXYyO0SdEFU0Rw+1Dhbs+FvbO19bvNMeFd5uQQW+on21UroTcLOOl VVSCByznwGbEdQEVbCMuhHgSbvrujdWZqrjJ8L94=
From: Martin Thomson <notifications@github.com>
Reply-To: quicwg/base-drafts <reply+0166e4abd8ccf8130d1061d4ebac0c50fb82d8b48c72e59492cf00000001182f084192a169ce174df843@reply.github.com>
To: quicwg/base-drafts <base-drafts@noreply.github.com>
Cc: Subscribed <subscribed@noreply.github.com>
Message-ID: <quicwg/base-drafts/issues/2184/447739531@github.com>
In-Reply-To: <quicwg/base-drafts/issues/2184@github.com>
References: <quicwg/base-drafts/issues/2184@github.com>
Subject: Re: [quicwg/base-drafts] kInitialRtt of 100 msec is too aggressive (#2184)
Mime-Version: 1.0
Content-Type: multipart/alternative; boundary="--==_mimepart_5c174641f776_692a3ffa6f4d45b4322772"; 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/QA0B9tZ5JiaxjUredp46BioefCw>
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, 17 Dec 2018 06:46:28 -0000

Do we have a maximum?  I didn't think that was the subject of the discussion.  Timeouts always need to look at the tail.  Though having more packets in the pipe might allow that tail to be brought in a little more than otherwise.

As for remembering RTTs being the solution here, strengthening our reliance on mechanisms that reinforce incumbancy is the best outcome.  I certainly expect people to do that, but if that means that a site is only "fast" on return visits, that's going to disadvantage new players more.

-- 
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/2184#issuecomment-447739531