[Anima] Intent per ASA or per AF?

"Michael Behringer (mbehring)" <mbehring@cisco.com> Fri, 18 November 2016 01:53 UTC

Return-Path: <mbehring@cisco.com>
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 E9672129602 for <anima@ietfa.amsl.com>; Thu, 17 Nov 2016 17:53:04 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -16.018
X-Spam-Level:
X-Spam-Status: No, score=-16.018 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_HI=-5, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, RP_MATCHES_RCVD=-1.497, SPF_PASS=-0.001, USER_IN_DEF_DKIM_WL=-7.5] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=cisco.com
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 kNB_14TvxDw5 for <anima@ietfa.amsl.com>; Thu, 17 Nov 2016 17:53:04 -0800 (PST)
Received: from rcdn-iport-2.cisco.com (rcdn-iport-2.cisco.com [173.37.86.73]) (using TLSv1.2 with cipher DHE-RSA-SEED-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id EB5CB1293E1 for <anima@ietf.org>; Thu, 17 Nov 2016 17:53:03 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=587; q=dns/txt; s=iport; t=1479433983; x=1480643583; h=from:to:subject:date:message-id: content-transfer-encoding:mime-version; bh=irZhiL8ao7PUj0NFLOA/Ci6dSqDMZ7eU7sZyyc8Z5Ew=; b=FyJs0ZrXsj4xjTCzkgBSfyY9qTXrf8nwIIwbRkvC/J22fgG3wZPQ8TSd hpOmZJ/4jAqHZqdlVS5vIaaT9woElGkOnUcYF45OVvAaja/r3jj8akULB 5xpXmeng1PVP+b5OckJzY6YbSZcQj1HxHHBCxRRJeEcc6qS7gesEj9Y9l 0=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: A0AAAgDpXS5Y/5hdJa1eGwEBAQMBAQEJAQEBgzcBAQEBAR+BX404q3SCB4URgzE/FAECAQEBAQEBAWIdC4RvOlEBPkImAQQbiGScSJIli1gBAQgBAQEBI4Y8jwQFmkMBgUWPIIFhjkyRWgEeN4ELhTuHX4EMAQEB
X-IronPort-AV: E=Sophos;i="5.31,655,1473120000"; d="scan'208";a="175622615"
Received: from rcdn-core-1.cisco.com ([173.37.93.152]) by rcdn-iport-2.cisco.com with ESMTP/TLS/DHE-RSA-AES256-GCM-SHA384; 18 Nov 2016 01:53:03 +0000
Received: from XCH-ALN-009.cisco.com (xch-aln-009.cisco.com [173.36.7.19]) by rcdn-core-1.cisco.com (8.14.5/8.14.5) with ESMTP id uAI1r32B011771 (version=TLSv1/SSLv3 cipher=AES256-SHA bits=256 verify=FAIL) for <anima@ietf.org>; Fri, 18 Nov 2016 01:53:03 GMT
Received: from xch-rcd-006.cisco.com (173.37.102.16) by XCH-ALN-009.cisco.com (173.36.7.19) with Microsoft SMTP Server (TLS) id 15.0.1210.3; Thu, 17 Nov 2016 19:53:02 -0600
Received: from xch-rcd-006.cisco.com ([173.37.102.16]) by XCH-RCD-006.cisco.com ([173.37.102.16]) with mapi id 15.00.1210.000; Thu, 17 Nov 2016 19:53:02 -0600
From: "Michael Behringer (mbehring)" <mbehring@cisco.com>
To: "anima@ietf.org" <anima@ietf.org>
Thread-Topic: Intent per ASA or per AF?
Thread-Index: AdJBPZCUap75TyB7THivcdpl+3+EcA==
Date: Fri, 18 Nov 2016 01:53:02 +0000
Message-ID: <7f30b33118334c09a54acb9293b2c265@XCH-RCD-006.cisco.com>
Accept-Language: en-GB, en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-ms-exchange-transport-fromentityheader: Hosted
x-originating-ip: [10.70.231.136]
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Archived-At: <https://mailarchive.ietf.org/arch/msg/anima/pKsA1tx90M_qFpCAycuKWozWsgw>
Subject: [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 01:53:05 -0000

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