Debian Codegraph @

rfc8921.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 8921: Dynamic Service Negotiation: The Connectivity Provisioning Negotiation Protocol (CPNP)</title>
8 <meta content="Mohamed Boucadair" name="author">
9 <meta content="Christian Jacquenet" name="author">
10 <meta content="Dacheng Zhang" name="author">
11 <meta content="Panos Georgatsos" name="author">
12 <meta content="
13 This document defines the Connectivity Provisioning Negotiation
14 Protocol (CPNP), which is designed to facilitate the dynamic negotiation
15 of service parameters.
16 CPNP is a generic protocol that can be used for various negotiation
17 purposes that include (but are not necessarily limited to) connectivity
18 provisioning services, storage facilities, Content Delivery Networks,
19 etc.
20 " name="description">
21 <meta content="xml2rfc 3.3.0" name="generator">
22 <meta content="SDN" name="keyword">
23 <meta content="Order Request Handling" name="keyword">
24 <meta content="Automation" name="keyword">
25 <meta content="Dynamic Provisioning" name="keyword">
26 <meta content="CDN" name="keyword">
27 <meta content="Interconnection" name="keyword">
28 <meta content="Service Delivery" name="keyword">
29 <meta content="Service Activation" name="keyword">
30 <meta content="8921" name="rfc.number">
31 <!-- Generator version information:
32 xml2rfc 3.3.0
33 Python 3.6.10
34 appdirs 1.4.4
35 ConfigArgParse 1.2.3
36 google-i18n-address 2.3.5
37 html5lib 1.0.1
38 intervaltree 3.0.2
39 Jinja2 2.11.2
40 kitchen 1.2.6
41 lxml 4.4.2
42 pycairo 1.19.0
43 pycountry 19.8.18
44 pyflakes 2.1.1
45 PyYAML 5.3.1
46 requests 2.22.0
47 setuptools 40.6.2
48 six 1.14.0
49 WeasyPrint 51
50 -->
51 <link href="rfc8921.xml" rel="alternate" type="application/rfc+xml">
52 <link href="#copyright" rel="license">
53 <style type="text/css">/*
54
55 NOTE: Changes at the bottom of this file overrides some earlier settings.
56
57 Once the style has stabilized and has been adopted as an official RFC style,
58 this can be consolidated so that style settings occur only in one place, but
59 for now the contents of this file consists first of the initial CSS work as
60 provided to the RFC Formatter (xml2rfc) work, followed by itemized and
61 commented changes found necssary during the development of the v3
62 formatters.
63
64 */
65
66 /* fonts */
67 @import url('https://fonts.googleapis.com/css?family=Noto+Sans'); /* Sans-serif */
68 @import url('https://fonts.googleapis.com/css?family=Noto+Serif'); /* Serif (print) */
69 @import url('https://fonts.googleapis.com/css?family=Roboto+Mono'); /* Monospace */
70
71 @viewport {
72 zoom: 1.0;
73 width: extend-to-zoom;
74 }
75 @-ms-viewport {
76 width: extend-to-zoom;
77 zoom: 1.0;
78 }
79 /* general and mobile first */
80 html {
81 }
82 body {
83 max-width: 90%;
84 margin: 1.5em auto;
85 color: #222;
86 background-color: #fff;
87 font-size: 14px;
88 font-family: 'Noto Sans', Arial, Helvetica, sans-serif;
89 line-height: 1.6;
90 scroll-behavior: smooth;
91 }
92 .ears {
93 display: none;
94 }
95
96 /* headings */
97 #title, h1, h2, h3, h4, h5, h6 {
98 margin: 1em 0 0.5em;
99 font-weight: bold;
100 line-height: 1.3;
101 }
102 #title {
103 clear: both;
104 border-bottom: 1px solid #ddd;
105 margin: 0 0 0.5em 0;
106 padding: 1em 0 0.5em;
107 }
108 .author {
109 padding-bottom: 4px;
110 }
111 h1 {
112 font-size: 26px;
113 margin: 1em 0;
114 }
115 h2 {
116 font-size: 22px;
117 margin-top: -20px; /* provide offset for in-page anchors */
118 padding-top: 33px;
119 }
120 h3 {
121 font-size: 18px;
122 margin-top: -36px; /* provide offset for in-page anchors */
123 padding-top: 42px;
124 }
125 h4 {
126 font-size: 16px;
127 margin-top: -36px; /* provide offset for in-page anchors */
128 padding-top: 42px;
129 }
130 h5, h6 {
131 font-size: 14px;
132 }
133 #n-copyright-notice {
134 border-bottom: 1px solid #ddd;
135 padding-bottom: 1em;
136 margin-bottom: 1em;
137 }
138 /* general structure */
139 p {
140 padding: 0;
141 margin: 0 0 1em 0;
142 text-align: left;
143 }
144 div, span {
145 position: relative;
146 }
147 div {
148 margin: 0;
149 }
150 .alignRight.art-text {
151 background-color: #f9f9f9;
152 border: 1px solid #eee;
153 border-radius: 3px;
154 padding: 1em 1em 0;
155 margin-bottom: 1.5em;
156 }
157 .alignRight.art-text pre {
158 padding: 0;
159 }
160 .alignRight {
161 margin: 1em 0;
162 }
163 .alignRight > *:first-child {
164 border: none;
165 margin: 0;
166 float: right;
167 clear: both;
168 }
169 .alignRight > *:nth-child(2) {
170 clear: both;
171 display: block;
172 border: none;
173 }
174 svg {
175 display: block;
176 }
177 .alignCenter.art-text {
178 background-color: #f9f9f9;
179 border: 1px solid #eee;
180 border-radius: 3px;
181 padding: 1em 1em 0;
182 margin-bottom: 1.5em;
183 }
184 .alignCenter.art-text pre {
185 padding: 0;
186 }
187 .alignCenter {
188 margin: 1em 0;
189 }
190 .alignCenter > *:first-child {
191 border: none;
192 /* this isn't optimal, but it's an existence proof. PrinceXML doesn't
193 support flexbox yet.
194 */
195 display: table;
196 margin: 0 auto;
197 }
198
199 /* lists */
200 ol, ul {
201 padding: 0;
202 margin: 0 0 1em 2em;
203 }
204 ol ol, ul ul, ol ul, ul ol {
205 margin-left: 1em;
206 }
207 li {
208 margin: 0 0 0.25em 0;
209 }
210 .ulCompact li {
211 margin: 0;
212 }
213 ul.empty, .ulEmpty {
214 list-style-type: none;
215 }
216 ul.empty li, .ulEmpty li {
217 margin-top: 0.5em;
218 }
219 ul.compact, .ulCompact,
220 ol.compact, .olCompact {
221 line-height: 100%;
222 margin: 0 0 0 2em;
223 }
224
225 /* definition lists */
226 dl {
227 }
228 dl > dt {
229 float: left;
230 margin-right: 1em;
231 }
232 /*
233 dl.nohang > dt {
234 float: none;
235 }
236 */
237 dl > dd {
238 margin-bottom: .8em;
239 min-height: 1.3em;
240 }
241 dl.compact > dd, .dlCompact > dd {
242 margin-bottom: 0em;
243 }
244 dl > dd > dl {
245 margin-top: 0.5em;
246 margin-bottom: 0em;
247 }
248
249 /* links */
250 a {
251 text-decoration: none;
252 }
253 a[href] {
254 color: #22e; /* Arlen: WCAG 2019 */
255 }
256 a[href]:hover {
257 background-color: #f2f2f2;
258 }
259 figcaption a[href],
260 a[href].selfRef {
261 color: #222;
262 }
263 /* XXX probably not this:
264 a.selfRef:hover {
265 background-color: transparent;
266 cursor: default;
267 } */
268
269 /* Figures */
270 tt, code, pre, code {
271 background-color: #f9f9f9;
272 font-family: 'Roboto Mono', monospace;
273 }
274 pre {
275 border: 1px solid #eee;
276 margin: 0;
277 padding: 1em;
278 }
279 img {
280 max-width: 100%;
281 }
282 figure {
283 margin: 0;
284 }
285 figure blockquote {
286 margin: 0.8em 0.4em 0.4em;
287 }
288 figcaption {
289 font-style: italic;
290 margin: 0 0 1em 0;
291 }
292 @media screen {
293 pre {
294 overflow-x: auto;
295 max-width: 100%;
296 max-width: calc(100% - 22px);
297 }
298 }
299
300 /* aside, blockquote */
301 aside, blockquote {
302 margin-left: 0;
303 padding: 1.2em 2em;
304 }
305 blockquote {
306 background-color: #f9f9f9;
307 color: #111; /* Arlen: WCAG 2019 */
308 border: 1px solid #ddd;
309 border-radius: 3px;
310 margin: 1em 0;
311 }
312 cite {
313 display: block;
314 text-align: right;
315 font-style: italic;
316 }
317
318 /* tables */
319 table {
320 width: 100%;
321 margin: 0 0 1em;
322 border-collapse: collapse;
323 border: 1px solid #eee;
324 }
325 th, td {
326 text-align: left;
327 vertical-align: top;
328 padding: 0.5em 0.75em;
329 }
330 th {
331 text-align: left;
332 background-color: #e9e9e9;
333 }
334 tr:nth-child(2n+1) > td {
335 background-color: #f5f5f5;
336 }
337 table caption {
338 font-style: italic;
339 margin: 0;
340 padding: 0;
341 text-align: left;
342 }
343 table p {
344 /* XXX to avoid bottom margin on table row signifiers. If paragraphs should
345 be allowed within tables more generally, it would be far better to select on a class. */
346 margin: 0;
347 }
348
349 /* pilcrow */
350 a.pilcrow {
351 color: #666; /* Arlen: AHDJ 2019 */
352 text-decoration: none;
353 visibility: hidden;
354 user-select: none;
355 -ms-user-select: none;
356 -o-user-select:none;
357 -moz-user-select: none;
358 -khtml-user-select: none;
359 -webkit-user-select: none;
360 -webkit-touch-callout: none;
361 }
362 @media screen {
363 aside:hover > a.pilcrow,
364 p:hover > a.pilcrow,
365 blockquote:hover > a.pilcrow,
366 div:hover > a.pilcrow,
367 li:hover > a.pilcrow,
368 pre:hover > a.pilcrow {
369 visibility: visible;
370 }
371 a.pilcrow:hover {
372 background-color: transparent;
373 }
374 }
375
376 /* misc */
377 hr {
378 border: 0;
379 border-top: 1px solid #eee;
380 }
381 .bcp14 {
382 font-variant: small-caps;
383 }
384
385 .role {
386 font-variant: all-small-caps;
387 }
388
389 /* info block */
390 #identifiers {
391 margin: 0;
392 font-size: 0.9em;
393 }
394 #identifiers dt {
395 width: 3em;
396 clear: left;
397 }
398 #identifiers dd {
399 float: left;
400 margin-bottom: 0;
401 }
402 #identifiers .authors .author {
403 display: inline-block;
404 margin-right: 1.5em;
405 }
406 #identifiers .authors .org {
407 font-style: italic;
408 }
409
410 /* The prepared/rendered info at the very bottom of the page */
411 .docInfo {
412 color: #666; /* Arlen: WCAG 2019 */
413 font-size: 0.9em;
414 font-style: italic;
415 margin-top: 2em;
416 }
417 .docInfo .prepared {
418 float: left;
419 }
420 .docInfo .prepared {
421 float: right;
422 }
423
424 /* table of contents */
425 #toc {
426 padding: 0.75em 0 2em 0;
427 margin-bottom: 1em;
428 }
429 nav.toc ul {
430 margin: 0 0.5em 0 0;
431 padding: 0;
432 list-style: none;
433 }
434 nav.toc li {
435 line-height: 1.3em;
436 margin: 0.75em 0;
437 padding-left: 1.2em;
438 text-indent: -1.2em;
439 }
440 /* references */
441 .references dt {
442 text-align: right;
443 font-weight: bold;
444 min-width: 7em;
445 }
446 .references dd {
447 margin-left: 8em;
448 overflow: auto;
449 }
450
451 .refInstance {
452 margin-bottom: 1.25em;
453 }
454
455 .references .ascii {
456 margin-bottom: 0.25em;
457 }
458
459 /* index */
460 .index ul {
461 margin: 0 0 0 1em;
462 padding: 0;
463 list-style: none;
464 }
465 .index ul ul {
466 margin: 0;
467 }
468 .index li {
469 margin: 0;
470 text-indent: -2em;
471 padding-left: 2em;
472 padding-bottom: 5px;
473 }
474 .indexIndex {
475 margin: 0.5em 0 1em;
476 }
477 .index a {
478 font-weight: 700;
479 }
480 /* make the index two-column on all but the smallest screens */
481 @media (min-width: 600px) {
482 .index ul {
483 -moz-column-count: 2;
484 -moz-column-gap: 20px;
485 }
486 .index ul ul {
487 -moz-column-count: 1;
488 -moz-column-gap: 0;
489 }
490 }
491
492 /* authors */
493 address.vcard {
494 font-style: normal;
495 margin: 1em 0;
496 }
497
498 address.vcard .nameRole {
499 font-weight: 700;
500 margin-left: 0;
501 }
502 address.vcard .label {
503 font-family: "Noto Sans",Arial,Helvetica,sans-serif;
504 margin: 0.5em 0;
505 }
506 address.vcard .type {
507 display: none;
508 }
509 .alternative-contact {
510 margin: 1.5em 0 1em;
511 }
512 hr.addr {
513 border-top: 1px dashed;
514 margin: 0;
515 color: #ddd;
516 max-width: calc(100% - 16px);
517 }
518
519 /* temporary notes */
520 .rfcEditorRemove::before {
521 position: absolute;
522 top: 0.2em;
523 right: 0.2em;
524 padding: 0.2em;
525 content: "The RFC Editor will remove this note";
526 color: #9e2a00; /* Arlen: WCAG 2019 */
527 background-color: #ffd; /* Arlen: WCAG 2019 */
528 }
529 .rfcEditorRemove {
530 position: relative;
531 padding-top: 1.8em;
532 background-color: #ffd; /* Arlen: WCAG 2019 */
533 border-radius: 3px;
534 }
535 .cref {
536 background-color: #ffd; /* Arlen: WCAG 2019 */
537 padding: 2px 4px;
538 }
539 .crefSource {
540 font-style: italic;
541 }
542 /* alternative layout for smaller screens */
543 @media screen and (max-width: 1023px) {
544 body {
545 padding-top: 2em;
546 }
547 #title {
548 padding: 1em 0;
549 }
550 h1 {
551 font-size: 24px;
552 }
553 h2 {
554 font-size: 20px;
555 margin-top: -18px; /* provide offset for in-page anchors */
556 padding-top: 38px;
557 }
558 #identifiers dd {
559 max-width: 60%;
560 }
561 #toc {
562 position: fixed;
563 z-index: 2;
564 top: 0;
565 right: 0;
566 padding: 0;
567 margin: 0;
568 background-color: inherit;
569 border-bottom: 1px solid #ccc;
570 }
571 #toc h2 {
572 margin: -1px 0 0 0;
573 padding: 4px 0 4px 6px;
574 padding-right: 1em;
575 min-width: 190px;
576 font-size: 1.1em;
577 text-align: right;
578 background-color: #444;
579 color: white;
580 cursor: pointer;
581 }
582 #toc h2::before { /* css hamburger */
583 float: right;
584 position: relative;
585 width: 1em;
586 height: 1px;
587 left: -164px;
588 margin: 6px 0 0 0;
589 background: white none repeat scroll 0 0;
590 box-shadow: 0 4px 0 0 white, 0 8px 0 0 white;
591 content: "";
592 }
593 #toc nav {
594 display: none;
595 padding: 0.5em 1em 1em;
596 overflow: auto;
597 height: calc(100vh - 48px);
598 border-left: 1px solid #ddd;
599 }
600 }
601
602 /* alternative layout for wide screens */
603 @media screen and (min-width: 1024px) {
604 body {
605 max-width: 724px;
606 margin: 42px auto;
607 padding-left: 1.5em;
608 padding-right: 29em;
609 }
610 #toc {
611 position: fixed;
612 top: 42px;
613 right: 42px;
614 width: 25%;
615 margin: 0;
616 padding: 0 1em;
617 z-index: 1;
618 }
619 #toc h2 {
620 border-top: none;
621 border-bottom: 1px solid #ddd;
622 font-size: 1em;
623 font-weight: normal;
624 margin: 0;
625 padding: 0.25em 1em 1em 0;
626 }
627 #toc nav {
628 display: block;
629 height: calc(90vh - 84px);
630 bottom: 0;
631 padding: 0.5em 0 0;
632 overflow: auto;
633 }
634 img { /* future proofing */
635 max-width: 100%;
636 height: auto;
637 }
638 }
639
640 /* pagination */
641 @media print {
642 body {
643
644 width: 100%;
645 }
646 p {
647 orphans: 3;
648 widows: 3;
649 }
650 #n-copyright-notice {
651 border-bottom: none;
652 }
653 #toc, #n-introduction {
654 page-break-before: always;
655 }
656 #toc {
657 border-top: none;
658 padding-top: 0;
659 }
660 figure, pre {
661 page-break-inside: avoid;
662 }
663 figure {
664 overflow: scroll;
665 }
666 h1, h2, h3, h4, h5, h6 {
667 page-break-after: avoid;
668 }
669 h2+*, h3+*, h4+*, h5+*, h6+* {
670 page-break-before: avoid;
671 }
672 pre {
673 white-space: pre-wrap;
674 word-wrap: break-word;
675 font-size: 10pt;
676 }
677 table {
678 border: 1px solid #ddd;
679 }
680 td {
681 border-top: 1px solid #ddd;
682 }
683 }
684
685 /* This is commented out here, as the string-set: doesn't
686 pass W3C validation currently */
687 /*
688 .ears thead .left {
689 string-set: ears-top-left content();
690 }
691
692 .ears thead .center {
693 string-set: ears-top-center content();
694 }
695
696 .ears thead .right {
697 string-set: ears-top-right content();
698 }
699
700 .ears tfoot .left {
701 string-set: ears-bottom-left content();
702 }
703
704 .ears tfoot .center {
705 string-set: ears-bottom-center content();
706 }
707
708 .ears tfoot .right {
709 string-set: ears-bottom-right content();
710 }
711 */
712
713 @page :first {
714 padding-top: 0;
715 @top-left {
716 content: normal;
717 border: none;
718 }
719 @top-center {
720 content: normal;
721 border: none;
722 }
723 @top-right {
724 content: normal;
725 border: none;
726 }
727 }
728
729 @page {
730 size: A4;
731 margin-bottom: 45mm;
732 padding-top: 20px;
733 /* The follwing is commented out here, but set appropriately by in code, as
734 the content depends on the document */
735 /*
736 @top-left {
737 content: 'Internet-Draft';
738 vertical-align: bottom;
739 border-bottom: solid 1px #ccc;
740 }
741 @top-left {
742 content: string(ears-top-left);
743 vertical-align: bottom;
744 border-bottom: solid 1px #ccc;
745 }
746 @top-center {
747 content: string(ears-top-center);
748 vertical-align: bottom;
749 border-bottom: solid 1px #ccc;
750 }
751 @top-right {
752 content: string(ears-top-right);
753 vertical-align: bottom;
754 border-bottom: solid 1px #ccc;
755 }
756 @bottom-left {
757 content: string(ears-bottom-left);
758 vertical-align: top;
759 border-top: solid 1px #ccc;
760 }
761 @bottom-center {
762 content: string(ears-bottom-center);
763 vertical-align: top;
764 border-top: solid 1px #ccc;
765 }
766 @bottom-right {
767 content: '[Page ' counter(page) ']';
768 vertical-align: top;
769 border-top: solid 1px #ccc;
770 }
771 */
772
773 }
774
775 /* Changes introduced to fix issues found during implementation */
776 /* Make sure links are clickable even if overlapped by following H* */
777 a {
778 z-index: 2;
779 }
780 /* Separate body from document info even without intervening H1 */
781 section {
782 clear: both;
783 }
784
785
786 /* Top align author divs, to avoid names without organization dropping level with org names */
787 .author {
788 vertical-align: top;
789 }
790
791 /* Leave room in document info to show Internet-Draft on one line */
792 #identifiers dt {
793 width: 8em;
794 }
795
796 /* Don't waste quite as much whitespace between label and value in doc info */
797 #identifiers dd {
798 margin-left: 1em;
799 }
800
801 /* Give floating toc a background color (needed when it's a div inside section */
802 #toc {
803 background-color: white;
804 }
805
806 /* Make the collapsed ToC header render white on gray also when it's a link */
807 @media screen and (max-width: 1023px) {
808 #toc h2 a,
809 #toc h2 a:link,
810 #toc h2 a:focus,
811 #toc h2 a:hover,
812 #toc a.toplink,
813 #toc a.toplink:hover {
814 color: white;
815 background-color: #444;
816 text-decoration: none;
817 }
818 }
819
820 /* Give the bottom of the ToC some whitespace */
821 @media screen and (min-width: 1024px) {
822 #toc {
823 padding: 0 0 1em 1em;
824 }
825 }
826
827 /* Style section numbers with more space between number and title */
828 .section-number {
829 padding-right: 0.5em;
830 }
831
832 /* prevent monospace from becoming overly large */
833 tt, code, pre, code {
834 font-size: 95%;
835 }
836
837 /* Fix the height/width aspect for ascii art*/
838 pre.sourcecode,
839 .art-text pre {
840 line-height: 1.12;
841 }
842
843
844 /* Add styling for a link in the ToC that points to the top of the document */
845 a.toplink {
846 float: right;
847 margin-right: 0.5em;
848 }
849
850 /* Fix the dl styling to match the RFC 7992 attributes */
851 dl > dt,
852 dl.dlParallel > dt {
853 float: left;
854 margin-right: 1em;
855 }
856 dl.dlNewline > dt {
857 float: none;
858 }
859
860 /* Provide styling for table cell text alignment */
861 table td.text-left,
862 table th.text-left {
863 text-align: left;
864 }
865 table td.text-center,
866 table th.text-center {
867 text-align: center;
868 }
869 table td.text-right,
870 table th.text-right {
871 text-align: right;
872 }
873
874 /* Make the alternative author contact informatio look less like just another
875 author, and group it closer with the primary author contact information */
876 .alternative-contact {
877 margin: 0.5em 0 0.25em 0;
878 }
879 address .non-ascii {
880 margin: 0 0 0 2em;
881 }
882
883 /* With it being possible to set tables with alignment
884 left, center, and right, { width: 100%; } does not make sense */
885 table {
886 width: auto;
887 }
888
889 /* Avoid reference text that sits in a block with very wide left margin,
890 because of a long floating dt label.*/
891 .references dd {
892 overflow: visible;
893 }
894
895 /* Control caption placement */
896 caption {
897 caption-side: bottom;
898 }
899
900 /* Limit the width of the author address vcard, so names in right-to-left
901 script don't end up on the other side of the page. */
902
903 address.vcard {
904 max-width: 30em;
905 margin-right: auto;
906 }
907
908 /* For address alignment dependent on LTR or RTL scripts */
909 address div.left {
910 text-align: left;
911 }
912 address div.right {
913 text-align: right;
914 }
915
916 /* Provide table alignment support. We can't use the alignX classes above
917 since they do unwanted things with caption and other styling. */
918 table.right {
919 margin-left: auto;
920 margin-right: 0;
921 }
922 table.center {
923 margin-left: auto;
924 margin-right: auto;
925 }
926 table.left {
927 margin-left: 0;
928 margin-right: auto;
929 }
930
931 /* Give the table caption label the same styling as the figcaption */
932 caption a[href] {
933 color: #222;
934 }
935
936 @media print {
937 .toplink {
938 display: none;
939 }
940
941 /* avoid overwriting the top border line with the ToC header */
942 #toc {
943 padding-top: 1px;
944 }
945
946 /* Avoid page breaks inside dl and author address entries */
947 .vcard {
948 page-break-inside: avoid;
949 }
950
951 }
952 /* Tweak the bcp14 keyword presentation */
953 .bcp14 {
954 font-variant: small-caps;
955 font-weight: bold;
956 font-size: 0.9em;
957 }
958 /* Tweak the invisible space above H* in order not to overlay links in text above */
959 h2 {
960 margin-top: -18px; /* provide offset for in-page anchors */
961 padding-top: 31px;
962 }
963 h3 {
964 margin-top: -18px; /* provide offset for in-page anchors */
965 padding-top: 24px;
966 }
967 h4 {
968 margin-top: -18px; /* provide offset for in-page anchors */
969 padding-top: 24px;
970 }
971 /* Float artwork pilcrow to the right */
972 @media screen {
973 .artwork a.pilcrow {
974 display: block;
975 line-height: 0.7;
976 margin-top: 0.15em;
977 }
978 }
979 /* Make pilcrows on dd visible */
980 @media screen {
981 dd:hover > a.pilcrow {
982 visibility: visible;
983 }
984 }
985 /* Make the placement of figcaption match that of a table's caption
986 by removing the figure's added bottom margin */
987 .alignLeft.art-text,
988 .alignCenter.art-text,
989 .alignRight.art-text {
990 margin-bottom: 0;
991 }
992 .alignLeft,
993 .alignCenter,
994 .alignRight {
995 margin: 1em 0 0 0;
996 }
997 /* In print, the pilcrow won't show on hover, so prevent it from taking up space,
998 possibly even requiring a new line */
999 @media print {
1000 a.pilcrow {
1001 display: none;
1002 }
1003 }
1004 /* Styling for the external metadata */
1005 div#external-metadata {
1006 background-color: #eee;
1007 padding: 0.5em;
1008 margin-bottom: 0.5em;
1009 display: none;
1010 }
1011 div#internal-metadata {
1012 padding: 0.5em; /* to match the external-metadata padding */
1013 }
1014 /* Styling for title RFC Number */
1015 h1#rfcnum {
1016 clear: both;
1017 margin: 0 0 -1em;
1018 padding: 1em 0 0 0;
1019 }
1020 /* Make .olPercent look the same as <ol><li> */
1021 dl.olPercent > dd {
1022 margin-bottom: 0.25em;
1023 min-height: initial;
1024 }
1025 /* Give aside some styling to set it apart */
1026 aside {
1027 border-left: 1px solid #ddd;
1028 margin: 1em 0 1em 2em;
1029 padding: 0.2em 2em;
1030 }
1031 aside > dl,
1032 aside > ol,
1033 aside > ul,
1034 aside > table,
1035 aside > p {
1036 margin-bottom: 0.5em;
1037 }
1038 /* Additional page break settings */
1039 @media print {
1040 figcaption, table caption {
1041 page-break-before: avoid;
1042 }
1043 }
1044 /* Font size adjustments for print */
1045 @media print {
1046 body { font-size: 10pt; line-height: normal; max-width: 96%; }
1047 h1 { font-size: 1.72em; padding-top: 1.5em; } /* 1*1.2*1.2*1.2 */
1048 h2 { font-size: 1.44em; padding-top: 1.5em; } /* 1*1.2*1.2 */
1049 h3 { font-size: 1.2em; padding-top: 1.5em; } /* 1*1.2 */
1050 h4 { font-size: 1em; padding-top: 1.5em; }
1051 h5, h6 { font-size: 1em; margin: initial; padding: 0.5em 0 0.3em; }
1052 }
1053 /* Sourcecode margin in print, when there's no pilcrow */
1054 @media print {
1055 .artwork,
1056 .sourcecode {
1057 margin-bottom: 1em;
1058 }
1059 }
1060 /* Avoid narrow tables forcing too narrow table captions, which may render badly */
1061 table {
1062 min-width: 20em;
1063 }
1064 /* ol type a */
1065 ol.type-a { list-style-type: lower-alpha; }
1066 ol.type-A { list-style-type: upper-alpha; }
1067 ol.type-i { list-style-type: lower-roman; }
1068 ol.type-I { list-style-type: lower-roman; }
1069 /* Apply the print table and row borders in general, on request from the RPC,
1070 and increase the contrast between border and odd row background sligthtly */
1071 table {
1072 border: 1px solid #ddd;
1073 }
1074 td {
1075 border-top: 1px solid #ddd;
1076 }
1077 tr:nth-child(2n+1) > td {
1078 background-color: #f8f8f8;
1079 }
1080 /* Use style rules to govern display of the TOC. */
1081 @media screen and (max-width: 1023px) {
1082 #toc nav { display: none; }
1083 #toc.active nav { display: block; }
1084 }
1085 /* Add support for keepWithNext */
1086 .keepWithNext {
1087 break-after: avoid-page;
1088 break-after: avoid-page;
1089 }
1090 /* Add support for keepWithPrevious */
1091 .keepWithPrevious {
1092 break-before: avoid-page;
1093 }
1094 /* Change the approach to avoiding breaks inside artwork etc. */
1095 figure, pre, table, .artwork, .sourcecode {
1096 break-before: avoid-page;
1097 break-after: auto;
1098 }
1099 /* Avoid breaks between <dt> and <dd> */
1100 dl {
1101 break-before: auto;
1102 break-inside: auto;
1103 }
1104 dt {
1105 break-before: auto;
1106 break-after: avoid-page;
1107 }
1108 dd {
1109 break-before: avoid-page;
1110 break-after: auto;
1111 orphans: 3;
1112 widows: 3
1113 }
1114 span.break, dd.break {
1115 margin-bottom: 0;
1116 min-height: 0;
1117 break-before: auto;
1118 break-inside: auto;
1119 break-after: auto;
1120 }
1121 /* Undo break-before ToC */
1122 @media print {
1123 #toc {
1124 break-before: auto;
1125 }
1126 }
1127 /* Text in compact lists should not get extra bottim margin space,
1128 since that would makes the list not compact */
1129 ul.compact p, .ulCompact p,
1130 ol.compact p, .olCompact p {
1131 margin: 0;
1132 }
1133 /* But the list as a whole needs the extra space at the end */
1134 section ul.compact,
1135 section .ulCompact,
1136 section ol.compact,
1137 section .olCompact {
1138 margin-bottom: 1em; /* same as p not within ul.compact etc. */
1139 }
1140 /* The tt and code background above interferes with for instance table cell
1141 backgrounds. Changed to something a bit more selective. */
1142 tt, code {
1143 background-color: transparent;
1144 }
1145 p tt, p code, li tt, li code {
1146 background-color: #f8f8f8;
1147 }
1148 /* Tweak the pre margin -- 0px doesn't come out well */
1149 pre {
1150 margin-top: 0.5px;
1151 }
1152 /* Tweak the comact list text */
1153 ul.compact, .ulCompact,
1154 ol.compact, .olCompact,
1155 dl.compact, .dlCompact {
1156 line-height: normal;
1157 }
1158 /* Don't add top margin for nested lists */
1159 li > ul, li > ol, li > dl,
1160 dd > ul, dd > ol, dd > dl,
1161 dl > dd > dl {
1162 margin-top: initial;
1163 }
1164 /* Elements that should not be rendered on the same line as a <dt> */
1165 /* This should match the element list in writer.text.TextWriter.render_dl() */
1166 dd > div.artwork:first-child,
1167 dd > aside:first-child,
1168 dd > figure:first-child,
1169 dd > ol:first-child,
1170 dd > div:first-child > pre.sourcecode,
1171 dd > table:first-child,
1172 dd > ul:first-child {
1173 clear: left;
1174 }
1175 /* fix for weird browser behaviour when <dd/> is empty */
1176 dt+dd:empty::before{
1177 content: "\00a0";
1178 }
1179 </style>
1180 <link href="rfc-local.css" rel="stylesheet" type="text/css">
1181 <link href="https://dx.doi.org/10.17487/rfc8921" rel="alternate">
1182 <link href="urn:issn:2070-1721" rel="alternate">
1183 <link href="https://datatracker.ietf.org/doc/draft-boucadair-connectivity-provisioning-protocol-22" rel="prev">
1184 </head>
1185 <body>
1186 <script src="https://www.rfc-editor.org/js/metadata.min.js"></script>
1187 <table class="ears">
1188 <thead><tr>
1189 <td class="left">RFC 8921</td>
1190 <td class="center">CPNP</td>
1191 <td class="right">October 2020</td>
1192 </tr></thead>
1193 <tfoot><tr>
1194 <td class="left">Boucadair, et al.</td>
1195 <td class="center">Informational</td>
1196 <td class="right">[Page]</td>
1197 </tr></tfoot>
1198 </table>
1199 <div id="external-metadata" class="document-information"></div>
1200 <div id="internal-metadata" class="document-information">
1201 <dl id="identifiers">
1202 <dt class="label-stream">Stream:</dt>
1203 <dd class="stream">Independent Submission</dd>
1204 <dt class="label-rfc">RFC:</dt>
1205 <dd class="rfc"><a href="https://www.rfc-editor.org/rfc/rfc8921" class="eref">8921</a></dd>
1206 <dt class="label-category">Category:</dt>
1207 <dd class="category">Informational</dd>
1208 <dt class="label-published">Published:</dt>
1209 <dd class="published">
1210 <time datetime="2020-10" class="published">October 2020</time>
1211 </dd>
1212 <dt class="label-issn">ISSN:</dt>
1213 <dd class="issn">2070-1721</dd>
1214 <dt class="label-authors">Authors:</dt>
1215 <dd class="authors">
1216 <div class="author">
1217 <div class="author-name">M. Boucadair, <span class="editor">Ed.</span>
1218 </div>
1219 <div class="org">Orange</div>
1220 </div>
1221 <div class="author">
1222 <div class="author-name">C. Jacquenet</div>
1223 <div class="org">Orange</div>
1224 </div>
1225 <div class="author">
1226 <div class="author-name">D. Zhang</div>
1227 <div class="org">Huawei Technologies</div>
1228 </div>
1229 <div class="author">
1230 <div class="author-name">P. Georgatsos</div>
1231 <div class="org">CERTH</div>
1232 </div>
1233 </dd>
1234 </dl>
1235 </div>
1236 <h1 id="rfcnum">RFC 8921</h1>
1237 <h1 id="title">Dynamic Service Negotiation: The Connectivity Provisioning Negotiation Protocol (CPNP)</h1>
1238 <section id="section-abstract">
1239 <h2 id="abstract"><a href="#abstract" class="selfRef">Abstract</a></h2>
1240 <p id="section-abstract-1">This document defines the Connectivity Provisioning Negotiation
1241 Protocol (CPNP), which is designed to facilitate the dynamic negotiation
1242 of service parameters.<a href="#section-abstract-1" class="pilcrow">¶</a></p>
1243 <p id="section-abstract-2">CPNP is a generic protocol that can be used for various negotiation
1244 purposes that include (but are not necessarily limited to) connectivity
1245 provisioning services, storage facilities, Content Delivery Networks,
1246 etc.<a href="#section-abstract-2" class="pilcrow">¶</a></p>
1247 </section>
1248 <div id="status-of-memo">
1249 <section id="section-boilerplate.1">
1250 <h2 id="name-status-of-this-memo">
1251 <a href="#name-status-of-this-memo" class="section-name selfRef">Status of This Memo</a>
1252 </h2>
1253 <p id="section-boilerplate.1-1">
1254 This document is not an Internet Standards Track specification; it is
1255 published for informational purposes.<a href="#section-boilerplate.1-1" class="pilcrow">¶</a></p>
1256 <p id="section-boilerplate.1-2">
1257 This is a contribution to the RFC Series, independently of any
1258 other RFC stream. The RFC Editor has chosen to publish this
1259 document at its discretion and makes no statement about its value
1260 for implementation or deployment. Documents approved for
1261 publication by the RFC Editor are not candidates for any level of
1262 Internet Standard; see Section 2 of RFC 7841.<a href="#section-boilerplate.1-2" class="pilcrow">¶</a></p>
1263 <p id="section-boilerplate.1-3">
1264 Information about the current status of this document, any
1265 errata, and how to provide feedback on it may be obtained at
1266 <span><a href="https://www.rfc-editor.org/info/rfc8921">https://www.rfc-editor.org/info/rfc8921</a></span>.<a href="#section-boilerplate.1-3" class="pilcrow">¶</a></p>
1267 </section>
1268 </div>
1269 <div id="copyright">
1270 <section id="section-boilerplate.2">
1271 <h2 id="name-copyright-notice">
1272 <a href="#name-copyright-notice" class="section-name selfRef">Copyright Notice</a>
1273 </h2>
1274 <p id="section-boilerplate.2-1">
1275 Copyright (c) 2020 IETF Trust and the persons identified as the
1276 document authors. All rights reserved.<a href="#section-boilerplate.2-1" class="pilcrow">¶</a></p>
1277 <p id="section-boilerplate.2-2">
1278 This document is subject to BCP 78 and the IETF Trust's Legal
1279 Provisions Relating to IETF Documents
1280 (<span><a href="https://trustee.ietf.org/license-info">https://trustee.ietf.org/license-info</a></span>) in effect on the date of
1281 publication of this document. Please review these documents
1282 carefully, as they describe your rights and restrictions with
1283 respect to this document.<a href="#section-boilerplate.2-2" class="pilcrow">¶</a></p>
1284 </section>
1285 </div>
1286 <div id="toc">
1287 <section id="section-toc.1">
1288 <a href="#" onclick="scroll(0,0)" class="toplink">▲</a><h2 id="name-table-of-contents">
1289 <a href="#name-table-of-contents" class="section-name selfRef">Table of Contents</a>
1290 </h2>
1291 <nav class="toc"><ul class="ulEmpty compact toc">
1292 <li class="ulEmpty compact toc" id="section-toc.1-1.1">
1293 <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><a href="#section-toc.1-1.1.1" class="pilcrow">¶</a></p>
1294 </li>
1295 <li class="ulEmpty compact toc" id="section-toc.1-1.2">
1296 <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><a href="#section-toc.1-1.2.1" class="pilcrow">¶</a></p>
1297 </li>
1298 <li class="ulEmpty compact toc" id="section-toc.1-1.3">
1299 <p id="section-toc.1-1.3.1" class="keepWithNext"><a href="#section-3" class="xref">3</a>.  <a href="#name-cpnp-functional-elements" class="xref">CPNP Functional Elements</a><a href="#section-toc.1-1.3.1" class="pilcrow">¶</a></p>
1300 </li>
1301 <li class="ulEmpty compact toc" id="section-toc.1-1.4">
1302 <p id="section-toc.1-1.4.1"><a href="#section-4" class="xref">4</a>.  <a href="#name-order-processing-models" class="xref">Order Processing Models</a><a href="#section-toc.1-1.4.1" class="pilcrow">¶</a></p>
1303 </li>
1304 <li class="ulEmpty compact toc" id="section-toc.1-1.5">
1305 <p id="section-toc.1-1.5.1"><a href="#section-5" class="xref">5</a>.  <a href="#name-sample-use-cases" class="xref">Sample Use Cases</a><a href="#section-toc.1-1.5.1" class="pilcrow">¶</a></p>
1306 </li>
1307 <li class="ulEmpty compact toc" id="section-toc.1-1.6">
1308 <p id="section-toc.1-1.6.1"><a href="#section-6" class="xref">6</a>.  <a href="#name-cpnp-deployment-models" class="xref">CPNP Deployment Models</a><a href="#section-toc.1-1.6.1" class="pilcrow">¶</a></p>
1309 </li>
1310 <li class="ulEmpty compact toc" id="section-toc.1-1.7">
1311 <p id="section-toc.1-1.7.1"><a href="#section-7" class="xref">7</a>.  <a href="#name-cpnp-negotiation-model" class="xref">CPNP Negotiation Model</a><a href="#section-toc.1-1.7.1" class="pilcrow">¶</a></p>
1312 </li>
1313 <li class="ulEmpty compact toc" id="section-toc.1-1.8">
1314 <p id="section-toc.1-1.8.1"><a href="#section-8" class="xref">8</a>.  <a href="#name-protocol-overview" class="xref">Protocol Overview</a><a href="#section-toc.1-1.8.1" class="pilcrow">¶</a></p>
1315 <ul class="ulEmpty compact toc">
1316 <li class="ulEmpty compact toc" id="section-toc.1-1.8.2.1">
1317 <p id="section-toc.1-1.8.2.1.1"><a href="#section-8.1" class="xref">8.1</a>.  <a href="#name-client-server-communication" class="xref">Client/Server Communication</a><a href="#section-toc.1-1.8.2.1.1" class="pilcrow">¶</a></p>
1318 </li>
1319 <li class="ulEmpty compact toc" id="section-toc.1-1.8.2.2">
1320 <p id="section-toc.1-1.8.2.2.1"><a href="#section-8.2" class="xref">8.2</a>.  <a href="#name-policy-configuration-on-the" class="xref">Policy Configuration on the CPNP Server</a><a href="#section-toc.1-1.8.2.2.1" class="pilcrow">¶</a></p>
1321 </li>
1322 <li class="ulEmpty compact toc" id="section-toc.1-1.8.2.3">
1323 <p id="section-toc.1-1.8.2.3.1"><a href="#section-8.3" class="xref">8.3</a>.  <a href="#name-cpnp-session-entries" class="xref">CPNP Session Entries</a><a href="#section-toc.1-1.8.2.3.1" class="pilcrow">¶</a></p>
1324 </li>
1325 <li class="ulEmpty compact toc" id="section-toc.1-1.8.2.4">
1326 <p id="section-toc.1-1.8.2.4.1"><a href="#section-8.4" class="xref">8.4</a>.  <a href="#name-cpnp-transactions" class="xref">CPNP Transactions</a><a href="#section-toc.1-1.8.2.4.1" class="pilcrow">¶</a></p>
1327 </li>
1328 <li class="ulEmpty compact toc" id="section-toc.1-1.8.2.5">
1329 <p id="section-toc.1-1.8.2.5.1"><a href="#section-8.5" class="xref">8.5</a>.  <a href="#name-cpnp-timers" class="xref">CPNP Timers</a><a href="#section-toc.1-1.8.2.5.1" class="pilcrow">¶</a></p>
1330 </li>
1331 <li class="ulEmpty compact toc" id="section-toc.1-1.8.2.6">
1332 <p id="section-toc.1-1.8.2.6.1"><a href="#section-8.6" class="xref">8.6</a>.  <a href="#name-cpnp-operations" class="xref">CPNP Operations</a><a href="#section-toc.1-1.8.2.6.1" class="pilcrow">¶</a></p>
1333 </li>
1334 <li class="ulEmpty compact toc" id="section-toc.1-1.8.2.7">
1335 <p id="section-toc.1-1.8.2.7.1"><a href="#section-8.7" class="xref">8.7</a>.  <a href="#name-connectivity-provisioning-d" class="xref">Connectivity Provisioning Documents</a><a href="#section-toc.1-1.8.2.7.1" class="pilcrow">¶</a></p>
1336 </li>
1337 <li class="ulEmpty compact toc" id="section-toc.1-1.8.2.8">
1338 <p id="section-toc.1-1.8.2.8.1"><a href="#section-8.8" class="xref">8.8</a>.  <a href="#name-child-pqos" class="xref">Child PQOs</a><a href="#section-toc.1-1.8.2.8.1" class="pilcrow">¶</a></p>
1339 </li>
1340 <li class="ulEmpty compact toc" id="section-toc.1-1.8.2.9">
1341 <p id="section-toc.1-1.8.2.9.1"><a href="#section-8.9" class="xref">8.9</a>.  <a href="#name-multi-segment-service" class="xref">Multi-Segment Service</a><a href="#section-toc.1-1.8.2.9.1" class="pilcrow">¶</a></p>
1342 </li>
1343 <li class="ulEmpty compact toc" id="section-toc.1-1.8.2.10">
1344 <p id="section-toc.1-1.8.2.10.1"><a href="#section-8.10" class="xref">8.10</a>. <a href="#name-negotiating-with-multiple-c" class="xref">Negotiating with Multiple CPNP Servers</a><a href="#section-toc.1-1.8.2.10.1" class="pilcrow">¶</a></p>
1345 </li>
1346 <li class="ulEmpty compact toc" id="section-toc.1-1.8.2.11">
1347 <p id="section-toc.1-1.8.2.11.1"><a href="#section-8.11" class="xref">8.11</a>. <a href="#name-state-management" class="xref">State Management</a><a href="#section-toc.1-1.8.2.11.1" class="pilcrow">¶</a></p>
1348 <ul class="ulEmpty compact toc">
1349 <li class="ulEmpty compact toc" id="section-toc.1-1.8.2.11.2.1">
1350 <p id="section-toc.1-1.8.2.11.2.1.1"><a href="#section-8.11.1" class="xref">8.11.1</a>.  <a href="#name-on-the-client-side" class="xref">On the Client Side</a><a href="#section-toc.1-1.8.2.11.2.1.1" class="pilcrow">¶</a></p>
1351 </li>
1352 <li class="ulEmpty compact toc" id="section-toc.1-1.8.2.11.2.2">
1353 <p id="section-toc.1-1.8.2.11.2.2.1"><a href="#section-8.11.2" class="xref">8.11.2</a>.  <a href="#name-on-the-server-side" class="xref">On the Server Side</a><a href="#section-toc.1-1.8.2.11.2.2.1" class="pilcrow">¶</a></p>
1354 </li>
1355 </ul>
1356 </li>
1357 </ul>
1358 </li>
1359 <li class="ulEmpty compact toc" id="section-toc.1-1.9">
1360 <p id="section-toc.1-1.9.1"><a href="#section-9" class="xref">9</a>.  <a href="#name-cpnp-objects" class="xref">CPNP Objects</a><a href="#section-toc.1-1.9.1" class="pilcrow">¶</a></p>
1361 <ul class="ulEmpty compact toc">
1362 <li class="ulEmpty compact toc" id="section-toc.1-1.9.2.1">
1363 <p id="section-toc.1-1.9.2.1.1"><a href="#section-9.1" class="xref">9.1</a>.  <a href="#name-attributes" class="xref">Attributes</a><a href="#section-toc.1-1.9.2.1.1" class="pilcrow">¶</a></p>
1364 <ul class="ulEmpty compact toc">
1365 <li class="ulEmpty compact toc" id="section-toc.1-1.9.2.1.2.1">
1366 <p id="section-toc.1-1.9.2.1.2.1.1"><a href="#section-9.1.1" class="xref">9.1.1</a>.  <a href="#name-customer_order_identifier" class="xref">CUSTOMER_ORDER_IDENTIFIER</a><a href="#section-toc.1-1.9.2.1.2.1.1" class="pilcrow">¶</a></p>
1367 </li>
1368 <li class="ulEmpty compact toc" id="section-toc.1-1.9.2.1.2.2">
1369 <p id="section-toc.1-1.9.2.1.2.2.1"><a href="#section-9.1.2" class="xref">9.1.2</a>.  <a href="#name-provider_order_identifier" class="xref">PROVIDER_ORDER_IDENTIFIER</a><a href="#section-toc.1-1.9.2.1.2.2.1" class="pilcrow">¶</a></p>
1370 </li>
1371 <li class="ulEmpty compact toc" id="section-toc.1-1.9.2.1.2.3">
1372 <p id="section-toc.1-1.9.2.1.2.3.1"><a href="#section-9.1.3" class="xref">9.1.3</a>.  <a href="#name-transaction_id" class="xref">TRANSACTION_ID</a><a href="#section-toc.1-1.9.2.1.2.3.1" class="pilcrow">¶</a></p>
1373 </li>
1374 <li class="ulEmpty compact toc" id="section-toc.1-1.9.2.1.2.4">
1375 <p id="section-toc.1-1.9.2.1.2.4.1"><a href="#section-9.1.4" class="xref">9.1.4</a>.  <a href="#name-sequence_number" class="xref">SEQUENCE_NUMBER</a><a href="#section-toc.1-1.9.2.1.2.4.1" class="pilcrow">¶</a></p>
1376 </li>
1377 <li class="ulEmpty compact toc" id="section-toc.1-1.9.2.1.2.5">
1378 <p id="section-toc.1-1.9.2.1.2.5.1"><a href="#section-9.1.5" class="xref">9.1.5</a>.  <a href="#name-nonce" class="xref">NONCE</a><a href="#section-toc.1-1.9.2.1.2.5.1" class="pilcrow">¶</a></p>
1379 </li>
1380 <li class="ulEmpty compact toc" id="section-toc.1-1.9.2.1.2.6">
1381 <p id="section-toc.1-1.9.2.1.2.6.1"><a href="#section-9.1.6" class="xref">9.1.6</a>.  <a href="#name-expected_response_time" class="xref">EXPECTED_RESPONSE_TIME</a><a href="#section-toc.1-1.9.2.1.2.6.1" class="pilcrow">¶</a></p>
1382 </li>
1383 <li class="ulEmpty compact toc" id="section-toc.1-1.9.2.1.2.7">
1384 <p id="section-toc.1-1.9.2.1.2.7.1"><a href="#section-9.1.7" class="xref">9.1.7</a>.  <a href="#name-expected_offer_time" class="xref">EXPECTED_OFFER_TIME</a><a href="#section-toc.1-1.9.2.1.2.7.1" class="pilcrow">¶</a></p>
1385 </li>
1386 <li class="ulEmpty compact toc" id="section-toc.1-1.9.2.1.2.8">
1387 <p id="section-toc.1-1.9.2.1.2.8.1"><a href="#section-9.1.8" class="xref">9.1.8</a>.  <a href="#name-validity_offer_time" class="xref">VALIDITY_OFFER_TIME</a><a href="#section-toc.1-1.9.2.1.2.8.1" class="pilcrow">¶</a></p>
1388 </li>
1389 <li class="ulEmpty compact toc" id="section-toc.1-1.9.2.1.2.9">
1390 <p id="section-toc.1-1.9.2.1.2.9.1"><a href="#section-9.1.9" class="xref">9.1.9</a>.  <a href="#name-service_description" class="xref">SERVICE_DESCRIPTION</a><a href="#section-toc.1-1.9.2.1.2.9.1" class="pilcrow">¶</a></p>
1391 </li>
1392 <li class="ulEmpty compact toc" id="section-toc.1-1.9.2.1.2.10">
1393 <p id="section-toc.1-1.9.2.1.2.10.1"><a href="#section-9.1.10" class="xref">9.1.10</a>. <a href="#name-cpnp-information-elements" class="xref">CPNP Information Elements</a><a href="#section-toc.1-1.9.2.1.2.10.1" class="pilcrow">¶</a></p>
1394 </li>
1395 </ul>
1396 </li>
1397 <li class="ulEmpty compact toc" id="section-toc.1-1.9.2.2">
1398 <p id="section-toc.1-1.9.2.2.1"><a href="#section-9.2" class="xref">9.2</a>.  <a href="#name-operation-messages" class="xref">Operation Messages</a><a href="#section-toc.1-1.9.2.2.1" class="pilcrow">¶</a></p>
1399 <ul class="ulEmpty compact toc">
1400 <li class="ulEmpty compact toc" id="section-toc.1-1.9.2.2.2.1">
1401 <p id="section-toc.1-1.9.2.2.2.1.1"><a href="#section-9.2.1" class="xref">9.2.1</a>.  <a href="#name-quotation" class="xref">QUOTATION</a><a href="#section-toc.1-1.9.2.2.2.1.1" class="pilcrow">¶</a></p>
1402 </li>
1403 <li class="ulEmpty compact toc" id="section-toc.1-1.9.2.2.2.2">
1404 <p id="section-toc.1-1.9.2.2.2.2.1"><a href="#section-9.2.2" class="xref">9.2.2</a>.  <a href="#name-processing" class="xref">PROCESSING</a><a href="#section-toc.1-1.9.2.2.2.2.1" class="pilcrow">¶</a></p>
1405 </li>
1406 <li class="ulEmpty compact toc" id="section-toc.1-1.9.2.2.2.3">
1407 <p id="section-toc.1-1.9.2.2.2.3.1"><a href="#section-9.2.3" class="xref">9.2.3</a>.  <a href="#name-offer" class="xref">OFFER</a><a href="#section-toc.1-1.9.2.2.2.3.1" class="pilcrow">¶</a></p>
1408 </li>
1409 <li class="ulEmpty compact toc" id="section-toc.1-1.9.2.2.2.4">
1410 <p id="section-toc.1-1.9.2.2.2.4.1"><a href="#section-9.2.4" class="xref">9.2.4</a>.  <a href="#name-accept" class="xref">ACCEPT</a><a href="#section-toc.1-1.9.2.2.2.4.1" class="pilcrow">¶</a></p>
1411 </li>
1412 <li class="ulEmpty compact toc" id="section-toc.1-1.9.2.2.2.5">
1413 <p id="section-toc.1-1.9.2.2.2.5.1"><a href="#section-9.2.5" class="xref">9.2.5</a>.  <a href="#name-decline" class="xref">DECLINE</a><a href="#section-toc.1-1.9.2.2.2.5.1" class="pilcrow">¶</a></p>
1414 </li>
1415 <li class="ulEmpty compact toc" id="section-toc.1-1.9.2.2.2.6">
1416 <p id="section-toc.1-1.9.2.2.2.6.1"><a href="#section-9.2.6" class="xref">9.2.6</a>.  <a href="#name-ack" class="xref">ACK</a><a href="#section-toc.1-1.9.2.2.2.6.1" class="pilcrow">¶</a></p>
1417 </li>
1418 <li class="ulEmpty compact toc" id="section-toc.1-1.9.2.2.2.7">
1419 <p id="section-toc.1-1.9.2.2.2.7.1"><a href="#section-9.2.7" class="xref">9.2.7</a>.  <a href="#name-cancel" class="xref">CANCEL</a><a href="#section-toc.1-1.9.2.2.2.7.1" class="pilcrow">¶</a></p>
1420 </li>
1421 <li class="ulEmpty compact toc" id="section-toc.1-1.9.2.2.2.8">
1422 <p id="section-toc.1-1.9.2.2.2.8.1"><a href="#section-9.2.8" class="xref">9.2.8</a>.  <a href="#name-withdraw" class="xref">WITHDRAW</a><a href="#section-toc.1-1.9.2.2.2.8.1" class="pilcrow">¶</a></p>
1423 </li>
1424 <li class="ulEmpty compact toc" id="section-toc.1-1.9.2.2.2.9">
1425 <p id="section-toc.1-1.9.2.2.2.9.1"><a href="#section-9.2.9" class="xref">9.2.9</a>.  <a href="#name-update" class="xref">UPDATE</a><a href="#section-toc.1-1.9.2.2.2.9.1" class="pilcrow">¶</a></p>
1426 </li>
1427 <li class="ulEmpty compact toc" id="section-toc.1-1.9.2.2.2.10">
1428 <p id="section-toc.1-1.9.2.2.2.10.1"><a href="#section-9.2.10" class="xref">9.2.10</a>. <a href="#name-fail" class="xref">FAIL</a><a href="#section-toc.1-1.9.2.2.2.10.1" class="pilcrow">¶</a></p>
1429 </li>
1430 <li class="ulEmpty compact toc" id="section-toc.1-1.9.2.2.2.11">
1431 <p id="section-toc.1-1.9.2.2.2.11.1"><a href="#section-9.2.11" class="xref">9.2.11</a>. <a href="#name-activate" class="xref">ACTIVATE</a><a href="#section-toc.1-1.9.2.2.2.11.1" class="pilcrow">¶</a></p>
1432 </li>
1433 </ul>
1434 </li>
1435 </ul>
1436 </li>
1437 <li class="ulEmpty compact toc" id="section-toc.1-1.10">
1438 <p id="section-toc.1-1.10.1"><a href="#section-10" class="xref">10</a>. <a href="#name-cpnp-message-validation" class="xref">CPNP Message Validation</a><a href="#section-toc.1-1.10.1" class="pilcrow">¶</a></p>
1439 <ul class="ulEmpty compact toc">
1440 <li class="ulEmpty compact toc" id="section-toc.1-1.10.2.1">
1441 <p id="section-toc.1-1.10.2.1.1"><a href="#section-10.1" class="xref">10.1</a>.  <a href="#name-on-the-client-side-2" class="xref">On the Client Side</a><a href="#section-toc.1-1.10.2.1.1" class="pilcrow">¶</a></p>
1442 </li>
1443 <li class="ulEmpty compact toc" id="section-toc.1-1.10.2.2">
1444 <p id="section-toc.1-1.10.2.2.1"><a href="#section-10.2" class="xref">10.2</a>.  <a href="#name-on-the-server-side-2" class="xref">On the Server Side</a><a href="#section-toc.1-1.10.2.2.1" class="pilcrow">¶</a></p>
1445 </li>
1446 </ul>
1447 </li>
1448 <li class="ulEmpty compact toc" id="section-toc.1-1.11">
1449 <p id="section-toc.1-1.11.1"><a href="#section-11" class="xref">11</a>. <a href="#name-theory-of-operation" class="xref">Theory of Operation</a><a href="#section-toc.1-1.11.1" class="pilcrow">¶</a></p>
1450 <ul class="ulEmpty compact toc">
1451 <li class="ulEmpty compact toc" id="section-toc.1-1.11.2.1">
1452 <p id="section-toc.1-1.11.2.1.1"><a href="#section-11.1" class="xref">11.1</a>.  <a href="#name-client-behavior" class="xref">Client Behavior</a><a href="#section-toc.1-1.11.2.1.1" class="pilcrow">¶</a></p>
1453 <ul class="ulEmpty compact toc">
1454 <li class="ulEmpty compact toc" id="section-toc.1-1.11.2.1.2.1">
1455 <p id="section-toc.1-1.11.2.1.2.1.1"><a href="#section-11.1.1" class="xref">11.1.1</a>.  <a href="#name-order-negotiation-cycle" class="xref">Order Negotiation Cycle</a><a href="#section-toc.1-1.11.2.1.2.1.1" class="pilcrow">¶</a></p>
1456 </li>
1457 <li class="ulEmpty compact toc" id="section-toc.1-1.11.2.1.2.2">
1458 <p id="section-toc.1-1.11.2.1.2.2.1"><a href="#section-11.1.2" class="xref">11.1.2</a>.  <a href="#name-order-withdrawal-cycle" class="xref">Order Withdrawal Cycle</a><a href="#section-toc.1-1.11.2.1.2.2.1" class="pilcrow">¶</a></p>
1459 </li>
1460 <li class="ulEmpty compact toc" id="section-toc.1-1.11.2.1.2.3">
1461 <p id="section-toc.1-1.11.2.1.2.3.1"><a href="#section-11.1.3" class="xref">11.1.3</a>.  <a href="#name-order-update-cycle" class="xref">Order Update Cycle</a><a href="#section-toc.1-1.11.2.1.2.3.1" class="pilcrow">¶</a></p>
1462 </li>
1463 </ul>
1464 </li>
1465 <li class="ulEmpty compact toc" id="section-toc.1-1.11.2.2">
1466 <p id="section-toc.1-1.11.2.2.1"><a href="#section-11.2" class="xref">11.2</a>.  <a href="#name-server-behavior" class="xref">Server Behavior</a><a href="#section-toc.1-1.11.2.2.1" class="pilcrow">¶</a></p>
1467 <ul class="ulEmpty compact toc">
1468 <li class="ulEmpty compact toc" id="section-toc.1-1.11.2.2.2.1">
1469 <p id="section-toc.1-1.11.2.2.2.1.1"><a href="#section-11.2.1" class="xref">11.2.1</a>.  <a href="#name-order-processing" class="xref">Order Processing</a><a href="#section-toc.1-1.11.2.2.2.1.1" class="pilcrow">¶</a></p>
1470 </li>
1471 <li class="ulEmpty compact toc" id="section-toc.1-1.11.2.2.2.2">
1472 <p id="section-toc.1-1.11.2.2.2.2.1"><a href="#section-11.2.2" class="xref">11.2.2</a>.  <a href="#name-order-withdrawal" class="xref">Order Withdrawal</a><a href="#section-toc.1-1.11.2.2.2.2.1" class="pilcrow">¶</a></p>
1473 </li>
1474 <li class="ulEmpty compact toc" id="section-toc.1-1.11.2.2.2.3">
1475 <p id="section-toc.1-1.11.2.2.2.3.1"><a href="#section-11.2.3" class="xref">11.2.3</a>.  <a href="#name-order-update" class="xref">Order Update</a><a href="#section-toc.1-1.11.2.2.2.3.1" class="pilcrow">¶</a></p>
1476 </li>
1477 </ul>
1478 </li>
1479 <li class="ulEmpty compact toc" id="section-toc.1-1.11.2.3">
1480 <p id="section-toc.1-1.11.2.3.1"><a href="#section-11.3" class="xref">11.3</a>.  <a href="#name-sequence-numbers" class="xref">Sequence Numbers</a><a href="#section-toc.1-1.11.2.3.1" class="pilcrow">¶</a></p>
1481 </li>
1482 <li class="ulEmpty compact toc" id="section-toc.1-1.11.2.4">
1483 <p id="section-toc.1-1.11.2.4.1"><a href="#section-11.4" class="xref">11.4</a>.  <a href="#name-message-retransmission" class="xref">Message Retransmission</a><a href="#section-toc.1-1.11.2.4.1" class="pilcrow">¶</a></p>
1484 </li>
1485 </ul>
1486 </li>
1487 <li class="ulEmpty compact toc" id="section-toc.1-1.12">
1488 <p id="section-toc.1-1.12.1"><a href="#section-12" class="xref">12</a>. <a href="#name-some-operational-guidelines" class="xref">Some Operational Guidelines</a><a href="#section-toc.1-1.12.1" class="pilcrow">¶</a></p>
1489 <ul class="ulEmpty compact toc">
1490 <li class="ulEmpty compact toc" id="section-toc.1-1.12.2.1">
1491 <p id="section-toc.1-1.12.2.1.1"><a href="#section-12.1" class="xref">12.1</a>.  <a href="#name-cpnp-server-logging" class="xref">CPNP Server Logging</a><a href="#section-toc.1-1.12.2.1.1" class="pilcrow">¶</a></p>
1492 </li>
1493 <li class="ulEmpty compact toc" id="section-toc.1-1.12.2.2">
1494 <p id="section-toc.1-1.12.2.2.1"><a href="#section-12.2" class="xref">12.2</a>.  <a href="#name-business-guidelines-and-obj" class="xref">Business Guidelines and Objectives</a><a href="#section-toc.1-1.12.2.2.1" class="pilcrow">¶</a></p>
1495 </li>
1496 </ul>
1497 </li>
1498 <li class="ulEmpty compact toc" id="section-toc.1-1.13">
1499 <p id="section-toc.1-1.13.1"><a href="#section-13" class="xref">13</a>. <a href="#name-security-considerations" class="xref">Security Considerations</a><a href="#section-toc.1-1.13.1" class="pilcrow">¶</a></p>
1500 </li>
1501 <li class="ulEmpty compact toc" id="section-toc.1-1.14">
1502 <p id="section-toc.1-1.14.1"><a href="#section-14" class="xref">14</a>. <a href="#name-iana-considerations" class="xref">IANA Considerations</a><a href="#section-toc.1-1.14.1" class="pilcrow">¶</a></p>
1503 </li>
1504 <li class="ulEmpty compact toc" id="section-toc.1-1.15">
1505 <p id="section-toc.1-1.15.1"><a href="#section-15" class="xref">15</a>. <a href="#name-references" class="xref">References</a><a href="#section-toc.1-1.15.1" class="pilcrow">¶</a></p>
1506 <ul class="ulEmpty compact toc">
1507 <li class="ulEmpty compact toc" id="section-toc.1-1.15.2.1">
1508 <p id="section-toc.1-1.15.2.1.1"><a href="#section-15.1" class="xref">15.1</a>.  <a href="#name-normative-references" class="xref">Normative References</a><a href="#section-toc.1-1.15.2.1.1" class="pilcrow">¶</a></p>
1509 </li>
1510 <li class="ulEmpty compact toc" id="section-toc.1-1.15.2.2">
1511 <p id="section-toc.1-1.15.2.2.1"><a href="#section-15.2" class="xref">15.2</a>.  <a href="#name-informative-references" class="xref">Informative References</a><a href="#section-toc.1-1.15.2.2.1" class="pilcrow">¶</a></p>
1512 </li>
1513 </ul>
1514 </li>
1515 <li class="ulEmpty compact toc" id="section-toc.1-1.16">
1516 <p id="section-toc.1-1.16.1"><a href="#section-appendix.a" class="xref"></a><a href="#name-acknowledgements" class="xref">Acknowledgements</a><a href="#section-toc.1-1.16.1" class="pilcrow">¶</a></p>
1517 </li>
1518 <li class="ulEmpty compact toc" id="section-toc.1-1.17">
1519 <p id="section-toc.1-1.17.1"><a href="#section-appendix.b" class="xref"></a><a href="#name-authors-addresses" class="xref">Authors' Addresses</a><a href="#section-toc.1-1.17.1" class="pilcrow">¶</a></p>
1520 </li>
1521 </ul>
1522 </nav>
1523 </section>
1524 </div>
1525 <section id="section-1">
1526 <h2 id="name-introduction">
1527 <a href="#section-1" class="section-number selfRef">1. </a><a href="#name-introduction" class="section-name selfRef">Introduction</a>
1528 </h2>
1529 <p id="section-1-1">This document defines the Connectivity Provisioning Negotiation
1530 Protocol (CPNP) that is meant to dynamically exchange and negotiate
1531 connectivity provisioning parameters and other service-specific
1532 parameters between a Customer and a Provider. CPNP is a tool that
1533 introduces automation to the service negotiation and activation
1534 procedures, thus fostering the overall service provisioning process.
1535 CPNP can be seen as a component of the dynamic negotiation metadomain
1536 described in <span><a href="https://www.rfc-editor.org/rfc/rfc7149#section-2.4" class="relref">Section 2.4</a> of [<a href="#RFC7149" class="xref">RFC7149</a>]</span>.<a href="#section-1-1" class="pilcrow">¶</a></p>
1537 <p id="section-1-2">CPNP is a generic protocol that can be used for negotiation
1538 purposes other than connectivity provisioning. For example, CPNP can be used
1539 to request extra storage resources, to extend the footprint of a
1540 Content Delivery Network (CDN), to enable additional features from a cloud
1541 Provider, etc. CPNP can be extended with new Information Elements (IEs).
1542 Sample negotiation use cases are described in
1543 <a href="#suc" class="xref">Section 5</a>. <a href="#opm" class="xref">Section 4</a> introduces several
1544 order processing models and defines those that are targeted by CPNP.
1545 The CPNP negotiation model is then detailed in <a href="#cnm" class="xref">Section 7</a>.<a href="#section-1-2" class="pilcrow">¶</a></p>
1546 <p id="section-1-3"><span>[<a href="#RFC7297" class="xref">RFC7297</a>]</span> describes a Connectivity Provisioning
1547 Profile (CPP) template to capture connectivity requirements to be met by
1548 a transport infrastructure for the delivery of various services such as
1549 Voice over IP (VoIP), IPTV, and Virtual Private Network (VPN) services
1550 <span>[<a href="#RFC4026" class="xref">RFC4026</a>]</span>. The CPP document defines the set of IP
1551 transfer parameters that reflect the guarantees that can be provided by
1552 the underlying transport network together with reachability scope and
1553 capacity needs. CPNP uses the CPP template to encode connectivity
1554 provisioning clauses that are subject to negotiation. The accepted CPP
1555 will then be passed to other functional elements that are responsible
1556 for the actual service activation and provisioning. For example,
1557 Network Configuration Protocol (NETCONF)
1558 <span>[<a href="#RFC6241" class="xref">RFC6241</a>]</span> or RESTCONF
1559 <span>[<a href="#RFC8040" class="xref">RFC8040</a>]</span> can be used to activate adequate network
1560 features that are required to deliver the accepted service. How the
1561 outcome of CPNP negotiation is translated into service and network
1562 provisioning actions is out of scope of this document.<a href="#section-1-3" class="pilcrow">¶</a></p>
1563 <p id="section-1-4">As a reminder, several proposals have been made in the past by the
1564 (research) community (e.g., Common Open Policy Service protocol for
1565 supporting Service Level Specification <span>[<a href="#I-D.nguyen-rap-cops-sls" class="xref">COPS-SLS</a>]</span>, Service Negotiation Protocol
1566 <span>[<a href="#SrNP" class="xref">SrNP</a>]</span>, Dynamic Service Negotiation
1567 Protocol <span>[<a href="#I-D.itsumo-dsnp" class="xref">DSNP</a>]</span>, Resource
1568 Negotiation and Pricing Protocol <span>[<a href="#RNAP" class="xref">RNAP</a>]</span>,
1569 Service Negotiation and Acquisition Protocol <span>[<a href="#SNAP" class="xref">SNAP</a>]</span>).
1570 CPNP leverages the authors' experience
1571 with SrNP by separating the negotiation primitives from the service
1572 under negotiation. Moreover, careful examination of the other proposals
1573 revealed certain deficiencies that were easier to address through the
1574 creation of a new protocol rather than the modification of existing protocols. For
1575 example:<a href="#section-1-4" class="pilcrow">¶</a></p>
1576 <ul class="normal">
1577 <li class="normal" id="section-1-5.1">COPS-SLS relies upon the COPS usage for policy provisioning (COPS-PR) <span>[<a href="#RFC3084" class="xref">RFC3084</a>]</span>,
1578 which is a Historic RFC.<a href="#section-1-5.1" class="pilcrow">¶</a>
1579 </li>
1580 <li class="normal" id="section-1-5.2">DSNP is tightly designed with one specific service in mind (QoS)
1581 and does not make any distinction between a quotation phase and the
1582 actual service-ordering phase.<a href="#section-1-5.2" class="pilcrow">¶</a>
1583 </li>
1584 </ul>
1585 <p id="section-1-6">One of the primary motivations of this document is to provide a
1586 permanent reference to exemplify how service negotiation can be
1587 automated.<a href="#section-1-6" class="pilcrow">¶</a></p>
1588 <p id="section-1-7">Implementation details are out of scope. An example of required
1589 modules and interfaces to implement this specification is sketched in
1590 Section 4 of <span>[<a href="#AGAVE" class="xref">AGAVE</a>]</span>. This specification builds on
1591 that effort.<a href="#section-1-7" class="pilcrow">¶</a></p>
1592 </section>
1593 <section id="section-2">
1594 <h2 id="name-terminology">
1595 <a href="#section-2" class="section-number selfRef">2. </a><a href="#name-terminology" class="section-name selfRef">Terminology</a>
1596 </h2>
1597 <p id="section-2-1">This document makes use of the following terms:<a href="#section-2-1" class="pilcrow">¶</a></p>
1598 <span class="break"></span><dl class="dlParallel" id="section-2-2">
1599 <dt id="section-2-2.1">Customer:</dt>
1600 <dd style="margin-left: 1.5em" id="section-2-2.2">
1601 <p id="section-2-2.2.1">Is a business role that denotes an entity
1602 that is involved in the definition and the possible negotiation of
1603 an order, including a Connectivity Provisioning Agreement, with a
1604 Provider. A connectivity provisioning document is captured in a
1605 dedicated CPP template-based document, which may specify (among
1606 other information) the sites to be connected, border nodes,
1607 outsourced operations (e.g., routing, traffic steering).<a href="#section-2-2.2.1" class="pilcrow">¶</a></p>
1608 <p id="section-2-2.2.2">The right to invoke the subscribed service may be
1609 delegated by the Customer to third-party end users or brokering
1610 services.<a href="#section-2-2.2.2" class="pilcrow">¶</a></p>
1611 <p id="section-2-2.2.3">A Customer can be a Service
1612 Provider, an application owner, an enterprise, a user, etc.<a href="#section-2-2.2.3" class="pilcrow">¶</a></p>
1613 </dd>
1614 <dd class="break"></dd>
1615 <dt id="section-2-2.3">Network Provider (or Provider):</dt>
1616 <dd style="margin-left: 1.5em" id="section-2-2.4">
1617 <p id="section-2-2.4.1">Owns and administers
1618 one or many transport domain(s) (typically Autonomous Systems (ASes))
1619 composed of (IP) switching and transmission resources (e.g.,
1620 routing, switching, forwarding, etc.). Network Providers are
1621 responsible for delivering and operating connectivity services
1622 (e.g., offering global or restricted reachability at specific
1623 rates). Offered connectivity services may not necessarily be
1624 restricted to IP.<a href="#section-2-2.4.1" class="pilcrow">¶</a></p>
1625 <p id="section-2-2.4.2">The policies to be
1626 enforced by the connectivity service delivery components can be
1627 derived from the technology-specific clauses that might be included
1628 in agreements with the Customers. If no such clauses are included in
1629 the agreement, the mapping between the connectivity requirements and
1630 the underlying technology-specific policies to be enforced is
1631 deployment specific.<a href="#section-2-2.4.2" class="pilcrow">¶</a></p>
1632 </dd>
1633 <dd class="break"></dd>
1634 <dt id="section-2-2.5">Quotation Order:</dt>
1635 <dd style="margin-left: 1.5em" id="section-2-2.6">Denotes a request made by the
1636 Customer to the Provider that includes a set of requirements. The
1637 Customer may express its service-specific requirements by assigning
1638 (strictly or loosely defined) values to the information items
1639 included in the commonly understood template (e.g., CPP template)
1640 describing the offered service. These requirements constitute the
1641 parameters to be mutually agreed upon.<a href="#section-2-2.6" class="pilcrow">¶</a>
1642 </dd>
1643 <dd class="break"></dd>
1644 <dt id="section-2-2.7">Offer:</dt>
1645 <dd style="margin-left: 1.5em" id="section-2-2.8">
1646 <p id="section-2-2.8.1">Refers to a response made by the Provider to a
1647 Customer's quotation order that describes the ability of the
1648 Provider to satisfy the order at the time of its receipt. Offers
1649 reflect the capability of the Provider in accommodating received
1650 Customer orders beyond monolithic 'yes/no' answers.<a href="#section-2-2.8.1" class="pilcrow">¶</a></p>
1651 <p id="section-2-2.8.2">An offer may fully or partially meet the
1652 requirements of the corresponding order. In the latter case, it may
1653 include alternative suggestions that the Customer may take into
1654 account by issuing a new order.<a href="#section-2-2.8.2" class="pilcrow">¶</a></p>
1655 </dd>
1656 <dd class="break"></dd>
1657 <dt id="section-2-2.9">Agreement:</dt>
1658 <dd style="margin-left: 1.5em" id="section-2-2.10">Refers to an order placed by the Customer
1659 and accepted by the Provider. It signals the successful conclusion
1660 of a negotiation cycle.<a href="#section-2-2.10" class="pilcrow">¶</a>
1661 </dd>
1662 <dd class="break"></dd>
1663 </dl>
1664 </section>
1665 <div id="fe">
1666 <section id="section-3">
1667 <h2 id="name-cpnp-functional-elements">
1668 <a href="#section-3" class="section-number selfRef">3. </a><a href="#name-cpnp-functional-elements" class="section-name selfRef">CPNP Functional Elements</a>
1669 </h2>
1670 <p id="section-3-1">The following functional elements are defined:<a href="#section-3-1" class="pilcrow">¶</a></p>
1671 <span class="break"></span><dl class="dlParallel" id="section-3-2">
1672 <dt id="section-3-2.1">CPNP client (or client): </dt>
1673 <dd style="margin-left: 1.5em" id="section-3-2.2">
1674 <p id="section-3-2.2.1">Denotes a software instance
1675 that sends CPNP requests and receives CPNP responses. The current
1676 operations that can be performed by a CPNP client are listed
1677 below:<a href="#section-3-2.2.1" class="pilcrow">¶</a></p>
1678 <ol start="1" type="1" class="normal type-1" id="section-3-2.2.2">
1679 <li id="section-3-2.2.2.1">Create a quotation order (<a href="#provision" class="xref">Section 9.2.1</a>).<a href="#section-3-2.2.2.1" class="pilcrow">¶</a>
1680 </li>
1681 <li id="section-3-2.2.2.2">Cancel an ongoing quotation order under negotiation (<a href="#cancel" class="xref">Section 9.2.7</a>).<a href="#section-3-2.2.2.2" class="pilcrow">¶</a>
1682 </li>
1683 <li id="section-3-2.2.2.3">Accept an offer made by a server (<a href="#accept" class="xref">Section 9.2.4</a>).<a href="#section-3-2.2.2.3" class="pilcrow">¶</a>
1684 </li>
1685 <li id="section-3-2.2.2.4">Withdraw an agreement (<a href="#with" class="xref">Section 9.2.8</a>).<a href="#section-3-2.2.2.4" class="pilcrow">¶</a>
1686 </li>
1687 <li id="section-3-2.2.2.5">Update an agreement (<a href="#upd" class="xref">Section 9.2.9</a>).<a href="#section-3-2.2.2.5" class="pilcrow">¶</a>
1688 </li>
1689 </ol>
1690 </dd>
1691 <dd class="break"></dd>
1692 <dt id="section-3-2.3">CPNP server (or server):</dt>
1693 <dd style="margin-left: 1.5em" id="section-3-2.4">
1694 <p id="section-3-2.4.1">Denotes a software instance
1695 that receives CPNP requests and sends back CPNP responses
1696 accordingly. The CPNP server is responsible for the following
1697 operations:<a href="#section-3-2.4.1" class="pilcrow">¶</a></p>
1698 <ol start="1" type="1" class="normal type-1" id="section-3-2.4.2">
1699 <li id="section-3-2.4.2.1">Process a quotation order (<a href="#proc" class="xref">Section 9.2.2</a>).<a href="#section-3-2.4.2.1" class="pilcrow">¶</a>
1700 </li>
1701 <li id="section-3-2.4.2.2">Make an offer (<a href="#offer" class="xref">Section 9.2.3</a>).<a href="#section-3-2.4.2.2" class="pilcrow">¶</a>
1702 </li>
1703 <li id="section-3-2.4.2.3">Cancel an ongoing quotation order (<a href="#sordu" class="xref">Section 11.2.3</a>).<a href="#section-3-2.4.2.3" class="pilcrow">¶</a>
1704 </li>
1705 <li id="section-3-2.4.2.4">Process an order withdrawal (<a href="#sordu" class="xref">Section 11.2.3</a>).<a href="#section-3-2.4.2.4" class="pilcrow">¶</a>
1706 </li>
1707 </ol>
1708 </dd>
1709 <dd class="break"></dd>
1710 </dl>
1711 </section>
1712 </div>
1713 <div id="opm">
1714 <section id="section-4">
1715 <h2 id="name-order-processing-models">
1716 <a href="#section-4" class="section-number selfRef">4. </a><a href="#name-order-processing-models" class="section-name selfRef">Order Processing Models</a>
1717 </h2>
1718 <p id="section-4-1">For preparing their service orders, Customers may need to be aware of
1719 the offered services. Therefore, Providers should first proceed with the
1720 announcement (or the exposure) of the services they can provide. The
1721 service announcement process may take place at designated global or
1722 Provider-specific service markets or through explicit interactions with
1723 the Providers. The details of this process are outside the scope of this
1724 document.<a href="#section-4-1" class="pilcrow">¶</a></p>
1725 <p id="section-4-2">With or without such service announcement/exposure mechanisms in
1726 place, the following order processing models can be distinguished:<a href="#section-4-2" class="pilcrow">¶</a></p>
1727 <span class="break"></span><dl class="dlNewline" id="section-4-3">
1728 <dt id="section-4-3.1">Frozen model:</dt>
1729 <dd style="margin-left: 1.5em" id="section-4-3.2">The Customer
1730 cannot actually negotiate the parameters of the service(s) offered
1731 by a Provider. After consulting the Provider's service portfolio,
1732 the Customer selects the service offer to which he or she wants to subscribe and
1733 places an order to the Provider. Order handling is quite simple on
1734 the Provider side because the service is not customized per
1735 Customer's requirements, but rather designed to address a
1736 Customer base that shares the same requirements (i.e., these
1737 Customers share the same Connectivity Provisioning Profile). This mode
1738 can be implemented using existing tools such as <span>[<a href="#RFC8309" class="xref">RFC8309</a>]</span>.<a href="#section-4-3.2" class="pilcrow">¶</a>
1739 </dd>
1740 <dd class="break"></dd>
1741 <dt id="section-4-3.3">Negotiation-based model:</dt>
1742 <dd style="margin-left: 1.5em" id="section-4-3.4">Unlike the frozen model, the Customer documents
1743 his/her requirements in a request for a quotation, which is then
1744 sent to one or several Providers. Solicited Providers check whether
1745 they can address these requirements or not, and get back to the
1746 Customer accordingly, possibly with an offer that may not exactly
1747 match the Customer's requirements (e.g., a 100 Mbps connection cannot be
1748 provisioned given the amount of available resources, but an 80 Mbps
1749 connection can be provided). A negotiation between the Customer and
1750 the Provider(s) then follows until both parties reach an agreement
1751 (or do not).<a href="#section-4-3.4" class="pilcrow">¶</a>
1752 </dd>
1753 <dd class="break"></dd>
1754 </dl>
1755 <p id="section-4-4">Both frozen and negotiation-based models require the existence of
1756 appropriate service templates like a CPP template and their
1757 instantiation for expressing specific offerings from Providers and
1758 service requirements from Customers, respectively. CPNP can be used in
1759 either model for automating the required Customer-Provider interactions.
1760 The frozen model can be seen as a special case of the negotiation-based
1761 model. This document focuses on the negotiation-based model. Not only
1762 'yes/no' answers but also counterproposals may be offered
1763 by the Provider in response to Customer orders.<a href="#section-4-4" class="pilcrow">¶</a></p>
1764 <p id="section-4-5">Order processing management on the Network Provider's side usually
1765 solicits features supported by the following functional blocks:<a href="#section-4-5" class="pilcrow">¶</a></p>
1766 <ul class="normal">
1767 <li class="normal" id="section-4-6.1">Network provisioning (including order activation, Network
1768 Planning, etc.)<a href="#section-4-6.1" class="pilcrow">¶</a>
1769 </li>
1770 <li class="normal" id="section-4-6.2">Authentication, authorization, and accounting (AAA)<a href="#section-4-6.2" class="pilcrow">¶</a>
1771 </li>
1772 <li class="normal" id="section-4-6.3">Network and service management (performance measurement and
1773 assessment, fault detection, etc.)<a href="#section-4-6.3" class="pilcrow">¶</a>
1774 </li>
1775 <li class="normal" id="section-4-6.4">Sales-related functional blocks (e.g., billing, invoice
1776 validation)<a href="#section-4-6.4" class="pilcrow">¶</a>
1777 </li>
1778 <li class="normal" id="section-4-6.5">Network impact analysis<a href="#section-4-6.5" class="pilcrow">¶</a>
1779 </li>
1780 </ul>
1781 <p id="section-4-7">CPNP does not assume any specific knowledge about these functional
1782 blocks, drawing an explicit line between protocol operation and the
1783 logic for handling connectivity provisioning requests. An order
1784 processing logic is typically fed with the information manipulated by
1785 the aforementioned functional blocks. For example, the resources that
1786 can be allocated to accommodate the Customer's requirements may depend on
1787 network availability estimates as calculated by the planning functions
1788 and related policies, as well as the number of orders to be processed
1789 simultaneously over a given period of time.<a href="#section-4-7" class="pilcrow">¶</a></p>
1790 <p id="section-4-8">This document does not elaborate on how Customers are identified and
1791 subsequently managed by the Provider's information system.<a href="#section-4-8" class="pilcrow">¶</a></p>
1792 </section>
1793 </div>
1794 <div id="suc">
1795 <section id="section-5">
1796 <h2 id="name-sample-use-cases">
1797 <a href="#section-5" class="section-number selfRef">5. </a><a href="#name-sample-use-cases" class="section-name selfRef">Sample Use Cases</a>
1798 </h2>
1799 <p id="section-5-1">A non-exhaustive list of CPNP use cases is provided below:<a href="#section-5-1" class="pilcrow">¶</a></p>
1800 <ol start="1" type="1" class="normal type-1" id="section-5-2">
1801 <li id="section-5-2.1">
1802 <p id="section-5-2.1.1"><span>[<a href="#RFC4176" class="xref">RFC4176</a>]</span> introduces the Layer 3 VPN (L3VPN)
1803 Service Order Management functional block, which is responsible for
1804 managing the requests initiated by the Customers and tracks the
1805 status of the completion of the related operations. CPNP can be used
1806 between the Customer and the Provider to negotiate L3VPN service
1807 parameters.<a href="#section-5-2.1.1" class="pilcrow">¶</a></p>
1808 <p id="section-5-2.1.2">A CPNP server could therefore
1809 be part of the L3VPN Service Order Management functional block
1810 discussed in <span>[<a href="#RFC4176" class="xref">RFC4176</a>]</span>. A L3VPN Service YANG
1811 data model (L3SM) is defined in <span>[<a href="#RFC8299" class="xref">RFC8299</a>]</span>. Once
1812 an agreement is reached, the service can be provisioned using, e.g.,
1813 the L3VPN Network YANG data model specified in <span>[<a href="#I-D.ietf-opsawg-l3sm-l3nm" class="xref">L3VPN-NETWORK-YANG</a>]</span>.<a href="#section-5-2.1.2" class="pilcrow">¶</a></p>
1814 <p id="section-5-2.1.3">Likewise, a CPNP server could be part of the Layer
1815 2 VPN (L2VPN) Service Order Management functional block. A YANG data
1816 model for L2VPN service delivery is defined in <span>[<a href="#RFC8466" class="xref">RFC8466</a>]</span>. Once an agreement is reached, the L2VPN
1817 service can be provisioned using, e.g., the L2VPN Network YANG data model
1818 specified in <span>[<a href="#I-D.ietf-opsawg-l2nm" class="xref">L2VPN-NETWORK-YANG</a>]</span>.<a href="#section-5-2.1.3" class="pilcrow">¶</a></p>
1819 </li>
1820 <li id="section-5-2.2">
1821 <p id="section-5-2.2.1">CPNP can be used between two adjacent domains to deliver IP
1822 interconnection services (e.g., enable, update, disconnect). For
1823 example, two Autonomous Systems (ASes) can be connected via several
1824 interconnection points. CPNP can be used between these ASes to
1825 upgrade existing links, request additional resources, provision a
1826 new interconnection point, etc.<a href="#section-5-2.2.1" class="pilcrow">¶</a></p>
1827 <p id="section-5-2.2.2">See, for
1828 example, the framework documented in <span>[<a href="#ETICS" class="xref">ETICS</a>]</span>.<a href="#section-5-2.2.2" class="pilcrow">¶</a></p>
1829 </li>
1830 <li id="section-5-2.3">An integrated Provider can use CPNP to rationalize connectivity
1831 provisioning needs related to its service portfolio. A CPNP server
1832 function is used by network operations teams. A CPNP interface to
1833 trigger CPNP negotiation cycles is exposed to service management
1834 teams.<a href="#section-5-2.3" class="pilcrow">¶</a>
1835 </li>
1836 <li id="section-5-2.4">
1837 <p id="section-5-2.4.1">Service Providers can use CPNP to initiate connectivity
1838 provisioning requests towards a number of Network Providers so as to
1839 optimize the cost of delivering their services. Although multiple
1840 CPNP ordering cycles can be initiated by a Service Provider towards
1841 multiple Network Providers, a subset of these orders may actually be
1842 put into effect.<a href="#section-5-2.4.1" class="pilcrow">¶</a></p>
1843 <p id="section-5-2.4.2">For example, a cloud
1844 Service Provider can use CPNP to request more resources from Network
1845 Providers.<a href="#section-5-2.4.2" class="pilcrow">¶</a></p>
1846 </li>
1847 <li id="section-5-2.5">CPNP can also be used in the context of network slicing
1848 <span>[<a href="#I-D.geng-netslices-architecture" class="xref">NETSLICES-ARCH</a>]</span> to request network
1849 resources together with a set of requirements that need to be
1850 satisfied by the Provider. Such requirements are not restricted to
1851 basic IP forwarding capabilities, but may also include a
1852 characterization of a set of service functions that may be invoked.
1853 For the network slicing case, the instances of a CPP template could
1854 be derived from the network slice template documented in
1855 <span>[<a href="#I-D.contreras-teas-slice-nbi" class="xref">TEAS-SLICE-NBI</a>]</span>.<a href="#section-5-2.5" class="pilcrow">¶</a>
1856 </li>
1857 <li id="section-5-2.6">
1858 <p id="section-5-2.6.1">CPNP can be used in Machine-to-Machine (M2M) environments to
1859 dynamically subscribe to M2M services (e.g., access data
1860 retrieved by a set of sensors, extend sensor coverage, etc.).<a href="#section-5-2.6.1" class="pilcrow">¶</a></p>
1861 <p id="section-5-2.6.2">Also, Internet of Things (IoT) <span>[<a href="#RFC6574" class="xref">RFC6574</a>]</span>
1862 domains may rely on CPNP to enable dynamic
1863 access to data produced by involved objects, according to their
1864 specific policies, to various external stakeholders such as data
1865 analytics and business intelligence companies. Direct CPNP-based
1866 interactions between IoT domains and interested parties enable open
1867 access to diverse sets of data across the Internet, e.g., from
1868 multiple types of sensors, user groups, and/or geographical
1869 areas.<a href="#section-5-2.6.2" class="pilcrow">¶</a></p>
1870 </li>
1871 <li id="section-5-2.7">CPNP can be used in the context of Interface to Network Security Functions
1872 (I2NSF) <span>[<a href="#RFC8329" class="xref">RFC8329</a>]</span>
1873 to capture the Customer-driven policies to
1874 be enforced by a set of Network Security Functions.<a href="#section-5-2.7" class="pilcrow">¶</a>
1875 </li>
1876 <li id="section-5-2.8">
1877 <p id="section-5-2.8.1">A Provider offering cloud services can expose a CPNP interface to
1878 allow Customers to dynamically negotiate typical data center
1879 resources, such as additional storage, processing and networking
1880 resources, enhanced security filters, etc.<a href="#section-5-2.8.1" class="pilcrow">¶</a></p>
1881 <p id="section-5-2.8.2">Cloud computing Providers typically structure their
1882 computation service offerings by bundling CPU, RAM, and storage
1883 units as quotas, instances, or flavors that can be consumed in an
1884 ephemeral or temporal fashion during the lifetime of the required
1885 function. A similar approach is followed by CPNP (see for example,
1886 <a href="#activate" class="xref">Section 9.2.11</a>).<a href="#section-5-2.8.2" class="pilcrow">¶</a></p>
1887 </li>
1888 <li id="section-5-2.9">In the inter-cloud context (also called cloud of clouds or cloud
1889 federation), CPNP can be used to reserve computing and networking
1890 resources hosted by various cloud infrastructures.<a href="#section-5-2.9" class="pilcrow">¶</a>
1891 </li>
1892 <li id="section-5-2.10">
1893 <p id="section-5-2.10.1">CDN Providers can use CPNP to extend their footprint by
1894 interconnecting their respective CDN infrastructures <span>[<a href="#RFC6770" class="xref">RFC6770</a>]</span> (see <a href="#cdni" class="xref">Figure 1</a>).<a href="#section-5-2.10.1" class="pilcrow">¶</a></p>
1895 <span id="name-cdn-interconnection"></span><div id="cdni">
1896 <figure id="figure-1">
1897 <div class="artwork art-text alignCenter" id="section-5-2.10.2.1">
1898 <pre>
1899 ,--,--,--. ,--,--,--.
1900 ,-' `-. ,-' `-.
1901 (CDN Provider 'A')=====(CDN Provider 'B')
1902 `-. (CDN-A) ,-' `-. (CDN-B) ,-'
1903 `--'--'--' `--'--'--'
1904 </pre>
1905 </div>
1906 <figcaption><a href="#figure-1" class="selfRef">Figure 1</a>:
1907 <a href="#name-cdn-interconnection" class="selfRef">CDN Interconnection</a>
1908 </figcaption></figure>
1909 </div>
1910 </li>
1911 <li id="section-5-2.11">
1912 <p id="section-5-2.11.1">Mapping Service Providers (MSPs) <span>[<a href="#RFC7215" class="xref">RFC7215</a>]</span>
1913 can use CPNP to enrich their mapping database by interconnecting
1914 their mapping system (see <a href="#map" class="xref">Figure 2</a>). This
1915 interconnection allows the relaxation of the constraints on PxTR (Proxy
1916 Ingress/Egress Tunnel Router) in favour of native LISP (Locator/ID
1917 Separation Protocol) forwarding <span>[<a href="#RFC6830" class="xref">RFC6830</a>]</span>.
1918 Also, it prevents the fragmentation of the LISP mapping database. A
1919 framework is described in <span>[<a href="#I-D.boucadair-lisp-idr-ms-discovery" class="xref">LISP-MS-DISCOVERY</a>]</span>.<a href="#section-5-2.11.1" class="pilcrow">¶</a></p>
1920 <span id="name-lisp-mapping-system-interco"></span><div id="map">
1921 <figure id="figure-2">
1922 <div class="artwork art-text alignCenter" id="section-5-2.11.2.1">
1923 <pre>
1924 ,--,--,--. ,--,--,--.
1925 ,-' `-. ,-' `-.
1926 (Mapping System 'A')===(Mapping System 'B')
1927 `-. ,-' `-. ,-'
1928 `--'--'--' `--'--'--'
1929 </pre>
1930 </div>
1931 <figcaption><a href="#figure-2" class="selfRef">Figure 2</a>:
1932 <a href="#name-lisp-mapping-system-interco" class="selfRef">LISP Mapping System Interconnect</a>
1933 </figcaption></figure>
1934 </div>
1935 </li>
1936 <li id="section-5-2.12">CPNP may also be used between SDN (Software-Defined Networking)
1937 controllers in contexts where Cooperating Layered Architecture for
1938 Software-Defined Networking (CLAS) is enabled <span>[<a href="#RFC8597" class="xref">RFC8597</a>]</span>.<a href="#section-5-2.12" class="pilcrow">¶</a>
1939 </li>
1940 </ol>
1941 </section>
1942 </div>
1943 <div id="dm">
1944 <section id="section-6">
1945 <h2 id="name-cpnp-deployment-models">
1946 <a href="#section-6" class="section-number selfRef">6. </a><a href="#name-cpnp-deployment-models" class="section-name selfRef">CPNP Deployment Models</a>
1947 </h2>
1948 <p id="section-6-1">Several CPNP deployment models can be envisaged. Two examples are
1949 listed below:<a href="#section-6-1" class="pilcrow">¶</a></p>
1950 <ul class="normal">
1951 <li class="normal" id="section-6-2.1">The Customer deploys a CPNP client while one or several CPNP
1952 servers are deployed by the Provider. A CPNP client can discover its
1953 CPNP servers using a variety of means (static, dynamic, etc.).<a href="#section-6-2.1" class="pilcrow">¶</a>
1954 </li>
1955 <li class="normal" id="section-6-2.2">The Customer does not enable any CPNP client. The Provider
1956 maintains a Customer Order Management portal. The Customer can
1957 initiate connectivity provisioning quotation orders via the portal;
1958 appropriate CPNP messages are then generated and sent to the
1959 relevant CPNP server. In this model, both the CPNP client and CPNP
1960 server are under the responsibility of the same administrative
1961 entity (i.e., Network Provider).<a href="#section-6-2.2" class="pilcrow">¶</a>
1962 </li>
1963 </ul>
1964 <p id="section-6-3">Once the negotiation of connectivity provisioning parameters is
1965 successfully concluded, that is, an order has been placed by the
1966 Customer, the actual network provisioning operations are initiated. The
1967 specification of related dynamic resource allocation and policy
1968 enforcement schemes, as well as how CPNP servers interact with the
1969 network provisioning functional blocks on the Provider side, are out of the
1970 scope of this document.<a href="#section-6-3" class="pilcrow">¶</a></p>
1971 <p id="section-6-4">This document does not make any assumptions about the CPNP deployment
1972 model either.<a href="#section-6-4" class="pilcrow">¶</a></p>
1973 </section>
1974 </div>
1975 <div id="cnm">
1976 <section id="section-7">
1977 <h2 id="name-cpnp-negotiation-model">
1978 <a href="#section-7" class="section-number selfRef">7. </a><a href="#name-cpnp-negotiation-model" class="section-name selfRef">CPNP Negotiation Model</a>
1979 </h2>
1980 <p id="section-7-1">CPNP runs between a Customer and a Provider, carrying service orders
1981 from the Customer and corresponding responses from the Provider in
1982 order to reach a service provisioning agreement. As the services
1983 offered by the Provider are well described, by means of the CPP template
1984 for connectivity matters, the negotiation process is essentially a
1985 value-settlement process, where an agreement is pursued on the values of
1986 the commonly understood information items (service parameters) included
1987 in the service description template (<a href="#service_template" class="xref">Section 9.1.9</a>).<a href="#section-7-1" class="pilcrow">¶</a></p>
1988 <p id="section-7-2">The content that CPNP carries and the negotiation logic invoked
1989 at Customer and Provider sides to manipulate the content (i.e.,
1990 the information carried in CPNP messages to proceed with the
1991 negotiation) is transparent to the protocol.<a href="#section-7-2" class="pilcrow">¶</a></p>
1992 <p id="section-7-3">The protocol aims to facilitate the execution of the negotiation
1993 logic by providing the required generic communication primitives.<a href="#section-7-3" class="pilcrow">¶</a></p>
1994 <p id="section-7-4">Since negotiations are initiated and primarily driven by the
1995 Customer's negotiation logic, it is reasonable to assume that the
1996 Customer is the only party that can call for an agreement. An implicit
1997 approach is adopted for not overloading the protocol with additional
1998 messages. In particular, the acceptance of an offer made by the Provider
1999 signals a call for agreement from the Customer. Note that it is almost
2000 certain the Provider will accept this call since it refers to an offer
2001 that the Provider made. Of course, at any point the Provider or the Customer
2002 may quit the negotiations, each on its own grounds.<a href="#section-7-4" class="pilcrow">¶</a></p>
2003 <p id="section-7-5">Based on the above, CPNP adopts a quotation order/offer/answer model,
2004 which proceeds through the following basic steps (<a href="#service_variants" class="xref">Figure 3</a>):<a href="#section-7-5" class="pilcrow">¶</a></p>
2005 <ol start="1" type="1" class="normal type-1" id="section-7-6">
2006 <li id="section-7-6.1">The CPNP client specifies its service requirements in a
2007 Provisioning Quotation Order (PQO). The order may include strictly or
2008 loosely defined values in the clauses describing service
2009 provisioning characteristics.<a href="#section-7-6.1" class="pilcrow">¶</a>
2010 </li>
2011 <li id="section-7-6.2">The CPNP server declines the PQO, or makes an offer to address
2012 the requirements of the PQO, or suggests a counterproposal that
2013 partially addresses the requirements of the PQO in case specific
2014 requirements cannot be accommodated.<a href="#section-7-6.2" class="pilcrow">¶</a>
2015 </li>
2016 <li id="section-7-6.3">The CPNP client either accepts or declines the offer. The acceptance
2017 of the offer by the CPNP client implies a call for
2018 agreement and, thus, the
2019 agreement between both parties and the conclusion of the
2020 negotiation.<a href="#section-7-6.3" class="pilcrow">¶</a>
2021 </li>
2022 </ol>
2023 <span id="name-simplified-service-negotiat"></span><div id="service_variants">
2024 <figure id="figure-3">
2025 <div class="artwork art-text alignCenter" id="section-7-7.1">
2026 <pre>
2027 +------+ +------+
2028 |Client| |Server|
2029 +------+ +------+
2030 |=====Requested Service=====&gt;|
2031 |&lt;=====Offered Service=======|
2032 |=====Accepted Service======&gt;|
2033 </pre>
2034 </div>
2035 <figcaption><a href="#figure-3" class="selfRef">Figure 3</a>:
2036 <a href="#name-simplified-service-negotiat" class="selfRef">Simplified Service Negotiation</a>
2037 </figcaption></figure>
2038 </div>
2039 <p id="section-7-8">Multiple instances of CPNP may run at a Customer's or a Provider's
2040 domains. A CPNP client may be engaged in multiple, simultaneous
2041 negotiations with the same or different CPNP servers (parallel
2042 negotiations, see <a href="#mser" class="xref">Section 8.10</a>), and a CPNP server may
2043 need to negotiate with other Provider(s) as part of negotiations that
2044 are ongoing with a CPNP client (cascaded negotiations, see <a href="#cascaded" class="xref">Section 8.8</a>).<a href="#section-7-8" class="pilcrow">¶</a></p>
2045 <p id="section-7-9">CPNP relies on various timers to run its operations. Two types of
2046 timers are defined: those that are specific to CPNP message transmission
2047 and those that are specific to the negotiation logic. The latter are
2048 used to guide the negotiation logic at both CPNP client and CPNP server
2049 sides, particularly in cases where the CPNP client is involved in
2050 parallel negotiations with several CPNP servers or in cases where the
2051 CPNP server is, in turn, involved in negotiations with other Providers for
2052 processing a given Customer-originated quotation order. CPNP allows a
2053 CPNP server to request extra time to proceed with the negotiation.
2054 This request may be accepted or rejected by the CPNP client.<a href="#section-7-9" class="pilcrow">¶</a></p>
2055 <p id="section-7-10">Providers may need to publish available services to the Customers
2056 (see <a href="#opm" class="xref">Section 4</a>). CPNP may optionally support this
2057 functionality. Dedicated templates can be defined for the purpose of
2058 service announcement, which will be used by the CPNP clients to initiate
2059 their CPNP negotiation cycles.<a href="#section-7-10" class="pilcrow">¶</a></p>
2060 <p id="section-7-11">For the sake of simplicity, a single offer/answer stage is assumed
2061 within one CPNP negotiation cycle. Nevertheless, as already stated,
2062 multiple CPNP negotiation cycles can be undertaken by a CPNP client (see
2063 <a href="#examples" class="xref">Figure 4</a>).<a href="#section-7-11" class="pilcrow">¶</a></p>
2064 <p id="section-7-12">The model is flexible enough to accommodate changing conditions
2065 during the lifetime of a service (e.g., the introduction of an additional
2066 VPN site).<a href="#section-7-12" class="pilcrow">¶</a></p>
2067 <span id="name-overall-negotiation-process"></span><div id="examples">
2068 <figure id="figure-4">
2069 <div class="artwork art-text alignCenter" id="section-7-13.1">
2070 <pre>
2071 +------+ +------+ +------+ +------+
2072 |Client| |Server| |Client| |Server|
2073 +------+ +------+ +------+ +------+
2074 |=====Quotation Order=====&gt;| |=====Quotation Order=====&gt;|
2075 |&lt;==========Offer==========| |&lt;==========Offer==========|
2076 |===========Accept========&gt;| |==========Decline========&gt;|
2077
2078 1-Step Successful Negotiation 1-Step Failed Negotiation
2079 Cycle Cycle
2080
2081 +------+ +------+ +------+ +------+
2082 |Client| |Server| |Client| |Server|
2083 +------+ +------+ +------+ +------+
2084 |===Quotation Order(a)====&gt;| |===Quotation Order(i)====&gt;|
2085 |&lt;==========Offer==========| |&lt;==========Offer==========|
2086 |==========Decline========&gt;| |==========Decline========&gt;|
2087 |===Quotation Order(b)====&gt;| |===Quotation Order(j)====&gt;|
2088 |&lt;==========Offer==========| |&lt;==========Offer==========|
2089 |===========Accept========&gt;| |==========Decline========&gt;|
2090 |===Quotation Order(k)====&gt;|
2091 |&lt;==========Offer==========|
2092 |==========Decline========&gt;|
2093 |===Quotation Order(l)====&gt;|
2094 |&lt;==Fail to make an offer==|
2095
2096 N-Step Negotiation Cycle: N-Step Negotiation Cycle:
2097 Successful Negotiation Failed Negotiation
2098 </pre>
2099 </div>
2100 <figcaption><a href="#figure-4" class="selfRef">Figure 4</a>:
2101 <a href="#name-overall-negotiation-process" class="selfRef">Overall Negotiation Process</a>
2102 </figcaption></figure>
2103 </div>
2104 <p id="section-7-14">The means used by a CPNP client to retrieve a list of active/accepted
2105 offers are not defined in this document.<a href="#section-7-14" class="pilcrow">¶</a></p>
2106 <p id="section-7-15">An order can be implicitly or explicitly activated.
2107 <span><a href="https://www.rfc-editor.org/rfc/rfc7297#section-3.11" class="relref">Section 3.11</a> of [<a href="#RFC7297" class="xref">RFC7297</a>]</span> specifies a dedicated clause called
2108 Activation Means. Such a clause indicates the required action(s) to be
2109 undertaken to activate access to the (IP connectivity) service. This
2110 document defines a dedicated CPNP message that can be used for explicit
2111 activation (<a href="#activate" class="xref">Section 9.2.11</a>).<a href="#section-7-15" class="pilcrow">¶</a></p>
2112 </section>
2113 </div>
2114 <div id="po">
2115 <section id="section-8">
2116 <h2 id="name-protocol-overview">
2117 <a href="#section-8" class="section-number selfRef">8. </a><a href="#name-protocol-overview" class="section-name selfRef">Protocol Overview</a>
2118 </h2>
2119 <section id="section-8.1">
2120 <h3 id="name-client-server-communication">
2121 <a href="#section-8.1" class="section-number selfRef">8.1. </a><a href="#name-client-server-communication" class="section-name selfRef">Client/Server Communication</a>
2122 </h3>
2123 <p id="section-8.1-1">CPNP is a client/server protocol that can run over any transport
2124 protocol. The default transport mode is UDP secured with Datagram
2125 Transport Layer Security (DTLS) <span>[<a href="#RFC6347" class="xref">RFC6347</a>]</span>. No
2126 permanent CPNP transport session needs to be maintained between the
2127 client and the server.<a href="#section-8.1-1" class="pilcrow">¶</a></p>
2128 <p id="section-8.1-2">The CPNP client can be configured with the CPNP server(s).
2129 Typically, the CPNP client is configured with an IP address together
2130 with a port number using manual or dynamic configuration means
2131 (e.g., DHCP). Alternatively, a Provider may advertise the port number
2132 (CPNP_PORT) it uses to bind the CPNP service using SRV <span>[<a href="#RFC2782" class="xref">RFC2782</a>]</span>.<a href="#section-8.1-2" class="pilcrow">¶</a></p>
2133 <p id="section-8.1-3">The CPNP client may be provided with a domain name of the CPNP
2134 server for PKIX-based authentication purposes. CPNP servers should
2135 prefer the use of DNS-ID and SRV-ID over CN-ID identifier types in
2136 certificate requests (<span><a href="https://www.rfc-editor.org/rfc/rfc6125#section-2.3" class="relref">Section 2.3</a> of [<a href="#RFC6125" class="xref">RFC6125</a>]</span>).
2137 URI-IDs should not be used for CPNP server identity verification.<a href="#section-8.1-3" class="pilcrow">¶</a></p>
2138 <p id="section-8.1-4">The client sends CPNP requests using CPNP_PORT as the destination
2139 port number. The same port number used as the source port number of a
2140 CPNP request sent to a CPNP server is used by the server to reply to
2141 that request.<a href="#section-8.1-4" class="pilcrow">¶</a></p>
2142 <p id="section-8.1-5">CPNP is independent of the IP address family.<a href="#section-8.1-5" class="pilcrow">¶</a></p>
2143 <p id="section-8.1-6">CPNP retransmission for unreliable transports is discussed in
2144 <a href="#retrans" class="xref">Section 11.4</a>.<a href="#section-8.1-6" class="pilcrow">¶</a></p>
2145 <p id="section-8.1-7">Considerations related to mutual authentication are discussed in
2146 <a href="#Security" class="xref">Section 13</a>.<a href="#section-8.1-7" class="pilcrow">¶</a></p>
2147 </section>
2148 <section id="section-8.2">
2149 <h3 id="name-policy-configuration-on-the">
2150 <a href="#section-8.2" class="section-number selfRef">8.2. </a><a href="#name-policy-configuration-on-the" class="section-name selfRef">Policy Configuration on the CPNP Server</a>
2151 </h3>
2152 <p id="section-8.2-1">As an input to its decision-making process, the CPNP server may be
2153 connected to various external modules such as Customer Profiles,
2154 Network Topology, Network Resource Management, Order Repositories,
2155 AAA, and Network Provisioning Manager (an example is shown in <a href="#fb" class="xref">Figure 5</a>).<a href="#section-8.2-1" class="pilcrow">¶</a></p>
2156 <p id="section-8.2-2">These external modules provide inputs to the CPNP server so that
2157 it can do the following:<a href="#section-8.2-2" class="pilcrow">¶</a></p>
2158 <ul class="normal">
2159 <li class="normal" id="section-8.2-3.1">Check whether a Customer is entitled to initiate a provisioning
2160 quotation request.<a href="#section-8.2-3.1" class="pilcrow">¶</a>
2161 </li>
2162 <li class="normal" id="section-8.2-3.2">Check whether a Customer is entitled to cancel an ongoing
2163 order.<a href="#section-8.2-3.2" class="pilcrow">¶</a>
2164 </li>
2165 <li class="normal" id="section-8.2-3.3">Check whether administrative data (e.g., billing-related
2166 information) have been verified before the processing of the
2167 request starts.<a href="#section-8.2-3.3" class="pilcrow">¶</a>
2168 </li>
2169 <li class="normal" id="section-8.2-3.4">Check whether network capacity is available or additional
2170 capacity is required.<a href="#section-8.2-3.4" class="pilcrow">¶</a>
2171 </li>
2172 <li class="normal" id="section-8.2-3.5">Receive guidelines from network design and sales blocks (e.g.,
2173 pricing, network usage levels, thresholds associated with the
2174 number of CPP templates that can be processed over a given period
2175 of time as a function of the nature of the service to be
2176 delivered, etc.).<a href="#section-8.2-3.5" class="pilcrow">¶</a>
2177 </li>
2178 <li class="normal" id="section-8.2-3.6">Transfer completed orders to network provisioning blocks
2179 (referred to as "Network Provisioning Manager" in <a href="#fb" class="xref">Figure 5</a>). For example, the outcome of CPNP may be
2180 passed to modules such as Application-Based Network Operations
2181 (ABNO) <span>[<a href="#RFC7491" class="xref">RFC7491</a>]</span> or network controllers.
2182 These controllers will use protocols such as NETCONF <span>[<a href="#RFC6241" class="xref">RFC6241</a>]</span> to interact with the appropriate network
2183 nodes and functions for the sake of proper service activation and
2184 delivery.<a href="#section-8.2-3.6" class="pilcrow">¶</a>
2185 </li>
2186 </ul>
2187 <p id="section-8.2-4">The above list of CPNP server operations is not
2188 exhaustive.<a href="#section-8.2-4" class="pilcrow">¶</a></p>
2189 <span id="name-order-handling-management-f"></span><div id="fb">
2190 <figure id="figure-5">
2191 <div class="artwork art-text alignCenter" id="section-8.2-5.1">
2192 <pre> . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
2193 .Business &amp; Administrative Management .
2194 .+------------------------++---------------------------+.
2195 .| Business Guidelines || Billing &amp; Charging |.
2196 .+-----------+------------++-----------+---------------+.
2197 . | | .
2198 . +-------------------+ | .
2199 . . . . . . . . . . . . . . . . .|. . .|. . . . . . . . .
2200 . . . . . . . . . . . . . . . . .|. . .|. . . . . . . . .
2201 .Order Handling Management | | .
2202 . +-------------------+ +-------+-----+--------------+ .
2203 . |Network Topology DB+--+ CPNP Server | .
2204 . +-------------------+ +-+---+---+---+---+-----+----+ .
2205 . | | | | | | .
2206 . +------------------------+-+ | | | | | .
2207 . | Network Dimensioning | | | | | | .
2208 . | &amp; Planning | | | | | | .
2209 . +--------------------------+ | | | | | .
2210 . +----------------------------+-+ | | | +---+----+ .
2211 . | | | | | | AAA | .
2212 . | Network +------------+ | | | +--------+ .
2213 . | Resource | +------------+-+ | +-+----------+ .
2214 . | Management | | Customer | | | Orders | .
2215 . | | | Profiles | | | Repository | .
2216 . +-----------------+ +--------------+ | +------------+ .
2217 . . . . . . . . . . . . . . . . . . . .|. . . . . . . . .
2218 +--------------------------------------+----------------+
2219 | Network Provisioning Manager |
2220 +-------------------------------------------------------+
2221 </pre>
2222 </div>
2223 <figcaption><a href="#figure-5" class="selfRef">Figure 5</a>:
2224 <a href="#name-order-handling-management-f" class="selfRef">Order Handling Management Functional Block (Focus on Internal Interfaces)</a>
2225 </figcaption></figure>
2226 </div>
2227 <p id="section-8.2-6">The following order-handling modes can also be configured on the
2228 server:<a href="#section-8.2-6" class="pilcrow">¶</a></p>
2229 <span class="break"></span><dl class="dlParallel" id="section-8.2-7">
2230 <dt id="section-8.2-7.1">Fully automated mode:</dt>
2231 <dd style="margin-left: 1.5em" id="section-8.2-7.2">This mode does not require any action
2232 from the administrator when receiving a request for a service. The
2233 server can execute its decision-making process related to the
2234 orders received and can generate corresponding offers.<a href="#section-8.2-7.2" class="pilcrow">¶</a>
2235 </dd>
2236 <dd class="break"></dd>
2237 <dt id="section-8.2-7.3">Administrative validation checking:</dt>
2238 <dd style="margin-left: 1.5em" id="section-8.2-7.4">Some or all of the server's
2239 operations are subject to administrative validation procedures.
2240 This mode requires an action from the administrator for every
2241 request received. To that aim, the CPNP methods that can be
2242 automatically handled by the server (or are subject to one or
2243 several validation administrative checks) can be configured on the
2244 server.<a href="#section-8.2-7.4" class="pilcrow">¶</a>
2245 </dd>
2246 <dd class="break"></dd>
2247 </dl>
2248 </section>
2249 <div id="session">
2250 <section id="section-8.3">
2251 <h3 id="name-cpnp-session-entries">
2252 <a href="#section-8.3" class="section-number selfRef">8.3. </a><a href="#name-cpnp-session-entries" class="section-name selfRef">CPNP Session Entries</a>
2253 </h3>
2254 <p id="section-8.3-1">A CPNP session entry is represented by a tuple defined as follows:<a href="#section-8.3-1" class="pilcrow">¶</a></p>
2255 <ul class="normal">
2256 <li class="normal" id="section-8.3-2.1">Transport session (typically, the IP address of the CPNP client,
2257 the client's port number, the IP address of the CPNP server, and the CPNP
2258 server's port number).<a href="#section-8.3-2.1" class="pilcrow">¶</a>
2259 </li>
2260 <li class="normal" id="section-8.3-2.2">Incremented sequence number (<a href="#sq_nu" class="xref">Section 11.3</a>).<a href="#section-8.3-2.2" class="pilcrow">¶</a>
2261 </li>
2262 <li class="normal" id="section-8.3-2.3">Customer agreement identifier: This is a unique identifier
2263 assigned to the order under negotiation by the CPNP client (<a href="#cu_id" class="xref">Section 9.1.1</a>). This identifier is also used by the
2264 client to identify the agreement that will result from a
2265 successful negotiation.<a href="#section-8.3-2.3" class="pilcrow">¶</a>
2266 </li>
2267 <li class="normal" id="section-8.3-2.4">Provider agreement identifier: This is a unique identifier
2268 assigned to the order under negotiation by the CPNP server (<a href="#pr_id" class="xref">Section 9.1.2</a>). This identifier is also used by the
2269 server to identify the agreement that will result from a
2270 successful negotiation.<a href="#section-8.3-2.4" class="pilcrow">¶</a>
2271 </li>
2272 <li class="normal" id="section-8.3-2.5">Transaction-ID (<a href="#trans" class="xref">Section 8.4</a>).<a href="#section-8.3-2.5" class="pilcrow">¶</a>
2273 </li>
2274 </ul>
2275 </section>
2276 </div>
2277 <div id="trans">
2278 <section id="section-8.4">
2279 <h3 id="name-cpnp-transactions">
2280 <a href="#section-8.4" class="section-number selfRef">8.4. </a><a href="#name-cpnp-transactions" class="section-name selfRef">CPNP Transactions</a>
2281 </h3>
2282 <p id="section-8.4-1">A CPNP transaction occurs between a client and a server for
2283 completing, modifying, or withdrawing a service agreement, and comprises
2284 all CPNP messages exchanged between the client and the server, from
2285 the first request sent by the client to the final response sent by the
2286 server. A CPNP transaction is bound to a CPNP session (<a href="#session" class="xref">Section 8.3</a>).<a href="#section-8.4-1" class="pilcrow">¶</a></p>
2287 <p id="section-8.4-2">Because multiple CPNP transactions can be maintained by the CPNP
2288 client, the client must assign an identifier to uniquely identify a
2289 given transaction. This identifier is the Transaction-ID.<a href="#section-8.4-2" class="pilcrow">¶</a></p>
2290 <p id="section-8.4-3">The Transaction-ID must be randomly assigned by the CPNP client,
2291 according to the best current practice for generating random numbers
2292 <span>[<a href="#RFC4086" class="xref">RFC4086</a>]</span> that cannot be guessed easily.
2293 The Transaction-ID is used for validating CPNP responses received by the
2294 client.<a href="#section-8.4-3" class="pilcrow">¶</a></p>
2295 <p id="section-8.4-4">In the context of a transaction, the client needs to
2296 select a sequence number randomly and then needs to assign it to the first CPNP message to
2297 send. This number is then incremented for each request message that is
2298 subsequently sent within the ongoing CPNP transaction (see <a href="#sq_nu" class="xref">Section 11.3</a>).<a href="#section-8.4-4" class="pilcrow">¶</a></p>
2299 </section>
2300 </div>
2301 <div id="timers">
2302 <section id="section-8.5">
2303 <h3 id="name-cpnp-timers">
2304 <a href="#section-8.5" class="section-number selfRef">8.5. </a><a href="#name-cpnp-timers" class="section-name selfRef">CPNP Timers</a>
2305 </h3>
2306 <p id="section-8.5-1">CPNP adopts a simple retransmission procedure that relies on a
2307 retransmission timer represented by RETRANS_TIMER and a maximum retry
2308 threshold. The use of RETRANS_TIMER and a maximum retry threshold are
2309 described in <a href="#behavior" class="xref">Section 11</a>.<a href="#section-8.5-1" class="pilcrow">¶</a></p>
2310 <p id="section-8.5-2">The response timer (EXPECTED_RESPONSE_TIME) is set by the client to
2311 denote the time, in seconds, the client will wait to receive a
2312 response from the server to a PQO request
2313 (see <a href="#extime" class="xref">Section 9.1.6</a>). If the timer expires, the
2314 respective PQO is cancelled by the client, and a CANCEL
2315 message is generated accordingly.<a href="#section-8.5-2" class="pilcrow">¶</a></p>
2316 <p id="section-8.5-3">The expected offer timer (EXPECTED_OFFER_TIME) is set by the server
2317 to indicate the time by when the CPNP server is expected to make an
2318 offer to the CPNP client (see <a href="#EXPECTED_OFFER_TIME" class="xref">Section 9.1.7</a>). If no offer is received by
2319 then, the CPNP client will consider the order as rejected.<a href="#section-8.5-3" class="pilcrow">¶</a></p>
2320 <p id="section-8.5-4">An offer expiration timer (VALIDITY_OFFER_TIME) is set by the
2321 server to represent the time, in minutes, after which an offer made by
2322 the server becomes invalid (see <a href="#valtime" class="xref">Section 9.1.8</a>).<a href="#section-8.5-4" class="pilcrow">¶</a></p>
2323 </section>
2324 </div>
2325 <section id="section-8.6">
2326 <h3 id="name-cpnp-operations">
2327 <a href="#section-8.6" class="section-number selfRef">8.6. </a><a href="#name-cpnp-operations" class="section-name selfRef">CPNP Operations</a>
2328 </h3>
2329 <p id="section-8.6-1">CPNP operations are listed below. They may be augmented depending
2330 on the nature of some transactions or because of security
2331 considerations that may necessitate a distinct CPNP client/server
2332 authentication phase before negotiation begins.<a href="#section-8.6-1" class="pilcrow">¶</a></p>
2333 <span class="break"></span><dl class="dlNewline" id="section-8.6-2">
2334 <dt id="section-8.6-2.1">QUOTATION (<a href="#provision" class="xref">Section 9.2.1</a>): </dt>
2335 <dd style="margin-left: 1.5em" id="section-8.6-2.2">This operation is used by the client to initiate
2336 a PQO. Upon receipt of a QUOTATION
2337 request, the server may respond with a PROCESSING, OFFER, or a FAIL
2338 message. A QUOTATION-initiated transaction can be terminated by a
2339 FAIL message.<a href="#section-8.6-2.2" class="pilcrow">¶</a>
2340 </dd>
2341 <dd class="break"></dd>
2342 <dt id="section-8.6-2.3">PROCESSING (<a href="#proc" class="xref">Section 9.2.2</a>): </dt>
2343 <dd style="margin-left: 1.5em" id="section-8.6-2.4">This operation is used to inform the remote party
2344 that its message (the order quotation or the offer) was
2345 received and it is being processed. This message can also be issued by
2346 the server to request more time, in which case, the client may
2347 reply with an ACK or FAIL message depending on whether extra time
2348 can or cannot be granted.<a href="#section-8.6-2.4" class="pilcrow">¶</a>
2349 </dd>
2350 <dd class="break"></dd>
2351 <dt id="section-8.6-2.5">OFFER (<a href="#offer" class="xref">Section 9.2.3</a>): </dt>
2352 <dd style="margin-left: 1.5em" id="section-8.6-2.6">This operation is used by the server to inform
2353 the client about an offer that can best accommodate the
2354 requirements indicated in the previously received QUOTATION
2355 message.<a href="#section-8.6-2.6" class="pilcrow">¶</a>
2356 </dd>
2357 <dd class="break"></dd>
2358 <dt id="section-8.6-2.7">ACCEPT (<a href="#accept" class="xref">Section 9.2.4</a>): </dt>
2359 <dd style="margin-left: 1.5em" id="section-8.6-2.8">This operation is used by the client to confirm
2360 the acceptance of an offer made by the server. This message
2361 implies a call for agreement. An agreement is reached when an ACK
2362 is subsequently received from the server, which is likely to
2363 happen if the message is sent before the offer validity time
2364 expires; the server is unlikely to reject an offer that it has
2365 already made.<a href="#section-8.6-2.8" class="pilcrow">¶</a>
2366 </dd>
2367 <dd class="break"></dd>
2368 <dt id="section-8.6-2.9">DECLINE (<a href="#dec" class="xref">Section 9.2.5</a>): </dt>
2369 <dd style="margin-left: 1.5em" id="section-8.6-2.10">This operation is used by the client to reject an
2370 offer made by the server. The ongoing transaction may not be
2371 terminated immediately, e.g., the client may issue another order
2372 or the server may issue another offer.<a href="#section-8.6-2.10" class="pilcrow">¶</a>
2373 </dd>
2374 <dd class="break"></dd>
2375 <dt id="section-8.6-2.11">ACK (<a href="#ack" class="xref">Section 9.2.6</a>): </dt>
2376 <dd style="margin-left: 1.5em" id="section-8.6-2.12">This
2377 operation is used by the server to acknowledge the receipt of an
2378 ACCEPT or WITHDRAW message or by the client to confirm the server's
2379 request for a time extension (conveyed in a PROCESSING message)
2380 in order to process the last received quotation order.<a href="#section-8.6-2.12" class="pilcrow">¶</a>
2381 </dd>
2382 <dd class="break"></dd>
2383 <dt id="section-8.6-2.13">CANCEL (<a href="#cancel" class="xref">Section 9.2.7</a>): </dt>
2384 <dd style="margin-left: 1.5em" id="section-8.6-2.14">This operation is used by the client to cancel
2385 (quit) the ongoing transaction.<a href="#section-8.6-2.14" class="pilcrow">¶</a>
2386 </dd>
2387 <dd class="break"></dd>
2388 <dt id="section-8.6-2.15">WITHDRAW (<a href="#with" class="xref">Section 9.2.8</a>): </dt>
2389 <dd style="margin-left: 1.5em" id="section-8.6-2.16">This operation is used by the client to withdraw
2390 a completed order (i.e., an agreement).<a href="#section-8.6-2.16" class="pilcrow">¶</a>
2391 </dd>
2392 <dd class="break"></dd>
2393 <dt id="section-8.6-2.17">UPDATE (<a href="#upd" class="xref">Section 9.2.9</a>): </dt>
2394 <dd style="margin-left: 1.5em" id="section-8.6-2.18">This operation is used by the client to update an
2395 existing agreement. For example, this method can be invoked to add
2396 a new VPN site. This method will trigger a new negotiation
2397 cycle.<a href="#section-8.6-2.18" class="pilcrow">¶</a>
2398 </dd>
2399 <dd class="break"></dd>
2400 <dt id="section-8.6-2.19">FAIL (<a href="#fail" class="xref">Section 9.2.10</a>): </dt>
2401 <dd style="margin-left: 1.5em" id="section-8.6-2.20">
2402 <p id="section-8.6-2.20.1">This operation is used by the server to indicate
2403 that it cannot accommodate the requirements documented in the PQO
2404 conveyed in the QUOTATION message or to inform the client about an
2405 error encountered when processing the received message. In either
2406 case, the message implies that the server is unable to make offers,
2407 and, as a consequence, it terminates the ongoing transaction.<a href="#section-8.6-2.20.1" class="pilcrow">¶</a></p>
2408 <p id="section-8.6-2.20.2">This message is also used by the client
2409 to reject a time extension request in a PROCESSING message received
2410 from the server. The message includes a status code that
2411 provides explanatory information.<a href="#section-8.6-2.20.2" class="pilcrow">¶</a></p>
2412 </dd>
2413 <dd class="break"></dd>
2414 </dl>
2415 <p id="section-8.6-3">The above CPNP primitives are service independent. CPNP messages
2416 may transparently carry service-specific objects that are handled by
2417 the negotiation logic at either side.<a href="#section-8.6-3" class="pilcrow">¶</a></p>
2418 <p id="section-8.6-4">The document defines the service objects that are required for
2419 connectivity provisioning negotiation purposes
2420 (see <a href="#cpd" class="xref">Section 8.7</a>).
2421 Additional service-specific objects for CPNP messages to accommodate alternative
2422 deployment schemes or other service provisioning needs can be
2423 defined in the future.<a href="#section-8.6-4" class="pilcrow">¶</a></p>
2424 </section>
2425 <div id="cpd">
2426 <section id="section-8.7">
2427 <h3 id="name-connectivity-provisioning-d">
2428 <a href="#section-8.7" class="section-number selfRef">8.7. </a><a href="#name-connectivity-provisioning-d" class="section-name selfRef">Connectivity Provisioning Documents</a>
2429 </h3>
2430 <p id="section-8.7-1">CPNP makes use of several flavors of Connectivity Provisioning
2431 Documents (CPD). These documents follow the same CPP template
2432 described in <span>[<a href="#RFC7297" class="xref">RFC7297</a>]</span>.<a href="#section-8.7-1" class="pilcrow">¶</a></p>
2433 <span class="break"></span><dl class="dlNewline" id="section-8.7-2">
2434 <dt id="section-8.7-2.1">Requested CPD: </dt>
2435 <dd style="margin-left: 1.5em" id="section-8.7-2.2">Refers
2436 to the CPD included by a CPNP client in a QUOTATION request.<a href="#section-8.7-2.2" class="pilcrow">¶</a>
2437 </dd>
2438 <dd class="break"></dd>
2439 <dt id="section-8.7-2.3">Offered CPD: </dt>
2440 <dd style="margin-left: 1.5em" id="section-8.7-2.4">This
2441 document is included by a CPNP server in an OFFER message. Its
2442 information reflects the proposal of the server to accommodate all
2443 or a subset of the clauses depicted in a Requested CPD. A validity
2444 time is associated with the offer made.<a href="#section-8.7-2.4" class="pilcrow">¶</a>
2445 </dd>
2446 <dd class="break"></dd>
2447 <dt id="section-8.7-2.5">Accepted CPD: </dt>
2448 <dd style="margin-left: 1.5em" id="section-8.7-2.6">If
2449 the client accepts an offer made by the server, the Offered CPD is
2450 included in an ACCEPT message. This CPD is also included in an ACK
2451 message. Thus, a three-way handshake procedure is followed for
2452 successfully completing the negotiation.<a href="#section-8.7-2.6" class="pilcrow">¶</a>
2453 </dd>
2454 <dd class="break"></dd>
2455 </dl>
2456 <p id="section-8.7-3"><a href="#example" class="xref">Figure 6</a> shows a typical CPNP negotiation
2457 cycle and the use of the different types of CPDs.<a href="#section-8.7-3" class="pilcrow">¶</a></p>
2458 <span id="name-connectivity-provisioning-do"></span><div id="example">
2459 <figure id="figure-6">
2460 <div class="artwork art-text alignCenter" id="section-8.7-4.1">
2461 <pre>
2462 +------+ +------+
2463 |Client| |Server|
2464 +------+ +------+
2465 |======QUOTATION (Requested CPD)=====&gt;|
2466 |&lt;============PROCESSING==============|
2467 |&lt;========OFFER (Offered CPD)=========|
2468 |=============PROCESSING=============&gt;|
2469 |=======ACCEPT (Accepted CPD)========&gt;|
2470 |&lt;=======ACK (Accepted CPD)===========|
2471 | |
2472 </pre>
2473 </div>
2474 <figcaption><a href="#figure-6" class="selfRef">Figure 6</a>:
2475 <a href="#name-connectivity-provisioning-do" class="selfRef">Connectivity Provisioning Documents</a>
2476 </figcaption></figure>
2477 </div>
2478 <p id="section-8.7-5">A CPD can include parameters with fixed values,
2479 loosely defined values, or any combination thereof. A CPD
2480 is said to be concrete if all clauses have fixed values.<a href="#section-8.7-5" class="pilcrow">¶</a></p>
2481 <p id="section-8.7-6">A typical evolution of a negotiation cycle would start with a
2482 quotation order with loosely defined parameters, and then, as offers
2483 are made, it would conclude with a concrete CPD for
2484 calling for the agreement.<a href="#section-8.7-6" class="pilcrow">¶</a></p>
2485 </section>
2486 </div>
2487 <div id="cascaded">
2488 <section id="section-8.8">
2489 <h3 id="name-child-pqos">
2490 <a href="#section-8.8" class="section-number selfRef">8.8. </a><a href="#name-child-pqos" class="section-name selfRef">Child PQOs</a>
2491 </h3>
2492 <p id="section-8.8-1">If the server detects that network resources from another Network
2493 Provider need to be allocated in order to accommodate the requirements
2494 described in a PQO (e.g., in the context of an inter-domain VPN
2495 service, additional Provider Edge (PE) router resources need to be allocated), the
2496 server may generate child PQOs to request the appropriate network
2497 provisioning operations (see <a href="#child" class="xref">Figure 7</a>). In such a
2498 situation, the server also behaves as a CPNP client. The server
2499 associates the parent order with its child PQOs. How this is achieved
2500 is implementation specific (e.g., this can be typically achieved by
2501 locally adding the reference of the child PQO to the parent
2502 order).<a href="#section-8.8-1" class="pilcrow">¶</a></p>
2503 <span id="name-example-of-child-orders"></span><div id="child">
2504 <figure id="figure-7">
2505 <div class="artwork art-text alignCenter" id="section-8.8-2.1">
2506 <pre>
2507 +------+ +--------+ +--------+
2508 |Client| |Server A| |Server B|
2509 +------+ +--------+ +--------+
2510 | | |
2511 |=====QUOTATION=====&gt;| |
2512 |&lt;====PROCESSING=====| |
2513 | |=====QUOTATION=====&gt;|
2514 | |&lt;====PROCESSING=====|
2515 | |&lt;=======OFFER=======|
2516 | |=====PROCESSING====&gt;|
2517 | |=======ACCEPT======&gt;|
2518 | |&lt;=======ACK=========|
2519 |&lt;=======OFFER=======| |
2520 |=====PROCESSING====&gt;| |
2521 |=======ACCEPT======&gt;| |
2522 |&lt;=======ACK=========| |
2523 | | |
2524 </pre>
2525 </div>
2526 <figcaption><a href="#figure-7" class="selfRef">Figure 7</a>:
2527 <a href="#name-example-of-child-orders" class="selfRef">Example of Child Orders</a>
2528 </figcaption></figure>
2529 </div>
2530 <p id="section-8.8-3">Note that the server must not activate recursion for an
2531 order if the client includes a negotiation option to restrict the
2532 negotiation scope to the resources of the server's domain (<a href="#nego" class="xref">Section 9.1.10.3</a>).<a href="#section-8.8-3" class="pilcrow">¶</a></p>
2533 <p id="section-8.8-4">If recursion is not explicitly disabled, the server may notify the
2534 client when appropriate (<a href="#proc" class="xref">Section 9.2.2</a>). Such
2535 notification may depend on the nature of the service and also
2536 regulatory considerations.<a href="#section-8.8-4" class="pilcrow">¶</a></p>
2537 </section>
2538 </div>
2539 <section id="section-8.9">
2540 <h3 id="name-multi-segment-service">
2541 <a href="#section-8.9" class="section-number selfRef">8.9. </a><a href="#name-multi-segment-service" class="section-name selfRef">Multi-Segment Service</a>
2542 </h3>
2543 <p id="section-8.9-1">A composite service (e.g., connectivity) requested by a Customer
2544 could imply multi-segment services (e.g., multi-segment connectivity
2545 spanning an end-to-end scope), in the sense that one single CPNP
2546 request is decomposed into multiple connectivity requests on the Provider's
2547 side (thereby leading to child orders). The Provider is in charge of
2548 handling the complexity of splitting the generic provisioning order in
2549 a multi-segment context. Such complexity is local to the Provider.<a href="#section-8.9-1" class="pilcrow">¶</a></p>
2550 </section>
2551 <div id="mser">
2552 <section id="section-8.10">
2553 <h3 id="name-negotiating-with-multiple-c">
2554 <a href="#section-8.10" class="section-number selfRef">8.10. </a><a href="#name-negotiating-with-multiple-c" class="section-name selfRef">Negotiating with Multiple CPNP Servers</a>
2555 </h3>
2556 <p id="section-8.10-1">A CPNP client may undertake multiple negotiations in parallel with
2557 several servers for various reasons, such as cost optimization and
2558 fail-safety. These multiple negotiations may lead to one or many
2559 agreements.<a href="#section-8.10-1" class="pilcrow">¶</a></p>
2560 <p id="section-8.10-2">The salient point underlining the parallel negotiation scenarios is
2561 that, although the negotiation protocol is strictly between two
2562 parties, this may not be the case of the negotiation logic. The CPNP
2563 client negotiation logic may need to collectively drive parallel
2564 negotiations, as the negotiation with one server may affect the
2565 negotiation with other servers; for example, it may need to use the
2566 responses from all servers as an input for determining the messages
2567 (and their content) to subsequently send within the course of each
2568 individual negotiation. Therefore, timing is an important aspect on the
2569 client's side. The CPNP client needs to have the ability to
2570 synchronize the receipt of the responses from the servers. CPNP takes
2571 into account this requirement by allowing clients to specify in the
2572 QUOTATION message the time by which the server needs to respond (see
2573 <a href="#extime" class="xref">Section 9.1.6</a>).<a href="#section-8.10-2" class="pilcrow">¶</a></p>
2574 </section>
2575 </div>
2576 <section id="section-8.11">
2577 <h3 id="name-state-management">
2578 <a href="#section-8.11" class="section-number selfRef">8.11. </a><a href="#name-state-management" class="section-name selfRef">State Management</a>
2579 </h3>
2580 <p id="section-8.11-1">Both the client and the server maintain repositories to store
2581 ongoing orders. How these repositories are maintained is
2582 deployment specific. It is out of scope of this document to elaborate
2583 on such considerations. Timestamps are also logged to track state
2584 change. Tracking may be needed for various reasons, including
2585 regulatory or billing ones.<a href="#section-8.11-1" class="pilcrow">¶</a></p>
2586 <p id="section-8.11-2">In order to accommodate failures that may lead to the reboot of the
2587 client or the server, the use of permanent storage is recommended,
2588 thereby facilitating state recovery.<a href="#section-8.11-2" class="pilcrow">¶</a></p>
2589 <section id="section-8.11.1">
2590 <h4 id="name-on-the-client-side">
2591 <a href="#section-8.11.1" class="section-number selfRef">8.11.1. </a><a href="#name-on-the-client-side" class="section-name selfRef">On the Client Side</a>
2592 </h4>
2593 <p id="section-8.11.1-1">This is the list of the typical states that can be associated
2594 with a given order on the client's side:<a href="#section-8.11.1-1" class="pilcrow">¶</a></p>
2595 <span class="break"></span><dl class="dlParallel" id="section-8.11.1-2">
2596 <dt id="section-8.11.1-2.1">Created:</dt>
2597 <dd style="margin-left: 1.5em" id="section-8.11.1-2.2">The order has been created. It is not handled
2598 by the client until the administrator allows it to be processed.<a href="#section-8.11.1-2.2" class="pilcrow">¶</a>
2599 </dd>
2600 <dd class="break"></dd>
2601 <dt id="section-8.11.1-2.3">AwaitingProcessing:</dt>
2602 <dd style="margin-left: 1.5em" id="section-8.11.1-2.4">The administrator has approved the
2603 processing of a created order, but the order has not been handled
2604 yet.<a href="#section-8.11.1-2.4" class="pilcrow">¶</a>
2605 </dd>
2606 <dd class="break"></dd>
2607 <dt id="section-8.11.1-2.5">PQOSent:</dt>
2608 <dd style="margin-left: 1.5em" id="section-8.11.1-2.6"> The order has been sent to the server.<a href="#section-8.11.1-2.6" class="pilcrow">¶</a>
2609 </dd>
2610 <dd class="break"></dd>
2611 <dt id="section-8.11.1-2.7">ServerProcessing:</dt>
2612 <dd style="margin-left: 1.5em" id="section-8.11.1-2.8">The server has confirmed the receipt
2613 of the order.<a href="#section-8.11.1-2.8" class="pilcrow">¶</a>
2614 </dd>
2615 <dd class="break"></dd>
2616 <dt id="section-8.11.1-2.9">OfferReceived:</dt>
2617 <dd style="margin-left: 1.5em" id="section-8.11.1-2.10">An offer has been received from the
2618 server.<a href="#section-8.11.1-2.10" class="pilcrow">¶</a>
2619 </dd>
2620 <dd class="break"></dd>
2621 <dt id="section-8.11.1-2.11">OfferProcessing:</dt>
2622 <dd style="margin-left: 1.5em" id="section-8.11.1-2.12">A received offer is being processed
2623 by the client.<a href="#section-8.11.1-2.12" class="pilcrow">¶</a>
2624 </dd>
2625 <dd class="break"></dd>
2626 <dt id="section-8.11.1-2.13">AcceptSent:</dt>
2627 <dd style="margin-left: 1.5em" id="section-8.11.1-2.14">The client has confirmed the offer to the
2628 server.<a href="#section-8.11.1-2.14" class="pilcrow">¶</a>
2629 </dd>
2630 <dd class="break"></dd>
2631 <dt id="section-8.11.1-2.15">Completed:</dt>
2632 <dd style="margin-left: 1.5em" id="section-8.11.1-2.16">The offer has been acknowledged by the server.<a href="#section-8.11.1-2.16" class="pilcrow">¶</a>
2633 </dd>
2634 <dd class="break"></dd>
2635 <dt id="section-8.11.1-2.17">Cancelled:</dt>
2636 <dd style="margin-left: 1.5em" id="section-8.11.1-2.18">The order has failed or was cancelled.<a href="#section-8.11.1-2.18" class="pilcrow">¶</a>
2637 </dd>
2638 <dd class="break"></dd>
2639 </dl>
2640 <p id="section-8.11.1-3">Sub-states may be defined (e.g., to track failed vs. cancelled
2641 orders), but those are not shown in <a href="#clientstate" class="xref">Figure 8</a>.<a href="#section-8.11.1-3" class="pilcrow">¶</a></p>
2642 <span id="name-example-of-a-cpnp-finite-st"></span><div id="clientstate">
2643 <figure id="figure-8">
2644 <div class="artwork art-text alignCenter" id="section-8.11.1-4.1">
2645 <pre>
2646 +------------------+
2647 | Created |-----------------+
2648 +------------------+ |
2649 | |
2650 v |
2651 +------------------+ |
2652 |AwaitingProcessing|----------------+|
2653 +------------------+ ||
2654 | ||
2655 QUOTATION/UPDATE ||
2656 v ||
2657 +------------------+ ||
2658 | PQOSent |---CANCEL------+||
2659 +------------------+ vvv
2660 | +-----+
2661 PROCESSING | |
2662 v | |
2663 +------------------+ CANCEL | C |
2664 | ServerProcessing |------------&gt;| A |
2665 +------------------+ FAIL | N |
2666 | | C |
2667 | | E |
2668 OFFER | L |
2669 | | L |
2670 v | E |
2671 +------------------+ | D |
2672 | OfferReceived |---CANCEL---&gt;| |
2673 +------------------+ | |
2674 | PROCESSING +-----+
2675 v ^^^
2676 +------------------+ |||
2677 | OfferProcessing |---DECLINE-----+||
2678 +------------------+ ||
2679 | ACCEPT ||
2680 v ||
2681 +------------------+ ||
2682 | AcceptSent |---CANCEL-------+|
2683 +------------------+ |
2684 | ACK |
2685 v |
2686 +------------------+ |
2687 | Completed |---WITHDRAW------+
2688 +------------------+
2689 </pre>
2690 </div>
2691 <figcaption><a href="#figure-8" class="selfRef">Figure 8</a>:
2692 <a href="#name-example-of-a-cpnp-finite-st" class="selfRef">Example of a CPNP Finite State Machine (Client Side)</a>
2693 </figcaption></figure>
2694 </div>
2695 </section>
2696 <section id="section-8.11.2">
2697 <h4 id="name-on-the-server-side">
2698 <a href="#section-8.11.2" class="section-number selfRef">8.11.2. </a><a href="#name-on-the-server-side" class="section-name selfRef">On the Server Side</a>
2699 </h4>
2700 <p id="section-8.11.2-1">The following lists the states on the server's side that can be associated with a
2701 given order and a corresponding offer:<a href="#section-8.11.2-1" class="pilcrow">¶</a></p>
2702 <span class="break"></span><dl class="dlParallel" id="section-8.11.2-2">
2703 <dt id="section-8.11.2-2.1">PQOReceived:</dt>
2704 <dd style="margin-left: 1.5em" id="section-8.11.2-2.2">The order has been received from the
2705 client.<a href="#section-8.11.2-2.2" class="pilcrow">¶</a>
2706 </dd>
2707 <dd class="break"></dd>
2708 <dt id="section-8.11.2-2.3">AwaitingProcessing: </dt>
2709 <dd style="margin-left: 1.5em" id="section-8.11.2-2.4">The order is being processed by the
2710 server. An action from the server administrator may be
2711 needed.<a href="#section-8.11.2-2.4" class="pilcrow">¶</a>
2712 </dd>
2713 <dd class="break"></dd>
2714 <dt id="section-8.11.2-2.5">OfferProposed:</dt>
2715 <dd style="margin-left: 1.5em" id="section-8.11.2-2.6">The request has been successfully handled,
2716 and an offer has been sent to the client.<a href="#section-8.11.2-2.6" class="pilcrow">¶</a>
2717 </dd>
2718 <dd class="break"></dd>
2719 <dt id="section-8.11.2-2.7">ProcessingReceived:</dt>
2720 <dd style="margin-left: 1.5em" id="section-8.11.2-2.8">The server has received a PROCESSING message for
2721 an offer sent to the client.<a href="#section-8.11.2-2.8" class="pilcrow">¶</a>
2722 </dd>
2723 <dd class="break"></dd>
2724 <dt id="section-8.11.2-2.9">AcceptReceived:</dt>
2725 <dd style="margin-left: 1.5em" id="section-8.11.2-2.10">The server has received a confirmation for
2726 the offer from the client.<a href="#section-8.11.2-2.10" class="pilcrow">¶</a>
2727 </dd>
2728 <dd class="break"></dd>
2729 <dt id="section-8.11.2-2.11">Completed:</dt>
2730 <dd style="margin-left: 1.5em" id="section-8.11.2-2.12">The server has acknowledged the offer (accepted
2731 by client) to the client. Transitioning to this state assumes
2732 that the ACK was received by the client (this can be detected by
2733 the server if it receives a retransmitted ACCEPT message from the
2734 client).<a href="#section-8.11.2-2.12" class="pilcrow">¶</a>
2735 </dd>
2736 <dd class="break"></dd>
2737 <dt id="section-8.11.2-2.13">Cancelled:</dt>
2738 <dd style="margin-left: 1.5em" id="section-8.11.2-2.14">The order cannot be accommodated, or it has
2739 been cancelled by the client. Associated resources must be
2740 released in the latter case, if previously reserved.<a href="#section-8.11.2-2.14" class="pilcrow">¶</a>
2741 </dd>
2742 <dd class="break"></dd>
2743 <dt id="section-8.11.2-2.15">ChildCreated:</dt>
2744 <dd style="margin-left: 1.5em" id="section-8.11.2-2.16">A child order has been created in cases
2745 where resources from another Network Provider are needed.<a href="#section-8.11.2-2.16" class="pilcrow">¶</a>
2746 </dd>
2747 <dd class="break"></dd>
2748 <dt id="section-8.11.2-2.17">ChildPQOSent:</dt>
2749 <dd style="margin-left: 1.5em" id="section-8.11.2-2.18">A child order has been sent to the remote
2750 server.<a href="#section-8.11.2-2.18" class="pilcrow">¶</a>
2751 </dd>
2752 <dd class="break"></dd>
2753 <dt id="section-8.11.2-2.19">ChildServerProcessing:</dt>
2754 <dd style="margin-left: 1.5em" id="section-8.11.2-2.20">A child order is being
2755 processed by the remote server.<a href="#section-8.11.2-2.20" class="pilcrow">¶</a>
2756 </dd>
2757 <dd class="break"></dd>
2758 <dt id="section-8.11.2-2.21">ChildOfferReceived:</dt>
2759 <dd style="margin-left: 1.5em" id="section-8.11.2-2.22"> The remote server has received an offer to a
2760 child order.<a href="#section-8.11.2-2.22" class="pilcrow">¶</a>
2761 </dd>
2762 <dd class="break"></dd>
2763 <dt id="section-8.11.2-2.23">ChildOfferProcessing:</dt>
2764 <dd style="margin-left: 1.5em" id="section-8.11.2-2.24"> A received offer to a child order
2765 is being processed.<a href="#section-8.11.2-2.24" class="pilcrow">¶</a>
2766 </dd>
2767 <dd class="break"></dd>
2768 <dt id="section-8.11.2-2.25">ChildAcceptSent: </dt>
2769 <dd style="margin-left: 1.5em" id="section-8.11.2-2.26">The child offer (the offer received from
2770 the remote server in response to a child order) is confirmed to
2771 the remote server.<a href="#section-8.11.2-2.26" class="pilcrow">¶</a>
2772 </dd>
2773 <dd class="break"></dd>
2774 <dt id="section-8.11.2-2.27">ChildCompleted:</dt>
2775 <dd style="margin-left: 1.5em" id="section-8.11.2-2.28"> The accepted child offer has been acknowledged
2776 by the remote server.<a href="#section-8.11.2-2.28" class="pilcrow">¶</a>
2777 </dd>
2778 <dd class="break"></dd>
2779 </dl>
2780 <span id="name-cpnp-finite-state-machine-s"></span><div id="serverstate">
2781 <figure id="figure-9">
2782 <div class="artwork art-text alignCenter" id="section-8.11.2-3.1">
2783 <pre>
2784 +------------------+ +------------------+
2785 |AwaitingProcessing|&lt;----------| ChildCreated |
2786 +------------------+ +------------------+
2787 | | ^
2788 v | |
2789 +------------------+ | |
2790 | ChildPQOSent |----------------+| Q
2791 +------------------+ || U
2792 | || O
2793 QUOTATION/UPDATE || T
2794 v || A +--------------------+
2795 +---------------------+ CANCEL || T | PQOReceived |
2796 |ChildServerProcessing|------------+|| I +--------------------+
2797 +---------------------+ FAIL vvv O | |
2798 | +-----+ N CANCEL |
2799 PROCESSING | |&lt;---|-------+ PROCESSING
2800 v | | | v
2801 +------------------+ | | +------------------------+
2802 |ChildOfferReceived|----CANCEL---| C |&lt;--| AwaitingProcessing |
2803 +------------------+ | A | +------------------------+
2804 | | N | ^ | OFFER
2805 OFFER | C | | +------------------+
2806 | | E |&lt;DECLINE-| OfferProposed |
2807 | | L | | +------------------+
2808 v | L | | |
2809 +------------------+ | E | | PROCESSING
2810 |ChildOfferReceived|---CANCEL----| D | | v
2811 +------------------+ | | | +------------------+
2812 | | |&lt;DECLINE-| Proc'ingReceived |
2813 PROCESSING | | |+------------------+
2814 | +-----+ | | ACCEPT
2815 v ^^^^^ | v
2816 +------------------+ ||||| | +------------------+
2817 |ChildOfferProc'ing|---DECLINE----+|||+-CANCEL-|-| AcceptReceived |
2818 +------------------+ ||| | +------------------+
2819 |ACCEPT ||| | |ACK
2820 v ||| | v
2821 +------------------+ ||| | +------------------+
2822 | ChildAcceptSent |---CANCEL------+|+-WITHDRAW|-| Completed |
2823 +------------------+ | | +------------------+
2824 | ACK | |
2825 v | |
2826 +------------------+ | |
2827 | ChildCompleted |---WITHDRAW-----+ |
2828 | +---------------------------+
2829 +------------------+
2830 </pre>
2831 </div>
2832 <figcaption><a href="#figure-9" class="selfRef">Figure 9</a>:
2833 <a href="#name-cpnp-finite-state-machine-s" class="selfRef">CPNP Finite State Machine (Server Side)</a>
2834 </figcaption></figure>
2835 </div>
2836 </section>
2837 </section>
2838 </section>
2839 </div>
2840 <div id="co">
2841 <section id="section-9">
2842 <h2 id="name-cpnp-objects">
2843 <a href="#section-9" class="section-number selfRef">9. </a><a href="#name-cpnp-objects" class="section-name selfRef">CPNP Objects</a>
2844 </h2>
2845 <p id="section-9-1">This section defines CPNP objects using the Routing Backus-Naur Form (RBNF) format defined in
2846 <span>[<a href="#RFC5511" class="xref">RFC5511</a>]</span>. Please also note the
2847 following:<a href="#section-9-1" class="pilcrow">¶</a></p>
2848 <aside id="section-9-2">
2849 <p id="section-9-2.1">Note 1: The formats of CPNP messages are provided using a generic
2850 format. Implementors can adapt RBNF definitions to their "favorite"
2851 message format. For example, JSON <span>[<a href="#RFC8259" class="xref">RFC8259</a>]</span> or
2852 Concise Binary Object Representation (CBOR) <span>[<a href="#RFC7049" class="xref">RFC7049</a>]</span> can be used.<a href="#section-9-2.1" class="pilcrow">¶</a></p>
2853 </aside>
2854 <aside id="section-9-3">
2855 <p id="section-9-3.1">Note 2: CPNP messages cannot be blindly mapped to RESTCONF
2856 messages with the target service being modelled as configuration
2857 data because such data is supposed to be manipulated by a RESTCONF
2858 client only. In such a model, the RESTCONF server cannot use a value
2859 other than the one set by the client (e.g., <a href="#offer" class="xref">Section 9.2.3</a>)
2860 or remove offers from its own initiative
2861 (e.g., <a href="#valtime" class="xref">Section 9.1.8</a>). An alternate approach might
2862 be to map CPNP operations into RESTCONF actions (RPC). Assessing the
2863 feasibility of such approach is out of scope.<a href="#section-9-3.1" class="pilcrow">¶</a></p>
2864 </aside>
2865 <section id="section-9.1">
2866 <h3 id="name-attributes">
2867 <a href="#section-9.1" class="section-number selfRef">9.1. </a><a href="#name-attributes" class="section-name selfRef">Attributes</a>
2868 </h3>
2869 <div id="cu_id">
2870 <section id="section-9.1.1">
2871 <h4 id="name-customer_order_identifier">
2872 <a href="#section-9.1.1" class="section-number selfRef">9.1.1. </a><a href="#name-customer_order_identifier" class="section-name selfRef">CUSTOMER_ORDER_IDENTIFIER</a>
2873 </h4>
2874 <p id="section-9.1.1-1">The CUSTOMER_ORDER_IDENTIFIER (Customer Order Identifier) is an identifier that is assigned
2875 by a client to identify an agreement. This identifier must be unique
2876 to the client.<a href="#section-9.1.1-1" class="pilcrow">¶</a></p>
2877 <p id="section-9.1.1-2">Rules for assigning this identifier (including the structure and
2878 semantics) are specific to the client (Customer). The value of
2879 CUSTOMER_ORDER_IDENTIFIER is included in all CPNP messages.<a href="#section-9.1.1-2" class="pilcrow">¶</a></p>
2880 <p id="section-9.1.1-3">The client (Customer) assigns an identifier to an order under
2881 negotiation before an agreement is reached. This identifier will be
2882 used to unambiguously identify the resulting agreement at the client
2883 side (Customer).<a href="#section-9.1.1-3" class="pilcrow">¶</a></p>
2884 <p id="section-9.1.1-4">The server handles the CUSTOMER_ORDER_IDENTIFIER as an opaque
2885 value.<a href="#section-9.1.1-4" class="pilcrow">¶</a></p>
2886 </section>
2887 </div>
2888 <div id="pr_id">
2889 <section id="section-9.1.2">
2890 <h4 id="name-provider_order_identifier">
2891 <a href="#section-9.1.2" class="section-number selfRef">9.1.2. </a><a href="#name-provider_order_identifier" class="section-name selfRef">PROVIDER_ORDER_IDENTIFIER</a>
2892 </h4>
2893 <p id="section-9.1.2-1">The PROVIDER_ORDER_IDENTIFIER (Provider Order Identifier) is an identifier that is assigned
2894 by a server to identify an order. This identifier must be unique to
2895 the server.<a href="#section-9.1.2-1" class="pilcrow">¶</a></p>
2896 <p id="section-9.1.2-2">Rules for assigning this identifier (including the structure and
2897 semantics) are specific to the server (Provider).
2898 The PROVIDER_ORDER_IDENTIFIER is included in all CPNP messages
2899 except QUOTATION messages (because the state is only present at the
2900 client side).<a href="#section-9.1.2-2" class="pilcrow">¶</a></p>
2901 <p id="section-9.1.2-3">The server (Provider) assigns an identifier to an order under
2902 negotiation before an agreement is reached. This identifier will be
2903 used to unambiguously identify the resulting agreement at the server
2904 side (Provider).<a href="#section-9.1.2-3" class="pilcrow">¶</a></p>
2905 <p id="section-9.1.2-4">The client handles the PROVIDER_ORDER_IDENTIFIER as an opaque
2906 value.<a href="#section-9.1.2-4" class="pilcrow">¶</a></p>
2907 </section>
2908 </div>
2909 <div id="trans_id">
2910 <section id="section-9.1.3">
2911 <h4 id="name-transaction_id">
2912 <a href="#section-9.1.3" class="section-number selfRef">9.1.3. </a><a href="#name-transaction_id" class="section-name selfRef">TRANSACTION_ID</a>
2913 </h4>
2914 <p id="section-9.1.3-1">This object conveys the Transaction-ID introduced in <a href="#trans" class="xref">Section 8.4</a>.<a href="#section-9.1.3-1" class="pilcrow">¶</a></p>
2915 </section>
2916 </div>
2917 <section id="section-9.1.4">
2918 <h4 id="name-sequence_number">
2919 <a href="#section-9.1.4" class="section-number selfRef">9.1.4. </a><a href="#name-sequence_number" class="section-name selfRef">SEQUENCE_NUMBER</a>
2920 </h4>
2921 <p id="section-9.1.4-1">The sequence number is a number that is monotonically incremented in
2922 every new CPNP message pertaining to a given CPNP transaction. This
2923 number is used to avoid replay attacks.<a href="#section-9.1.4-1" class="pilcrow">¶</a></p>
2924 <p id="section-9.1.4-2">Refer to <a href="#sq_nu" class="xref">Section 11.3</a>.<a href="#section-9.1.4-2" class="pilcrow">¶</a></p>
2925 </section>
2926 <section id="section-9.1.5">
2927 <h4 id="name-nonce">
2928 <a href="#section-9.1.5" class="section-number selfRef">9.1.5. </a><a href="#name-nonce" class="section-name selfRef">NONCE</a>
2929 </h4>
2930 <p id="section-9.1.5-1">The NONCE is a random value assigned by the CPNP server.
2931 Assigning a unique NONCE value for each order is recommended.<a href="#section-9.1.5-1" class="pilcrow">¶</a></p>
2932 <p id="section-9.1.5-2">It is mandatory to then include the NONCE in subsequent CPNP client
2933 operations on the associated order (including the resulting
2934 agreement) such as withdrawing the order or updating the order.<a href="#section-9.1.5-2" class="pilcrow">¶</a></p>
2935 <p id="section-9.1.5-3">If the NONCE validation checks fail, the server rejects the
2936 request with a FAIL message that includes the appropriate failure reason
2937 code.<a href="#section-9.1.5-3" class="pilcrow">¶</a></p>
2938 </section>
2939 <div id="extime">
2940 <section id="section-9.1.6">
2941 <h4 id="name-expected_response_time">
2942 <a href="#section-9.1.6" class="section-number selfRef">9.1.6. </a><a href="#name-expected_response_time" class="section-name selfRef">EXPECTED_RESPONSE_TIME</a>
2943 </h4>
2944 <p id="section-9.1.6-1">This attribute indicates the time by when the CPNP client is
2945 expecting to receive a response from the CPNP server to a given PQO.
2946 If no offer is received by then, the CPNP client will consider the
2947 quotation order to be rejected.<a href="#section-9.1.6-1" class="pilcrow">¶</a></p>
2948 <p id="section-9.1.6-2">The EXPECTED_RESPONSE_TIME follows the date format specified in <span>[<a href="#RFC3339" class="xref">RFC3339</a>]</span>.<a href="#section-9.1.6-2" class="pilcrow">¶</a></p>
2949 </section>
2950 </div>
2951 <div id="EXPECTED_OFFER_TIME">
2952 <section id="section-9.1.7">
2953 <h4 id="name-expected_offer_time">
2954 <a href="#section-9.1.7" class="section-number selfRef">9.1.7. </a><a href="#name-expected_offer_time" class="section-name selfRef">EXPECTED_OFFER_TIME</a>
2955 </h4>
2956 <p id="section-9.1.7-1">This attribute indicates the time by when the CPNP server is
2957 expecting to make an offer to the CPNP client. If no offer is
2958 received by then, the CPNP client will consider the order
2959 rejected.<a href="#section-9.1.7-1" class="pilcrow">¶</a></p>
2960 <p id="section-9.1.7-2">The CPNP server may propose an expected offer time that does not
2961 match the expected response time indicated in the quotation order
2962 message. The CPNP client can accept or reject the proposed expected
2963 time by when the CPNP server will make an offer.<a href="#section-9.1.7-2" class="pilcrow">¶</a></p>
2964 <p id="section-9.1.7-3">The CPNP server can always request extra time for its processing,
2965 but this may be accepted or rejected by the CPNP client.<a href="#section-9.1.7-3" class="pilcrow">¶</a></p>
2966 <p id="section-9.1.7-4">The EXPECTED_OFFER_TIME follows the date format specified in <span>[<a href="#RFC3339" class="xref">RFC3339</a>]</span>.<a href="#section-9.1.7-4" class="pilcrow">¶</a></p>
2967 </section>
2968 </div>
2969 <div id="valtime">
2970 <section id="section-9.1.8">
2971 <h4 id="name-validity_offer_time">
2972 <a href="#section-9.1.8" class="section-number selfRef">9.1.8. </a><a href="#name-validity_offer_time" class="section-name selfRef">VALIDITY_OFFER_TIME</a>
2973 </h4>
2974 <p id="section-9.1.8-1">This attribute indicates the time of validity of an offer made by
2975 the CPNP server. If the offer is not accepted before this time
2976 expires, the CPNP server will consider the CPNP client as having rejected
2977 the offer; the CPNP server will silently remove this order from its
2978 base.<a href="#section-9.1.8-1" class="pilcrow">¶</a></p>
2979 <p id="section-9.1.8-2">The VALIDITY_OFFER_TIME follows date format specified in <span>[<a href="#RFC3339" class="xref">RFC3339</a>]</span>.<a href="#section-9.1.8-2" class="pilcrow">¶</a></p>
2980 </section>
2981 </div>
2982 <div id="service_template">
2983 <section id="section-9.1.9">
2984 <h4 id="name-service_description">
2985 <a href="#section-9.1.9" class="section-number selfRef">9.1.9. </a><a href="#name-service_description" class="section-name selfRef">SERVICE_DESCRIPTION</a>
2986 </h4>
2987 <p id="section-9.1.9-1">This document defines a machinery to negotiate any aspect subject
2988 to negotiation. Service clauses that are under negotiation are
2989 conveyed using this attribute.<a href="#section-9.1.9-1" class="pilcrow">¶</a></p>
2990 <p id="section-9.1.9-2">The structure of the connectivity provisioning clauses is
2991 provided in the following subsection.<a href="#section-9.1.9-2" class="pilcrow">¶</a></p>
2992 <div id="cpd_template">
2993 <section id="section-9.1.9.1">
2994 <h5 id="name-cpd">
2995 <a href="#section-9.1.9.1" class="section-number selfRef">9.1.9.1. </a><a href="#name-cpd" class="section-name selfRef">CPD</a>
2996 </h5>
2997 <p id="section-9.1.9.1-1">The RBNF format of the CPD
2998 is shown in <a href="#rbnf_cpd" class="xref">Figure 10</a>.<a href="#section-9.1.9.1-1" class="pilcrow">¶</a></p>
2999 <span id="name-the-rbnf-format-of-the-cpd"></span><div id="rbnf_cpd">
3000 <figure id="figure-10">
3001 <div id="section-9.1.9.1-2.1">
3002 <pre class="sourcecode lang-rbnf">
3003 &lt;CPD&gt; ::= &lt;Connectivity Provisioning Component&gt; ...
3004 &lt;Connectivity Provisioning Component&gt; ::=
3005 &lt;CONNECTIVITY_PROVISIONING_PROFILE&gt; ...
3006 &lt;CONNECTIVITY_PROVISIONING_PROFILE&gt; ::=
3007 &lt;Customer Nodes Map&gt;
3008 &lt;SCOPE&gt;
3009 &lt;QoS Guarantees&gt;
3010 &lt;Availability&gt;
3011 &lt;CAPACITY&gt;
3012 &lt;Traffic Isolation&gt;
3013 &lt;Conformance Traffic&gt;
3014 &lt;Flow Identification&gt;
3015 &lt;Overall Traffic Guarantees&gt;
3016 &lt;Routing and Forwarding&gt;
3017 &lt;Activation Means&gt;
3018 &lt;Invocation Means&gt;
3019 &lt;Notifications&gt;
3020 &lt;Customer Nodes Map&gt; ::= &lt;Customer Node&gt; ...
3021 &lt;Customer Node&gt; ::= &lt;IDENTIFIER&gt;
3022 &lt;LINK_IDENTIFIER&gt;
3023 &lt;LOCALIZATION&gt;
3024 </pre>
3025 </div>
3026 <figcaption><a href="#figure-10" class="selfRef">Figure 10</a>:
3027 <a href="#name-the-rbnf-format-of-the-cpd" class="selfRef">The RBNF format of the CPD</a>
3028 </figcaption></figure>
3029 </div>
3030 </section>
3031 </div>
3032 </section>
3033 </div>
3034 <section id="section-9.1.10">
3035 <h4 id="name-cpnp-information-elements">
3036 <a href="#section-9.1.10" class="section-number selfRef">9.1.10. </a><a href="#name-cpnp-information-elements" class="section-name selfRef">CPNP Information Elements</a>
3037 </h4>
3038 <p id="section-9.1.10-1">An Information Element (IE) is an optional object that can be
3039 included in a CPNP message.<a href="#section-9.1.10-1" class="pilcrow">¶</a></p>
3040 <section id="section-9.1.10.1">
3041 <h5 id="name-customer-description">
3042 <a href="#section-9.1.10.1" class="section-number selfRef">9.1.10.1. </a><a href="#name-customer-description" class="section-name selfRef">Customer Description</a>
3043 </h5>
3044 <p id="section-9.1.10.1-1">The client may include administrative information such
3045 as the following:<a href="#section-9.1.10.1-1" class="pilcrow">¶</a></p>
3046 <ul class="normal">
3047 <li class="normal" id="section-9.1.10.1-2.1">Name<a href="#section-9.1.10.1-2.1" class="pilcrow">¶</a>
3048 </li>
3049 <li class="normal" id="section-9.1.10.1-2.2">Contact Information<a href="#section-9.1.10.1-2.2" class="pilcrow">¶</a>
3050 </li>
3051 </ul>
3052 <p id="section-9.1.10.1-3">The format of this Information Element is as follows:<a href="#section-9.1.10.1-3" class="pilcrow">¶</a></p>
3053 <div id="section-9.1.10.1-4">
3054 <pre class="sourcecode lang-rbnf">
3055 &lt;Customer Description&gt; ::= [&lt;NAME&gt;] [&lt;Contact Information&gt;]
3056 &lt;Contact Information&gt; ::= [&lt;EMAIL_ADDRESS&gt;] [&lt;POSTAL_ADDRESS&gt;]
3057 [&lt;TELEPHONE_NUMBER&gt; ...]
3058 </pre><a href="#section-9.1.10.1-4" class="pilcrow">¶</a>
3059 </div>
3060 </section>
3061 <section id="section-9.1.10.2">
3062 <h5 id="name-provider-description">
3063 <a href="#section-9.1.10.2" class="section-number selfRef">9.1.10.2. </a><a href="#name-provider-description" class="section-name selfRef">Provider Description</a>
3064 </h5>
3065 <p id="section-9.1.10.2-1">The server may include administrative information in an offer
3066 such as the following:<a href="#section-9.1.10.2-1" class="pilcrow">¶</a></p>
3067 <ul class="normal">
3068 <li class="normal" id="section-9.1.10.2-2.1">Name<a href="#section-9.1.10.2-2.1" class="pilcrow">¶</a>
3069 </li>
3070 <li class="normal" id="section-9.1.10.2-2.2">AS Number <span>[<a href="#RFC6793" class="xref">RFC6793</a>]</span><a href="#section-9.1.10.2-2.2" class="pilcrow">¶</a>
3071 </li>
3072 <li class="normal" id="section-9.1.10.2-2.3">Contact Information<a href="#section-9.1.10.2-2.3" class="pilcrow">¶</a>
3073 </li>
3074 </ul>
3075 <p id="section-9.1.10.2-3">The format of this Information Element is as follows:<a href="#section-9.1.10.2-3" class="pilcrow">¶</a></p>
3076 <div id="section-9.1.10.2-4">
3077 <pre class="sourcecode lang-rbnf">
3078 &lt;Provider Description&gt; ::= [&lt;NAME&gt;][&lt;Contact Information&gt;]
3079 [&lt;AS_NUMBER&gt;]
3080 </pre><a href="#section-9.1.10.2-4" class="pilcrow">¶</a>
3081 </div>
3082 </section>
3083 <div id="nego">
3084 <section id="section-9.1.10.3">
3085 <h5 id="name-negotiation-options">
3086 <a href="#section-9.1.10.3" class="section-number selfRef">9.1.10.3. </a><a href="#name-negotiation-options" class="section-name selfRef">Negotiation Options</a>
3087 </h5>
3088 <p id="section-9.1.10.3-1">The client may include some negotiation options such as the following:<a href="#section-9.1.10.3-1" class="pilcrow">¶</a></p>
3089 <span class="break"></span><dl class="dlParallel" id="section-9.1.10.3-2">
3090 <dt id="section-9.1.10.3-2.1">Setup purpose:</dt>
3091 <dd style="margin-left: 1.5em" id="section-9.1.10.3-2.2">A client may request the setup of a service
3092 (e.g., connectivity) only for testing purposes during a
3093 limited period. The order can be extended to become permanent
3094 if the client was satisfied during the test period. This
3095 operation is achieved using the UPDATE method.<a href="#section-9.1.10.3-2.2" class="pilcrow">¶</a>
3096 </dd>
3097 <dd class="break"></dd>
3098 <dt id="section-9.1.10.3-2.3">Activation type:</dt>
3099 <dd style="margin-left: 1.5em" id="section-9.1.10.3-2.4"> A client may request a permanent or
3100 scheduled activation type. If no activation type clause is
3101 included during the negotiation, this means that the order
3102 will be immediately activated right after the negotiation
3103 ends.<a href="#section-9.1.10.3-2.4" class="pilcrow">¶</a>
3104 </dd>
3105 <dd class="break"></dd>
3106 </dl>
3107 <p id="section-9.1.10.3-3">The format of this Information Element is as follows:<a href="#section-9.1.10.3-3" class="pilcrow">¶</a></p>
3108 <div id="section-9.1.10.3-4">
3109 <pre class="sourcecode lang-rbnf">
3110 &lt;Negotiation Options&gt; ::= [&lt;PURPOSE&gt;]
3111 </pre><a href="#section-9.1.10.3-4" class="pilcrow">¶</a>
3112 </div>
3113 </section>
3114 </div>
3115 </section>
3116 </section>
3117 <section id="section-9.2">
3118 <h3 id="name-operation-messages">
3119 <a href="#section-9.2" class="section-number selfRef">9.2. </a><a href="#name-operation-messages" class="section-name selfRef">Operation Messages</a>
3120 </h3>
3121 <p id="section-9.2-1">This section defines the RBNF format of CPNP operation messages.
3122 The following operation codes are used:<a href="#section-9.2-1" class="pilcrow">¶</a></p>
3123 <span id="name-cpnp-operation-message-code"></span><table class="left" id="table-1">
3124 <caption>
3125 <a href="#table-1" class="selfRef">Table 1</a>:
3126 <a href="#name-cpnp-operation-message-code" class="selfRef">CPNP Operation Message Codes</a>
3127 </caption>
3128 <thead>
3129 <tr>
3130 <th class="text-left" rowspan="1" colspan="1">Code</th>
3131 <th class="text-left" rowspan="1" colspan="1">Operation Message</th>
3132 <th class="text-left" rowspan="1" colspan="1">Reference</th>
3133 </tr>
3134 </thead>
3135 <tbody>
3136 <tr>
3137 <td class="text-left" rowspan="1" colspan="1">1</td>
3138 <td class="text-left" rowspan="1" colspan="1">QUOTATION</td>
3139 <td class="text-left" rowspan="1" colspan="1">
3140 <a href="#provision" class="xref">Section 9.2.1</a>
3141 </td>
3142 </tr>
3143 <tr>
3144 <td class="text-left" rowspan="1" colspan="1">2</td>
3145 <td class="text-left" rowspan="1" colspan="1">PROCESSING</td>
3146 <td class="text-left" rowspan="1" colspan="1">
3147 <a href="#proc" class="xref">Section 9.2.2</a>
3148 </td>
3149 </tr>
3150 <tr>
3151 <td class="text-left" rowspan="1" colspan="1">3</td>
3152 <td class="text-left" rowspan="1" colspan="1">OFFER</td>
3153 <td class="text-left" rowspan="1" colspan="1">
3154 <a href="#offer" class="xref">Section 9.2.3</a>
3155 </td>
3156 </tr>
3157 <tr>
3158 <td class="text-left" rowspan="1" colspan="1">4</td>
3159 <td class="text-left" rowspan="1" colspan="1">ACCEPT</td>
3160 <td class="text-left" rowspan="1" colspan="1">
3161 <a href="#accept" class="xref">Section 9.2.4</a>
3162 </td>
3163 </tr>
3164 <tr>
3165 <td class="text-left" rowspan="1" colspan="1">5</td>
3166 <td class="text-left" rowspan="1" colspan="1">DECLINE</td>
3167 <td class="text-left" rowspan="1" colspan="1">
3168 <a href="#dec" class="xref">Section 9.2.5</a>
3169 </td>
3170 </tr>
3171 <tr>
3172 <td class="text-left" rowspan="1" colspan="1">6</td>
3173 <td class="text-left" rowspan="1" colspan="1">ACK</td>
3174 <td class="text-left" rowspan="1" colspan="1">
3175 <a href="#ack" class="xref">Section 9.2.6</a>
3176 </td>
3177 </tr>
3178 <tr>
3179 <td class="text-left" rowspan="1" colspan="1">7</td>
3180 <td class="text-left" rowspan="1" colspan="1">CANCEL</td>
3181 <td class="text-left" rowspan="1" colspan="1">
3182 <a href="#cancel" class="xref">Section 9.2.7</a>
3183 </td>
3184 </tr>
3185 <tr>
3186 <td class="text-left" rowspan="1" colspan="1">8</td>
3187 <td class="text-left" rowspan="1" colspan="1">WITHDRAW</td>
3188 <td class="text-left" rowspan="1" colspan="1">
3189 <a href="#with" class="xref">Section 9.2.8</a>
3190 </td>
3191 </tr>
3192 <tr>
3193 <td class="text-left" rowspan="1" colspan="1">9</td>
3194 <td class="text-left" rowspan="1" colspan="1">UPDATE</td>
3195 <td class="text-left" rowspan="1" colspan="1">
3196 <a href="#upd" class="xref">Section 9.2.9</a>
3197 </td>
3198 </tr>
3199 <tr>
3200 <td class="text-left" rowspan="1" colspan="1">10</td>
3201 <td class="text-left" rowspan="1" colspan="1">FAIL</td>
3202 <td class="text-left" rowspan="1" colspan="1">
3203 <a href="#fail" class="xref">Section 9.2.10</a>
3204 </td>
3205 </tr>
3206 <tr>
3207 <td class="text-left" rowspan="1" colspan="1">11</td>
3208 <td class="text-left" rowspan="1" colspan="1">ACTIVATE</td>
3209 <td class="text-left" rowspan="1" colspan="1">
3210 <a href="#activate" class="xref">Section 9.2.11</a>
3211 </td>
3212 </tr>
3213 </tbody>
3214 </table>
3215 <p id="section-9.2-3">These codes are used to unambiguously identify a CPNP operation;
3216 the operation code is conveyed in the METHOD_CODE attribute
3217 mentioned in the following subsections.<a href="#section-9.2-3" class="pilcrow">¶</a></p>
3218 <p id="section-9.2-4">In the following, VERSION refers to the CPNP version number. This
3219 attribute must be set to 1.<a href="#section-9.2-4" class="pilcrow">¶</a></p>
3220 <div id="provision">
3221 <section id="section-9.2.1">
3222 <h4 id="name-quotation">
3223 <a href="#section-9.2.1" class="section-number selfRef">9.2.1. </a><a href="#name-quotation" class="section-name selfRef">QUOTATION</a>
3224 </h4>
3225 <p id="section-9.2.1-1">The format of the QUOTATION message is shown below:<a href="#section-9.2.1-1" class="pilcrow">¶</a></p>
3226 <div id="section-9.2.1-2">
3227 <pre class="sourcecode lang-rbnf">
3228 &lt;QUOTATION Message&gt; ::= &lt;VERSION&gt;
3229 &lt;METHOD_CODE&gt;
3230 &lt;SEQUENCE_NUMBER&gt;
3231 &lt;TRANSACTION_ID&gt;
3232 &lt;CUSTOMER_ORDER_IDENTIFIER&gt;
3233 [&lt;EXPECTED_RESPONSE_TIME&gt;]
3234 &lt;REQUESTED_CPD&gt;
3235 [&lt;INFORMATION_ELEMENT&gt;...]
3236 </pre><a href="#section-9.2.1-2" class="pilcrow">¶</a>
3237 </div>
3238 <p id="section-9.2.1-3">A QUOTATION message must include an order
3239 identifier that is generated by the client
3240 (CUSTOMER_ORDER_IDENTIFIER). Because several orders can be
3241 issued to several servers, the QUOTATION message must also include a
3242 Transaction-ID.<a href="#section-9.2.1-3" class="pilcrow">¶</a></p>
3243 <p id="section-9.2.1-4">The message may include an EXPECTED_RESPONSE_TIME, which indicates
3244 by when the client expects to receive an offer from the server.
3245 The QUOTATION message must also include a requested service description
3246 (that is, a Requested CPD for
3247 connectivity services).<a href="#section-9.2.1-4" class="pilcrow">¶</a></p>
3248 <p id="section-9.2.1-5">The message may include ACTIVATION_TYPE to request a permanent or
3249 scheduled activation type (e.g., using the ACTIVATE method defined
3250 in <a href="#activate" class="xref">Section 9.2.11</a>). If no such clause is included,
3251 the default mode is to assume that the order will be active once the
3252 accepted activation means are successfully invoked (e.g., <span><a href="https://www.rfc-editor.org/rfc/rfc7297#section-3.11" class="relref">Section 3.11</a> of [<a href="#RFC7297" class="xref">RFC7297</a>]</span>).<a href="#section-9.2.1-5" class="pilcrow">¶</a></p>
3253 <p id="section-9.2.1-6">When the client sends the QUOTATION message to the server, the
3254 state of the order changes to "PQOSent" at the client side.<a href="#section-9.2.1-6" class="pilcrow">¶</a></p>
3255 </section>
3256 </div>
3257 <div id="proc">
3258 <section id="section-9.2.2">
3259 <h4 id="name-processing">
3260 <a href="#section-9.2.2" class="section-number selfRef">9.2.2. </a><a href="#name-processing" class="section-name selfRef">PROCESSING</a>
3261 </h4>
3262 <p id="section-9.2.2-1">The format of the PROCESSING message is shown below:<a href="#section-9.2.2-1" class="pilcrow">¶</a></p>
3263 <div id="section-9.2.2-2">
3264 <pre class="sourcecode lang-rbnf">
3265 &lt;PROCESSING Message&gt; ::= &lt;VERSION&gt;
3266 &lt;METHOD_CODE&gt;
3267 &lt;SEQUENCE_NUMBER&gt;
3268 &lt;TRANSACTION_ID&gt;
3269 &lt;CUSTOMER_ORDER_IDENTIFIER&gt;
3270 &lt;PROVIDER_ORDER_IDENTIFIER&gt;
3271 [&lt;EXPECTED_OFFER_TIME&gt;]
3272 [&lt;PROCESSING_SUBCODE&gt;]
3273 </pre><a href="#section-9.2.2-2" class="pilcrow">¶</a>
3274 </div>
3275 <p id="section-9.2.2-3">Upon receipt of a QUOTATION message, the
3276 server proceeds with the parsing rules (see <a href="#validation" class="xref">Section 10</a>).
3277 If no error is encountered, the server
3278 generates a PROCESSING response to the client to indicate the PQO
3279 has been received and it is being processed. The server must
3280 generate an order identifier that identifies the order in its local
3281 order repository. The server must copy the content of the
3282 CUSTOMER_ORDER_IDENTIFIER and TRANSACTION_ID fields as conveyed
3283 in the QUOTATION message. The server may include an
3284 EXPECTED_OFFER_TIME by when it expects to make an offer to the
3285 client.<a href="#section-9.2.2-3" class="pilcrow">¶</a></p>
3286 <p id="section-9.2.2-4">Upon receipt of a PROCESSING message, the client verifies whether
3287 it has issued a PQO that contains the
3288 CUSTOMER_ORDER_IDENTIFIER and TRANSACTION_ID to that server. If no such PQO is
3289 found, the PROCESSING message must be silently ignored. If a PQO is
3290 found, the client may check whether it accepts the
3291 EXPECTED_OFFER_TIME, and then it changes to state of the order to
3292 "ServerProcessing".<a href="#section-9.2.2-4" class="pilcrow">¶</a></p>
3293 <p id="section-9.2.2-5">If the server requires more time to process the quotation
3294 order, it may send a PROCESSING message that includes a new
3295 EXPECTED_OFFER_TIME. The client can answer with an ACK message if
3296 more time is granted (<a href="#timegranted" class="xref">Figure 11</a>) or with a
3297 FAIL message if the time extension request is rejected (<a href="#timerejected" class="xref">Figure 12</a>).<a href="#section-9.2.2-5" class="pilcrow">¶</a></p>
3298 <p id="section-9.2.2-6">The server may provide more details in the PROCESSING_SUBCODE
3299 attribute about the reason for requesting more time to process the
3300 request. The following codes are defined:<a href="#section-9.2.2-6" class="pilcrow">¶</a></p>
3301 <span id="name-processing_subcode-codes"></span><table class="left" id="table-2">
3302 <caption>
3303 <a href="#table-2" class="selfRef">Table 2</a>:
3304 <a href="#name-processing_subcode-codes" class="selfRef">PROCESSING_SUBCODE Codes</a>
3305 </caption>
3306 <thead>
3307 <tr>
3308 <th class="text-left" rowspan="1" colspan="1">Subcode</th>
3309 <th class="text-left" rowspan="1" colspan="1">Description</th>
3310 </tr>
3311 </thead>
3312 <tbody>
3313 <tr>
3314 <td class="text-left" rowspan="1" colspan="1">1</td>
3315 <td class="text-left" rowspan="1" colspan="1">Upgrade of local resources</td>
3316 </tr>
3317 <tr>
3318 <td class="text-left" rowspan="1" colspan="1">2</td>
3319 <td class="text-left" rowspan="1" colspan="1">Request external resources</td>
3320 </tr>
3321 </tbody>
3322 </table>
3323 <span id="name-request-more-negotiation-ti"></span><div id="timegranted">
3324 <figure id="figure-11">
3325 <div class="artwork art-text alignCenter" id="section-9.2.2-8.1">
3326 <pre>
3327 +------+ +------+
3328 |Client| |Server|
3329 +------+ +------+
3330 |=======QUOTATION(Requested CPD)=====&gt;|
3331 |&lt;========PROCESSING(time1)===========|
3332 ...
3333 |&lt;========PROCESSING(MoreTime)========|
3334 |============ACK(TimeGranted)========&gt;|
3335 ...
3336 |&lt;=========OFFER(Offered CPD)=========|
3337 |=============PROCESSING=============&gt;|
3338 |=========ACCEPT(Accepted CPD)=======&gt;|
3339 |&lt;=========ACK(Accepted CPD)==========|
3340 | |
3341 </pre>
3342 </div>
3343 <figcaption><a href="#figure-11" class="selfRef">Figure 11</a>:
3344 <a href="#name-request-more-negotiation-ti" class="selfRef">Request More Negotiation Time: Granted</a>
3345 </figcaption></figure>
3346 </div>
3347 <span id="name-request-more-negotiation-tim"></span><div id="timerejected">
3348 <figure id="figure-12">
3349 <div class="artwork art-text alignCenter" id="section-9.2.2-9.1">
3350 <pre>
3351 +------+ +------+
3352 |Client| |Server|
3353 +------+ +------+
3354 |=======QUOTATION(Requested CPD)=====&gt;|
3355 |&lt;========PROCESSING(time1)===========|
3356 ...
3357 |&lt;========PROCESSING(MoreTime)========|
3358 |=====FAIL(More Time Rejected)=======&gt;|
3359 </pre>
3360 </div>
3361 <figcaption><a href="#figure-12" class="selfRef">Figure 12</a>:
3362 <a href="#name-request-more-negotiation-tim" class="selfRef">Request More Negotiation Time: Rejected</a>
3363 </figcaption></figure>
3364 </div>
3365 </section>
3366 </div>
3367 <div id="offer">
3368 <section id="section-9.2.3">
3369 <h4 id="name-offer">
3370 <a href="#section-9.2.3" class="section-number selfRef">9.2.3. </a><a href="#name-offer" class="section-name selfRef">OFFER</a>
3371 </h4>
3372 <p id="section-9.2.3-1">The format of the OFFER message is shown below:<a href="#section-9.2.3-1" class="pilcrow">¶</a></p>
3373 <div id="section-9.2.3-2">
3374 <pre class="sourcecode lang-rbnf">
3375 &lt;OFFER Message&gt; ::= &lt;VERSION&gt;
3376 &lt;METHOD_CODE&gt;
3377 &lt;SEQUENCE_NUMBER&gt;
3378 &lt;TRANSACTION_ID&gt;
3379 &lt;CUSTOMER_ORDER_IDENTIFIER&gt;
3380 &lt;PROVIDER_ORDER_IDENTIFIER&gt;
3381 &lt;NONCE&gt;
3382 &lt;VALIDITY_OFFER_TIME&gt;
3383 &lt;OFFERED_CPD&gt;
3384 [&lt;INFORMATION_ELEMENT&gt;...]
3385 </pre><a href="#section-9.2.3-2" class="pilcrow">¶</a>
3386 </div>
3387 <p id="section-9.2.3-3">The server answers
3388 a QUOTATION request received from the client with an OFFER message. The offer will be
3389 considered to be rejected by the client if no confirmation (i.e., an ACCEPT
3390 message sent by the client) is received by the server before the
3391 expiration of the validity time.<a href="#section-9.2.3-3" class="pilcrow">¶</a></p>
3392 <p id="section-9.2.3-4">The server may include ACTIVATION_TYPE to indicate whether the
3393 offer is about a permanent or scheduled activation type. The message
3394 may include ACTIVATION_SCHEDULE to indicate when the order is to be
3395 activated. If no such clause is included, the default mode is to
3396 assume that the order will be active once the accepted activation
3397 means are successfully invoked (e.g., <span><a href="https://www.rfc-editor.org/rfc/rfc7297#section-3.11" class="relref">Section 3.11</a> of [<a href="#RFC7297" class="xref">RFC7297</a>]</span> or <a href="#activate" class="xref">Section 9.2.11</a>).<a href="#section-9.2.3-4" class="pilcrow">¶</a></p>
3398 </section>
3399 </div>
3400 <div id="accept">
3401 <section id="section-9.2.4">
3402 <h4 id="name-accept">
3403 <a href="#section-9.2.4" class="section-number selfRef">9.2.4. </a><a href="#name-accept" class="section-name selfRef">ACCEPT</a>
3404 </h4>
3405 <p id="section-9.2.4-1">The format of the ACCEPT message is shown below:<a href="#section-9.2.4-1" class="pilcrow">¶</a></p>
3406 <div id="section-9.2.4-2">
3407 <pre class="sourcecode lang-rbnf">
3408 &lt;ACCEPT Message&gt; ::= &lt;VERSION&gt;
3409 &lt;METHOD_CODE&gt;
3410 &lt;SEQUENCE_NUMBER&gt;
3411 &lt;TRANSACTION_ID&gt;
3412 &lt;CUSTOMER_ORDER_IDENTIFIER&gt;
3413 &lt;PROVIDER_ORDER_IDENTIFIER&gt;
3414 &lt;NONCE&gt;
3415 &lt;ACCEPTED_CPD&gt;
3416 [&lt;INFORMATION_ELEMENT&gt;...]
3417 </pre><a href="#section-9.2.4-2" class="pilcrow">¶</a>
3418 </div>
3419 <p id="section-9.2.4-3">This message is used by a client to
3420 confirm the acceptance of an offer received from a server. The
3421 fields of this message must be copied from the received OFFER
3422 message. This message should not be sent after the validity time of
3423 the offer expires, as indicated by the server (<a href="#offer" class="xref">Section 9.2.3</a>).<a href="#section-9.2.4-3" class="pilcrow">¶</a></p>
3424 </section>
3425 </div>
3426 <div id="dec">
3427 <section id="section-9.2.5">
3428 <h4 id="name-decline">
3429 <a href="#section-9.2.5" class="section-number selfRef">9.2.5. </a><a href="#name-decline" class="section-name selfRef">DECLINE</a>
3430 </h4>
3431 <p id="section-9.2.5-1">The format of the DECLINE message is shown below:<a href="#section-9.2.5-1" class="pilcrow">¶</a></p>
3432 <div id="section-9.2.5-2">
3433 <pre class="sourcecode lang-rbnf">
3434 &lt;DECLINE Message&gt; ::= &lt;VERSION&gt;
3435 &lt;METHOD_CODE&gt;
3436 &lt;SEQUENCE_NUMBER&gt;
3437 &lt;TRANSACTION_ID&gt;
3438 &lt;CUSTOMER_ORDER_IDENTIFIER&gt;
3439 &lt;PROVIDER_ORDER_IDENTIFIER&gt;
3440 &lt;NONCE&gt;
3441 [&lt;REASON&gt;...]
3442 </pre><a href="#section-9.2.5-2" class="pilcrow">¶</a>
3443 </div>
3444 <p id="section-9.2.5-3">The client may issue a DECLINE
3445 message to reject an offer. CUSTOMER_ORDER_IDENTIFIER,
3446 PROVIDER_ORDER_IDENTIFIER, TRANSACTION_ID, and NONCE are used by
3447 the server as keys to find the corresponding order. If an order
3448 matches, the server changes the state of this order to "Cancelled"
3449 and then returns an ACK with a copy of the Requested CPD to the
3450 requesting client.<a href="#section-9.2.5-3" class="pilcrow">¶</a></p>
3451 <p id="section-9.2.5-4">A DECLINE message may include an Information Element to indicate
3452 the reason for declining an offer. The following codes are defined:<a href="#section-9.2.5-4" class="pilcrow">¶</a></p>
3453 <span id="name-decline-message-codes"></span><table class="left" id="table-3">
3454 <caption>
3455 <a href="#table-3" class="selfRef">Table 3</a>:
3456 <a href="#name-decline-message-codes" class="selfRef">DECLINE Message Codes</a>
3457 </caption>
3458 <thead>
3459 <tr>
3460 <th class="text-left" rowspan="1" colspan="1">Code</th>
3461 <th class="text-left" rowspan="1" colspan="1">Description</th>
3462 </tr>
3463 </thead>
3464 <tbody>
3465 <tr>
3466 <td class="text-left" rowspan="1" colspan="1">1</td>
3467 <td class="text-left" rowspan="1" colspan="1">Unacceptable gap between the request and the offer</td>
3468 </tr>
3469 <tr>
3470 <td class="text-left" rowspan="1" colspan="1">2</td>
3471 <td class="text-left" rowspan="1" colspan="1">Conflict with another offer from another server</td>
3472 </tr>
3473 <tr>
3474 <td class="text-left" rowspan="1" colspan="1">3</td>
3475 <td class="text-left" rowspan="1" colspan="1">Activation type mismatch</td>
3476 </tr>
3477 </tbody>
3478 </table>
3479 <p id="section-9.2.5-6">If no order is found, the server returns a FAIL message to the
3480 requesting client. In order to prevent DDoS (Distributed Denial of
3481 Service) attacks, the server should restrict the number of FAIL
3482 messages sent to a requesting client. It may also rate-limit FAIL
3483 messages.<a href="#section-9.2.5-6" class="pilcrow">¶</a></p>
3484 <p id="section-9.2.5-7">A flow example is shown in <a href="#decline" class="xref">Figure 13</a>.<a href="#section-9.2.5-7" class="pilcrow">¶</a></p>
3485 <span id="name-decline-flow-example"></span><div id="decline">
3486 <figure id="figure-13">
3487 <div class="artwork art-text alignCenter" id="section-9.2.5-8.1">
3488 <pre>+------+ +------+
3489 |Client| |Server|
3490 +------+ +------+
3491 |=======QUOTATION(Requested CPD)=====&gt;|
3492 |&lt;============PROCESSING==============|
3493 |&lt;=========OFFER(Offered CPD)=========|
3494 |=============PROCESSING=============&gt;|
3495 |===============DECLINE==============&gt;|
3496 |&lt;================ACK=================|
3497 | |
3498 </pre>
3499 </div>
3500 <figcaption><a href="#figure-13" class="selfRef">Figure 13</a>:
3501 <a href="#name-decline-flow-example" class="selfRef">DECLINE Flow Example</a>
3502 </figcaption></figure>
3503 </div>
3504 </section>
3505 </div>
3506 <div id="ack">
3507 <section id="section-9.2.6">
3508 <h4 id="name-ack">
3509 <a href="#section-9.2.6" class="section-number selfRef">9.2.6. </a><a href="#name-ack" class="section-name selfRef">ACK</a>
3510 </h4>
3511 <p id="section-9.2.6-1">The format of the ACK message is shown below:<a href="#section-9.2.6-1" class="pilcrow">¶</a></p>
3512 <div id="section-9.2.6-2">
3513 <pre class="sourcecode lang-rbnf">
3514 &lt;ACK Message&gt; ::= &lt;VERSION&gt;
3515 &lt;METHOD_CODE&gt;
3516 &lt;SEQUENCE_NUMBER&gt;
3517 &lt;TRANSACTION_ID&gt;
3518 &lt;CUSTOMER_ORDER_IDENTIFIER&gt;
3519 &lt;PROVIDER_ORDER_IDENTIFIER&gt;
3520 [&lt;EXPECTED_RESPONSE_TIME&gt;]
3521 [&lt;CPD&gt;]
3522 [&lt;INFORMATION_ELEMENT&gt;...]
3523 </pre><a href="#section-9.2.6-2" class="pilcrow">¶</a>
3524 </div>
3525 <p id="section-9.2.6-3">This message is issued by the server to
3526 close a CPNP transaction or by a client to grant more negotiation
3527 time to the server.<a href="#section-9.2.6-3" class="pilcrow">¶</a></p>
3528 <p id="section-9.2.6-4">This message is sent by the server as a response to an ACCEPT,
3529 WITHDRAW, DECLINE, or CANCEL message. In this case, the ACK message
3530 must include the copy of the service description (i.e., CPD for connectivity services) as stored
3531 by the server. In particular, the following considerations are taken
3532 into account for connectivity provisioning services:<a href="#section-9.2.6-4" class="pilcrow">¶</a></p>
3533 <ul class="normal">
3534 <li class="normal" id="section-9.2.6-5.1">A copy of the Requested/Offered CPD is included by the server
3535 if it successfully handled a CANCEL message.<a href="#section-9.2.6-5.1" class="pilcrow">¶</a>
3536 </li>
3537 <li class="normal" id="section-9.2.6-5.2">A copy of the Updated CPD is included by the server if it
3538 successfully handled an UPDATE message.<a href="#section-9.2.6-5.2" class="pilcrow">¶</a>
3539 </li>
3540 <li class="normal" id="section-9.2.6-5.3">A copy of the Offered CPD is included by the server if it
3541 successfully handled an ACCEPT message in the context of a
3542 QUOTATION transaction (refer to "Accepted CPD" in <a href="#cpd" class="xref">Section 8.7</a>).<a href="#section-9.2.6-5.3" class="pilcrow">¶</a>
3543 </li>
3544 <li class="normal" id="section-9.2.6-5.4">An Empty CPD is included by the server if it successfully
3545 handled a DECLINE or WITHDRAW message.<a href="#section-9.2.6-5.4" class="pilcrow">¶</a>
3546 </li>
3547 </ul>
3548 <p id="section-9.2.6-6">A client may issue an ACK message as a response to a time
3549 extension request (conveyed in PROCESSING) received from the server.
3550 In such case, the ACK message must include an EXPECTED_RESPONSE_TIME
3551 that is likely to be set to the time extension requested by the
3552 server.<a href="#section-9.2.6-6" class="pilcrow">¶</a></p>
3553 </section>
3554 </div>
3555 <div id="cancel">
3556 <section id="section-9.2.7">
3557 <h4 id="name-cancel">
3558 <a href="#section-9.2.7" class="section-number selfRef">9.2.7. </a><a href="#name-cancel" class="section-name selfRef">CANCEL</a>
3559 </h4>
3560 <p id="section-9.2.7-1">The format of the CANCEL message is shown below:<a href="#section-9.2.7-1" class="pilcrow">¶</a></p>
3561 <div id="section-9.2.7-2">
3562 <pre class="sourcecode lang-rbnf">
3563 &lt;CANCEL Message&gt; ::= &lt;VERSION&gt;
3564 &lt;METHOD_CODE&gt;
3565 &lt;SEQUENCE_NUMBER&gt;
3566 &lt;TRANSACTION_ID&gt;
3567 &lt;CUSTOMER_ORDER_IDENTIFIER&gt;
3568 [&lt;CPD&gt;]
3569 </pre><a href="#section-9.2.7-2" class="pilcrow">¶</a>
3570 </div>
3571 <p id="section-9.2.7-3">The client can issue a CANCEL
3572 message at any stage during the CPNP negotiation process before an
3573 agreement is reached. The CUSTOMER_ORDER_IDENTIFIER and
3574 TRANSACTION_ID are used by the server as keys to find the
3575 corresponding order. If a quotation order matches, the server
3576 changes the state of this quotation order to "Cancelled" and then
3577 returns an ACK with a copy of the Requested CPD to the requesting
3578 client.<a href="#section-9.2.7-3" class="pilcrow">¶</a></p>
3579 <p id="section-9.2.7-4">If no quotation order is found, the server returns a FAIL message
3580 to the requesting client.<a href="#section-9.2.7-4" class="pilcrow">¶</a></p>
3581 </section>
3582 </div>
3583 <div id="with">
3584 <section id="section-9.2.8">
3585 <h4 id="name-withdraw">
3586 <a href="#section-9.2.8" class="section-number selfRef">9.2.8. </a><a href="#name-withdraw" class="section-name selfRef">WITHDRAW</a>
3587 </h4>
3588 <p id="section-9.2.8-1">The format of the WITHDRAW message is shown below:<a href="#section-9.2.8-1" class="pilcrow">¶</a></p>
3589 <div id="section-9.2.8-2">
3590 <pre class="sourcecode lang-rbnf">
3591 &lt;WITHDRAW Message&gt; ::= &lt;VERSION&gt;
3592 &lt;METHOD_CODE&gt;
3593 &lt;SEQUENCE_NUMBER&gt;
3594 &lt;TRANSACTION_ID&gt;
3595 &lt;CUSTOMER_ORDER_IDENTIFIER&gt;
3596 &lt;PROVIDER_ORDER_IDENTIFIER&gt;
3597 &lt;NONCE&gt;
3598 [&lt;ACCEPTED_CPD&gt;]
3599 [&lt;INFORMATION_ELEMENT&gt;...]
3600 </pre><a href="#section-9.2.8-2" class="pilcrow">¶</a>
3601 </div>
3602 <p id="section-9.2.8-3">This message is used to withdraw an offer
3603 already accepted by the Customer. <a href="#withdraw" class="xref">Figure 14</a>
3604 shows a typical usage of this message.<a href="#section-9.2.8-3" class="pilcrow">¶</a></p>
3605 <span id="name-withdraw-flow-example"></span><div id="withdraw">
3606 <figure id="figure-14">
3607 <div class="artwork art-text alignCenter" id="section-9.2.8-4.1">
3608 <pre>
3609 +------+ +------+
3610 |Client| |Server|
3611 +------+ +------+
3612 |============WITHDRAW(CPD)===========&gt;|
3613 |&lt;============PROCESSING==============|
3614 |&lt;===========ACK(Empty CPD)===========|
3615 | |
3616 </pre>
3617 </div>
3618 <figcaption><a href="#figure-14" class="selfRef">Figure 14</a>:
3619 <a href="#name-withdraw-flow-example" class="selfRef">WITHDRAW Flow Example</a>
3620 </figcaption></figure>
3621 </div>
3622 <p id="section-9.2.8-5">The WITHDRAW message must include the same
3623 CUSTOMER_ORDER_IDENTIFIER, PROVIDER_ORDER_IDENTIFIER, and
3624 NONCE as those used when creating the order.<a href="#section-9.2.8-5" class="pilcrow">¶</a></p>
3625 <p id="section-9.2.8-6">Upon receipt of a WITHDRAW message, the server checks whether an
3626 order matching the request is found. If an order is found, the state
3627 of the order is changed to "Cancelled", and an ACK message including
3628 an Empty CPD is returned to the requesting client. If no order is
3629 found, the server returns a FAIL message to the requesting
3630 client.<a href="#section-9.2.8-6" class="pilcrow">¶</a></p>
3631 </section>
3632 </div>
3633 <div id="upd">
3634 <section id="section-9.2.9">
3635 <h4 id="name-update">
3636 <a href="#section-9.2.9" class="section-number selfRef">9.2.9. </a><a href="#name-update" class="section-name selfRef">UPDATE</a>
3637 </h4>
3638 <p id="section-9.2.9-1">The format of the UPDATE message is shown below:<a href="#section-9.2.9-1" class="pilcrow">¶</a></p>
3639 <div id="section-9.2.9-2">
3640 <pre class="sourcecode lang-rbnf">
3641 &lt;UPDATE Message&gt; ::= &lt;VERSION&gt;
3642 &lt;METHOD_CODE&gt;
3643 &lt;SEQUENCE_NUMBER&gt;
3644 &lt;TRANSACTION_ID&gt;
3645 &lt;CUSTOMER_ORDER_IDENTIFIER&gt;
3646 &lt;PROVIDER_ORDER_IDENTIFIER&gt;
3647 &lt;NONCE&gt;
3648 &lt;EXPECTED_RESPONSE_TIME&gt;
3649 &lt;REQUESTED_CPD&gt;
3650 [&lt;INFORMATION_ELEMENT&gt;...]
3651 </pre><a href="#section-9.2.9-2" class="pilcrow">¶</a>
3652 </div>
3653 <p id="section-9.2.9-3">This message is sent by the CPNP client
3654 to update an existing service agreement (e.g., Accepted
3655 CPD). The UPDATE message must include the same
3656 CUSTOMER_ORDER_IDENTIFIER, PROVIDER_ORDER_IDENTIFIER, and
3657 NONCE as those used when creating the order. The CPNP client
3658 includes a new service description (e.g., Updated CPD) that
3659 integrates the requested modifications. A new Transaction_ID must be
3660 assigned by the client.<a href="#section-9.2.9-3" class="pilcrow">¶</a></p>
3661 <p id="section-9.2.9-4">Upon receipt of an UPDATE message, the server checks whether an
3662 order, having state "Completed", matches
3663 CUSTOMER_ORDER_IDENTIFIER, PROVIDER_ORDER_IDENTIFIER, and
3664 NONCE.<a href="#section-9.2.9-4" class="pilcrow">¶</a></p>
3665 <ul class="normal">
3666 <li class="normal" id="section-9.2.9-5.1">If no order is found, the CPNP server generates a FAIL error
3667 with the appropriate error code (<a href="#fail" class="xref">Section 9.2.10</a>).<a href="#section-9.2.9-5.1" class="pilcrow">¶</a>
3668 </li>
3669 <li class="normal" id="section-9.2.9-5.2">
3670 <p id="section-9.2.9-5.2.1">If an order is found, the server checks whether it can honor
3671 the request:<a href="#section-9.2.9-5.2.1" class="pilcrow">¶</a></p>
3672 <ul class="normal">
3673 <li class="normal" id="section-9.2.9-5.2.2.1">A FAIL message is sent to the client if the server cannot
3674 honor the request. The client may initiate a new PQO
3675 negotiation cycle (that is, send a new UPDATE message).<a href="#section-9.2.9-5.2.2.1" class="pilcrow">¶</a>
3676 </li>
3677 <li class="normal" id="section-9.2.9-5.2.2.2">
3678 <p id="section-9.2.9-5.2.2.2.1">An OFFER message including the updated clauses (e.g.,
3679 Updated CPD) is sent to the
3680 client. For example, the server maintains an order for
3681 provisioning a VPN service that connects sites A, B, and C.
3682 If the client sends an UPDATE message to remove site C, only
3683 sites A and B will be included in the OFFER sent by the
3684 server to the requesting client.<a href="#section-9.2.9-5.2.2.2.1" class="pilcrow">¶</a></p>
3685 <p id="section-9.2.9-5.2.2.2.2">Note that the cycle that is triggered by an
3686 UPDATE message is also considered to be a negotiation
3687 cycle.<a href="#section-9.2.9-5.2.2.2.2" class="pilcrow">¶</a></p>
3688 </li>
3689 </ul>
3690 </li>
3691 </ul>
3692 <p id="section-9.2.9-6">A flow chart that illustrates the use of UPDATE operation is
3693 shown in <a href="#update" class="xref">Figure 15</a>.<a href="#section-9.2.9-6" class="pilcrow">¶</a></p>
3694 <span id="name-update-flow-example"></span><div id="update">
3695 <figure id="figure-15">
3696 <div class="artwork art-text alignCenter" id="section-9.2.9-7.1">
3697 <pre>
3698 +------+ +------+
3699 |Client| |Server|
3700 +------+ +------+
3701 |=========UPDATE(Requested CPD)======&gt;|
3702 |&lt;============PROCESSING==============|
3703 |&lt;=========OFFER(Updated CPD)=========|
3704 |=============PROCESSING=============&gt;|
3705 |==========ACCEPT(Updated CPD)=======&gt;|
3706 |&lt;==========ACK(Updated CPD)==========|
3707 | |
3708 </pre>
3709 </div>
3710 <figcaption><a href="#figure-15" class="selfRef">Figure 15</a>:
3711 <a href="#name-update-flow-example" class="selfRef">UPDATE Flow Example</a>
3712 </figcaption></figure>
3713 </div>
3714 </section>
3715 </div>
3716 <div id="fail">
3717 <section id="section-9.2.10">
3718 <h4 id="name-fail">
3719 <a href="#section-9.2.10" class="section-number selfRef">9.2.10. </a><a href="#name-fail" class="section-name selfRef">FAIL</a>
3720 </h4>
3721 <p id="section-9.2.10-1">The format of the FAIL message is shown below:<a href="#section-9.2.10-1" class="pilcrow">¶</a></p>
3722 <div id="section-9.2.10-2">
3723 <pre class="sourcecode lang-rbnf">
3724 &lt;FAIL Message&gt; ::= &lt;VERSION&gt;
3725 &lt;METHOD_CODE&gt;
3726 &lt;SEQUENCE_NUMBER&gt;
3727 &lt;TRANSACTION_ID&gt;
3728 &lt;CUSTOMER_ORDER_IDENTIFIER&gt;
3729 &lt;PROVIDER_ORDER_IDENTIFIER&gt;
3730 &lt;STATUS_CODE&gt;
3731 </pre><a href="#section-9.2.10-2" class="pilcrow">¶</a>
3732 </div>
3733 <p id="section-9.2.10-3">This message is sent in the following
3734 cases:<a href="#section-9.2.10-3" class="pilcrow">¶</a></p>
3735 <ul class="normal">
3736 <li class="normal" id="section-9.2.10-4.1">The server cannot honor an order received from the client
3737 (i.e., received in a QUOTATION or UPDATE request).<a href="#section-9.2.10-4.1" class="pilcrow">¶</a>
3738 </li>
3739 <li class="normal" id="section-9.2.10-4.2">The server encounters an error when processing a CPNP request
3740 received from the client.<a href="#section-9.2.10-4.2" class="pilcrow">¶</a>
3741 </li>
3742 <li class="normal" id="section-9.2.10-4.3">The client cannot grant more time to the server. This is a
3743 response to a time extension request carried in a PROCESSING
3744 message.<a href="#section-9.2.10-4.3" class="pilcrow">¶</a>
3745 </li>
3746 </ul>
3747 <p id="section-9.2.10-5">The status code indicates the error code. The following codes are
3748 supported:<a href="#section-9.2.10-5" class="pilcrow">¶</a></p>
3749 <span id="name-fail-message-error-codes"></span><table class="center" id="table-4">
3750 <caption>
3751 <a href="#table-4" class="selfRef">Table 4</a>:
3752 <a href="#name-fail-message-error-codes" class="selfRef">FAIL Message Error Codes</a>
3753 </caption>
3754 <thead>
3755 <tr>
3756 <th class="text-left" rowspan="1" colspan="1">Status Code</th>
3757 <th class="text-left" rowspan="1" colspan="1">Error Code</th>
3758 <th class="text-left" rowspan="1" colspan="1">Description</th>
3759 </tr>
3760 </thead>
3761 <tbody>
3762 <tr>
3763 <td class="text-left" rowspan="1" colspan="1">1</td>
3764 <td class="text-left" rowspan="1" colspan="1">Message Validation Error</td>
3765 <td class="text-left" rowspan="1" colspan="1">The message cannot be validated (see <a href="#validation" class="xref">Section 10</a>).</td>
3766 </tr>
3767 <tr>
3768 <td class="text-left" rowspan="1" colspan="1">2</td>
3769 <td class="text-left" rowspan="1" colspan="1">Authentication Required</td>
3770 <td class="text-left" rowspan="1" colspan="1">The request cannot be handled because authentication is required.</td>
3771 </tr>
3772 <tr>
3773 <td class="text-left" rowspan="1" colspan="1">3</td>
3774 <td class="text-left" rowspan="1" colspan="1">Authorization Failed</td>
3775 <td class="text-left" rowspan="1" colspan="1">The request cannot be handled because authorization failed.</td>
3776 </tr>
3777 <tr>
3778 <td class="text-left" rowspan="1" colspan="1">4</td>
3779 <td class="text-left" rowspan="1" colspan="1">Administratively prohibited</td>
3780 <td class="text-left" rowspan="1" colspan="1">The request cannot be handled because of administrative policies.</td>
3781 </tr>
3782 <tr>
3783 <td class="text-left" rowspan="1" colspan="1">5</td>
3784 <td class="text-left" rowspan="1" colspan="1">Out of Resources</td>
3785 <td class="text-left" rowspan="1" colspan="1">The request cannot be honored because resources (e.g., capacity) are insufficient.</td>
3786 </tr>
3787 <tr>
3788 <td class="text-left" rowspan="1" colspan="1">6</td>
3789 <td class="text-left" rowspan="1" colspan="1">Network Presence Error</td>
3790 <td class="text-left" rowspan="1" colspan="1">The request cannot be honored because there is no network presence.</td>
3791 </tr>
3792 <tr>
3793 <td class="text-left" rowspan="1" colspan="1">7</td>
3794 <td class="text-left" rowspan="1" colspan="1">More Time Rejected</td>
3795 <td class="text-left" rowspan="1" colspan="1">The request to extend the time for negotiation is rejected by the client.</td>
3796 </tr>
3797 <tr>
3798 <td class="text-left" rowspan="1" colspan="1">8</td>
3799 <td class="text-left" rowspan="1" colspan="1">Unsupported Activation Type</td>
3800 <td class="text-left" rowspan="1" colspan="1">The request cannot be handled because the requested activation type is not
3801 supported.</td>
3802 </tr>
3803 </tbody>
3804 </table>
3805 </section>
3806 </div>
3807 <div id="activate">
3808 <section id="section-9.2.11">
3809 <h4 id="name-activate">
3810 <a href="#section-9.2.11" class="section-number selfRef">9.2.11. </a><a href="#name-activate" class="section-name selfRef">ACTIVATE</a>
3811 </h4>
3812 <p id="section-9.2.11-1">The format of the ACTIVATE message is shown below:<a href="#section-9.2.11-1" class="pilcrow">¶</a></p>
3813 <div id="section-9.2.11-2">
3814 <pre class="sourcecode lang-rbnf">
3815 &lt;ACTIVATE Message&gt; ::= &lt;VERSION&gt;
3816 &lt;METHOD_CODE&gt;
3817 &lt;SEQUENCE_NUMBER&gt;
3818 &lt;TRANSACTION_ID&gt;
3819 &lt;CUSTOMER_ORDER_IDENTIFIER&gt;
3820 &lt;PROVIDER_ORDER_IDENTIFIER&gt;
3821 &lt;NONCE&gt;
3822 &lt;ACTIVATION_SCHEDULE&gt;
3823 [&lt;INFORMATION_ELEMENT&gt;...]
3824 </pre><a href="#section-9.2.11-2" class="pilcrow">¶</a>
3825 </div>
3826 <p id="section-9.2.11-3">This message is sent by the CPNP client
3827 to request the activation of an existing service agreement. The
3828 message must include the same CUSTOMER_ORDER_IDENTIFIER,
3829 PROVIDER_ORDER_IDENTIFIER, and NONCE as those used when creating
3830 the order. The CPNP client may include a schedule target for
3831 activating this order. A new Transaction_ID must be assigned by the
3832 client.<a href="#section-9.2.11-3" class="pilcrow">¶</a></p>
3833 <p id="section-9.2.11-4">Upon receipt of an ACTIVATE message, the server checks whether an
3834 order, having state "Completed", matches
3835 CUSTOMER_ORDER_IDENTIFIER, PROVIDER_ORDER_IDENTIFIER, and
3836 NONCE.<a href="#section-9.2.11-4" class="pilcrow">¶</a></p>
3837 <ul class="normal">
3838 <li class="normal" id="section-9.2.11-5.1">If no completed order is found, the CPNP server generates a
3839 FAIL error with the appropriate error code (<a href="#fail" class="xref">Section 9.2.10</a>).<a href="#section-9.2.11-5.1" class="pilcrow">¶</a>
3840 </li>
3841 <li class="normal" id="section-9.2.11-5.2">
3842 <p id="section-9.2.11-5.2.1">If an order is found, the server checks whether it can honor
3843 the request:<a href="#section-9.2.11-5.2.1" class="pilcrow">¶</a></p>
3844 <ul class="normal">
3845 <li class="normal" id="section-9.2.11-5.2.2.1">A FAIL message is sent to the client if the server cannot
3846 honor the request (e.g., out of resources or explicit
3847 activation wasn't negotiated with this client).<a href="#section-9.2.11-5.2.2.1" class="pilcrow">¶</a>
3848 </li>
3849 <li class="normal" id="section-9.2.11-5.2.2.2">An ACK is sent to the client to confirm that the
3850 immediate activation (or deactivation) of the order or its
3851 successful scheduling if a non-null ACTIVATION_SCHEDULE was
3852 included in the request. Note that setting
3853 ACTIVATION_SCHEDULE to 0 in an ACTIVATE request has a
3854 special meaning: it is used to request a deactivation of an
3855 accepted order.<a href="#section-9.2.11-5.2.2.2" class="pilcrow">¶</a>
3856 </li>
3857 </ul>
3858 </li>
3859 </ul>
3860 <p id="section-9.2.11-6"><a href="#activateex" class="xref">Figure 16</a> illustrates the use of the ACTIVATE
3861 operation.<a href="#section-9.2.11-6" class="pilcrow">¶</a></p>
3862 <span id="name-activate-flow-example"></span><div id="activateex">
3863 <figure id="figure-16">
3864 <div class="artwork art-text alignCenter" id="section-9.2.11-7.1">
3865 <pre>
3866 +------+ +------+
3867 |Client| |Server|
3868 +------+ +------+
3869 |================ACTIVATE()==========&gt;|
3870 |&lt;==============ACK()=================|
3871 | |
3872 </pre>
3873 </div>
3874 <figcaption><a href="#figure-16" class="selfRef">Figure 16</a>:
3875 <a href="#name-activate-flow-example" class="selfRef">ACTIVATE Flow Example</a>
3876 </figcaption></figure>
3877 </div>
3878 </section>
3879 </div>
3880 </section>
3881 </section>
3882 </div>
3883 <div id="validation">
3884 <section id="section-10">
3885 <h2 id="name-cpnp-message-validation">
3886 <a href="#section-10" class="section-number selfRef">10. </a><a href="#name-cpnp-message-validation" class="section-name selfRef">CPNP Message Validation</a>
3887 </h2>
3888 <p id="section-10-1">Both the client and the server proceed with CPNP message validation. The
3889 following tables summarize the validation checks to be followed.<a href="#section-10-1" class="pilcrow">¶</a></p>
3890 <section id="section-10.1">
3891 <h3 id="name-on-the-client-side-2">
3892 <a href="#section-10.1" class="section-number selfRef">10.1. </a><a href="#name-on-the-client-side-2" class="section-name selfRef">On the Client Side</a>
3893 </h3>
3894 <span id="name-client-side-validation-chec"></span><table class="left" id="table-5">
3895 <caption>
3896 <a href="#table-5" class="selfRef">Table 5</a>:
3897 <a href="#name-client-side-validation-chec" class="selfRef">Client Side Validation Checks</a>
3898 </caption>
3899 <thead>
3900 <tr>
3901 <th class="text-left" rowspan="1" colspan="1">Operation</th>
3902 <th class="text-left" rowspan="1" colspan="1">Validation Checks</th>
3903 </tr>
3904 </thead>
3905 <tbody>
3906 <tr>
3907 <td class="text-left" rowspan="1" colspan="1">PROCESSING</td>
3908 <td class="text-left" rowspan="1" colspan="1">{Source IP address, source port number, destination IP address,
3909 destination port number, Transaction-ID, Customer Order Identifier}
3910 must match an existing PQO with a state set to "PQOSent". The
3911 sequence number carried in the packet must be larger than the
3912 sequence number maintained by the client.</td>
3913 </tr>
3914 <tr>
3915 <td class="text-left" rowspan="1" colspan="1">OFFER</td>
3916 <td class="text-left" rowspan="1" colspan="1">{Source IP address, source port number, destination IP address,
3917 destination port number, Transaction-ID, Customer Order Identifier}
3918 must match an existing order with state set to "PQOSent", or {Source
3919 IP address, source port number, destination IP address, destination
3920 port number, Transaction-ID, Customer Order Identifier, Provider
3921 Order Identifier} must match an existing order with a state set to
3922 "ServerProcessing". The sequence number carried in the packet must
3923 be larger than the sequence number maintained by the client.</td>
3924 </tr>
3925 <tr>
3926 <td class="text-left" rowspan="1" colspan="1">ACK (QUOTATION Transaction)</td>
3927 <td class="text-left" rowspan="1" colspan="1">{Source IP address, source port number, destination IP address,
3928 destination port number, Transaction-ID, Customer Order Identifier,
3929 Provider Order Identifier, Offered Connectivity Provisioning Document}
3930 must match an order with a state set to "AcceptSent". The sequence
3931 number carried in the packet must be larger than the sequence number
3932 maintained by the client.</td>
3933 </tr>
3934 <tr>
3935 <td class="text-left" rowspan="1" colspan="1">ACK (UPDATE Transaction)</td>
3936 <td class="text-left" rowspan="1" colspan="1">{Source IP address, source port number, destination IP address,
3937 destination port number, Transaction-ID, Customer Order Identifier,
3938 Provider Order Identifier, Updated Connectivity Provisioning Document}
3939 must match an order with a state set to "AcceptSent". The sequence
3940 number carried in the packet must be larger than the sequence number
3941 maintained by the client.</td>
3942 </tr>
3943 <tr>
3944 <td class="text-left" rowspan="1" colspan="1">ACK (WITHDRAW Transaction)</td>
3945 <td class="text-left" rowspan="1" colspan="1">{Source IP address, source port number, destination IP address,
3946 destination port number, Transaction-ID, Customer Order Identifier,
3947 Provider Order Identifier, Empty Connectivity Provisioning Document}
3948 must match an order with a state set to "Cancelled". The sequence
3949 number carried in the packet must be larger than the sequence number
3950 maintained by the client.</td>
3951 </tr>
3952 </tbody>
3953 </table>
3954 </section>
3955 <section id="section-10.2">
3956 <h3 id="name-on-the-server-side-2">
3957 <a href="#section-10.2" class="section-number selfRef">10.2. </a><a href="#name-on-the-server-side-2" class="section-name selfRef">On the Server Side</a>
3958 </h3>
3959 <span id="name-server-side-validation-chec"></span><table class="left" id="table-6">
3960 <caption>
3961 <a href="#table-6" class="selfRef">Table 6</a>:
3962 <a href="#name-server-side-validation-chec" class="selfRef">Server Side Validation Checks</a>
3963 </caption>
3964 <thead>
3965 <tr>
3966 <th class="text-left" rowspan="1" colspan="1">Method</th>
3967 <th class="text-left" rowspan="1" colspan="1">Validation Checks</th>
3968 </tr>
3969 </thead>
3970 <tbody>
3971 <tr>
3972 <td class="text-left" rowspan="1" colspan="1">QUOTATION</td>
3973 <td class="text-left" rowspan="1" colspan="1">The source IP address passes existing access filters (if any).
3974 The sequence number carried in the packet must not be lower than the
3975 sequence number maintained by the server.</td>
3976 </tr>
3977 <tr>
3978 <td class="text-left" rowspan="1" colspan="1">PROCESSING</td>
3979 <td class="text-left" rowspan="1" colspan="1">The sequence number carried in the packet must be greater than
3980 the sequence number maintained by the server.</td>
3981 </tr>
3982 <tr>
3983 <td class="text-left" rowspan="1" colspan="1">CANCEL</td>
3984 <td class="text-left" rowspan="1" colspan="1">{Source IP address, source port number, destination IP address,
3985 destination port number, Transaction-ID, Customer Order Identifier}
3986 must match an order with state set to "PQOReceived" or
3987 "OfferProposed" or "ProcessingReceived" or "AcceptReceived". The
3988 sequence number carried in the packet must be greater than the
3989 sequence number maintained by the server.</td>
3990 </tr>
3991 <tr>
3992 <td class="text-left" rowspan="1" colspan="1">ACCEPT</td>
3993 <td class="text-left" rowspan="1" colspan="1">{Source IP address, source port number, destination IP address,
3994 destination port number, Transaction-ID, Customer Order Identifier,
3995 Provider Order Identifier, Nonce, Offered Connectivity Provisioning
3996 Document} must match an order with state set to "OfferProposed" or
3997 "ProcessingReceived". The sequence number carried in the packet must
3998 be greater than the sequence number maintained by the server.</td>
3999 </tr>
4000 <tr>
4001 <td class="text-left" rowspan="1" colspan="1">FAIL</td>
4002 <td class="text-left" rowspan="1" colspan="1">{Source IP address, source port number, destination IP address,
4003 destination port number, Transaction-ID, Customer Order Identifier,
4004 Provider Order Identifier} must match an order with state set to
4005 "AwaitingProcessing" and for which a request to grant more time to
4006 process an offer was requested. The sequence number carried in the
4007 packet must be greater than the sequence number maintained by the
4008 server.</td>
4009 </tr>
4010 <tr>
4011 <td class="text-left" rowspan="1" colspan="1">DECLINE</td>
4012 <td class="text-left" rowspan="1" colspan="1">{Source IP address, source port number, destination IP address,
4013 destination port number, Transaction-ID, Customer Order Identifier,
4014 Provider Order Identifier, Nonce} must match an order with state set
4015 to "OfferProposed" or "ProcessingReceived". The sequence number
4016 carried in the packet must be greater than the sequence number
4017 maintained by the server.</td>
4018 </tr>
4019 <tr>
4020 <td class="text-left" rowspan="1" colspan="1">UPDATE</td>
4021 <td class="text-left" rowspan="1" colspan="1">The source IP address passes existing access filters (if any), and
4022 {Customer Order Identifier, Provider Order Identifier, Nonce} must
4023 match an existing order with state "Completed".</td>
4024 </tr>
4025 <tr>
4026 <td class="text-left" rowspan="1" colspan="1">WITHDRAW</td>
4027 <td class="text-left" rowspan="1" colspan="1">The source IP address passes existing access filters (if any), and
4028 {Customer Order Identifier, Provider Order Identifier, Nonce} must
4029 match an existing order with state "Completed".</td>
4030 </tr>
4031 <tr>
4032 <td class="text-left" rowspan="1" colspan="1">ACTIVATE</td>
4033 <td class="text-left" rowspan="1" colspan="1">The source IP address passes existing access filters (if any), and
4034 {Customer Order Identifier, Provider Order Identifier, Nonce} must
4035 match an existing order with a state of "Completed" and its
4036 activation procedure set to explicit.</td>
4037 </tr>
4038 </tbody>
4039 </table>
4040 </section>
4041 </section>
4042 </div>
4043 <div id="behavior">
4044 <section id="section-11">
4045 <h2 id="name-theory-of-operation">
4046 <a href="#section-11" class="section-number selfRef">11. </a><a href="#name-theory-of-operation" class="section-name selfRef">Theory of Operation</a>
4047 </h2>
4048 <p id="section-11-1">Both the CPNP client and server proceed with message validation checks as
4049 specified in <a href="#validation" class="xref">Section 10</a>.<a href="#section-11-1" class="pilcrow">¶</a></p>
4050 <section id="section-11.1">
4051 <h3 id="name-client-behavior">
4052 <a href="#section-11.1" class="section-number selfRef">11.1. </a><a href="#name-client-behavior" class="section-name selfRef">Client Behavior</a>
4053 </h3>
4054 <div id="creation">
4055 <section id="section-11.1.1">
4056 <h4 id="name-order-negotiation-cycle">
4057 <a href="#section-11.1.1" class="section-number selfRef">11.1.1. </a><a href="#name-order-negotiation-cycle" class="section-name selfRef">Order Negotiation Cycle</a>
4058 </h4>
4059 <p id="section-11.1.1-1">To place a PQO, the client first
4060 initiates a local quotation order object identified by a unique
4061 identifier assigned by the client (Client Order Identifier). The
4062 state of the quotation order is set to "Created". The client then
4063 generates a QUOTATION request that includes the assigned
4064 identifier, possibly an expected response time, a Transaction-ID,
4065 and a requested service (e.g., Requested CPD). The client may include additional Information Elements
4066 such as Customer Description or Negotiation Options.<a href="#section-11.1.1-1" class="pilcrow">¶</a></p>
4067 <p id="section-11.1.1-2">The client may be configured to not enforce negotiation checks on
4068 EXPECTED_OFFER_TIME; if so, the client should either not include
4069 the EXPECTED_RESPONSE_TIME attribute in the PQO or it should set
4070 the attribute to infinite.<a href="#section-11.1.1-2" class="pilcrow">¶</a></p>
4071 <p id="section-11.1.1-3">Once the request is sent to the server, the state of the request
4072 is set to "PQOSent", and if a response time is included in
4073 the quotation order, a timer is set to the expiration time as included in
4074 the QUOTATION request. The client also maintains a copy of the CPNP
4075 session entry details used to generate the QUOTATION request. The
4076 CPNP client must listen on the same port number that it used to send
4077 the QUOTATION request.<a href="#section-11.1.1-3" class="pilcrow">¶</a></p>
4078 <p id="section-11.1.1-4">If no answer is received from the server before the
4079 retransmission timer expires (i.e., RETRANS_TIMER, <a href="#timers" class="xref">Section 8.5</a>), the client retransmits the message until
4080 maximum retry is reached (e.g., three times). The same sequence number
4081 is used for retransmitted packets.<a href="#section-11.1.1-4" class="pilcrow">¶</a></p>
4082 <p id="section-11.1.1-5">If a FAIL message is received, the client may decide to issue
4083 another (corrected) request towards the same server, cancel the
4084 local order, or contact another server. The behavior of the client
4085 depends on the error code returned by the server in the FAIL
4086 message.<a href="#section-11.1.1-5" class="pilcrow">¶</a></p>
4087 <p id="section-11.1.1-6">If a PROCESSING message matching the CPNP session entry (<a href="#session" class="xref">Section 8.3</a>) is received, the client updates the CPNP
4088 session entry with the PROVIDER_ORDER_IDENTIFIER information. If
4089 the client does not accept the expected offer time that may have
4090 been indicated in the PROCESSING message, the client may decide to
4091 cancel the quotation order. If the client accepts the
4092 EXPECTED_OFFER_TIME, it changes the state of the order to
4093 "ServerProcessing" and sets a timer to the value of
4094 EXPECTED_OFFER_TIME. If no offer is made before the timer expires,
4095 the client changes the state of the order to "Cancelled".<a href="#section-11.1.1-6" class="pilcrow">¶</a></p>
4096 <p id="section-11.1.1-7">As a response to a time extension request (conveyed in a
4097 PROCESSING message that included a new EXPECTED_OFFER_TIME), the
4098 client may either grant this extension by issuing an ACK message or reject
4099 the time extension by issuing a FAIL message with a status code set to
4100 "More Time Rejected".<a href="#section-11.1.1-7" class="pilcrow">¶</a></p>
4101 <p id="section-11.1.1-8">If an OFFER message matching the CPNP session entry is received,
4102 the client checks if a PROCESSING message having the same
4103 PROVIDER_ORDER_IDENTIFIER has been received from the server. If
4104 a PROCESSING message was already received for the same order, but the
4105 PROVIDER_ORDER_IDENTIFIER does not match the identifier included
4106 in the OFFER message, the client silently ignores the message. If a
4107 PROCESSING message with the same PROVIDER_ORDER_IDENTIFIER was
4108 already received and matches the CPNP transaction identifier, the
4109 client changes the state of the order to "OfferReceived" and sets a
4110 timer to the value of VALIDITY_OFFER_TIME indicated in the OFFER
4111 message.<a href="#section-11.1.1-8" class="pilcrow">¶</a></p>
4112 <p id="section-11.1.1-9">If an offer is received from the server (i.e., as documented in
4113 an OFFER message), the client may accept or reject the offer. The
4114 client accepts the offer by generating an ACCEPT message that
4115 confirms that the client agrees to subscribe to the offer documented
4116 in the OFFER message; the state of the order is passed to
4117 "AcceptSent". The transaction is terminated if an ACK message is
4118 received from the server. If no ACK is received from the server, the
4119 client proceeds with the retransmission of the ACCEPT message until
4120 the maximum retry is reached (<a href="#retrans" class="xref">Section 11.4</a>).<a href="#section-11.1.1-9" class="pilcrow">¶</a></p>
4121 <p id="section-11.1.1-10">The client may also decide to reject the offer by sending a
4122 DECLINE message. The state of the order is set by the client to
4123 "Cancelled". If an offer is not acceptable to the client, the client
4124 may decide to contact a new server or submit another order to the
4125 same server. Guidelines to issue an updated order or terminate the
4126 negotiation are specific to the client.<a href="#section-11.1.1-10" class="pilcrow">¶</a></p>
4127 <p id="section-11.1.1-11">An order can be activated (or deactivated) using the ACTIVATE
4128 message or other accepted activation means (<span><a href="https://www.rfc-editor.org/rfc/rfc7297#section-3.11" class="relref">Section 3.11</a> of [<a href="#RFC7297" class="xref">RFC7297</a>]</span>).<a href="#section-11.1.1-11" class="pilcrow">¶</a></p>
4129 </section>
4130 </div>
4131 <div id="corw">
4132 <section id="section-11.1.2">
4133 <h4 id="name-order-withdrawal-cycle">
4134 <a href="#section-11.1.2" class="section-number selfRef">11.1.2. </a><a href="#name-order-withdrawal-cycle" class="section-name selfRef">Order Withdrawal Cycle</a>
4135 </h4>
4136 <p id="section-11.1.2-1">A client may withdraw a completed order. This is achieved by
4137 issuing a WITHDRAW message. This message must include the Customer Order
4138 Identifier, Provider Order Identifier, and Nonce returned during the order
4139 negotiation cycle, as specified in <a href="#creation" class="xref">Section 11.1.1</a>.<a href="#section-11.1.2-1" class="pilcrow">¶</a></p>
4140 <p id="section-11.1.2-2">If no ACK is received from the server, the client proceeds with
4141 the retransmission of the message. If no ACK is received after the
4142 maximum retry is exhausted, the client should log the information
4143 and must send an alarm to the administrator. If there is no specific
4144 instruction from the administrator, the client should schedule
4145 another Withdrawal cycle. The client must not retry this Withdrawal
4146 cycle more frequently than every 300 seconds and must not retry more
4147 frequently than every 60 seconds.<a href="#section-11.1.2-2" class="pilcrow">¶</a></p>
4148 </section>
4149 </div>
4150 <div id="cordu">
4151 <section id="section-11.1.3">
4152 <h4 id="name-order-update-cycle">
4153 <a href="#section-11.1.3" class="section-number selfRef">11.1.3. </a><a href="#name-order-update-cycle" class="section-name selfRef">Order Update Cycle</a>
4154 </h4>
4155 <p id="section-11.1.3-1">A client may update a completed order. This is achieved by
4156 issuing an UPDATE message. This message must include the Customer Order
4157 Identifier, Provider Order Identifier, and Nonce returned during the
4158 order negotiation cycle specified in <a href="#creation" class="xref">Section 11.1.1</a>. The client must include in the UPDATE
4159 message an Updated CPD with the requested changes.<a href="#section-11.1.3-1" class="pilcrow">¶</a></p>
4160 <p id="section-11.1.3-2">The subsequent message exchange is similar to what is documented in
4161 <a href="#creation" class="xref">Section 11.1.1</a>.<a href="#section-11.1.3-2" class="pilcrow">¶</a></p>
4162 </section>
4163 </div>
4164 </section>
4165 <section id="section-11.2">
4166 <h3 id="name-server-behavior">
4167 <a href="#section-11.2" class="section-number selfRef">11.2. </a><a href="#name-server-behavior" class="section-name selfRef">Server Behavior</a>
4168 </h3>
4169 <div id="handling">
4170 <section id="section-11.2.1">
4171 <h4 id="name-order-processing">
4172 <a href="#section-11.2.1" class="section-number selfRef">11.2.1. </a><a href="#name-order-processing" class="section-name selfRef">Order Processing</a>
4173 </h4>
4174 <p id="section-11.2.1-1">Upon receipt of a QUOTATION message from a client, the server
4175 sets a CPNP session, stores the Transaction-ID, and generates a Provider
4176 Order Identifier. Once preliminary validation checks are completed
4177 (<a href="#validation" class="xref">Section 10</a>), the server may return a
4178 PROCESSING message to inform the client that the quotation order is
4179 received and it is under processing; the server may include an
4180 expected offer time to notify the client by when an offer will be
4181 proposed. An order with state "AwaitingProcessing" is created by the
4182 server. The server runs its decision-making process to decide which
4183 offer it can make to honor the received order. The offer should be
4184 made before the expected offer time expires.<a href="#section-11.2.1-1" class="pilcrow">¶</a></p>
4185 <p id="section-11.2.1-2">If the server cannot make an offer, it sends backs a FAIL message
4186 with the appropriate error code (<a href="#fail" class="xref">Section 9.2.10</a>).<a href="#section-11.2.1-2" class="pilcrow">¶</a></p>
4187 <p id="section-11.2.1-3">If the server requires more negotiation time, it must send a
4188 PROCESSING message with a new EXPECTED_OFFER_TIME. The client may
4189 grant this extension by issuing an ACK message or reject the time
4190 extension by issuing a FAIL message with the status code set to "More Time
4191 Rejected". If the client doesn't grant more time, the server must
4192 answer before the initial expected offer time; otherwise, the client
4193 will decline the quotation order.<a href="#section-11.2.1-3" class="pilcrow">¶</a></p>
4194 <p id="section-11.2.1-4">If the server can honor the request, or if it can make an offer that
4195 meets only some of the requirements, it creates an OFFER message.
4196 The server must indicate the Transaction-ID, the Customer Order
4197 Identifier as indicated in the QUOTATION message, and the Provider
4198 Order Identifier generated for this order. The server must also
4199 include the Nonce and the offered service document (e.g., Offered
4200 CPD). The server includes an offer
4201 validity time as well. Once sent to the client, the server changes
4202 the state of the order to "OfferProposed", and a timer set to the
4203 validity time is initiated.<a href="#section-11.2.1-4" class="pilcrow">¶</a></p>
4204 <p id="section-11.2.1-5">If the server determines that additional network resources from
4205 another Network Provider are needed to accommodate a quotation
4206 order, it will create child PQO(s) and will behave as a CPNP client
4207 to negotiate child PQO(s) with possible partnering Providers (see
4208 <a href="#child" class="xref">Figure 7</a>).<a href="#section-11.2.1-5" class="pilcrow">¶</a></p>
4209 <p id="section-11.2.1-6">If no PROCESSING, ACCEPT, or DECLINE message is received before
4210 the expiry of the RETRANS_TIMER, the server resends the same offer
4211 to the client. This procedure is repeated until maximum retry is
4212 reached.<a href="#section-11.2.1-6" class="pilcrow">¶</a></p>
4213 <p id="section-11.2.1-7">If an ACCEPT message is received before the offered validity time
4214 expires, the server proceeds with validation checks as specified in
4215 <a href="#validation" class="xref">Section 10</a>. The state of the corresponding
4216 order is passed to "AcceptReceived". The server sends back an ACK
4217 message to terminate the order processing cycle.<a href="#section-11.2.1-7" class="pilcrow">¶</a></p>
4218 <p id="section-11.2.1-8">If a CANCEL or a DECLINE message is received, the server proceeds with
4219 the cancellation of the order. The state of the order is then passed
4220 to "Cancelled".<a href="#section-11.2.1-8" class="pilcrow">¶</a></p>
4221 </section>
4222 </div>
4223 <div id="sordw">
4224 <section id="section-11.2.2">
4225 <h4 id="name-order-withdrawal">
4226 <a href="#section-11.2.2" class="section-number selfRef">11.2.2. </a><a href="#name-order-withdrawal" class="section-name selfRef">Order Withdrawal</a>
4227 </h4>
4228 <p id="section-11.2.2-1">A client may withdraw a completed order by issuing a WITHDRAW
4229 message. Upon receipt of a WITHDRAW message, the server proceeds
4230 with the validation checks, as specified in <a href="#validation" class="xref">Section 10</a>:<a href="#section-11.2.2-1" class="pilcrow">¶</a></p>
4231 <ul class="normal">
4232 <li class="normal" id="section-11.2.2-2.1">If the checks fail, a FAIL message is sent back to the client
4233 with the appropriate error code (e.g., 1 (Message Validation
4234 Error), 2 (Authentication Required), or 3 (Authorization
4235 Failed)).<a href="#section-11.2.2-2.1" class="pilcrow">¶</a>
4236 </li>
4237 <li class="normal" id="section-11.2.2-2.2">If the checks succeed, the server clears the clauses of the
4238 CPD, changes the state of the
4239 order to "Cancelled", and sends back an ACK message with an
4240 Empty CPD.<a href="#section-11.2.2-2.2" class="pilcrow">¶</a>
4241 </li>
4242 </ul>
4243 </section>
4244 </div>
4245 <div id="sordu">
4246 <section id="section-11.2.3">
4247 <h4 id="name-order-update">
4248 <a href="#section-11.2.3" class="section-number selfRef">11.2.3. </a><a href="#name-order-update" class="section-name selfRef">Order Update</a>
4249 </h4>
4250 <p id="section-11.2.3-1">A client may update an order by issuing an UPDATE message. Upon
4251 receipt of an UPDATE message, the server proceeds with the
4252 validation checks as specified in <a href="#validation" class="xref">Section 10</a>:<a href="#section-11.2.3-1" class="pilcrow">¶</a></p>
4253 <ul class="normal">
4254 <li class="normal" id="section-11.2.3-2.1">If the checks fail, a FAIL message is sent back to the client
4255 with the appropriate error code (e.g., 1 (Message Validation
4256 Error), 2 (Authentication Required), 3 (Authorization Failed),
4257 or 6 (Network Presence Error)).<a href="#section-11.2.3-2.1" class="pilcrow">¶</a>
4258 </li>
4259 <li class="normal" id="section-11.2.3-2.2">The exchange of subsequent messages is similar to what is
4260 specified in <a href="#creation" class="xref">Section 11.1.1</a>. The server should
4261 generate a new Nonce value to be included in the offer made to
4262 the client.<a href="#section-11.2.3-2.2" class="pilcrow">¶</a>
4263 </li>
4264 </ul>
4265 </section>
4266 </div>
4267 </section>
4268 <div id="sq_nu">
4269 <section id="section-11.3">
4270 <h3 id="name-sequence-numbers">
4271 <a href="#section-11.3" class="section-number selfRef">11.3. </a><a href="#name-sequence-numbers" class="section-name selfRef">Sequence Numbers</a>
4272 </h3>
4273 <p id="section-11.3-1">In each transaction, sequence numbers are used to protect the
4274 transaction against replay attacks. Each communicating partner of the
4275 transaction maintains two sequence numbers, one for incoming packets
4276 and one for outgoing packets. When a partner receives a message, it
4277 will check whether the sequence number in the message is larger than
4278 the incoming sequence number maintained locally. If not, the message
4279 will be discarded. If the message is proved to be legitimate, the
4280 value of the incoming sequence number maintained locally will be
4281 replaced by the value of the sequence number in the message. When a
4282 partner sends out a message, it will insert the value of the outgoing
4283 sequence number into the message and increase the outgoing sequence
4284 number maintained locally by 1.<a href="#section-11.3-1" class="pilcrow">¶</a></p>
4285 </section>
4286 </div>
4287 <div id="retrans">
4288 <section id="section-11.4">
4289 <h3 id="name-message-retransmission">
4290 <a href="#section-11.4" class="section-number selfRef">11.4. </a><a href="#name-message-retransmission" class="section-name selfRef">Message Retransmission</a>
4291 </h3>
4292 <p id="section-11.4-1">If a transaction partner sends out a message and does not receive
4293 any expected reply before the retransmission timer expires (i.e.,
4294 RETRANS_TIMER), a transaction partner will try to retransmit the
4295 message. The procedure is reiterated until a maximum retry is reached
4296 (e.g., three times). An exception is the last message (e.g., ACK) sent
4297 from the server in a transaction. After sending this message, the
4298 retransmission timer will be disabled since no additional feedback is
4299 expected.<a href="#section-11.4-1" class="pilcrow">¶</a></p>
4300 <p id="section-11.4-2">In addition, if the partner receives a retransmission of the last
4301 incoming packet it handled, the partner can resend the same answer to
4302 the incoming packet with a limited frequency. If an answer cannot be
4303 generated right after the request is received, the partner needs to
4304 generate a PROCESSING message as the answer.<a href="#section-11.4-2" class="pilcrow">¶</a></p>
4305 <p id="section-11.4-3">To optimize message retransmission, a partner could also store the
4306 last incoming packet and the associated answer. Note that the times of
4307 retransmission could be decided by the local policy, and retransmission
4308 will not cause any change of sequence numbers.<a href="#section-11.4-3" class="pilcrow">¶</a></p>
4309 </section>
4310 </div>
4311 </section>
4312 </div>
4313 <div id="og">
4314 <section id="section-12">
4315 <h2 id="name-some-operational-guidelines">
4316 <a href="#section-12" class="section-number selfRef">12. </a><a href="#name-some-operational-guidelines" class="section-name selfRef">Some Operational Guidelines</a>
4317 </h2>
4318 <section id="section-12.1">
4319 <h3 id="name-cpnp-server-logging">
4320 <a href="#section-12.1" class="section-number selfRef">12.1. </a><a href="#name-cpnp-server-logging" class="section-name selfRef">CPNP Server Logging</a>
4321 </h3>
4322 <p id="section-12.1-1">The CPNP server should be configurable to log various events and
4323 associated information. Such information may include the following:<a href="#section-12.1-1" class="pilcrow">¶</a></p>
4324 <ul class="normal">
4325 <li class="normal" id="section-12.1-2.1">Client's IP address<a href="#section-12.1-2.1" class="pilcrow">¶</a>
4326 </li>
4327 <li class="normal" id="section-12.1-2.2">Any event change (e.g., new quotation order, offer sent, order
4328 confirmation, order cancellation, order withdrawal, etc.)<a href="#section-12.1-2.2" class="pilcrow">¶</a>
4329 </li>
4330 <li class="normal" id="section-12.1-2.3">Timestamp<a href="#section-12.1-2.3" class="pilcrow">¶</a>
4331 </li>
4332 </ul>
4333 <p id="section-12.1-3">The exact logging details are deployment specific.<a href="#section-12.1-3" class="pilcrow">¶</a></p>
4334 </section>
4335 <section id="section-12.2">
4336 <h3 id="name-business-guidelines-and-obj">
4337 <a href="#section-12.2" class="section-number selfRef">12.2. </a><a href="#name-business-guidelines-and-obj" class="section-name selfRef">Business Guidelines and Objectives</a>
4338 </h3>
4339 <p id="section-12.2-1">The CPNP server can operate in the following modes:<a href="#section-12.2-1" class="pilcrow">¶</a></p>
4340 <span class="break"></span><dl class="dlNewline" id="section-12.2-2">
4341 <dt id="section-12.2-2.1">Fully automated mode: </dt>
4342 <dd style="margin-left: 1.5em" id="section-12.2-2.2">The CPNP server
4343 is provisioned with a set of business guidelines and objectives
4344 that will be used as an input to the decision-making process. The
4345 CPNP server will service received orders that fall into these
4346 business guidelines; otherwise, requests will be escalated to an
4347 administrator that will formally validate or invalidate an order
4348 request. The set of policies to be configured to the CPNP server
4349 are specific to each administrative entity managing a CPNP
4350 server.<a href="#section-12.2-2.2" class="pilcrow">¶</a>
4351 </dd>
4352 <dd class="break"></dd>
4353 <dt id="section-12.2-2.3">Administrative-based mode: </dt>
4354 <dd style="margin-left: 1.5em" id="section-12.2-2.4">This mode
4355 assumes some or all of the CPNP server's operations are subject to a
4356 formal administrative validation. CPNP events will trigger
4357 appropriate validation requests that will be forwarded to the
4358 contact person(s) or department that is responsible for
4359 validating the orders. Administrative validation messages are
4360 relayed using another protocol (e.g., SMTP) or a dedicated
4361 tool.<a href="#section-12.2-2.4" class="pilcrow">¶</a>
4362 </dd>
4363 <dd class="break"></dd>
4364 </dl>
4365 <p id="section-12.2-3">Business guidelines are local to each administrative entity.
4366 How validation requests are presented to an administrator are out of
4367 scope of this document; each administrative entity may decide the
4368 appropriate mechanism to enable for that purpose.<a href="#section-12.2-3" class="pilcrow">¶</a></p>
4369 </section>
4370 </section>
4371 </div>
4372 <div id="Security">
4373 <section id="section-13">
4374 <h2 id="name-security-considerations">
4375 <a href="#section-13" class="section-number selfRef">13. </a><a href="#name-security-considerations" class="section-name selfRef">Security Considerations</a>
4376 </h2>
4377 <p id="section-13-1">Means to defend the server against denial-of-service attacks must be
4378 enabled. For example, access control lists can be enforced on the
4379 client, the server, or the network in between to allow a trusted client
4380 to communicate with a trusted server.<a href="#section-13-1" class="pilcrow">¶</a></p>
4381 <p id="section-13-2">The client and the server must be mutually authenticated.
4382 Authenticated encryption must be used for data confidentiality and
4383 message integrity.<a href="#section-13-2" class="pilcrow">¶</a></p>
4384 <p id="section-13-3">The protocol does not provide security mechanisms to protect the
4385 confidentiality and integrity of the packets transported between the
4386 client and the server. An underlying security protocol such as (e.g.,
4387 Datagram Transport Layer Security (DTLS) <span>[<a href="#RFC6347" class="xref">RFC6347</a>]</span>,
4388 Transport Layer Security (TLS) <span>[<a href="#RFC8446" class="xref">RFC8446</a>]</span>) must be
4389 used to protect the integrity and confidentiality of protocol messages.
4390 In this case, if it is possible to provide automated key management
4391 (<span><a href="https://www.rfc-editor.org/rfc/rfc4107#section-2.1" class="relref">Section 2.1</a> of [<a href="#RFC4107" class="xref">RFC4107</a>]</span>)
4392 and associate each transaction with a different key, inter-transaction
4393 replay attacks can naturally be addressed. If the client and the server
4394 use a single key, an additional mechanism should be provided to protect against
4395 inter-transaction replay attacks between them. Clients must implement
4396 DTLS record replay detection (<span><a href="https://www.rfc-editor.org/rfc/rfc6347#section-3.3" class="relref">Section 3.3</a> of [<a href="#RFC6347" class="xref">RFC6347</a>]</span>) or an equivalent mechanism to protect against
4397 replay attacks.<a href="#section-13-3" class="pilcrow">¶</a></p>
4398 <p id="section-13-4">DTLS and TLS with a cipher suite offering confidentiality protection
4399 and the guidance given in <span>[<a href="#RFC7525" class="xref">RFC7525</a>]</span> must be
4400 followed to avoid attacks on (D)TLS.<a href="#section-13-4" class="pilcrow">¶</a></p>
4401 <p id="section-13-5">The client must silently discard CPNP responses received from unknown
4402 CPNP servers. The use of a randomly generated Transaction-ID makes it
4403 hard to forge a response from a server with a spoofed IP address
4404 belonging to a legitimate CPNP server. Furthermore, CPNP demands that
4405 messages from the server must include the correct identifiers of the
4406 orders. Two order identifiers are used: one generated by the client and
4407 a second one generated by the server. Both the CPNP client and server
4408 maintain the local identifier they assigned and the one assigned by the
4409 peer for a given order. Means to detect swapping of these identifiers
4410 (even when such swapping occurs inadvertently at the client or the
4411 server) should be enabled by CPNP clients/servers. For example, the CPNP
4412 server should not assign a Provider agreement identifier that is equal
4413 to a Customer agreement identifier used by the CPNP client.<a href="#section-13-5" class="pilcrow">¶</a></p>
4414 <p id="section-13-6">The Provider must enforce the means to protect privacy-related
4415 information included in the documents (see <a href="#cpd" class="xref">Section 8.7</a>)
4416 exchanged in CPNP messages <span>[<a href="#RFC6462" class="xref">RFC6462</a>]</span>. In
4417 particular, this information must not be revealed to external parties
4418 without the consent of Customers. Providers should enforce policies to
4419 make Customer fingerprinting difficult to achieve (e.g., in a recursion
4420 request). For more discussion about privacy, refer to <span>[<a href="#RFC6462" class="xref">RFC6462</a>]</span>
4421 <span>[<a href="#RFC6973" class="xref">RFC6973</a>]</span>.<a href="#section-13-6" class="pilcrow">¶</a></p>
4422 <p id="section-13-7">The Nonce and the Transaction-ID attributes provide sufficient
4423 randomness and can effectively tolerate attacks raised by off-path
4424 adversaries, who do not have the capability of eavesdropping and
4425 intercepting the packets transported between the client and the server.
4426 Only authorized clients must be able to modify accepted CPNP orders. The
4427 use of a randomly generated Nonce by the server makes it hard to modify
4428 an agreement on behalf of a malicious third party.<a href="#section-13-7" class="pilcrow">¶</a></p>
4429 </section>
4430 </div>
4431 <div id="IANA">
4432 <section id="section-14">
4433 <h2 id="name-iana-considerations">
4434 <a href="#section-14" class="section-number selfRef">14. </a><a href="#name-iana-considerations" class="section-name selfRef">IANA Considerations</a>
4435 </h2>
4436 <p id="section-14-1">This document has no IANA actions.<a href="#section-14-1" class="pilcrow">¶</a></p>
4437 </section>
4438 </div>
4439 <section id="section-15">
4440 <h2 id="name-references">
4441 <a href="#section-15" class="section-number selfRef">15. </a><a href="#name-references" class="section-name selfRef">References</a>
4442 </h2>
4443 <section id="section-15.1">
4444 <h3 id="name-normative-references">
4445 <a href="#section-15.1" class="section-number selfRef">15.1. </a><a href="#name-normative-references" class="section-name selfRef">Normative References</a>
4446 </h3>
4447 <dl class="references">
4448 <dt id="RFC3339">[RFC3339]</dt>
4449 <dd>
4450 <span class="refAuthor">Klyne, G.</span><span class="refAuthor"> and C. Newman</span>, <span class="refTitle">"Date and Time on the Internet: Timestamps"</span>, <span class="seriesInfo">RFC 3339</span>, <span class="seriesInfo">DOI 10.17487/RFC3339</span>, <time datetime="2002-07" class="refDate">July 2002</time>, <span>&lt;<a href="https://www.rfc-editor.org/info/rfc3339">https://www.rfc-editor.org/info/rfc3339</a>&gt;</span>. </dd>
4451 <dd class="break"></dd>
4452 <dt id="RFC4086">[RFC4086]</dt>
4453 <dd>
4454 <span class="refAuthor">Eastlake 3rd, D.</span><span class="refAuthor">, Schiller, J.</span><span class="refAuthor">, and S. Crocker</span>, <span class="refTitle">"Randomness Requirements for Security"</span>, <span class="seriesInfo">BCP 106</span>, <span class="seriesInfo">RFC 4086</span>, <span class="seriesInfo">DOI 10.17487/RFC4086</span>, <time datetime="2005-06" class="refDate">June 2005</time>, <span>&lt;<a href="https://www.rfc-editor.org/info/rfc4086">https://www.rfc-editor.org/info/rfc4086</a>&gt;</span>. </dd>
4455 <dd class="break"></dd>
4456 <dt id="RFC5511">[RFC5511]</dt>
4457 <dd>
4458 <span class="refAuthor">Farrel, A.</span>, <span class="refTitle">"Routing Backus-Naur Form (RBNF): A Syntax Used to Form Encoding Rules in Various Routing Protocol Specifications"</span>, <span class="seriesInfo">RFC 5511</span>, <span class="seriesInfo">DOI 10.17487/RFC5511</span>, <time datetime="2009-04" class="refDate">April 2009</time>, <span>&lt;<a href="https://www.rfc-editor.org/info/rfc5511">https://www.rfc-editor.org/info/rfc5511</a>&gt;</span>. </dd>
4459 <dd class="break"></dd>
4460 <dt id="RFC6347">[RFC6347]</dt>
4461 <dd>
4462 <span class="refAuthor">Rescorla, E.</span><span class="refAuthor"> and N. Modadugu</span>, <span class="refTitle">"Datagram Transport Layer Security Version 1.2"</span>, <span class="seriesInfo">RFC 6347</span>, <span class="seriesInfo">DOI 10.17487/RFC6347</span>, <time datetime="2012-01" class="refDate">January 2012</time>, <span>&lt;<a href="https://www.rfc-editor.org/info/rfc6347">https://www.rfc-editor.org/info/rfc6347</a>&gt;</span>. </dd>
4463 <dd class="break"></dd>
4464 <dt id="RFC7297">[RFC7297]</dt>
4465 <dd>
4466 <span class="refAuthor">Boucadair, M.</span><span class="refAuthor">, Jacquenet, C.</span><span class="refAuthor">, and N. Wang</span>, <span class="refTitle">"IP Connectivity Provisioning Profile (CPP)"</span>, <span class="seriesInfo">RFC 7297</span>, <span class="seriesInfo">DOI 10.17487/RFC7297</span>, <time datetime="2014-07" class="refDate">July 2014</time>, <span>&lt;<a href="https://www.rfc-editor.org/info/rfc7297">https://www.rfc-editor.org/info/rfc7297</a>&gt;</span>. </dd>
4467 <dd class="break"></dd>
4468 <dt id="RFC7525">[RFC7525]</dt>
4469 <dd>
4470 <span class="refAuthor">Sheffer, Y.</span><span class="refAuthor">, Holz, R.</span><span class="refAuthor">, and P. Saint-Andre</span>, <span class="refTitle">"Recommendations for Secure Use of Transport Layer Security (TLS) and Datagram Transport Layer Security (DTLS)"</span>, <span class="seriesInfo">BCP 195</span>, <span class="seriesInfo">RFC 7525</span>, <span class="seriesInfo">DOI 10.17487/RFC7525</span>, <time datetime="2015-05" class="refDate">May 2015</time>, <span>&lt;<a href="https://www.rfc-editor.org/info/rfc7525">https://www.rfc-editor.org/info/rfc7525</a>&gt;</span>. </dd>
4471 <dd class="break"></dd>
4472 <dt id="RFC8446">[RFC8446]</dt>
4473 <dd>
4474 <span class="refAuthor">Rescorla, E.</span>, <span class="refTitle">"The Transport Layer Security (TLS) Protocol Version 1.3"</span>, <span class="seriesInfo">RFC 8446</span>, <span class="seriesInfo">DOI 10.17487/RFC8446</span>, <time datetime="2018-08" class="refDate">August 2018</time>, <span>&lt;<a href="https://www.rfc-editor.org/info/rfc8446">https://www.rfc-editor.org/info/rfc8446</a>&gt;</span>. </dd>
4475 <dd class="break"></dd>
4476 </dl>
4477 </section>
4478 <section id="section-15.2">
4479 <h3 id="name-informative-references">
4480 <a href="#section-15.2" class="section-number selfRef">15.2. </a><a href="#name-informative-references" class="section-name selfRef">Informative References</a>
4481 </h3>
4482 <dl class="references">
4483 <dt id="AGAVE">[AGAVE]</dt>
4484 <dd>
4485 <span class="refAuthor">Boucadair, M.</span><span class="refAuthor">, Georgatsos, P.</span><span class="refAuthor">, Wang, N.</span><span class="refAuthor">, Griffin, D.</span><span class="refAuthor">, Pavlou, G.</span><span class="refAuthor">, Howarth, M.</span><span class="refAuthor">, and A. Elizondo</span>, <span class="refTitle">"The AGAVE Approach for Network Virtualization: Differentiated Services Delivery"</span>, <span class="refContent">Annals of Telecommunication, Volume 64, 277-288</span>, <span class="seriesInfo">DOI 10.1007/s12243-009-0103-4</span>, <time datetime="2009-04" class="refDate">April 2009</time>, <span>&lt;<a href="https://rd.springer.com/article/10.1007/s12243-009-0103-4">https://rd.springer.com/article/10.1007/s12243-009-0103-4</a>&gt;</span>. </dd>
4486 <dd class="break"></dd>
4487 <dt id="I-D.nguyen-rap-cops-sls">[COPS-SLS]</dt>
4488 <dd>
4489 <span class="refAuthor">Nguyen, T.</span>, <span class="refTitle">"COPS Usage for SLS negotiation (COPS-SLS)"</span>, <span class="refContent">Work in Progress</span>, <span class="seriesInfo">Internet-Draft, draft-nguyen-rap-cops-sls-03</span>, <time datetime="2002-07-05" class="refDate">5 July 2002</time>, <span>&lt;<a href="https://tools.ietf.org/html/draft-nguyen-rap-cops-sls-03">https://tools.ietf.org/html/draft-nguyen-rap-cops-sls-03</a>&gt;</span>. </dd>
4490 <dd class="break"></dd>
4491 <dt id="I-D.itsumo-dsnp">[DSNP]</dt>
4492 <dd>
4493 <span class="refAuthor">Chen, J.</span>, <span class="refTitle">"Dynamic Service Negotiation Protocol (DSNP)"</span>, <span class="refContent">Work in Progress</span>, <span class="seriesInfo">Internet-Draft, draft-itsumo-dsnp-03</span>, <time datetime="2006-03-02" class="refDate">2 March 2006</time>, <span>&lt;<a href="https://tools.ietf.org/html/draft-itsumo-dsnp-03">https://tools.ietf.org/html/draft-itsumo-dsnp-03</a>&gt;</span>. </dd>
4494 <dd class="break"></dd>
4495 <dt id="ETICS">[ETICS]</dt>
4496 <dd>
4497 <span class="refAuthor">EU FP7 ETICS Project</span>, <span class="refTitle">"Economics and Technologies of Inter-Carrier Services"</span>, <time datetime="2014-01" class="refDate">January 2014</time>, <span>&lt;<a href="https://cordis.europa.eu/project/id/248567">https://cordis.europa.eu/project/id/248567</a>&gt;</span>. </dd>
4498 <dd class="break"></dd>
4499 <dt id="I-D.ietf-opsawg-l2nm">[L2VPN-NETWORK-YANG]</dt>
4500 <dd>
4501 <span class="refAuthor">Barguil, S.</span><span class="refAuthor">, Dios, O. G. D.</span><span class="refAuthor">, Boucadair, M.</span><span class="refAuthor">, Munoz, L. A.</span><span class="refAuthor">, Jalil, L.</span><span class="refAuthor">, and J. Ma</span>, <span class="refTitle">"A Layer 2 VPN Network YANG Model"</span>, <span class="refContent">Work in Progress</span>, <span class="seriesInfo">Internet-Draft, draft-ietf-opsawg-l2nm-00</span>, <time datetime="2020-07-02" class="refDate">2 July 2020</time>, <span>&lt;<a href="https://tools.ietf.org/html/draft-ietf-opsawg-l2nm-00">https://tools.ietf.org/html/draft-ietf-opsawg-l2nm-00</a>&gt;</span>. </dd>
4502 <dd class="break"></dd>
4503 <dt id="I-D.ietf-opsawg-l3sm-l3nm">[L3VPN-NETWORK-YANG]</dt>
4504 <dd>
4505 <span class="refAuthor">Barguil, S.</span><span class="refAuthor">, Dios, O. G. D.</span><span class="refAuthor">, Boucadair, M.</span><span class="refAuthor">, Munoz, L. A.</span><span class="refAuthor">, and A. Aguado</span>, <span class="refTitle">"A Layer 3 VPN Network YANG Model"</span>, <span class="refContent">Work in Progress</span>, <span class="seriesInfo">Internet-Draft, draft-ietf-opsawg-l3sm-l3nm-05</span>, <time datetime="2020-10-16" class="refDate">16 October 2020</time>, <span>&lt;<a href="https://tools.ietf.org/html/draft-ietf-opsawg-l3sm-l3nm-05">https://tools.ietf.org/html/draft-ietf-opsawg-l3sm-l3nm-05</a>&gt;</span>. </dd>
4506 <dd class="break"></dd>
4507 <dt id="I-D.boucadair-lisp-idr-ms-discovery">[LISP-MS-DISCOVERY]</dt>
4508 <dd>
4509 <span class="refAuthor">Boucadair, M.</span><span class="refAuthor"> and C. Jacquenet</span>, <span class="refTitle">"LISP Mapping Service Discovery at Large"</span>, <span class="refContent">Work in Progress</span>, <span class="seriesInfo">Internet-Draft, draft-boucadair-lisp-idr-ms-discovery-01</span>, <time datetime="2016-03-09" class="refDate">9 March 2016</time>, <span>&lt;<a href="https://tools.ietf.org/html/draft-boucadair-lisp-idr-ms-discovery-01">https://tools.ietf.org/html/draft-boucadair-lisp-idr-ms-discovery-01</a>&gt;</span>. </dd>
4510 <dd class="break"></dd>
4511 <dt id="I-D.geng-netslices-architecture">[NETSLICES-ARCH]</dt>
4512 <dd>
4513 <span class="refAuthor">Geng, L.</span><span class="refAuthor">, Dong, J.</span><span class="refAuthor">, Bryant, S.</span><span class="refAuthor">, Makhijani, K.</span><span class="refAuthor">, Galis, A.</span><span class="refAuthor">, Foy, X. D.</span><span class="refAuthor">, and S. Kuklinski</span>, <span class="refTitle">"Network Slicing Architecture"</span>, <span class="refContent">Work in Progress</span>, <span class="seriesInfo">Internet-Draft, draft-geng-netslices-architecture-02</span>, <time datetime="2017-07-03" class="refDate">3 July 2017</time>, <span>&lt;<a href="https://tools.ietf.org/html/draft-geng-netslices-architecture-02">https://tools.ietf.org/html/draft-geng-netslices-architecture-02</a>&gt;</span>. </dd>
4514 <dd class="break"></dd>
4515 <dt id="RFC2782">[RFC2782]</dt>
4516 <dd>
4517 <span class="refAuthor">Gulbrandsen, A.</span><span class="refAuthor">, Vixie, P.</span><span class="refAuthor">, and L. Esibov</span>, <span class="refTitle">"A DNS RR for specifying the location of services (DNS SRV)"</span>, <span class="seriesInfo">RFC 2782</span>, <span class="seriesInfo">DOI 10.17487/RFC2782</span>, <time datetime="2000-02" class="refDate">February 2000</time>, <span>&lt;<a href="https://www.rfc-editor.org/info/rfc2782">https://www.rfc-editor.org/info/rfc2782</a>&gt;</span>. </dd>
4518 <dd class="break"></dd>
4519 <dt id="RFC3084">[RFC3084]</dt>
4520 <dd>
4521 <span class="refAuthor">Chan, K.</span><span class="refAuthor">, Seligson, J.</span><span class="refAuthor">, Durham, D.</span><span class="refAuthor">, Gai, S.</span><span class="refAuthor">, McCloghrie, K.</span><span class="refAuthor">, Herzog, S.</span><span class="refAuthor">, Reichmeyer, F.</span><span class="refAuthor">, Yavatkar, R.</span><span class="refAuthor">, and A. Smith</span>, <span class="refTitle">"COPS Usage for Policy Provisioning (COPS-PR)"</span>, <span class="seriesInfo">RFC 3084</span>, <span class="seriesInfo">DOI 10.17487/RFC3084</span>, <time datetime="2001-03" class="refDate">March 2001</time>, <span>&lt;<a href="https://www.rfc-editor.org/info/rfc3084">https://www.rfc-editor.org/info/rfc3084</a>&gt;</span>. </dd>
4522 <dd class="break"></dd>
4523 <dt id="RFC4026">[RFC4026]</dt>
4524 <dd>
4525 <span class="refAuthor">Andersson, L.</span><span class="refAuthor"> and T. Madsen</span>, <span class="refTitle">"Provider Provisioned Virtual Private Network (VPN) Terminology"</span>, <span class="seriesInfo">RFC 4026</span>, <span class="seriesInfo">DOI 10.17487/RFC4026</span>, <time datetime="2005-03" class="refDate">March 2005</time>, <span>&lt;<a href="https://www.rfc-editor.org/info/rfc4026">https://www.rfc-editor.org/info/rfc4026</a>&gt;</span>. </dd>
4526 <dd class="break"></dd>
4527 <dt id="RFC4107">[RFC4107]</dt>
4528 <dd>
4529 <span class="refAuthor">Bellovin, S.</span><span class="refAuthor"> and R. Housley</span>, <span class="refTitle">"Guidelines for Cryptographic Key Management"</span>, <span class="seriesInfo">BCP 107</span>, <span class="seriesInfo">RFC 4107</span>, <span class="seriesInfo">DOI 10.17487/RFC4107</span>, <time datetime="2005-06" class="refDate">June 2005</time>, <span>&lt;<a href="https://www.rfc-editor.org/info/rfc4107">https://www.rfc-editor.org/info/rfc4107</a>&gt;</span>. </dd>
4530 <dd class="break"></dd>
4531 <dt id="RFC4176">[RFC4176]</dt>
4532 <dd>
4533 <span class="refAuthor">El Mghazli, Y., Ed.</span><span class="refAuthor">, Nadeau, T.</span><span class="refAuthor">, Boucadair, M.</span><span class="refAuthor">, Chan, K.</span><span class="refAuthor">, and A. Gonguet</span>, <span class="refTitle">"Framework for Layer 3 Virtual Private Networks (L3VPN) Operations and Management"</span>, <span class="seriesInfo">RFC 4176</span>, <span class="seriesInfo">DOI 10.17487/RFC4176</span>, <time datetime="2005-10" class="refDate">October 2005</time>, <span>&lt;<a href="https://www.rfc-editor.org/info/rfc4176">https://www.rfc-editor.org/info/rfc4176</a>&gt;</span>. </dd>
4534 <dd class="break"></dd>
4535 <dt id="RFC6125">[RFC6125]</dt>
4536 <dd>
4537 <span class="refAuthor">Saint-Andre, P.</span><span class="refAuthor"> and J. Hodges</span>, <span class="refTitle">"Representation and Verification of Domain-Based Application Service Identity within Internet Public Key Infrastructure Using X.509 (PKIX) Certificates in the Context of Transport Layer Security (TLS)"</span>, <span class="seriesInfo">RFC 6125</span>, <span class="seriesInfo">DOI 10.17487/RFC6125</span>, <time datetime="2011-03" class="refDate">March 2011</time>, <span>&lt;<a href="https://www.rfc-editor.org/info/rfc6125">https://www.rfc-editor.org/info/rfc6125</a>&gt;</span>. </dd>
4538 <dd class="break"></dd>
4539 <dt id="RFC6241">[RFC6241]</dt>
4540 <dd>
4541 <span class="refAuthor">Enns, R., Ed.</span><span class="refAuthor">, Bjorklund, M., Ed.</span><span class="refAuthor">, Schoenwaelder, J., Ed.</span><span class="refAuthor">, and 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>
4542 <dd class="break"></dd>
4543 <dt id="RFC6462">[RFC6462]</dt>
4544 <dd>
4545 <span class="refAuthor">Cooper, A.</span>, <span class="refTitle">"Report from the Internet Privacy Workshop"</span>, <span class="seriesInfo">RFC 6462</span>, <span class="seriesInfo">DOI 10.17487/RFC6462</span>, <time datetime="2012-01" class="refDate">January 2012</time>, <span>&lt;<a href="https://www.rfc-editor.org/info/rfc6462">https://www.rfc-editor.org/info/rfc6462</a>&gt;</span>. </dd>
4546 <dd class="break"></dd>
4547 <dt id="RFC6574">[RFC6574]</dt>
4548 <dd>
4549 <span class="refAuthor">Tschofenig, H.</span><span class="refAuthor"> and J. Arkko</span>, <span class="refTitle">"Report from the Smart Object Workshop"</span>, <span class="seriesInfo">RFC 6574</span>, <span class="seriesInfo">DOI 10.17487/RFC6574</span>, <time datetime="2012-04" class="refDate">April 2012</time>, <span>&lt;<a href="https://www.rfc-editor.org/info/rfc6574">https://www.rfc-editor.org/info/rfc6574</a>&gt;</span>. </dd>
4550 <dd class="break"></dd>
4551 <dt id="RFC6770">[RFC6770]</dt>
4552 <dd>
4553 <span class="refAuthor">Bertrand, G., Ed.</span><span class="refAuthor">, Stephan, E.</span><span class="refAuthor">, Burbridge, T.</span><span class="refAuthor">, Eardley, P.</span><span class="refAuthor">, Ma, K.</span><span class="refAuthor">, and G. Watson</span>, <span class="refTitle">"Use Cases for Content Delivery Network Interconnection"</span>, <span class="seriesInfo">RFC 6770</span>, <span class="seriesInfo">DOI 10.17487/RFC6770</span>, <time datetime="2012-11" class="refDate">November 2012</time>, <span>&lt;<a href="https://www.rfc-editor.org/info/rfc6770">https://www.rfc-editor.org/info/rfc6770</a>&gt;</span>. </dd>
4554 <dd class="break"></dd>
4555 <dt id="RFC6793">[RFC6793]</dt>
4556 <dd>
4557 <span class="refAuthor">Vohra, Q.</span><span class="refAuthor"> and E. Chen</span>, <span class="refTitle">"BGP Support for Four-Octet Autonomous System (AS) Number Space"</span>, <span class="seriesInfo">RFC 6793</span>, <span class="seriesInfo">DOI 10.17487/RFC6793</span>, <time datetime="2012-12" class="refDate">December 2012</time>, <span>&lt;<a href="https://www.rfc-editor.org/info/rfc6793">https://www.rfc-editor.org/info/rfc6793</a>&gt;</span>. </dd>
4558 <dd class="break"></dd>
4559 <dt id="RFC6830">[RFC6830]</dt>
4560 <dd>
4561 <span class="refAuthor">Farinacci, D.</span><span class="refAuthor">, Fuller, V.</span><span class="refAuthor">, Meyer, D.</span><span class="refAuthor">, and D. Lewis</span>, <span class="refTitle">"The Locator/ID Separation Protocol (LISP)"</span>, <span class="seriesInfo">RFC 6830</span>, <span class="seriesInfo">DOI 10.17487/RFC6830</span>, <time datetime="2013-01" class="refDate">January 2013</time>, <span>&lt;<a href="https://www.rfc-editor.org/info/rfc6830">https://www.rfc-editor.org/info/rfc6830</a>&gt;</span>. </dd>
4562 <dd class="break"></dd>
4563 <dt id="RFC6973">[RFC6973]</dt>
4564 <dd>
4565 <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><span class="refAuthor">, and 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>
4566 <dd class="break"></dd>
4567 <dt id="RFC7049">[RFC7049]</dt>
4568 <dd>
4569 <span class="refAuthor">Bormann, C.</span><span class="refAuthor"> and P. Hoffman</span>, <span class="refTitle">"Concise Binary Object Representation (CBOR)"</span>, <span class="seriesInfo">RFC 7049</span>, <span class="seriesInfo">DOI 10.17487/RFC7049</span>, <time datetime="2013-10" class="refDate">October 2013</time>, <span>&lt;<a href="https://www.rfc-editor.org/info/rfc7049">https://www.rfc-editor.org/info/rfc7049</a>&gt;</span>. </dd>
4570 <dd class="break"></dd>
4571 <dt id="RFC7149">[RFC7149]</dt>
4572 <dd>
4573 <span class="refAuthor">Boucadair, M.</span><span class="refAuthor"> and C. Jacquenet</span>, <span class="refTitle">"Software-Defined Networking: A Perspective from within a Service Provider Environment"</span>, <span class="seriesInfo">RFC 7149</span>, <span class="seriesInfo">DOI 10.17487/RFC7149</span>, <time datetime="2014-03" class="refDate">March 2014</time>, <span>&lt;<a href="https://www.rfc-editor.org/info/rfc7149">https://www.rfc-editor.org/info/rfc7149</a>&gt;</span>. </dd>
4574 <dd class="break"></dd>
4575 <dt id="RFC7215">[RFC7215]</dt>
4576 <dd>
4577 <span class="refAuthor">Jakab, L.</span><span class="refAuthor">, Cabellos-Aparicio, A.</span><span class="refAuthor">, Coras, F.</span><span class="refAuthor">, Domingo-Pascual, J.</span><span class="refAuthor">, and D. Lewis</span>, <span class="refTitle">"Locator/Identifier Separation Protocol (LISP) Network Element Deployment Considerations"</span>, <span class="seriesInfo">RFC 7215</span>, <span class="seriesInfo">DOI 10.17487/RFC7215</span>, <time datetime="2014-04" class="refDate">April 2014</time>, <span>&lt;<a href="https://www.rfc-editor.org/info/rfc7215">https://www.rfc-editor.org/info/rfc7215</a>&gt;</span>. </dd>
4578 <dd class="break"></dd>
4579 <dt id="RFC7491">[RFC7491]</dt>
4580 <dd>
4581 <span class="refAuthor">King, D.</span><span class="refAuthor"> and A. Farrel</span>, <span class="refTitle">"A PCE-Based Architecture for Application-Based Network Operations"</span>, <span class="seriesInfo">RFC 7491</span>, <span class="seriesInfo">DOI 10.17487/RFC7491</span>, <time datetime="2015-03" class="refDate">March 2015</time>, <span>&lt;<a href="https://www.rfc-editor.org/info/rfc7491">https://www.rfc-editor.org/info/rfc7491</a>&gt;</span>. </dd>
4582 <dd class="break"></dd>
4583 <dt id="RFC8040">[RFC8040]</dt>
4584 <dd>
4585 <span class="refAuthor">Bierman, A.</span><span class="refAuthor">, Bjorklund, M.</span><span class="refAuthor">, and K. Watsen</span>, <span class="refTitle">"RESTCONF Protocol"</span>, <span class="seriesInfo">RFC 8040</span>, <span class="seriesInfo">DOI 10.17487/RFC8040</span>, <time datetime="2017-01" class="refDate">January 2017</time>, <span>&lt;<a href="https://www.rfc-editor.org/info/rfc8040">https://www.rfc-editor.org/info/rfc8040</a>&gt;</span>. </dd>
4586 <dd class="break"></dd>
4587 <dt id="RFC8259">[RFC8259]</dt>
4588 <dd>
4589 <span class="refAuthor">Bray, T., Ed.</span>, <span class="refTitle">"The JavaScript Object Notation (JSON) Data Interchange Format"</span>, <span class="seriesInfo">STD 90</span>, <span class="seriesInfo">RFC 8259</span>, <span class="seriesInfo">DOI 10.17487/RFC8259</span>, <time datetime="2017-12" class="refDate">December 2017</time>, <span>&lt;<a href="https://www.rfc-editor.org/info/rfc8259">https://www.rfc-editor.org/info/rfc8259</a>&gt;</span>. </dd>
4590 <dd class="break"></dd>
4591 <dt id="RFC8299">[RFC8299]</dt>
4592 <dd>
4593 <span class="refAuthor">Wu, Q., Ed.</span><span class="refAuthor">, Litkowski, S.</span><span class="refAuthor">, Tomotaki, L.</span><span class="refAuthor">, and K. Ogaki</span>, <span class="refTitle">"YANG Data Model for L3VPN Service Delivery"</span>, <span class="seriesInfo">RFC 8299</span>, <span class="seriesInfo">DOI 10.17487/RFC8299</span>, <time datetime="2018-01" class="refDate">January 2018</time>, <span>&lt;<a href="https://www.rfc-editor.org/info/rfc8299">https://www.rfc-editor.org/info/rfc8299</a>&gt;</span>. </dd>
4594 <dd class="break"></dd>
4595 <dt id="RFC8309">[RFC8309]</dt>
4596 <dd>
4597 <span class="refAuthor">Wu, Q.</span><span class="refAuthor">, Liu, W.</span><span class="refAuthor">, and A. Farrel</span>, <span class="refTitle">"Service Models Explained"</span>, <span class="seriesInfo">RFC 8309</span>, <span class="seriesInfo">DOI 10.17487/RFC8309</span>, <time datetime="2018-01" class="refDate">January 2018</time>, <span>&lt;<a href="https://www.rfc-editor.org/info/rfc8309">https://www.rfc-editor.org/info/rfc8309</a>&gt;</span>. </dd>
4598 <dd class="break"></dd>
4599 <dt id="RFC8329">[RFC8329]</dt>
4600 <dd>
4601 <span class="refAuthor">Lopez, D.</span><span class="refAuthor">, Lopez, E.</span><span class="refAuthor">, Dunbar, L.</span><span class="refAuthor">, Strassner, J.</span><span class="refAuthor">, and R. Kumar</span>, <span class="refTitle">"Framework for Interface to Network Security Functions"</span>, <span class="seriesInfo">RFC 8329</span>, <span class="seriesInfo">DOI 10.17487/RFC8329</span>, <time datetime="2018-02" class="refDate">February 2018</time>, <span>&lt;<a href="https://www.rfc-editor.org/info/rfc8329">https://www.rfc-editor.org/info/rfc8329</a>&gt;</span>. </dd>
4602 <dd class="break"></dd>
4603 <dt id="RFC8466">[RFC8466]</dt>
4604 <dd>
4605 <span class="refAuthor">Wen, B.</span><span class="refAuthor">, Fioccola, G., Ed.</span><span class="refAuthor">, Xie, C.</span><span class="refAuthor">, and L. Jalil</span>, <span class="refTitle">"A YANG Data Model for Layer 2 Virtual Private Network (L2VPN) Service Delivery"</span>, <span class="seriesInfo">RFC 8466</span>, <span class="seriesInfo">DOI 10.17487/RFC8466</span>, <time datetime="2018-10" class="refDate">October 2018</time>, <span>&lt;<a href="https://www.rfc-editor.org/info/rfc8466">https://www.rfc-editor.org/info/rfc8466</a>&gt;</span>. </dd>
4606 <dd class="break"></dd>
4607 <dt id="RFC8597">[RFC8597]</dt>
4608 <dd>
4609 <span class="refAuthor">Contreras, LM.</span><span class="refAuthor">, Bernardos, CJ.</span><span class="refAuthor">, Lopez, D.</span><span class="refAuthor">, Boucadair, M.</span><span class="refAuthor">, and P. Iovanna</span>, <span class="refTitle">"Cooperating Layered Architecture for Software-Defined Networking (CLAS)"</span>, <span class="seriesInfo">RFC 8597</span>, <span class="seriesInfo">DOI 10.17487/RFC8597</span>, <time datetime="2019-05" class="refDate">May 2019</time>, <span>&lt;<a href="https://www.rfc-editor.org/info/rfc8597">https://www.rfc-editor.org/info/rfc8597</a>&gt;</span>. </dd>
4610 <dd class="break"></dd>
4611 <dt id="RNAP">[RNAP]</dt>
4612 <dd>
4613 <span class="refAuthor">Wang, X.</span>, <span class="refTitle">"A Resource Negotiation and Pricing Protocol (RNAP)"</span>, <span>&lt;<a href="http://www.cs.columbia.edu/~xinwang/public/projects/protocol.html">http://www.cs.columbia.edu/~xinwang/public/projects/protocol.html</a>&gt;</span>. </dd>
4614 <dd class="break"></dd>
4615 <dt id="SNAP">[SNAP]</dt>
4616 <dd>
4617 <span class="refAuthor">Czajkowski, K.</span><span class="refAuthor">, Foster, I.</span><span class="refAuthor">, Kesselman, C.</span><span class="refAuthor">, Sander, V.</span><span class="refAuthor">, and S. Tuecke</span>, <span class="refTitle">"SNAP: A Protocol for Negotiating Service Level Agreements and Coordinating Resource Management in Distributed Systems"</span>, <span class="seriesInfo">DOI 10.1.1.19.5907</span>, <time datetime="2002" class="refDate">2002</time>, <span>&lt;<a href="http://citeseerx.ist.psu.edu/viewdoc/summary?doi=10.1.1.19.5907">http://citeseerx.ist.psu.edu/viewdoc/summary?doi=10.1.1.19.5907</a>&gt;</span>. </dd>
4618 <dd class="break"></dd>
4619 <dt id="SrNP">[SrNP]</dt>
4620 <dd>
4621 <span class="refAuthor">Georgatsos, P.</span><span class="refAuthor"> and G. Giannakopoulos</span>, <span class="refTitle">"Service Negotiation Protocol (SrNP)"</span>, <span>&lt;<a href="https://www.ist-tequila.org/presentations/srnp-pipcm.pdf">https://www.ist-tequila.org/presentations/srnp-pipcm.pdf</a>&gt;</span>. </dd>
4622 <dd class="break"></dd>
4623 <dt id="I-D.contreras-teas-slice-nbi">[TEAS-SLICE-NBI]</dt>
4624 <dd>
4625 <span class="refAuthor">Contreras, L. M.</span><span class="refAuthor">, Homma, S.</span><span class="refAuthor">, and J. A. Ordonez-Lucena</span>, <span class="refTitle">"Considerations for defining a Transport Slice NBI"</span>, <span class="refContent">Work in Progress</span>, <span class="seriesInfo">Internet-Draft, draft-contreras-teas-slice-nbi-02</span>, <time datetime="2020-07-13" class="refDate">13 July 2020</time>, <span>&lt;<a href="https://tools.ietf.org/html/draft-contreras-teas-slice-nbi-02">https://tools.ietf.org/html/draft-contreras-teas-slice-nbi-02</a>&gt;</span>. </dd>
4626 <dd class="break"></dd>
4627 </dl>
4628 </section>
4629 </section>
4630 <section id="section-appendix.a">
4631 <h2 id="name-acknowledgements">
4632 <a href="#name-acknowledgements" class="section-name selfRef">Acknowledgements</a>
4633 </h2>
4634 <p id="section-appendix.a-1">Thanks to <span class="contact-name">Diego R. Lopez</span>,
4635 <span class="contact-name">Adrian Farrel</span>, <span class="contact-name">Éric Vyncke</span>,
4636 <span class="contact-name">Eric Kline</span>, and <span class="contact-name">Benjamin Kaduk</span> for the comments.<a href="#section-appendix.a-1" class="pilcrow">¶</a></p>
4637 <p id="section-appendix.a-2">Thanks to those that reviewed this document for publication
4638 in the Independent Stream.<a href="#section-appendix.a-2" class="pilcrow">¶</a></p>
4639 <p id="section-appendix.a-3">Special thanks to <span class="contact-name">Luis Miguel Contreras Murillo</span> for the detailed
4640 review.<a href="#section-appendix.a-3" class="pilcrow">¶</a></p>
4641 </section>
4642 <div id="authors-addresses">
4643 <section id="section-appendix.b">
4644 <h2 id="name-authors-addresses">
4645 <a href="#name-authors-addresses" class="section-name selfRef">Authors' Addresses</a>
4646 </h2>
4647 <address class="vcard">
4648 <div dir="auto" class="left"><span class="fn nameRole">Mohamed Boucadair (<span class="role">editor</span>)</span></div>
4649 <div dir="auto" class="left"><span class="org">Orange</span></div>
4650 <div dir="auto" class="left">
4651 <span class="postal-code">35000</span> <span class="locality">Rennes</span>
4652 </div>
4653 <div dir="auto" class="left"><span class="country-name">France</span></div>
4654 <div class="email">
4655 <span>Email:</span>
4656 <a href="mailto:[email protected]" class="email">[email protected]</a>
4657 </div>
4658 </address>
4659 <address class="vcard">
4660 <div dir="auto" class="left"><span class="fn nameRole">Christian Jacquenet</span></div>
4661 <div dir="auto" class="left"><span class="org">Orange</span></div>
4662 <div dir="auto" class="left">
4663 <span class="postal-code">35000</span> <span class="locality">Rennes</span>
4664 </div>
4665 <div dir="auto" class="left"><span class="country-name">France</span></div>
4666 <div class="email">
4667 <span>Email:</span>
4668 <a href="mailto:[email protected]" class="email">[email protected]</a>
4669 </div>
4670 </address>
4671 <address class="vcard">
4672 <div dir="auto" class="left"><span class="fn nameRole">Dacheng Zhang</span></div>
4673 <div dir="auto" class="left"><span class="org">Huawei Technologies</span></div>
4674 <div class="email">
4675 <span>Email:</span>
4676 <a href="mailto:[email protected]" class="email">[email protected]</a>
4677 </div>
4678 </address>
4679 <address class="vcard">
4680 <div dir="auto" class="left"><span class="fn nameRole">Panos Georgatsos</span></div>
4681 <div dir="auto" class="left"><span class="org">Centre for Research and Innovation Hellas</span></div>
4682 <div dir="auto" class="left"><span class="street-address">78, Filikis Etairias str.</span></div>
4683 <div dir="auto" class="left">
4684 <span class="postal-code">38334</span> <span class="locality">Volos</span>
4685 </div>
4686 <div dir="auto" class="left"><span class="country-name">Greece</span></div>
4687 <div class="tel">
4688 <span>Phone:</span>
4689 <a href="tel:+302421306070" class="tel">+302421306070</a>
4690 </div>
4691 <div class="email">
4692 <span>Email:</span>
4693 <a href="mailto:[email protected]" class="email">[email protected]</a>
4694 </div>
4695 </address>
4696 </section>
4697 </div>
4698 <script>const toc = document.getElementById("toc");
4699 toc.querySelector("h2").addEventListener("click", e => {
4700 toc.classList.toggle("active");
4701 });
4702 toc.querySelector("nav").addEventListener("click", e => {
4703 toc.classList.remove("active");
4704 });
4705 </script>
4706 </body>
4707 </html>