Re: [quicwg/base-drafts] Spin per peer (#1982)

[Christian Huitema <[e-mail]>]

huitema commented on this pull request.



> @@ -235,11 +235,19 @@ 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 the spin bit on a randomly chosen
-fraction of connections.  The selection process should be designed such that
-on average the spin bit is disabled for at least 1/8th of the connections.
-
-When the spin bit is disabled, endpoints SHOULD set the spin bit value to zero,
-regardless of the values received from their peer. Addendums or revisions to
+fraction of connections.
+
+The selection process SHOULD be designed such that
+on average the spin bit is disabled for at least one eighth of network paths.
+The random choice SHOULD be dependent
+on the source and destination addresses of the path,
+so that the spin bit is consistently enabled or
+disabled for repeated use of the same path.

My preference would be to make a policy decision to spin or not at the connection level, that is flip the coin based on the initial pair of addresses. But then, we also need a paragraph stating that the initial value of the spin bit is randomly computed for each path in a connection. If the policy decides to spin, this value will spin. If not, it will stay constant, to zero or one. 

-- 
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/1982#discussion_r236050063