[quicwg/base-drafts] kGranularity and max_ack_delay possibly should be added after exponential backoff (#2393)
ianswett <notifications@github.com> Wed, 30 January 2019 22:15 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 77F82130FFE for <quic-issues@ietfa.amsl.com>; Wed, 30 Jan 2019 14:15:01 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.149
X-Spam-Level:
X-Spam-Status: No, score=-6.149 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIMWL_WL_HIGH=-4.553, 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_NONE=-0.0001, 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 ylrNj5cPEYpR for <quic-issues@ietfa.amsl.com>; Wed, 30 Jan 2019 14:14:59 -0800 (PST)
Received: from o5.sgmail.github.com (o5.sgmail.github.com [192.254.113.10]) (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 3DF8A130EB2 for <quic-issues@ietf.org>; Wed, 30 Jan 2019 14:14:59 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed/relaxed; d=github.com; h=from:reply-to:to:cc:subject:mime-version:content-type:content-transfer-encoding:list-id:list-archive:list-post:list-unsubscribe; s=s20150108; bh=+MQbhs4Ed+tHaO9ap3DVKh+RtS4=; b=XPl2NwbZP6cpQDy0 GULggBUfRXD4X3SyIKwlobEjUt5vfvjECysCLMKTHz6oNXx7/c5fMOHhjfRGRnmV 9ifKYKjTowVoAsWEJOmEtc7q+cljYIB16/QBEl179a7vQ0zYFe9aSYn+Dw9/xTEN JMY5g0JxMVTqyIVRGME0Hw8BYhs=
Received: by filter1608p1mdw1.sendgrid.net with SMTP id filter1608p1mdw1-4059-5C5221E1-16 2019-01-30 22:14:57.854129133 +0000 UTC m=+171928.005338844
Received: from github-lowworker-baaab27.cp1-iad.github.net (unknown [192.30.252.33]) by ismtpd0005p1iad2.sendgrid.net (SG) with ESMTP id lWA1BvmvQi-IW68b8XuLsA for <quic-issues@ietf.org>; Wed, 30 Jan 2019 22:14:57.816 +0000 (UTC)
Received: from github.com (localhost [127.0.0.1]) by github-lowworker-baaab27.cp1-iad.github.net (Postfix) with ESMTP id C28C280375 for <quic-issues@ietf.org>; Wed, 30 Jan 2019 14:14:57 -0800 (PST)
Date: Wed, 30 Jan 2019 22:14:58 +0000
From: ianswett <notifications@github.com>
Reply-To: quicwg/base-drafts <reply+0166e4ab61c48880ab0760db4d43211aee139e3ae171c1d492cf000000011869e3e192a169ce1823a471@reply.github.com>
To: quicwg/base-drafts <base-drafts@noreply.github.com>
Cc: Subscribed <subscribed@noreply.github.com>
Message-ID: <quicwg/base-drafts/issues/2393@github.com>
Subject: [quicwg/base-drafts] kGranularity and max_ack_delay possibly should be added after exponential backoff (#2393)
Mime-Version: 1.0
Content-Type: multipart/alternative; boundary="--==_mimepart_5c5221e1c03d9_32ce3fc2a06d45b438252c"; 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: l64QuQ2uJCcEyUykJbxN122A6QRmEpucztpreh3Pak2R0veyE6YZYTjXWQl6Nl+MTyKAxQU/OypDhw /MSBc73q1BqR+dOv5F9Pdx8NScO48jSekPnKL8snf4ReQjakfx4jXwDcpfwzbE5mIIaIs+fjLxFNbw mxKKHxsYqlZLjLEoCEUP4BzqpSr51Rmtrhhjg0fsKvlF0Um39aODOjqJGA==
Archived-At: <https://mailarchive.ietf.org/arch/msg/quic-issues/g5hkurrgHkFQdw05Mv7npjVB9as>
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: Wed, 30 Jan 2019 22:15:05 -0000
Right now, exponential backoff occurs last. But it's reasonable to consider adding/maxing them at the end after exponential backoff. On the one hand, the current pseudocode provides true exponential backoff. On the other hand, it might be overly conservative in some cases. This only applies on subsequent PTOs, so maybe this is an academic question. I'm opening this in the interest in discussing design issues on issues and not on PRs, but I'm also fine with it being closed as not being important and/or needing more information. This came up in #2365 -- 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/2393
- [quicwg/base-drafts] kGranularity and max_ack_del… ianswett
- Re: [quicwg/base-drafts] kGranularity and max_ack… Nick Banks
- Re: [quicwg/base-drafts] kGranularity and max_ack… ianswett
- Re: [quicwg/base-drafts] kGranularity and max_ack… Praveen Balasubramanian
- Re: [quicwg/base-drafts] kGranularity and max_ack… ianswett
- Re: [quicwg/base-drafts] kGranularity and max_ack… ianswett