Content-Type: text/plain;
	charset=utf-8
Mime-Version: 1.0 (Mac OS X Mail 11.5 \(3445.9.1\))
From: =?utf-8?B?0JLQsNGB0LjQu9C40Lkg0JTQvtC70LzQsNGC0L7Qsg==?=
 <vdolmatov@gmail.com>
In-Reply-To: <E7C38177-DD0B-4D92-AE0E-EB457691E493@cisco.com>
Date: Mon, 20 Jan 2020 17:09:51 +0300
Cc: Lars Eggert <lars@eggert.org>, "lwip@ietf.org" <lwip@ietf.org>,
 "t2trg@irtf.org" <t2trg@irtf.org>
Content-Transfer-Encoding: quoted-printable
Message-Id: <6B9FFEF5-CDC9-4703-BB10-616DBEDE80AB@gmail.com>
References: <6CB4D459-4AAA-4313-B95C-05DF22C9A9DD@eggert.org>
 <E7C38177-DD0B-4D92-AE0E-EB457691E493@cisco.com>
To: "Eliot Lear (elear)" <elear@cisco.com>
Archived-At: <https://mailarchive.ietf.org/arch/msg/lwip/txzbEiXiwxqj9SJzTvCbOywLlmw>
Subject: Re: [Lwip] [T2TRG] QUIC on IoT boards
Precedence: list



> 20 =D1=8F=D0=BD=D0=B2. 2020 =D0=B3., =D0=B2 16:45, Eliot Lear (elear) =
<elear@cisco.com> =D0=BD=D0=B0=D0=BF=D0=B8=D1=81=D0=B0=D0=BB(=D0=B0):
>=20
> Hi Lars,
>=20
> 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 =E2=80=93 not to mention encrypting =
communications =E2=80=93 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?

absence of encryption can cause that sudden =C2=ABgreen signal=C2=BB be =
created by joking school pupils.

>=20
> Be careful what you wish for.  You may not like the results.
>=20
> Eliot
>=20