Re: [Anima] Adoption call for draft-liu-anima-grasp-distribution (ends 01/27/2020)

Xun Xiao <> Tue, 25 February 2020 10:39 UTC

Return-Path: <>
Received: from localhost (localhost []) by (Postfix) with ESMTP id 7613D3A0925; Tue, 25 Feb 2020 02:39:21 -0800 (PST)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: -1.9
X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Received: from ([]) by localhost ( []) (amavisd-new, port 10024) with ESMTP id Fdcgv60jv6EQ; Tue, 25 Feb 2020 02:39:18 -0800 (PST)
Received: from ( []) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by (Postfix) with ESMTPS id 915773A07D2; Tue, 25 Feb 2020 02:39:18 -0800 (PST)
Received: from (unknown []) by Forcepoint Email with ESMTP id 06D20318D600BC4D0F1A; Tue, 25 Feb 2020 10:39:16 +0000 (GMT)
Received: from ( by ( with Microsoft SMTP Server (TLS) id 14.3.408.0; Tue, 25 Feb 2020 10:38:35 +0000
Received: from ( by ( with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256) id 15.1.1713.5; Tue, 25 Feb 2020 11:38:35 +0100
Received: from ([]) by ([]) with mapi id 15.01.1713.004; Tue, 25 Feb 2020 11:38:35 +0100
From: Xun Xiao <>
To: Toerless Eckert <>, "" <>
CC: "" <>
Thread-Topic: [Anima] Adoption call for draft-liu-anima-grasp-distribution (ends 01/27/2020)
Thread-Index: AQHVygcEixrclYVRzkuIMbNn6stxL6gVKlSAgBbDJdA=
Date: Tue, 25 Feb 2020 10:38:34 +0000
Message-ID: <>
References: <> <>
In-Reply-To: <>
Accept-Language: en-US
Content-Language: en-US
x-originating-ip: []
Content-Type: text/plain; charset="iso-2022-jp"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-CFilter-Loop: Reflected
Archived-At: <>
Subject: Re: [Anima] Adoption call for draft-liu-anima-grasp-distribution (ends 01/27/2020)
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Autonomic Networking Integrated Model and Approach <>
List-Unsubscribe: <>, <>
List-Archive: <>
List-Post: <>
List-Help: <>
List-Subscribe: <>, <>
X-List-Received-Date: Tue, 25 Feb 2020 10:39:22 -0000

Dear Toerless,

Thanks again for taking care of the adoption. As required, we have generated the version -00.

On behalf of all the other authors, we have uploaded the version -00 to datatracker. For some reasons, we did not get any notification of a successful upload. We hope we upload it correctly and you will get notified.

Please also find our replies to your email inline. Thanks a lot!

Best Regards,

Xun Xiao (肖迅)
Advanced Wireless Technology Lab
Munich Research Center
Huawei Technologies Co.,Ltd.

-----Original Message-----
From: Toerless Eckert [] 
Sent: Tuesday, 11 February 2020 00:13
Subject: Re: [Anima] Adoption call for draft-liu-anima-grasp-distribution (ends 01/27/2020)

We had 5 voices feedback (from non-authors) to support adoption of this document, and no voices objecting. I think this qualifies for adoption of the document.

Nevertheless, the supporting voices did indicate a range of improvements they would like to see. So, jere is what i would propose:


A) Please add a section Open Issues, mark it as
[RFC-Editor: To Be removed before becoming RFC].
Make it contain the following text:

[XX] This is done by adding Appendix A in the draft version -00.

The following issues where identified by the WG when adopting the -00 draft version. These issues will be individually removed in upcoming when they are resolved.

1. More reference to the use cases in the introduction.

2. Better explanation of the required context of the Connected-Car case:
Not applicable unless the ACP will be extended to the car, which may not be desirable with the current ACP design, but maybe refocussing on an "autonomous fleet" use-case (e.g.: all cars operated by some taxi like service).

3. Consider use-case/example of firmware update.  By abstracting the location of the firmware from the name of the firmware, while providing a way to notify about it, this significantly supports distribution of firmware updates.
References to SUIT would appropriate.

4. Issues discussed in

5. Rethink/refine terminology, e.g.: "module" seems to be too prescriptive.
Refine proposed extensions.

6. I support adoption, but also support the suggestion (from IETF106) Provide more protocol behavior description  instead of only implementation / software module architecture description. 
Reduce the latter or provide better justification for their presence due to explained interoperability requirements.

7. Better motivation in sections 1..4 of the proposed extensions

8. Consider moving examples from appendices into core-text . Ideally craft a single use-case showing/applying all extensions (most simple use case that uses them all).

9. Refine terminology to better match/reuse-the established terminology from the pre-existing ANIMA documents.

B) Add changelog section, equally marked as to be removed before . For this version -00 it should just list above section from A) to be new.

[XX] This is done by adding Appendix A in the draft version -00.

C) Designate in the authors list one or two main editors for the time
   being, doesn't have to be final, just whoever has the main edit pen
   from you.  Post this version as -00 with name
   and replacing draft-liu-anima-grasp-distribution
[XX] Bing Liu and me (Xun Xiao) were specified as Ed. In the author list and the draft name was also changed as required.

   I will then approve that doc as WG chair.
[XX] Thanks.

D) Feel free to work on -01 and further. In the changelog, please
   describe for each change which of the above 9 points are addressed by
   the change and concentrate on those changes first before addressing
   further enhancements.
[XX] Indeed, those comments are not completely independent, some of them may affect each other, so we were considering them as a whole and try to make a systematic revision in version -01. In parallel with version -00, we already started to work on the version -01, but need more time.

E) I would strongly suggest you authors consider to create a repo for
   this document under It specifically makees
   it easier to open for each of the above 10 bullet points possible
   "Issues" where it would be easier to have focussed discusses.
[XX] We tried to create a new repo there, but do we have access right to create a repository under anima-wg?

   I am not a github is the only way groupie though, so please make sure
   all discussions are Cc'ed to the mailing list, even though it may primarily be on
   github to make then easier to track/find.


On Mon, Jan 13, 2020 at 12:45:33PM +0100, Toerless Eckert wrote:
> This message starts a two-week adoption call, it ends on January 27th, 2020.
> draft-liu-anima-grasp-distribution was progressed up to version -13 
> with the help of the WG, it was last presented at IETF106 with good interest.
> The draft is now clearly in scope of ANIMA charter 2 that was adopted 
> around IETF106. The authors asked for adoption of the document.
> As far as the chairs heard, there was no objection in the room.
> We therefore are asking the ANIMA working group for adoption of the following work:
> Title:    Information Distribution in Autonomic Networking
> Name:     draft-liu-anima-grasp-distribution
> Authors:  B. Liu, X. Xiao, A. Hecker, S. Jiang, Z. Despotovic
> URL:
> This document is intended to become a standards track ANIMA WG document.
> Standard track is desired because it is meant to become the required 
> small set of protocol extensions to the GRASP protocol in support of 
> the self-organization of ASA.
> Please express your support or rejection. If you think this document 
> should _not_ be adopted, please also explicitly indicate the reasons.
> For the ANIMA WG chairs, 
>     Toerless
> _______________________________________________
> Anima mailing list