Debian Codegraph @

rfc9222.html

raw
1 <!DOCTYPE html>
2 <html lang="en" class="RFC">
3 <head>
4 <meta charset="utf-8">
5 <meta content="Common,Latin" name="scripts">
6 <meta content="initial-scale=1.0" name="viewport">
7 <title>RFC 9222: Guidelines for Autonomic Service Agents</title>
8 <meta content="Brian Carpenter" name="author">
9 <meta content="Laurent Ciavaglia" name="author">
10 <meta content="Sheng Jiang" name="author">
11 <meta content="Pierre Peloso" name="author">
12 <meta content="
13 This document proposes guidelines for the design of Autonomic Service
14 Agents for autonomic networks. Autonomic Service Agents, together with
15 the Autonomic Network Infrastructure, the Autonomic Control Plane, and
16 the GeneRic Autonomic Signaling Protocol, constitute base elements of an
17 autonomic networking ecosystem.
18
19 " name="description">
20 <meta content="xml2rfc 3.12.2" name="generator">
21 <meta content="GRASP" name="keyword">
22 <meta content="autonomous" name="keyword">
23 <meta content="autonomic function" name="keyword">
24 <meta content="self-management" name="keyword">
25 <meta content="autonomic networking" name="keyword">
26 <meta content="autonomous operation" name="keyword">
27 <meta content="self-management" name="keyword">
28 <meta content="infrastructure" name="keyword">
29 <meta content="intent" name="keyword">
30 <meta content="autonomic control plane" name="keyword">
31 <meta content="9222" name="rfc.number">
32 <!-- Generator version information:
33 xml2rfc 3.12.2
34 Python 3.6.15
35 appdirs 1.4.4
36 ConfigArgParse 1.4.1
37 google-i18n-address 2.4.0
38 html5lib 1.0.1
39 intervaltree 3.0.2
40 Jinja2 2.11.3
41 kitchen 1.2.6
42 lxml 4.4.2
43 pycairo 1.15.1
44 pycountry 19.8.18
45 pyflakes 2.1.1
46 PyYAML 5.4.1
47 requests 2.24.0
48 setuptools 40.5.0
49 six 1.14.0
50 WeasyPrint 52.5
51 -->
52 <link href="rfc9222.xml" rel="alternate" type="application/rfc+xml">
53 <link href="#copyright" rel="license">
54 <style type="text/css">/*
55
56 NOTE: Changes at the bottom of this file overrides some earlier settings.
57
58 Once the style has stabilized and has been adopted as an official RFC style,
59 this can be consolidated so that style settings occur only in one place, but
60 for now the contents of this file consists first of the initial CSS work as
61 provided to the RFC Formatter (xml2rfc) work, followed by itemized and
62 commented changes found necssary during the development of the v3
63 formatters.
64
65 */
66
67 /* fonts */
68 @import url('https://fonts.googleapis.com/css?family=Noto+Sans'); /* Sans-serif */
69 @import url('https://fonts.googleapis.com/css?family=Noto+Serif'); /* Serif (print) */
70 @import url('https://fonts.googleapis.com/css?family=Roboto+Mono'); /* Monospace */
71
72 @viewport {
73 zoom: 1.0;
74 width: extend-to-zoom;
75 }
76 @-ms-viewport {
77 width: extend-to-zoom;
78 zoom: 1.0;
79 }
80 /* general and mobile first */
81 html {
82 }
83 body {
84 max-width: 90%;
85 margin: 1.5em auto;
86 color: #222;
87 background-color: #fff;
88 font-size: 14px;
89 font-family: 'Noto Sans', Arial, Helvetica, sans-serif;
90 line-height: 1.6;
91 scroll-behavior: smooth;
92 }
93 .ears {
94 display: none;
95 }
96
97 /* headings */
98 #title, h1, h2, h3, h4, h5, h6 {
99 margin: 1em 0 0.5em;
100 font-weight: bold;
101 line-height: 1.3;
102 }
103 #title {
104 clear: both;
105 border-bottom: 1px solid #ddd;
106 margin: 0 0 0.5em 0;
107 padding: 1em 0 0.5em;
108 }
109 .author {
110 padding-bottom: 4px;
111 }
112 h1 {
113 font-size: 26px;
114 margin: 1em 0;
115 }
116 h2 {
117 font-size: 22px;
118 margin-top: -20px; /* provide offset for in-page anchors */
119 padding-top: 33px;
120 }
121 h3 {
122 font-size: 18px;
123 margin-top: -36px; /* provide offset for in-page anchors */
124 padding-top: 42px;
125 }
126 h4 {
127 font-size: 16px;
128 margin-top: -36px; /* provide offset for in-page anchors */
129 padding-top: 42px;
130 }
131 h5, h6 {
132 font-size: 14px;
133 }
134 #n-copyright-notice {
135 border-bottom: 1px solid #ddd;
136 padding-bottom: 1em;
137 margin-bottom: 1em;
138 }
139 /* general structure */
140 p {
141 padding: 0;
142 margin: 0 0 1em 0;
143 text-align: left;
144 }
145 div, span {
146 position: relative;
147 }
148 div {
149 margin: 0;
150 }
151 .alignRight.art-text {
152 background-color: #f9f9f9;
153 border: 1px solid #eee;
154 border-radius: 3px;
155 padding: 1em 1em 0;
156 margin-bottom: 1.5em;
157 }
158 .alignRight.art-text pre {
159 padding: 0;
160 }
161 .alignRight {
162 margin: 1em 0;
163 }
164 .alignRight > *:first-child {
165 border: none;
166 margin: 0;
167 float: right;
168 clear: both;
169 }
170 .alignRight > *:nth-child(2) {
171 clear: both;
172 display: block;
173 border: none;
174 }
175 svg {
176 display: block;
177 }
178 .alignCenter.art-text {
179 background-color: #f9f9f9;
180 border: 1px solid #eee;
181 border-radius: 3px;
182 padding: 1em 1em 0;
183 margin-bottom: 1.5em;
184 }
185 .alignCenter.art-text pre {
186 padding: 0;
187 }
188 .alignCenter {
189 margin: 1em 0;
190 }
191 .alignCenter > *:first-child {
192 border: none;
193 /* this isn't optimal, but it's an existence proof. PrinceXML doesn't
194 support flexbox yet.
195 */
196 display: table;
197 margin: 0 auto;
198 }
199
200 /* lists */
201 ol, ul {
202 padding: 0;
203 margin: 0 0 1em 2em;
204 }
205 ol ol, ul ul, ol ul, ul ol {
206 margin-left: 1em;
207 }
208 li {
209 margin: 0 0 0.25em 0;
210 }
211 .ulCompact li {
212 margin: 0;
213 }
214 ul.empty, .ulEmpty {
215 list-style-type: none;
216 }
217 ul.empty li, .ulEmpty li {
218 margin-top: 0.5em;
219 }
220 ul.ulBare, li.ulBare {
221 margin-left: 0em !important;
222 }
223 ul.compact, .ulCompact,
224 ol.compact, .olCompact {
225 line-height: 100%;
226 margin: 0 0 0 2em;
227 }
228
229 /* definition lists */
230 dl {
231 }
232 dl > dt {
233 float: left;
234 margin-right: 1em;
235 }
236 /*
237 dl.nohang > dt {
238 float: none;
239 }
240 */
241 dl > dd {
242 margin-bottom: .8em;
243 min-height: 1.3em;
244 }
245 dl.compact > dd, .dlCompact > dd {
246 margin-bottom: 0em;
247 }
248 dl > dd > dl {
249 margin-top: 0.5em;
250 margin-bottom: 0em;
251 }
252
253 /* links */
254 a {
255 text-decoration: none;
256 }
257 a[href] {
258 color: #22e; /* Arlen: WCAG 2019 */
259 }
260 a[href]:hover {
261 background-color: #f2f2f2;
262 }
263 figcaption a[href],
264 a[href].selfRef {
265 color: #222;
266 }
267 /* XXX probably not this:
268 a.selfRef:hover {
269 background-color: transparent;
270 cursor: default;
271 } */
272
273 /* Figures */
274 tt, code, pre, code {
275 background-color: #f9f9f9;
276 font-family: 'Roboto Mono', monospace;
277 }
278 pre {
279 border: 1px solid #eee;
280 margin: 0;
281 padding: 1em;
282 }
283 img {
284 max-width: 100%;
285 }
286 figure {
287 margin: 0;
288 }
289 figure blockquote {
290 margin: 0.8em 0.4em 0.4em;
291 }
292 figcaption {
293 font-style: italic;
294 margin: 0 0 1em 0;
295 }
296 @media screen {
297 pre {
298 overflow-x: auto;
299 max-width: 100%;
300 max-width: calc(100% - 22px);
301 }
302 }
303
304 /* aside, blockquote */
305 aside, blockquote {
306 margin-left: 0;
307 padding: 1.2em 2em;
308 }
309 blockquote {
310 background-color: #f9f9f9;
311 color: #111; /* Arlen: WCAG 2019 */
312 border: 1px solid #ddd;
313 border-radius: 3px;
314 margin: 1em 0;
315 }
316 cite {
317 display: block;
318 text-align: right;
319 font-style: italic;
320 }
321
322 /* tables */
323 table {
324 width: 100%;
325 margin: 0 0 1em;
326 border-collapse: collapse;
327 border: 1px solid #eee;
328 }
329 th, td {
330 text-align: left;
331 vertical-align: top;
332 padding: 0.5em 0.75em;
333 }
334 th {
335 text-align: left;
336 background-color: #e9e9e9;
337 }
338 tr:nth-child(2n+1) > td {
339 background-color: #f5f5f5;
340 }
341 table caption {
342 font-style: italic;
343 margin: 0;
344 padding: 0;
345 text-align: left;
346 }
347 table p {
348 /* XXX to avoid bottom margin on table row signifiers. If paragraphs should
349 be allowed within tables more generally, it would be far better to select on a class. */
350 margin: 0;
351 }
352
353 /* pilcrow */
354 a.pilcrow {
355 color: #666; /* Arlen: AHDJ 2019 */
356 text-decoration: none;
357 visibility: hidden;
358 user-select: none;
359 -ms-user-select: none;
360 -o-user-select:none;
361 -moz-user-select: none;
362 -khtml-user-select: none;
363 -webkit-user-select: none;
364 -webkit-touch-callout: none;
365 }
366 @media screen {
367 aside:hover > a.pilcrow,
368 p:hover > a.pilcrow,
369 blockquote:hover > a.pilcrow,
370 div:hover > a.pilcrow,
371 li:hover > a.pilcrow,
372 pre:hover > a.pilcrow {
373 visibility: visible;
374 }
375 a.pilcrow:hover {
376 background-color: transparent;
377 }
378 }
379
380 /* misc */
381 hr {
382 border: 0;
383 border-top: 1px solid #eee;
384 }
385 .bcp14 {
386 font-variant: small-caps;
387 }
388
389 .role {
390 font-variant: all-small-caps;
391 }
392
393 /* info block */
394 #identifiers {
395 margin: 0;
396 font-size: 0.9em;
397 }
398 #identifiers dt {
399 width: 3em;
400 clear: left;
401 }
402 #identifiers dd {
403 float: left;
404 margin-bottom: 0;
405 }
406 /* Fix PDF info block run off issue */
407 @media print {
408 #identifiers dd {
409 float: none;
410 }
411 }
412 #identifiers .authors .author {
413 display: inline-block;
414 margin-right: 1.5em;
415 }
416 #identifiers .authors .org {
417 font-style: italic;
418 }
419
420 /* The prepared/rendered info at the very bottom of the page */
421 .docInfo {
422 color: #666; /* Arlen: WCAG 2019 */
423 font-size: 0.9em;
424 font-style: italic;
425 margin-top: 2em;
426 }
427 .docInfo .prepared {
428 float: left;
429 }
430 .docInfo .prepared {
431 float: right;
432 }
433
434 /* table of contents */
435 #toc {
436 padding: 0.75em 0 2em 0;
437 margin-bottom: 1em;
438 }
439 nav.toc ul {
440 margin: 0 0.5em 0 0;
441 padding: 0;
442 list-style: none;
443 }
444 nav.toc li {
445 line-height: 1.3em;
446 margin: 0.75em 0;
447 padding-left: 1.2em;
448 text-indent: -1.2em;
449 }
450 /* references */
451 .references dt {
452 text-align: right;
453 font-weight: bold;
454 min-width: 7em;
455 }
456 .references dd {
457 margin-left: 8em;
458 overflow: auto;
459 }
460
461 .refInstance {
462 margin-bottom: 1.25em;
463 }
464
465 .references .ascii {
466 margin-bottom: 0.25em;
467 }
468
469 /* index */
470 .index ul {
471 margin: 0 0 0 1em;
472 padding: 0;
473 list-style: none;
474 }
475 .index ul ul {
476 margin: 0;
477 }
478 .index li {
479 margin: 0;
480 text-indent: -2em;
481 padding-left: 2em;
482 padding-bottom: 5px;
483 }
484 .indexIndex {
485 margin: 0.5em 0 1em;
486 }
487 .index a {
488 font-weight: 700;
489 }
490 /* make the index two-column on all but the smallest screens */
491 @media (min-width: 600px) {
492 .index ul {
493 -moz-column-count: 2;
494 -moz-column-gap: 20px;
495 }
496 .index ul ul {
497 -moz-column-count: 1;
498 -moz-column-gap: 0;
499 }
500 }
501
502 /* authors */
503 address.vcard {
504 font-style: normal;
505 margin: 1em 0;
506 }
507
508 address.vcard .nameRole {
509 font-weight: 700;
510 margin-left: 0;
511 }
512 address.vcard .label {
513 font-family: "Noto Sans",Arial,Helvetica,sans-serif;
514 margin: 0.5em 0;
515 }
516 address.vcard .type {
517 display: none;
518 }
519 .alternative-contact {
520 margin: 1.5em 0 1em;
521 }
522 hr.addr {
523 border-top: 1px dashed;
524 margin: 0;
525 color: #ddd;
526 max-width: calc(100% - 16px);
527 }
528
529 /* temporary notes */
530 .rfcEditorRemove::before {
531 position: absolute;
532 top: 0.2em;
533 right: 0.2em;
534 padding: 0.2em;
535 content: "The RFC Editor will remove this note";
536 color: #9e2a00; /* Arlen: WCAG 2019 */
537 background-color: #ffd; /* Arlen: WCAG 2019 */
538 }
539 .rfcEditorRemove {
540 position: relative;
541 padding-top: 1.8em;
542 background-color: #ffd; /* Arlen: WCAG 2019 */
543 border-radius: 3px;
544 }
545 .cref {
546 background-color: #ffd; /* Arlen: WCAG 2019 */
547 padding: 2px 4px;
548 }
549 .crefSource {
550 font-style: italic;
551 }
552 /* alternative layout for smaller screens */
553 @media screen and (max-width: 1023px) {
554 body {
555 padding-top: 2em;
556 }
557 #title {
558 padding: 1em 0;
559 }
560 h1 {
561 font-size: 24px;
562 }
563 h2 {
564 font-size: 20px;
565 margin-top: -18px; /* provide offset for in-page anchors */
566 padding-top: 38px;
567 }
568 #identifiers dd {
569 max-width: 60%;
570 }
571 #toc {
572 position: fixed;
573 z-index: 2;
574 top: 0;
575 right: 0;
576 padding: 0;
577 margin: 0;
578 background-color: inherit;
579 border-bottom: 1px solid #ccc;
580 }
581 #toc h2 {
582 margin: -1px 0 0 0;
583 padding: 4px 0 4px 6px;
584 padding-right: 1em;
585 min-width: 190px;
586 font-size: 1.1em;
587 text-align: right;
588 background-color: #444;
589 color: white;
590 cursor: pointer;
591 }
592 #toc h2::before { /* css hamburger */
593 float: right;
594 position: relative;
595 width: 1em;
596 height: 1px;
597 left: -164px;
598 margin: 6px 0 0 0;
599 background: white none repeat scroll 0 0;
600 box-shadow: 0 4px 0 0 white, 0 8px 0 0 white;
601 content: "";
602 }
603 #toc nav {
604 display: none;
605 padding: 0.5em 1em 1em;
606 overflow: auto;
607 height: calc(100vh - 48px);
608 border-left: 1px solid #ddd;
609 }
610 }
611
612 /* alternative layout for wide screens */
613 @media screen and (min-width: 1024px) {
614 body {
615 max-width: 724px;
616 margin: 42px auto;
617 padding-left: 1.5em;
618 padding-right: 29em;
619 }
620 #toc {
621 position: fixed;
622 top: 42px;
623 right: 42px;
624 width: 25%;
625 margin: 0;
626 padding: 0 1em;
627 z-index: 1;
628 }
629 #toc h2 {
630 border-top: none;
631 border-bottom: 1px solid #ddd;
632 font-size: 1em;
633 font-weight: normal;
634 margin: 0;
635 padding: 0.25em 1em 1em 0;
636 }
637 #toc nav {
638 display: block;
639 height: calc(90vh - 84px);
640 bottom: 0;
641 padding: 0.5em 0 0;
642 overflow: auto;
643 }
644 img { /* future proofing */
645 max-width: 100%;
646 height: auto;
647 }
648 }
649
650 /* pagination */
651 @media print {
652 body {
653
654 width: 100%;
655 }
656 p {
657 orphans: 3;
658 widows: 3;
659 }
660 #n-copyright-notice {
661 border-bottom: none;
662 }
663 #toc, #n-introduction {
664 page-break-before: always;
665 }
666 #toc {
667 border-top: none;
668 padding-top: 0;
669 }
670 figure, pre {
671 page-break-inside: avoid;
672 }
673 figure {
674 overflow: scroll;
675 }
676 h1, h2, h3, h4, h5, h6 {
677 page-break-after: avoid;
678 }
679 h2+*, h3+*, h4+*, h5+*, h6+* {
680 page-break-before: avoid;
681 }
682 pre {
683 white-space: pre-wrap;
684 word-wrap: break-word;
685 font-size: 10pt;
686 }
687 table {
688 border: 1px solid #ddd;
689 }
690 td {
691 border-top: 1px solid #ddd;
692 }
693 }
694
695 /* This is commented out here, as the string-set: doesn't
696 pass W3C validation currently */
697 /*
698 .ears thead .left {
699 string-set: ears-top-left content();
700 }
701
702 .ears thead .center {
703 string-set: ears-top-center content();
704 }
705
706 .ears thead .right {
707 string-set: ears-top-right content();
708 }
709
710 .ears tfoot .left {
711 string-set: ears-bottom-left content();
712 }
713
714 .ears tfoot .center {
715 string-set: ears-bottom-center content();
716 }
717
718 .ears tfoot .right {
719 string-set: ears-bottom-right content();
720 }
721 */
722
723 @page :first {
724 padding-top: 0;
725 @top-left {
726 content: normal;
727 border: none;
728 }
729 @top-center {
730 content: normal;
731 border: none;
732 }
733 @top-right {
734 content: normal;
735 border: none;
736 }
737 }
738
739 @page {
740 size: A4;
741 margin-bottom: 45mm;
742 padding-top: 20px;
743 /* The follwing is commented out here, but set appropriately by in code, as
744 the content depends on the document */
745 /*
746 @top-left {
747 content: 'Internet-Draft';
748 vertical-align: bottom;
749 border-bottom: solid 1px #ccc;
750 }
751 @top-left {
752 content: string(ears-top-left);
753 vertical-align: bottom;
754 border-bottom: solid 1px #ccc;
755 }
756 @top-center {
757 content: string(ears-top-center);
758 vertical-align: bottom;
759 border-bottom: solid 1px #ccc;
760 }
761 @top-right {
762 content: string(ears-top-right);
763 vertical-align: bottom;
764 border-bottom: solid 1px #ccc;
765 }
766 @bottom-left {
767 content: string(ears-bottom-left);
768 vertical-align: top;
769 border-top: solid 1px #ccc;
770 }
771 @bottom-center {
772 content: string(ears-bottom-center);
773 vertical-align: top;
774 border-top: solid 1px #ccc;
775 }
776 @bottom-right {
777 content: '[Page ' counter(page) ']';
778 vertical-align: top;
779 border-top: solid 1px #ccc;
780 }
781 */
782
783 }
784
785 /* Changes introduced to fix issues found during implementation */
786 /* Make sure links are clickable even if overlapped by following H* */
787 a {
788 z-index: 2;
789 }
790 /* Separate body from document info even without intervening H1 */
791 section {
792 clear: both;
793 }
794
795
796 /* Top align author divs, to avoid names without organization dropping level with org names */
797 .author {
798 vertical-align: top;
799 }
800
801 /* Leave room in document info to show Internet-Draft on one line */
802 #identifiers dt {
803 width: 8em;
804 }
805
806 /* Don't waste quite as much whitespace between label and value in doc info */
807 #identifiers dd {
808 margin-left: 1em;
809 }
810
811 /* Give floating toc a background color (needed when it's a div inside section */
812 #toc {
813 background-color: white;
814 }
815
816 /* Make the collapsed ToC header render white on gray also when it's a link */
817 @media screen and (max-width: 1023px) {
818 #toc h2 a,
819 #toc h2 a:link,
820 #toc h2 a:focus,
821 #toc h2 a:hover,
822 #toc a.toplink,
823 #toc a.toplink:hover {
824 color: white;
825 background-color: #444;
826 text-decoration: none;
827 }
828 }
829
830 /* Give the bottom of the ToC some whitespace */
831 @media screen and (min-width: 1024px) {
832 #toc {
833 padding: 0 0 1em 1em;
834 }
835 }
836
837 /* Style section numbers with more space between number and title */
838 .section-number {
839 padding-right: 0.5em;
840 }
841
842 /* prevent monospace from becoming overly large */
843 tt, code, pre, code {
844 font-size: 95%;
845 }
846
847 /* Fix the height/width aspect for ascii art*/
848 pre.sourcecode,
849 .art-text pre {
850 line-height: 1.12;
851 }
852
853
854 /* Add styling for a link in the ToC that points to the top of the document */
855 a.toplink {
856 float: right;
857 margin-right: 0.5em;
858 }
859
860 /* Fix the dl styling to match the RFC 7992 attributes */
861 dl > dt,
862 dl.dlParallel > dt {
863 float: left;
864 margin-right: 1em;
865 }
866 dl.dlNewline > dt {
867 float: none;
868 }
869
870 /* Provide styling for table cell text alignment */
871 table td.text-left,
872 table th.text-left {
873 text-align: left;
874 }
875 table td.text-center,
876 table th.text-center {
877 text-align: center;
878 }
879 table td.text-right,
880 table th.text-right {
881 text-align: right;
882 }
883
884 /* Make the alternative author contact informatio look less like just another
885 author, and group it closer with the primary author contact information */
886 .alternative-contact {
887 margin: 0.5em 0 0.25em 0;
888 }
889 address .non-ascii {
890 margin: 0 0 0 2em;
891 }
892
893 /* With it being possible to set tables with alignment
894 left, center, and right, { width: 100%; } does not make sense */
895 table {
896 width: auto;
897 }
898
899 /* Avoid reference text that sits in a block with very wide left margin,
900 because of a long floating dt label.*/
901 .references dd {
902 overflow: visible;
903 }
904
905 /* Control caption placement */
906 caption {
907 caption-side: bottom;
908 }
909
910 /* Limit the width of the author address vcard, so names in right-to-left
911 script don't end up on the other side of the page. */
912
913 address.vcard {
914 max-width: 30em;
915 margin-right: auto;
916 }
917
918 /* For address alignment dependent on LTR or RTL scripts */
919 address div.left {
920 text-align: left;
921 }
922 address div.right {
923 text-align: right;
924 }
925
926 /* Provide table alignment support. We can't use the alignX classes above
927 since they do unwanted things with caption and other styling. */
928 table.right {
929 margin-left: auto;
930 margin-right: 0;
931 }
932 table.center {
933 margin-left: auto;
934 margin-right: auto;
935 }
936 table.left {
937 margin-left: 0;
938 margin-right: auto;
939 }
940
941 /* Give the table caption label the same styling as the figcaption */
942 caption a[href] {
943 color: #222;
944 }
945
946 @media print {
947 .toplink {
948 display: none;
949 }
950
951 /* avoid overwriting the top border line with the ToC header */
952 #toc {
953 padding-top: 1px;
954 }
955
956 /* Avoid page breaks inside dl and author address entries */
957 .vcard {
958 page-break-inside: avoid;
959 }
960
961 }
962 /* Tweak the bcp14 keyword presentation */
963 .bcp14 {
964 font-variant: small-caps;
965 font-weight: bold;
966 font-size: 0.9em;
967 }
968 /* Tweak the invisible space above H* in order not to overlay links in text above */
969 h2 {
970 margin-top: -18px; /* provide offset for in-page anchors */
971 padding-top: 31px;
972 }
973 h3 {
974 margin-top: -18px; /* provide offset for in-page anchors */
975 padding-top: 24px;
976 }
977 h4 {
978 margin-top: -18px; /* provide offset for in-page anchors */
979 padding-top: 24px;
980 }
981 /* Float artwork pilcrow to the right */
982 @media screen {
983 .artwork a.pilcrow {
984 display: block;
985 line-height: 0.7;
986 margin-top: 0.15em;
987 }
988 }
989 /* Make pilcrows on dd visible */
990 @media screen {
991 dd:hover > a.pilcrow {
992 visibility: visible;
993 }
994 }
995 /* Make the placement of figcaption match that of a table's caption
996 by removing the figure's added bottom margin */
997 .alignLeft.art-text,
998 .alignCenter.art-text,
999 .alignRight.art-text {
1000 margin-bottom: 0;
1001 }
1002 .alignLeft,
1003 .alignCenter,
1004 .alignRight {
1005 margin: 1em 0 0 0;
1006 }
1007 /* In print, the pilcrow won't show on hover, so prevent it from taking up space,
1008 possibly even requiring a new line */
1009 @media print {
1010 a.pilcrow {
1011 display: none;
1012 }
1013 }
1014 /* Styling for the external metadata */
1015 div#external-metadata {
1016 background-color: #eee;
1017 padding: 0.5em;
1018 margin-bottom: 0.5em;
1019 display: none;
1020 }
1021 div#internal-metadata {
1022 padding: 0.5em; /* to match the external-metadata padding */
1023 }
1024 /* Styling for title RFC Number */
1025 h1#rfcnum {
1026 clear: both;
1027 margin: 0 0 -1em;
1028 padding: 1em 0 0 0;
1029 }
1030 /* Make .olPercent look the same as <ol><li> */
1031 dl.olPercent > dd {
1032 margin-bottom: 0.25em;
1033 min-height: initial;
1034 }
1035 /* Give aside some styling to set it apart */
1036 aside {
1037 border-left: 1px solid #ddd;
1038 margin: 1em 0 1em 2em;
1039 padding: 0.2em 2em;
1040 }
1041 aside > dl,
1042 aside > ol,
1043 aside > ul,
1044 aside > table,
1045 aside > p {
1046 margin-bottom: 0.5em;
1047 }
1048 /* Additional page break settings */
1049 @media print {
1050 figcaption, table caption {
1051 page-break-before: avoid;
1052 }
1053 }
1054 /* Font size adjustments for print */
1055 @media print {
1056 body { font-size: 10pt; line-height: normal; max-width: 96%; }
1057 h1 { font-size: 1.72em; padding-top: 1.5em; } /* 1*1.2*1.2*1.2 */
1058 h2 { font-size: 1.44em; padding-top: 1.5em; } /* 1*1.2*1.2 */
1059 h3 { font-size: 1.2em; padding-top: 1.5em; } /* 1*1.2 */
1060 h4 { font-size: 1em; padding-top: 1.5em; }
1061 h5, h6 { font-size: 1em; margin: initial; padding: 0.5em 0 0.3em; }
1062 }
1063 /* Sourcecode margin in print, when there's no pilcrow */
1064 @media print {
1065 .artwork,
1066 .sourcecode {
1067 margin-bottom: 1em;
1068 }
1069 }
1070 /* Avoid narrow tables forcing too narrow table captions, which may render badly */
1071 table {
1072 min-width: 20em;
1073 }
1074 /* ol type a */
1075 ol.type-a { list-style-type: lower-alpha; }
1076 ol.type-A { list-style-type: upper-alpha; }
1077 ol.type-i { list-style-type: lower-roman; }
1078 ol.type-I { list-style-type: lower-roman; }
1079 /* Apply the print table and row borders in general, on request from the RPC,
1080 and increase the contrast between border and odd row background sligthtly */
1081 table {
1082 border: 1px solid #ddd;
1083 }
1084 td {
1085 border-top: 1px solid #ddd;
1086 }
1087 tr:nth-child(2n+1) > td {
1088 background-color: #f8f8f8;
1089 }
1090 /* Use style rules to govern display of the TOC. */
1091 @media screen and (max-width: 1023px) {
1092 #toc nav { display: none; }
1093 #toc.active nav { display: block; }
1094 }
1095 /* Add support for keepWithNext */
1096 .keepWithNext {
1097 break-after: avoid-page;
1098 break-after: avoid-page;
1099 }
1100 /* Add support for keepWithPrevious */
1101 .keepWithPrevious {
1102 break-before: avoid-page;
1103 }
1104 /* Change the approach to avoiding breaks inside artwork etc. */
1105 figure, pre, table, .artwork, .sourcecode {
1106 break-before: auto;
1107 break-after: auto;
1108 }
1109 /* Avoid breaks between <dt> and <dd> */
1110 dl {
1111 break-before: auto;
1112 break-inside: auto;
1113 }
1114 dt {
1115 break-before: auto;
1116 break-after: avoid-page;
1117 }
1118 dd {
1119 break-before: avoid-page;
1120 break-after: auto;
1121 orphans: 3;
1122 widows: 3
1123 }
1124 span.break, dd.break {
1125 margin-bottom: 0;
1126 min-height: 0;
1127 break-before: auto;
1128 break-inside: auto;
1129 break-after: auto;
1130 }
1131 /* Undo break-before ToC */
1132 @media print {
1133 #toc {
1134 break-before: auto;
1135 }
1136 }
1137 /* Text in compact lists should not get extra bottim margin space,
1138 since that would makes the list not compact */
1139 ul.compact p, .ulCompact p,
1140 ol.compact p, .olCompact p {
1141 margin: 0;
1142 }
1143 /* But the list as a whole needs the extra space at the end */
1144 section ul.compact,
1145 section .ulCompact,
1146 section ol.compact,
1147 section .olCompact {
1148 margin-bottom: 1em; /* same as p not within ul.compact etc. */
1149 }
1150 /* The tt and code background above interferes with for instance table cell
1151 backgrounds. Changed to something a bit more selective. */
1152 tt, code {
1153 background-color: transparent;
1154 }
1155 p tt, p code, li tt, li code {
1156 background-color: #f8f8f8;
1157 }
1158 /* Tweak the pre margin -- 0px doesn't come out well */
1159 pre {
1160 margin-top: 0.5px;
1161 }
1162 /* Tweak the comact list text */
1163 ul.compact, .ulCompact,
1164 ol.compact, .olCompact,
1165 dl.compact, .dlCompact {
1166 line-height: normal;
1167 }
1168 /* Don't add top margin for nested lists */
1169 li > ul, li > ol, li > dl,
1170 dd > ul, dd > ol, dd > dl,
1171 dl > dd > dl {
1172 margin-top: initial;
1173 }
1174 /* Elements that should not be rendered on the same line as a <dt> */
1175 /* This should match the element list in writer.text.TextWriter.render_dl() */
1176 dd > div.artwork:first-child,
1177 dd > aside:first-child,
1178 dd > figure:first-child,
1179 dd > ol:first-child,
1180 dd > div:first-child > pre.sourcecode,
1181 dd > table:first-child,
1182 dd > ul:first-child {
1183 clear: left;
1184 }
1185 /* fix for weird browser behaviour when <dd/> is empty */
1186 dt+dd:empty::before{
1187 content: "\00a0";
1188 }
1189 /* Make paragraph spacing inside <li> smaller than in body text, to fit better within the list */
1190 li > p {
1191 margin-bottom: 0.5em
1192 }
1193 /* Don't let p margin spill out from inside list items */
1194 li > p:last-of-type {
1195 margin-bottom: 0;
1196 }
1197 </style>
1198 <link href="rfc-local.css" rel="stylesheet" type="text/css">
1199 <link href="https://dx.doi.org/10.17487/rfc9222" rel="alternate">
1200 <link href="urn:issn:2070-1721" rel="alternate">
1201 <link href="https://datatracker.ietf.org/doc/draft-ietf-anima-asa-guidelines-7" rel="prev">
1202 </head>
1203 <body>
1204 <script src="https://www.rfc-editor.org/js/metadata.min.js"></script>
1205 <table class="ears">
1206 <thead><tr>
1207 <td class="left">RFC 9222</td>
1208 <td class="center">ASA Guidelines</td>
1209 <td class="right">March 2022</td>
1210 </tr></thead>
1211 <tfoot><tr>
1212 <td class="left">Carpenter, et al.</td>
1213 <td class="center">Informational</td>
1214 <td class="right">[Page]</td>
1215 </tr></tfoot>
1216 </table>
1217 <div id="external-metadata" class="document-information"></div>
1218 <div id="internal-metadata" class="document-information">
1219 <dl id="identifiers">
1220 <dt class="label-stream">Stream:</dt>
1221 <dd class="stream">Internet Engineering Task Force (IETF)</dd>
1222 <dt class="label-rfc">RFC:</dt>
1223 <dd class="rfc"><a href="https://www.rfc-editor.org/rfc/rfc9222" class="eref">9222</a></dd>
1224 <dt class="label-category">Category:</dt>
1225 <dd class="category">Informational</dd>
1226 <dt class="label-published">Published:</dt>
1227 <dd class="published">
1228 <time datetime="2022-03" class="published">March 2022</time>
1229 </dd>
1230 <dt class="label-issn">ISSN:</dt>
1231 <dd class="issn">2070-1721</dd>
1232 <dt class="label-authors">Authors:</dt>
1233 <dd class="authors">
1234 <div class="author">
1235 <div class="author-name">B. Carpenter</div>
1236 <div class="org">Univ. of Auckland</div>
1237 </div>
1238 <div class="author">
1239 <div class="author-name">L. Ciavaglia</div>
1240 <div class="org">Rakuten Mobile</div>
1241 </div>
1242 <div class="author">
1243 <div class="author-name">S. Jiang</div>
1244 <div class="org">Huawei Technologies Co., Ltd</div>
1245 </div>
1246 <div class="author">
1247 <div class="author-name">P. Peloso</div>
1248 <div class="org">Nokia</div>
1249 </div>
1250 </dd>
1251 </dl>
1252 </div>
1253 <h1 id="rfcnum">RFC 9222</h1>
1254 <h1 id="title">Guidelines for Autonomic Service Agents</h1>
1255 <section id="section-abstract">
1256 <h2 id="abstract"><a href="#abstract" class="selfRef">Abstract</a></h2>
1257 <p id="section-abstract-1">This document proposes guidelines for the design of Autonomic Service
1258 Agents for autonomic networks. Autonomic Service Agents, together with
1259 the Autonomic Network Infrastructure, the Autonomic Control Plane, and
1260 the GeneRic Autonomic Signaling Protocol, constitute base elements of an
1261 autonomic networking ecosystem.<a href="#section-abstract-1" class="pilcrow">¶</a></p>
1262 </section>
1263 <div id="status-of-memo">
1264 <section id="section-boilerplate.1">
1265 <h2 id="name-status-of-this-memo">
1266 <a href="#name-status-of-this-memo" class="section-name selfRef">Status of This Memo</a>
1267 </h2>
1268 <p id="section-boilerplate.1-1">
1269 This document is not an Internet Standards Track specification; it is
1270 published for informational purposes.<a href="#section-boilerplate.1-1" class="pilcrow">¶</a></p>
1271 <p id="section-boilerplate.1-2">
1272 This document is a product of the Internet Engineering Task Force
1273 (IETF). It represents the consensus of the IETF community. It has
1274 received public review and has been approved for publication by the
1275 Internet Engineering Steering Group (IESG). Not all documents
1276 approved by the IESG are candidates for any level of Internet
1277 Standard; see Section 2 of RFC 7841.<a href="#section-boilerplate.1-2" class="pilcrow">¶</a></p>
1278 <p id="section-boilerplate.1-3">
1279 Information about the current status of this document, any
1280 errata, and how to provide feedback on it may be obtained at
1281 <span><a href="https://www.rfc-editor.org/info/rfc9222">https://www.rfc-editor.org/info/rfc9222</a></span>.<a href="#section-boilerplate.1-3" class="pilcrow">¶</a></p>
1282 </section>
1283 </div>
1284 <div id="copyright">
1285 <section id="section-boilerplate.2">
1286 <h2 id="name-copyright-notice">
1287 <a href="#name-copyright-notice" class="section-name selfRef">Copyright Notice</a>
1288 </h2>
1289 <p id="section-boilerplate.2-1">
1290 Copyright (c) 2022 IETF Trust and the persons identified as the
1291 document authors. All rights reserved.<a href="#section-boilerplate.2-1" class="pilcrow">¶</a></p>
1292 <p id="section-boilerplate.2-2">
1293 This document is subject to BCP 78 and the IETF Trust's Legal
1294 Provisions Relating to IETF Documents
1295 (<span><a href="https://trustee.ietf.org/license-info">https://trustee.ietf.org/license-info</a></span>) in effect on the date of
1296 publication of this document. Please review these documents
1297 carefully, as they describe your rights and restrictions with
1298 respect to this document. Code Components extracted from this
1299 document must include Revised BSD License text as described in
1300 Section 4.e of the Trust Legal Provisions and are provided without
1301 warranty as described in the Revised BSD License.<a href="#section-boilerplate.2-2" class="pilcrow">¶</a></p>
1302 </section>
1303 </div>
1304 <div id="toc">
1305 <section id="section-toc.1">
1306 <a href="#" onclick="scroll(0,0)" class="toplink">▲</a><h2 id="name-table-of-contents">
1307 <a href="#name-table-of-contents" class="section-name selfRef">Table of Contents</a>
1308 </h2>
1309 <nav class="toc"><ul class="compact toc ulBare ulEmpty">
1310 <li class="compact toc ulBare ulEmpty" id="section-toc.1-1.1">
1311 <p id="section-toc.1-1.1.1" class="keepWithNext"><a href="#section-1" class="xref">1</a>.  <a href="#name-introduction" class="xref">Introduction</a></p>
1312 </li>
1313 <li class="compact toc ulBare ulEmpty" id="section-toc.1-1.2">
1314 <p id="section-toc.1-1.2.1" class="keepWithNext"><a href="#section-2" class="xref">2</a>.  <a href="#name-terminology" class="xref">Terminology</a></p>
1315 </li>
1316 <li class="compact toc ulBare ulEmpty" id="section-toc.1-1.3">
1317 <p id="section-toc.1-1.3.1" class="keepWithNext"><a href="#section-3" class="xref">3</a>.  <a href="#name-logical-structure-of-an-aut" class="xref">Logical Structure of an Autonomic Service Agent</a></p>
1318 </li>
1319 <li class="compact toc ulBare ulEmpty" id="section-toc.1-1.4">
1320 <p id="section-toc.1-1.4.1"><a href="#section-4" class="xref">4</a>.  <a href="#name-interaction-with-the-autono" class="xref">Interaction with the Autonomic Networking Infrastructure</a></p>
1321 <ul class="compact toc ulBare ulEmpty">
1322 <li class="compact toc ulBare ulEmpty" id="section-toc.1-1.4.2.1">
1323 <p id="section-toc.1-1.4.2.1.1"><a href="#section-4.1" class="xref">4.1</a>.  <a href="#name-interaction-with-the-securi" class="xref">Interaction with the Security Mechanisms</a></p>
1324 </li>
1325 <li class="compact toc ulBare ulEmpty" id="section-toc.1-1.4.2.2">
1326 <p id="section-toc.1-1.4.2.2.1"><a href="#section-4.2" class="xref">4.2</a>.  <a href="#name-interaction-with-the-autonom" class="xref">Interaction with the Autonomic Control Plane</a></p>
1327 </li>
1328 <li class="compact toc ulBare ulEmpty" id="section-toc.1-1.4.2.3">
1329 <p id="section-toc.1-1.4.2.3.1"><a href="#section-4.3" class="xref">4.3</a>.  <a href="#name-interaction-with-grasp-and-" class="xref">Interaction with GRASP and its API</a></p>
1330 </li>
1331 <li class="compact toc ulBare ulEmpty" id="section-toc.1-1.4.2.4">
1332 <p id="section-toc.1-1.4.2.4.1"><a href="#section-4.4" class="xref">4.4</a>.  <a href="#name-interaction-with-policy-mec" class="xref">Interaction with Policy Mechanisms</a></p>
1333 </li>
1334 </ul>
1335 </li>
1336 <li class="compact toc ulBare ulEmpty" id="section-toc.1-1.5">
1337 <p id="section-toc.1-1.5.1"><a href="#section-5" class="xref">5</a>.  <a href="#name-interaction-with-non-autono" class="xref">Interaction with Non-autonomic Components and Systems</a></p>
1338 </li>
1339 <li class="compact toc ulBare ulEmpty" id="section-toc.1-1.6">
1340 <p id="section-toc.1-1.6.1"><a href="#section-6" class="xref">6</a>.  <a href="#name-design-of-grasp-objectives" class="xref">Design of GRASP Objectives</a></p>
1341 </li>
1342 <li class="compact toc ulBare ulEmpty" id="section-toc.1-1.7">
1343 <p id="section-toc.1-1.7.1"><a href="#section-7" class="xref">7</a>.  <a href="#name-life-cycle" class="xref">Life Cycle</a></p>
1344 <ul class="compact toc ulBare ulEmpty">
1345 <li class="compact toc ulBare ulEmpty" id="section-toc.1-1.7.2.1">
1346 <p id="section-toc.1-1.7.2.1.1"><a href="#section-7.1" class="xref">7.1</a>.  <a href="#name-installation-phase" class="xref">Installation Phase</a></p>
1347 <ul class="compact toc ulBare ulEmpty">
1348 <li class="compact toc ulBare ulEmpty" id="section-toc.1-1.7.2.1.2.1">
1349 <p id="section-toc.1-1.7.2.1.2.1.1"><a href="#section-7.1.1" class="xref">7.1.1</a>.  <a href="#name-installation-phase-inputs-a" class="xref">Installation Phase Inputs and Outputs</a></p>
1350 </li>
1351 </ul>
1352 </li>
1353 <li class="compact toc ulBare ulEmpty" id="section-toc.1-1.7.2.2">
1354 <p id="section-toc.1-1.7.2.2.1"><a href="#section-7.2" class="xref">7.2</a>.  <a href="#name-instantiation-phase" class="xref">Instantiation Phase</a></p>
1355 <ul class="compact toc ulBare ulEmpty">
1356 <li class="compact toc ulBare ulEmpty" id="section-toc.1-1.7.2.2.2.1">
1357 <p id="section-toc.1-1.7.2.2.2.1.1"><a href="#section-7.2.1" class="xref">7.2.1</a>.  <a href="#name-operators-goal" class="xref">Operator's Goal</a></p>
1358 </li>
1359 <li class="compact toc ulBare ulEmpty" id="section-toc.1-1.7.2.2.2.2">
1360 <p id="section-toc.1-1.7.2.2.2.2.1"><a href="#section-7.2.2" class="xref">7.2.2</a>.  <a href="#name-instantiation-phase-inputs-" class="xref">Instantiation Phase Inputs and Outputs</a></p>
1361 </li>
1362 <li class="compact toc ulBare ulEmpty" id="section-toc.1-1.7.2.2.2.3">
1363 <p id="section-toc.1-1.7.2.2.2.3.1"><a href="#section-7.2.3" class="xref">7.2.3</a>.  <a href="#name-instantiation-phase-require" class="xref">Instantiation Phase Requirements</a></p>
1364 </li>
1365 </ul>
1366 </li>
1367 <li class="compact toc ulBare ulEmpty" id="section-toc.1-1.7.2.3">
1368 <p id="section-toc.1-1.7.2.3.1"><a href="#section-7.3" class="xref">7.3</a>.  <a href="#name-operation-phase" class="xref">Operation Phase</a></p>
1369 </li>
1370 <li class="compact toc ulBare ulEmpty" id="section-toc.1-1.7.2.4">
1371 <p id="section-toc.1-1.7.2.4.1"><a href="#section-7.4" class="xref">7.4</a>.  <a href="#name-removal-phase" class="xref">Removal Phase</a></p>
1372 </li>
1373 </ul>
1374 </li>
1375 <li class="compact toc ulBare ulEmpty" id="section-toc.1-1.8">
1376 <p id="section-toc.1-1.8.1"><a href="#section-8" class="xref">8</a>.  <a href="#name-coordination-and-data-model" class="xref">Coordination and Data Models</a></p>
1377 <ul class="compact toc ulBare ulEmpty">
1378 <li class="compact toc ulBare ulEmpty" id="section-toc.1-1.8.2.1">
1379 <p id="section-toc.1-1.8.2.1.1"><a href="#section-8.1" class="xref">8.1</a>.  <a href="#name-coordination-between-autono" class="xref">Coordination between Autonomic Functions</a></p>
1380 </li>
1381 <li class="compact toc ulBare ulEmpty" id="section-toc.1-1.8.2.2">
1382 <p id="section-toc.1-1.8.2.2.1"><a href="#section-8.2" class="xref">8.2</a>.  <a href="#name-coordination-with-tradition" class="xref">Coordination with Traditional Management Functions</a></p>
1383 </li>
1384 <li class="compact toc ulBare ulEmpty" id="section-toc.1-1.8.2.3">
1385 <p id="section-toc.1-1.8.2.3.1"><a href="#section-8.3" class="xref">8.3</a>.  <a href="#name-data-models" class="xref">Data Models</a></p>
1386 </li>
1387 </ul>
1388 </li>
1389 <li class="compact toc ulBare ulEmpty" id="section-toc.1-1.9">
1390 <p id="section-toc.1-1.9.1"><a href="#section-9" class="xref">9</a>.  <a href="#name-robustness" class="xref">Robustness</a></p>
1391 </li>
1392 <li class="compact toc ulBare ulEmpty" id="section-toc.1-1.10">
1393 <p id="section-toc.1-1.10.1"><a href="#section-10" class="xref">10</a>. <a href="#name-security-considerations" class="xref">Security Considerations</a></p>
1394 </li>
1395 <li class="compact toc ulBare ulEmpty" id="section-toc.1-1.11">
1396 <p id="section-toc.1-1.11.1"><a href="#section-11" class="xref">11</a>. <a href="#name-iana-considerations" class="xref">IANA Considerations</a></p>
1397 </li>
1398 <li class="compact toc ulBare ulEmpty" id="section-toc.1-1.12">
1399 <p id="section-toc.1-1.12.1"><a href="#section-12" class="xref">12</a>. <a href="#name-references" class="xref">References</a></p>
1400 <ul class="compact toc ulBare ulEmpty">
1401 <li class="compact toc ulBare ulEmpty" id="section-toc.1-1.12.2.1">
1402 <p id="section-toc.1-1.12.2.1.1"><a href="#section-12.1" class="xref">12.1</a>.  <a href="#name-normative-references" class="xref">Normative References</a></p>
1403 </li>
1404 <li class="compact toc ulBare ulEmpty" id="section-toc.1-1.12.2.2">
1405 <p id="section-toc.1-1.12.2.2.1"><a href="#section-12.2" class="xref">12.2</a>.  <a href="#name-informative-references" class="xref">Informative References</a></p>
1406 </li>
1407 </ul>
1408 </li>
1409 <li class="compact toc ulBare ulEmpty" id="section-toc.1-1.13">
1410 <p id="section-toc.1-1.13.1"><a href="#appendix-A" class="xref">Appendix A</a>.  <a href="#name-example-logic-flows" class="xref">Example Logic Flows</a></p>
1411 </li>
1412 <li class="compact toc ulBare ulEmpty" id="section-toc.1-1.14">
1413 <p id="section-toc.1-1.14.1"><a href="#appendix-B" class="xref"></a><a href="#name-acknowledgements" class="xref">Acknowledgements</a></p>
1414 </li>
1415 <li class="compact toc ulBare ulEmpty" id="section-toc.1-1.15">
1416 <p id="section-toc.1-1.15.1"><a href="#appendix-C" class="xref"></a><a href="#name-authors-addresses" class="xref">Authors' Addresses</a></p>
1417 </li>
1418 </ul>
1419 </nav>
1420 </section>
1421 </div>
1422 <div id="intro">
1423 <section id="section-1">
1424 <h2 id="name-introduction">
1425 <a href="#section-1" class="section-number selfRef">1. </a><a href="#name-introduction" class="section-name selfRef">Introduction</a>
1426 </h2>
1427 <p id="section-1-1">
1428 This document proposes guidelines for the design of Autonomic Service Agents
1429 (ASAs) in the context of an Autonomic Network (AN) based on the Autonomic Network
1430 Infrastructure (ANI) outlined in the autonomic networking reference model <span>[<a href="#RFC8993" class="xref">RFC8993</a>]</span>.
1431 This infrastructure makes use of
1432 the Autonomic Control Plane (ACP) <span>[<a href="#RFC8994" class="xref">RFC8994</a>]</span> and
1433 the GeneRic Autonomic Signaling Protocol (GRASP) <span>[<a href="#RFC8990" class="xref">RFC8990</a>]</span>.
1434 A general introduction to this environment may be found at <span>[<a href="#IPJ" class="xref">IPJ</a>]</span>,
1435 which also includes explanatory diagrams,
1436 and a summary of terminology is in <a href="#terminology" class="xref">Section 2</a>.<a href="#section-1-1" class="pilcrow">¶</a></p>
1437 <p id="section-1-2">
1438 This document is a contribution to the description of an autonomic
1439 networking ecosystem, recognizing that a deployable autonomic network
1440 needs more than just ACP and GRASP implementations. Such an autonomic
1441 network must achieve management tasks that a Network Operations Center
1442 (NOC) cannot readily achieve manually, such as continuous resource
1443 optimization or automated fault detection and repair. These tasks, and
1444 other management automation goals, are described at length in <span>[<a href="#RFC7575" class="xref">RFC7575</a>]</span>. The net result should be significant operational
1445 improvement. To achieve this, the autonomic networking ecosystem must
1446 include at least a library of ASAs and corresponding GRASP technical
1447 objective definitions. A GRASP objective <span>[<a href="#RFC8990" class="xref">RFC8990</a>]</span> is a
1448 data structure whose main contents are a name and a value. The value
1449 consists of a single configurable parameter or a set of parameters of
1450 some kind.<a href="#section-1-2" class="pilcrow">¶</a></p>
1451 <p id="section-1-3">There must also be tools to deploy and oversee ASAs, and integration with
1452 existing operational mechanisms <span>[<a href="#RFC8368" class="xref">RFC8368</a>]</span>. However, this document focuses
1453 on the design of ASAs, with some reference to implementation and operational aspects.<a href="#section-1-3" class="pilcrow">¶</a></p>
1454 <p id="section-1-4">There is considerable literature about autonomic agents with a variety of
1455 proposals about how they should be characterized. Some examples are
1456 <span>[<a href="#DEMOLA06" class="xref">DEMOLA06</a>]</span>,
1457 <span>[<a href="#HUEBSCHER08" class="xref">HUEBSCHER08</a>]</span>,
1458 <span>[<a href="#MOVAHEDI12" class="xref">MOVAHEDI12</a>]</span>, and
1459 <span>[<a href="#GANA13" class="xref">GANA13</a>]</span>. However, for the present document,
1460 the basic definitions and goals for autonomic networking given in <span>[<a href="#RFC7575" class="xref">RFC7575</a>]</span>
1461 apply. According to RFC 7575, an Autonomic Service Agent is
1462 "An agent implemented
1463 on an autonomic node that implements an autonomic function, either in part
1464 (in the case of a distributed function) or whole."<a href="#section-1-4" class="pilcrow">¶</a></p>
1465 <p id="section-1-5">ASAs must be distinguished from other forms of software
1466 components. They are components of network or service management; they
1467 do not in themselves provide services to end users. They do, however,
1468 provide management services to network operators and administrators.
1469 For example, the services envisaged for network function virtualization
1470 (NFV) <span>[<a href="#NFV" class="xref">NFV</a>]</span> or for service function chaining (SFC) <span>[<a href="#RFC7665" class="xref">RFC7665</a>]</span> might be managed by an ASA rather than by traditional
1471 configuration tools.<a href="#section-1-5" class="pilcrow">¶</a></p>
1472 <p id="section-1-6">Another example is that an existing script running within a router to
1473 locally monitor or configure functions or services could be upgraded to an
1474 ASA that could communicate with peer scripts on neighboring or remote
1475 routers. A high-level API will allow such upgraded scripts to take full
1476 advantage of the secure ACP and the discovery, negotiation, and
1477 synchronization features of GRASP. Familiar tasks such as configuring an
1478 Interior Gateway Protocol (IGP) on neighboring routers or even exchanging
1479 IGP security keys could be performed securely in this way. This document
1480 mainly addresses issues affecting quite complex ASAs, but initially, the
1481 most useful ASAs may in fact be rather simple evolutions of existing
1482 scripts.<a href="#section-1-6" class="pilcrow">¶</a></p>
1483 <p id="section-1-7">The reference model <span>[<a href="#RFC8993" class="xref">RFC8993</a>]</span> for autonomic networks
1484 explains further the functionality of ASAs by adding the following:<a href="#section-1-7" class="pilcrow">¶</a></p>
1485 <blockquote id="section-1-8">
1486 [An ASA is] a process that makes use of the features provided by the
1487 ANI to achieve its own goals, usually including interaction with other
1488 ASAs via GRASP <span>[<a href="#RFC8990" class="xref">RFC8990</a>]</span> or otherwise. Of
1489 course, it also interacts with the specific targets of its function,
1490 using any suitable mechanism. Unless its function is very simple, the
1491 ASA will need to handle overlapping asynchronous operations. It may
1492 therefore be a quite complex piece of software in its own right, forming
1493 part of the application layer above the ANI.<a href="#section-1-8" class="pilcrow">¶</a>
1494 </blockquote>
1495 <p id="section-1-9">As mentioned, there will certainly be simple ASAs that manage a
1496 single objective in a straightforward way and do not need asynchronous
1497 operations. In nodes where computing power and memory space are limited,
1498 ASAs should run at a much lower frequency than the primary workload, so
1499 CPU load should not be a big issue, but memory footprint in a
1500 constrained node is certainly a concern. ASAs installed in constrained
1501 devices will have limited functionality. In such cases, many aspects of
1502 the current document do not apply. However, in the general case, an ASA
1503 may be a relatively complex software component that will in many cases
1504 control and monitor simpler entities in the same or remote host(s). For
1505 example, a device controller that manages tens or hundreds of simple
1506 devices might contain a single ASA.<a href="#section-1-9" class="pilcrow">¶</a></p>
1507 <p id="section-1-10">The remainder of this document offers guidance on the design of complex ASAs.
1508 Some of the material may be familiar to those experienced in distributed
1509 fault-tolerant and real-time control systems. Robustness and security
1510 are of particular importance in autonomic networks and are discussed
1511 in Sections <a href="#robust" class="xref">9</a> and <a href="#security" class="xref">10</a>.<a href="#section-1-10" class="pilcrow">¶</a></p>
1512 </section>
1513 </div>
1514 <div id="terminology">
1515 <section id="section-2">
1516 <h2 id="name-terminology">
1517 <a href="#section-2" class="section-number selfRef">2. </a><a href="#name-terminology" class="section-name selfRef">Terminology</a>
1518 </h2>
1519 <p id="section-2-1">This section summarizes various acronyms and terminology used in the
1520 document. Where no other reference is given, please consult <span>[<a href="#RFC8993" class="xref">RFC8993</a>]</span> or <span>[<a href="#RFC7575" class="xref">RFC7575</a>]</span>.<a href="#section-2-1" class="pilcrow">¶</a></p>
1521 <span class="break"></span><dl class="dlParallel" id="section-2-2">
1522 <dt id="section-2-2.1">Autonomic:
1523 </dt>
1524 <dd style="margin-left: 1.5em" id="section-2-2.2">self-managing (self-configuring, self-protecting, self- healing,
1525 self-optimizing), but allowing high-level guidance by a central entity
1526 such as a NOC<a href="#section-2-2.2" class="pilcrow">¶</a>
1527 </dd>
1528 <dd class="break"></dd>
1529 <dt id="section-2-2.3">Autonomic Function:
1530 </dt>
1531 <dd style="margin-left: 1.5em" id="section-2-2.4">a function that adapts on its own to a changing environment<a href="#section-2-2.4" class="pilcrow">¶</a>
1532 </dd>
1533 <dd class="break"></dd>
1534 <dt id="section-2-2.5">Autonomic Node:
1535 </dt>
1536 <dd style="margin-left: 1.5em" id="section-2-2.6">a node that employs autonomic functions<a href="#section-2-2.6" class="pilcrow">¶</a>
1537 </dd>
1538 <dd class="break"></dd>
1539 <dt id="section-2-2.7">ACP:
1540 </dt>
1541 <dd style="margin-left: 1.5em" id="section-2-2.8">Autonomic Control Plane <span>[<a href="#RFC8994" class="xref">RFC8994</a>]</span><a href="#section-2-2.8" class="pilcrow">¶</a>
1542 </dd>
1543 <dd class="break"></dd>
1544 <dt id="section-2-2.9">AN:
1545 </dt>
1546 <dd style="margin-left: 1.5em" id="section-2-2.10">Autonomic Network; a network of autonomic nodes, which interact directly with each other<a href="#section-2-2.10" class="pilcrow">¶</a>
1547 </dd>
1548 <dd class="break"></dd>
1549 <dt id="section-2-2.11">ANI:
1550 </dt>
1551 <dd style="margin-left: 1.5em" id="section-2-2.12">Autonomic Network Infrastructure<a href="#section-2-2.12" class="pilcrow">¶</a>
1552 </dd>
1553 <dd class="break"></dd>
1554 <dt id="section-2-2.13">ASA:
1555 </dt>
1556 <dd style="margin-left: 1.5em" id="section-2-2.14">Autonomic Service Agent; an agent installed on an autonomic node
1557 that implements an autonomic function, either partially (in the case
1558 of a distributed function) or completely<a href="#section-2-2.14" class="pilcrow">¶</a>
1559 </dd>
1560 <dd class="break"></dd>
1561 <dt id="section-2-2.15">BRSKI:
1562 </dt>
1563 <dd style="margin-left: 1.5em" id="section-2-2.16">Bootstrapping Remote Secure Key Infrastructure <span>[<a href="#RFC8995" class="xref">RFC8995</a>]</span><a href="#section-2-2.16" class="pilcrow">¶</a>
1564 </dd>
1565 <dd class="break"></dd>
1566 <dt id="section-2-2.17">CBOR:
1567 </dt>
1568 <dd style="margin-left: 1.5em" id="section-2-2.18">Concise Binary Object Representation<span>[<a href="#RFC8949" class="xref">RFC8949</a>]</span><a href="#section-2-2.18" class="pilcrow">¶</a>
1569 </dd>
1570 <dd class="break"></dd>
1571 <dt id="section-2-2.19">GRASP:
1572 </dt>
1573 <dd style="margin-left: 1.5em" id="section-2-2.20">GeneRric Autonomic Signaling Protocol <span>[<a href="#RFC8990" class="xref">RFC8990</a>]</span><a href="#section-2-2.20" class="pilcrow">¶</a>
1574 </dd>
1575 <dd class="break"></dd>
1576 <dt id="section-2-2.21">GRASP API:
1577 </dt>
1578 <dd style="margin-left: 1.5em" id="section-2-2.22">GRASP Application Programming Interface <span>[<a href="#RFC8991" class="xref">RFC8991</a>]</span><a href="#section-2-2.22" class="pilcrow">¶</a>
1579 </dd>
1580 <dd class="break"></dd>
1581 <dt id="section-2-2.23">NOC:
1582 </dt>
1583 <dd style="margin-left: 1.5em" id="section-2-2.24">Network Operations Center <span>[<a href="#RFC8368" class="xref">RFC8368</a>]</span><a href="#section-2-2.24" class="pilcrow">¶</a>
1584 </dd>
1585 <dd class="break"></dd>
1586 <dt id="section-2-2.25">Objective:
1587 </dt>
1588 <dd style="margin-left: 1.5em" id="section-2-2.26">A GRASP technical objective is a data structure whose main
1589 contents are a name and a value. The value consists of a single
1590 configurable parameter or a set of parameters of some kind <span>[<a href="#RFC8990" class="xref">RFC8990</a>]</span>.<a href="#section-2-2.26" class="pilcrow">¶</a>
1591 </dd>
1592 <dd class="break"></dd>
1593 </dl>
1594 </section>
1595 </div>
1596 <div id="structure">
1597 <section id="section-3">
1598 <h2 id="name-logical-structure-of-an-aut">
1599 <a href="#section-3" class="section-number selfRef">3. </a><a href="#name-logical-structure-of-an-aut" class="section-name selfRef">Logical Structure of an Autonomic Service Agent</a>
1600 </h2>
1601 <p id="section-3-1">As mentioned above, all but the simplest ASAs will need to support
1602 asynchronous operations. Different programming environments support
1603 asynchronicity in different ways. In this document, we use an explicit
1604 multi-threading model to describe operations. This is illustrative, and
1605 alternatives to multi-threading are discussed in detail in connection
1606 with the GRASP API (see <a href="#api" class="xref">Section 4.3</a>).<a href="#section-3-1" class="pilcrow">¶</a></p>
1607 <p id="section-3-2">A typical ASA will have a main thread that performs various initial
1608 housekeeping actions such as:<a href="#section-3-2" class="pilcrow">¶</a></p>
1609 <ul class="normal">
1610 <li class="normal" id="section-3-3.1">obtain authorization credentials, if needed<a href="#section-3-3.1" class="pilcrow">¶</a>
1611 </li>
1612 <li class="normal" id="section-3-3.2">register the ASA with GRASP<a href="#section-3-3.2" class="pilcrow">¶</a>
1613 </li>
1614 <li class="normal" id="section-3-3.3">acquire relevant policy parameters<a href="#section-3-3.3" class="pilcrow">¶</a>
1615 </li>
1616 <li class="normal" id="section-3-3.4">declare data structures for relevant GRASP objectives<a href="#section-3-3.4" class="pilcrow">¶</a>
1617 </li>
1618 <li class="normal" id="section-3-3.5">register with GRASP those objectives that it will actively manage<a href="#section-3-3.5" class="pilcrow">¶</a>
1619 </li>
1620 <li class="normal" id="section-3-3.6">launch a self-monitoring thread<a href="#section-3-3.6" class="pilcrow">¶</a>
1621 </li>
1622 <li class="normal" id="section-3-3.7">enter its main loop<a href="#section-3-3.7" class="pilcrow">¶</a>
1623 </li>
1624 </ul>
1625 <p id="section-3-4">The logic of the main loop will depend on the details of the autonomic function concerned.
1626 Whenever asynchronous operations are required, extra threads may be launched.
1627 Examples of such threads include:<a href="#section-3-4" class="pilcrow">¶</a></p>
1628 <ul class="normal">
1629 <li class="normal" id="section-3-5.1">repeatedly flood an objective to the AN so that any ASA can
1630 receive the objective's latest value<a href="#section-3-5.1" class="pilcrow">¶</a>
1631 </li>
1632 <li class="normal" id="section-3-5.2">accept incoming synchronization requests for an objective managed by this ASA<a href="#section-3-5.2" class="pilcrow">¶</a>
1633 </li>
1634 <li class="normal" id="section-3-5.3">accept incoming negotiation requests for an objective managed by this ASA,
1635 and then conduct the resulting negotiation with the counterpart ASA<a href="#section-3-5.3" class="pilcrow">¶</a>
1636 </li>
1637 <li class="normal" id="section-3-5.4">manage subsidiary non-autonomic devices directly<a href="#section-3-5.4" class="pilcrow">¶</a>
1638 </li>
1639 </ul>
1640 <p id="section-3-6">These threads should all either exit after their job is done or
1641 enter a wait state for new work to avoid wasting system resources.<a href="#section-3-6" class="pilcrow">¶</a></p>
1642 <p id="section-3-7">According to the degree of parallelism needed by the application,
1643 some of these threads might be launched in multiple instances. In
1644 particular, if negotiation sessions with other ASAs are expected to be
1645 long or to involve wait states, the ASA designer might allow for
1646 multiple simultaneous negotiating threads, with appropriate use of
1647 queues and synchronization primitives to maintain consistency.<a href="#section-3-7" class="pilcrow">¶</a></p>
1648 <p id="section-3-8">The main loop itself could act as the initiator of synchronization
1649 requests or negotiation requests when the ASA needs data or resources
1650 from other ASAs. In particular, the main loop should watch for changes
1651 in policy parameters that affect its operation and, if appropriate,
1652 occasionally refresh authorization credentials. It should also do
1653 whatever is required to avoid unnecessary resource consumption, for
1654 example, by limiting its frequency of execution.<a href="#section-3-8" class="pilcrow">¶</a></p>
1655 <p id="section-3-9">The self-monitoring thread is of considerable importance. Failure of
1656 autonomic service agents is highly undesirable. To a large extent, this
1657 depends on careful coding and testing, with no unhandled error returns
1658 or exceptions, but if there is nevertheless some sort of failure, the
1659 self-monitoring thread should detect it, fix it if possible, and, in the
1660 worst case, restart the entire ASA.<a href="#section-3-9" class="pilcrow">¶</a></p>
1661 <p id="section-3-10"><a href="#eg" class="xref">Appendix A</a> presents some example logic flows in informal pseudocode.<a href="#section-3-10" class="pilcrow">¶</a></p>
1662 </section>
1663 </div>
1664 <div id="interact">
1665 <section id="section-4">
1666 <h2 id="name-interaction-with-the-autono">
1667 <a href="#section-4" class="section-number selfRef">4. </a><a href="#name-interaction-with-the-autono" class="section-name selfRef">Interaction with the Autonomic Networking Infrastructure</a>
1668 </h2>
1669 <div id="interacts">
1670 <section id="section-4.1">
1671 <h3 id="name-interaction-with-the-securi">
1672 <a href="#section-4.1" class="section-number selfRef">4.1. </a><a href="#name-interaction-with-the-securi" class="section-name selfRef">Interaction with the Security Mechanisms</a>
1673 </h3>
1674 <p id="section-4.1-1">An ASA by definition runs in an autonomic node. Before any normal
1675 ASAs are started, such nodes must be bootstrapped into the autonomic
1676 network's secure key infrastructure, typically in accordance with
1677 <span>[<a href="#RFC8995" class="xref">RFC8995</a>]</span>. This key infrastructure will be used to
1678 secure the ACP (next section) and may be used by ASAs to set up
1679 additional secure interactions with their peers, if needed.<a href="#section-4.1-1" class="pilcrow">¶</a></p>
1680 <p id="section-4.1-2">Note that the secure bootstrap process itself incorporates simple
1681 special-purpose ASAs that use a restricted mode of GRASP (<span><a href="https://www.rfc-editor.org/rfc/rfc8995#section-4" class="relref">Section 4</a> of [<a href="#RFC8995" class="xref">RFC8995</a>]</span>).<a href="#section-4.1-2" class="pilcrow">¶</a></p>
1682 </section>
1683 </div>
1684 <div id="interacta">
1685 <section id="section-4.2">
1686 <h3 id="name-interaction-with-the-autonom">
1687 <a href="#section-4.2" class="section-number selfRef">4.2. </a><a href="#name-interaction-with-the-autonom" class="section-name selfRef">Interaction with the Autonomic Control Plane</a>
1688 </h3>
1689 <p id="section-4.2-1">In a normal autonomic network, ASAs will run as clients of the ACP,
1690 which will provide a fully secured network environment for all
1691 communication with other ASAs, in most cases mediated by GRASP (next
1692 section).<a href="#section-4.2-1" class="pilcrow">¶</a></p>
1693 <p id="section-4.2-2">Note that the ACP formation process itself incorporates simple
1694 special-purpose ASAs that use a restricted mode of GRASP (<span><a href="https://www.rfc-editor.org/rfc/rfc8994#section-6.4" class="relref">Section 6.4</a> of [<a href="#RFC8994" class="xref">RFC8994</a>]</span>).<a href="#section-4.2-2" class="pilcrow">¶</a></p>
1695 </section>
1696 </div>
1697 <div id="api">
1698 <section id="section-4.3">
1699 <h3 id="name-interaction-with-grasp-and-">
1700 <a href="#section-4.3" class="section-number selfRef">4.3. </a><a href="#name-interaction-with-grasp-and-" class="section-name selfRef">Interaction with GRASP and its API</a>
1701 </h3>
1702 <p id="section-4.3-1">In a node where a significant number of ASAs are installed, GRASP
1703 <span>[<a href="#RFC8990" class="xref">RFC8990</a>]</span> is likely to run as a separate process with
1704 its API <span>[<a href="#RFC8991" class="xref">RFC8991</a>]</span> available in user space. Thus, ASAs
1705 may operate without special privilege, unless they need it for other
1706 reasons. The ASA's view of GRASP is built around GRASP objectives
1707 (<a href="#objdes" class="xref">Section 6</a>), defined as data structures containing
1708 administrative information such as the objective's unique name, and
1709 its current value. The format and size of the value is not restricted
1710 by the protocol, except that it must be possible to serialize it for
1711 transmission in Concise Binary Object Representation (CBOR) <span>[<a href="#RFC8949" class="xref">RFC8949</a>]</span>, subject only to GRASP's maximum message size as
1712 discussed in <a href="#objdes" class="xref">Section 6</a>.<a href="#section-4.3-1" class="pilcrow">¶</a></p>
1713 <p id="section-4.3-2">As discussed in <a href="#structure" class="xref">Section 3</a>, GRASP is an asynchronous
1714 protocol, and this document uses a multi-threading model to describe
1715 operations. In many programming environments, an "event loop" model is
1716 used instead, in which case each thread would be implemented as an event
1717 handler called in turn by the main loop. For this case, the GRASP API
1718 must provide non-blocking calls and possibly support callbacks. This
1719 topic is discussed in more detail in <span>[<a href="#RFC8991" class="xref">RFC8991</a>]</span>, and other
1720 asynchronicity models are also possible. Whenever necessary, the GRASP
1721 session identifier will be used to distinguish simultaneous
1722 operations.<a href="#section-4.3-2" class="pilcrow">¶</a></p>
1723 <p id="section-4.3-3">The GRASP API should offer the following features:<a href="#section-4.3-3" class="pilcrow">¶</a></p>
1724 <ul class="normal">
1725 <li class="normal" id="section-4.3-4.1">Registration functions, so that an ASA can register itself and
1726 the objectives that it manages.<a href="#section-4.3-4.1" class="pilcrow">¶</a>
1727 </li>
1728 <li class="normal" id="section-4.3-4.2">A discovery function, by which an ASA can discover other ASAs
1729 supporting a given objective.<a href="#section-4.3-4.2" class="pilcrow">¶</a>
1730 </li>
1731 <li class="normal" id="section-4.3-4.3">A negotiation request function, by which an ASA can start
1732 negotiation of an objective with a counterpart ASA. With this,
1733 there is a corresponding listening function for an ASA that wishes
1734 to respond to negotiation requests and a set of functions to
1735 support negotiating steps. Once a negotiation starts, it is a
1736 symmetric process with both sides sending successive objective
1737 values to each other until agreement is reached (or the negotiation
1738 fails).<a href="#section-4.3-4.3" class="pilcrow">¶</a>
1739 </li>
1740 <li class="normal" id="section-4.3-4.4">A synchronization function, by which an ASA can request the
1741 current value of an objective from a counterpart ASA. With this,
1742 there is a corresponding listening function for an ASA that wishes
1743 to respond to synchronization requests. Unlike negotiation,
1744 synchronization is an asymmetric process in which the listener sends
1745 a single objective value to the requester.<a href="#section-4.3-4.4" class="pilcrow">¶</a>
1746 </li>
1747 <li class="normal" id="section-4.3-4.5">A flood function, by which an ASA can cause the current value of
1748 an objective to be flooded throughout the AN so that any ASA can
1749 receive it.<a href="#section-4.3-4.5" class="pilcrow">¶</a>
1750 </li>
1751 </ul>
1752 <p id="section-4.3-5">For further details and some additional housekeeping functions, see <span>[<a href="#RFC8991" class="xref">RFC8991</a>]</span>.<a href="#section-4.3-5" class="pilcrow">¶</a></p>
1753 <p id="section-4.3-6">The GRASP API is intended to support the various interactions
1754 expected between most ASAs, such as the interactions outlined in <a href="#structure" class="xref">Section 3</a>. However, if ASAs require additional
1755 communication between themselves, they can do so directly over the ACP
1756 to benefit from its security. One option is to use GRASP discovery and
1757 synchronization as a rendezvous mechanism between two ASAs, passing
1758 communication parameters such as a TCP port number via GRASP. The use
1759 of TLS over the ACP for such communications is advisable, as described
1760 in <span><a href="https://www.rfc-editor.org/rfc/rfc8994#section-6.9.2" class="relref">Section 6.9.2</a> of [<a href="#RFC8994" class="xref">RFC8994</a>]</span>.<a href="#section-4.3-6" class="pilcrow">¶</a></p>
1761 </section>
1762 </div>
1763 <section id="section-4.4">
1764 <h3 id="name-interaction-with-policy-mec">
1765 <a href="#section-4.4" class="section-number selfRef">4.4. </a><a href="#name-interaction-with-policy-mec" class="section-name selfRef">Interaction with Policy Mechanisms</a>
1766 </h3>
1767 <p id="section-4.4-1"> At the time of writing, the policy mechanisms for the ANI are
1768 undefined. In particular, the use of declarative policies (aka
1769 Intents) for the definition and management of an ASA's behaviors remains
1770 a research topic <span>[<a href="#I-D.irtf-nmrg-ibn-concepts-definitions" class="xref">IBN-CONCEPTS</a>]</span>.<a href="#section-4.4-1" class="pilcrow">¶</a></p>
1771 <p id="section-4.4-2"> In the cases where ASAs are defined as closed control
1772 loops, the specifications defined in <span>[<a href="#ZSM009-1" class="xref">ZSM009-1</a>]</span>
1773 regarding imperative and declarative goal statements may be
1774 applicable.<a href="#section-4.4-2" class="pilcrow">¶</a></p>
1775 <p id="section-4.4-3">In the ANI, policy dissemination is expected to operate by
1776 an information distribution mechanism (e.g., via GRASP <span>[<a href="#RFC8990" class="xref">RFC8990</a>]</span>) that can reach all autonomic nodes and
1777 therefore every ASA. However, each ASA must be capable of
1778 operating "out of the box" in the absence of locally defined
1779 policy, so every ASA implementation must include carefully
1780 chosen default values and settings for all policy
1781 parameters.<a href="#section-4.4-3" class="pilcrow">¶</a></p>
1782 </section>
1783 </section>
1784 </div>
1785 <div id="nonauto">
1786 <section id="section-5">
1787 <h2 id="name-interaction-with-non-autono">
1788 <a href="#section-5" class="section-number selfRef">5. </a><a href="#name-interaction-with-non-autono" class="section-name selfRef">Interaction with Non-autonomic Components and Systems</a>
1789 </h2>
1790 <p id="section-5-1">To have any external effects, an ASA must also interact with non-autonomic
1791 components of the node where it is installed. For example, an ASA whose purpose
1792 is to manage a resource must interact with that resource. An ASA managing
1793 an entity that is also managed by local software must interact
1794 with that software. For example, if such management is performed by NETCONF
1795 <span>[<a href="#RFC6241" class="xref">RFC6241</a>]</span>, the ASA must interact with the NETCONF
1796 server as an independent NETCONF client in the same node to avoid
1797 any inconsistency between configuration changes delivered
1798 via NETCONF and configuration changes made by the ASA.<a href="#section-5-1" class="pilcrow">¶</a></p>
1799 <p id="section-5-2">In an environment where systems are virtualized and specialized using
1800 techniques such as network function virtualization or network slicing,
1801 there will be a design choice whether ASAs are deployed once per physical node
1802 or once per virtual context. A related issue is whether the ANI as a whole
1803 is deployed once on a physical network or whether several virtual ANIs
1804 are deployed. This aspect needs to be considered by the ASA designer.<a href="#section-5-2" class="pilcrow">¶</a></p>
1805 </section>
1806 </div>
1807 <div id="objdes">
1808 <section id="section-6">
1809 <h2 id="name-design-of-grasp-objectives">
1810 <a href="#section-6" class="section-number selfRef">6. </a><a href="#name-design-of-grasp-objectives" class="section-name selfRef">Design of GRASP Objectives</a>
1811 </h2>
1812 <p id="section-6-1">The design of an ASA will often require the design of a new GRASP
1813 objective. The general rules for the format of GRASP objectives, their
1814 names, and IANA registration are given in <span>[<a href="#RFC8990" class="xref">RFC8990</a>]</span>. Additionally, that document discusses various
1815 general considerations for the design of objectives, which are not
1816 repeated here. However, note that GRASP, like HTTP, does
1817 not provide transactional integrity. In particular, steps in a GRASP
1818 negotiation are not idempotent. The design of a GRASP objective and the
1819 logic flow of the ASA should take this into account. One approach, which
1820 should be used when possible, is to design objectives with idempotent
1821 semantics. If this is not possible, typically if an ASA is allocating
1822 part of a shared resource to other ASAs, it needs to ensure that the
1823 same part of the resource is not allocated twice. The easiest way is to
1824 run only one negotiation at a time. If an ASA is capable of overlapping
1825 several negotiations, it must avoid interference between these
1826 negotiations.<a href="#section-6-1" class="pilcrow">¶</a></p>
1827 <p id="section-6-2">Negotiations will always end, normally because one end or the other
1828 declares success or failure. If this does not happen, either a timeout or
1829 exhaustion of the loop count will occur. The definition of a GRASP
1830 objective should describe a specific negotiation policy if it is not self-evident.<a href="#section-6-2" class="pilcrow">¶</a></p>
1831 <p id="section-6-3">GRASP allows a "dry run" mode of negotiation, where a negotiation
1832 session follows its normal course but is not committed at either end
1833 until a subsequent live negotiation session. If dry run mode is
1834 defined for the objective, its specification, and every implementation,
1835 must consider what state needs to be saved following a dry run
1836 negotiation, such that a subsequent live negotiation can be expected to
1837 succeed. It must be clear how long this state is kept and what happens
1838 if the live negotiation occurs after this state is deleted. An ASA that
1839 requests a dry run negotiation must take account of the possibility that
1840 a successful dry run is followed by a failed live negotiation. Because
1841 of these complexities, the dry run mechanism should only be supported by
1842 objectives and ASAs where there is a significant benefit from it.<a href="#section-6-3" class="pilcrow">¶</a></p>
1843 <p id="section-6-4">The actual value field of an objective is limited by the GRASP
1844 protocol definition to any data structure that can be expressed in
1845 Concise Binary Object Representation (CBOR) <span>[<a href="#RFC8949" class="xref">RFC8949</a>]</span>. For some objectives, a single data item will
1846 suffice, for example, an integer, a floating point
1847 number, a UTF-8 string, or an arbitrary byte string. For more complex
1848 cases, a simple tuple structure such as [item1, item2, item3] could be
1849 used. Since CBOR is closely linked to JSON, it is also rather easy to
1850 define an objective whose value is a JSON structure. The formats
1851 acceptable by the GRASP API will limit the options in practice. A
1852 generic solution is for the API to accept and deliver the value field in
1853 raw CBOR, with the ASA itself encoding and decoding it via a CBOR
1854 library (<span><a href="https://www.rfc-editor.org/rfc/rfc8991#section-2.3.2.4" class="relref">Section 2.3.2.4</a> of [<a href="#RFC8991" class="xref">RFC8991</a>]</span>).<a href="#section-6-4" class="pilcrow">¶</a></p>
1855 <p id="section-6-5">The maximum size of the value field of an objective is limited by the
1856 GRASP maximum message size. If the default maximum size specified as
1857 GRASP_DEF_MAX_SIZE by <span>[<a href="#RFC8990" class="xref">RFC8990</a>]</span> is not enough, the
1858 specification of the objective must indicate the required maximum message
1859 size for both unicast and multicast messages.<a href="#section-6-5" class="pilcrow">¶</a></p>
1860 <p id="section-6-6">A mapping from YANG to CBOR is defined by <span>[<a href="#I-D.ietf-core-yang-cbor" class="xref">CBOR-YANG</a>]</span>. Subject to
1861 the size limit defined for GRASP messages, nothing prevents objectives transporting YANG in this way.<a href="#section-6-6" class="pilcrow">¶</a></p>
1862 <p id="section-6-7">The flexibility of CBOR implies that the value field of many objectives can be extended in service,
1863 to add additional information or alternative content, especially if JSON-like structures are
1864 used. This has consequences for the robustness of ASAs, as discussed in <a href="#robust" class="xref">Section 9</a>.<a href="#section-6-7" class="pilcrow">¶</a></p>
1865 </section>
1866 </div>
1867 <div id="life">
1868 <section id="section-7">
1869 <h2 id="name-life-cycle">
1870 <a href="#section-7" class="section-number selfRef">7. </a><a href="#name-life-cycle" class="section-name selfRef">Life Cycle</a>
1871 </h2>
1872 <p id="section-7-1">The ASA life cycle is discussed in <span>[<a href="#I-D.peloso-anima-autonomic-function" class="xref">AUTONOMIC-FUNCTION</a>]</span>,
1873 from which the following text was derived. It does not cover all details, and some
1874 of the terms used would require precise definitions in a given implementation.<a href="#section-7-1" class="pilcrow">¶</a></p>
1875 <p id="section-7-2">In simple cases, autonomic functions could be permanent, in the sense
1876 that ASAs are shipped as part of a product and persist throughout the
1877 product's life. However, in complex cases, a more likely situation is
1878 that ASAs need to be installed or updated dynamically because of new
1879 requirements or bugs. This section describes one approach to the
1880 resulting life cycle of individual ASAs. It does not consider wider
1881 issues such as updates of shared libraries.<a href="#section-7-2" class="pilcrow">¶</a></p>
1882 <p id="section-7-3">Because continuity of service is fundamental to autonomic networking,
1883 the process of seamlessly replacing a running instance of an ASA with a
1884 new version needs to be part of the ASA's design. The implication of
1885 service continuity on the design of ASAs can be illustrated along the
1886 three main phases of the ASA life cycle, namely installation,
1887 instantiation, and operation.<a href="#section-7-3" class="pilcrow">¶</a></p>
1888 <span id="name-life-cycle-of-an-autonomic-"></span><div id="Fig_LC">
1889 <figure id="figure-1">
1890 <div class="alignLeft art-text artwork" id="section-7-4.1">
1891 <pre>
1892 +--------------+
1893 Undeployed ------&gt;| |------&gt; Undeployed
1894 | Installed |
1895 +--&gt;| |---+
1896 Mandate | +--------------+ | Receives a
1897 is revoked | +--------------+ | Mandate
1898 +---| |&lt;--+
1899 | Instantiated |
1900 +--&gt;| |---+
1901 set | +--------------+ | set
1902 down | +--------------+ | up
1903 +---| |&lt;--+
1904 | Operational |
1905 | |
1906 +--------------+
1907 </pre>
1908 </div>
1909 <figcaption><a href="#figure-1" class="selfRef">Figure 1</a>:
1910 <a href="#name-life-cycle-of-an-autonomic-" class="selfRef">Life Cycle of an Autonomic Service Agent</a>
1911 </figcaption></figure>
1912 </div>
1913 <section id="section-7.1">
1914 <h3 id="name-installation-phase">
1915 <a href="#section-7.1" class="section-number selfRef">7.1. </a><a href="#name-installation-phase" class="section-name selfRef">Installation Phase</a>
1916 </h3>
1917 <p id="section-7.1-1">We define "installation" to mean that a piece of software is loaded into
1918 a device, along with any necessary libraries, but is not yet activated.<a href="#section-7.1-1" class="pilcrow">¶</a></p>
1919 <p id="section-7.1-2">Before being able to instantiate and run ASAs, the operator will first provision the
1920 infrastructure with the sets of ASA software corresponding to its needs and objectives.
1921 Such software must be checked for integrity and authenticity before installation.
1922 The provisioning of the infrastructure is realized in the installation phase and consists of
1923 installing (or checking the availability of) the pieces of software of the different ASAs
1924 in a set of Installation Hosts within the autonomic network.<a href="#section-7.1-2" class="pilcrow">¶</a></p>
1925 <p id="section-7.1-3">There are three properties applicable to the installation of ASAs:<a href="#section-7.1-3" class="pilcrow">¶</a></p>
1926 <ul class="normal">
1927 <li class="normal" id="section-7.1-4.1">The dynamic installation property
1928 allows installing an ASA on demand, on any hosts compatible with the ASA.<a href="#section-7.1-4.1" class="pilcrow">¶</a>
1929 </li>
1930 <li class="normal" id="section-7.1-4.2">The decoupling property
1931 allows an ASA on one machine to control resources in another machine
1932 (known as "decoupled mode").<a href="#section-7.1-4.2" class="pilcrow">¶</a>
1933 </li>
1934 <li class="normal" id="section-7.1-4.3">The multiplicity property
1935 allows controlling multiple sets of resources from a single ASA.<a href="#section-7.1-4.3" class="pilcrow">¶</a>
1936 </li>
1937 </ul>
1938 <p id="section-7.1-5">These three properties are very important in the context of the installation
1939 phase as their variations condition how the ASA could be installed on the infrastructure.<a href="#section-7.1-5" class="pilcrow">¶</a></p>
1940 <section id="section-7.1.1">
1941 <h4 id="name-installation-phase-inputs-a">
1942 <a href="#section-7.1.1" class="section-number selfRef">7.1.1. </a><a href="#name-installation-phase-inputs-a" class="section-name selfRef">Installation Phase Inputs and Outputs</a>
1943 </h4>
1944 <p id="section-7.1.1-1">Inputs are:<a href="#section-7.1.1-1" class="pilcrow">¶</a></p>
1945 <ul class="normal">
1946 <li class="normal" id="section-7.1.1-2.1">[ASA_type]: specifies which ASA to install.<a href="#section-7.1.1-2.1" class="pilcrow">¶</a>
1947 </li>
1948 <li class="normal" id="section-7.1.1-2.2">[Installation_target_infrastructure]: specifies the candidate installation Hosts.<a href="#section-7.1.1-2.2" class="pilcrow">¶</a>
1949 </li>
1950 <li class="normal" id="section-7.1.1-2.3">[ASA_placement_function]: specifies how the installation phase will meet the operator's
1951 needs and objectives for the provision of the infrastructure. This
1952 function is only useful in the decoupled mode. It can be as simple
1953 as an explicit list of hosts on which the ASAs are to be
1954 installed, or it could consist of operator-defined criteria and
1955 constraints.<a href="#section-7.1.1-2.3" class="pilcrow">¶</a>
1956 </li>
1957 </ul>
1958 <p id="section-7.1.1-3">The main output of the installation phase is a [List_of_ASAs] installed on
1959 [List_of_hosts]. This output is also useful for the coordination function
1960 where it acts as a static interaction map (see <a href="#coordi" class="xref">Section 8.1</a>).<a href="#section-7.1.1-3" class="pilcrow">¶</a></p>
1961 <p id="section-7.1.1-4">The condition to validate in order to pass to next phase is to
1962 ensure that [List_of_ASAs] are correctly installed on
1963 [List_of_hosts]. A minimum set of primitives to support the
1964 installation of ASAs could be the following: install (List_of_ASAs,
1965 Installation_target_infrastructure, ASA_placement_function) and
1966 uninstall (List_of_ASAs).<a href="#section-7.1.1-4" class="pilcrow">¶</a></p>
1967 </section>
1968 </section>
1969 <div id="Sec_Inst">
1970 <section id="section-7.2">
1971 <h3 id="name-instantiation-phase">
1972 <a href="#section-7.2" class="section-number selfRef">7.2. </a><a href="#name-instantiation-phase" class="section-name selfRef">Instantiation Phase</a>
1973 </h3>
1974 <p id="section-7.2-1">We define "instantiation" as the operation of creating a single ASA instance
1975 from the corresponding piece of installed software.<a href="#section-7.2-1" class="pilcrow">¶</a></p>
1976 <p id="section-7.2-2">Once the ASAs are installed on the appropriate hosts in the
1977 network, these ASAs may start to operate. From the operator
1978 viewpoint, an operating ASA means the ASA manages the network
1979 resources as per the objectives given. At the ASA local level,
1980 operating means executing their control loop algorithm.<a href="#section-7.2-2" class="pilcrow">¶</a></p>
1981 <p id="section-7.2-3">There are two aspects to take into consideration. First, having a
1982 piece of code installed and available to run on a host is not the same
1983 as having an agent based on this piece of code running inside the
1984 host. Second, in a coupled case, determining which resources are
1985 controlled by an ASA is straightforward (the ASA runs on the same
1986 autonomic node as the resources it is controlling). In a decoupled
1987 mode, determining this is a bit more complex: a starting agent will
1988 have to either discover the set of resources it ought to control, or
1989 such information has to be communicated to the ASA.<a href="#section-7.2-3" class="pilcrow">¶</a></p>
1990 <p id="section-7.2-4">The instantiation phase of an ASA covers both these aspects:
1991 starting the agent code (when this does not start automatically) and
1992 determining which resources have to be controlled (when this is not
1993 straightforward).<a href="#section-7.2-4" class="pilcrow">¶</a></p>
1994 <div id="Sec_Inst_Goal">
1995 <section id="section-7.2.1">
1996 <h4 id="name-operators-goal">
1997 <a href="#section-7.2.1" class="section-number selfRef">7.2.1. </a><a href="#name-operators-goal" class="section-name selfRef">Operator's Goal</a>
1998 </h4>
1999 <p id="section-7.2.1-1">Through this phase, the operator wants to control its autonomic
2000 network regarding at least two aspects:<a href="#section-7.2.1-1" class="pilcrow">¶</a></p>
2001 <ol start="1" type="1" class="normal type-1" id="section-7.2.1-2">
2002 <li id="section-7.2.1-2.1">determine the scope of autonomic functions by instructing which network
2003 resources have to be managed by which autonomic function (and more precisely
2004 by which release of the ASA software code, e.g., version number or provider).<a href="#section-7.2.1-2.1" class="pilcrow">¶</a>
2005 </li>
2006 <li id="section-7.2.1-2.2">determine how the autonomic functions are organized by instantiating a set
2007 of ASAs across one or more autonomic nodes and instructing them
2008 accordingly about the other ASAs in the set as necessary.<a href="#section-7.2.1-2.2" class="pilcrow">¶</a>
2009 </li>
2010 </ol>
2011 <p id="section-7.2.1-3">
2012 In this phase, the operator may also want to
2013 set goals for autonomic functions, e.g., by
2014 configuring GRASP objectives.<a href="#section-7.2.1-3" class="pilcrow">¶</a></p>
2015 <p id="section-7.2.1-4">The operator's goal can be summarized in an instruction to the autonomic ecosystem matching the following format,
2016 explained in detail in the next sub-section:<a href="#section-7.2.1-4" class="pilcrow">¶</a></p>
2017 <p style="margin-left: 1.5em" id="section-7.2.1-5">[Instances_of_ASA_type] ready to control [Instantiation_target_infrastructure] with [Instantiation_target_parameters]<a href="#section-7.2.1-5" class="pilcrow">¶</a></p>
2018 </section>
2019 </div>
2020 <div id="Sec_Inst_InOut">
2021 <section id="section-7.2.2">
2022 <h4 id="name-instantiation-phase-inputs-">
2023 <a href="#section-7.2.2" class="section-number selfRef">7.2.2. </a><a href="#name-instantiation-phase-inputs-" class="section-name selfRef">Instantiation Phase Inputs and Outputs</a>
2024 </h4>
2025 <p id="section-7.2.2-1">Inputs are:<a href="#section-7.2.2-1" class="pilcrow">¶</a></p>
2026 <ul class="normal">
2027 <li class="normal" id="section-7.2.2-2.1">[Instances_of_ASA_type]: specifies which ASAs to instantiate<a href="#section-7.2.2-2.1" class="pilcrow">¶</a>
2028 </li>
2029 <li class="normal" id="section-7.2.2-2.2">[Instantiation_target_infrastructure]: specifies which
2030 resources are to be managed by the autonomic function; this can be
2031 the whole network or a subset of it like a domain, a physical
2032 segment, or even a specific list of resources.<a href="#section-7.2.2-2.2" class="pilcrow">¶</a>
2033 </li>
2034 <li class="normal" id="section-7.2.2-2.3">[Instantiation_target_parameters]: specifies which GRASP
2035 objectives are to be sent to ASAs (e.g., an optimization target)<a href="#section-7.2.2-2.3" class="pilcrow">¶</a>
2036 </li>
2037 </ul>
2038 <p id="section-7.2.2-3">Outputs are:<a href="#section-7.2.2-3" class="pilcrow">¶</a></p>
2039 <ul class="normal">
2040 <li class="normal" id="section-7.2.2-4.1">[Set_of_ASA_resources_relations]: describes which resources are managed by which ASA instances; this is
2041 not a formal message but a resulting configuration log for a set of ASAs.<a href="#section-7.2.2-4.1" class="pilcrow">¶</a>
2042 </li>
2043 </ul>
2044 </section>
2045 </div>
2046 <div id="Sec_Inst_Reqs">
2047 <section id="section-7.2.3">
2048 <h4 id="name-instantiation-phase-require">
2049 <a href="#section-7.2.3" class="section-number selfRef">7.2.3. </a><a href="#name-instantiation-phase-require" class="section-name selfRef">Instantiation Phase Requirements</a>
2050 </h4>
2051 <p id="section-7.2.3-1">The instructions described in <a href="#Sec_Inst" class="xref">Section 7.2</a> could be
2052 either of the following:<a href="#section-7.2.3-1" class="pilcrow">¶</a></p>
2053 <ul class="normal">
2054 <li class="normal" id="section-7.2.3-2.1">Sent to a targeted ASA. In this case, the receiving Agent will have to manage the
2055 specified list of [Instantiation_target_infrastructure], with the
2056 [Instantiation_target_parameters].<a href="#section-7.2.3-2.1" class="pilcrow">¶</a>
2057 </li>
2058 <li class="normal" id="section-7.2.3-2.2">Broadcast to all ASAs. In this case, the ASAs would determine from the list which
2059 ASAs would handle which [Instantiation_target_infrastructure],
2060 with the [Instantiation_target_parameters].<a href="#section-7.2.3-2.2" class="pilcrow">¶</a>
2061 </li>
2062 </ul>
2063 <p id="section-7.2.3-3">These instructions may be grouped as a specific data structure referred to
2064 as an ASA Instance Mandate. The specification of such an ASA Instance Mandate
2065 is beyond the scope of this document.<a href="#section-7.2.3-3" class="pilcrow">¶</a></p>
2066 <p id="section-7.2.3-4">The conclusion of this instantiation phase is a set of ASA
2067 instances ready to operate. These ASA instances are characterized
2068 by the resources they manage, the metrics being monitored, and the
2069 actions that can be executed (like modifying certain parameter
2070 values). The description of the ASA instance may be defined in an
2071 ASA Instance Manifest data structure. The specification of such an
2072 ASA Instance Manifest is beyond the scope of this document.<a href="#section-7.2.3-4" class="pilcrow">¶</a></p>
2073 <p id="section-7.2.3-5">The ASA Instance Manifest does not only serve informational
2074 purposes such as acknowledgement of successful instantiation to the
2075 operator but is also necessary for further autonomic operations with:<a href="#section-7.2.3-5" class="pilcrow">¶</a></p>
2076 <ul class="normal">
2077 <li class="normal" id="section-7.2.3-6.1">coordinated entities (see <a href="#coordi" class="xref">Section 8.1</a>)<a href="#section-7.2.3-6.1" class="pilcrow">¶</a>
2078 </li>
2079 <li class="normal" id="section-7.2.3-6.2">collaborative entities with purposes such as to establish knowledge exchange
2080 (some ASAs may produce knowledge or monitor metrics that would be useful for other ASAs)<a href="#section-7.2.3-6.2" class="pilcrow">¶</a>
2081 </li>
2082 </ul>
2083 </section>
2084 </div>
2085 </section>
2086 </div>
2087 <div id="Sec_Operation">
2088 <section id="section-7.3">
2089 <h3 id="name-operation-phase">
2090 <a href="#section-7.3" class="section-number selfRef">7.3. </a><a href="#name-operation-phase" class="section-name selfRef">Operation Phase</a>
2091 </h3>
2092 <p id="section-7.3-1">During the operation phase, the operator can:<a href="#section-7.3-1" class="pilcrow">¶</a></p>
2093 <ul class="normal">
2094 <li class="normal" id="section-7.3-2.1">activate/deactivate ASAs: enable/disable their autonomic loops<a href="#section-7.3-2.1" class="pilcrow">¶</a>
2095 </li>
2096 <li class="normal" id="section-7.3-2.2">modify ASA targets: set different technical objectives<a href="#section-7.3-2.2" class="pilcrow">¶</a>
2097 </li>
2098 <li class="normal" id="section-7.3-2.3">modify ASAs managed resources: update the Instance Mandate to specify a different set of resources to
2099 manage (only applicable to decoupled ASAs)<a href="#section-7.3-2.3" class="pilcrow">¶</a>
2100 </li>
2101 </ul>
2102 <p id="section-7.3-3">During the operation phase, running ASAs can interact with other ASAs:<a href="#section-7.3-3" class="pilcrow">¶</a></p>
2103 <ul class="normal">
2104 <li class="normal" id="section-7.3-4.1">in order to exchange knowledge (e.g., an ASA providing traffic
2105 predictions to a load balancing ASA)<a href="#section-7.3-4.1" class="pilcrow">¶</a>
2106 </li>
2107 <li class="normal" id="section-7.3-4.2">in order to collaboratively reach an objective (e.g., ASAs
2108 pertaining to the same autonomic function will collaborate, e.g., in
2109 the case of a load balancing function, by modifying link metrics
2110 according to neighboring resource loads)<a href="#section-7.3-4.2" class="pilcrow">¶</a>
2111 </li>
2112 </ul>
2113 <p id="section-7.3-5">During the operation phase, running ASAs are expected to apply
2114 coordination schemes as per <a href="#coordi" class="xref">Section 8.1</a>.<a href="#section-7.3-5" class="pilcrow">¶</a></p>
2115 </section>
2116 </div>
2117 <div id="Sec_Removal">
2118 <section id="section-7.4">
2119 <h3 id="name-removal-phase">
2120 <a href="#section-7.4" class="section-number selfRef">7.4. </a><a href="#name-removal-phase" class="section-name selfRef">Removal Phase</a>
2121 </h3>
2122 <p id="section-7.4-1">When an ASA is removed from service and uninstalled, the above steps
2123 are reversed. It is important
2124 that its data, especially any security key material, is purged.<a href="#section-7.4-1" class="pilcrow">¶</a></p>
2125 </section>
2126 </div>
2127 </section>
2128 </div>
2129 <div id="coordm">
2130 <section id="section-8">
2131 <h2 id="name-coordination-and-data-model">
2132 <a href="#section-8" class="section-number selfRef">8. </a><a href="#name-coordination-and-data-model" class="section-name selfRef">Coordination and Data Models</a>
2133 </h2>
2134 <div id="coordi">
2135 <section id="section-8.1">
2136 <h3 id="name-coordination-between-autono">
2137 <a href="#section-8.1" class="section-number selfRef">8.1. </a><a href="#name-coordination-between-autono" class="section-name selfRef">Coordination between Autonomic Functions</a>
2138 </h3>
2139 <p id="section-8.1-1">Some autonomic functions will be completely independent of each
2140 other. However, others are at risk of interfering with each other; for
2141 example, two different optimization functions might both attempt to
2142 modify the same underlying parameter in different ways. In a complete
2143 system, a method is needed for identifying ASAs that might
2144 interfere with each other and coordinating their actions when
2145 necessary.<a href="#section-8.1-1" class="pilcrow">¶</a></p>
2146 </section>
2147 </div>
2148 <div id="coordt">
2149 <section id="section-8.2">
2150 <h3 id="name-coordination-with-tradition">
2151 <a href="#section-8.2" class="section-number selfRef">8.2. </a><a href="#name-coordination-with-tradition" class="section-name selfRef">Coordination with Traditional Management Functions</a>
2152 </h3>
2153 <p id="section-8.2-1">Some ASAs will have functions that overlap with existing
2154 configuration tools and network management mechanisms such as
2155 command-line interfaces, DHCP, DHCPv6, SNMP, NETCONF, and RESTCONF.
2156 This is, of course, an existing problem whenever multiple configuration
2157 tools are in use by the NOC. Each ASA designer will need to consider
2158 this issue and how to avoid clashes and inconsistencies in various
2159 deployment scenarios. Some specific considerations for interaction with
2160 OAM tools are given in <span>[<a href="#RFC8368" class="xref">RFC8368</a>]</span>. As another example,
2161 <span>[<a href="#RFC8992" class="xref">RFC8992</a>]</span> describes how autonomic management of IPv6
2162 prefixes can interact with prefix delegation via DHCPv6. The description
2163 of a GRASP objective and of an ASA using it should include a discussion
2164 of any such interactions.<a href="#section-8.2-1" class="pilcrow">¶</a></p>
2165 </section>
2166 </div>
2167 <div id="datam">
2168 <section id="section-8.3">
2169 <h3 id="name-data-models">
2170 <a href="#section-8.3" class="section-number selfRef">8.3. </a><a href="#name-data-models" class="section-name selfRef">Data Models</a>
2171 </h3>
2172 <p id="section-8.3-1">Management functions often include a shared data model, quite likely
2173 to be expressed in a formal notation such as YANG. This aspect should
2174 not be an afterthought in the design of an ASA. To the contrary, the
2175 design of the ASA and of its GRASP objectives should match the data
2176 model; as noted in <a href="#objdes" class="xref">Section 6</a>, YANG serialized as CBOR may
2177 be used directly as the value of a GRASP objective.<a href="#section-8.3-1" class="pilcrow">¶</a></p>
2178 </section>
2179 </div>
2180 </section>
2181 </div>
2182 <div id="robust">
2183 <section id="section-9">
2184 <h2 id="name-robustness">
2185 <a href="#section-9" class="section-number selfRef">9. </a><a href="#name-robustness" class="section-name selfRef">Robustness</a>
2186 </h2>
2187 <p id="section-9-1">It is of great importance that all components of an autonomic system
2188 are highly robust. Although ASA designers should aim for their
2189 component to never fail, it is more important to design the ASA to
2190 assume that failures will happen and to gracefully recover from those
2191 failures when they occur. Hence, this section lists various aspects of
2192 robustness that ASA designers should consider:<a href="#section-9-1" class="pilcrow">¶</a></p>
2193 <ol start="1" type="1" class="normal type-1" id="section-9-2">
2194 <li id="section-9-2.1">If despite all precautions, an ASA does encounter a fatal error,
2195 it should in any case restart automatically and try again. To
2196 mitigate a loop in case of persistent failure, a suitable pause should
2197 be inserted before such a restart. The length of the pause depends on
2198 the use case; randomization and exponential backoff should be
2199 considered.<a href="#section-9-2.1" class="pilcrow">¶</a>
2200 </li>
2201 <li id="section-9-2.2">If a newly received or calculated value for a parameter falls out
2202 of bounds, the corresponding parameter should be either left unchanged
2203 or restored to a value known to be safe in all configurations.<a href="#section-9-2.2" class="pilcrow">¶</a>
2204 </li>
2205 <li id="section-9-2.3">If a GRASP synchronization or negotiation session fails for any
2206 reason, it may be repeated after a suitable pause. The length of the
2207 pause depends on the use case; randomization and exponential backoff
2208 should be considered.<a href="#section-9-2.3" class="pilcrow">¶</a>
2209 </li>
2210 <li id="section-9-2.4">If a session fails repeatedly, the ASA should consider that its
2211 peer has failed, and it should cause GRASP to flush its discovery cache and
2212 repeat peer discovery.<a href="#section-9-2.4" class="pilcrow">¶</a>
2213 </li>
2214 <li id="section-9-2.5">In any case, it may be prudent to repeat discovery periodically,
2215 depending on the use case.<a href="#section-9-2.5" class="pilcrow">¶</a>
2216 </li>
2217 <li id="section-9-2.6">Any received GRASP message should be checked. If it is wrongly
2218 formatted, it should be ignored. Within a unicast session, an Invalid
2219 message (M_INVALID) may be sent. This function may be provided by the
2220 GRASP implementation itself.<a href="#section-9-2.6" class="pilcrow">¶</a>
2221 </li>
2222 <li id="section-9-2.7">Any received GRASP objective should be checked. Basic formatting
2223 errors like invalid CBOR will likely be detected by GRASP itself, but
2224 the ASA is responsible for checking the precise syntax and semantics
2225 of a received objective. If it is wrongly formatted, it should be
2226 ignored. Within a negotiation session, a Negotiation End message
2227 (M_END) with a Decline option (O_DECLINE) should be sent. An ASA may
2228 log such events for diagnostic purposes.<a href="#section-9-2.7" class="pilcrow">¶</a>
2229 </li>
2230 <li id="section-9-2.8">On the other hand, the definitions of GRASP objectives are very
2231 likely to be extended, using the flexibility of CBOR or JSON.
2232 Therefore, ASAs should be able to deal gracefully with unknown components
2233 within the values of objectives. The specification of an objective should
2234 describe how unknown components are to be handled (ignored, logged and
2235 ignored, or rejected as an error).<a href="#section-9-2.8" class="pilcrow">¶</a>
2236 </li>
2237 <li id="section-9-2.9">If an ASA receives either an Invalid message (M_INVALID) or a Negotiation End
2238 message (M_END) with a Decline option (O_DECLINE), one possible reason is that
2239 the peer ASA does not support a new feature of either GRASP or the objective
2240 in question. In such a case, the ASA may choose to repeat the operation concerned
2241 without using that new feature.<a href="#section-9-2.9" class="pilcrow">¶</a>
2242 </li>
2243 <li id="section-9-2.10">All other possible exceptions should be handled in an orderly
2244 way. There should be no such thing as an unhandled exception (but see
2245 point 1 above).<a href="#section-9-2.10" class="pilcrow">¶</a>
2246 </li>
2247 </ol>
2248 <p id="section-9-3">At a slightly more general level, ASAs are not services in themselves,
2249 but they automate services. This has a fundamental impact on how to design
2250 robust ASAs. In general, when an ASA observes a particular state (1) of
2251 operations of the services/resources it controls, it typically aims to
2252 improve this state to a better state, say (2). Ideally, the ASA is built
2253 so that it can ensure that any error encountered can still lead to
2254 returning to (1) instead of a state (3), which is worse than (1). One
2255 example instance of this principle is "make-before-break" used in
2256 reconfiguration of routing protocols in manual operations. This principle
2257 of operations can accordingly be coded into the operation of an ASA. The
2258 GRASP dry run option mentioned in <a href="#objdes" class="xref">Section 6</a> is another tool
2259 helpful for this ASA design goal of "test-before-make".<a href="#section-9-3" class="pilcrow">¶</a></p>
2260 </section>
2261 </div>
2262 <div id="security">
2263 <section id="section-10">
2264 <h2 id="name-security-considerations">
2265 <a href="#section-10" class="section-number selfRef">10. </a><a href="#name-security-considerations" class="section-name selfRef">Security Considerations</a>
2266 </h2>
2267 <p id="section-10-1">ASAs are intended to run in an environment that is protected by the
2268 Autonomic Control Plane <span>[<a href="#RFC8994" class="xref">RFC8994</a>]</span>, admission to which
2269 depends on an initial secure bootstrap process such as BRSKI <span>[<a href="#RFC8995" class="xref">RFC8995</a>]</span>. Those documents describe security considerations
2270 relating to the use of and properties provided by the ACP and BRSKI,
2271 respectively. Such an ACP can provide keying material for mutual
2272 authentication between ASAs as well as confidential communication
2273 channels for messages between ASAs. In some deployments, a secure
2274 partition of the link layer might be used instead. GRASP itself has
2275 significant security considerations <span>[<a href="#RFC8990" class="xref">RFC8990</a>]</span>. However,
2276 this does not relieve ASAs of responsibility for security. When ASAs
2277 configure or manage network elements outside the ACP, potentially in a
2278 different physical node, they must interact with other non-autonomic
2279 software components to perform their management functions. The details
2280 are specific to each case, but this has an important security
2281 implication. An ASA might act as a loophole by which the managed entity
2282 could penetrate the security boundary of the ANI. Thus, ASAs must be
2283 designed to avoid loopholes such as passing on executable code or
2284 proxying unverified commands and should, if possible, operate in an
2285 unprivileged mode. In particular, they must use secure coding
2286 practices, e.g., carefully validate all incoming information and avoid
2287 unnecessary elevation of privilege. This will apply in particular when
2288 an ASA interacts with a management component such as a NETCONF
2289 server.<a href="#section-10-1" class="pilcrow">¶</a></p>
2290 <p id="section-10-2">A similar situation will arise if an ASA acts as a gateway between
2291 two separate autonomic networks, i.e., it has access to two separate
2292 ACPs. Such an ASA must also be designed to avoid loopholes and to
2293 validate incoming information from both sides.<a href="#section-10-2" class="pilcrow">¶</a></p>
2294 <p id="section-10-3">As a reminder, GRASP does not intrinsically provide transactional
2295 integrity (<a href="#objdes" class="xref">Section 6</a>).<a href="#section-10-3" class="pilcrow">¶</a></p>
2296 <p id="section-10-4">As appropriate to their specific functions, ASAs should take account
2297 of relevant privacy considerations <span>[<a href="#RFC6973" class="xref">RFC6973</a>]</span>.<a href="#section-10-4" class="pilcrow">¶</a></p>
2298 <p id="section-10-5">The initial version of the autonomic infrastructure assumes that all
2299 autonomic nodes are trusted by virtue of their admission to the ACP.
2300 ASAs are therefore trusted to manipulate any GRASP objective simply
2301 because they are installed on a node that has successfully joined the
2302 ACP. In the general case, a node may have multiple roles, and a role may
2303 use multiple ASAs, each using multiple GRASP objectives. Additional
2304 mechanisms for the fine-grained authorization of nodes and ASAs to
2305 manipulate specific GRASP objectives could be designed. Meanwhile, we
2306 repeat that ASAs should run without special privilege if possible.
2307 Independently of this, interfaces between ASAs and the router
2308 configuration and monitoring services of the node can be subject to
2309 authentication that provides more fine-grained authorization for
2310 specific services. These additional authentication parameters could be
2311 passed to an ASA during its instantiation phase.<a href="#section-10-5" class="pilcrow">¶</a></p>
2312 </section>
2313 </div>
2314 <div id="iana">
2315 <section id="section-11">
2316 <h2 id="name-iana-considerations">
2317 <a href="#section-11" class="section-number selfRef">11. </a><a href="#name-iana-considerations" class="section-name selfRef">IANA Considerations</a>
2318 </h2>
2319 <p id="section-11-1">This document has no IANA actions.<a href="#section-11-1" class="pilcrow">¶</a></p>
2320 </section>
2321 </div>
2322 <section id="section-12">
2323 <h2 id="name-references">
2324 <a href="#section-12" class="section-number selfRef">12. </a><a href="#name-references" class="section-name selfRef">References</a>
2325 </h2>
2326 <section id="section-12.1">
2327 <h3 id="name-normative-references">
2328 <a href="#section-12.1" class="section-number selfRef">12.1. </a><a href="#name-normative-references" class="section-name selfRef">Normative References</a>
2329 </h3>
2330 <dl class="references">
2331 <dt id="RFC8949">[RFC8949]</dt>
2332 <dd>
2333 <span class="refAuthor">Bormann, C.</span> and <span class="refAuthor">P. Hoffman</span>, <span class="refTitle">"Concise Binary Object Representation (CBOR)"</span>, <span class="seriesInfo">STD 94</span>, <span class="seriesInfo">RFC 8949</span>, <span class="seriesInfo">DOI 10.17487/RFC8949</span>, <time datetime="2020-12" class="refDate">December 2020</time>, <span>&lt;<a href="https://www.rfc-editor.org/info/rfc8949">https://www.rfc-editor.org/info/rfc8949</a>&gt;</span>. </dd>
2334 <dd class="break"></dd>
2335 <dt id="RFC8990">[RFC8990]</dt>
2336 <dd>
2337 <span class="refAuthor">Bormann, C.</span>, <span class="refAuthor">Carpenter, B., Ed.</span>, and <span class="refAuthor">B. Liu, Ed.</span>, <span class="refTitle">"GeneRic Autonomic Signaling Protocol (GRASP)"</span>, <span class="seriesInfo">RFC 8990</span>, <span class="seriesInfo">DOI 10.17487/RFC8990</span>, <time datetime="2021-05" class="refDate">May 2021</time>, <span>&lt;<a href="https://www.rfc-editor.org/info/rfc8990">https://www.rfc-editor.org/info/rfc8990</a>&gt;</span>. </dd>
2338 <dd class="break"></dd>
2339 <dt id="RFC8994">[RFC8994]</dt>
2340 <dd>
2341 <span class="refAuthor">Eckert, T., Ed.</span>, <span class="refAuthor">Behringer, M., Ed.</span>, and <span class="refAuthor">S. Bjarnason</span>, <span class="refTitle">"An Autonomic Control Plane (ACP)"</span>, <span class="seriesInfo">RFC 8994</span>, <span class="seriesInfo">DOI 10.17487/RFC8994</span>, <time datetime="2021-05" class="refDate">May 2021</time>, <span>&lt;<a href="https://www.rfc-editor.org/info/rfc8994">https://www.rfc-editor.org/info/rfc8994</a>&gt;</span>. </dd>
2342 <dd class="break"></dd>
2343 <dt id="RFC8995">[RFC8995]</dt>
2344 <dd>
2345 <span class="refAuthor">Pritikin, M.</span>, <span class="refAuthor">Richardson, M.</span>, <span class="refAuthor">Eckert, T.</span>, <span class="refAuthor">Behringer, M.</span>, and <span class="refAuthor">K. Watsen</span>, <span class="refTitle">"Bootstrapping Remote Secure Key Infrastructure (BRSKI)"</span>, <span class="seriesInfo">RFC 8995</span>, <span class="seriesInfo">DOI 10.17487/RFC8995</span>, <time datetime="2021-05" class="refDate">May 2021</time>, <span>&lt;<a href="https://www.rfc-editor.org/info/rfc8995">https://www.rfc-editor.org/info/rfc8995</a>&gt;</span>. </dd>
2346 <dd class="break"></dd>
2347 </dl>
2348 </section>
2349 <section id="section-12.2">
2350 <h3 id="name-informative-references">
2351 <a href="#section-12.2" class="section-number selfRef">12.2. </a><a href="#name-informative-references" class="section-name selfRef">Informative References</a>
2352 </h3>
2353 <dl class="references">
2354 <dt id="I-D.peloso-anima-autonomic-function">[AUTONOMIC-FUNCTION]</dt>
2355 <dd>
2356 <span class="refAuthor">Pierre, P.</span> and <span class="refAuthor">L. Ciavaglia</span>, <span class="refTitle">"A Day in the Life of an Autonomic Function"</span>, <span class="refContent">Work in Progress</span>, <span class="seriesInfo">Internet-Draft, draft-peloso-anima-autonomic-function-01</span>, <time datetime="2016-03-21" class="refDate">21 March 2016</time>, <span>&lt;<a href="https://datatracker.ietf.org/doc/html/draft-peloso-anima-autonomic-function-01">https://datatracker.ietf.org/doc/html/draft-peloso-anima-autonomic-function-01</a>&gt;</span>. </dd>
2357 <dd class="break"></dd>
2358 <dt id="I-D.ietf-core-yang-cbor">[CBOR-YANG]</dt>
2359 <dd>
2360 <span class="refAuthor">Veillette, M., Ed.</span>, <span class="refAuthor">Petrov, I., Ed.</span>, <span class="refAuthor">Pelov, A.</span>, <span class="refAuthor">Bormann, C.</span>, and <span class="refAuthor">M. Richardson</span>, <span class="refTitle">"CBOR Encoding of Data Modeled with YANG"</span>, <span class="refContent">Work in Progress</span>, <span class="seriesInfo">Internet-Draft, draft-ietf-core-yang-cbor-18</span>, <time datetime="2021-12" class="refDate">December 2021</time>, <span>&lt;<a href="https://datatracker.ietf.org/doc/html/draft-ietf-core-yang-cbor-18">https://datatracker.ietf.org/doc/html/draft-ietf-core-yang-cbor-18</a>&gt;</span>. </dd>
2361 <dd class="break"></dd>
2362 <dt id="DEMOLA06">[DEMOLA06]</dt>
2363 <dd>
2364 <span class="refAuthor">De Mola, F.</span> and <span class="refAuthor">R. Quitadamo</span>, <span class="refTitle">"Towards an Agent Model for Future Autonomic Communications"</span>, <span class="seriesInfo">Proceedings of the 7th WOA 2006 Workshop From Objects to Agents 51-59</span>, <time datetime="2006-09" class="refDate">September 2006</time>. </dd>
2365 <dd class="break"></dd>
2366 <dt id="GANA13">[GANA13]</dt>
2367 <dd>
2368 <span class="refAuthor">ETSI</span>, <span class="refTitle">"Autonomic network engineering for the self-managing Future Internet (AFI); Generic Autonomic Network Architecture (An Architectural Reference Model for Autonomic Networking, Cognitive Networking and Self-Management)"</span>, <span class="refContent">GS AFI 002</span>, <span class="refContent">V1.1.1</span>, <time datetime="2013-04" class="refDate">April 2013</time>, <span>&lt;<a href="https://www.etsi.org/deliver/etsi_gs/AFI/001_099/002/01.01.01_60/gs_afi002v010101p.pdf">https://www.etsi.org/deliver/etsi_gs/AFI/001_099/002/01.01.01_60/gs_afi002v010101p.pdf</a>&gt;</span>. </dd>
2369 <dd class="break"></dd>
2370 <dt id="HUEBSCHER08">[HUEBSCHER08]</dt>
2371 <dd>
2372 <span class="refAuthor">Huebscher, M. C.</span> and <span class="refAuthor">J. A. McCann</span>, <span class="refTitle">"A survey of autonomic computing - degrees, models, and applications"</span>, <span class="refContent">ACM Computing Surveys (CSUR)</span>, <span class="refContent">Volume 40, Issue 3</span>, <span class="seriesInfo">DOI 10.1145/1380584.1380585</span>, <time datetime="2008-08" class="refDate">August 2008</time>, <span>&lt;<a href="https://doi.org/10.1145/1380584.1380585">https://doi.org/10.1145/1380584.1380585</a>&gt;</span>. </dd>
2373 <dd class="break"></dd>
2374 <dt id="I-D.irtf-nmrg-ibn-concepts-definitions">[IBN-CONCEPTS]</dt>
2375 <dd>
2376 <span class="refAuthor">Clemm, A.</span>, <span class="refAuthor">Ciavaglia, L.</span>, <span class="refAuthor">Granville, L. Z.</span>, and <span class="refAuthor">J. Tantsura</span>, <span class="refTitle">"Intent-Based Networking - Concepts and Definitions"</span>, <span class="refContent">Work in Progress</span>, <span class="seriesInfo">Internet-Draft, draft-irtf-nmrg-ibn-concepts-definitions-09</span>, <time datetime="2022-03-24" class="refDate">24 March 2022</time>, <span>&lt;<a href="https://datatracker.ietf.org/doc/html/draft-irtf-nmrg-ibn-concepts-definitions-09">https://datatracker.ietf.org/doc/html/draft-irtf-nmrg-ibn-concepts-definitions-09</a>&gt;</span>. </dd>
2377 <dd class="break"></dd>
2378 <dt id="IPJ">[IPJ]</dt>
2379 <dd>
2380 <span class="refAuthor">Behringer, M.</span>, <span class="refAuthor">Bormann, C.</span>, <span class="refAuthor">Carpenter, B. E.</span>, <span class="refAuthor">Eckert, T.</span>, <span class="refAuthor">Campos Nobre, J.</span>, <span class="refAuthor">Jiang, S.</span>, <span class="refAuthor">Li, Y.</span>, and <span class="refAuthor">M. C. Richardson</span>, <span class="refTitle">"Autonomic Networking Gets Serious"</span>, <span class="refContent">The Internet Protocol Journal</span>, <span class="refContent">Volume 24, Issue 3, Page(s) 2 - 18</span>, <span class="refContent">ISSN 1944-1134</span>, <time datetime="2021-10" class="refDate">October 2021</time>, <span>&lt;<a href="https://ipj.dreamhosters.com/wp-content/uploads/2021/10/243-ipj.pdf">https://ipj.dreamhosters.com/wp-content/uploads/2021/10/243-ipj.pdf</a>&gt;</span>. </dd>
2381 <dd class="break"></dd>
2382 <dt id="MOVAHEDI12">[MOVAHEDI12]</dt>
2383 <dd>
2384 <span class="refAuthor">Movahedi, Z.</span>, <span class="refAuthor">Ayari, M.</span>, <span class="refAuthor">Langar, R.</span>, and <span class="refAuthor">G. Pujolle</span>, <span class="refTitle">"A Survey of Autonomic Network Architectures and Evaluation Criteria"</span>, <span class="refContent">IEEE Communications Surveys &amp; Tutorials</span>, <span class="refContent">Volume 14, Issue 2, Pages 464 - 490</span>, <span class="seriesInfo">DOI 10.1109/SURV.2011.042711.00078</span>, <time datetime="2012" class="refDate">2012</time>, <span>&lt;<a href="https://doi.org/10.1109/SURV.2011.042711.00078">https://doi.org/10.1109/SURV.2011.042711.00078</a>&gt;</span>. </dd>
2385 <dd class="break"></dd>
2386 <dt id="NFV">[NFV]</dt>
2387 <dd>
2388 <span class="refAuthor">ETSI</span>, <span class="refTitle">"Network Functions Virtualisation"</span>, <span class="refContent">SDN and OpenFlow World Congress</span>, <time datetime="2012-10" class="refDate">October 2012</time>, <span>&lt;<a href="https://portal.etsi.org/NFV/NFV_White_Paper.pdf">https://portal.etsi.org/NFV/NFV_White_Paper.pdf</a>&gt;</span>. </dd>
2389 <dd class="break"></dd>
2390 <dt id="RFC6241">[RFC6241]</dt>
2391 <dd>
2392 <span class="refAuthor">Enns, R., Ed.</span>, <span class="refAuthor">Bjorklund, M., Ed.</span>, <span class="refAuthor">Schoenwaelder, J., Ed.</span>, and <span class="refAuthor">A. Bierman, Ed.</span>, <span class="refTitle">"Network Configuration Protocol (NETCONF)"</span>, <span class="seriesInfo">RFC 6241</span>, <span class="seriesInfo">DOI 10.17487/RFC6241</span>, <time datetime="2011-06" class="refDate">June 2011</time>, <span>&lt;<a href="https://www.rfc-editor.org/info/rfc6241">https://www.rfc-editor.org/info/rfc6241</a>&gt;</span>. </dd>
2393 <dd class="break"></dd>
2394 <dt id="RFC6973">[RFC6973]</dt>
2395 <dd>
2396 <span class="refAuthor">Cooper, A.</span>, <span class="refAuthor">Tschofenig, H.</span>, <span class="refAuthor">Aboba, B.</span>, <span class="refAuthor">Peterson, J.</span>, <span class="refAuthor">Morris, J.</span>, <span class="refAuthor">Hansen, M.</span>, and <span class="refAuthor">R. Smith</span>, <span class="refTitle">"Privacy Considerations for Internet Protocols"</span>, <span class="seriesInfo">RFC 6973</span>, <span class="seriesInfo">DOI 10.17487/RFC6973</span>, <time datetime="2013-07" class="refDate">July 2013</time>, <span>&lt;<a href="https://www.rfc-editor.org/info/rfc6973">https://www.rfc-editor.org/info/rfc6973</a>&gt;</span>. </dd>
2397 <dd class="break"></dd>
2398 <dt id="RFC7575">[RFC7575]</dt>
2399 <dd>
2400 <span class="refAuthor">Behringer, M.</span>, <span class="refAuthor">Pritikin, M.</span>, <span class="refAuthor">Bjarnason, S.</span>, <span class="refAuthor">Clemm, A.</span>, <span class="refAuthor">Carpenter, B.</span>, <span class="refAuthor">Jiang, S.</span>, and <span class="refAuthor">L. Ciavaglia</span>, <span class="refTitle">"Autonomic Networking: Definitions and Design Goals"</span>, <span class="seriesInfo">RFC 7575</span>, <span class="seriesInfo">DOI 10.17487/RFC7575</span>, <time datetime="2015-06" class="refDate">June 2015</time>, <span>&lt;<a href="https://www.rfc-editor.org/info/rfc7575">https://www.rfc-editor.org/info/rfc7575</a>&gt;</span>. </dd>
2401 <dd class="break"></dd>
2402 <dt id="RFC7665">[RFC7665]</dt>
2403 <dd>
2404 <span class="refAuthor">Halpern, J., Ed.</span> and <span class="refAuthor">C. Pignataro, Ed.</span>, <span class="refTitle">"Service Function Chaining (SFC) Architecture"</span>, <span class="seriesInfo">RFC 7665</span>, <span class="seriesInfo">DOI 10.17487/RFC7665</span>, <time datetime="2015-10" class="refDate">October 2015</time>, <span>&lt;<a href="https://www.rfc-editor.org/info/rfc7665">https://www.rfc-editor.org/info/rfc7665</a>&gt;</span>. </dd>
2405 <dd class="break"></dd>
2406 <dt id="RFC8368">[RFC8368]</dt>
2407 <dd>
2408 <span class="refAuthor">Eckert, T., Ed.</span> and <span class="refAuthor">M. Behringer</span>, <span class="refTitle">"Using an Autonomic Control Plane for Stable Connectivity of Network Operations, Administration, and Maintenance (OAM)"</span>, <span class="seriesInfo">RFC 8368</span>, <span class="seriesInfo">DOI 10.17487/RFC8368</span>, <time datetime="2018-05" class="refDate">May 2018</time>, <span>&lt;<a href="https://www.rfc-editor.org/info/rfc8368">https://www.rfc-editor.org/info/rfc8368</a>&gt;</span>. </dd>
2409 <dd class="break"></dd>
2410 <dt id="RFC8991">[RFC8991]</dt>
2411 <dd>
2412 <span class="refAuthor">Carpenter, B.</span>, <span class="refAuthor">Liu, B., Ed.</span>, <span class="refAuthor">Wang, W.</span>, and <span class="refAuthor">X. Gong</span>, <span class="refTitle">"GeneRic Autonomic Signaling Protocol Application Program Interface (GRASP API)"</span>, <span class="seriesInfo">RFC 8991</span>, <span class="seriesInfo">DOI 10.17487/RFC8991</span>, <time datetime="2021-05" class="refDate">May 2021</time>, <span>&lt;<a href="https://www.rfc-editor.org/info/rfc8991">https://www.rfc-editor.org/info/rfc8991</a>&gt;</span>. </dd>
2413 <dd class="break"></dd>
2414 <dt id="RFC8992">[RFC8992]</dt>
2415 <dd>
2416 <span class="refAuthor">Jiang, S., Ed.</span>, <span class="refAuthor">Du, Z.</span>, <span class="refAuthor">Carpenter, B.</span>, and <span class="refAuthor">Q. Sun</span>, <span class="refTitle">"Autonomic IPv6 Edge Prefix Management in Large-Scale Networks"</span>, <span class="seriesInfo">RFC 8992</span>, <span class="seriesInfo">DOI 10.17487/RFC8992</span>, <time datetime="2021-05" class="refDate">May 2021</time>, <span>&lt;<a href="https://www.rfc-editor.org/info/rfc8992">https://www.rfc-editor.org/info/rfc8992</a>&gt;</span>. </dd>
2417 <dd class="break"></dd>
2418 <dt id="RFC8993">[RFC8993]</dt>
2419 <dd>
2420 <span class="refAuthor">Behringer, M., Ed.</span>, <span class="refAuthor">Carpenter, B.</span>, <span class="refAuthor">Eckert, T.</span>, <span class="refAuthor">Ciavaglia, L.</span>, and <span class="refAuthor">J. Nobre</span>, <span class="refTitle">"A Reference Model for Autonomic Networking"</span>, <span class="seriesInfo">RFC 8993</span>, <span class="seriesInfo">DOI 10.17487/RFC8993</span>, <time datetime="2021-05" class="refDate">May 2021</time>, <span>&lt;<a href="https://www.rfc-editor.org/info/rfc8993">https://www.rfc-editor.org/info/rfc8993</a>&gt;</span>. </dd>
2421 <dd class="break"></dd>
2422 <dt id="ZSM009-1">[ZSM009-1]</dt>
2423 <dd>
2424 <span class="refAuthor">ETSI</span>, <span class="refTitle">"Zero-touch network and Service Management (ZSM); Closed-Loop Automation; Part 1: Enablers"</span>, <span class="refContent">GS ZSM 009-1</span>, <span class="refContent">Version 1.1.1</span>, <time datetime="2021-06" class="refDate">June 2021</time>, <span>&lt;<a href="https://www.etsi.org/deliver/etsi_gs/ZSM/001_099/00901/01.01.01_60/gs_ZSM00901v010101p.pdf">https://www.etsi.org/deliver/etsi_gs/ZSM/001_099/00901/01.01.01_60/gs_ZSM00901v010101p.pdf</a>&gt;</span>. </dd>
2425 <dd class="break"></dd>
2426 </dl>
2427 </section>
2428 </section>
2429 <div id="eg">
2430 <section id="appendix-A">
2431 <h2 id="name-example-logic-flows">
2432 <a href="#appendix-A" class="section-number selfRef">Appendix A. </a><a href="#name-example-logic-flows" class="section-name selfRef">Example Logic Flows</a>
2433 </h2>
2434 <p id="appendix-A-1">This appendix describes generic logic flows that combine to act as an
2435 Autonomic Service Agent (ASA) for resource management. Note that these
2436 are illustrative examples and are in no sense requirements. As long as
2437 the rules of GRASP are followed, a real implementation could be
2438 different. The reader is assumed to be familiar with GRASP <span>[<a href="#RFC8990" class="xref">RFC8990</a>]</span> and its conceptual API <span>[<a href="#RFC8991" class="xref">RFC8991</a>]</span>.<a href="#appendix-A-1" class="pilcrow">¶</a></p>
2439 <p id="appendix-A-2">A complete autonomic function for a distributed resource will consist
2440 of a number of instances of the ASA placed at relevant points in a
2441 network. Specific details will, of course, depend on the resource
2442 concerned. One example is IP address prefix management, as specified in
2443 <span>[<a href="#RFC8992" class="xref">RFC8992</a>]</span>. In this case, an instance of the ASA will
2444 exist in each delegating router.<a href="#appendix-A-2" class="pilcrow">¶</a></p>
2445 <p id="appendix-A-3">
2446 An underlying assumption is that there is an initial source of the resource in
2447 question, referred to here as an origin ASA. The other ASAs, known as
2448 delegators, obtain supplies of the resource from the origin, delegate
2449 quantities of the resource to consumers that request it, and recover it when
2450 no longer needed.<a href="#appendix-A-3" class="pilcrow">¶</a></p>
2451 <p id="appendix-A-4">
2452 Another assumption is there is a set of network-wide policy parameters, which
2453 the origin will provide to the delegators. These parameters will control how
2454 the delegators decide how much resource to provide to consumers. Thus, the
2455 ASA logic has two operating modes: origin and delegator. When running as an
2456 origin, it starts by obtaining a quantity of the resource from the NOC, and it
2457 acts as a source of policy parameters, via both GRASP flooding and GRASP
2458 synchronization. (In some scenarios, flooding or synchronization alone might
2459 be sufficient, but this example includes both.)<a href="#appendix-A-4" class="pilcrow">¶</a></p>
2460 <p id="appendix-A-5">
2461 When running as a delegator, it starts with an empty resource pool,
2462 acquires the policy parameters by GRASP synchronization, and delegates
2463 quantities of the resource to consumers that request it. Both as an origin and as a delegator, when its pool is low,
2464 it seeks quantities of the resource by
2465 requesting GRASP negotiation with peer ASAs. When its pool is sufficient, it
2466 hands out resource to peer ASAs in response to negotiation requests. Thus,
2467 over time, the initial resource pool held by the origin will be shared among
2468 all the delegators according to demand.<a href="#appendix-A-5" class="pilcrow">¶</a></p>
2469 <p id="appendix-A-6">
2470 In theory, a network could include any number of origins and any number of
2471 delegators, with the only condition being that each origin's initial resource
2472 pool is unique. A realistic scenario is to have exactly one origin and as many
2473 delegators as you like. A scenario with no origin is useless.<a href="#appendix-A-6" class="pilcrow">¶</a></p>
2474 <p id="appendix-A-7">
2475 An implementation requirement is that resource pools are kept in stable storage. Otherwise, if a delegator exits for any reason, all the resources it has obtained or delegated are lost. If an origin exits, its entire spare pool is lost. The logic for using stable storage and for crash recovery is not included in the pseudocode below, which focuses on communication between ASAs. Since GRASP operations are not intrinsically idempotent, data integrity during failure scenarios is the responsibility of the ASA designer. This is a complex topic in its own right that is not discussed in the present document.<a href="#appendix-A-7" class="pilcrow">¶</a></p>
2476 <p id="appendix-A-8">
2477 The description below does not implement GRASP's dry run function. That would require temporarily marking any resource handed out in a dry run negotiation as reserved, until either the peer obtains it in a live run, or a suitable timeout occurs.<a href="#appendix-A-8" class="pilcrow">¶</a></p>
2478 <p id="appendix-A-9">
2479 The main data structures used in each instance of the ASA are:<a href="#appendix-A-9" class="pilcrow">¶</a></p>
2480 <ul class="normal">
2481 <li class="normal" id="appendix-A-10.1">resource_pool: an ordered list of available resources, for example. Depending on the
2482 nature of the resource, units of resource are split when appropriate, and a
2483 background garbage collector recombines split resources if they are returned
2484 to the pool.<a href="#appendix-A-10.1" class="pilcrow">¶</a>
2485 </li>
2486 <li class="normal" id="appendix-A-10.2">delegated_list: where a delegator stores the resources it has given to subsidiary devices.<a href="#appendix-A-10.2" class="pilcrow">¶</a>
2487 </li>
2488 </ul>
2489 <p id="appendix-A-11">
2490 Possible main logic flows are below, using a threaded implementation model. As noted above, alternative approaches to asynchronous operations are possible. The transformation to an event loop model should be apparent; each thread would correspond to one event in the event loop.<a href="#appendix-A-11" class="pilcrow">¶</a></p>
2491 <p id="appendix-A-12">
2492 The GRASP objectives are as follows:<a href="#appendix-A-12" class="pilcrow">¶</a></p>
2493 <ul class="normal">
2494 <li class="normal" id="appendix-A-13.1">["EX1.Resource", flags, loop_count, value], where the value depends on the resource concerned but will typically include its size and
2495 identification.<a href="#appendix-A-13.1" class="pilcrow">¶</a>
2496 </li>
2497 <li class="normal" id="appendix-A-13.2">["EX1.Params", flags, loop_count, value], where the value will be, for example, a JSON object defining the applicable parameters.<a href="#appendix-A-13.2" class="pilcrow">¶</a>
2498 </li>
2499 </ul>
2500 <p id="appendix-A-14">
2501 In the outline logic flows below, these objectives are represented simply by their names.<a href="#appendix-A-14" class="pilcrow">¶</a></p>
2502 <div id="appendix-A-15">
2503 <pre class="lang-pseudocode sourcecode">
2504 MAIN PROGRAM:
2505
2506 Create empty resource_pool (and an associated lock)
2507 Create empty delegated_list
2508 Determine whether to act as origin
2509 if origin:
2510 Obtain initial resource_pool contents from NOC
2511 Obtain value of EX1.Params from NOC
2512 Register ASA with GRASP
2513 Register GRASP objectives EX1.Resource and EX1.Params
2514 if origin:
2515 Start FLOODER thread to flood EX1.Params
2516 Start SYNCHRONIZER listener for EX1.Params
2517 Start MAIN_NEGOTIATOR thread for EX1.Resource
2518 if not origin:
2519 Obtain value of EX1.Params from GRASP flood or synchronization
2520 Start DELEGATOR thread
2521 Start GARBAGE_COLLECTOR thread
2522 good_peer = none
2523 do forever:
2524 if resource_pool is low:
2525 Calculate amount A of resource needed
2526 Discover peers using GRASP M_DISCOVER / M_RESPONSE
2527 if good_peer in peers:
2528 peer = good_peer
2529 else:
2530 peer = #any choice among peers
2531 grasp.request_negotiate("EX1.Resource", peer)
2532 #i.e., send negotiation request
2533 Wait for response (M_NEGOTIATE, M_END or M_WAIT)
2534 if OK:
2535 if offered amount of resource sufficient:
2536 Send M_END + O_ACCEPT #negotiation succeeded
2537 Add resource to pool
2538 good_peer = peer #remember this choice
2539 else:
2540 Send M_END + O_DECLINE #negotiation failed
2541 good_peer = none #forget this choice
2542 sleep() #periodic timer suitable for application scenario
2543 </pre><a href="#appendix-A-15" class="pilcrow">¶</a>
2544 </div>
2545 <div id="appendix-A-16">
2546 <pre class="lang-pseudocode sourcecode">
2547 MAIN_NEGOTIATOR thread:
2548
2549 do forever:
2550 grasp.listen_negotiate("EX1.Resource")
2551 #i.e., wait for negotiation request
2552 Start a separate new NEGOTIATOR thread for requested amount A
2553 </pre><a href="#appendix-A-16" class="pilcrow">¶</a>
2554 </div>
2555 <div id="appendix-A-17">
2556 <pre class="lang-pseudocode sourcecode">
2557 NEGOTIATOR thread:
2558
2559 Request resource amount A from resource_pool
2560 if not OK:
2561 while not OK and A &gt; Amin:
2562 A = A-1
2563 Request resource amount A from resource_pool
2564 if OK:
2565 Offer resource amount A to peer by GRASP M_NEGOTIATE
2566 if received M_END + O_ACCEPT:
2567 #negotiation succeeded
2568 elif received M_END + O_DECLINE or other error:
2569 #negotiation failed
2570 Return resource to resource_pool
2571 else:
2572 Send M_END + O_DECLINE #negotiation failed
2573 #thread exits
2574 </pre><a href="#appendix-A-17" class="pilcrow">¶</a>
2575 </div>
2576 <div id="appendix-A-18">
2577 <pre class="lang-pseudocode sourcecode">
2578 DELEGATOR thread:
2579
2580 do forever:
2581 Wait for request or release for resource amount A
2582 if request:
2583 Get resource amount A from resource_pool
2584 if OK:
2585 Delegate resource to consumer #atomic
2586 Record in delegated_list #operation
2587 else:
2588 Signal failure to consumer
2589 Signal main thread that resource_pool is low
2590 else:
2591 Delete resource from delegated_list
2592 Return resource amount A to resource_pool
2593 </pre><a href="#appendix-A-18" class="pilcrow">¶</a>
2594 </div>
2595 <div id="appendix-A-19">
2596 <pre class="lang-pseudocode sourcecode">
2597 SYNCHRONIZER thread:
2598
2599 do forever:
2600 Wait for M_REQ_SYN message for EX1.Params
2601 Reply with M_SYNCH message for EX1.Params
2602 </pre><a href="#appendix-A-19" class="pilcrow">¶</a>
2603 </div>
2604 <div id="appendix-A-20">
2605 <pre class="lang-pseudocode sourcecode">
2606 FLOODER thread:
2607
2608 do forever:
2609 Send M_FLOOD message for EX1.Params
2610 sleep() #periodic timer suitable for application scenario
2611
2612 </pre><a href="#appendix-A-20" class="pilcrow">¶</a>
2613 </div>
2614 <div id="appendix-A-21">
2615 <pre class="lang-pseudocode sourcecode">
2616 GARBAGE_COLLECTOR thread:
2617
2618 do forever:
2619 Search resource_pool for adjacent resources
2620 Merge adjacent resources
2621 sleep() #periodic timer suitable for application scenario
2622 </pre><a href="#appendix-A-21" class="pilcrow">¶</a>
2623 </div>
2624 </section>
2625 </div>
2626 <div id="ack">
2627 <section id="appendix-B">
2628 <h2 id="name-acknowledgements">
2629 <a href="#name-acknowledgements" class="section-name selfRef">Acknowledgements</a>
2630 </h2>
2631 <p id="appendix-B-1">Valuable comments were received from <span class="contact-name">Michael Behringer</span>, <span class="contact-name">Menachem Dodge</span>, <span class="contact-name">Martin Dürst</span>, <span class="contact-name">Toerless Eckert</span>,
2632 <span class="contact-name">Thomas Fossati</span>, <span class="contact-name">Alex Galis</span>,
2633 <span class="contact-name">Bing Liu</span>, <span class="contact-name">Benno Overeinder</span>,
2634 <span class="contact-name">Michael Richardson</span>, <span class="contact-name">Rob Wilton</span>, and other IESG members.<a href="#appendix-B-1" class="pilcrow">¶</a></p>
2635 </section>
2636 </div>
2637 <div id="authors-addresses">
2638 <section id="appendix-C">
2639 <h2 id="name-authors-addresses">
2640 <a href="#name-authors-addresses" class="section-name selfRef">Authors' Addresses</a>
2641 </h2>
2642 <address class="vcard">
2643 <div dir="auto" class="left"><span class="fn nameRole">Brian Carpenter</span></div>
2644 <div dir="auto" class="left"><span class="street-address">School of Computer Science<br>University of Auckland<br>PB 92019</span></div>
2645 <div dir="auto" class="left">
2646 <span class="locality">Auckland</span> <span class="postal-code">1142</span>
2647 </div>
2648 <div dir="auto" class="left"><span class="country-name">New Zealand</span></div>
2649 <div class="email">
2650 <span>Email:</span>
2651 <a href="mailto:[email protected]" class="email">[email protected]</a>
2652 </div>
2653 </address>
2654 <address class="vcard">
2655 <div dir="auto" class="left"><span class="fn nameRole">Laurent Ciavaglia</span></div>
2656 <div dir="auto" class="left"><span class="org">Rakuten Mobile</span></div>
2657 <div dir="auto" class="left"><span class="locality">Paris</span></div>
2658 <div dir="auto" class="left"><span class="country-name">France</span></div>
2659 <div class="email">
2660 <span>Email:</span>
2661 <a href="mailto:[email protected]" class="email">[email protected]</a>
2662 </div>
2663 </address>
2664 <address class="vcard">
2665 <div dir="auto" class="left"><span class="fn nameRole">Sheng Jiang</span></div>
2666 <div dir="auto" class="left"><span class="org">Huawei Technologies Co., Ltd</span></div>
2667 <div dir="auto" class="left"><span class="street-address">Q14 Huawei Campus<br>156 Beiqing Road<br>Hai-Dian District</span></div>
2668 <div dir="auto" class="left"><span class="locality">Beijing</span></div>
2669 <div dir="auto" class="left"><span class="postal-code">100095</span></div>
2670 <div dir="auto" class="left"><span class="country-name">China</span></div>
2671 <div class="email">
2672 <span>Email:</span>
2673 <a href="mailto:[email protected]" class="email">[email protected]</a>
2674 </div>
2675 </address>
2676 <address class="vcard">
2677 <div dir="auto" class="left"><span class="fn nameRole">Pierre Peloso</span></div>
2678 <div dir="auto" class="left"><span class="org">Nokia</span></div>
2679 <div dir="auto" class="left"><span class="street-address">Villarceaux</span></div>
2680 <div dir="auto" class="left">
2681 <span class="postal-code">91460</span> <span class="locality">Nozay</span>
2682 </div>
2683 <div dir="auto" class="left"><span class="country-name">France</span></div>
2684 <div class="email">
2685 <span>Email:</span>
2686 <a href="mailto:[email protected]" class="email">[email protected]</a>
2687 </div>
2688 </address>
2689 </section>
2690 </div>
2691 <script>const toc = document.getElementById("toc");
2692 toc.querySelector("h2").addEventListener("click", e => {
2693 toc.classList.toggle("active");
2694 });
2695 toc.querySelector("nav").addEventListener("click", e => {
2696 toc.classList.remove("active");
2697 });
2698 </script>
2699 </body>
2700 </html>