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

Sheng Jiang <shengjiang@bupt.edu.cn> Wed, 15 March 2023 08:01 UTC

Return-Path: <shengjiang@bupt.edu.cn>
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 300A1C1524AC for <anima@ietfa.amsl.com>; Wed, 15 Mar 2023 01:01:14 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.895
X-Spam-Level:
X-Spam-Status: No, score=-1.895 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_BLOCKED=0.001, RCVD_IN_MSPIKE_H2=-0.001, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_NONE=0.001, URIBL_BLOCKED=0.001, URIBL_DBL_BLOCKED_OPENDNS=0.001, URIBL_ZEN_BLOCKED_OPENDNS=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 0yX1Z-cHfjjO for <anima@ietfa.amsl.com>; Wed, 15 Mar 2023 01:01:11 -0700 (PDT)
Received: from smtpbgau2.qq.com (smtpbgau2.qq.com [54.206.34.216]) (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 97421C1522DB for <anima@ietf.org>; Wed, 15 Mar 2023 01:01:09 -0700 (PDT)
X-QQ-mid: bizesmtp72t1678867264txl5idcn
Received: from SJ-Uni ( [223.72.42.68]) by bizesmtp.qq.com (ESMTP) with id ; Wed, 15 Mar 2023 16:01:03 +0800 (CST)
X-QQ-SSF: 01400000002000G0Z000B00A0000000
X-QQ-FEAT: 5q30pvLz2ieqhP3paWC/yZNzfyBYZwPMf0ug1CepyIevdXw6/S+pz/235JWQx VwHj/IpnUMPZWiQQmEkbkkh+e2TtGBZfmNxMJI1OQkrR1o9vd1h/zRpBhS1Z21qnFZKB2Z1 fKvjhJBLhZnlMsKmyTXrxXP5JaCaoW6POyLh3gxyzu/zb+6RoJaHSPlF8XRYHkiJEi/Arud ZonMguSjvuzBuSFxSuTv6hlZcwXuwRo+nVBTx+/ddDuHM6i/+uEmds9OBoeqf0AKSiYh27E xnrMzO+HgN2AqPyjNA5i2RXniEB3liP+1Xweu9hMt7Sgv/issXh14nIifB90TZuBauEvR9X eWr9BS/BzyLKSrW72Kov7DcUZ63X2NqK4IQR8CFIBy9R3fAAb9Z0ej8X7ygnVwV8DtYUGyk FnA8NGd8qAs=
X-QQ-GoodBg: 2
Date: Wed, 15 Mar 2023 16:01:03 +0800
From: Sheng Jiang <shengjiang@bupt.edu.cn>
To: Michael Richardson <mcr+ietf@sandelman.ca>, anima <anima@ietf.org>
References: <167844143207.23755.11725832079832244761@ietfa.amsl.com>, <CBA602EFBB994C74+2023031311493839883724@bupt.edu.cn>, <2347296.1678702970@dyas>, <2470030.1678797688@dyas>
X-Priority: 3
X-GUID: 1F42D0B0-4C34-429B-BDAC-FB912C4DF4E1
X-Has-Attach: no
X-Mailer: Foxmail 7.2.25.213[cn]
Mime-Version: 1.0
Message-ID: <898731B9CC4085C7+2023031516010246054441@bupt.edu.cn>
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64
X-QQ-SENDSIZE: 520
Feedback-ID: bizesmtp:bupt.edu.cn:qybglogicsvr:qybglogicsvr2
Archived-At: <https://mailarchive.ietf.org/arch/msg/anima/5l-K1nAWPF0BsTuuvqF_CnJ8ilI>
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 08:01:14 -0000

Hi, Michael,

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.



Sheng



>Hi, I recalled that I'm the document shepherd for this document.



>I did my shepherd review a year ago on version -04, and I also did a review



>in 2020 when we adopted it:



>  https://mailarchive.ietf.org/arch/msg/anima/hCv5bZxBrzSzA6BjA5DY7_RDo6U/



>



>I am updating my shepherd review, but let me highlight some comments from



>January 2022 review, and my January 2020 comments that have still not been



>acted upon.



>



>I think that the use cases are not well supported.



>I can not comment on whether SBA is a reasonable use case, if it were, then I



>would expect a 3GPP document to cite this one.  Has that occured?



>



>I do not find the INC use case credible.



>I can see that yes, the INC needs data backup and data aggregation, but I



>don't see why they would do that via the ACP.  I can see that perhaps there



>is an ASA that would run over an ACP that would provision where computing is



>supposed to go, but the actual movement of the data seems to belong in the



>production network.  Then the data might move by rsync, etc.



>



>I don't find the V2X communications use credible either.



>This is because I don't think V2X will deploy an ACP, or for that matter



>*can* deploy such a thing as it would cross the boundaries of authorities.



>



>The thing that I **do** find credible is software updates, particularly within



>Enterprises and ISPs for their core switching equipment, but also for IoT



>devices that might be connected at the edge of the switching network.



>The firmware updates can be transfered across a high-speed network to the



>edge where slow/sleepy IoT devices can pick them up via one-hop



>communications.



>



>I did not find the Smart Home use case credible.



>Amazon, Google and Apple have invested in CSA/MATTER, and it has it's own



>communication fabric.  That spec does not cite this spec, so I don't see how



>this helps.



>



>



>--



>Michael Richardson <mcr+IETF@sandelman.ca>, Sandelman Software Works



> -= IPv6 IoT consulting =-                      *I*LIKE*TRAINS*



>



>



>