News for hackers. Stuff that matters.
Re:Google’s QUIC protocol: moving the web from TCP to UDP by drdaeman on Monday August 01, 2016 @09:11AM (#12202069)
The problem is, we've basically lost L4. Too many networks (firewalls, and especially NATs) just don't pass anything but protocols 6 (TCP) and 17 (UDP). Even ICMP is not always reliably available (leading to all sort of weird PMTU issues[1]), or heavily filtered.

I think that's why many good protocols (e.g. SCTP) are rare sights and frequently aren't even considered as an option.

[1] Yes, some idiots just block ICMP completely because they heard it's "secure" and make DHCP or PPP cap MTU at 1200 with "uh, it works just fine" attitude.

Re:Google’s QUIC protocol: moving the web from TCP to UDP by panic on Monday August 01, 2016 @09:51AM (#12202337)
It's too late for IPv4, but maybe a strong push could get a protocol like SCTP supported on IPv6 networks?
Re:Google’s QUIC protocol: moving the web from TCP to UDP by drdaeman on Monday August 01, 2016 @10:47AM (#12202757)
Given that IPv6 doesn't normally use NAT (and for IPv4, it's NAT, not firewalls, is the primary source of problems why non-TCP/UDP protocols don't work in practice) it's a possibility that it would be okay.

IPv6 adoption is a problem, though. I think despite all IANA efforts to push v6, we'll be stuck with IPv4 for long years.

Re:Google’s QUIC protocol: moving the web from TCP to UDP by wtbob on Monday August 01, 2016 @10:10AM (#12202469)
IIRC IPv6 requires ICMPv6 to work. I'd be in favour of SCTP support as well; dunno how it compares to QUIC for mobile devices though.