Dear all,
I submitted a draft [0], [1] to discuss a potential extension to the
QUIC protocol. In a nutshell, this extension is a collection of light
changes to the QUIC wire format with the goal to enable implementers to
provide a contiguous zero-copy interface on the receive path to an
application embedding QUIC, which is not something we can do on QUIC v1
using atomic authenticated encryption APIs.
This suggestion may help with QUIC's efficiency concerns to some extend,
and should be cumulative to any future benefit brought by UDP IO
optimizations.
We have an implementation of the suggestions forked from quiche, called
quiceh [2]. We also have a blogpost [3] summarizing the rational and
expected benefits, as well as a (draft) paper [4] with more details and
experiments.
I would suggest reading [3] first, then jumping into [4] for any detail
of concern, and then eventually reading [0]. Please let me know if you
have any question or feedback.
@QUIC chairs: if possible, I'd like to have a few minutes at the next
IETF meeting (121 in Dublin?) to discuss this proposal.
Best regards,
Florentin
[0]
https://www.ietf.org/archive/id/draft-frochet-quicwg-reverso-for-quic-00.html
[1] https://github.com/frochet/draft-rochet-reverso-for-quic
[2] https://github.com/frochet/quiceh
[3] https://reverso.info.unamur.be/
[4] https://arxiv.org/abs/2409.07138
