> This conversation strengthens my conviction that we should leave this as
> flexible as possible, because the requirements will change with experience.
> In other words, label each segment of Intent - and the label may well be the
> name of an autonomic function - but do not make rules about the l
On 21/11/2016 06:36, Michael Behringer (mbehring) wrote:
>> -Original Message-
>> From: Michael Richardson [mailto:mcr+i...@sandelman.ca]
>> Sent: 20 November 2016 07:42
>> To: Michael Behringer (mbehring)
>> Cc: anima@ietf.org
>> Subject:
> -Original Message-
> From: Michael Richardson [mailto:mcr+i...@sandelman.ca]
> Sent: 20 November 2016 07:42
> To: Michael Behringer (mbehring)
> Cc: anima@ietf.org
> Subject: Re: [Anima] Intent per ASA or per AF?
>
>
> Michael Behringer (mbehring) wrote
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: - allow
>
: 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
ASA or per AF?
Michael,
Definitely not designed per ASA.
As mentioned at the mic, in draft-peloso
(https://datatracker.ietf.org/doc/draft-peloso-anima-autonomic-function), we've
proposed format for "intent" at the AF level.
Please note, that once "resolved" the
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:
> - allo
Michael,
Definitely not designed per ASA.
As mentioned at the mic, in draft-peloso
(https://datatracker.ietf.org/doc/draft-peloso-anima-autonomic-function),
we've proposed format for "intent" at the AF level.
Please note, that once "resolved" the AF intent will exist (be
translated) in the in
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:
- allow bootstrapping new devices only during maintenance window
For such In
