Re: [quicwg/base-drafts] kDefaultInitialRtt too large (#752)
janaiyengar <notifications@github.com> Fri, 08 September 2017 19:27 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 2BAC4132199 for <quic-issues@ietfa.amsl.com>; Fri, 8 Sep 2017 12:27:40 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -7.02
X-Spam-Level:
X-Spam-Status: No, score=-7.02 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_HI=-5, RCVD_IN_MSPIKE_H4=-0.01, RCVD_IN_MSPIKE_WL=-0.01, 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 hmty1IsolBIE for <quic-issues@ietfa.amsl.com>; Fri, 8 Sep 2017 12:27:38 -0700 (PDT)
Received: from github-smtp2a-ext-cp1-prd.iad.github.net (github-smtp2-ext8.iad.github.net [192.30.252.199]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 8CC011320C9 for <quic-issues@ietf.org>; Fri, 8 Sep 2017 12:27:38 -0700 (PDT)
Date: Fri, 08 Sep 2017 12:27:35 -0700
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1504898855; bh=G6kOrZcG1/0GxSYIPPCJkK0fQpegrQi1w8SMOmjca20=; h=From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=MJoX8calDOkDOB5MSRvLyRwhj+Oipu0uV5OC2v7sd79h+17lgtme4RPJapxiAOdbx qpj/OqwscNc8HSzirNqrd6O6FK4qsJZvJS826HOPQT7azsmZD+m6RqRwP1ahwfSKmR dmFODwZe4d3kMSbVFFI3ejmTTIOBCrg/sIEn2JOs=
From: janaiyengar <notifications@github.com>
Reply-To: quicwg/base-drafts <reply+0166e4abc2c7519de8871d08c59eb682de8a9b3b4736510b92cf0000000115cab12792a169ce0f1cc61a@reply.github.com>
To: quicwg/base-drafts <base-drafts@noreply.github.com>
Cc: Subscribed <subscribed@noreply.github.com>
Message-ID: <quicwg/base-drafts/issues/752/328193197@github.com>
In-Reply-To: <quicwg/base-drafts/issues/752@github.com>
References: <quicwg/base-drafts/issues/752@github.com>
Subject: Re: [quicwg/base-drafts] kDefaultInitialRtt too large (#752)
Mime-Version: 1.0
Content-Type: multipart/alternative; boundary="--==_mimepart_59b2ef275ceb1_578e3ff036623c3c449d"; 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/c_gzbk4J9JqFrfcSttEk2zPAPSc>
X-BeenThere: quic-issues@ietf.org
X-Mailman-Version: 2.1.22
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: Fri, 08 Sep 2017 19:27:40 -0000
Finally getting to this. Note that the initial RTT only matters insofar as retransmissions are concerned. The handshake RTO is 2 x initialRTT, which means retransmissions should happen after 200ms, which is good enough for 90% of the cases. Separately, on constants: the IETF has always been reluctant to change TCP's constants despite the fact that implementations have changed them a long time ago. Consider the min RTO, which is still recommended by RFC 6298 to be 1 second, is not used in practice. The minimum RTO in Linux is ~200 ms. I agree with @mcmanus: I would put latency over bandwidth, or at least provide a knob to allow QUIC implementations to put latency over bandwidth. In this case, I would argue that a few extra retransmissions are really not a major cost, but waiting for a long time when you have just one packet outstanding in the network is a massive cost that browsers and server have repeatedly shown to be worth reducing. It's all about latency. IMO a few extra retransmissions don't matter. -- 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/752#issuecomment-328193197
- Re: [quicwg/base-drafts] kDefaultInitialRtt too l… Christian Huitema
- [quicwg/base-drafts] kDefaultInitialRtt too large… Lars Eggert
- Re: [quicwg/base-drafts] kDefaultInitialRtt too l… Martin Thomson
- Re: [quicwg/base-drafts] kDefaultInitialRtt too l… Lars Eggert
- Re: [quicwg/base-drafts] kDefaultInitialRtt too l… Martin Thomson
- Re: [quicwg/base-drafts] kDefaultInitialRtt too l… Lars Eggert
- Re: [quicwg/base-drafts] kDefaultInitialRtt too l… Patrick McManus
- Re: [quicwg/base-drafts] kDefaultInitialRtt too l… Lars Eggert
- Re: [quicwg/base-drafts] kDefaultInitialRtt too l… Lars Eggert
- Re: [quicwg/base-drafts] kDefaultInitialRtt too l… Ryan Hamilton
- Re: [quicwg/base-drafts] kDefaultInitialRtt too l… Christian Huitema
- Re: [quicwg/base-drafts] kDefaultInitialRtt too l… Christian Huitema
- Re: [quicwg/base-drafts] kDefaultInitialRtt too l… janaiyengar
- Re: [quicwg/base-drafts] kDefaultInitialRtt too l… ianswett
- Re: [quicwg/base-drafts] kDefaultInitialRtt too l… Lars Eggert
- Re: [quicwg/base-drafts] kDefaultInitialRtt too l… Lars Eggert