QUIC Plugins
draft-piraux-quic-plugins-00
| Document | Type |
Expired Internet-Draft
(individual)
Expired & archived
|
|
|---|---|---|---|
| Authors | Maxime Piraux , Quentin De Coninck , François Michel , Florentin Rochet , Olivier Bonaventure | ||
| Last updated | 2020-09-10 (Latest revision 2020-03-09) | ||
| RFC stream | (None) | ||
| Intended RFC status | (None) | ||
| Formats | |||
| Stream | Stream state | (No stream defined) | |
| Consensus boilerplate | Unknown | ||
| RFC Editor Note | (None) | ||
| IESG | IESG state | Expired | |
| Telechat date | (None) | ||
| Responsible AD | (None) | ||
| Send notices to | (None) |
This Internet-Draft is no longer active. A copy of the expired Internet-Draft is available in these formats:
Abstract
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.
Authors
Maxime Piraux
Quentin De Coninck
François Michel
Florentin Rochet
Olivier Bonaventure
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)