|
1 |
| -Open Architecture Working Group |
2 |
| -Internet-Draft |
3 |
| -Intended status: Draft |
4 |
| -Expires: June 1, 2023 |
5 |
| - March 12, 2022 |
| 1 | +Open Architecture |
| 2 | +################# |
6 | 3 |
|
| 4 | +Version: 0.0.1 |
| 5 | +Date: 2022-04-17 |
7 | 6 |
|
8 |
| - Open Architecture: Methodology for interpreting directed graphs as |
9 |
| - any system architecture |
| 7 | +Status |
| 8 | +****** |
10 | 9 |
|
11 |
| -Abstract |
| 10 | +Proposed |
12 | 11 |
|
13 |
| - This document describes the Open Architecture, aka Alice; a proxy format |
14 |
| - for domain specific representations of architecture. |
| 12 | +Description |
| 13 | +*********** |
15 | 14 |
|
16 |
| - The Open Architecture is a methodology for intepretation of exisitng |
17 |
| - well established, formats, protocols, and other domain specific |
18 |
| - representations of architecture. We define a methodology for interpreting |
19 |
| - a directed graph representing a system architecture. |
| 15 | +The Open Architecture is a methodology for interpreting directed graphs as |
| 16 | +any system architecture. |
20 | 17 |
|
21 |
| - We provide implementations which interpret those graphs as software and hardware |
22 |
| - architectures. |
| 18 | +Context |
| 19 | +******* |
23 | 20 |
|
24 |
| -Status of This Memo |
| 21 | +This document describes the Open Architecture; a proxy format for domain |
| 22 | +specific representations of architecture. |
25 | 23 |
|
26 |
| - This Internet-Draft will be submitted in full conformance with the |
27 |
| - provisions of BCP 78 and BCP 79. |
| 24 | +The Open Architecture is a methodology for intepretation of exisitng |
| 25 | +well established, formats, protocols, and other domain specific |
| 26 | +representations of architecture. We define a methodology for interpreting |
| 27 | +a directed graph representing a system architecture. |
28 | 28 |
|
29 |
| - This draft will expire on June 1st, 2023. |
| 29 | +We provide implementations which interpret graphs as software and hardware |
| 30 | +architectures. |
30 | 31 |
|
31 |
| -Table of Contents |
| 32 | +The Open Architecture also enables hybrid on/off chain smart contacts. |
| 33 | +It does this by incorporating risk management into architecture definition / |
| 34 | +smart contract. Smart contracts with understanding of risk are effectively |
| 35 | +entities making decisions based on models. This allows for mutation in |
| 36 | +implementation while maintaining principles. |
32 | 37 |
|
33 |
| - 1. Introduction |
34 |
| - 2. References |
| 38 | +The smart contract is able to make its own decisions based on learned |
| 39 | +experience so as to continue to operate until its strategic goals are meet. |
| 40 | +As measured by oracle data ordained from trusted parties as is |
| 41 | +applicable to context. Where chains of trust are established via Peer DIDs |
| 42 | +between entities and data for provenance. Leveraging verifiable credentials |
| 43 | +for review system to measure risk in absence of attestation. |
35 | 44 |
|
36 |
| -1. Introduction |
| 45 | +Intent |
| 46 | +****** |
37 | 47 |
|
38 |
| - The Open Architecture enables hybrid on/off chain smart contacts. |
39 |
| - It does this by incorporating risk management into architecture definition / |
40 |
| - smart contract. Smart contracts with understanding of risk are effectively |
41 |
| - entities making decisions based on models. This allows for mutation in |
42 |
| - implementation while maintaining principles. |
| 48 | +- ``upstream`` MUST be treated as the document itself if the document is a |
| 49 | + domain sepcific architecture or manifest already. |
43 | 50 |
|
44 |
| - The smart contract is able to make its own decisions based on learned |
45 |
| - experience so as to continue to operate until its strategic goals are meet. |
46 |
| - As measured by oracle data ordained from trusted parties as is |
47 |
| - applicable to context. Where chains of trust are established via Peer DIDs |
48 |
| - between entities and data for provenance. Leveraging verifiable credentials |
49 |
| - for review system to measure risk in absence of attestation. |
| 51 | +- ``overlay`` MUST be applied to upstream following overlay application process |
| 52 | + describied in **TODO** `Overlay <https://github.com/intel/dffml/blob/alice/Overlay>`_ if given |
50 | 53 |
|
51 |
| -2. References |
| 54 | +- ``orchestrator`` SHOULD be loaded and inspected for compliance with top level |
| 55 | + system context's policy (sandbox) before execution. |
52 | 56 |
|
53 |
| -2.1. Normative References |
| 57 | +References |
| 58 | +********** |
54 | 59 |
|
55 |
| -2.2. Informative References |
| 60 | +- Living Threat Models |
56 | 61 |
|
57 |
| - [alice-reveiw] |
58 |
| - DFFML Authors, "Alice", May 2022, |
59 |
| - <https://github.com/intel/dffml/pulls/1401>. |
| 62 | + - John L Whiteman & John S Andersen, "Living Threat Models", June 11th 2022 |
| 63 | + - https://github.com/johnlwhiteman/living-threat-models |
60 | 64 |
|
61 |
| - [living-threat-models] |
62 |
| - John L Whiteman & John S Andersen, "Living Threat Models", June 11th 2022, |
63 |
| - <https://github.com/johnlwhiteman/living-threat-models>. |
| 65 | +- TODO |
| 66 | + |
| 67 | + - Add content from discussion thread |
| 68 | + |
| 69 | + - `docs/arch/alice/discussion/0004/reply_0005.md <https://github.com/intel/dffml/blob/alice/docs/arch/alice/discussion/0004/reply_0005.md>`_ |
| 70 | + - `docs/arch/alice/discussion/0023/reply_0020.md <https://github.com/intel/dffml/blob/alice/docs/arch/alice/discussion/0023/reply_0020.md>`_ |
| 71 | + - `docs/arch/alice/discussion/0023/reply_0022.md <https://github.com/intel/dffml/blob/alice/docs/arch/alice/discussion/0023/reply_0022.md>`_ |
| 72 | + - `docs/arch/alice/discussion/0023/reply_0028.md <https://github.com/intel/dffml/blob/alice/docs/arch/alice/discussion/0023/reply_0028.md>`_ |
| 73 | + - `docs/arch/alice/discussion/0023/reply_0037.md <https://github.com/intel/dffml/blob/alice/docs/arch/alice/discussion/0023/reply_0037.md>`_ |
| 74 | + - `docs/arch/alice/discussion/0023/reply_0040.md <https://github.com/intel/dffml/blob/alice/docs/arch/alice/discussion/0023/reply_0040.md>`_ |
| 75 | + - `docs/arch/alice/discussion/0023/reply_0055.md <https://github.com/intel/dffml/blob/alice/docs/arch/alice/discussion/0023/reply_0055.md>`_ |
| 76 | + - `docs/arch/alice/discussion/0036/reply_0022.md <https://github.com/intel/dffml/blob/alice/docs/arch/alice/discussion/0036/reply_0022.md>`_ |
| 77 | + - `docs/arch/alice/discussion/0036/reply_0045.md <https://github.com/intel/dffml/blob/alice/docs/arch/alice/discussion/0036/reply_0045.md>`_ |
| 78 | + - `docs/arch/alice/discussion/0036/reply_0062.md <https://github.com/intel/dffml/blob/alice/docs/arch/alice/discussion/0036/reply_0062.md>`_ |
| 79 | + - `docs/arch/alice/discussion/0036/reply_0066.md <https://github.com/intel/dffml/blob/alice/docs/arch/alice/discussion/0036/reply_0066.md>`_ |
| 80 | + - `docs/arch/alice/discussion/0036/reply_0067.md <https://github.com/intel/dffml/blob/alice/docs/arch/alice/discussion/0036/reply_0067.md>`_ |
| 81 | + - `docs/arch/alice/discussion/0039/index.md <https://github.com/intel/dffml/blob/alice/docs/arch/alice/discussion/0039/index.md>`_ |
| 82 | + - `docs/tutorials/rolling_alice/0000_architecting_alice/README.md <https://github.com/intel/dffml/blob/alice/docs/tutorials/rolling_alice/0000_architecting_alice/README.md>`_ |
| 83 | + - `docs/tutorials/rolling_alice/0000_forward.md <https://github.com/intel/dffml/blob/alice/docs/tutorials/rolling_alice/0000_forward.md>`_ |
| 84 | + - `docs/tutorials/rolling_alice/0000_preface.md <https://github.com/intel/dffml/blob/alice/docs/tutorials/rolling_alice/0000_preface.md>`_ |
| 85 | + - `docs/tutorials/rolling_alice/README.md <https://github.com/intel/dffml/blob/alice/docs/tutorials/rolling_alice/README.md>`_ |
0 commit comments