IETF Logo Mail Archive

Re: [Danish] Charter Text and the Problem Statement

Michael Richardson <mcr+ietf@sandelman.ca> Sat, 19 June 2021 20:28 UTC

Return-Path: <mcr+ietf@sandelman.ca>
X-Original-To: danish@ietfa.amsl.com
Delivered-To: danish@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 598CF3A1F0C for <danish@ietfa.amsl.com>; Sat, 19 Jun 2021 13:28:10 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.001
X-Spam-Level:
X-Spam-Status: No, score=0.001 tagged_above=-999 required=5 tests=[SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=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 vkua08t2XNeN for <danish@ietfa.amsl.com>; Sat, 19 Jun 2021 13:28:05 -0700 (PDT)
Received: from tuna.sandelman.ca (tuna.sandelman.ca [IPv6:2607:f0b0:f:3:216:3eff:fe7c:d1f3]) (using TLSv1.2 with cipher ADH-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 776273A1F0A for <danish@ietf.org>; Sat, 19 Jun 2021 13:28:05 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by tuna.sandelman.ca (Postfix) with ESMTP id 3985038BC0; Sat, 19 Jun 2021 16:29:30 -0400 (EDT)
Received: from tuna.sandelman.ca ([127.0.0.1]) by localhost (localhost [127.0.0.1]) (amavisd-new, port 10024) with LMTP id hWUrze8QoWG9; Sat, 19 Jun 2021 16:29:28 -0400 (EDT)
Received: from sandelman.ca (obiwan.sandelman.ca [IPv6:2607:f0b0:f:2::247]) by tuna.sandelman.ca (Postfix) with ESMTP id D1E5038BA5; Sat, 19 Jun 2021 16:29:27 -0400 (EDT)
Received: from localhost (localhost [IPv6:::1]) by sandelman.ca (Postfix) with ESMTP id BE0C8B75; Sat, 19 Jun 2021 16:28:01 -0400 (EDT)
From: Michael Richardson <mcr+ietf@sandelman.ca>
To: Hannes Tschofenig <Hannes.Tschofenig@arm.com>, "danish@ietf.org" <danish@ietf.org>
In-Reply-To: <DBBPR08MB5915C107E3620968DFE34D97FA0C9@DBBPR08MB5915.eurprd08.prod.outlook.com>
References: <DBBPR08MB5915066E1CE5BDB2D695A8DAFA0F9@DBBPR08MB5915.eurprd08.prod.outlook.com> <CAEfM=vQehhvSNeBNitJJjisEbimn_gizoo8VTtHWUJ1zSU+rQg@mail.gmail.com> <DBBPR08MB5915D8FC201DFEB31F7D8EA8FA0E9@DBBPR08MB5915.eurprd08.prod.outlook.com> <CAEfM=vTHPmDcOimf9xOvkYgeObbHvpfG1uZUVjBJFhykrZNafg@mail.gmail.com> <DBBPR08MB5915C107E3620968DFE34D97FA0C9@DBBPR08MB5915.eurprd08.prod.outlook.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, 19 Jun 2021 16:28:01 -0400
Message-ID: <23295.1624134481@localhost>
Archived-At: <https://mailarchive.ietf.org/arch/msg/danish/SBfHHgC9TjDmZ1s2whw8yqcq1TQ>
Subject: Re: [Danish] Charter Text and the Problem Statement
X-BeenThere: danish@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: DANE AutheNtication for Iot Service Hardening <danish.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/danish>, <mailto:danish-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/danish/>
List-Post: <mailto:danish@ietf.org>
List-Help: <mailto:danish-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/danish>, <mailto:danish-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 19 Jun 2021 20:28:10 -0000

Hannes Tschofenig <Hannes.Tschofenig@arm.com> wrote:
    > Regarding “best practice to ensure that a device is patched before
    > putting it into production, and updating roots of trust fits within the
    > scope of that sort of activity”: I don’t think there is any expectation
    > that the device will be updated before it is put in production
    > (i.e. powered on for the first time). You can assume that the device,
    > when it comes online for the first time and reaches out to the device
    > management server, gets a firmware update. Having that firmware update
    > happen before it is connected to the network is extremely unlikely.

One can onboard onto a quarantine network on which firmware updates can
occur, and then move to the production network.

    > EAP-TLS is also not an IoT device onboarding protocol. From the charter
    > text I am also not assuming that you are attempting to define a new IoT
    > onboarding protocol or do you?

Yes, but several people are trying to do EAP-TEAP-BRSKI.

    > I am still trying to figure out how DANISH fits into the larger picture
    > and hence I am looking forward to read an architecture document. Is the
    > a pre-draft available already?

I don't think so, but maybe that would be a good direction to consider.

--
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