Re: [Danish] Charter Text and the Problem Statement

Michael Richardson <mcr+ietf@sandelman.ca> Sun, 20 June 2021 21:41 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 257813A12CD for <danish@ietfa.amsl.com>; Sun, 20 Jun 2021 14:41:42 -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 zySJ6xosvFEN for <danish@ietfa.amsl.com>; Sun, 20 Jun 2021 14:41:37 -0700 (PDT)
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 3C9833A12CA for <danish@ietf.org>; Sun, 20 Jun 2021 14:41:37 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by tuna.sandelman.ca (Postfix) with ESMTP id 13B5B38AE6; Sun, 20 Jun 2021 17:43:06 -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 eEae3VWkWxlo; Sun, 20 Jun 2021 17:43:02 -0400 (EDT)
Received: from sandelman.ca (obiwan.sandelman.ca [209.87.249.21]) by tuna.sandelman.ca (Postfix) with ESMTP id 50B3F38AE3; Sun, 20 Jun 2021 17:43:02 -0400 (EDT)
Received: from localhost (localhost [IPv6:::1]) by sandelman.ca (Postfix) with ESMTP id D244418B; Sun, 20 Jun 2021 17:41:31 -0400 (EDT)
From: Michael Richardson <mcr+ietf@sandelman.ca>
To: Hannes Tschofenig <Hannes.Tschofenig@arm.com>
cc: "danish@ietf.org" <danish@ietf.org>
In-Reply-To: <DBBPR08MB591546610B09B3606721EF2CFA0B9@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> <23295.1624134481@localhost> <DBBPR08MB591546610B09B3606721EF2CFA0B9@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: Sun, 20 Jun 2021 17:41:31 -0400
Message-ID: <5631.1624225291@localhost>
Archived-At: <https://mailarchive.ietf.org/arch/msg/danish/UnLJAh1xAaU6juDB09mQ9CmyqdQ>
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: Sun, 20 Jun 2021 21:41:42 -0000

Hannes Tschofenig <Hannes.Tschofenig@arm.com> wrote:
    > You mention "EAP-TEAP-BRSKI", another technology where I do not
    > precisely know how it is supposed to fit into the DANISH work (if at
    > all).

It isn't.  The point is that there is work in EAP to do onboarding.
If you use DANISH, then you don't need to onboard the device (i.e. enroll it
with a new certificate), because you already have secure access to the
correct certificate via DNS(SEC).

    > I started with a simple task: I read through the charter text. I didn't
    > understood the problem statement. Then, I looked through the mailing
    > list and at the slides presented at the last meeting. I can find a lot
    > of solution discussions but little discussion about the problem.

Fair enough.  I agree that we need improvements in the charter text, and I
appreciate your comments.

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