The NetDev conference wiki

User Tools

Site Tools

Trace:
0x13:reports:d1t2t03-quic-tutorial

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revisionPrevious revision
Next revision		Previous revision
0x13:reports:d1t2t03-quic-tutorial [2019/04/08 23:06] – ehalep0x13:reports:d1t2t03-quic-tutorial [2019/09/28 17:04] (current) – external edit 127.0.0.1
Line 4: Line 4:
 Report by: Evangelos Haleplidis Report by: Evangelos Haleplidis
  
-Jana from Fastly, started his QUIC tutorial by going through the history of the QUIC protocol. The QUIC protocol begun at Google around 2014 and was between google services and Chrome and mobile apps. The inital results showed improvements in application performance. Now more than 35% percent of Google's egress traffic is using QUIC. QUIC was introduced to the IETF around 2016 to modularize and standardize QUIC.+Jana from Fastly, started his QUIC tutorial by going through the history of the QUIC protocol. The QUIC protocol begun at Google around 2014 and was between google services and Chrome and mobile apps. The initial results showed improvements in application performance. Now more than 35% percent of Google's egress traffic is using QUIC. QUIC was introduced to the IETF around 2016 to modularize and standardize QUIC.
  
 The QUIC standard is over UDP and uses TLS encryption. QUIC design goals are the following: The QUIC standard is over UDP and uses TLS encryption. QUIC design goals are the following:
 1. Deployability and evolvability. QUIC uses encryption to remove the issues of middleboxes. Jana recounted an issue with the flipping of a bit, QUIC was blocked by firewalls.  1. Deployability and evolvability. QUIC uses encryption to remove the issues of middleboxes. Jana recounted an issue with the flipping of a bit, QUIC was blocked by firewalls. 
 2. Low latency secure connection establishment. QUIC mostly creates establishes connections with 0-RTT and sometimes with 1-RTT. 2. Low latency secure connection establishment. QUIC mostly creates establishes connections with 0-RTT and sometimes with 1-RTT.
-3. Streams and multiplexing. Lightweight abstrations within a connection to avoid head-of-line blocking.+3. Streams and multiplexing. Lightweight abstractions within a connection to avoid head-of-line blocking.
 4. Better loss recovery and flexible congestion control. 4. Better loss recovery and flexible congestion control.
 5. Congestion migration  5. Congestion migration 
Line 41: Line 41:
  
 Q: Optimization for CDN? Q: Optimization for CDN?
-A: This should be a layer abouve quic+A: This should be a layer above quic
  
 Jana then moved to the issue of tracing. In regards to wireshark, it is not enough as data is encrypted. You have to record the whole data and decode before looking at wireshark. Tracing happends at endpoints. Tracing is getting traction, there are currently two tools, quic-trace and Quicvis. Jana then moved to the issue of tracing. In regards to wireshark, it is not enough as data is encrypted. You have to record the whole data and decode before looking at wireshark. Tracing happends at endpoints. Tracing is getting traction, there are currently two tools, quic-trace and Quicvis.
Line 55: Line 55:
 In regards to the acknowledge, it's about the data and not the packets. There is no packet retransmission, but data retransmission.  In regards to the acknowledge, it's about the data and not the packets. There is no packet retransmission, but data retransmission. 
  
-Site: https://www.netdevconf.org/0x13/session.html?tutorial-QUIC+Site: https://www.netdevconf.info/0x13/session.html?tutorial-QUIC
 github: https://github.com/h2o/quicly github: https://github.com/h2o/quicly
- 
-Slides:  
-Videos:  
- 
- 
- 
- 
- 
  
0x13/reports/d1t2t03-quic-tutorial.1554764796.txt.gz · Last modified: 2019/09/28 17:04 (external edit)
Donate Powered by PHP Valid HTML5 Valid CSS Driven by DokuWiki