IETF Logo Mail Archive

Re: [Iotops] [Anima] [Secdispatch] I-D: Deploying Publicly Trusted TLS Servers on IoT Devices Using SNI-based End-to-End TLS Forwarding (SNIF)

Michael Richardson <mcr+ietf@sandelman.ca> Sat, 05 March 2022 22:28 UTC

Return-Path: <mcr+ietf@sandelman.ca>
X-Original-To: iotops@ietfa.amsl.com
Delivered-To: iotops@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 07BC23A0D58; Sat, 5 Mar 2022 14:28:00 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.109
X-Spam-Level:
X-Spam-Status: No, score=-2.109 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, T_SCC_BODY_TEXT_LINE=-0.01, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=sandelman.ca
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 TTkd00A7CRPP; Sat, 5 Mar 2022 14:27:55 -0800 (PST)
Received: from tuna.sandelman.ca (tuna.sandelman.ca [209.87.249.19]) (using TLSv1.2 with cipher ADH-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 8255E3A0D51; Sat, 5 Mar 2022 14:27:53 -0800 (PST)
Received: from localhost (localhost [127.0.0.1]) by tuna.sandelman.ca (Postfix) with ESMTP id 5466638CC5; Sat, 5 Mar 2022 17:37:04 -0500 (EST)
Received: from tuna.sandelman.ca ([127.0.0.1]) by localhost (localhost [127.0.0.1]) (amavisd-new, port 10024) with LMTP id lDQ8XiIamZt2; Sat, 5 Mar 2022 17:37:00 -0500 (EST)
Received: from sandelman.ca (obiwan.sandelman.ca [IPv6:2607:f0b0:f:2::247]) by tuna.sandelman.ca (Postfix) with ESMTP id D1D3638CC3; Sat, 5 Mar 2022 17:37:00 -0500 (EST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=sandelman.ca; s=mail; t=1646519820; bh=/NRgkXE8y2KcNRMIgp3e8LwmKBeMWEh8dLr78Lv11aw=; h=From:To:Subject:In-Reply-To:References:Date:From; b=1ntN62jvxcCpFSE5ypFkzTeu2cdL1S0C/K7zWlcnPqAwN7XLmHJZRUzprWeLIr4eY MquZdek5245FlOHz0YhD3PbSxxtJk8RpnoS1f0zyHWpTCpetlCkv1n8r68vGIAfAw1 oMXlbFnuBw6PUgXAh/kmV0lUx+HsNvt3+bMC7g+zxTLr0s7SriCbX6miFdnYTCaM7I JjYlcezrzN+ThCTKgRBrWFytANEbA5CMuUA68mydzUTLmryP6kHn5TD1Y3KZ9WKSPI RRpp+n3KP7j0XDFK7Jul1+G7e0u/mAeBWWWR9kOGvHecF4SO8jvkMp4fuIfr+7qZZU GkCS9aTEZfRRg==
Received: from localhost (localhost [IPv6:::1]) by sandelman.ca (Postfix) with ESMTP id 0F8D266A; Sat, 5 Mar 2022 17:27:48 -0500 (EST)
From: Michael Richardson <mcr+ietf@sandelman.ca>
To: Eric Rescorla <ekr@rtfm.com>, "secdispatch@ietf.org" <secdispatch@ietf.org>, Jim Zubov <ietf-list@commercebyte.com>, Hannes Tschofenig <Hannes.Tschofenig@arm.com>, "anima@ietf.org" <anima@ietf.org>, "iotops@ietf.org" <iotops@ietf.org>
In-Reply-To: <CABcZeBM9sUs2cZyf8564-501p0RUve_FBvEBAd45k2RhyRbFqg@mail.gmail.com>
References: <0075B437-024A-4D84-ABD7-92FE8DAFA59F@commercebyte.com> <1865.1644434146@localhost> <E1nHwaz-0000LM-I5@ocean1.commercebyte.com> <4026.1644516168@localhost> <685366A1-01F4-4788-B025-0F5F4CE7947F@commercebyte.com> <DBBPR08MB591577EC79C3D11114AA747CFA3C9@DBBPR08MB5915.eurprd08.prod.outlook.com> <FC43EB7C-5ABF-4061-89BA-1503F0B6340D@commercebyte.com> <DBBPR08MB59159BFB36A926DA8E851723FA3D9@DBBPR08MB5915.eurprd08.prod.outlook.com> <665685D3-B9AA-4A5E-B5B0-33D313A40716@commercebyte.com> <6296.1646509436@localhost> <CABcZeBM9sUs2cZyf8564-501p0RUve_FBvEBAd45k2RhyRbFqg@mail.gmail.com>
X-Mailer: MH-E 8.6+git; nmh 1.7+dev; GNU Emacs 26.1
X-Face: $\n1pF)h^`}$H>Hk{L"x@)JS7<%Az}5RyS@k9X%29-lHB$Ti.V>2bi.~ehC0; <'$9xN5Ub# z!G,p`nR&p7Fz@^UXIn156S8.~^@MJ*mMsD7=QFeq%AL4m<nPbLgmtKK-5dC@#:k
MIME-Version: 1.0
Content-Type: multipart/signed; boundary="=-=-="; micalg="pgp-sha512"; protocol="application/pgp-signature"
Date: Sat, 05 Mar 2022 17:27:48 -0500
Message-ID: <22243.1646519268@localhost>
Archived-At: <https://mailarchive.ietf.org/arch/msg/iotops/Z4dbcF-T-Sy6v7OVUMnSJ53ltW0>
Subject: Re: [Iotops] [Anima] [Secdispatch] I-D: Deploying Publicly Trusted TLS Servers on IoT Devices Using SNI-based End-to-End TLS Forwarding (SNIF)
X-BeenThere: iotops@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: IOT Operations <iotops.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/iotops>, <mailto:iotops-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/iotops/>
List-Post: <mailto:iotops@ietf.org>
List-Help: <mailto:iotops-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/iotops>, <mailto:iotops-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 05 Mar 2022 22:28:00 -0000

Eric Rescorla <ekr@rtfm.com> wrote:
    > I provided some comments at the end of my review. Briefly, I have doubts
    > that this
    > is the best technical approach and so I think if we are to work on this
    > problem
    > we should start by working out the problem statement and requirements first.

I would agree with you.

In particular,  I think that UPnP or PCP, in combination with some kind
of dynamic DNS infrastructure, could do everything SNIF does, and do it in a
far more decentralized fashion.

So what is it that SNIF does that is truly different?

    >> Have the SECDISPATCH chairs put it on the
    >> agenda,

    > I think putting it on the SECDISPATCH agenda would be appropriate

Good.

    >> or is there any agreement that maybe IOTOPS should dispatch it?

    > I think that would be a bad idea. There's nothing really IoT-specific here.

There is often nothing IoT specific about many things.
There is however a community of people who understand the set of tradeoff in
deploying systems at large scale that have no human at the helm.

--
Michael Richardson <mcr+IETF@sandelman.ca>   . o O ( IPv6 IøT consulting )
           Sandelman Software Works Inc, Ottawa and Worldwide

v2.23.0 | Report a Bug | By Email