Re: [Anima] Intent per ASA or per AF?

Agree, Laurent. Then let’s nail this down in the Intent draft: “Intent is defined per Autonomic Function”. Michael From: Laurent Ciavaglia [mailto:laurent.ciavag...@nokia-bell-labs.com] Sent: 18 November 2016 11:04 To: Michael Behringer (mbehring) ; anima@ietf.org Subject: Re:

Re: [Anima] Intent per ASA or per AF?

On 18/11/2016 14:53, Michael Behringer (mbehring) wrote: > One question that just came up: Should Intent be designed per ASA or per AF? > > My suggestion previously was to segment Intent into sections per Autonomic > Functions. > > Example: Intent for the bootstrap function could be: > -

Re: [Anima] The ACP is not an ASA, but...

> -Original Message- > From: Anima [mailto:anima-boun...@ietf.org] On Behalf Of Brian E > Carpenter > Sent: 18 November 2016 10:32 > To: Anima WG > Subject: [Anima] The ACP is not an ASA, but... > > The ACP is not an ASA, it's actually a set of components, and probably it

Re: [Anima] I-D Action: draft-carpenter-anima-ani-objectives-00.txt

Some comments on the BRSKI discussion inline, > On Nov 17, 2016, at 3:17 PM, Toerless Eckert wrote: > > > Thanks Brian & Bing > > Inline > The following quote levels appear to be direct or paraphrases from the objectives draft. I’m tempted not even to respond to this email

[Anima] Quick clarification re GRASP tests

Just to clarify a comment Bing made about the tests with my Python prototype: - I have tested it in a single host by running multiple GRASP instances. These tests require the host to listen to its own multicasts. Done on both Windows 7 and Linux. - I have tested it between Windows and Linux on a

Re: [Anima] additional information and JSON/CBOR

> On Nov 17, 2016, at 3:10 AM, Eliot Lear wrote: > > Hi authors, > > The Fairhair folk would like some clarity on the following statement in > Section 3.1.7: > >> Functionality to provide generic "configuration" information is >> supported. The parsing of this data and

Re: [Anima] I-D Action: draft-carpenter-anima-ani-objectives-00.txt

A bit last minute but if you have a chance to look at this today, please do so. It attempts to make some important details more precise. Note: This draft is posted to allow systematic discussion of the various objectives in a consistent way. It is quite probable that rather than this

[Anima] additional information and JSON/CBOR

Hi authors, The Fairhair folk would like some clarity on the following statement in Section 3.1.7: >Functionality to provide generic "configuration" information is >supported. The parsing of this data and any subsequent use of the >data, for example communications with a Network