Re: [Danish] Charter Text and the Problem Statement

Michael Richardson <mcr+ietf@sandelman.ca> Sun, 20 June 2021 21:39 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 E25563A12C3 for <danish@ietfa.amsl.com>; Sun, 20 Jun 2021 14:39:54 -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 y1jZd0XBEu_t for <danish@ietfa.amsl.com>; Sun, 20 Jun 2021 14:39:50 -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 08C353A12C1 for <danish@ietf.org>; Sun, 20 Jun 2021 14:39:49 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by tuna.sandelman.ca (Postfix) with ESMTP id 6F41638AE6; Sun, 20 Jun 2021 17:41:17 -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 Qg87pgV4f5iO; Sun, 20 Jun 2021 17:41:15 -0400 (EDT)
Received: from sandelman.ca (obiwan.sandelman.ca [IPv6:2607:f0b0:f:2::247]) by tuna.sandelman.ca (Postfix) with ESMTP id 6294E38AA7; Sun, 20 Jun 2021 17:41:15 -0400 (EDT)
Received: from localhost (localhost [IPv6:::1]) by sandelman.ca (Postfix) with ESMTP id 62EA518B; Sun, 20 Jun 2021 17:39:45 -0400 (EDT)
From: Michael Richardson <mcr+ietf@sandelman.ca>
To: Wes Hardaker <wjhns1@hardakers.net>
cc: Ash Wilson <ash.wilson=40valimail.com@dmarc.ietf.org>, "danish@ietf.org" <danish@ietf.org>, Hannes Tschofenig <Hannes.Tschofenig@arm.com>
In-Reply-To: <yblczsg8udj.fsf@w7.hardakers.net>
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> <CAEfM=vQVK__gEjXmDpHCJiTi6wWo7ryG+cpSngnv6EfevfBDXQ@mail.gmail.com> <yblczsg8udj.fsf@w7.hardakers.net>
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:39:45 -0400
Message-ID: <5144.1624225185@localhost>
Archived-At: <https://mailarchive.ietf.org/arch/msg/danish/lE6_iM7XpB5JcU0vbOzUdZbow7w>
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:39:55 -0000

Wes Hardaker <wjhns1@hardakers.net> wrote:
    >> I'm very happy to hear that you're interested in how EAP-TLS will fit
    >> with this effort and I have no objection to including this in the
    >> charter, as long as the chairs are OK with it.

    > It does seem to me that EAP-TLS should be considered after the other
    > parts of the problem space have a good start, unless that someone has a
    > good case for why they have to be simultaneously worked on.  And there
    > is nothing wrong with making charter items that outline a series of
    > things to do.  I'd suggest that based on discussions to date, it sounds
    > like there are now three major sections, none of which are huge, to work
    > on:

    > 1. An architecture document
    > 2. Base protocol documents
    > 3. EAP-TLS and other immediate follow on items, if there are agreements
    > now this this really should be the next step (otherwise rechartering
    > when 1 and 2 are done and decide on priorities then)

I agree 100% with this approach.
I think that using EAP-TLS with client side certificates for network access
could be a really useful thing.  But, that it should come afterward as a
milestone.

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