IETF Logo Mail Archive

Re: QUIC for IoT embeddeds system

Mikkel Fahnøe Jørgensen <mikkelfj@gmail.com> Sun, 18 August 2019 05:57 UTC

Return-Path: <mikkelfj@gmail.com>
X-Original-To: quic@ietfa.amsl.com
Delivered-To: quic@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id A0248120041 for <quic@ietfa.amsl.com>; Sat, 17 Aug 2019 22:57:42 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.997
X-Spam-Level:
X-Spam-Status: No, score=-0.997 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, FREEMAIL_REPLY=1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, UNPARSEABLE_RELAY=0.001] autolearn=no autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id p0rPV3NjF6Jj for <quic@ietfa.amsl.com>; Sat, 17 Aug 2019 22:57:41 -0700 (PDT)
Received: from mail-ed1-x531.google.com (mail-ed1-x531.google.com [IPv6:2a00:1450:4864:20::531]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 2FA0412001A for <quic@ietf.org>; Sat, 17 Aug 2019 22:57:41 -0700 (PDT)
Received: by mail-ed1-x531.google.com with SMTP id s15so8485152edx.0 for <quic@ietf.org>; Sat, 17 Aug 2019 22:57:41 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=from:in-reply-to:references:mime-version:date:message-id:subject:to; bh=C8O2eV2ecuMzhqBG2WXMvxmPcz/J+dYepCS4lGu7+zs=; b=pbF3M3XOVWgum0V+2d6av0qmjixsSzb7bspZQwEdWMjKI5Qm+AbIDC4aGhqprolfZZ 3iBmN2LgXUV5xb73Wa2qAdFWb7zAoFqi8oEYeLvGrOfKJeAksncnSn7O1qxSVbfuCzOz zNdAgVm3fJm+hsH29IuRo5KJsgrruCYeJvXKoPGj4O8VmaaWNyYFSP8BTOK0JTfLJSRd L+U8JWslRWZBsWHGm1y2miWsQJiaaSP7RKBhE2YVetciM+hOmrGzMqaGPFweK/7SR9HS 28jyP7qyNPAkL8EA7eLPjTBEuTbhh/l54dNJLquS/ixGcdOxdLCdzKJAnZTz2X2rwCf9 sRTg==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:from:in-reply-to:references:mime-version:date :message-id:subject:to; bh=C8O2eV2ecuMzhqBG2WXMvxmPcz/J+dYepCS4lGu7+zs=; b=qLqojR0fPP+6uqNGTQm3Aiq5T1FiGyvvqfAfYXUZoO/EDZyxXVsfEOJI7xWhdtZxjp JnLbBSKKDf98snKMjziinyljW6m1Sfk0tlPaplBMolQANtvSOOdAvMjcXp4WmInz/35s eaJNsxzGmnRpbNTbEYBWKx8XjdsvqQpqczqd0/bWLIdtg6qo9MSAkvh9BOiEP6q9fl7y yhv2jlCZrnK3mUYhfB0PG3YZNR2Br1rltzHOTu+Xbkw5kYI5+VdG/nfy5NwQyvA1Zchy XBeRFURVIXrzcaQKfclAKmXHWSjHcKWj4VUaz4lprbZOmZcy7kKcBrw//JjM3WT5QgFt QAQg==
X-Gm-Message-State: APjAAAVWdVrYuVLey3OkWOY1M9jOtYMKiF7ONDXTCTeZbxMEEL7t5Qis NR8vXwsm3Vl1lhhNanuaxyWaHnCrnh5NOVuhLN0=
X-Google-Smtp-Source: APXvYqzNx/I8/38LMEjz4EO9j2a0dWINLatmn+/AvVwJMcVytz3I1DOsniY11U1YLVwJ4cVwNqbFcGN2tzKAnBY8lFs=
X-Received: by 2002:a17:906:4c81:: with SMTP id q1mr4768247eju.185.1566107859724; Sat, 17 Aug 2019 22:57:39 -0700 (PDT)
Received: from 1058052472880 named unknown by gmailapi.google.com with HTTPREST; Sun, 18 Aug 2019 01:57:38 -0400
From: Mikkel Fahnøe Jørgensen <mikkelfj@gmail.com>
In-Reply-To: <CAA=hcWQ2dPNcktjNMQBE8ovj1xyEOtBgE8S2qBuRz832R=7d6w@mail.gmail.com>
References: <CAA=hcWQ2dPNcktjNMQBE8ovj1xyEOtBgE8S2qBuRz832R=7d6w@mail.gmail.com>
X-Mailer: Airmail (420)
MIME-Version: 1.0
Date: Sun, 18 Aug 2019 01:57:38 -0400
Message-ID: <CAN1APdfHBgR3NMPZTakny2uecgHnngMxAXVpyP7hjucBUOv7oQ@mail.gmail.com>
Subject: Re: QUIC for IoT embeddeds system
To: JH <jupiter.hce@gmail.com>, IETF QUIC WG <quic@ietf.org>
Content-Type: multipart/alternative; boundary="000000000000a8add805905de667"
Archived-At: <https://mailarchive.ietf.org/arch/msg/quic/fnIOo-kX5q8TvRf_LqG8O3Law4k>
X-BeenThere: quic@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Main mailing list of the IETF QUIC working group <quic.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/quic>, <mailto:quic-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/quic/>
List-Post: <mailto:quic@ietf.org>
List-Help: <mailto:quic-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/quic>, <mailto:quic-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sun, 18 Aug 2019 05:57:43 -0000

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.

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.

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.

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

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.


Kind Regards,
Mikkel Fahnøe Jørgensen


On 18 August 2019 at 02.03.06, JH (jupiter.hce@gmail.com) 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

v2.46.0 | Report a Bug | By Email | System Status