IETF Logo Mail Archive

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

ianswett <notifications@github.com> Tue, 26 March 2019 11:03 UTC

Return-Path: <bounces+848413-a050-quic-issues=ietf.org@sgmail.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 390271202BD for <quic-issues@ietfa.amsl.com>; Tue, 26 Mar 2019 04:03:31 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.383
X-Spam-Level:
X-Spam-Status: No, score=-1.383 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, HTML_IMAGE_ONLY_24=1.618, HTML_MESSAGE=0.001, MAILING_LIST_MULTI=-1, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001] autolearn=no 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 5IEalK61zha3 for <quic-issues@ietfa.amsl.com>; Tue, 26 Mar 2019 04:03:29 -0700 (PDT)
Received: from o1.sgmail.github.com (o1.sgmail.github.com [192.254.114.176]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 99C521202BC for <quic-issues@ietf.org>; Tue, 26 Mar 2019 04:03:29 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed/relaxed; d=github.com; h=from:reply-to:to:cc:in-reply-to:references:subject:mime-version:content-type:content-transfer-encoding:list-id:list-archive:list-post:list-unsubscribe; s=s20150108; bh=+Ocgf897hVimtcXqHZcp8jLrYpQ=; b=CgkGNoeHPH/oU2aT WmqkZ8Bmy+zZqy5OddTF+ziJsdLw5jlM35mBOZYChTLD/tdti4GiMZvDTubQgo7H KyEtBLfAAAokgjJNnxnueT7B6xDtgcOgcTbhh0gciUYXtXuhAxJ0SUkj+0BiSZ+L Bg0Cs0IVS3YnlJQqceN08ex3giQ=
Received: by filter1556p1mdw1.sendgrid.net with SMTP id filter1556p1mdw1-8563-5C9A0700-1 2019-03-26 11:03:28.043654504 +0000 UTC m=+920758.963273564
Received: from github-lowworker-cb75ac4.cp1-iad.github.net (unknown [192.30.252.40]) by ismtpd0010p1iad1.sendgrid.net (SG) with ESMTP id 4vetq5_lSFCNNGUcLMW27g for <quic-issues@ietf.org>; Tue, 26 Mar 2019 11:03:27.990 +0000 (UTC)
Received: from github.com (localhost [127.0.0.1]) by github-lowworker-cb75ac4.cp1-iad.github.net (Postfix) with ESMTP id EBD3DC21129 for <quic-issues@ietf.org>; Tue, 26 Mar 2019 04:03:27 -0700 (PDT)
Date: Tue, 26 Mar 2019 11:03:28 +0000
From: ianswett <notifications@github.com>
Reply-To: quicwg/base-drafts <reply+0166e4abd791345c3edce76cd3ef362cb4326ffe46d31c5992cf0000000118b1c8ff92a169ce174df843@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/476577452@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_5c9a06ffe98d4_5ab03fe2c56d45c41681e6"; 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
X-SG-EID: l64QuQ2uJCcEyUykJbxN122A6QRmEpucztpreh3Pak22bTTnuUCkv6UnVIiPCxx/iJLja0Jm6Rsx6W Y7SgIQZ0ZVr2jSWVBcLKpf3Fz6/SiH2yuDXMHhwbTQJprPcw/zwuVV+2WMNEe4YRd50uZUrX7waTMR wbgZtfep9SK5hb5qRk2FIdAo0ENVUQfvmrSicJZ45ewSFrz/yp76w/7sYA==
Archived-At: <https://mailarchive.ietf.org/arch/msg/quic-issues/pDDOZNfULlDSbUHCKDgN5P-yZlM>
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: Tue, 26 Mar 2019 11:03:31 -0000

The discussion in Prague concluded that we should recommend 1 second to align with RFC6298 and clarify when previous RTT estimates should be expired(ie: upon network change) and when the persisted RTT associated with 0-RTT credentials should no longer be used(ie: upon network change).

-- 
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-476577452

v2.23.0 | Report a Bug | By Email