Re: Spin bit discussion - where we're at

[Roland Zink <[e-mail]>]

I agree it is not only QUIC. I also don't think it is necessary to panic 
now. We have issue #740 
(https://github.com/quicwg/base-drafts/issues/740) about adding a 
security issues section were existing means could be added. When QUIC 
can help to address such issues it can become more reliable so I 
wouldn't say this is out of scope just because other protocols have 
similar issues. If it really turns out that the current mitigations are 
not sufficient then work on better queue management algorithm will 
probably come too late.


Roland



Am 27.11.2017 um 19:02 schrieb Christian Huitema:
> On 11/27/2017 9:36 AM, Roland Zink wrote:
>
>> If QUIC makes the problem crystal clear then now seems to be a good
>> time to solve or mitigate it before risking it becomes a real world
>> problem.
> First, let's start by agreeing that this is not a problem specific QUIC.
> You could say the same about Bit Torrent, any protocol that sends video
> over UDP, or any application that opens multiple TCP connection. So,
> yes, there may well be a problem, but since it is not specific to QUIC
> the mitigation does not have to be specific to QUIC either.
>
> But let's not panic. Practical mitigation has started long ago, with
> ISPs effectively controlling how much data can be sent through a
> customer's up-link. Maybe these current mitigations are not sufficient,
> but if that is the case I would expect more work on better queue
> management algorithm.
>
> -- Christian Huitema
>