Re: Small size of core QUIC library to replace TCP for embedded system

[Jupiter <[e-mail]>]

Thanks Lars and all responses, I am very grateful for all of your kind
comments and advice.

On 7/21/20, Lars Eggert <[e-mail]> wrote:
> you don't really say what type of device you are targeting, so it's a bit
> difficult to respond in detail.

Sorry for neglecting that part, I am running Linux on iMX6ULZ using
all sorts of open source libraries in C and C++.

> But I did port my quant QUIC stack (https://github.com/NTAP/quant) to
> Particle DeviceOS and RIOT, and ran some client-only measurements on a
> Particle Argon and an ESP32. There's a writeup in
> https://eggert.org/papers/2020-ndss-quic-iot.pdf, slides in
> https://github.com/t2trg/2020-ietf107/blob/master/slides/22-towards-securing-the-internet-of-things-with-quic.pdf.
> (There was also a recording of the T2TRG talk, but it doesn't seem to be
> uploaded to GitHub yet.)

Thanks for the links, I have to admit, my QUIC knowledge is limited, I
thought QUIC should be a user space program, anything talking to low
layers through Linux kernel API, seems you have to alter Ethernet RX /
TX for QUIC, does that mean you have to alter WiFi or other media
communications as well? My WiFi is currently supported by Linux open
source mwifiex.

> It should be reasonably straightforward to add a packet I/O backend for
> other IoT platforms to warpcore, (https://github.com/NTAP/warpcore) which is
> quant's packet I/O library. I had been considering Zephyr support, but ran
> out of time.

Looks very good, I suppose I should be able to run it on an Ubuntu 18
laptop, right?

> Note: quant is a research effort and not meant for production.

Understood, let me see if I can make some contributions for the project.


Thank you.

Kind regards,

jupiter


--
"A man can fail many times, but he isn't a failure until he begins to
blame somebody else."
-- John Burroughs