Re: [quicwg/base-drafts] Disabling Spin bit for what percentage of connections? (#3270)

Kazuho Oku <notifications@github.com> Mon, 25 November 2019 08:10 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 2305D12081C for <quic-issues@ietfa.amsl.com>; Mon, 25 Nov 2019 00:10:24 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -8
X-Spam-Level:
X-Spam-Status: No, score=-8 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_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 j8mU92XEBVES for <quic-issues@ietfa.amsl.com>; Mon, 25 Nov 2019 00:10:22 -0800 (PST)
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 B03341200B4 for <quic-issues@ietf.org>; Mon, 25 Nov 2019 00:10:22 -0800 (PST)
Date: Mon, 25 Nov 2019 00:10:21 -0800
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1574669421; bh=7TQuiP8+MPFltEHTIaIN+kc22EdXMhVIRvRzrQLs9MU=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=Z4ESw5IhLfgHUkvPr0XkoWAmyDBwUgSHxyguVR6Yh1WuLUykq0/QZZMEtM387MC+z +pyal0rqi4TLtWh34Io8rZX/HjgB4ooPWaqpljy4RRtWEvuTmCMZJ5ApYtRQHLPM1f 3t09nn1FHnrwGgrrz2wjM27IY+sJD1Mr86DMDbb4=
From: Kazuho Oku <notifications@github.com>
Reply-To: quicwg/base-drafts <reply+AFTOJK47QLN26A3PMQK5BON35C7O3EVBNHHB6VIZLI@reply.github.com>
To: quicwg/base-drafts <base-drafts@noreply.github.com>
Cc: Subscribed <subscribed@noreply.github.com>
Message-ID: <quicwg/base-drafts/pull/3270/review/322094846@github.com>
In-Reply-To: <quicwg/base-drafts/pull/3270@github.com>
References: <quicwg/base-drafts/pull/3270@github.com>
Subject: Re: [quicwg/base-drafts] Disabling Spin bit for what percentage of connections? (#3270)
Mime-Version: 1.0
Content-Type: multipart/alternative; boundary="--==_mimepart_5ddb8c6da8244_19223ff961ecd96c9324e7"; charset=UTF-8
Content-Transfer-Encoding: 7bit
Precedence: list
X-GitHub-Sender: kazuho
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/9XWy5xlazZFj5ZbsmVTJTvxroIs>
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: Mon, 25 Nov 2019 08:10:24 -0000

kazuho commented on this pull request.



> @@ -4331,11 +4331,10 @@ Each endpoint unilaterally decides if the spin bit is enabled or disabled for a
 connection. Implementations MUST allow administrators of clients and servers
 to disable the spin bit either globally or on a per-connection basis. Even when
 the spin bit is not disabled by the administrator, implementations MUST disable
-the spin bit for a given connection with a certain likelihood. The random
-selection process SHOULD be designed such that on average the spin bit is
-disabled for at least one eighth of network paths. The selection process
-performed at the beginning of the connection SHOULD be applied for all paths
-used by the connection.
+the spin bit for at least a sixteenth of connections with an expectation that
+the spin bit is disabled for at least one eighth of network paths. The selection

@martinthomson If we are to "ensure" that the spin bit signal would be disabled for approx. 1/8 of network paths, I think we need to require endpoints to select one in every 16 paths *at random*. Otherwise, the paths that would have the spin bit disabled could go below 1/8. For example, when there is only one client and one server talking to each other, and if both of them disable spin bit for every 16th connection they handle, then the spin bit would be enabled for only 1/16 of all the connections.

-- 
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/pull/3270#discussion_r350033868