{"id":9693,"date":"2017-01-24T04:33:56","date_gmt":"2017-01-24T03:33:56","guid":{"rendered":"https:\/\/daniel.haxx.se\/blog\/?p=9693"},"modified":"2017-01-24T04:33:56","modified_gmt":"2017-01-24T03:33:56","slug":"first-quic-interim-in-tokyo","status":"publish","type":"post","link":"https:\/\/daniel.haxx.se\/blog\/2017\/01\/24\/first-quic-interim-in-tokyo\/","title":{"rendered":"First QUIC interim &#8211; in Tokyo"},"content":{"rendered":"<p>The <a href=\"https:\/\/datatracker.ietf.org\/wg\/quic\/\">IETF working group QUIC<\/a> has its first <a href=\"https:\/\/github.com\/quicwg\/wg-materials\/blob\/master\/interim-17-01\/arrangements.md\">interim meeting<\/a> in Tokyo Japan for three days. Day one is today, January 24th 2017.<\/p>\n<p>As I&#8217;m not there physically, I attend the meeting from remote using the webex that&#8217;s been setup for this purpose, and I&#8217;ll drop in a little screenshot below from one of the discussions (click it for hires) to give you a feel for it. It shows the issue being discussed and the camera view of the room in Tokyo. I run the jabber client on a different computer which allows me to also chat with the other participants. It works really well, both audio and video are quite crisp and understandable.<\/p>\n<p><a href=\"https:\/\/daniel.haxx.se\/blog\/wp-content\/uploads\/2017\/01\/QUIC-interim-webex.jpg\"><img loading=\"lazy\" decoding=\"async\" class=\"aligncenter size-large wp-image-9709\" src=\"https:\/\/daniel.haxx.se\/blog\/wp-content\/uploads\/2017\/01\/QUIC-interim-webex-1200x639.jpg\" alt=\"\" width=\"474\" height=\"252\" srcset=\"https:\/\/daniel.haxx.se\/blog\/wp-content\/uploads\/2017\/01\/QUIC-interim-webex-1200x639.jpg 1200w, https:\/\/daniel.haxx.se\/blog\/wp-content\/uploads\/2017\/01\/QUIC-interim-webex-200x107.jpg 200w, https:\/\/daniel.haxx.se\/blog\/wp-content\/uploads\/2017\/01\/QUIC-interim-webex-450x240.jpg 450w, https:\/\/daniel.haxx.se\/blog\/wp-content\/uploads\/2017\/01\/QUIC-interim-webex-768x409.jpg 768w, https:\/\/daniel.haxx.se\/blog\/wp-content\/uploads\/2017\/01\/QUIC-interim-webex.jpg 1918w\" sizes=\"auto, (max-width: 474px) 100vw, 474px\" \/><\/a>Japan is eight hours ahead of me time zone wise, so this meeting\u00a0 runs from 01:30 until 09:30 Central European Time. That&#8217;s less comfortable and it may cause me some troubles to attend the entire thing.<\/p>\n<h2>On QUIC<\/h2>\n<p>We started off at once with a lot of discussions on basic issues. Versioning and what a specific version actually means and entails. Error codes and how error codes should be used within QUIC and its different components. Should the transport level know about priorities or shouldn&#8217;t it? How is the security protocol decided?<\/p>\n<p>Everyone who is following <a href=\"https:\/\/github.com\/quicwg\/base-drafts\">the QUIC issues on github<\/a> knows that there are plenty of people with a lot of ideas and thoughts on these matters and this meeting shows this impression is real.<\/p>\n<p>For a casual bystander, you might&#8217;ve been fooled into thinking that because Google already made and deployed QUIC, these issues should be if not already done and decided, at least fairly speedily gone over. But nope. I think there are plenty of indications already that the protocol outputs that will come in the end of this process, the IETF QUIC will differ from the Google QUIC in a fair number of places.<\/p>\n<p>The plan is that the different QUIC drafts (there are at least 4 different planned RFCs as they&#8217;re divided right now) should all be &#8220;done&#8221; during 2018.<\/p>\n<p>(At 4am, the room took lunch and I wrote this up.)<\/p>\n","protected":false},"excerpt":{"rendered":"<p>The IETF working group QUIC has its first interim meeting in Tokyo Japan for three days. Day one is today, January 24th 2017. As I&#8217;m not there physically, I attend the meeting from remote using the webex that&#8217;s been setup for this purpose, and I&#8217;ll drop in a little screenshot below from one of the &hellip; <a href=\"https:\/\/daniel.haxx.se\/blog\/2017\/01\/24\/first-quic-interim-in-tokyo\/\" class=\"more-link\">Continue reading <span class=\"screen-reader-text\">First QUIC interim &#8211; in Tokyo<\/span> <span class=\"meta-nav\">&rarr;<\/span><\/a><\/p>\n","protected":false},"author":5,"featured_media":0,"comment_status":"open","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[22,13],"tags":[249,414],"class_list":["post-9693","post","type-post","status-publish","format-standard","hentry","category-mozilla","category-net","tag-ietf","tag-quic"],"_links":{"self":[{"href":"https:\/\/daniel.haxx.se\/blog\/wp-json\/wp\/v2\/posts\/9693","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/daniel.haxx.se\/blog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/daniel.haxx.se\/blog\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/daniel.haxx.se\/blog\/wp-json\/wp\/v2\/users\/5"}],"replies":[{"embeddable":true,"href":"https:\/\/daniel.haxx.se\/blog\/wp-json\/wp\/v2\/comments?post=9693"}],"version-history":[{"count":8,"href":"https:\/\/daniel.haxx.se\/blog\/wp-json\/wp\/v2\/posts\/9693\/revisions"}],"predecessor-version":[{"id":9716,"href":"https:\/\/daniel.haxx.se\/blog\/wp-json\/wp\/v2\/posts\/9693\/revisions\/9716"}],"wp:attachment":[{"href":"https:\/\/daniel.haxx.se\/blog\/wp-json\/wp\/v2\/media?parent=9693"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/daniel.haxx.se\/blog\/wp-json\/wp\/v2\/categories?post=9693"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/daniel.haxx.se\/blog\/wp-json\/wp\/v2\/tags?post=9693"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}