{"id":8242,"date":"2017-10-04T12:00:13","date_gmt":"2017-10-04T16:00:13","guid":{"rendered":"https:\/\/blog.litespeedtech.com\/?p=8242"},"modified":"2017-10-04T12:00:13","modified_gmt":"2017-10-04T16:00:13","slug":"nftr-quic-working-group-day-one","status":"publish","type":"post","link":"https:\/\/lswp.store\/index.php\/2017\/10\/04\/nftr-quic-working-group-day-one\/","title":{"rendered":"NFtR: QUIC Working Group Day One"},"content":{"rendered":"<p><a href=\"https:\/\/lswp.store\/wp-content\/uploads\/2017\/10\/nftr02.png\"><img fetchpriority=\"high\" decoding=\"async\" class=\"aligncenter size-large wp-image-8246\" src=\"https:\/\/lswp.store\/wp-content\/uploads\/2017\/10\/nftr02-1024x512.png\" alt=\"\" width=\"1024\" height=\"512\" srcset=\"https:\/\/lswp.store\/wp-content\/uploads\/2017\/10\/nftr02-1024x512.png 1024w, https:\/\/lswp.store\/wp-content\/uploads\/2017\/10\/nftr02-300x150.png 300w, https:\/\/lswp.store\/wp-content\/uploads\/2017\/10\/nftr02-768x384.png 768w, https:\/\/lswp.store\/wp-content\/uploads\/2017\/10\/nftr02-1536x768.png 1536w, https:\/\/lswp.store\/wp-content\/uploads\/2017\/10\/nftr02-1320x660.png 1320w, https:\/\/lswp.store\/wp-content\/uploads\/2017\/10\/nftr02-600x300.png 600w, https:\/\/lswp.store\/wp-content\/uploads\/2017\/10\/nftr02.png 1600w\" sizes=\"(max-width: 1024px) 100vw, 1024px\" \/><\/a><\/p>\n<p>Today, October 3rd, was the <em>interop<\/em> day, allocated for the different IETF QUIC implementations to test interoperability: that is, whether they can talk to each other using the QUIC protocol. &#8230;But let me take a step back and start at the beginning.<\/p>\n<p>I came to the IETF QUIC Working Group (WG) Interim Meeting in Seattle, WA to participate in discussions to iron out the details of the IETF version of the QUIC protocol, which is to become the standard. The drafts under consideration &#8212; <a href=\"https:\/\/github.com\/quicwg\/base-drafts\/blob\/master\/draft-ietf-quic-transport.md\">QUIC Transport<\/a>, <a href=\"https:\/\/github.com\/quicwg\/base-drafts\/blob\/master\/draft-ietf-quic-http.md\">HTTP over QUIC<\/a>, <a href=\"https:\/\/github.com\/quicwg\/base-drafts\/blob\/master\/draft-ietf-quic-tls.md\">QUIC Crypto<\/a>, and the two compression proposals to replace HPACK &#8212; <a href=\"https:\/\/tools.ietf.org\/html\/draft-bishop-quic-http-and-qpack\">QPACK<\/a> and <a href=\"https:\/\/tools.ietf.org\/html\/draft-krasic-quic-qcram\">QCRAM<\/a> &#8212; differ significantly from the current QUIC specifications. Or, rather, the current gQUIC specifications (let\u2019s be precise!) &#8212; <strong>g<\/strong> is for Google. QUIC has evolved from being simply a <a href=\"https:\/\/docs.google.com\/document\/d\/1RNHkx_VvKWyWg6Lr8SZ-saqsQx7rFV-ev2jRFUoVD34\/preview\">transport to better support SPDY<\/a> to being a generic transport protocol &#8212; <a href=\"https:\/\/quicwg.github.io\/\">the next transport protocol for the Internet<\/a>.<\/p>\n<p>That sounds somewhat grandiose, but if anyone can pull it off, this group of people can. The interest in QUIC is growing, as evidenced by the attendees: F5 Networks (the conference host); Akamai; Apple; AT&amp;T; Facebook; Google; Microsoft; and several smaller organizations, among which I certainly count ourselves, LiteSpeed Technologies.<\/p>\n<p><a href=\"https:\/\/lswp.store\/wp-content\/uploads\/2017\/10\/WP_20171003_015.jpg\"><img decoding=\"async\" class=\"aligncenter wp-image-8248 size-large\" src=\"https:\/\/lswp.store\/wp-content\/uploads\/2017\/10\/WP_20171003_015-e1507121739337-1024x579.jpg\" alt=\"\" width=\"1024\" height=\"579\" srcset=\"https:\/\/lswp.store\/wp-content\/uploads\/2017\/10\/WP_20171003_015-e1507121739337-1024x579.jpg 1024w, https:\/\/lswp.store\/wp-content\/uploads\/2017\/10\/WP_20171003_015-e1507121739337-300x170.jpg 300w, https:\/\/lswp.store\/wp-content\/uploads\/2017\/10\/WP_20171003_015-e1507121739337-768x434.jpg 768w, https:\/\/lswp.store\/wp-content\/uploads\/2017\/10\/WP_20171003_015-e1507121739337-1536x869.jpg 1536w, https:\/\/lswp.store\/wp-content\/uploads\/2017\/10\/WP_20171003_015-e1507121739337-2048x1158.jpg 2048w, https:\/\/lswp.store\/wp-content\/uploads\/2017\/10\/WP_20171003_015-e1507121739337-1320x746.jpg 1320w, https:\/\/lswp.store\/wp-content\/uploads\/2017\/10\/WP_20171003_015-e1507121739337-600x339.jpg 600w\" sizes=\"(max-width: 1024px) 100vw, 1024px\" \/><\/a><\/p>\n<p>Our own LiteSpeed QUIC does not yet support IETF QUIC. Hence, I spent my time building and reading other projects. There are already a few, to borrow a term, <em>inchoate<\/em> IETF QUIC <a href=\"https:\/\/github.com\/quicwg\/base-drafts\/wiki\/Implementations\">implementations<\/a>, and that is very good.<\/p>\n<p>It was great to meet, and talk shop with, Marten Seemann (he of the quic-go project) and Jana Iyengar (Chromium), whose code I\u2019ve studied and used to test <a href=\"https:\/\/github.com\/litespeedtech\/lsquic-client\">our own code<\/a>. I also met Eric Rescorla, whose <a href=\"https:\/\/www.amazon.com\/SSL-TLS-Designing-Building-Systems\/dp\/0201615983\">SSL book<\/a> I first read fifteen years ago. (If you did programming fifteen years ago, you\u2019ve read his book). I haven\u2019t caught the names of all the people in attendance, but I hope to rectify that over the next two days, when the protocol is to be debated.<\/p>\n<p>Now it is getting late and it is time to turn down for the night. Perhaps I will re-read a few pages of the new drafts before shutting my eyes. I will dream of QUIC.<\/p>\n<p>P. S. For lunch, a few of us went across the street to get Thai food <strong>from a food truck!<\/strong> Of course, it tasted like one would expect food truck Thai food to taste. You can\u2019t win them all.<\/p>\n","protected":false},"excerpt":{"rendered":"<p>Thoughts from the IETF QUIC Working Group Interim Meeting in Seattle, where they are ironing out the details of the IETF version of the QUIC protocol.<\/p>\n","protected":false},"author":1,"featured_media":8246,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"_jetpack_memberships_contains_paid_content":false,"footnotes":""},"categories":[18],"tags":[201,238,240],"class_list":["post-8242","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-conferences","tag-notes-from-the-road","tag-quic","tag-quic-working-group"],"jetpack_featured_media_url":"https:\/\/lswp.store\/wp-content\/uploads\/2017\/10\/nftr02.png","jetpack_sharing_enabled":true,"_links":{"self":[{"href":"https:\/\/lswp.store\/index.php\/wp-json\/wp\/v2\/posts\/8242","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/lswp.store\/index.php\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/lswp.store\/index.php\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/lswp.store\/index.php\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/lswp.store\/index.php\/wp-json\/wp\/v2\/comments?post=8242"}],"version-history":[{"count":0,"href":"https:\/\/lswp.store\/index.php\/wp-json\/wp\/v2\/posts\/8242\/revisions"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/lswp.store\/index.php\/wp-json\/wp\/v2\/media\/8246"}],"wp:attachment":[{"href":"https:\/\/lswp.store\/index.php\/wp-json\/wp\/v2\/media?parent=8242"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/lswp.store\/index.php\/wp-json\/wp\/v2\/categories?post=8242"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/lswp.store\/index.php\/wp-json\/wp\/v2\/tags?post=8242"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}