QUIC Plugins

Document Type Expired Internet-Draft (individual)
Authors Maxime Piraux  , Quentin De Coninck  , Fran├žois Michel  , Florentin Rochet  , Olivier Bonaventure 
Last updated 2020-09-10 (latest revision 2020-03-09)
Stream (None)
Expired & archived
pdf htmlized bibtex
Additional Resources
Stream Stream state (No stream defined)
Consensus Boilerplate Unknown
RFC Editor Note (None)
IESG IESG state Expired
Telechat date
Responsible AD (None)
Send notices to (None)

This Internet-Draft is no longer active. A copy of the expired Internet-Draft can be found at


The extensibility of Internet protocols is a key factor to their success. Yet, their implementations are often not designed with agility in mind. In this document, we leverage the features of the QUIC protocol and propose a solution to dynamically extend QUIC implementations. Our solution relies on QUIC Plugins that allow tuning and extending the QUIC protocol on a per-connection basis. These platform-independent plugins are executed inside a sandboxed environment which can be included in QUIC implementations. We describe how such plugins can be used in different use cases. This document is a straw-man proposal. It aims at sparking discussions on the proposed approach.


Maxime Piraux (maxime.piraux@uclouvain.be)
Quentin De Coninck (quentin.deconinck@uclouvain.be)
Fran├žois Michel (francois.michel@uclouvain.be)
Florentin Rochet (florentin.rochet@uclouvain.be)
Olivier Bonaventure (Olivier.Bonaventure@uclouvain.be)

(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)