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

[Jana Iyengar <[e-mail]>]

Hi Jupiter,

You might consider the various implementations listed at
https://github.com/quicwg/base-drafts/wiki/Implementations. All the
implementers are on this list, so you should be able to reach them here.

- jana

On Mon, Jul 20, 2020 at 5:53 PM Nick Banks <nibanks=
[e-mail]> wrote:

> Hello!
>
> Feel free to take a look at MsQuic (https://github.com/microsoft/msquic).
> It's written in C and is purely a QUIC implementation (no HTTP/3). We've
> not necessarily targeted it for embedded systems and I can't tell you
> off-hand how small the library will end up being in your scenario. If you
> try it out and find any specific problems, feel free to open issues and we
> can discuss fixing them.
>
> Thanks,
> - Nick
>
> -----Original Message-----
> From: QUIC <[e-mail]> On Behalf Of Jupiter
> Sent: Monday, July 20, 2020 5:31 PM
> To: quic <[e-mail]>
> Subject: Small size of core QUIC library to replace TCP for embedded system
>
> Hi,
>
> I am looking for a slim backbone core QUIC library to replace TCP stack.
>
> Here are core features currently I am using TCP, I am wondering if there
> is a QUIC open source library can be used or to be further developed to
> replace following TCP key functionality
>
> - Replace Boost ASIO TCP by QUIC for socket communication between the
> device and Cloud services.
>
> - Use (Address)-restricted-cone NAT
>
> - Use TCP TLS
>
> The major issue when I looked at Google and other QUIC source is because
> it supports HTTPS, the size is too large, it is not modularized, Some open
> source claimed the library can be used by adding or removing options, the
> reality is most of the QUIC libraries are designed based on HTTPS in mind,
> it is hard to have a clean small size QUIC core functions above.
>
> I have to admit my knowledge about QUIC is limited, but I am a programmer,
> I am keen to participate a modular QUIC open source development for
> embedded system, here are options:
>
> - Take an existing QUIC library (C/C++)
>
> - Fork a QUIC Git source to develop a slim C/C++ QUIC for the embedded
> system.
>
> - Start from scratch based on reference of some QUIC library
>
> Appreciate your advice and suggestions.
>
> 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
>
>