Re: [quicwg/base-drafts] Guidance on path retransmission timer (#2130)
janaiyengar <notifications@github.com> Thu, 13 December 2018 01:29 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 A096912D4E6 for <quic-issues@ietfa.amsl.com>; Wed, 12 Dec 2018 17:29:03 -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 PSnvRQ3GqIh5 for <quic-issues@ietfa.amsl.com>; Wed, 12 Dec 2018 17:29:02 -0800 (PST)
Received: from out-2.smtp.github.com (out-2.smtp.github.com [192.30.252.193]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id E1EB0128B14 for <quic-issues@ietf.org>; Wed, 12 Dec 2018 17:29:01 -0800 (PST)
Date: Wed, 12 Dec 2018 17:29:00 -0800
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1544664540; bh=6Q/8W9SQzpU5ZYLEdY6yufVJKDYv88WjlEhFg8xRHVg=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=TWSBcbA+D7/xsMx1llCBjC/7522kyBKkqwYV3557gQhY2gp6vt1vOPlFt1xaRjvyC mgV/lZr+o9vbVLYrv3d/0Rw70Xj7qzTWTphKPGXotyxbNwh9gE/LP6W/yzgPFFYEbA WRqA7qE9x7fw1GtFMZEgMJzek/Zn0VErDMAcvjQM=
From: janaiyengar <notifications@github.com>
Reply-To: quicwg/base-drafts <reply+0166e4ab911e9bc6d42601cff49bac874a71f439c696e8e192cf00000001182977dc92a169ce1743bbcf@reply.github.com>
To: quicwg/base-drafts <base-drafts@noreply.github.com>
Cc: Subscribed <subscribed@noreply.github.com>
Message-ID: <quicwg/base-drafts/issues/2130/446808444@github.com>
In-Reply-To: <quicwg/base-drafts/issues/2130@github.com>
References: <quicwg/base-drafts/issues/2130@github.com>
Subject: Re: [quicwg/base-drafts] Guidance on path retransmission timer (#2130)
Mime-Version: 1.0
Content-Type: multipart/alternative; boundary="--==_mimepart_5c11b5dc6905a_36b3fde8aad45b48413e"; 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/elkC-yUGJEzZcTAlndUzB823mOs>
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: Thu, 13 Dec 2018 01:29:03 -0000
The recommendation is 3 RTO, and the RTO computation includes a rule for initial values when no RTT measurement has happened. Did you mean a different recommendation? FWIW, initial retransmit can be a bit aggressive, for latency reasons, and I don't think path validation needs to be aggressive. That said, it has always bothered me that we say 3RTO when we know that this is a different path, and the RTO measurement from other paths are unlikely to hold true. I'm fine with stipulating a constant here. I propose 3 x Initial RTOs = 600ms. -- 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/2130#issuecomment-446808444
- [quicwg/base-drafts] Guidance on path retransmiss… ekr
- Re: [quicwg/base-drafts] Guidance on path retrans… janaiyengar
- Re: [quicwg/base-drafts] Guidance on path retrans… janaiyengar
- Re: [quicwg/base-drafts] Guidance on path retrans… Martin Thomson
- Re: [quicwg/base-drafts] Guidance on path retrans… ekr
- Re: [quicwg/base-drafts] Guidance on path retrans… Martin Thomson
- Re: [quicwg/base-drafts] Guidance on path retrans… Jana Iyengar
- Re: [quicwg/base-drafts] Guidance on path retrans… Jana Iyengar