Re: [quicwg/base-drafts] Updated spinbit text (#2564)

mirjak <notifications@github.com> Tue, 02 April 2019 12: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 5759F1201AE for <quic-issues@ietfa.amsl.com>; Tue, 2 Apr 2019 05:12:23 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -8.001
X-Spam-Level:
X-Spam-Status: No, score=-8.001 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_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 Yusq3IL5hbqO for <quic-issues@ietfa.amsl.com>; Tue, 2 Apr 2019 05:12:21 -0700 (PDT)
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 663E912015D for <quic-issues@ietf.org>; Tue, 2 Apr 2019 05:12:21 -0700 (PDT)
Date: Tue, 02 Apr 2019 05:12:19 -0700
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1554207139; bh=eV9Uc/hrEfQlAVf122Bkfah9G/2WoLVwHeVbyq1RiVI=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=qMEsqyC+MBtJldLfhvoSRbbOtCogv5RVm8aQZDHKUoR1d+FJfPGHM8594l9msffd/ PSeSsplaFOk05vQaoigcrLx1DnOvd3a3iRwaUIksvegHSvXzpwMzLUkERWg64nubJH JAzMrh5e6mcxMWVtB+jgXgwEyQUw5jgs7MoxRB70=
From: mirjak <notifications@github.com>
Reply-To: quicwg/base-drafts <reply+0166e4ab8977f20cdaaf77335b595de7ecd2062d729efab892cf0000000118bb13a392a169ce196a996c@reply.github.com>
To: quicwg/base-drafts <base-drafts@noreply.github.com>
Cc: Subscribed <subscribed@noreply.github.com>
Message-ID: <quicwg/base-drafts/pull/2564/review/221617043@github.com>
In-Reply-To: <quicwg/base-drafts/pull/2564@github.com>
References: <quicwg/base-drafts/pull/2564@github.com>
Subject: Re: [quicwg/base-drafts] Updated spinbit text (#2564)
Mime-Version: 1.0
Content-Type: multipart/alternative; boundary="--==_mimepart_5ca351a33dfe8_370b3fc6040d45bc129144"; charset="UTF-8"
Content-Transfer-Encoding: 7bit
Precedence: list
X-GitHub-Sender: mirjak
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/qFU7wOdUJESIroQ-1Cff-n3qaxk>
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, 02 Apr 2019 12:12:23 -0000

mirjak commented on this pull request.



> +the spin bit on a randomly chosen fraction of connections. 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 should be externally
+unpredictable but consistent for any given combination of source and destination
+address and port. The selection process performed at the beginning of the
+connection SHOULD be applied for all paths used by the connection.
+
+In case multiple connections share the same five-tuple, i.e. same source and
+destination IP address and UDP port the setting of the spin bit needs to be
+coordinated across all connections to ensure a clear signal to any on path
+measurement point, however that might not be feasible.
+
+When the spin bit is disabled, endpoints MAY set the spin bit to any value, and
+MUST accept any incoming value. It is RECOMMENDED that they set the spin bit to
+a random value either chosen independently for each packet, or chosen
+independently for each path and kept constant for that path.

Yes, we should allow for this flexibility. In fact there is no way to not allow for it. I'm just saying we should recommend per-connection random values as the preferred way to do it.

-- 
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/2564#discussion_r271269907