Re: [quicwg/base-drafts] Use a higher seed RTT for new paths (#2789)

ianswett <notifications@github.com> Fri, 19 July 2019 11:12 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 349DB120154 for <quic-issues@ietfa.amsl.com>; Fri, 19 Jul 2019 04:12:02 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.596
X-Spam-Level:
X-Spam-Status: No, score=-6.596 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_28=1.404, HTML_MESSAGE=0.001, MAILING_LIST_MULTI=-1, RCVD_IN_DNSWL_HI=-5, 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 NnPSKp5AIrvk for <quic-issues@ietfa.amsl.com>; Fri, 19 Jul 2019 04:11:59 -0700 (PDT)
Received: from out-23.smtp.github.com (out-23.smtp.github.com [192.30.252.206]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 90C2212001E for <quic-issues@ietf.org>; Fri, 19 Jul 2019 04:11:59 -0700 (PDT)
Date: Fri, 19 Jul 2019 04:11:58 -0700
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1563534718; bh=UyIlRLnjzShcP+2gvaFn7+hqbssV3ZH5gffkKLKD0/k=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=XEJODw4bqSSKWnu9hiMi6cuLBN9T7+P4I6kKr56Xi7mk520aESJaAGr9iLwOqL/Rs 9dto+g6m98pCiIhyOSbfWFdZl1/dd3qyacmGLhRiShBk2UebWGbPy0RwFHTz9B3jhk ji48HarxOS9ilrD502IrwSTN1/Vm1S6I9NCjn2XQ=
From: ianswett <notifications@github.com>
Reply-To: quicwg/base-drafts <reply+AFTOJKYWPR44QGM7UOOLRCV3H3L75EVBNHHBWLLVNI@reply.github.com>
To: quicwg/base-drafts <base-drafts@noreply.github.com>
Cc: Subscribed <subscribed@noreply.github.com>
Message-ID: <quicwg/base-drafts/issues/2789/513190762@github.com>
In-Reply-To: <quicwg/base-drafts/issues/2789@github.com>
References: <quicwg/base-drafts/issues/2789@github.com>
Subject: Re: [quicwg/base-drafts] Use a higher seed RTT for new paths (#2789)
Mime-Version: 1.0
Content-Type: multipart/alternative; boundary="--==_mimepart_5d31a57e98847_26713fa3f02cd96c20826c"; 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/FKfufzjwXbcLBs2y7upNpzt1mSg>
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: Fri, 19 Jul 2019 11:12:02 -0000

I believe the relevant text is(?):
" (5.7) If the timer expires awaiting the ACK of a SYN segment and the
         TCP implementation is using an RTO less than 3 seconds, the RTO
         MUST be re-initialized to 3 seconds when data transmission
         begins (i.e., after the three-way handshake completes)."

I believe that's saying the RTO should be set to 3 seconds if any syn timers expired?  Do implementations(ie: Linux, Windows, etc) do that?  If so, that means a single packet loss in the handshake causes the RTO to increase to 3 seconds, but a subsequent data packet loss would not have that effect?

@gorryfair  If you're in Montreal Saturday or Sunday at the Hackathon, maybe we can talk about this more and figure out what to do here?

-- 
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/2789#issuecomment-513190762