Re: [Dance] Robert Wilton's No Objection on charter-ietf-dance-00-01: (with COMMENT)

Wes Hardaker <wjhns1@hardakers.net> Wed, 08 September 2021 14:31 UTC

Return-Path: <wjhns1@hardakers.net>
X-Original-To: dance@ietfa.amsl.com
Delivered-To: dance@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 139E23A1F87; Wed, 8 Sep 2021 07:31:06 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.899
X-Spam-Level:
X-Spam-Status: No, score=-1.899 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, 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 B49eaPFG9fLY; Wed, 8 Sep 2021 07:31:00 -0700 (PDT)
Received: from mail.hardakers.net (mail.hardakers.net [168.150.192.181]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 66CB23A2A2B; Wed, 8 Sep 2021 07:31:00 -0700 (PDT)
Received: from localhost (unknown [10.0.0.3]) by mail.hardakers.net (Postfix) with ESMTPA id 3E739234B4; Wed, 8 Sep 2021 07:30:55 -0700 (PDT)
From: Wes Hardaker <wjhns1@hardakers.net>
To: Robert Wilton via Datatracker <noreply@ietf.org>
Cc: "The IESG" <iesg@ietf.org>, Robert Wilton <rwilton@cisco.com>, dance-chairs@ietf.org, dance@ietf.org
References: <163110591083.990.12493531700395844407@ietfa.amsl.com>
Date: Wed, 08 Sep 2021 07:30:55 -0700
In-Reply-To: <163110591083.990.12493531700395844407@ietfa.amsl.com> (Robert Wilton via Datatracker's message of "Wed, 08 Sep 2021 05:58:31 -0700")
Message-ID: <ybl35qff8bk.fsf@w7.hardakers.net>
User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/27.2 (gnu/linux)
MIME-Version: 1.0
Content-Type: text/plain
Archived-At: <https://mailarchive.ietf.org/arch/msg/dance/YyrLbacaiR_CTbEwb9nRKsZqjBE>
Subject: Re: [Dance] Robert Wilton's No Objection on charter-ietf-dance-00-01: (with COMMENT)
X-BeenThere: dance@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: DANE Authentication for Network Clients Everywhere <dance.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dance>, <mailto:dance-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/dance/>
List-Post: <mailto:dance@ietf.org>
List-Help: <mailto:dance-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dance>, <mailto:dance-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 08 Sep 2021 14:31:07 -0000

Robert Wilton via Datatracker <noreply@ietf.org> writes:

> I'm wondering whether restricting the initial use case to TLS client only will
> limit its usefulness in IOT onboarding?

This comes from the discussions in the BOF where there was concern that
the problem space was too large, because a lot of future follow-on
efforts were discussed.  The result is that we agreed that we should
start with just the client side only, and change the charter after we
achieved success with the single (but not necessarily trivial) starting
problem.

> Para 3:
> "DANE builds on" => "DANE built on"?  Or otherwise perhaps change "DANE did
> not" to "the DANE WG did not".
> 
> Para 4:
> "large deployment" => "large deployments"?

Accepted in my local copy ()

> Are the milestone dates correct (i.e., the architecture and use cases is
> expected to be standardized after the solution)?

Good point, they were supposed to be "after architecture".  I've changed
my copy to indicate just that.

https://github.com/hardaker/danish-bof/blob/main/charter.md
-- 
Wes Hardaker
USC/ISI