Re: [quicwg/base-drafts] Spin bit should be applied per each 5-tuple rather than per connection (#1828)

[Martin Thomson <[e-mail]>]

I don't think that we need fancy here.  Simply state that - ideally - spinning is scoped to a 5-tuple.  You might then observe that if connections share the same path, then they might not be able to coordinate spinning.

Aside from it being logistically difficult to coordinate across connections, coordination isn't possible in all cases. With diverse endpoints, there could be NATs/load-balancers/middleboxes that know how to multiplex and demultiplex based on connection ID at both ends.  That makes @britram's thinking useful (...minimum publishable unit?).  Of course, if spinning could be coordinated, that would make the signal cleaner.

Note that multiple connections on the same path is hard to distinguish from the same connection with alternating connection IDs, unless the end-to-end latency differs.  (Note to self: look into gaming this.)

-- 
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/issues/1828#issuecomment-438058714