Skip to content

Latest commit

 

History

History
19 lines (14 loc) · 3.08 KB

quic-weekly-2020-12-09.md

File metadata and controls

19 lines (14 loc) · 3.08 KB
Raw

A collection of various awesome lists for videos, pentesters, libraries and frameworks.

QUIC is the Quick UDP Internet Connections protocol, developed by Google and currently in IETF workgroups for further development. It is being considered for replacing TCP as a transport protocol for HTTP/3. We are building an Open source project for IoT & Edge Computing atop QUIC called 🦖YoMo

Online Community: 🍖discord/quic

Maintainer: 🦖YoMo

QUIC Weekly - 20201209

  • Wireshark v3.4.1 release with lots of updates to QUIC
  • 📢 draft-ietf-quic-manageability discusses manageability of the QUIC transport protocol, focusing on caveats impacting network operations involving QUIC traffic
  • 📢 Applicability of the QUIC Transport Protocol discusses the applicability of the QUIC transport protocol, focusing on caveats impacting application protocol development and deployment over QUIC
  • w3c WebTransport defines a set of ECMAScript APIs in WebIDL to allow data to be sent and received between a browser and server, implementing pluggable protocols underneath with common APIs on top. This specification uses pluggable protocols, with QUIC [QUIC-TRANSPORT] as one such protocol, to send data to and receive data from servers. It can be used like WebSockets but with support for multiple streams, unidirectional streams, out-of-order delivery, and reliable as well as unreliable transport.
  • 📽 David Schinaz from Google QUIC 101
  • Netty release 0.0.1.Final This codec provides a QUIC implementation of draft 32 by wrapping quiche and expose QUIC via the Channel API.
  • Cloudflare blog Accelerating UDP packet transmission for QUIC
  • PDF: Performance analysis of Google’s Quick UDP Internet Connection Protocol under Software Simulator
  • 📢 draft-schinazi-masque-h3-datagram-01 QUIC DATAGRAM extension provides application protocols running over QUIC with a mechanism to send unreliable data while leveraging the security and congestion-control properties of QUIC. However,QUIC DATAGRAM frames do not provide a means to demultiplex application contexts. This document defines how to use QUIC DATAGRAM frames when the application protocol running over QUIC is HTTP/3 by adding an identifier at the start of the frame payload. This allows HTTP messages to convey related information using unreliable DATAGRAM frames, ensuring those frames are properly associated with an HTTP message.