QUIC! IETF sets November deadline for last comments on TCP-killer spawned by Google and Cloudflare
(2020/10/26)
- Reference: 1603697411
- News link: https://www.theregister.co.uk/2020/10/26/quic_last_call_ietf/
- Source link:
The Internet Engineering Task Force has set November 16th, 2020, as the final date for comment on Quick UDP Internet Connections, the would-be TCP-killer that Google and Cloudflare have offered up as part of HTTP/3.
QUIC’s backers point out that TCP is chatty and therefore imposes long round-trip times on traffic. Which is never welcome, but especially undesirable on wireless networks.
By using a flavor of TLS (Transport Layer Security) over the internet's UDP protocol instead of the customary TCP, QUIC can bust some bottlenecks that can happen when a TCP connection loses packets. QUIC therefore makes it possible for a client and server that have never connected to send data without any round trips between the devices.
The result is faster-loading web pages – which explains why Google backed QUIC – and more elegant internetworking – which explains why Cloudflare likes it.
Speaking of Cloudflare, one of its engineers named Lucas Pardue, who is also the QUIC Working Group co-Chair, last week [1]pointed out that the Internet Engineering Task Force (IETF) last week [2]posted a notification that QUIC is now at “last call” stage.
QUIC, dig in: Microsoft open-sources MsQuic, its implementation of Google-spawned TCP-killer QUIC [3]READ MORE
As the IETF explains [4]here , Last Call status represent “the final stage of open community review”.
Or as Pardue put it: “At the end of the Last Call period, the stakeholders will take stock, address feedback as needed and, fingers crossed, go onto the next step of requesting the documents be published as RFCs on the Standards Track.”
Which is where things get a little odd, as Pardue writes that even though the Last Call refers to draft 32 of the QUIC spec, version 29 has been chosen as the one to use and is indeed already out there in most major browsers.
That’s not the end of the matter, however. Assuming QUIC survives the last call it will become an IETF RFC, which opens it to further debate and review.
And as Pardue explains, QUIC and HTTP/3 are extensible, so there’s much more to be done. ®
Get our [5]Tech Resources
[1] https://blog.cloudflare.com/last-call-for-quic/
[2] https://mailarchive.ietf.org/arch/msg/quic/ye1LeRl7oEz898RxjE6D3koWhn0/
[3] https://www.theregister.com/2020/05/04/microsoft_reveals_msquic_quic_implementation/
[4] https://www.ietf.org/about/groups/iesg/statements/last-call-guidance/
[5] https://whitepapers.theregister.com/
QUIC’s backers point out that TCP is chatty and therefore imposes long round-trip times on traffic. Which is never welcome, but especially undesirable on wireless networks.
By using a flavor of TLS (Transport Layer Security) over the internet's UDP protocol instead of the customary TCP, QUIC can bust some bottlenecks that can happen when a TCP connection loses packets. QUIC therefore makes it possible for a client and server that have never connected to send data without any round trips between the devices.
The result is faster-loading web pages – which explains why Google backed QUIC – and more elegant internetworking – which explains why Cloudflare likes it.
Speaking of Cloudflare, one of its engineers named Lucas Pardue, who is also the QUIC Working Group co-Chair, last week [1]pointed out that the Internet Engineering Task Force (IETF) last week [2]posted a notification that QUIC is now at “last call” stage.
QUIC, dig in: Microsoft open-sources MsQuic, its implementation of Google-spawned TCP-killer QUIC [3]READ MORE
As the IETF explains [4]here , Last Call status represent “the final stage of open community review”.
Or as Pardue put it: “At the end of the Last Call period, the stakeholders will take stock, address feedback as needed and, fingers crossed, go onto the next step of requesting the documents be published as RFCs on the Standards Track.”
Which is where things get a little odd, as Pardue writes that even though the Last Call refers to draft 32 of the QUIC spec, version 29 has been chosen as the one to use and is indeed already out there in most major browsers.
That’s not the end of the matter, however. Assuming QUIC survives the last call it will become an IETF RFC, which opens it to further debate and review.
And as Pardue explains, QUIC and HTTP/3 are extensible, so there’s much more to be done. ®
Get our [5]Tech Resources
[1] https://blog.cloudflare.com/last-call-for-quic/
[2] https://mailarchive.ietf.org/arch/msg/quic/ye1LeRl7oEz898RxjE6D3koWhn0/
[3] https://www.theregister.com/2020/05/04/microsoft_reveals_msquic_quic_implementation/
[4] https://www.ietf.org/about/groups/iesg/statements/last-call-guidance/
[5] https://whitepapers.theregister.com/