QUIC is Google’s new protocol aimed at increasing the efficiency and speed of the Internet. It is on Google Chrome by default and used by a rising website database. But, many, firewalls actually cannot acknowledge traffic of QUIC as ‘web’ traffic, so that it is not examined, reported or logged or and leaves a broken loop in the security of your network. In this article, we have covered the working of QUIC and its consequences on the security of the network.
Google is concerned with speed and has made multiple attempts throughout many years to make the Internet more useful and accessible. QUIC is a protocol used for the improvement of performance. QUIC is a different strategy utilizing UDP as just a transport protocol. It is HTTP/2 over UDP, a modern layer4 protocol.
QUIC is enabled in Google Chrome by default, and you can enable it in Opera 16. Specific other browsers are also going to follow the protocol once it is completed. It is applied to all internet resources of Google like Youtube, Gmail, Google Search, and Drive.
Why is QUIC created?
- When the data packets are lost, it gives you a better performance. HTTP/2 on TCP may be influenced by head-of-line blocking, a condition in which the first packet carries a series or line of data packets. When one data packet is missing, the receiver will wait until it is recovered, which will have an enormous effect on the connection quality. The QUIC protocol addresses this issue through the independent transmission of data streams into their target destination, and you don’t have to wait to fix the missing data package.
- The connection times have been reduced. The server and the client must conduct a TLS handshake and replace the keys of encryption to develop TLS encryption. In IT aspects, it is a lengthy method, because four round-trips requests are involved. As the information is transmitted through TCP, further steps are applied, and the connection further slows down. A handshake replaces all of this by QUIC.
- QUIC provides you with steady connections as the networks change. If you are linked to Internet service via a TPC and instantly the network switches, the connection times out will have to be re-established. Through offering every connection to the webserver a specific id, QUIC makes a seamless transition. They can be easily re-established by sending the packet, and you don’t have to establish a new connection.
- QUIC protocol is simple to develop. You have to implement it in the os Kernels, and it is not possible to change it. It is a very flexible protocol, and you can also apply it on the application level.
How QUIC effects the Network Security?
QUIC is expected to improve the effectiveness and speed of Web communications. The primary issue is that safety devices such as firewalls are not already supported, which means for several organizations, the security vulnerability has been created.
Many firewalls have a comprehensive interface when handling the HTTP and HTTPS traffic. Whenever the HTTPS traffic is spotted, it is transferred to the web security module for web filters, profound packet examination, etc. The HTTP traffic is treated, especially because firewalls can interpret the traffic from Layer4 to layer 7.
One of the key enhancements provided by HTTP/2 was the capability to multiply separate HTTP requests on that same TCP connection. HTTP/2 apps are able to handle requests to make better usage of available bandwidth simultaneously.
This was a significant increase in contrast to the status quo at the moment, which needed apps to execute numerous TLS + TCP connections if several HTTP/1.1 requests were to be handled simultaneously.
The creation of new connections involves regular handshakes and the initial congestion period ramp-up. Multiplexing HTTP exchanges avoid all of that. But it also has a negative side as the several requests and responses are transmitted across a TCP connection, so packet losses also affect them. It is known as “blocking head-of-line.”
Disabling or Blocking the QUIC
Given all the above, QUIC is a good thing for the world because it allows internet connections more effective and quicker between the user and the server because every internet user asks for the good internet speed so that the different web pages can load quickly and the Youtube videos can be viewed without buffering.
QUIC over UDP
UDP is a limited interface protocol that enables a request to reach simple datagram services provided by IP. A checksum and a length header which includes the UDP payload and UDP header is added in addition to the destination and source port numbers. It is basically an extension of the actual datagram IP model with some information to enable an IP protocol stack to guide an arriving packet to a request that is linked to a specified UDP port address.
When TCP is an overlay around the existing IP datagram network, then this is a tiny step to worry about putting TCP as just an overlay throughout the UDP datagram system.
Utilizing the internet model, QUIC seems to be, a transport datagram app that has been using the QUIC protocol for sending and receiving the packets with the UDP port 443. It’s a minor change to such an IP packet, contributing only eight bytes to that of the IP packet through putting the header of UDP between the packet headers of TCP and IP.
The QUIC protocol has a few disadvantages. This reduces latency and boosts internet communications, but it is still in its early phase. It is not used extensively by other web servers or sites.
You may also like:
RitaVPN is the most secure and highly encrypted VPN service, which ensures that no one can capture your packet sniffers. It changes your IP address, and the servers of RitaVPN provide you with the high speed of internet connection. Always use a Virtual private network while connecting with the public wifi hotspot. It provides you with a new wall of security.