On 2020-02-18 7:07 p.m., Ross Tajvar wrote:
Are you suggesting that ATT block all QUIC across their network? Blocking a (for you) undesirable option when an established fallback exists is a much better end user experience than introducing breakage into that option
When you throttle or subtly break things you get: On 2020-02-18 7:12 p.m., Daniel Sterling wrote:
One might argue they already *are* doing so; QUIC is essentially unusable on my AT&T ipv4 residential connection (and a web search suggests I'm not alone).
Or: I no longer use my ISP's IPv6 access (via 6rd) since it would cause terrible slowdowns due to packet loss when it broke Or: some AT&T customers cannot connect to our customers due to IPv6 HTTPS interception: https://meta.discourse.org/t/-/140769/3 Or (probably the same problem): https://tutanota.com/blog/posts/att-blocks-tutanota/ With blocking in these cases, QUIC falls back to TCP, Happy Eyeballs falls back to IPv4, everybody's happy.