Quick UDP Internet Connections
| Quick UDP Internet Connections | |
|---|---|
| Family: | Internet protocol family |
| Field of application: | Data transfer (hypertext, etc.) on the application layer |
| Based on | UDP |
| developed from | SPDY |
| Developer: | Google LLC , IETF |
| application | QUIC | ||||
| transport | UDP | ||||
| Internet | IP ( IPv4 , IPv6 ) | ||||
| Network access | Ethernet |
Token bus |
Token ring |
FDDI | ... |
Quick UDP Internet Connections ( QUIC ) is an experimental network protocol . It was originally developed by Google with the aim of speeding up internet traffic overall. The Internet Engineering Task Force (IETF) has been working on standardizing the QUIC protocol since February 2017 .
Background and characteristics
As a further development of HTTP , Google has already developed the SPDY protocol , but its innovations can not be fully used due to the restrictions of the underlying Transmission Control Protocol . The UDP- based QUIC is intended to remove these restrictions .
The original form of QUIC was introduced by Google on July 20, 2016 for standardization.
QUIC stipulates that the data sent is encrypted using TLS 1.3. Two different headers are used. The first header contains more information and is used to establish the connection. Once connected, the shorter header is used. In the case of a known host, the encryption is not renegotiated when the connection is re-established, but rather encrypted from the first packet onwards. Since a large part of the header is encrypted, less metadata can be read out of the header compared to older protocols. This on the one hand better preserves the privacy of the users, but on the other hand makes network monitoring and management more difficult.
support
QUIC must be supported by the application. The first browser to support QUIC on the client side was Google Chrome version 29 or higher. Example implementations for client and server can be found in the Chromium repository . However, this is still the version originally implemented by Google. Starting with version 72, Firefox has also implemented experimental support for the version developed by the IETF.
Web links
- HTTP / 3 explained free and open book on http / 3 and QUIC in different languages
Individual evidence
- ^ QUIC workgroup. Retrieved April 5, 2017 .
- ↑ Monika Ermert: QUIC comes quicker: IETF advances the new Internet transport protocol. Heise, April 5, 2017, accessed April 5, 2017 .
- ↑ Experimenting with QUIC. In: Chromium Blog. Google, June 27, 2013, accessed June 29, 2013 .
- ^ IETF-96: QUIC. July 20, 2016, accessed December 10, 2016 .
- ↑ M. Thomson, S. Turner: Using Transport Layer Security (TLS) to Secure QUIC. (txt) IETF, March 13, 2017, accessed April 5, 2017 (English).
- ↑ M. Kuehlewind, B. Trammell, D. Druta: Manageability of the QUIC Transport Protocol. (txt) IETF, March 9, 2017, accessed April 5, 2017 .
- ↑ Christian Kirsch: Google is experimenting with UDP for the web. In: iX. Heise, June 28, 2013, accessed June 29, 2013 .
- ↑ Sebastian Grüner: Firefox Nightly supports HTTP / 3 experiments. In: Golem.de. Computec Media GmbH, November 6, 2019, accessed on November 15, 2019 .