<?xml version="1.0" encoding="UTF-8"?>
<reference anchor="I-D.piraux-quic-plugins" target="https://datatracker.ietf.org/doc/html/draft-piraux-quic-plugins-00">
   <front>
      <title>QUIC Plugins</title>
      <author initials="M." surname="Piraux" fullname="Maxime Piraux">
         <organization>UCLouvain</organization>
      </author>
      <author initials="Q." surname="De Coninck" fullname="Quentin De Coninck">
         <organization>UCLouvain</organization>
      </author>
      <author initials="F." surname="Michel" fullname="François Michel">
         <organization>UCLouvain</organization>
      </author>
      <author initials="F." surname="Rochet" fullname="Florentin Rochet">
         <organization>UCLouvain</organization>
      </author>
      <author initials="O." surname="Bonaventure" fullname="Olivier Bonaventure">
         <organization>UCLouvain</organization>
      </author>
      <date month="March" day="9" year="2020" />
      <abstract>
	 <t>   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.

	 </t>
      </abstract>
   </front>
   <seriesInfo name="Internet-Draft" value="draft-piraux-quic-plugins-00" />
   
</reference>
