Subject: [saag] Anima report

From: "Nancy Cam-Winget (ncamwing)" <[email-masked]>
Date: Wed, 4 Nov 2015 02:09:45 +0000

ANIMA met on Monday (1pm) and Tuesday (3pm).

Below is a summary of the sessions (thanks to Max Pritikin for providing some of the summary content):

Update reports were provided for the following drafts:
 - draft-ietf-anima-grasp<https://datatracker.ietf.org/doc/draft-ietf-anima-grasp/> (Anima Generic Signaling)
 - draft-ietf-anima-bootstrapping-keyinfra<https://datatracker.ietf.org/doc/draft-ietf-anima-bootstrapping-keyinfra/> (Auto Bootstrapping status from the Design team)
 - draft-ietf-anima-autonomic-control-plane<https://datatracker.ietf.org/doc/draft-ietf-anima-autonomic-control-plane/> (Control Plane and Addressing)
 - draft-behringer-anima-reference-model<https://datatracker.ietf.org/doc/draft-behringer-anima-reference-model/> (Anima reference model)
 - draft-jiang-anima-prefix-management<https://datatracker.ietf.org/doc/draft-jiang-anima-prefix-management/> (Autonomic Prefix Management in Large-scale Networks)
 - draft-eckert-anima-stable-connectivity<https://datatracker.ietf.org/doc/draft-eckert-anima-stable-connectivity/> (Using the Control Plane for stable connections)
 - draft-liu-anima-grasp-distribution<https://datatracker.ietf.org/doc/draft-liu-anima-grasp-distribution/> (Information Distribution over GRASP)
 - draft-behringer-anima-autonomic-addressing<https://datatracker.ietf.org/doc/draft-behringer-anima-autonomic-addressing/> (Addressing in the ACP)
 - draft-du-anima-an-intent<https://datatracker.ietf.org/doc/draft-du-anima-an-intent/> (Autonomic Network Intent concept and format)
 - draft-peloso-anima-autonomic-function<https://datatracker.ietf.org/doc/draft-peloso-anima-autonomic-function/>
& draft-ciavaglia-anima-coordination<https://datatracker.ietf.org/doc/draft-ciavaglia-anima-coordination/> (A Day in the Life of an autonomic function)

There is discussion about GRASP depending on ACP security model or providing some of its own (to run independently of ACP).

* There is discussion of how to manage "adjacency table" state collected prior to security being established. Clearly a possible attack avenue.

* bootstrap key requirements touched on an important point but no further discussion ensued: does bootstrapping depend on having a valid clock or not? Anima may need to address time synchronization as part of bootstrapping but has not been picked up as a requirement yet.

* Update to ACP erquirements now explain why IPv6 (only) is sufficient; ACP requirements strive for long term simplicity

The group has accepted the Reference Model,  Stable Connectivity and Prefix Management as WG drafts.  There was discussion on adoption of the Autonomic Addressing with general consensus to accept which will also be confirmed on the email list.

- Nancy