QUIC is a new encrypted-by-default Internet transport protocol that accelerates HTTP traffic and which has the intention to eventually replace TCP. Originally proposed by Google, the IETF is now actively pursuing work to define and standardize a series of RFCs for the first IETF QUIC transport protocol.
Since QUIC transport fully encrypts all transport protocol headers and authenticates the endpoints of a connection, currently widely deployed Performance Enhancement Proxies (PEP) can no longer be used to improve TCP performance.
The real interactions of QUIC using a satellite service have not been fully explored yet. The project objectives are to identify the root causes of any shortfalls in performance of specific QUIC mechanisms, propose changes to the specification, and evaluate the new proposals using a real-time emulation test bed used already for the MTAILS project [LINK MTAILS PROJECT]. The results of this work are contributed as code patches, presentations and direct contributions to the IETF, primarily targeting the QUIC Working Group.
Initially, focus is on QUICv1, where there is still an opportunity to influence standardisation work. After its standardisation, work shall focus on satellite-specific enhancement to be included in QUICv2.