[Dance] templates for dancing instructions

Michael Richardson <mcr+ietf@sandelman.ca> Thu, 19 January 2023 17:54 UTC

Return-Path: <mcr+ietf@sandelman.ca>
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 02D09C151546 for <dance@ietfa.amsl.com>; Thu, 19 Jan 2023 09:54:14 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.397
X-Spam-Level:
X-Spam-Status: No, score=-4.397 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, RCVD_IN_DNSWL_MED=-2.3, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_DBL_BLOCKED_OPENDNS=0.001, URIBL_ZEN_BLOCKED_OPENDNS=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 ([50.223.129.194]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id re8RvpQZ-Una for <dance@ietfa.amsl.com>; Thu, 19 Jan 2023 09:54:10 -0800 (PST)
Received: from tuna.sandelman.ca (tuna.sandelman.ca [IPv6:2607:f0b0:f:3:216:3eff:fe7c:d1f3]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 1E3EAC15153E for <dance@ietf.org>; Thu, 19 Jan 2023 09:54:09 -0800 (PST)
Received: from localhost (localhost [127.0.0.1]) by tuna.sandelman.ca (Postfix) with ESMTP id 026E53898E for <dance@ietf.org>; Thu, 19 Jan 2023 13:23:21 -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 NjRpJRV5qD6r for <dance@ietf.org>; Thu, 19 Jan 2023 13:23:20 -0500 (EST)
Received: from sandelman.ca (obiwan.sandelman.ca [209.87.249.21]) by tuna.sandelman.ca (Postfix) with ESMTP id 487403898D for <dance@ietf.org>; Thu, 19 Jan 2023 13:23:20 -0500 (EST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=sandelman.ca; s=mail; t=1674152600; bh=9eh/4hDsjOeDDhSYsZKlX5AtvKNJZfSWLMl4E7+N1Ww=; h=From:To:Subject:Date:From; b=t90u129N202AwnMZzUNUlCPIHFIUyffgm/yf0ltIyxincKiD43eZojHK4nmkxE23J zeDFiVaihDaNX3XqlgbcbmfavgeklqM6ypjSon5uvFpnbBCioOV9niVJZuEvg8svlX 79Nyo64YrAG68cakE9rD/+rpBt1bGzGJTBA03gWA9W4pXYaYwReD1zaMPfOfyoELAC KB207DigcWHeLg9TYstN5xIZ5MFBHnowZcZpz6XBMfpvmZ6Hzpx00WIgQTZYpTUi7x +pZWyV5sMPYmtUXkmuAhzOSoS2nIzzZQisSkQ2R6P/ir5rd4R6ZWOVJoFVHhwerBml TNfVLfCyAclqg==
Received: from localhost (localhost [IPv6:::1]) by sandelman.ca (Postfix) with ESMTP id E83F717A for <dance@ietf.org>; Thu, 19 Jan 2023 12:54:06 -0500 (EST)
From: Michael Richardson <mcr+ietf@sandelman.ca>
To: dance@ietf.org
X-Attribution: mcr
X-Mailer: MH-E 8.6+git; nmh 1.7+dev; GNU Emacs 27.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: Thu, 19 Jan 2023 12:54:06 -0500
Message-ID: <12892.1674150846@localhost>
Archived-At: <https://mailarchive.ietf.org/arch/msg/dance/_5xSgml0z5QmiaEEIGX33yOZGxE>
Subject: [Dance] templates for dancing instructions
X-BeenThere: dance@ietf.org
X-Mailman-Version: 2.1.39
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: Thu, 19 Jan 2023 17:54:14 -0000

Hi, the DANCE architecture design team has been meeting on Monday ("mornings"
for me) to complete the contents of the architecture document.  We will post
a revision to the DT on Monday for Thursday's virtual interim, but you can
also follow changes in github.

We have a series of questions for the WG about the contents, and changes.

The WG chairs hava arrange for all the active documents to move to:
  https://github.com/ietf-wg-dance/

What I hope to do next is to write a series of small "DANCing" documents that
explain in normative detail how to use DANE for client authentication in a
number of target uses.  This requires protocol specific knowledge, and
protocol specific applications of DANE.   To reduce the effort and make sure
that the documents answer all important questions in a consistent way, we
have created a template document.
(I did this in the ROLL WG with the 4-5 applicability statements that we
needed. See:
https://datatracker.ietf.org/doc/draft-ietf-roll-applicability-template/ )

This template has been totally roughed at:
  https://github.com/ietf-wg-dance/draft-ietf-dance-dancing-template

It needs revision, and probably some text should be removed.

DANCers, what I'd like to do is to beat this template up a bit, and then have
the WG do an adoption call on it.  BUT, this document would NEVER be published!!!
It would serve as a template for all other dancing instructions.

__It probably won't be much more than a table of contents__ (and list of references).

What would be great is if there are a few DANCErs that could help work on
this document.

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