Re: [Dance] templates for dancing instructions

joeygsal <joeygsal@gmail.com> Tue, 24 January 2023 22:20 UTC

Return-Path: <joeygsal@gmail.com>
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 A89A9C16950F for <dance@ietfa.amsl.com>; Tue, 24 Jan 2023 14:20:37 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.095
X-Spam-Level:
X-Spam-Status: No, score=-2.095 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, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, 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=gmail.com
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 dgZSfV-Qi9Vz for <dance@ietfa.amsl.com>; Tue, 24 Jan 2023 14:20:37 -0800 (PST)
Received: from mail-wm1-x32a.google.com (mail-wm1-x32a.google.com [IPv6:2a00:1450:4864:20::32a]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits) server-digest SHA256) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 092B9C169518 for <dance@ietf.org>; Tue, 24 Jan 2023 14:20:36 -0800 (PST)
Received: by mail-wm1-x32a.google.com with SMTP id k16so12522946wms.2 for <dance@ietf.org>; Tue, 24 Jan 2023 14:20:36 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20210112; h=mime-version:to:from:importance:in-reply-to:subject:date :savedfromemail:message-id:from:to:cc:subject:date:message-id :reply-to; bh=IELi+RwczvoiN1y2fRrw0sqZo7hj6I464fwjhvsiWj8=; b=AGsCQTR1nTQ3OoekR25RdFrPLpHjLorJ2VEa7D7eg/flke2Q9gxn9mbdnHdF4xdcjJ pZUi12InmfUGYn6vffJWtmIkhqpjH+kazWdHC1cE7yqGv1zAcccy9FbgBIoes1laM7Kw BhegkwXCoHtA/Fi/evlR1YDxj/rJnSmvC0iDJ7TZsaVZafCdDgpK77yc2aFZtCNmh9QR MgKl2MAw4YPOh+L3kO+9Q+GmKoD9Lue+Tej1ol8BlGsh+0f70OffHRhWZN3/afqWW4Oi KVqzBhQb1TPNUHsqWF3LIGJlSE2etr1QRSS+WnkyTNhfcyoB6VVqoo3GbKzjJ5X2f2Zh 6DbQ==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=mime-version:to:from:importance:in-reply-to:subject:date :savedfromemail:message-id:x-gm-message-state:from:to:cc:subject :date:message-id:reply-to; bh=IELi+RwczvoiN1y2fRrw0sqZo7hj6I464fwjhvsiWj8=; b=jS+JM/Glp7oP2KIUk+7ggtjJV4BlXT/rFcA//FVgAoMfW2+YEr6cWJwqWkuaIznFrd gsMco+0DU8Bx/m6M4nUJ1cE65d+gEzHQYAoJ7e8y563L8+8Ml/yRvWUbxqrjETFlrupD wFbhFDrOY09HZYres8Ta5yKa7tpWnrjv+Hvz5hkKquzlE00aMlJsPl8+Zx5xSrj7a1Pt hOmTDrnTgiAhP0ra36h+3VyQcyLDMZSOg+tiV3+J47ybExLeE6mN8W2J6fUEsOoflAM/ +/da97jdqjm1XnDc9+TBnLbPEQr8RneboMJL1aZjXsZVjk7ILzyOC9LohwKKTaO/HdVQ orOw==
X-Gm-Message-State: AFqh2kpJorT2mBjOx5G7D1t8qUjymCVDZPTLkjaZknICC//ftxfNHrA1 951n6X7Q1wmGW2MH3oPSQkI=
X-Google-Smtp-Source: AMrXdXtSF1hjkJ5uj9oAvf+wMWon1ksoG28lcI2h5WBy0PbVH6tKkDUKzysyHgL+0RdCpDRQOza97w==
X-Received: by 2002:a05:600c:304a:b0:3d9:8635:a916 with SMTP id n10-20020a05600c304a00b003d98635a916mr30759407wmh.9.1674598835079; Tue, 24 Jan 2023 14:20:35 -0800 (PST)
Received: from [192.168.0.17] (62.174.143.5.static.user.ono.com. [62.174.143.5]) by smtp.gmail.com with ESMTPSA id p10-20020a05600c430a00b003dc0d5b4f75sm26147wme.43.2023.01.24.14.20.33 (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128); Tue, 24 Jan 2023 14:20:33 -0800 (PST)
Message-ID: <63d059b1.050a0220.42f3b.00ed@mx.google.com>
SavedFromEmail: joeygsal@gmail.com
Date: Tue, 24 Jan 2023 23:20:14 +0100
In-Reply-To: <12892.1674150846@localhost>
Importance: normal
From: joeygsal <joeygsal@gmail.com>
To: Michael Richardson <mcr+ietf@sandelman.ca>, dance@ietf.org
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="--_com.samsung.android.email_15340590191903710"
Archived-At: <https://mailarchive.ietf.org/arch/msg/dance/klFm5QBotUcGLUmjeofn_7drDL8>
Subject: Re: [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: Tue, 24 Jan 2023 22:20:37 -0000

Hi Michael, DANCE,Thank you for this, answering critical questions from the beginning will definitely help at different stages of writing and developing DANCE documents.DANCErs, your input here will help authors as they work on new and ongoing drafts. Please review!See you soon at the interim,--Joey
-------- Original message --------From: Michael Richardson <mcr+ietf@sandelman.ca> Date: 1/19/23  6:54 PM  (GMT+01:00) To: dance@ietf.org Subject: [Dance] templates for dancing instructions Hi, the DANCE architecture design team has been meeting on Monday ("mornings"for me) to complete the contents of the architecture document.  We will posta revision to the DT on Monday for Thursday's virtual interim, but you canalso 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 thatexplain in normative detail how to use DANE for client authentication in anumber of target uses.  This requires protocol specific knowledge, andprotocol specific applications of DANE.   To reduce the effort and make surethat the documents answer all important questions in a consistent way, wehave created a template document.(I did this in the ROLL WG with the 4-5 applicability statements that weneeded. 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-templateIt 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 havethe 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 onthis document.--Michael Richardson <mcr+IETF@sandelman.ca>   . o O ( IPv6 IøT consulting )           Sandelman Software Works Inc, Ottawa and Worldwide