Re: [Anima] I-D Action: draft-ietf-anima-grasp-distribution-07.txt

Michael Richardson <mcr+ietf@sandelman.ca> Wed, 15 March 2023 15:04 UTC

Return-Path: <mcr+ietf@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 DB01EC151527 for <anima@ietfa.amsl.com>; Wed, 15 Mar 2023 08:04:32 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.899
X-Spam-Level:
X-Spam-Status: No, score=-6.899 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_HI=-5, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
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 D-hi5NjQj8Sk for <anima@ietfa.amsl.com>; Wed, 15 Mar 2023 08:04:32 -0700 (PDT)
Received: from relay.sandelman.ca (relay.cooperix.net [176.58.120.209]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 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 09D20C14CE4B for <anima@ietf.org>; Wed, 15 Mar 2023 08:04:31 -0700 (PDT)
Received: from dyas.sandelman.ca (ip-185-104-136-29.ptr.icomera.net [185.104.136.29]) by relay.sandelman.ca (Postfix) with ESMTPS id 6C1151F47D; Wed, 15 Mar 2023 15:04:29 +0000 (UTC)
Received: by dyas.sandelman.ca (Postfix, from userid 1000) id 390F1A10BC; Wed, 15 Mar 2023 11:04:27 -0400 (EDT)
Received: from dyas (localhost [127.0.0.1]) by dyas.sandelman.ca (Postfix) with ESMTP id 36D61A013E; Wed, 15 Mar 2023 15:04:27 +0000 (GMT)
From: Michael Richardson <mcr+ietf@sandelman.ca>
To: Sheng Jiang <shengjiang@bupt.edu.cn>, anima <anima@ietf.org>
In-reply-to: <898731B9CC4085C7+2023031516010246054441@bupt.edu.cn>
References: <167844143207.23755.11725832079832244761@ietfa.amsl.com>, <CBA602EFBB994C74+2023031311493839883724@bupt.edu.cn>, <2347296.1678702970@dyas>, <2470030.1678797688@dyas> <898731B9CC4085C7+2023031516010246054441@bupt.edu.cn>
Comments: In-reply-to "Sheng Jiang" <shengjiang@bupt.edu.cn> message dated "Wed, 15 Mar 2023 16:01:03 +0800."
X-Mailer: MH-E 8.6+git; nmh 1.7+dev; GNU Emacs 26.3
MIME-Version: 1.0
Content-Type: multipart/signed; boundary="=-=-="; micalg="pgp-sha512"; protocol="application/pgp-signature"
Date: Wed, 15 Mar 2023 15:04:27 +0000
Message-ID: <2570486.1678892667@dyas>
Archived-At: <https://mailarchive.ietf.org/arch/msg/anima/jGXv1_pQvqKm0ZdBOETVqGFhpE0>
Subject: Re: [Anima] I-D Action: draft-ietf-anima-grasp-distribution-07.txt
X-BeenThere: anima@ietf.org
X-Mailman-Version: 2.1.39
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: Wed, 15 Mar 2023 15:04:33 -0000

Sheng Jiang <shengjiang@bupt.edu.cn> wrote:
    > I actually agree your observation on the supportiveness of use case
    > section. We were discussing to move use cases section into
    > appendix. Overall, use cases here are not necessary or as a MUST. What
    > we should focus on is the validity of technical requirements on Section
    > 4. If yes, infrastructure would be used when it is ready and good
    > enough to be used.

1) The use cases motivate doing the work.
2) The use cases tell us something about the threat/risk/benefit of the
   environment, and inform the reviewer what assumptions have been made.

So moving them into an appendix just makes it harder to understand what
problem you are trying to solve.  It also obscures that some of the use cases
are not really credible.

Instead, I suggest:
 a) pick a specific use case (firmware update?) and implement it.
 b) talk about that implementation, and see if any of the proposed other
 users are interested in the solution.

Otherwise, my advice to the chairs is that there is no audience for this
innovation, and we should not go through the expense/effort of publishing it.

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