Google ya sanar kwanakin baya an riga an fara shi ƙaddamar da HTTP / 3 da IETF QUIC a cikin Chrome kuma a cikin sanarwar, ya faɗi cewa yana tsammanin wannan sabuntawar zai kawo wasu ƙarin ingantaccen aikin, musamman tare da tallafi ga QUIC.
QUIC sabuwar yarjejeniya ce ta safarar hanyar sadarwa wanda ya haɗu da fasalin TCP, TLS da ƙari. HTTP / 3 shine sabon sigar HTTP, yarjejeniyar da ke dauke da yawancin zirga-zirgar yanar gizo. HTTP / 3 yana aiki ne kawai akan QUIC.
Engineeringungiyar Injiniyan Injin Intanet, ko IETF, sun gabatar da HTTP / 2 a cikin 2015, kuma ɗayan manyan ci gaban da aka yi shi ne tallafi don yawaita abubuwa.
Koyaya, tayi amfani da TCP azaman yarjejeniya ta jigilar kayayyaki da hanyoyin dawo da asara a cikin TCP, saboda haka ɓatattun fakiti na iya haifar da jinkiri a duk ma'amaloli masu aiki.
Ta hanyar yin amfani da QUIC, HTTP / 3 na iya ƙara inganta aikin canja wurin, Tunda ɓatattun fakiti a cikin wannan yanayin suna shafar ma'amaloli da abin ya shafa kai tsaye.
A gaskiya ma, QUIC asalin kamfanin Google ne suka kirkireshi kuma an fara sanarwa a cikin 2013. Tun daga wannan lokacin, ladabi ya tsufa kuma a halin yanzu shine ke da alhakin ɗaukar kashi ɗaya cikin uku na zirga-zirgar Google.
Bayan haka, a cikin 2015, ci gaban QUIC ya shiga hannun IETF, ƙa'idodin ƙungiyar da ke da alhakin kiyaye ladabi na Intanet. IETF ya inganta QUIC tare da canje-canje da yawa. Zuwa yau, akwai ladabi guda biyu, amma daban-daban, waɗanda sune: Google QUIC da IETF QUIC.
Google ya sanar da cewa koyaushe yana amfani da irin nasa na QUIC, amma cewa tawagarsa ta QUIC suma suna da hannu wajen aiwatar da sigar mallakar ta IEFT. "Mun yi matukar kokari don bunkasa Google QUIC a cikin shekaru biyar da suka gabata don ci gaba da sauye-sauyen da IETF ta yi, kuma sabon salon Google QUIC na yanzu yana da kamanceceniya da IETF QUIC," in ji rubutun a shafin. daga Google, ƙari, ya bayyana cewa wasu abubuwa har yanzu sun ɓace.
A matsayin misali, ya zuwa yanzu yawancin masu amfani da Chrome ba sa iya sadarwa tare da sabobin IETF QUIC ba tare da kunna wasu zaɓuɓɓukan layin umarni ba. Hakazalika, Google ya kara da cewa yanzu ya gano cewa IETF QUIC ya wuce HTTP sosai idan aka kwatanta da TLS 1.3 idan aka kwatanta da TCP.
Musamman, kamfanin ya ce jinkirin injin binciken Google ya ragu da fiye da 2%. Lokacin rage lokacin YouTube ya ragu da fiye da 9%. Ari, aikin abokin ciniki ya karu da fiye da 3% akan kwamfutocin tebur.
A wayoyin hannu, aikin abokin ciniki ya karu da fiye da 7%. Wadannan da sauran dalilan suna bayan sauyawar Chrome zuwa sigar QUIC ta IETF. “Muna farin cikin sanar da cewa Chrome na aiwatar da tallafi ga IETF QUIC (musamman, fasalin gwajin h3-29).
A yau, kimanin 25% na masu amfani da tsayayyen sigar Chrome suna amfani da h3-29, kuma muna shirin ƙara wannan lambar a cikin makonni masu zuwa ta hanyar ci gaba da lura da bayanan aikin, ”in ji kamfanin a cikin shafinsa na yanar gizo. .
Ya kara da cewa "Chrome zai taimaka sosai da IETF QUIC h3-29 da kuma Google QUIC version (Q050) don ba da dama ga sabobin da ke tallafawa Q050 su inganta zuwa IETF QUIC." Chrome m85 bai riga ya goyi bayan IETF QUIC 0-RTT ba kuma Google yana tsammanin wannan aikin ya fi kyau idan ya saki tallafi ga IETF QUIC 0-RTT a cikin watanni masu zuwa. Hakanan, tunda sigar IETF QUIC ta 30 da 31 basu ƙunshi canje-canje da zasu iya lalata daidaito ba, kamfanin ba ya shirin canza mai ganowa "waya-da-waya".
Wannan yana nuna cewa - zai ci gaba da bin sauye-sauye a cikin tsarin IETF, amma zai aiwatar azaman h3-29 / 0xff00001d.
Sabili da haka, yana ba da shawarar cewa sabobin su ci gaba da tallafawa h3-29 har sai an kammala RFCs ta ƙarshe idan suna son hulɗa da Chrome. Koyaya, idan IETF yayi canje-canje wanda ke lalata daidaituwa a cikin aikin gaba, Chrome zai juya wannan shawarar.
Source: https://blog.chromium.org