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

<ludwig@clemm.org> Fri, 18 November 2016 02:46 UTC

Return-Path: <ludwig@clemm.org>
X-Original-To: anima@ietfa.amsl.com
Delivered-To: anima@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id DBE2C126CD8 for <anima@ietfa.amsl.com>; Thu, 17 Nov 2016 18:46:43 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.39
X-Spam-Level:
X-Spam-Status: No, score=-1.39 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, RCVD_IN_SORBS_SPAM=0.5, SPF_HELO_PASS=-0.001, T_KAM_HTML_FONT_INVALID=0.01] autolearn=no autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id RbBPwPGXZC0k for <anima@ietfa.amsl.com>; Thu, 17 Nov 2016 18:46:42 -0800 (PST)
Received: from mout.perfora.net (mout.perfora.net [74.208.4.196]) (using TLSv1.2 with cipher DHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 3BEFF128E18 for <anima@ietf.org>; Thu, 17 Nov 2016 18:46:42 -0800 (PST)
Received: from LAPTOPR7T053C2 ([107.18.128.211]) by mrelay.perfora.net (mreueus003 [74.208.5.2]) with ESMTPSA (Nemesis) id 0LueDW-1cpb933yCW-00zrBG; Fri, 18 Nov 2016 03:46:38 +0100
From: ludwig@clemm.org
To: "'Michael Behringer (mbehring)'" <mbehring@cisco.com>, 'Laurent Ciavaglia' <Laurent.Ciavaglia@nokia-bell-labs.com>, anima@ietf.org
References: <7f30b33118334c09a54acb9293b2c265@XCH-RCD-006.cisco.com> <ee95389f-d74d-a5f1-6292-ba875613e6a2@nokia-bell-labs.com> <8934c1bb6dbb47878a0f8b911376bad7@XCH-RCD-006.cisco.com>
In-Reply-To: <8934c1bb6dbb47878a0f8b911376bad7@XCH-RCD-006.cisco.com>
Date: Thu, 17 Nov 2016 21:46:38 -0500
Message-ID: <00ff01d24145$fd820070$f8860150$@clemm.org>
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="----=_NextPart_000_0100_01D2411C.14AD7F10"
X-Mailer: Microsoft Outlook 16.0
Thread-Index: AQGm6i93Ts9PlZSen5cNpIqmN6f4EQLjObglAkfrncGhC14UgA==
Content-Language: en-us
X-Provags-ID: V03:K0:cDrewyXjy8CmN1mVTdVCc2UtdJpTDoft9/xM+qcCvlh08wqnFUc 5FHqJZHY3UFQ3v6gIh6qi+WmoycbEI1sPmx+N6yxnJvbCej3LuIhfesbPWhKIWoSroDEXd/ 4gFto9Todfw2e9TbH7UmS6Ldwp10dZnjDdkcoz1jUpF6jADxshu3O021JUfHEESyEj72rKq sLrx/6Ky33OvJMcb+kBRA==
X-UI-Out-Filterresults: notjunk:1;V01:K0:sOS4nbRxPPA=:8frfE16nixWiAv38Yzvm2k +JrwJHz+3M7lvuRmockzYJoujwdW7zN7owJa0XbWAcIobQTSKed0Z/ga7uWPeBWg604v87YP8 +b5YlRbdxDs6MxPaeJZRF/plfD+A5j8G4QcVoHeANhJDBxz14k5vXTE4B1hDUE5lrkVLoYKEd 9GFQhAaZNwSga5qi75JYxbGF98rNhJ9obK9Yw30k7+6IO7H668UiigqO6Yj2E4ehgON86a9Od jyG37Elo+cM9MGkYkTz3ZtVp6SJz5bO0q8H1pBDBmbCFfvrR0TCT3L+RluFOps6hMMrE5nDKo hIx+HOFlN2ujTbHMEJhzlkwzu7hydBfclvsGarnWjy/mIQPofCPyBVjEAzznB+fqtFm1psuaJ WHQdkHi2XLuT7WA66JGXeVYAUInhTj2zxzN8NT2bK3gjmHKjq4Wr6lRGsNsuYPW+Hc2M6QsTM 8VaayrFaDVTd7eCvMsjhDIVJpxbkVn6Auq4NkVxSTFJ+ZOBSKOABCTJ0Z6XV0vnI/tD1vQYmX 7m6cCWk2xkmGVZxu6RDwsumx9dOWjkIIwyPN49eu7BPxDvfz9btYjrO7m7J3lJZ1X7EGCO6/k AiCgn/dTCq20Ajs091KogdviP1Q4R6PlOnieQEHtrJXalKsldW16iy4VcJ/h1Xd8UI8sN0Xmu fJkCfYsVwx537y/0vhP+T9+BglkbZFCh8Olxkk60tHhz1tp8LOBtDx/cjlchyo2/hpXCcJxsx yxMnQSayO/F+16j4
Archived-At: <https://mailarchive.ietf.org/arch/msg/anima/stDvLSzHGDIqSgBkl1hdAtGRTos>
Subject: Re: [Anima] Intent per ASA or per AF?
X-BeenThere: anima@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: Autonomic Networking Integrated Model and Approach <anima.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/anima>, <mailto:anima-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/anima/>
List-Post: <mailto:anima@ietf.org>
List-Help: <mailto:anima-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/anima>, <mailto:anima-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 18 Nov 2016 02:46:44 -0000

+1 for defining it per autonomic function.  This is also a way to potentially “scope” intent distribution.  

--- Alex

From: Anima [mailto:anima-bounces@ietf.org] On Behalf Of Michael Behringer (mbehring)
Sent: Thursday, November 17, 2016 9:24 PM
To: Laurent Ciavaglia <Laurent.Ciavaglia@nokia-bell-labs.com>; anima@ietf.org
Subject: 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.Ciavaglia@nokia-bell-labs.com] 
Sent: 18 November 2016 11:04
To: Michael Behringer (mbehring) <mbehring@cisco.com <mailto:mbehring@cisco.com> >; anima@ietf.org <mailto:anima@ietf.org> 
Subject: Re: [Anima] Intent per 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 AF intent will exist (be translated) in the instances of the AF (the ASAs) as AF instance descriptor. This is ASA-level/specific information.

Best regards, Laurent.

On 18/11/2016 02: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: 
- allow bootstrapping new devices only during maintenance window
 
For such Intent, action could be taken on the registrar (one ASA of the AF), or on the proxy (another ASA of the same AF). 
 
It seems to me an author of an AF might like all ASAs of his AF to know about the Intent, because the proxy may also take actions. 
 
Michael
 
_______________________________________________
Anima mailing list
Anima@ietf.org <mailto:Anima@ietf.org> 
https://www.ietf.org/mailman/listinfo/anima
 

 

-- 

Laurent Ciavaglia

Nokia, Bell Labs

 

+33 160 402 636

route de Villejust - Nozay, France

linkedin.com/in/laurent.ciavaglia