Re: [quicwg/base-drafts] Moving text on spinbit into transport (#2364)

Marcus Ihlar <> Thu, 24 January 2019 10:01 UTC

Return-Path: <>
Received: from localhost (localhost []) by (Postfix) with ESMTP id B4A4D1310F3 for <>; Thu, 24 Jan 2019 02:01:11 -0800 (PST)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: -7.553
X-Spam-Status: No, score=-7.553 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_MESSAGE=0.001, MAILING_LIST_MULTI=-1, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: (amavisd-new); dkim=pass (1024-bit key)
Received: from ([]) by localhost ( []) (amavisd-new, port 10024) with ESMTP id 81ig4WgUbnhf for <>; Thu, 24 Jan 2019 02:01:09 -0800 (PST)
Received: from ( []) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by (Postfix) with ESMTPS id 0FD8E1310F1 for <>; Thu, 24 Jan 2019 02:00:55 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed/relaxed;; h=from:reply-to:to:cc:in-reply-to:references:subject:mime-version:content-type:content-transfer-encoding:list-id:list-archive:list-post:list-unsubscribe; s=s20150108; bh=mSRR3p+sF5wutzPD+0XdiDGg+lM=; b=e6SfmTEuI6sMFnnT 8dEXca/dNHgb+7Kky/yy1TpsvmfMNFisbwejTcLeon80JIf2ikEsEcEoRMYrwXjM WiK0gMUsyxu+h25kkHEJOIoZPqLJdWXWR5j4NxYWh5JFABpZWxr6y8A6tY5gZk9r zc3u9rEJsGpQdV7htnAyhVfJcUA=
Received: by with SMTP id filter0586p1iad2-18785-5C498CD6-17 2019-01-24 10:00:54.533207869 +0000 UTC m=+27647.903895803
Received: from (unknown []) by (SG) with ESMTP id KsRK0ksfTSqi4D2j5AseAg for <>; Thu, 24 Jan 2019 10:00:54.640 +0000 (UTC)
Received: from (localhost []) by (Postfix) with ESMTP id 5F8B9400012 for <>; Thu, 24 Jan 2019 02:00:54 -0800 (PST)
Date: Thu, 24 Jan 2019 10:00:54 +0000
From: Marcus Ihlar <>
Reply-To: quicwg/base-drafts <>
To: quicwg/base-drafts <>
Cc: Subscribed <>
Message-ID: <quicwg/base-drafts/pull/2364/review/>
In-Reply-To: <quicwg/base-drafts/pull/>
References: <quicwg/base-drafts/pull/>
Subject: Re: [quicwg/base-drafts] Moving text on spinbit into transport (#2364)
Mime-Version: 1.0
Content-Type: multipart/alternative; boundary="--==_mimepart_5c498cd65d5be_43e83fac796d45c490478e"; charset="UTF-8"
Content-Transfer-Encoding: 7bit
Precedence: list
X-GitHub-Sender: ihlar
X-GitHub-Recipient: quic-issues
X-GitHub-Reason: subscribed
X-Auto-Response-Suppress: All
X-SG-EID: l64QuQ2uJCcEyUykJbxN122A6QRmEpucztpreh3Pak1fIl1P9cne6D5w6Dw+1dpdFA/E1fruhac56S LA2Wc/KLACDFpXbKmY0Vz9VJJx7+4FanjmgW9g2NxCoq3Dot0XzucxJv7T6SfWedFB9nTQ5M++kUKd SxkbM+zHPaOGANUeXaLG+IkSbC+RRWErKs6OkrQvtQhCZPhfiDodD72vTj2vA/qtHbB7WAr3B9VQUZ Q=
Archived-At: <>
X-Mailman-Version: 2.1.29
List-Id: Notification list for GitHub issues related to the QUIC WG <>
List-Unsubscribe: <>, <>
List-Archive: <>
List-Post: <>
List-Help: <>
List-Subscribe: <>, <>
X-List-Received-Date: Thu, 24 Jan 2019 10:01:12 -0000

ihlar commented on this pull request.

> +will appear after version negotiation and connection establishment are
+completed. On-path measurement and use of the Latency Spin Bit is further
+discussed in {{QUIC-MANAGEABILITY}}.
+The spin bit utilizes a single bit in the first byte of the short header. The
+location of the bit and procedures for how to set it by clients and servers are
+defined in {{short-header}}.
+Implementations MAY select to not implement the full spin bit functionality. In
+that case they are only REQUIRED to implement what is defined for the spin bit
+when it is disabled.
+Each endpoint unilaterally decides if the spin bit is enabled or disabled for a
+connection. Implementations SHOULD 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 SHOULD disable

>           Also, we need to start an issue on this rather than commenting on the PR
@larseggert I'm not sure what the issue is? 
The consensus in BKK was that the bit should be included in the standard, this PR only contains the information necessary for implementors, no text on how to interpret or process the bit on path. Simply referencing a non-milestone potentially experimental document seems a bit odd.

You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub: