Re: [Anima] [Gen-art] dealing with many the secdir and genart comments [on draft-ietf-anima-bootstrapping-keyinfra]

Michael Richardson <mcr+ietf@sandelman.ca> Mon, 03 December 2018 09:23 UTC

Return-Path: <mcr@sandelman.ca>
X-Original-To: anima@ietfa.amsl.com
Delivered-To: anima@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id A85AD130E2A for <anima@ietfa.amsl.com>; Mon, 3 Dec 2018 01:23:35 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.901
X-Spam-Level:
X-Spam-Status: No, score=-1.901 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, SPF_PASS=-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 56g_8OuM3bTP for <anima@ietfa.amsl.com>; Mon, 3 Dec 2018 01:23:34 -0800 (PST)
Received: from relay.sandelman.ca (relay.cooperix.net [176.58.120.209]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id DAB74126C01 for <anima@ietf.org>; Mon, 3 Dec 2018 01:23:33 -0800 (PST)
Received: from dooku.sandelman.ca (unknown [IPv6:2a02:c7d:b752:2f00:c3eb:b5be:80ee:7c56]) by relay.sandelman.ca (Postfix) with ESMTPS id A2C311F8BD; Mon, 3 Dec 2018 09:23:31 +0000 (UTC)
Received: by dooku.sandelman.ca (Postfix, from userid 179) id B82251704; Mon, 3 Dec 2018 09:22:59 +0000 (GMT)
From: Michael Richardson <mcr+ietf@sandelman.ca>
To: Brian E Carpenter <brian.e.carpenter@gmail.com>
cc: anima@ietf.org
In-reply-to: <f6002a83-b292-b323-04ee-d0d26acdd782@gmail.com>
References: <153826253306.18743.9250084704876465818@ietfa.amsl.com> <153874289877.989.15433226866680411112@ietfa.amsl.com> <24358.1543530974@dooku.sandelman.ca> <0b517731-ef11-4484-7bf8-46e313a2ac49@gmail.com> <24016.1543794827@dooku.sandelman.ca> <f6002a83-b292-b323-04ee-d0d26acdd782@gmail.com>
Comments: In-reply-to Brian E Carpenter <brian.e.carpenter@gmail.com> message dated "Mon, 03 Dec 2018 13:06:33 +1300."
X-Mailer: MH-E 8.6; nmh 1.6; GNU Emacs 24.5.1
MIME-Version: 1.0
Content-Type: multipart/signed; boundary="=-=-="; micalg="pgp-sha256"; protocol="application/pgp-signature"
Date: Mon, 03 Dec 2018 09:22:59 -0000
Message-ID: <10330.1543828979@dooku.sandelman.ca>
Archived-At: <https://mailarchive.ietf.org/arch/msg/anima/3u4BiwdrGz_CJVOBMUuW00Hbkao>
Subject: Re: [Anima] [Gen-art] dealing with many the secdir and genart comments [on draft-ietf-anima-bootstrapping-keyinfra]
X-BeenThere: anima@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Autonomic Networking Integrated Model and Approach <anima.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/anima>, <mailto:anima-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/anima/>
List-Post: <mailto:anima@ietf.org>
List-Help: <mailto:anima-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/anima>, <mailto:anima-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 03 Dec 2018 09:23:36 -0000

Brian E Carpenter <brian.e.carpenter@gmail.com> wrote:
    >> Brian E Carpenter <brian.e.carpenter@gmail.com> wrote:
    >> >> The authors seriously believe that this will result in an attempt to
    >> >> boil the ocean.  Yes, BRSKI is exciting for many and opens many doors,
    >> >> but in the context of the *ANIMA* Charter, we strongly think that this
    >> >> document should leave the oceans alone, and deal only with the ANIMA
    >> >> ACP usage.
    >> 
    >> > Yes, violent agreement. From all the interest outside ANIMA, the basic
    >> > idea of BRSKI is a big hit and will be re-used in other contexts. I
    >> > think a strong statement about the specific scope of *this* document
    >> > belongs in the Abstract and Introduction, with a comment that variant
    >> > usages of BRSKI in other scenarios will be documented separately.
    >> 
    >> Brian, these are my proposed changes to the abstract, intro,
    >> and adding a section on ACP Applicability.  I think that there is probably
    >> more to say there.

    > Perhaps, but I think these changes clarify the scope correctly.

My sense in writing the words was that there were more words needed.
But I didn't know what else I could nail down scope-wise, so I stopped.

-- 
Michael Richardson <mcr+IETF@sandelman.ca>, Sandelman Software Works
 -= IPv6 IoT consulting =-