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

[mirjak <[e-mail]>]

mirjak commented on this pull request.



> +
+The 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/port. For instance,
+the implementation might have a static key which it uses to key a pseudorandom
+function over these values and use the output to determine whether to
+send the spin bit. The selection process performed at the beginning
+of the connection SHOULD be applied for all paths used by the connection.
+
+Note that where multiple connections use the same path,
+the use of the spin bit MAY be coordinated by endpoints,
+recognizing that this might not be possible in many cases.
+
+When the spin bit is disabled, endpoints MAY set the spin bit to any value,
+and MUST accept any incoming value.
 

Given that setting it random per packet or to a fixed value per path is both seen as acceptable and save, I strongly prefer to recommend the later. I dont' think that is it true that random values can be easily distringuished from valid signals because exactly those patterns in a valid signal where things look strange are often the interesting ones to detect problems, e.g. large amounts of re-odering. If you filter out random spinning connections and may also filter out exactly those cases you are most interesting of. 

-- 
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_r237022117