IETF Logo Mail Archive

QUIC for IoT embeddeds system

JH <jupiter.hce@gmail.com> Sun, 18 August 2019 00:02 UTC

Return-Path: <jupiter.hce@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 2300812007C for <quic@ietfa.amsl.com>; Sat, 17 Aug 2019 17:02:50 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.999
X-Spam-Level:
X-Spam-Status: No, score=-1.999 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, RCVD_IN_DNSWL_NONE=-0.0001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001] autolearn=ham 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 mAWh74MfAFaV for <quic@ietfa.amsl.com>; Sat, 17 Aug 2019 17:02:48 -0700 (PDT)
Received: from mail-io1-xd2f.google.com (mail-io1-xd2f.google.com [IPv6:2607:f8b0:4864:20::d2f]) (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 9A20812006D for <quic@ietf.org>; Sat, 17 Aug 2019 17:02:48 -0700 (PDT)
Received: by mail-io1-xd2f.google.com with SMTP id x4so13578890iog.13 for <quic@ietf.org>; Sat, 17 Aug 2019 17:02:48 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:from:date:message-id:subject:to; bh=niQz5LNnGccmLROgrdF3bIq5ogF6gsrvApa3x0qAmSs=; b=RadBqdnenpnCHuiqNJRmClETAOsGZhuejs74/oyLP8eULetyHYiA6vkyjIQrzb/w7N a9BllV+IesJ8oSTizY4kPBYGh1oyqS8ZJA4fMaVQx1LNhwYj8tXX0UDW/11xtTDnIRpB BhXrEPgBhNHFt1u4qxPeAsoQbdktIq2M8XdE5PYcZtAd4q41NQyE6FM8R5VSY4eGgMjq KitqCPFhIIizHXG8qwA0noMhZ+5FF5KJf6oaGFAXTT51Uv96Q574Y1Gxmq+y8Vk8QFvZ 9CfAJ8VXTOi1LFMnoneqRX4F89oYt8MXCJ8zQ1x/yF0eN/jovTrZGUmdqjrBa7RAzasp xTWQ==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:from:date:message-id:subject:to; bh=niQz5LNnGccmLROgrdF3bIq5ogF6gsrvApa3x0qAmSs=; b=R43ic/sc6KafEjORaQTWis/x1g7OXZqRgZVtBE50VbXdRq9+gEH/QOsVsNzOGPmj3Q A2fBB9hhZoqdWaCl5EPo9kh3BaSl4TMwibIuEgLFbhasITfEDee+WDnQmJCrghy3n4ds WEAAMVUkz738/3FQhWupwAvhpPz4K6Ved4vlF41pQkYNZqt8hq955DpQYxodfOsBbP/u /rr2JkM8Ga9rC5FdimvrslqswRuiJbAHtr3+EhX+ycwljD3HV5qMXxggi4/2wSE7hXnl tGjIdZgRl+dR2cQGu4BgbCsx01v85SOOPu5IkTzz2KHZyQdoA2VZiZ1SQjBZfMYmioaa 1DpQ==
X-Gm-Message-State: APjAAAWEk48sNq/kYTuNfNteLIrEK9WcsNyyegg02ZjQ/ZcUiRW2EiMw orxnYGRt6FnALzsXwcD+hs72rKqP5WOiuLS27NTTYpJ8
X-Google-Smtp-Source: APXvYqx2NEMCQfx/jyJkhKbkHPS32pnIh+CG6Ur2aaiAIqa47IqUlNBhERbKfdEq/m0C0iMctvPUa+PBNtXw9U53oNU=
X-Received: by 2002:a5e:c247:: with SMTP id w7mr15992509iop.72.1566086567815; Sat, 17 Aug 2019 17:02:47 -0700 (PDT)
MIME-Version: 1.0
Received: by 2002:ac0:a3c1:0:0:0:0:0 with HTTP; Sat, 17 Aug 2019 17:02:47 -0700 (PDT)
From: JH <jupiter.hce@gmail.com>
Date: Sun, 18 Aug 2019 10:02:47 +1000
Message-ID: <CAA=hcWQ2dPNcktjNMQBE8ovj1xyEOtBgE8S2qBuRz832R=7d6w@mail.gmail.com>
Subject: QUIC for IoT embeddeds system
To: IETF QUIC WG <quic@ietf.org>
Content-Type: text/plain; charset="UTF-8"
Archived-At: <https://mailarchive.ietf.org/arch/msg/quic/9E3g7GTmYjotXdSrDmo55C4w87Y>
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 00:02:50 -0000

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.23.0 | Report a Bug | By Email