QUIC
From Just Solve the File Format Problem
(Difference between revisions)
Dan Tobias (Talk | contribs) (Created page with "{{FormatInfo |subcat=Web |released=2013 }} '''QUIC''' is a UDP-based transport protocol introduced by Google and implemented in their client and server programs (such as the C...") |
|||
| Line 4: | Line 4: | ||
}} | }} | ||
'''QUIC''' is a UDP-based transport protocol introduced by Google and implemented in their client and server programs (such as the Chrome browser) and in open-source code available for experimentation. It is designed for faster Internet communication by reducsing the number of "round trips" of data transmission necessary to establish a secure connection, which it does by having the two sides of the connection keep track of the other hosts they have previously been in communication with so that preliminary stages in handshaking to establish a connection can be skipped. | '''QUIC''' is a UDP-based transport protocol introduced by Google and implemented in their client and server programs (such as the Chrome browser) and in open-source code available for experimentation. It is designed for faster Internet communication by reducsing the number of "round trips" of data transmission necessary to establish a secure connection, which it does by having the two sides of the connection keep track of the other hosts they have previously been in communication with so that preliminary stages in handshaking to establish a connection can be skipped. | ||
| + | |||
| + | == Specifications == | ||
| + | * RFC 8999: Version-Independent Properties of QUIC | ||
| + | * RFC 9000: QUIC | ||
| + | * RFC 9001: Using TLS to Secure QUIC | ||
| + | * RFC 9002: QUIC Loss Detection and Congestion Control | ||
== Links == | == Links == | ||
Latest revision as of 15:03, 31 May 2021
QUIC is a UDP-based transport protocol introduced by Google and implemented in their client and server programs (such as the Chrome browser) and in open-source code available for experimentation. It is designed for faster Internet communication by reducsing the number of "round trips" of data transmission necessary to establish a secure connection, which it does by having the two sides of the connection keep track of the other hosts they have previously been in communication with so that preliminary stages in handshaking to establish a connection can be skipped.
[edit] Specifications
- RFC 8999: Version-Independent Properties of QUIC
- RFC 9000: QUIC
- RFC 9001: Using TLS to Secure QUIC
- RFC 9002: QUIC Loss Detection and Congestion Control
