Re: QUIC for IoT embeddeds system

[JH <[e-mail]>]

On 8/18/19, Mikkel Fahnøe Jørgensen <[e-mail]> wrote:
> I believe the QUIC WG has its hand full just getting version 1 out of the
> door.
> The focus is not limited to HTTP although it is the only defined
> application protocol for the time being. There is a fairly strict
> separation between the transport layer (QUIC) and the application layer
> (HTTP etc. over QUIC). Game application etc. may also be relevant and there
> is separate ongoing work on WebRTC, Websockets, etc. in a new form over
> QUIC - the WebTransport work may cover some or all of this.

Are there any IETF QUIC open sources for clearly separation? Ideally,
a QUIC git source should only contain QUIC core functionality, the
moment you added HTTP, WebRTC, Web sockets to mix with the QUIC
source, there will never be a clear separation.

> The intention for IoT, as I undertand it, is for “someone” to pick up the
> ball and specify a new QUIC version aimed for constrained devices. QUIC is
> designed to handle such protocol variations.

If the QUIC spec can define core functions mandatory, variations and
options can be added or removed for specific platforms or
applications, that will make it easier to be adapted and adopted. For
IoT embedded system, the size is critical for many small devices.

> In the simplest form such a specification might do away with Retry,
> migration, have a lighter initial packet, and support a only subset of
> crypto algorithms. Note that a lighter initial packet is open to
> amplification attacks so there might be some concerns about IP
> whitelisting.

That details should be handled by implementation if it is capable of
plugging different fmodules or cryto algorithms.

> Another aspect could be transport over non-UDP, non-IP fabric.

The IP is the Internet, same as UDP or TCP, I don't see any non-IP,
non-UDP or non-TCP can be succeeded.

> That would not directly address HTTP/3 or other application protocols but
> it would be a precondition.
> I for one would like to see MQTT over a lighter version of QUIC.

Applications and high level protocols can come and go, QUIC should
follow in UDP/TCP/IP footstep. I am not clear if IETF has already got
an experiment of QUIC open source or if it is going to develop one,
appreciate your advice.

Thanks Mikkel,

- jupiter

>
> Kind Regards,
> Mikkel Fahnøe Jørgensen
>
>
> On 18 August 2019 at 02.03.06, JH ([e-mail]) wrote:
>
> Hi,
>
> I am new to QUIC and just joined the mailing list, it seems to me that
> QUIC working groups focus on HTTP and Web applications. Are there any
> WG working for small socket level QUIC client server for embedded
> system? The requirements for embedded system QUIC is very much
> different to large size of QUIC for HTTP, using small size socket
> level QUIC in embedded system is long overdue, I will be very
> interested in involving the embedded system QUIC development,
> appreciate more information about IETF WG agenda and clarification.
>
> Thank you.
>
> Kind regards,
>
> - Jupiter
>