Re: QUIC – Will it Replace TCP/IP?

Adrian Chadd adrian.chadd at
Wed Apr 29 20:31:40 UTC 2020

On Wed, 29 Apr 2020 at 13:12, Michael Tuexen <tuexen at> wrote:

> > Microsoft just announced that they are open-sourcing their QUIC stack (under an MIT license).
> >
> > MSQUIC is suitable for application and kernel-use (it will ship as part of the Windows kernel), so it might be usable in
> My understanding was that QUIC focuses purely on userland implementations this is interesting.
> Since understanding how the Windows kernel works is on my ToDo list for next life,
> can you explain how they do the public crypto operations in the kernel without
> risking CPU exhaustion attacks (last time I checked, these were expensive).
> > other kernel contexts (FreeBSD/ONTAP, Linux) as well. The amount of work needed is likely (much) less than porting another QUIC stack that is only meant for user-space use. Also, based on my testing, MSQUIC is amongst the faster and most interoperable stacks.
> >
> > In short, if we wanted to do something with QUIC, MSQUIC would probably a good starting point.
> Is there really a demand for kernel based QUIC stacks?

Would we need it to be userland + sockets API, or would just having
their userland API be enough?


More information about the freebsd-transport mailing list