Re: [Lwip] [T2TRG] QUIC on IoT boards

"David R. Oran" <daveoran@orandom.net> Mon, 20 January 2020 14:02 UTC

Return-Path: <daveoran@orandom.net>
X-Original-To: lwip@ietfa.amsl.com
Delivered-To: lwip@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 0C56E120132; Mon, 20 Jan 2020 06:02:02 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.9
X-Spam-Level:
X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, SPF_HELO_NONE=0.001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
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 weATujPSm5Mf; Mon, 20 Jan 2020 06:01:57 -0800 (PST)
Received: from spark.crystalorb.net (spark.crystalorb.net [IPv6:2607:fca8:1530::c]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 3C84D12013F; Mon, 20 Jan 2020 06:01:57 -0800 (PST)
Received: from [192.168.15.102] ([IPv6:2601:184:407f:80ce:3498:cbc1:44fd:d28c]) (authenticated bits=0) by spark.crystalorb.net (8.14.4/8.14.4/Debian-4+deb7u1) with ESMTP id 00KE1ZAk031768 (version=TLSv1/SSLv3 cipher=AES256-GCM-SHA384 bits=256 verify=NO); Mon, 20 Jan 2020 06:01:37 -0800
From: "David R. Oran" <daveoran@orandom.net>
To: Eliot Lear <elear@cisco.com>
Cc: Lars Eggert <lars@eggert.org>, lwip@ietf.org, t2trg@irtf.org
Date: Mon, 20 Jan 2020 09:01:30 -0500
X-Mailer: MailMate (1.13.1r5676)
Message-ID: <FE3955D6-6026-4800-BC34-7CE923843841@orandom.net>
In-Reply-To: <E7C38177-DD0B-4D92-AE0E-EB457691E493@cisco.com>
References: <6CB4D459-4AAA-4313-B95C-05DF22C9A9DD@eggert.org> <E7C38177-DD0B-4D92-AE0E-EB457691E493@cisco.com>
MIME-Version: 1.0
Content-Type: text/plain; charset="UTF-8"; format="flowed"
Content-Transfer-Encoding: 8bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/lwip/1QNSpIg2LMdjviXj2_h24szYXTE>
Subject: Re: [Lwip] [T2TRG] QUIC on IoT boards
X-BeenThere: lwip@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: "Lightweight IP stack. Official mailing list for IETF LWIG Working Group." <lwip.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/lwip>, <mailto:lwip-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/lwip/>
List-Post: <mailto:lwip@ietf.org>
List-Help: <mailto:lwip-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/lwip>, <mailto:lwip-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 20 Jan 2020 14:02:02 -0000

On 20 Jan 2020, at 8:45, Eliot Lear (elear) wrote:

> Hi Lars,
>
> A fundamental question to ask is whether which IoT uses QUIC is 
> appropriate for and which ones it is not.  For example, obscuring port 
> information on an industrial device – not to mention encrypting 
> communications – might actually cause more harm than good if the 
> result is an inability to audit industrial automation behavior.  As 
> in: why did that signal turn green that caused two trains to collide?
>
It would be helpful to distinguish auditing from surveillance. It’s ok 
for auditing to require the cooperation of the audited entities. That 
cooperation could, for example, involve the controlled sharing of keys. 
Eliot does raise a good point, in that auditing may be very hard if keys 
and cypher suites with PFS are chosen.

> Be careful what you wish for.  You may not like the results.
>
> Eliot
>
>> On 20 Jan 2020, at 09:24, Lars Eggert <lars@eggert.org> wrote:
>>
>> Signed PGP part
>> Hi,
>>
>> I wrote up my experiences of getting QUIC to run on some IoT boards 
>> for the NDSS DISS workshop. Feedback welcome!
>>
>> Towards Securing the Internet of Things with QUIC. Lars Eggert. Proc. 
>> NDSS Workshop on Decentralized IoT Systems and Security (DISS), San 
>> Diego, CA, USA, February 23, 2020. 
>> https://eggert.org/papers/2020-ndss-quic-iot.pdf
>>
>> Would be happy to chat about this more, possibly in Vancouver?
>>
>> Thanks,
>> Lars
>>
>>
>>
>
> _______________________________________________
> T2TRG mailing list
> T2TRG@irtf.org
> https://www.irtf.org/mailman/listinfo/t2trg

DaveO