ramverma | af74a62 | 2018-07-31 18:25:39 +0100 | [diff] [blame^] | 1 | // |
| 2 | // ============LICENSE_START======================================================= |
| 3 | // Copyright (C) 2016-2018 Ericsson. All rights reserved. |
| 4 | // ================================================================================ |
| 5 | // This file is licensed under the CREATIVE COMMONS ATTRIBUTION 4.0 INTERNATIONAL LICENSE |
| 6 | // Full license text at https://creativecommons.org/licenses/by/4.0/legalcode |
| 7 | // |
| 8 | // SPDX-License-Identifier: CC-BY-4.0 |
| 9 | // ============LICENSE_END========================================================= |
| 10 | // |
| 11 | // @author Sven van der Meer (sven.van.der.meer@ericsson.com) |
| 12 | // |
| 13 | |
| 14 | == Unifying Policy Theory (the APEX theory) (NOMS'18) |
| 15 | |
| 16 | [width="100%",cols="15%,90%"] |
| 17 | |=== |
| 18 | |
| 19 | h| Title |
| 20 | e| Taming Policy Complexity: Model to Execution |
| 21 | |
| 22 | h| Venue |
| 23 | | IEEE NOMS, Taipei, April 2018 |
| 24 | |
| 25 | h| Abstract |
| 26 | | Since the 1970’s it has been acknowledged that a |
| 27 | complex system can be broken into (a) its invariant functional |
| 28 | parts (mechanism), and (b) the externalized choices for how the |
| 29 | system should behave (policy). Policy-based management’s main |
| 30 | objective is to separate and externalize the decisions required by a |
| 31 | system from the mechanisms provided by the system, and provide |
| 32 | a way to define and evaluate these decisions. A few decades later, |
| 33 | we have today a plethora of different policy models and even more |
| 34 | policy languages – plus tooling – offering policy-based solutions |
| 35 | for virtually any use case and scenario. However, policy-based |
| 36 | management as a standalone domain has never been evaluated |
| 37 | in terms of which parts are variant / invariant, i.e. which parts |
| 38 | of policy-based management can be domain-, model-, language-, |
| 39 | usecase-independent. In this paper, we introduce and define a |
| 40 | formal universal policy model that does exactly that. The result |
| 41 | is a model that can be used to design, implement, and deploy |
| 42 | immutable policy infrastructure (engine and executor) being able |
| 43 | to execute (virtually) any policy model. |
| 44 | |
| 45 | h| BibTeX |
| 46 | a| |
| 47 | [source,bibtex] |
| 48 | ---- |
| 49 | @inproceedings{noms/MeerMK18a, |
| 50 | author = {Sven van der Meer and |
| 51 | John Keeney and |
| 52 | Liam Fallon}, |
| 53 | title = {Taming Policy Complexity: Model to Execution}, |
| 54 | booktitle = {2018 {IEEE/IFIP} Network Operations and Management Symposium, |
| 55 | {NOMS} 2018, Taipei, Taiwan, April 23-27, 2018}, |
| 56 | year = {2018} |
| 57 | ---- |
| 58 | |
| 59 | |=== |
| 60 | |