Re: [quicwg/base-drafts] Enable/disable/coordinate spin per path (#2751)

ianswett <notifications@github.com> Tue, 28 May 2019 19:39 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 1C26E12026A for <quic-issues@ietfa.amsl.com>; Tue, 28 May 2019 12:39:25 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -8.008
X-Spam-Level:
X-Spam-Status: No, score=-8.008 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, 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_HELO_NONE=0.001, SPF_PASS=-0.001, T_DKIMWL_WL_HIGH=-0.01] 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 h55SkIL3Tzip for <quic-issues@ietfa.amsl.com>; Tue, 28 May 2019 12:39:23 -0700 (PDT)
Received: from out-3.smtp.github.com (out-3.smtp.github.com [192.30.252.194]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 15637120267 for <quic-issues@ietf.org>; Tue, 28 May 2019 12:39:23 -0700 (PDT)
Date: Tue, 28 May 2019 12:39:22 -0700
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1559072362; bh=KaoS1HhbuGecH2AK2FL00yeCiodtXlH9meR1GCZOBMI=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=QsD+vfg/B8DAYOBxAGnhWHaPQbXlA+sj2iX+OiqSHNagf3irtYM3X/IkksEDZK0es X0rbIBCsa3EmHoEAjk6nVZOZDp4SrYQxODOQsrrZGbKL46E0TbQi6Ypw9JpErieA5H /1Yo3PrmvLmzS9I29WxAVtDHba97hj6b6qsNVgog=
From: ianswett <notifications@github.com>
Reply-To: quicwg/base-drafts <reply+AFTOJKY2G6KBDRFPAEEZKKV27LAOVEVBNHHBVJ6MAY@reply.github.com>
To: quicwg/base-drafts <base-drafts@noreply.github.com>
Cc: Subscribed <subscribed@noreply.github.com>
Message-ID: <quicwg/base-drafts/pull/2751/review/242880488@github.com>
In-Reply-To: <quicwg/base-drafts/pull/2751@github.com>
References: <quicwg/base-drafts/pull/2751@github.com>
Subject: Re: [quicwg/base-drafts] Enable/disable/coordinate spin per path (#2751)
Mime-Version: 1.0
Content-Type: multipart/alternative; boundary="--==_mimepart_5ced8e6a1d020_39523f85bbccd96017189d"; 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/BAivnBbvg_dL4iIWCovrTz1OWu4>
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, 28 May 2019 19:39:30 -0000

ianswett commented on this pull request.



> @@ -4019,14 +4019,14 @@ 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 connections. 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, that is, have the same
-source and destination IP address and UDP ports, endpoints should try to
-co-ordinate across all connections to ensure a clear signal to any on-path
-measurement points.
+disabled for at least one eighth of network paths. The selection process

What happens when the client thinks the path hasn't changed but the server has?  An observer could be on either side of the NAT.

-- 
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/2751#pullrequestreview-242880488