![\"http:\/\/3.bp.blogspot.com\/-smLjXAyzEP0\/VZJ9IktYvyI\/AAAAAAAAGFU\/zd_FQmBZWF0\/s1600\/1.png\"](\"http:\/\/3.bp.blogspot.com\/-smLjXAyzEP0\/VZJ9IktYvyI\/AAAAAAAAGFU\/zd_FQmBZWF0\/s1600\/1.png\")
<\/p>\nAs improving TCP is a long-term goal for Google, QUIC aims to be nearly equivalent to an independent\u00a0TCP\u00a0connection, but with much reduced latency (goal: 0-RTT\u00a0connectivity overhead) and better\u00a0SPDY-like stream-multiplexing support; if QUIC features prove effective, those features could migrate into a later version of TCP and TLS (which have a notably longer deployment cycle).\u00a0With QUIC, Google aims to combine some of the best features of UDP and TCP with modern security tools.<\/p>\n
<\/p>\n
On a typical secure TCP connection,\u00a0it typically takes two or three round-trips before the browser can actually start receiving data. Using QUIC, a browser can immediately start talking to a server it has talked to before.\u00a0QUIC also introduces a couple of new features like congestion control and automatic re-transmission, making it more reliable that pure UDP.<\/p>\n
With SPDY, which later became the basis for the HTTP\/2 standard, Google already developed\u00a0another alternative protocol that\u00a0had many of the same goals as QUIC, but HTTP\/2\u00a0still runs over TCP and still runs into some of the same latency cost.<\/p>\n
It\u2019s reasonable to ask\u00a0why Google doesn\u2019t just work on improving TCP instead then. The problem here, the company\u00a0points out, is that TCP support is often built directly into operating system kernels \u2014 and that\u2019s not something Google has any control over. \u201cQUIC allows us to test and experiment with new ideas, and to get results sooner,\u201d the team writes in explaining its decision. \u201cWe are hopeful that QUIC features will migrate into TCP and TLS if they prove effective.\u201d<\/p>\n
If Google designed a whole new protocol, then all\u00a0of the machines that make up the backbone of the Internet\u00a0would also have to understand it \u2014 but they already understand UDP.<\/p>\n
QUIC (Quick UDP Internet Connections) is an experimental transport layer network protocol developed by Google. Starting from 2015, some sites (For example Google and YouTube) offer connection via QUIC protocol. Google Chrome support it in latest version by default. QUIC uses UDP port 80 and port 443 and often permits clients to bypass transparent proxies, in which UTM feature such as web filtering may not work properly on Google Chrome only, but works perfectly on other browsers such as Internet Explorer or Mozilla Firefox.<\/p>\n
There are three ways to block\/disable QUIC:<\/u><\/strong><\/p>\n Method 1:<\/strong> Disable Experimental QUIC protocol on Google Chrome browser. – This can be done by opening Google Chrome, in the URL type “chrome:\/\/flags”. Look for Experimental QUIC protocol and disable it.<\/p>\n Method 2:<\/strong> Block QUIC using Application Control – Go to Application Control profile, look for Application signature name “QUIC” and select the action “Block”. Apply this Application Control profile into the firewall policy.<\/p>\n Method 3<\/strong>: Block QUIC using firewall policy – Create a custom firewall service for UDP port 80 and port 443. Configure a firewall policy with the custom service created and set the action to Deny. Make sure this policy on top of all ( inside to outside)<\/p>\n <\/p>\n As improving TCP is a long-term goal for Google, QUIC aims to be nearly equivalent to an independent\u00a0TCP\u00a0connection, but with much reduced latency (goal: 0-RTT\u00a0connectivity overhead) and better\u00a0SPDY-like stream-multiplexing support; if QUIC features prove effective, those features could migrate into<\/p>\n","protected":false},"author":2,"featured_media":0,"comment_status":"open","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[33,20,26,6],"tags":[],"class_list":["post-286592","post","type-post","status-publish","format-standard","hentry","category-browsers","category-cloud","category-networking","category-security"],"_links":{"self":[{"href":"https:\/\/itblog.lcisd.net\/index.php?rest_route=\/wp\/v2\/posts\/286592","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/itblog.lcisd.net\/index.php?rest_route=\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/itblog.lcisd.net\/index.php?rest_route=\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/itblog.lcisd.net\/index.php?rest_route=\/wp\/v2\/users\/2"}],"replies":[{"embeddable":true,"href":"https:\/\/itblog.lcisd.net\/index.php?rest_route=%2Fwp%2Fv2%2Fcomments&post=286592"}],"version-history":[{"count":4,"href":"https:\/\/itblog.lcisd.net\/index.php?rest_route=\/wp\/v2\/posts\/286592\/revisions"}],"predecessor-version":[{"id":286596,"href":"https:\/\/itblog.lcisd.net\/index.php?rest_route=\/wp\/v2\/posts\/286592\/revisions\/286596"}],"wp:attachment":[{"href":"https:\/\/itblog.lcisd.net\/index.php?rest_route=%2Fwp%2Fv2%2Fmedia&parent=286592"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/itblog.lcisd.net\/index.php?rest_route=%2Fwp%2Fv2%2Fcategories&post=286592"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/itblog.lcisd.net\/index.php?rest_route=%2Fwp%2Fv2%2Ftags&post=286592"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}![\"http:\/\/1.bp.blogspot.com\/-S5bNlzvolpQ\/VZJ9bb0ynbI\/AAAAAAAAGFc\/65nuGnvJq78\/s1600\/2.png\"](\"http:\/\/1.bp.blogspot.com\/-S5bNlzvolpQ\/VZJ9bb0ynbI\/AAAAAAAAGFc\/65nuGnvJq78\/s1600\/2.png\")
<\/p>\n![\"http:\/\/4.bp.blogspot.com\/-Alh5Mrv-HZQ\/VZJ9qWU5CyI\/AAAAAAAAGFk\/trNIsigMdyY\/s1600\/3.png\"](\"http:\/\/4.bp.blogspot.com\/-Alh5Mrv-HZQ\/VZJ9qWU5CyI\/AAAAAAAAGFk\/trNIsigMdyY\/s1600\/3.png\")
<\/p>\nQUIC, a multiplexed stream transport over UDP<\/span><\/a><\/h3>\n","protected":false},"excerpt":{"rendered":"