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

[Marcus Ihlar <[e-mail]>]

ihlar commented on this pull request.



> +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
+the spin bit on a randomly chosen fraction of connections. However, connections
+may be configured to explicitly enable spinning, for example in the case of

Not sure why this would be a SHOULD, here we describe a case where a single connection has been explicitly configured to spin (e.g some debug or tracing mode enabled). In that case, spinning shouldn't be disabled for that specific connection as a result of the random selection process.

-- 
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/2364#discussion_r250691345