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

Michael Richardson <> Mon, 13 January 2020 18:23 UTC

Return-Path: <>
Received: from localhost (localhost []) by (Postfix) with ESMTP id 1FE211209F0 for <>; Mon, 13 Jan 2020 10:23:18 -0800 (PST)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: -4.2
X-Spam-Status: No, score=-4.2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, SPF_HELO_NONE=0.001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Received: from ([]) by localhost ( []) (amavisd-new, port 10024) with ESMTP id 3021lFZjHqXQ for <>; Mon, 13 Jan 2020 10:23:16 -0800 (PST)
Received: from ( []) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by (Postfix) with ESMTPS id 8A7751209E1 for <>; Mon, 13 Jan 2020 10:23:16 -0800 (PST)
Received: from ( [IPv6:2607:f0b0:f:2::247]) by (Postfix) with ESMTP id 665163818F for <>; Mon, 13 Jan 2020 13:22:50 -0500 (EST)
Received: from localhost (localhost [IPv6:::1]) by (Postfix) with ESMTP id 809F4A3B for <>; Mon, 13 Jan 2020 13:23:15 -0500 (EST)
From: Michael Richardson <>
In-Reply-To: <>
References: <>
X-Mailer: MH-E 8.6; nmh 1.7+dev; GNU Emacs 24.5.1
X-Face: $\n1pF)h^`}$H>Hk{L"x@)JS7<%Az}5RyS@k9X%29-lHB$Ti.V>2bi.~ehC0; <'$9xN5Ub# z!G,p`nR&p7Fz@^UXIn156S8.~^@MJ*mMsD7=QFeq%AL4m<nPbLgmtKK-5dC@#:k
MIME-Version: 1.0
Content-Type: multipart/signed; boundary="=-=-="; micalg=pgp-sha256; protocol="application/pgp-signature"
Date: Mon, 13 Jan 2020 13:23:15 -0500
Message-ID: <8902.1578939795@localhost>
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: Mon, 13 Jan 2020 18:23:18 -0000

I have re-read the document quickly.
I think that some of the how does it work parts will need to expanded.
I support adoption.

My non-blocking comments:
1) I think that I'd like to see more reference to the use cases in the
2) I think that Connected-Car case is not useful unless the ACP will
   be extended to the car, and I think that is unreasonable to do in
   the general situation.  Maybe it makes sense for an autonomous
   vehicle situation where all vehicles are owned by the 'taxi' service.

3) I think that the killer app for this is Firmware Updates.
   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.                

Toerless Eckert <> wrote:
    > 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.

Michael Richardson <>ca>, Sandelman Software Works
 -= IPv6 IoT consulting =-