Debian Codegraph @

rfc9168.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 9168: Path Computation Element Communication Protocol (PCEP) Extension for Flow Specification</title>
8 <meta content="Dhruv Dhody" name="author">
9 <meta content="Adrian Farrel" name="author">
10 <meta content="Zhenbin Li" name="author">
11 <meta content='
12 The Path Computation Element (PCE) is a functional component capable of selecting
13 paths through a traffic engineering (TE) network. These paths may be supplied
14 in response to requests for computation or may be unsolicited requests
15 issued by the PCE to network elements. Both approaches use the PCE Communication
16 Protocol (PCEP) to convey the details of the computed path.
17 Traffic flows may be categorized and described using "Flow Specifications". RFC 8955 defines the Flow Specification and describes how Flow Specification
18 components are used to describe traffic flows. RFC 8955 also defines how Flow
19 Specifications may be distributed in BGP to allow specific traffic flows to be
20 associated with routes.
21 This document specifies a set of extensions to PCEP to support dissemination of
22 Flow Specifications. This allows a PCE to indicate what traffic should be placed
23 on each path that it is aware of.
24 The extensions defined in this document include the creation, update, and withdrawal of Flow
25 Specifications via PCEP and can be applied to tunnels initiated by the PCE or to tunnels where
26 control is delegated to the PCE by the Path Computation Client (PCC).
27 Furthermore, a PCC requesting a new path can include
28 Flow Specifications in the request to indicate the purpose of the tunnel allowing the PCE to factor this into the path computation.
29 ' name="description">
30 <meta content="xml2rfc 3.12.0" name="generator">
31 <meta content="PCE" name="keyword">
32 <meta content="FlowSpec" name="keyword">
33 <meta content="Flow Spec" name="keyword">
34 <meta content="9168" name="rfc.number">
35 <!-- Generator version information:
36 xml2rfc 3.12.0
37 Python 3.6.15
38 appdirs 1.4.4
39 ConfigArgParse 1.4.1
40 google-i18n-address 2.4.0
41 html5lib 1.0.1
42 intervaltree 3.0.2
43 Jinja2 2.11.3
44 kitchen 1.2.6
45 lxml 4.4.2
46 pycairo 1.15.1
47 pycountry 19.8.18
48 pyflakes 2.1.1
49 PyYAML 5.4.1
50 requests 2.24.0
51 setuptools 40.5.0
52 six 1.14.0
53 WeasyPrint 52.5
54 -->
55 <link href="rfc9168.xml" rel="alternate" type="application/rfc+xml">
56 <link href="#copyright" rel="license">
57 <style type="text/css">/*
58
59 NOTE: Changes at the bottom of this file overrides some earlier settings.
60
61 Once the style has stabilized and has been adopted as an official RFC style,
62 this can be consolidated so that style settings occur only in one place, but
63 for now the contents of this file consists first of the initial CSS work as
64 provided to the RFC Formatter (xml2rfc) work, followed by itemized and
65 commented changes found necssary during the development of the v3
66 formatters.
67
68 */
69
70 /* fonts */
71 @import url('https://fonts.googleapis.com/css?family=Noto+Sans'); /* Sans-serif */
72 @import url('https://fonts.googleapis.com/css?family=Noto+Serif'); /* Serif (print) */
73 @import url('https://fonts.googleapis.com/css?family=Roboto+Mono'); /* Monospace */
74
75 @viewport {
76 zoom: 1.0;
77 width: extend-to-zoom;
78 }
79 @-ms-viewport {
80 width: extend-to-zoom;
81 zoom: 1.0;
82 }
83 /* general and mobile first */
84 html {
85 }
86 body {
87 max-width: 90%;
88 margin: 1.5em auto;
89 color: #222;
90 background-color: #fff;
91 font-size: 14px;
92 font-family: 'Noto Sans', Arial, Helvetica, sans-serif;
93 line-height: 1.6;
94 scroll-behavior: smooth;
95 }
96 .ears {
97 display: none;
98 }
99
100 /* headings */
101 #title, h1, h2, h3, h4, h5, h6 {
102 margin: 1em 0 0.5em;
103 font-weight: bold;
104 line-height: 1.3;
105 }
106 #title {
107 clear: both;
108 border-bottom: 1px solid #ddd;
109 margin: 0 0 0.5em 0;
110 padding: 1em 0 0.5em;
111 }
112 .author {
113 padding-bottom: 4px;
114 }
115 h1 {
116 font-size: 26px;
117 margin: 1em 0;
118 }
119 h2 {
120 font-size: 22px;
121 margin-top: -20px; /* provide offset for in-page anchors */
122 padding-top: 33px;
123 }
124 h3 {
125 font-size: 18px;
126 margin-top: -36px; /* provide offset for in-page anchors */
127 padding-top: 42px;
128 }
129 h4 {
130 font-size: 16px;
131 margin-top: -36px; /* provide offset for in-page anchors */
132 padding-top: 42px;
133 }
134 h5, h6 {
135 font-size: 14px;
136 }
137 #n-copyright-notice {
138 border-bottom: 1px solid #ddd;
139 padding-bottom: 1em;
140 margin-bottom: 1em;
141 }
142 /* general structure */
143 p {
144 padding: 0;
145 margin: 0 0 1em 0;
146 text-align: left;
147 }
148 div, span {
149 position: relative;
150 }
151 div {
152 margin: 0;
153 }
154 .alignRight.art-text {
155 background-color: #f9f9f9;
156 border: 1px solid #eee;
157 border-radius: 3px;
158 padding: 1em 1em 0;
159 margin-bottom: 1.5em;
160 }
161 .alignRight.art-text pre {
162 padding: 0;
163 }
164 .alignRight {
165 margin: 1em 0;
166 }
167 .alignRight > *:first-child {
168 border: none;
169 margin: 0;
170 float: right;
171 clear: both;
172 }
173 .alignRight > *:nth-child(2) {
174 clear: both;
175 display: block;
176 border: none;
177 }
178 svg {
179 display: block;
180 }
181 .alignCenter.art-text {
182 background-color: #f9f9f9;
183 border: 1px solid #eee;
184 border-radius: 3px;
185 padding: 1em 1em 0;
186 margin-bottom: 1.5em;
187 }
188 .alignCenter.art-text pre {
189 padding: 0;
190 }
191 .alignCenter {
192 margin: 1em 0;
193 }
194 .alignCenter > *:first-child {
195 border: none;
196 /* this isn't optimal, but it's an existence proof. PrinceXML doesn't
197 support flexbox yet.
198 */
199 display: table;
200 margin: 0 auto;
201 }
202
203 /* lists */
204 ol, ul {
205 padding: 0;
206 margin: 0 0 1em 2em;
207 }
208 ol ol, ul ul, ol ul, ul ol {
209 margin-left: 1em;
210 }
211 li {
212 margin: 0 0 0.25em 0;
213 }
214 .ulCompact li {
215 margin: 0;
216 }
217 ul.empty, .ulEmpty {
218 list-style-type: none;
219 }
220 ul.empty li, .ulEmpty li {
221 margin-top: 0.5em;
222 }
223 ul.ulBare, li.ulBare {
224 margin-left: 0em !important;
225 }
226 ul.compact, .ulCompact,
227 ol.compact, .olCompact {
228 line-height: 100%;
229 margin: 0 0 0 2em;
230 }
231
232 /* definition lists */
233 dl {
234 }
235 dl > dt {
236 float: left;
237 margin-right: 1em;
238 }
239 /*
240 dl.nohang > dt {
241 float: none;
242 }
243 */
244 dl > dd {
245 margin-bottom: .8em;
246 min-height: 1.3em;
247 }
248 dl.compact > dd, .dlCompact > dd {
249 margin-bottom: 0em;
250 }
251 dl > dd > dl {
252 margin-top: 0.5em;
253 margin-bottom: 0em;
254 }
255
256 /* links */
257 a {
258 text-decoration: none;
259 }
260 a[href] {
261 color: #22e; /* Arlen: WCAG 2019 */
262 }
263 a[href]:hover {
264 background-color: #f2f2f2;
265 }
266 figcaption a[href],
267 a[href].selfRef {
268 color: #222;
269 }
270 /* XXX probably not this:
271 a.selfRef:hover {
272 background-color: transparent;
273 cursor: default;
274 } */
275
276 /* Figures */
277 tt, code, pre, code {
278 background-color: #f9f9f9;
279 font-family: 'Roboto Mono', monospace;
280 }
281 pre {
282 border: 1px solid #eee;
283 margin: 0;
284 padding: 1em;
285 }
286 img {
287 max-width: 100%;
288 }
289 figure {
290 margin: 0;
291 }
292 figure blockquote {
293 margin: 0.8em 0.4em 0.4em;
294 }
295 figcaption {
296 font-style: italic;
297 margin: 0 0 1em 0;
298 }
299 @media screen {
300 pre {
301 overflow-x: auto;
302 max-width: 100%;
303 max-width: calc(100% - 22px);
304 }
305 }
306
307 /* aside, blockquote */
308 aside, blockquote {
309 margin-left: 0;
310 padding: 1.2em 2em;
311 }
312 blockquote {
313 background-color: #f9f9f9;
314 color: #111; /* Arlen: WCAG 2019 */
315 border: 1px solid #ddd;
316 border-radius: 3px;
317 margin: 1em 0;
318 }
319 cite {
320 display: block;
321 text-align: right;
322 font-style: italic;
323 }
324
325 /* tables */
326 table {
327 width: 100%;
328 margin: 0 0 1em;
329 border-collapse: collapse;
330 border: 1px solid #eee;
331 }
332 th, td {
333 text-align: left;
334 vertical-align: top;
335 padding: 0.5em 0.75em;
336 }
337 th {
338 text-align: left;
339 background-color: #e9e9e9;
340 }
341 tr:nth-child(2n+1) > td {
342 background-color: #f5f5f5;
343 }
344 table caption {
345 font-style: italic;
346 margin: 0;
347 padding: 0;
348 text-align: left;
349 }
350 table p {
351 /* XXX to avoid bottom margin on table row signifiers. If paragraphs should
352 be allowed within tables more generally, it would be far better to select on a class. */
353 margin: 0;
354 }
355
356 /* pilcrow */
357 a.pilcrow {
358 color: #666; /* Arlen: AHDJ 2019 */
359 text-decoration: none;
360 visibility: hidden;
361 user-select: none;
362 -ms-user-select: none;
363 -o-user-select:none;
364 -moz-user-select: none;
365 -khtml-user-select: none;
366 -webkit-user-select: none;
367 -webkit-touch-callout: none;
368 }
369 @media screen {
370 aside:hover > a.pilcrow,
371 p:hover > a.pilcrow,
372 blockquote:hover > a.pilcrow,
373 div:hover > a.pilcrow,
374 li:hover > a.pilcrow,
375 pre:hover > a.pilcrow {
376 visibility: visible;
377 }
378 a.pilcrow:hover {
379 background-color: transparent;
380 }
381 }
382
383 /* misc */
384 hr {
385 border: 0;
386 border-top: 1px solid #eee;
387 }
388 .bcp14 {
389 font-variant: small-caps;
390 }
391
392 .role {
393 font-variant: all-small-caps;
394 }
395
396 /* info block */
397 #identifiers {
398 margin: 0;
399 font-size: 0.9em;
400 }
401 #identifiers dt {
402 width: 3em;
403 clear: left;
404 }
405 #identifiers dd {
406 float: left;
407 margin-bottom: 0;
408 }
409 /* Fix PDF info block run off issue */
410 @media print {
411 #identifiers dd {
412 float: none;
413 }
414 }
415 #identifiers .authors .author {
416 display: inline-block;
417 margin-right: 1.5em;
418 }
419 #identifiers .authors .org {
420 font-style: italic;
421 }
422
423 /* The prepared/rendered info at the very bottom of the page */
424 .docInfo {
425 color: #666; /* Arlen: WCAG 2019 */
426 font-size: 0.9em;
427 font-style: italic;
428 margin-top: 2em;
429 }
430 .docInfo .prepared {
431 float: left;
432 }
433 .docInfo .prepared {
434 float: right;
435 }
436
437 /* table of contents */
438 #toc {
439 padding: 0.75em 0 2em 0;
440 margin-bottom: 1em;
441 }
442 nav.toc ul {
443 margin: 0 0.5em 0 0;
444 padding: 0;
445 list-style: none;
446 }
447 nav.toc li {
448 line-height: 1.3em;
449 margin: 0.75em 0;
450 padding-left: 1.2em;
451 text-indent: -1.2em;
452 }
453 /* references */
454 .references dt {
455 text-align: right;
456 font-weight: bold;
457 min-width: 7em;
458 }
459 .references dd {
460 margin-left: 8em;
461 overflow: auto;
462 }
463
464 .refInstance {
465 margin-bottom: 1.25em;
466 }
467
468 .references .ascii {
469 margin-bottom: 0.25em;
470 }
471
472 /* index */
473 .index ul {
474 margin: 0 0 0 1em;
475 padding: 0;
476 list-style: none;
477 }
478 .index ul ul {
479 margin: 0;
480 }
481 .index li {
482 margin: 0;
483 text-indent: -2em;
484 padding-left: 2em;
485 padding-bottom: 5px;
486 }
487 .indexIndex {
488 margin: 0.5em 0 1em;
489 }
490 .index a {
491 font-weight: 700;
492 }
493 /* make the index two-column on all but the smallest screens */
494 @media (min-width: 600px) {
495 .index ul {
496 -moz-column-count: 2;
497 -moz-column-gap: 20px;
498 }
499 .index ul ul {
500 -moz-column-count: 1;
501 -moz-column-gap: 0;
502 }
503 }
504
505 /* authors */
506 address.vcard {
507 font-style: normal;
508 margin: 1em 0;
509 }
510
511 address.vcard .nameRole {
512 font-weight: 700;
513 margin-left: 0;
514 }
515 address.vcard .label {
516 font-family: "Noto Sans",Arial,Helvetica,sans-serif;
517 margin: 0.5em 0;
518 }
519 address.vcard .type {
520 display: none;
521 }
522 .alternative-contact {
523 margin: 1.5em 0 1em;
524 }
525 hr.addr {
526 border-top: 1px dashed;
527 margin: 0;
528 color: #ddd;
529 max-width: calc(100% - 16px);
530 }
531
532 /* temporary notes */
533 .rfcEditorRemove::before {
534 position: absolute;
535 top: 0.2em;
536 right: 0.2em;
537 padding: 0.2em;
538 content: "The RFC Editor will remove this note";
539 color: #9e2a00; /* Arlen: WCAG 2019 */
540 background-color: #ffd; /* Arlen: WCAG 2019 */
541 }
542 .rfcEditorRemove {
543 position: relative;
544 padding-top: 1.8em;
545 background-color: #ffd; /* Arlen: WCAG 2019 */
546 border-radius: 3px;
547 }
548 .cref {
549 background-color: #ffd; /* Arlen: WCAG 2019 */
550 padding: 2px 4px;
551 }
552 .crefSource {
553 font-style: italic;
554 }
555 /* alternative layout for smaller screens */
556 @media screen and (max-width: 1023px) {
557 body {
558 padding-top: 2em;
559 }
560 #title {
561 padding: 1em 0;
562 }
563 h1 {
564 font-size: 24px;
565 }
566 h2 {
567 font-size: 20px;
568 margin-top: -18px; /* provide offset for in-page anchors */
569 padding-top: 38px;
570 }
571 #identifiers dd {
572 max-width: 60%;
573 }
574 #toc {
575 position: fixed;
576 z-index: 2;
577 top: 0;
578 right: 0;
579 padding: 0;
580 margin: 0;
581 background-color: inherit;
582 border-bottom: 1px solid #ccc;
583 }
584 #toc h2 {
585 margin: -1px 0 0 0;
586 padding: 4px 0 4px 6px;
587 padding-right: 1em;
588 min-width: 190px;
589 font-size: 1.1em;
590 text-align: right;
591 background-color: #444;
592 color: white;
593 cursor: pointer;
594 }
595 #toc h2::before { /* css hamburger */
596 float: right;
597 position: relative;
598 width: 1em;
599 height: 1px;
600 left: -164px;
601 margin: 6px 0 0 0;
602 background: white none repeat scroll 0 0;
603 box-shadow: 0 4px 0 0 white, 0 8px 0 0 white;
604 content: "";
605 }
606 #toc nav {
607 display: none;
608 padding: 0.5em 1em 1em;
609 overflow: auto;
610 height: calc(100vh - 48px);
611 border-left: 1px solid #ddd;
612 }
613 }
614
615 /* alternative layout for wide screens */
616 @media screen and (min-width: 1024px) {
617 body {
618 max-width: 724px;
619 margin: 42px auto;
620 padding-left: 1.5em;
621 padding-right: 29em;
622 }
623 #toc {
624 position: fixed;
625 top: 42px;
626 right: 42px;
627 width: 25%;
628 margin: 0;
629 padding: 0 1em;
630 z-index: 1;
631 }
632 #toc h2 {
633 border-top: none;
634 border-bottom: 1px solid #ddd;
635 font-size: 1em;
636 font-weight: normal;
637 margin: 0;
638 padding: 0.25em 1em 1em 0;
639 }
640 #toc nav {
641 display: block;
642 height: calc(90vh - 84px);
643 bottom: 0;
644 padding: 0.5em 0 0;
645 overflow: auto;
646 }
647 img { /* future proofing */
648 max-width: 100%;
649 height: auto;
650 }
651 }
652
653 /* pagination */
654 @media print {
655 body {
656
657 width: 100%;
658 }
659 p {
660 orphans: 3;
661 widows: 3;
662 }
663 #n-copyright-notice {
664 border-bottom: none;
665 }
666 #toc, #n-introduction {
667 page-break-before: always;
668 }
669 #toc {
670 border-top: none;
671 padding-top: 0;
672 }
673 figure, pre {
674 page-break-inside: avoid;
675 }
676 figure {
677 overflow: scroll;
678 }
679 h1, h2, h3, h4, h5, h6 {
680 page-break-after: avoid;
681 }
682 h2+*, h3+*, h4+*, h5+*, h6+* {
683 page-break-before: avoid;
684 }
685 pre {
686 white-space: pre-wrap;
687 word-wrap: break-word;
688 font-size: 10pt;
689 }
690 table {
691 border: 1px solid #ddd;
692 }
693 td {
694 border-top: 1px solid #ddd;
695 }
696 }
697
698 /* This is commented out here, as the string-set: doesn't
699 pass W3C validation currently */
700 /*
701 .ears thead .left {
702 string-set: ears-top-left content();
703 }
704
705 .ears thead .center {
706 string-set: ears-top-center content();
707 }
708
709 .ears thead .right {
710 string-set: ears-top-right content();
711 }
712
713 .ears tfoot .left {
714 string-set: ears-bottom-left content();
715 }
716
717 .ears tfoot .center {
718 string-set: ears-bottom-center content();
719 }
720
721 .ears tfoot .right {
722 string-set: ears-bottom-right content();
723 }
724 */
725
726 @page :first {
727 padding-top: 0;
728 @top-left {
729 content: normal;
730 border: none;
731 }
732 @top-center {
733 content: normal;
734 border: none;
735 }
736 @top-right {
737 content: normal;
738 border: none;
739 }
740 }
741
742 @page {
743 size: A4;
744 margin-bottom: 45mm;
745 padding-top: 20px;
746 /* The follwing is commented out here, but set appropriately by in code, as
747 the content depends on the document */
748 /*
749 @top-left {
750 content: 'Internet-Draft';
751 vertical-align: bottom;
752 border-bottom: solid 1px #ccc;
753 }
754 @top-left {
755 content: string(ears-top-left);
756 vertical-align: bottom;
757 border-bottom: solid 1px #ccc;
758 }
759 @top-center {
760 content: string(ears-top-center);
761 vertical-align: bottom;
762 border-bottom: solid 1px #ccc;
763 }
764 @top-right {
765 content: string(ears-top-right);
766 vertical-align: bottom;
767 border-bottom: solid 1px #ccc;
768 }
769 @bottom-left {
770 content: string(ears-bottom-left);
771 vertical-align: top;
772 border-top: solid 1px #ccc;
773 }
774 @bottom-center {
775 content: string(ears-bottom-center);
776 vertical-align: top;
777 border-top: solid 1px #ccc;
778 }
779 @bottom-right {
780 content: '[Page ' counter(page) ']';
781 vertical-align: top;
782 border-top: solid 1px #ccc;
783 }
784 */
785
786 }
787
788 /* Changes introduced to fix issues found during implementation */
789 /* Make sure links are clickable even if overlapped by following H* */
790 a {
791 z-index: 2;
792 }
793 /* Separate body from document info even without intervening H1 */
794 section {
795 clear: both;
796 }
797
798
799 /* Top align author divs, to avoid names without organization dropping level with org names */
800 .author {
801 vertical-align: top;
802 }
803
804 /* Leave room in document info to show Internet-Draft on one line */
805 #identifiers dt {
806 width: 8em;
807 }
808
809 /* Don't waste quite as much whitespace between label and value in doc info */
810 #identifiers dd {
811 margin-left: 1em;
812 }
813
814 /* Give floating toc a background color (needed when it's a div inside section */
815 #toc {
816 background-color: white;
817 }
818
819 /* Make the collapsed ToC header render white on gray also when it's a link */
820 @media screen and (max-width: 1023px) {
821 #toc h2 a,
822 #toc h2 a:link,
823 #toc h2 a:focus,
824 #toc h2 a:hover,
825 #toc a.toplink,
826 #toc a.toplink:hover {
827 color: white;
828 background-color: #444;
829 text-decoration: none;
830 }
831 }
832
833 /* Give the bottom of the ToC some whitespace */
834 @media screen and (min-width: 1024px) {
835 #toc {
836 padding: 0 0 1em 1em;
837 }
838 }
839
840 /* Style section numbers with more space between number and title */
841 .section-number {
842 padding-right: 0.5em;
843 }
844
845 /* prevent monospace from becoming overly large */
846 tt, code, pre, code {
847 font-size: 95%;
848 }
849
850 /* Fix the height/width aspect for ascii art*/
851 pre.sourcecode,
852 .art-text pre {
853 line-height: 1.12;
854 }
855
856
857 /* Add styling for a link in the ToC that points to the top of the document */
858 a.toplink {
859 float: right;
860 margin-right: 0.5em;
861 }
862
863 /* Fix the dl styling to match the RFC 7992 attributes */
864 dl > dt,
865 dl.dlParallel > dt {
866 float: left;
867 margin-right: 1em;
868 }
869 dl.dlNewline > dt {
870 float: none;
871 }
872
873 /* Provide styling for table cell text alignment */
874 table td.text-left,
875 table th.text-left {
876 text-align: left;
877 }
878 table td.text-center,
879 table th.text-center {
880 text-align: center;
881 }
882 table td.text-right,
883 table th.text-right {
884 text-align: right;
885 }
886
887 /* Make the alternative author contact informatio look less like just another
888 author, and group it closer with the primary author contact information */
889 .alternative-contact {
890 margin: 0.5em 0 0.25em 0;
891 }
892 address .non-ascii {
893 margin: 0 0 0 2em;
894 }
895
896 /* With it being possible to set tables with alignment
897 left, center, and right, { width: 100%; } does not make sense */
898 table {
899 width: auto;
900 }
901
902 /* Avoid reference text that sits in a block with very wide left margin,
903 because of a long floating dt label.*/
904 .references dd {
905 overflow: visible;
906 }
907
908 /* Control caption placement */
909 caption {
910 caption-side: bottom;
911 }
912
913 /* Limit the width of the author address vcard, so names in right-to-left
914 script don't end up on the other side of the page. */
915
916 address.vcard {
917 max-width: 30em;
918 margin-right: auto;
919 }
920
921 /* For address alignment dependent on LTR or RTL scripts */
922 address div.left {
923 text-align: left;
924 }
925 address div.right {
926 text-align: right;
927 }
928
929 /* Provide table alignment support. We can't use the alignX classes above
930 since they do unwanted things with caption and other styling. */
931 table.right {
932 margin-left: auto;
933 margin-right: 0;
934 }
935 table.center {
936 margin-left: auto;
937 margin-right: auto;
938 }
939 table.left {
940 margin-left: 0;
941 margin-right: auto;
942 }
943
944 /* Give the table caption label the same styling as the figcaption */
945 caption a[href] {
946 color: #222;
947 }
948
949 @media print {
950 .toplink {
951 display: none;
952 }
953
954 /* avoid overwriting the top border line with the ToC header */
955 #toc {
956 padding-top: 1px;
957 }
958
959 /* Avoid page breaks inside dl and author address entries */
960 .vcard {
961 page-break-inside: avoid;
962 }
963
964 }
965 /* Tweak the bcp14 keyword presentation */
966 .bcp14 {
967 font-variant: small-caps;
968 font-weight: bold;
969 font-size: 0.9em;
970 }
971 /* Tweak the invisible space above H* in order not to overlay links in text above */
972 h2 {
973 margin-top: -18px; /* provide offset for in-page anchors */
974 padding-top: 31px;
975 }
976 h3 {
977 margin-top: -18px; /* provide offset for in-page anchors */
978 padding-top: 24px;
979 }
980 h4 {
981 margin-top: -18px; /* provide offset for in-page anchors */
982 padding-top: 24px;
983 }
984 /* Float artwork pilcrow to the right */
985 @media screen {
986 .artwork a.pilcrow {
987 display: block;
988 line-height: 0.7;
989 margin-top: 0.15em;
990 }
991 }
992 /* Make pilcrows on dd visible */
993 @media screen {
994 dd:hover > a.pilcrow {
995 visibility: visible;
996 }
997 }
998 /* Make the placement of figcaption match that of a table's caption
999 by removing the figure's added bottom margin */
1000 .alignLeft.art-text,
1001 .alignCenter.art-text,
1002 .alignRight.art-text {
1003 margin-bottom: 0;
1004 }
1005 .alignLeft,
1006 .alignCenter,
1007 .alignRight {
1008 margin: 1em 0 0 0;
1009 }
1010 /* In print, the pilcrow won't show on hover, so prevent it from taking up space,
1011 possibly even requiring a new line */
1012 @media print {
1013 a.pilcrow {
1014 display: none;
1015 }
1016 }
1017 /* Styling for the external metadata */
1018 div#external-metadata {
1019 background-color: #eee;
1020 padding: 0.5em;
1021 margin-bottom: 0.5em;
1022 display: none;
1023 }
1024 div#internal-metadata {
1025 padding: 0.5em; /* to match the external-metadata padding */
1026 }
1027 /* Styling for title RFC Number */
1028 h1#rfcnum {
1029 clear: both;
1030 margin: 0 0 -1em;
1031 padding: 1em 0 0 0;
1032 }
1033 /* Make .olPercent look the same as <ol><li> */
1034 dl.olPercent > dd {
1035 margin-bottom: 0.25em;
1036 min-height: initial;
1037 }
1038 /* Give aside some styling to set it apart */
1039 aside {
1040 border-left: 1px solid #ddd;
1041 margin: 1em 0 1em 2em;
1042 padding: 0.2em 2em;
1043 }
1044 aside > dl,
1045 aside > ol,
1046 aside > ul,
1047 aside > table,
1048 aside > p {
1049 margin-bottom: 0.5em;
1050 }
1051 /* Additional page break settings */
1052 @media print {
1053 figcaption, table caption {
1054 page-break-before: avoid;
1055 }
1056 }
1057 /* Font size adjustments for print */
1058 @media print {
1059 body { font-size: 10pt; line-height: normal; max-width: 96%; }
1060 h1 { font-size: 1.72em; padding-top: 1.5em; } /* 1*1.2*1.2*1.2 */
1061 h2 { font-size: 1.44em; padding-top: 1.5em; } /* 1*1.2*1.2 */
1062 h3 { font-size: 1.2em; padding-top: 1.5em; } /* 1*1.2 */
1063 h4 { font-size: 1em; padding-top: 1.5em; }
1064 h5, h6 { font-size: 1em; margin: initial; padding: 0.5em 0 0.3em; }
1065 }
1066 /* Sourcecode margin in print, when there's no pilcrow */
1067 @media print {
1068 .artwork,
1069 .sourcecode {
1070 margin-bottom: 1em;
1071 }
1072 }
1073 /* Avoid narrow tables forcing too narrow table captions, which may render badly */
1074 table {
1075 min-width: 20em;
1076 }
1077 /* ol type a */
1078 ol.type-a { list-style-type: lower-alpha; }
1079 ol.type-A { list-style-type: upper-alpha; }
1080 ol.type-i { list-style-type: lower-roman; }
1081 ol.type-I { list-style-type: lower-roman; }
1082 /* Apply the print table and row borders in general, on request from the RPC,
1083 and increase the contrast between border and odd row background sligthtly */
1084 table {
1085 border: 1px solid #ddd;
1086 }
1087 td {
1088 border-top: 1px solid #ddd;
1089 }
1090 tr:nth-child(2n+1) > td {
1091 background-color: #f8f8f8;
1092 }
1093 /* Use style rules to govern display of the TOC. */
1094 @media screen and (max-width: 1023px) {
1095 #toc nav { display: none; }
1096 #toc.active nav { display: block; }
1097 }
1098 /* Add support for keepWithNext */
1099 .keepWithNext {
1100 break-after: avoid-page;
1101 break-after: avoid-page;
1102 }
1103 /* Add support for keepWithPrevious */
1104 .keepWithPrevious {
1105 break-before: avoid-page;
1106 }
1107 /* Change the approach to avoiding breaks inside artwork etc. */
1108 figure, pre, table, .artwork, .sourcecode {
1109 break-before: auto;
1110 break-after: auto;
1111 }
1112 /* Avoid breaks between <dt> and <dd> */
1113 dl {
1114 break-before: auto;
1115 break-inside: auto;
1116 }
1117 dt {
1118 break-before: auto;
1119 break-after: avoid-page;
1120 }
1121 dd {
1122 break-before: avoid-page;
1123 break-after: auto;
1124 orphans: 3;
1125 widows: 3
1126 }
1127 span.break, dd.break {
1128 margin-bottom: 0;
1129 min-height: 0;
1130 break-before: auto;
1131 break-inside: auto;
1132 break-after: auto;
1133 }
1134 /* Undo break-before ToC */
1135 @media print {
1136 #toc {
1137 break-before: auto;
1138 }
1139 }
1140 /* Text in compact lists should not get extra bottim margin space,
1141 since that would makes the list not compact */
1142 ul.compact p, .ulCompact p,
1143 ol.compact p, .olCompact p {
1144 margin: 0;
1145 }
1146 /* But the list as a whole needs the extra space at the end */
1147 section ul.compact,
1148 section .ulCompact,
1149 section ol.compact,
1150 section .olCompact {
1151 margin-bottom: 1em; /* same as p not within ul.compact etc. */
1152 }
1153 /* The tt and code background above interferes with for instance table cell
1154 backgrounds. Changed to something a bit more selective. */
1155 tt, code {
1156 background-color: transparent;
1157 }
1158 p tt, p code, li tt, li code {
1159 background-color: #f8f8f8;
1160 }
1161 /* Tweak the pre margin -- 0px doesn't come out well */
1162 pre {
1163 margin-top: 0.5px;
1164 }
1165 /* Tweak the comact list text */
1166 ul.compact, .ulCompact,
1167 ol.compact, .olCompact,
1168 dl.compact, .dlCompact {
1169 line-height: normal;
1170 }
1171 /* Don't add top margin for nested lists */
1172 li > ul, li > ol, li > dl,
1173 dd > ul, dd > ol, dd > dl,
1174 dl > dd > dl {
1175 margin-top: initial;
1176 }
1177 /* Elements that should not be rendered on the same line as a <dt> */
1178 /* This should match the element list in writer.text.TextWriter.render_dl() */
1179 dd > div.artwork:first-child,
1180 dd > aside:first-child,
1181 dd > figure:first-child,
1182 dd > ol:first-child,
1183 dd > div:first-child > pre.sourcecode,
1184 dd > table:first-child,
1185 dd > ul:first-child {
1186 clear: left;
1187 }
1188 /* fix for weird browser behaviour when <dd/> is empty */
1189 dt+dd:empty::before{
1190 content: "\00a0";
1191 }
1192 /* Make paragraph spacing inside <li> smaller than in body text, to fit better within the list */
1193 li > p {
1194 margin-bottom: 0.5em
1195 }
1196 /* Don't let p margin spill out from inside list items */
1197 li > p:last-of-type {
1198 margin-bottom: 0;
1199 }
1200 </style>
1201 <link href="rfc-local.css" rel="stylesheet" type="text/css">
1202 <link href="https://dx.doi.org/10.17487/rfc9168" rel="alternate">
1203 <link href="urn:issn:2070-1721" rel="alternate">
1204 <link href="https://datatracker.ietf.org/doc/draft-ietf-pce-pcep-flowspec-12" rel="prev">
1205 </head>
1206 <body>
1207 <script src="https://www.rfc-editor.org/js/metadata.min.js"></script>
1208 <table class="ears">
1209 <thead><tr>
1210 <td class="left">RFC 9168</td>
1211 <td class="center">PCEP Flow Spec</td>
1212 <td class="right">January 2022</td>
1213 </tr></thead>
1214 <tfoot><tr>
1215 <td class="left">Dhody, et al.</td>
1216 <td class="center">Standards Track</td>
1217 <td class="right">[Page]</td>
1218 </tr></tfoot>
1219 </table>
1220 <div id="external-metadata" class="document-information"></div>
1221 <div id="internal-metadata" class="document-information">
1222 <dl id="identifiers">
1223 <dt class="label-stream">Stream:</dt>
1224 <dd class="stream">Internet Engineering Task Force (IETF)</dd>
1225 <dt class="label-rfc">RFC:</dt>
1226 <dd class="rfc"><a href="https://www.rfc-editor.org/rfc/rfc9168" class="eref">9168</a></dd>
1227 <dt class="label-category">Category:</dt>
1228 <dd class="category">Standards Track</dd>
1229 <dt class="label-published">Published:</dt>
1230 <dd class="published">
1231 <time datetime="2022-01" class="published">January 2022</time>
1232 </dd>
1233 <dt class="label-issn">ISSN:</dt>
1234 <dd class="issn">2070-1721</dd>
1235 <dt class="label-authors">Authors:</dt>
1236 <dd class="authors">
1237 <div class="author">
1238 <div class="author-name">D. Dhody</div>
1239 <div class="org">Huawei Technologies</div>
1240 </div>
1241 <div class="author">
1242 <div class="author-name">A. Farrel</div>
1243 <div class="org">Old Dog Consulting</div>
1244 </div>
1245 <div class="author">
1246 <div class="author-name">Z. Li</div>
1247 <div class="org">Huawei Technologies</div>
1248 </div>
1249 </dd>
1250 </dl>
1251 </div>
1252 <h1 id="rfcnum">RFC 9168</h1>
1253 <h1 id="title">Path Computation Element Communication Protocol (PCEP) Extension for Flow Specification</h1>
1254 <section id="section-abstract">
1255 <h2 id="abstract"><a href="#abstract" class="selfRef">Abstract</a></h2>
1256 <p id="section-abstract-1">The Path Computation Element (PCE) is a functional component capable of selecting
1257 paths through a traffic engineering (TE) network. These paths may be supplied
1258 in response to requests for computation or may be unsolicited requests
1259 issued by the PCE to network elements. Both approaches use the PCE Communication
1260 Protocol (PCEP) to convey the details of the computed path.<a href="#section-abstract-1" class="pilcrow">¶</a></p>
1261 <p id="section-abstract-2">Traffic flows may be categorized and described using "Flow Specifications". RFC 8955 defines the Flow Specification and describes how Flow Specification
1262 components are used to describe traffic flows. RFC 8955 also defines how Flow
1263 Specifications may be distributed in BGP to allow specific traffic flows to be
1264 associated with routes.<a href="#section-abstract-2" class="pilcrow">¶</a></p>
1265 <p id="section-abstract-3">This document specifies a set of extensions to PCEP to support dissemination of
1266 Flow Specifications. This allows a PCE to indicate what traffic should be placed
1267 on each path that it is aware of.<a href="#section-abstract-3" class="pilcrow">¶</a></p>
1268 <p id="section-abstract-4">The extensions defined in this document include the creation, update, and withdrawal of Flow
1269 Specifications via PCEP and can be applied to tunnels initiated by the PCE or to tunnels where
1270 control is delegated to the PCE by the Path Computation Client (PCC).
1271 Furthermore, a PCC requesting a new path can include
1272 Flow Specifications in the request to indicate the purpose of the tunnel allowing the PCE to factor this into the path computation.<a href="#section-abstract-4" class="pilcrow">¶</a></p>
1273 </section>
1274 <div id="status-of-memo">
1275 <section id="section-boilerplate.1">
1276 <h2 id="name-status-of-this-memo">
1277 <a href="#name-status-of-this-memo" class="section-name selfRef">Status of This Memo</a>
1278 </h2>
1279 <p id="section-boilerplate.1-1">
1280 This is an Internet Standards Track document.<a href="#section-boilerplate.1-1" class="pilcrow">¶</a></p>
1281 <p id="section-boilerplate.1-2">
1282 This document is a product of the Internet Engineering Task Force
1283 (IETF). It represents the consensus of the IETF community. It has
1284 received public review and has been approved for publication by
1285 the Internet Engineering Steering Group (IESG). Further
1286 information on Internet Standards is available in Section 2 of
1287 RFC 7841.<a href="#section-boilerplate.1-2" class="pilcrow">¶</a></p>
1288 <p id="section-boilerplate.1-3">
1289 Information about the current status of this document, any
1290 errata, and how to provide feedback on it may be obtained at
1291 <span><a href="https://www.rfc-editor.org/info/rfc9168">https://www.rfc-editor.org/info/rfc9168</a></span>.<a href="#section-boilerplate.1-3" class="pilcrow">¶</a></p>
1292 </section>
1293 </div>
1294 <div id="copyright">
1295 <section id="section-boilerplate.2">
1296 <h2 id="name-copyright-notice">
1297 <a href="#name-copyright-notice" class="section-name selfRef">Copyright Notice</a>
1298 </h2>
1299 <p id="section-boilerplate.2-1">
1300 Copyright (c) 2022 IETF Trust and the persons identified as the
1301 document authors. All rights reserved.<a href="#section-boilerplate.2-1" class="pilcrow">¶</a></p>
1302 <p id="section-boilerplate.2-2">
1303 This document is subject to BCP 78 and the IETF Trust's Legal
1304 Provisions Relating to IETF Documents
1305 (<span><a href="https://trustee.ietf.org/license-info">https://trustee.ietf.org/license-info</a></span>) in effect on the date of
1306 publication of this document. Please review these documents
1307 carefully, as they describe your rights and restrictions with
1308 respect to this document. Code Components extracted from this
1309 document must include Revised BSD License text as described in
1310 Section 4.e of the Trust Legal Provisions and are provided without
1311 warranty as described in the Revised BSD License.<a href="#section-boilerplate.2-2" class="pilcrow">¶</a></p>
1312 </section>
1313 </div>
1314 <div id="toc">
1315 <section id="section-toc.1">
1316 <a href="#" onclick="scroll(0,0)" class="toplink">▲</a><h2 id="name-table-of-contents">
1317 <a href="#name-table-of-contents" class="section-name selfRef">Table of Contents</a>
1318 </h2>
1319 <nav class="toc"><ul class="compact toc ulBare ulEmpty">
1320 <li class="compact toc ulBare ulEmpty" id="section-toc.1-1.1">
1321 <p id="section-toc.1-1.1.1" class="keepWithNext"><a href="#section-1" class="xref">1</a>.  <a href="#name-introduction" class="xref">Introduction</a></p>
1322 </li>
1323 <li class="compact toc ulBare ulEmpty" id="section-toc.1-1.2">
1324 <p id="section-toc.1-1.2.1" class="keepWithNext"><a href="#section-2" class="xref">2</a>.  <a href="#name-terminology" class="xref">Terminology</a></p>
1325 </li>
1326 <li class="compact toc ulBare ulEmpty" id="section-toc.1-1.3">
1327 <p id="section-toc.1-1.3.1"><a href="#section-3" class="xref">3</a>.  <a href="#name-procedures-for-pce-use-of-f" class="xref">Procedures for PCE Use of Flow Specifications</a></p>
1328 <ul class="compact toc ulBare ulEmpty">
1329 <li class="compact toc ulBare ulEmpty" id="section-toc.1-1.3.2.1">
1330 <p id="section-toc.1-1.3.2.1.1" class="keepWithNext"><a href="#section-3.1" class="xref">3.1</a>.  <a href="#name-context-for-pce-use-of-flow" class="xref">Context for PCE Use of Flow Specifications</a></p>
1331 </li>
1332 <li class="compact toc ulBare ulEmpty" id="section-toc.1-1.3.2.2">
1333 <p id="section-toc.1-1.3.2.2.1"><a href="#section-3.2" class="xref">3.2</a>.  <a href="#name-elements-of-the-procedure" class="xref">Elements of the Procedure</a></p>
1334 <ul class="compact toc ulBare ulEmpty">
1335 <li class="compact toc ulBare ulEmpty" id="section-toc.1-1.3.2.2.2.1">
1336 <p id="section-toc.1-1.3.2.2.2.1.1"><a href="#section-3.2.1" class="xref">3.2.1</a>.  <a href="#name-capability-advertisement" class="xref">Capability Advertisement</a></p>
1337 <ul class="compact toc ulBare ulEmpty">
1338 <li class="compact toc ulBare ulEmpty" id="section-toc.1-1.3.2.2.2.1.2.1">
1339 <p id="section-toc.1-1.3.2.2.2.1.2.1.1"><a href="#section-3.2.1.1" class="xref">3.2.1.1</a>.  <a href="#name-pcep-open-message" class="xref">PCEP Open Message</a></p>
1340 </li>
1341 <li class="compact toc ulBare ulEmpty" id="section-toc.1-1.3.2.2.2.1.2.2">
1342 <p id="section-toc.1-1.3.2.2.2.1.2.2.1"><a href="#section-3.2.1.2" class="xref">3.2.1.2</a>.  <a href="#name-igp-pce-capabilities-advert" class="xref">IGP PCE Capabilities Advertisement</a></p>
1343 </li>
1344 </ul>
1345 </li>
1346 <li class="compact toc ulBare ulEmpty" id="section-toc.1-1.3.2.2.2.2">
1347 <p id="section-toc.1-1.3.2.2.2.2.1"><a href="#section-3.2.2" class="xref">3.2.2</a>.  <a href="#name-dissemination-procedures" class="xref">Dissemination Procedures</a></p>
1348 </li>
1349 <li class="compact toc ulBare ulEmpty" id="section-toc.1-1.3.2.2.2.3">
1350 <p id="section-toc.1-1.3.2.2.2.3.1"><a href="#section-3.2.3" class="xref">3.2.3</a>.  <a href="#name-flow-specification-synchron" class="xref">Flow Specification Synchronization</a></p>
1351 </li>
1352 </ul>
1353 </li>
1354 </ul>
1355 </li>
1356 <li class="compact toc ulBare ulEmpty" id="section-toc.1-1.4">
1357 <p id="section-toc.1-1.4.1"><a href="#section-4" class="xref">4</a>.  <a href="#name-pce-flowspec-capability-tlv" class="xref">PCE FlowSpec Capability TLV</a></p>
1358 </li>
1359 <li class="compact toc ulBare ulEmpty" id="section-toc.1-1.5">
1360 <p id="section-toc.1-1.5.1"><a href="#section-5" class="xref">5</a>.  <a href="#name-pcep-flowspec-object" class="xref">PCEP FLOWSPEC Object</a></p>
1361 </li>
1362 <li class="compact toc ulBare ulEmpty" id="section-toc.1-1.6">
1363 <p id="section-toc.1-1.6.1"><a href="#section-6" class="xref">6</a>.  <a href="#name-flow-filter-tlv" class="xref">Flow Filter TLV</a></p>
1364 </li>
1365 <li class="compact toc ulBare ulEmpty" id="section-toc.1-1.7">
1366 <p id="section-toc.1-1.7.1"><a href="#section-7" class="xref">7</a>.  <a href="#name-flow-specification-tlvs" class="xref">Flow Specification TLVs</a></p>
1367 </li>
1368 <li class="compact toc ulBare ulEmpty" id="section-toc.1-1.8">
1369 <p id="section-toc.1-1.8.1"><a href="#section-8" class="xref">8</a>.  <a href="#name-detailed-procedures" class="xref">Detailed Procedures</a></p>
1370 <ul class="compact toc ulBare ulEmpty">
1371 <li class="compact toc ulBare ulEmpty" id="section-toc.1-1.8.2.1">
1372 <p id="section-toc.1-1.8.2.1.1"><a href="#section-8.1" class="xref">8.1</a>.  <a href="#name-default-behavior-and-backwa" class="xref">Default Behavior and Backward Compatibility</a></p>
1373 </li>
1374 <li class="compact toc ulBare ulEmpty" id="section-toc.1-1.8.2.2">
1375 <p id="section-toc.1-1.8.2.2.1"><a href="#section-8.2" class="xref">8.2</a>.  <a href="#name-composite-flow-specificatio" class="xref">Composite Flow Specifications</a></p>
1376 </li>
1377 <li class="compact toc ulBare ulEmpty" id="section-toc.1-1.8.2.3">
1378 <p id="section-toc.1-1.8.2.3.1"><a href="#section-8.3" class="xref">8.3</a>.  <a href="#name-modifying-flow-specificatio" class="xref">Modifying Flow Specifications</a></p>
1379 </li>
1380 <li class="compact toc ulBare ulEmpty" id="section-toc.1-1.8.2.4">
1381 <p id="section-toc.1-1.8.2.4.1"><a href="#section-8.4" class="xref">8.4</a>.  <a href="#name-multiple-flow-specification" class="xref">Multiple Flow Specifications</a></p>
1382 </li>
1383 <li class="compact toc ulBare ulEmpty" id="section-toc.1-1.8.2.5">
1384 <p id="section-toc.1-1.8.2.5.1"><a href="#section-8.5" class="xref">8.5</a>.  <a href="#name-adding-and-removing-flow-sp" class="xref">Adding and Removing Flow Specifications</a></p>
1385 </li>
1386 <li class="compact toc ulBare ulEmpty" id="section-toc.1-1.8.2.6">
1387 <p id="section-toc.1-1.8.2.6.1"><a href="#section-8.6" class="xref">8.6</a>.  <a href="#name-vpn-identifiers" class="xref">VPN Identifiers</a></p>
1388 </li>
1389 <li class="compact toc ulBare ulEmpty" id="section-toc.1-1.8.2.7">
1390 <p id="section-toc.1-1.8.2.7.1"><a href="#section-8.7" class="xref">8.7</a>.  <a href="#name-priorities-and-overlapping-" class="xref">Priorities and Overlapping Flow Specifications</a></p>
1391 </li>
1392 </ul>
1393 </li>
1394 <li class="compact toc ulBare ulEmpty" id="section-toc.1-1.9">
1395 <p id="section-toc.1-1.9.1"><a href="#section-9" class="xref">9</a>.  <a href="#name-pcep-messages" class="xref">PCEP Messages</a></p>
1396 </li>
1397 <li class="compact toc ulBare ulEmpty" id="section-toc.1-1.10">
1398 <p id="section-toc.1-1.10.1"><a href="#section-10" class="xref">10</a>. <a href="#name-iana-considerations" class="xref">IANA Considerations</a></p>
1399 <ul class="compact toc ulBare ulEmpty">
1400 <li class="compact toc ulBare ulEmpty" id="section-toc.1-1.10.2.1">
1401 <p id="section-toc.1-1.10.2.1.1"><a href="#section-10.1" class="xref">10.1</a>.  <a href="#name-pcep-objects" class="xref">PCEP Objects</a></p>
1402 <ul class="compact toc ulBare ulEmpty">
1403 <li class="compact toc ulBare ulEmpty" id="section-toc.1-1.10.2.1.2.1">
1404 <p id="section-toc.1-1.10.2.1.2.1.1"><a href="#section-10.1.1" class="xref">10.1.1</a>.  <a href="#name-pcep-flowspec-object-flag-f" class="xref">PCEP FLOWSPEC Object Flag Field</a></p>
1405 </li>
1406 </ul>
1407 </li>
1408 <li class="compact toc ulBare ulEmpty" id="section-toc.1-1.10.2.2">
1409 <p id="section-toc.1-1.10.2.2.1"><a href="#section-10.2" class="xref">10.2</a>.  <a href="#name-pcep-tlv-type-indicators" class="xref">PCEP TLV Type Indicators</a></p>
1410 </li>
1411 <li class="compact toc ulBare ulEmpty" id="section-toc.1-1.10.2.3">
1412 <p id="section-toc.1-1.10.2.3.1"><a href="#section-10.3" class="xref">10.3</a>.  <a href="#name-flow-specification-tlv-type-" class="xref">Flow Specification TLV Type Indicators</a></p>
1413 </li>
1414 <li class="compact toc ulBare ulEmpty" id="section-toc.1-1.10.2.4">
1415 <p id="section-toc.1-1.10.2.4.1"><a href="#section-10.4" class="xref">10.4</a>.  <a href="#name-pcep-error-codes" class="xref">PCEP Error Codes</a></p>
1416 </li>
1417 <li class="compact toc ulBare ulEmpty" id="section-toc.1-1.10.2.5">
1418 <p id="section-toc.1-1.10.2.5.1"><a href="#section-10.5" class="xref">10.5</a>.  <a href="#name-pce-capability-flag" class="xref">PCE Capability Flag</a></p>
1419 </li>
1420 </ul>
1421 </li>
1422 <li class="compact toc ulBare ulEmpty" id="section-toc.1-1.11">
1423 <p id="section-toc.1-1.11.1"><a href="#section-11" class="xref">11</a>. <a href="#name-security-considerations" class="xref">Security Considerations</a></p>
1424 </li>
1425 <li class="compact toc ulBare ulEmpty" id="section-toc.1-1.12">
1426 <p id="section-toc.1-1.12.1"><a href="#section-12" class="xref">12</a>. <a href="#name-manageability-consideration" class="xref">Manageability Considerations</a></p>
1427 <ul class="compact toc ulBare ulEmpty">
1428 <li class="compact toc ulBare ulEmpty" id="section-toc.1-1.12.2.1">
1429 <p id="section-toc.1-1.12.2.1.1"><a href="#section-12.1" class="xref">12.1</a>.  <a href="#name-management-of-multiple-flow" class="xref">Management of Multiple Flow Specifications</a></p>
1430 </li>
1431 <li class="compact toc ulBare ulEmpty" id="section-toc.1-1.12.2.2">
1432 <p id="section-toc.1-1.12.2.2.1"><a href="#section-12.2" class="xref">12.2</a>.  <a href="#name-control-of-function-through" class="xref">Control of Function through Configuration and Policy</a></p>
1433 </li>
1434 <li class="compact toc ulBare ulEmpty" id="section-toc.1-1.12.2.3">
1435 <p id="section-toc.1-1.12.2.3.1"><a href="#section-12.3" class="xref">12.3</a>.  <a href="#name-information-and-data-models" class="xref">Information and Data Models</a></p>
1436 </li>
1437 <li class="compact toc ulBare ulEmpty" id="section-toc.1-1.12.2.4">
1438 <p id="section-toc.1-1.12.2.4.1"><a href="#section-12.4" class="xref">12.4</a>.  <a href="#name-liveness-detection-and-moni" class="xref">Liveness Detection and Monitoring</a></p>
1439 </li>
1440 <li class="compact toc ulBare ulEmpty" id="section-toc.1-1.12.2.5">
1441 <p id="section-toc.1-1.12.2.5.1"><a href="#section-12.5" class="xref">12.5</a>.  <a href="#name-verifying-correct-operation" class="xref">Verifying Correct Operation</a></p>
1442 </li>
1443 <li class="compact toc ulBare ulEmpty" id="section-toc.1-1.12.2.6">
1444 <p id="section-toc.1-1.12.2.6.1"><a href="#section-12.6" class="xref">12.6</a>.  <a href="#name-requirements-for-other-prot" class="xref">Requirements for Other Protocols and Functional Components</a></p>
1445 </li>
1446 <li class="compact toc ulBare ulEmpty" id="section-toc.1-1.12.2.7">
1447 <p id="section-toc.1-1.12.2.7.1"><a href="#section-12.7" class="xref">12.7</a>.  <a href="#name-impact-on-network-operation" class="xref">Impact on Network Operation</a></p>
1448 </li>
1449 </ul>
1450 </li>
1451 <li class="compact toc ulBare ulEmpty" id="section-toc.1-1.13">
1452 <p id="section-toc.1-1.13.1"><a href="#section-13" class="xref">13</a>. <a href="#name-references" class="xref">References</a></p>
1453 <ul class="compact toc ulBare ulEmpty">
1454 <li class="compact toc ulBare ulEmpty" id="section-toc.1-1.13.2.1">
1455 <p id="section-toc.1-1.13.2.1.1"><a href="#section-13.1" class="xref">13.1</a>.  <a href="#name-normative-references" class="xref">Normative References</a></p>
1456 </li>
1457 <li class="compact toc ulBare ulEmpty" id="section-toc.1-1.13.2.2">
1458 <p id="section-toc.1-1.13.2.2.1"><a href="#section-13.2" class="xref">13.2</a>.  <a href="#name-informative-references" class="xref">Informative References</a></p>
1459 </li>
1460 </ul>
1461 </li>
1462 <li class="compact toc ulBare ulEmpty" id="section-toc.1-1.14">
1463 <p id="section-toc.1-1.14.1"><a href="#appendix-A" class="xref"></a><a href="#name-acknowledgements" class="xref">Acknowledgements</a></p>
1464 </li>
1465 <li class="compact toc ulBare ulEmpty" id="section-toc.1-1.15">
1466 <p id="section-toc.1-1.15.1"><a href="#appendix-B" class="xref"></a><a href="#name-contributors" class="xref">Contributors</a></p>
1467 </li>
1468 <li class="compact toc ulBare ulEmpty" id="section-toc.1-1.16">
1469 <p id="section-toc.1-1.16.1"><a href="#appendix-C" class="xref"></a><a href="#name-authors-addresses" class="xref">Authors' Addresses</a></p>
1470 </li>
1471 </ul>
1472 </nav>
1473 </section>
1474 </div>
1475 <div id="Intro">
1476 <section id="section-1">
1477 <h2 id="name-introduction">
1478 <a href="#section-1" class="section-number selfRef">1. </a><a href="#name-introduction" class="section-name selfRef">Introduction</a>
1479 </h2>
1480 <p id="section-1-1"><span>[<a href="#RFC4655" class="xref">RFC4655</a>]</span> defines the Path Computation Element (PCE), a functional component
1481 capable of computing paths for use in traffic engineering networks. PCE was originally
1482 conceived for use in Multiprotocol Label Switching (MPLS) for traffic engineering (TE) networks
1483 to derive the routes of Label Switched Paths (LSPs). However, the scope of PCE was quickly
1484 extended to make it applicable to networks controlled by Generalized MPLS (GMPLS), and more recent work
1485 has brought other traffic engineering technologies and planning applications into scope (for
1486 example, Segment Routing (SR) <span>[<a href="#RFC8664" class="xref">RFC8664</a>]</span>).<a href="#section-1-1" class="pilcrow">¶</a></p>
1487 <p id="section-1-2"><span>[<a href="#RFC5440" class="xref">RFC5440</a>]</span> describes the PCE
1488 Communication Protocol (PCEP).
1489 PCEP defines the communication between a Path Computation Client (PCC) and a PCE, or between
1490 PCE and PCE, enabling computation of the path for MPLS-TE LSPs.<a href="#section-1-2" class="pilcrow">¶</a></p>
1491 <p id="section-1-3">Stateful PCE <span>[<a href="#RFC8231" class="xref">RFC8231</a>]</span> specifies a set of extensions to PCEP to enable control of
1492 TE-LSPs by a PCE that retains state about the LSPs provisioned in the network (a stateful PCE).
1493 <span>[<a href="#RFC8281" class="xref">RFC8281</a>]</span> describes the setup, maintenance, and teardown of LSPs initiated by a
1494 stateful PCE without the need for local configuration on the PCC, thus allowing for a dynamic
1495 network that is centrally controlled. <span>[<a href="#RFC8283" class="xref">RFC8283</a>]</span> introduces the architecture for PCE
1496 as a central controller and describes how PCE can be viewed as a component that performs computation
1497 to place "flows" within the network and decide how these flows are routed.<a href="#section-1-3" class="pilcrow">¶</a></p>
1498 <p id="section-1-4">The description of traffic flows by the combination of multiple Flow Specification components and
1499 their dissemination as traffic flow specifications (Flow Specifications) is described for BGP in
1500 <span>[<a href="#RFC8955" class="xref">RFC8955</a>]</span>. In BGP, a Flow Specification is comprised of traffic
1501 filtering rules and is associated with actions to perform on the packets that match the Flow
1502 Specification. The BGP routers that receive a Flow Specification can classify received packets
1503 according to the traffic filtering rules and can direct packets based on the associated actions.<a href="#section-1-4" class="pilcrow">¶</a></p>
1504 <p id="section-1-5">When a PCE is used to initiate tunnels (such as TE-LSPs or SR paths) using PCEP, it is important
1505 that the head end of the tunnels understands what traffic to place on each tunnel. The data flows
1506 intended for a tunnel can be described using Flow Specification components. When PCEP is in
1507 use for tunnel initiation, it makes sense for that same protocol to be used to distribute the Flow
1508 Specification components that describe what data is to flow on those tunnels.<a href="#section-1-5" class="pilcrow">¶</a></p>
1509 <p id="section-1-6">This document specifies a set of extensions to PCEP to support dissemination of Flow Specification
1510 components. We term the description of a traffic flow using Flow Specification components as a
1511 "Flow Specification". This term is conceptually the same as the term used in
1512 <span>[<a href="#RFC8955" class="xref">RFC8955</a>]</span>; however, no mechanism is provided to distribute an action
1513 associated with the Flow Specification because there is only one action that is applicable in the
1514 PCEP context (that is, directing the matching traffic to the identified LSP).<a href="#section-1-6" class="pilcrow">¶</a></p>
1515 <p id="section-1-7">The extensions defined in this document include the creation, update, and withdrawal of Flow
1516 Specifications via PCEP and can be applied to tunnels initiated by the PCE or to tunnels where
1517 control is delegated to the PCE by the PCC. Furthermore, a PCC requesting a new path can include
1518 Flow Specifications in the request to indicate the purpose of the tunnel allowing the PCE to factor
1519 this into the path computation.<a href="#section-1-7" class="pilcrow">¶</a></p>
1520 <p id="section-1-8">Flow Specifications are carried in TLVs within a new object called the FLOWSPEC object defined
1521 in this document. The flow filtering rules indicated by the Flow Specifications are mainly
1522 defined by BGP Flow Specifications.<a href="#section-1-8" class="pilcrow">¶</a></p>
1523 <p id="section-1-9">Note that PCEP-installed Flow Specifications are intended to be installed only at the head end of
1524 the LSP to which they direct traffic. It is acceptable (and potentially desirable) that other
1525 routers in the network have Flow Specifications installed that match the same traffic but direct
1526 it onto different routes or to different LSPs. Those other Flow Specifications may be installed
1527 using the PCEP extensions defined in this document, distributed using BGP per
1528 <span>[<a href="#RFC8955" class="xref">RFC8955</a>]</span>, or configured using manual operations. Since
1529 this document is about PCEP-installed Flow Specifications, those other Flow Specifications at
1530 other routers are out of scope. In this context, however, it is worth noting that changes to the
1531 wider routing system (such as the distribution and installation of BGP Flow Specifications, or
1532 fluctuations in the IGP link state database) might mean that traffic matching the PCEP Flow Specification
1533 never reaches the head end of the LSP at which the PCEP Flow Specification has been installed. This may
1534 or may not be desirable according to the operator's traffic engineering and routing policies and is
1535 particularly applicable at LSPs that do not have their head ends at the ingress edge of the network, but
1536 it is not an effect that this document seeks to address.<a href="#section-1-9" class="pilcrow">¶</a></p>
1537 </section>
1538 </div>
1539 <section id="section-2">
1540 <h2 id="name-terminology">
1541 <a href="#section-2" class="section-number selfRef">2. </a><a href="#name-terminology" class="section-name selfRef">Terminology</a>
1542 </h2>
1543 <p id="section-2-1">The key words "<span class="bcp14">MUST</span>", "<span class="bcp14">MUST NOT</span>", "<span class="bcp14">REQUIRED</span>", "<span class="bcp14">SHALL</span>", "<span class="bcp14">SHALL NOT</span>", "<span class="bcp14">SHOULD</span>", "<span class="bcp14">SHOULD NOT</span>",
1544 "<span class="bcp14">RECOMMENDED</span>", "<span class="bcp14">NOT RECOMMENDED</span>", "<span class="bcp14">MAY</span>", and "<span class="bcp14">OPTIONAL</span>" in this document are to be interpreted
1545 as described in BCP 14 <span>[<a href="#RFC2119" class="xref">RFC2119</a>]</span> <span>[<a href="#RFC8174" class="xref">RFC8174</a>]</span> when, and only when,
1546 they appear in all capitals, as shown here.<a href="#section-2-1" class="pilcrow">¶</a></p>
1547 <p id="section-2-2">This document uses the following terms defined in <span>[<a href="#RFC5440" class="xref">RFC5440</a>]</span>: PCC, PCE, and PCEP Peer.<a href="#section-2-2" class="pilcrow">¶</a></p>
1548 <p id="section-2-3">The following term from <span>[<a href="#RFC8955" class="xref">RFC8955</a>]</span> is used frequently throughout this
1549 document:<a href="#section-2-3" class="pilcrow">¶</a></p>
1550 <blockquote id="section-2-4">A Flow Specification is an n-tuple consisting of several matching criteria that can be
1551 applied to IP traffic. A given IP packet is said to match the defined Flow Specification
1552 if it matches all the specified criteria.<a href="#section-2-4" class="pilcrow">¶</a>
1553 </blockquote>
1554 <p id="section-2-5"><span>[<a href="#RFC8955" class="xref">RFC8955</a>]</span> also states that "[a] given Flow Specification may be
1555 associated with a set of attributes" and that "...attributes can be used to encode a set of
1556 predetermined actions." However, in the context of this document, no action is explicitly
1557 specified as associated with the Flow Specification since the action of forwarding all matching traffic
1558 onto the associated path is implicit.<a href="#section-2-5" class="pilcrow">¶</a></p>
1559 <p id="section-2-6">How an implementation decides to filter traffic that matches a Flow Specification does not form
1560 part of this specification, but a flag is provided to indicate whether the sender of a PCEP
1561 message that includes a Flow Specification intends it to be installed as a Longest Prefix Match (LPM) route or as a Flow Specification policy.<a href="#section-2-6" class="pilcrow">¶</a></p>
1562 <p id="section-2-7">This document uses the terms "stateful PCE" and "active PCE" as advocated in <span>[<a href="#RFC7399" class="xref">RFC7399</a>]</span>.<a href="#section-2-7" class="pilcrow">¶</a></p>
1563 </section>
1564 <section id="section-3">
1565 <h2 id="name-procedures-for-pce-use-of-f">
1566 <a href="#section-3" class="section-number selfRef">3. </a><a href="#name-procedures-for-pce-use-of-f" class="section-name selfRef">Procedures for PCE Use of Flow Specifications</a>
1567 </h2>
1568 <section id="section-3.1">
1569 <h3 id="name-context-for-pce-use-of-flow">
1570 <a href="#section-3.1" class="section-number selfRef">3.1. </a><a href="#name-context-for-pce-use-of-flow" class="section-name selfRef">Context for PCE Use of Flow Specifications</a>
1571 </h3>
1572 <p id="section-3.1-1">In the PCE architecture, there are five steps in the setup and use of LSPs:<a href="#section-3.1-1" class="pilcrow">¶</a></p>
1573 <ol start="1" type="1" class="normal type-1" id="section-3.1-2">
1574 <li id="section-3.1-2.1">Decide which LSPs to set up. The decision may be made by a user, by a PCC, or by the PCE.
1575 There can be a number of triggers for this, including user intervention and dynamic response
1576 to changes in traffic demands.<a href="#section-3.1-2.1" class="pilcrow">¶</a>
1577 </li>
1578 <li id="section-3.1-2.2">Decide what properties to assign to an LSP. This can include bandwidth reservations, priorities,
1579 and the Differentiated Services Code Point (DSCP) (i.e., MPLS Traffic Class field). This function is also determined by user configuration
1580 or in response to predicted or observed traffic demands.<a href="#section-3.1-2.2" class="pilcrow">¶</a>
1581 </li>
1582 <li id="section-3.1-2.3">Decide what traffic to put on the LSP. This is effectively determining which traffic flows to
1583 assign to which LSPs; practically, this is closely linked to the first two decisions listed
1584 above.<a href="#section-3.1-2.3" class="pilcrow">¶</a>
1585 </li>
1586 <li id="section-3.1-2.4">Cause the LSP to be set up and modified to have the right characteristics. This will usually
1587 involve the PCE advising or instructing the PCC at the head end of the LSP, and the PCC will
1588 then signal the LSP across the network.<a href="#section-3.1-2.4" class="pilcrow">¶</a>
1589 </li>
1590 <li id="section-3.1-2.5">Tell the head end of the LSP what traffic to put on the LSP. This may happen after or at the
1591 same time as the LSP is set up. This step is the subject of this document.<a href="#section-3.1-2.5" class="pilcrow">¶</a>
1592 </li>
1593 </ol>
1594 </section>
1595 <section id="section-3.2">
1596 <h3 id="name-elements-of-the-procedure">
1597 <a href="#section-3.2" class="section-number selfRef">3.2. </a><a href="#name-elements-of-the-procedure" class="section-name selfRef">Elements of the Procedure</a>
1598 </h3>
1599 <p id="section-3.2-1">There are three elements in the procedure:<a href="#section-3.2-1" class="pilcrow">¶</a></p>
1600 <ol start="1" type="1" class="normal type-1" id="section-3.2-2">
1601 <li id="section-3.2-2.1">A PCE and a PCC must be able to indicate whether or not they support the use of Flow
1602 Specifications.<a href="#section-3.2-2.1" class="pilcrow">¶</a>
1603 </li>
1604 <li id="section-3.2-2.2">A PCE or PCC must be able to include Flow Specifications in PCEP messages with a clear
1605 understanding of the applicability of those Flow Specifications in each case. This includes
1606 whether the use of such information is mandatory, constrained, or optional and how
1607 overlapping Flow Specifications will be resolved.<a href="#section-3.2-2.2" class="pilcrow">¶</a>
1608 </li>
1609 <li id="section-3.2-2.3">Flow Specification information/state must be synchronized between PCEP peers so that,
1610 on recovery, the peers have the same understanding of which Flow Specifications apply
1611 just as is required in the case of stateful PCE and LSP delegation (see <span><a href="https://www.rfc-editor.org/rfc/rfc8231#section-5.6" class="relref">Section 5.6</a> of [<a href="#RFC8231" class="xref">RFC8231</a>]</span>).<a href="#section-3.2-2.3" class="pilcrow">¶</a>
1612 </li>
1613 </ol>
1614 <p id="section-3.2-3">The following subsections describe these points.<a href="#section-3.2-3" class="pilcrow">¶</a></p>
1615 <section id="section-3.2.1">
1616 <h4 id="name-capability-advertisement">
1617 <a href="#section-3.2.1" class="section-number selfRef">3.2.1. </a><a href="#name-capability-advertisement" class="section-name selfRef">Capability Advertisement</a>
1618 </h4>
1619 <p id="section-3.2.1-1">As with most PCEP capability advertisements, the ability to support Flow Specifications can be
1620 indicated in the PCEP Open message or in IGP PCE capability advertisements.<a href="#section-3.2.1-1" class="pilcrow">¶</a></p>
1621 <div id="open">
1622 <section id="section-3.2.1.1">
1623 <h5 id="name-pcep-open-message">
1624 <a href="#section-3.2.1.1" class="section-number selfRef">3.2.1.1. </a><a href="#name-pcep-open-message" class="section-name selfRef">PCEP Open Message</a>
1625 </h5>
1626 <p id="section-3.2.1.1-1">During PCEP session establishment, a PCC or PCE that supports the procedures described in
1627 this document announces this fact by including the PCE FlowSpec Capability TLV (described in
1628 <a href="#cap" class="xref">Section 4</a>) in the OPEN object carried in the PCEP Open message.<a href="#section-3.2.1.1-1" class="pilcrow">¶</a></p>
1629 <p id="section-3.2.1.1-2">The presence of the PCE FlowSpec Capability TLV in the OPEN object in a PCE's Open message
1630 indicates that the PCE can distribute FlowSpecs to PCCs and can receive FlowSpecs in messages
1631 from PCCs.<a href="#section-3.2.1.1-2" class="pilcrow">¶</a></p>
1632 <p id="section-3.2.1.1-3">The presence of the PCE FlowSpec Capability TLV in the OPEN object in a PCC's Open message
1633 indicates that the PCC supports the FlowSpec functionality described in this document.<a href="#section-3.2.1.1-3" class="pilcrow">¶</a></p>
1634 <p id="section-3.2.1.1-4">If either one of a pair of PCEP peers does not include the PCE FlowSpec Capability TLV in the
1635 OPEN object in its Open message, then the other peer <span class="bcp14">MUST NOT</span> include a FLOWSPEC object in any
1636 PCEP message sent to the peer. If a FLOWSPEC object is received when support has not been indicated,
1637 the receiver will respond with a PCErr message reporting the objects containing the FlowSpec as described
1638 in <span>[<a href="#RFC5440" class="xref">RFC5440</a>]</span>: that is, it will use "Unknown Object" if it does not support this
1639 specification and "Not supported object" if it supports this specification but has not chosen
1640 to support FLOWSPEC objects on this PCEP session.<a href="#section-3.2.1.1-4" class="pilcrow">¶</a></p>
1641 </section>
1642 </div>
1643 <section id="section-3.2.1.2">
1644 <h5 id="name-igp-pce-capabilities-advert">
1645 <a href="#section-3.2.1.2" class="section-number selfRef">3.2.1.2. </a><a href="#name-igp-pce-capabilities-advert" class="section-name selfRef">IGP PCE Capabilities Advertisement</a>
1646 </h5>
1647 <p id="section-3.2.1.2-1">The ability to advertise support for PCEP and PCE features in IGP advertisements is provided
1648 for OSPF in <span>[<a href="#RFC5088" class="xref">RFC5088</a>]</span> and for IS-IS in <span>[<a href="#RFC5089" class="xref">RFC5089</a>]</span>. The mechanism
1649 uses the PCE Discovery TLV, which has a PCE-CAP-FLAGS sub-TLV containing bit flags, each of which
1650 indicates support for a different feature.<a href="#section-3.2.1.2-1" class="pilcrow">¶</a></p>
1651 <p id="section-3.2.1.2-2">This document defines a new PCE-CAP-FLAGS sub-TLV bit, the FlowSpec Capable flag (bit number 16).
1652 Setting the bit indicates that an advertising PCE supports the procedures defined in this document.<a href="#section-3.2.1.2-2" class="pilcrow">¶</a></p>
1653 <p id="section-3.2.1.2-3">Note that while PCE FlowSpec capability may be advertised during discovery, PCEP speakers that wish to
1654 use Flow Specification in PCEP <span class="bcp14">MUST</span> negotiate PCE FlowSpec capability during PCEP session setup, as
1655 specified in <a href="#open" class="xref">Section 3.2.1.1</a>. A PCC <span class="bcp14">MAY</span> initiate PCE FlowSpec capability negotiation at PCEP
1656 session setup even if it did not receive any IGP PCE capability advertisement, and a PCEP peer that
1657 advertised support for FlowSpec in the IGP is not obliged to support these procedures on any given
1658 PCEP session.<a href="#section-3.2.1.2-3" class="pilcrow">¶</a></p>
1659 </section>
1660 </section>
1661 <section id="section-3.2.2">
1662 <h4 id="name-dissemination-procedures">
1663 <a href="#section-3.2.2" class="section-number selfRef">3.2.2. </a><a href="#name-dissemination-procedures" class="section-name selfRef">Dissemination Procedures</a>
1664 </h4>
1665 <p id="section-3.2.2-1">This section describes the procedures to support Flow Specifications in PCEP messages.<a href="#section-3.2.2-1" class="pilcrow">¶</a></p>
1666 <p id="section-3.2.2-2">The primary purpose of distributing Flow Specification information is to allow a PCE to indicate to
1667 a PCC what traffic it should place on a path (such as an LSP or an SR path). This means that the
1668 Flow Specification may be included in:<a href="#section-3.2.2-2" class="pilcrow">¶</a></p>
1669 <ul class="normal">
1670 <li class="normal" id="section-3.2.2-3.1">PCInitiate messages so that an active PCE can indicate the traffic to place on a path at the time
1671 that the PCE instantiates the path.<a href="#section-3.2.2-3.1" class="pilcrow">¶</a>
1672 </li>
1673 <li class="normal" id="section-3.2.2-3.2">PCUpd messages so that an active PCE can indicate or change the traffic to place on a path
1674 that has already been set up.<a href="#section-3.2.2-3.2" class="pilcrow">¶</a>
1675 </li>
1676 <li class="normal" id="section-3.2.2-3.3">PCRpt messages so that a PCC can report the traffic that the PCC will place on the path.<a href="#section-3.2.2-3.3" class="pilcrow">¶</a>
1677 </li>
1678 <li class="normal" id="section-3.2.2-3.4">PCReq messages so that a PCC can indicate what traffic it plans to place on a path when it
1679 requests that the PCE perform a computation in case that information aids the PCE in its work.<a href="#section-3.2.2-3.4" class="pilcrow">¶</a>
1680 </li>
1681 <li class="normal" id="section-3.2.2-3.5">PCRep messages so that a PCE that has been asked to compute a path can suggest which traffic
1682 could be placed on a path that a PCC may be about to set up.<a href="#section-3.2.2-3.5" class="pilcrow">¶</a>
1683 </li>
1684 <li class="normal" id="section-3.2.2-3.6">PCErr messages so that issues related to paths and the traffic they carry can be reported to the
1685 PCE by the PCC and problems with other PCEP messages that carry Flow Specifications can
1686 be reported.<a href="#section-3.2.2-3.6" class="pilcrow">¶</a>
1687 </li>
1688 </ul>
1689 <p id="section-3.2.2-4">To carry Flow Specifications in PCEP messages, this document defines a new PCEP object called the
1690 "PCEP FLOWSPEC object". The object is <span class="bcp14">OPTIONAL</span> in the messages described above and <span class="bcp14">MAY</span> appear more
1691 than once in each message.<a href="#section-3.2.2-4" class="pilcrow">¶</a></p>
1692 <p id="section-3.2.2-5">To describe a traffic flow, the PCEP FLOWSPEC object carries a Flow Filter TLV.<a href="#section-3.2.2-5" class="pilcrow">¶</a></p>
1693 <p id="section-3.2.2-6">The inclusion of multiple PCEP FLOWSPEC objects allows multiple traffic flows to be placed on a single
1694 path.<a href="#section-3.2.2-6" class="pilcrow">¶</a></p>
1695 <p id="section-3.2.2-7">Once a PCE and PCC have established that they can both support the use of Flow Specifications in PCEP
1696 messages, such information may be exchanged at any time for new or existing paths.<a href="#section-3.2.2-7" class="pilcrow">¶</a></p>
1697 <p id="section-3.2.2-8">The application and prioritization of Flow Specifications are described in <a href="#priorities" class="xref">Section 8.7</a>.<a href="#section-3.2.2-8" class="pilcrow">¶</a></p>
1698 <p id="section-3.2.2-9">As per <span>[<a href="#RFC8231" class="xref">RFC8231</a>]</span>, any attributes of the path received from a PCE are subject to the PCC's
1699 local policy. This holds true for the Flow Specifications as well.<a href="#section-3.2.2-9" class="pilcrow">¶</a></p>
1700 </section>
1701 <section id="section-3.2.3">
1702 <h4 id="name-flow-specification-synchron">
1703 <a href="#section-3.2.3" class="section-number selfRef">3.2.3. </a><a href="#name-flow-specification-synchron" class="section-name selfRef">Flow Specification Synchronization</a>
1704 </h4>
1705 <p id="section-3.2.3-1">The Flow Specifications are carried along with the LSP state information as per <span>[<a href="#RFC8231" class="xref">RFC8231</a>]</span>,
1706 making the Flow Specifications part of the LSP database (LSP-DB). Thus, the synchronization of the Flow
1707 Specification information is done as part of LSP-DB synchronization. This may be achieved using normal
1708 state synchronization procedures as described in <span>[<a href="#RFC8231" class="xref">RFC8231</a>]</span> or enhanced state synchronization
1709 procedures as defined in <span>[<a href="#RFC8232" class="xref">RFC8232</a>]</span>.<a href="#section-3.2.3-1" class="pilcrow">¶</a></p>
1710 <p id="section-3.2.3-2">The approach selected will be implementation and deployment specific and will depend on issues such as
1711 how the databases are constructed and what level of synchronization support is needed.<a href="#section-3.2.3-2" class="pilcrow">¶</a></p>
1712 </section>
1713 </section>
1714 </section>
1715 <div id="cap">
1716 <section id="section-4">
1717 <h2 id="name-pce-flowspec-capability-tlv">
1718 <a href="#section-4" class="section-number selfRef">4. </a><a href="#name-pce-flowspec-capability-tlv" class="section-name selfRef">PCE FlowSpec Capability TLV</a>
1719 </h2>
1720 <p id="section-4-1">The PCE-FLOWSPEC-CAPABILITY TLV is an optional TLV that can be carried in the OPEN object
1721 <span>[<a href="#RFC5440" class="xref">RFC5440</a>]</span> to exchange the PCE FlowSpec capabilities of the PCEP speakers.<a href="#section-4-1" class="pilcrow">¶</a></p>
1722 <p id="section-4-2">The format of the PCE-FLOWSPEC-CAPABILITY TLV follows the format of all PCEP TLVs
1723 as defined in <span>[<a href="#RFC5440" class="xref">RFC5440</a>]</span> and is shown in <a href="#capfig" class="xref">Figure 1</a>.<a href="#section-4-2" class="pilcrow">¶</a></p>
1724 <span id="name-pce-flowspec-capability-tlv-"></span><div id="capfig">
1725 <figure id="figure-1">
1726 <div class="alignLeft art-text artwork" id="section-4-3.1">
1727 <pre>
1728 0 1 2 3
1729 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
1730 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
1731 | Type=51 | Length=2 |
1732 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
1733 | Value=0 | Padding |
1734 +---------------------------------------------------------------+
1735 </pre>
1736 </div>
1737 <figcaption><a href="#figure-1" class="selfRef">Figure 1</a>:
1738 <a href="#name-pce-flowspec-capability-tlv-" class="selfRef">PCE-FLOWSPEC-CAPABILITY TLV Format</a>
1739 </figcaption></figure>
1740 </div>
1741 <p id="section-4-4">The type of the PCE-FLOWSPEC-CAPABILITY TLV is 51, and it has a fixed length of 2 octets.
1742 The Value field <span class="bcp14">MUST</span> be set to 0 and <span class="bcp14">MUST</span> be ignored on receipt. The two bytes of padding
1743 <span class="bcp14">MUST</span> be set to zero and ignored on receipt.<a href="#section-4-4" class="pilcrow">¶</a></p>
1744 <p id="section-4-5">The inclusion of this TLV in an OPEN object indicates that the sender can perform FlowSpec handling
1745 as defined in this document.<a href="#section-4-5" class="pilcrow">¶</a></p>
1746 </section>
1747 </div>
1748 <section id="section-5">
1749 <h2 id="name-pcep-flowspec-object">
1750 <a href="#section-5" class="section-number selfRef">5. </a><a href="#name-pcep-flowspec-object" class="section-name selfRef">PCEP FLOWSPEC Object</a>
1751 </h2>
1752 <p id="section-5-1">The PCEP FLOWSPEC object defined in this document is compliant with the PCEP object format
1753 defined in <span>[<a href="#RFC5440" class="xref">RFC5440</a>]</span>.
1754
1755 It is <span class="bcp14">OPTIONAL</span> in the PCReq, PCRep, PCErr, PCInitiate,
1756 PCRpt, and PCUpd messages and <span class="bcp14">MAY</span> be present zero, one, or more times. Each instance of the
1757 object specifies a separate traffic flow.<a href="#section-5-1" class="pilcrow">¶</a></p>
1758 <p id="section-5-2">The PCEP FLOWSPEC object <span class="bcp14">MAY</span> carry a FlowSpec filter rule encoded in a Flow Filter TLV as defined in <a href="#tlv" class="xref">Section 6</a>.<a href="#section-5-2" class="pilcrow">¶</a></p>
1759 <p id="section-5-3">The FLOWSPEC Object-Class is 43 (to be assigned by IANA).<a href="#section-5-3" class="pilcrow">¶</a></p>
1760 <p id="section-5-4">The FLOWSPEC Object-Type is 1.<a href="#section-5-4" class="pilcrow">¶</a></p>
1761 <p id="section-5-5">The format of the body of the PCEP FLOWSPEC object is shown in <a href="#FlowSpecFig" class="xref">Figure 2</a>.<a href="#section-5-5" class="pilcrow">¶</a></p>
1762 <span id="name-pcep-flowspec-object-body-f"></span><div id="FlowSpecFig">
1763 <figure id="figure-2">
1764 <div class="alignLeft art-text artwork" id="section-5-6.1">
1765 <pre>
1766 0 1 2 3
1767 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
1768 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
1769 | FS-ID |
1770 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
1771 | AFI | Reserved | Flags |L|R|
1772 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
1773 | |
1774 // TLVs //
1775 | |
1776 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
1777 </pre>
1778 </div>
1779 <figcaption><a href="#figure-2" class="selfRef">Figure 2</a>:
1780 <a href="#name-pcep-flowspec-object-body-f" class="selfRef">PCEP FLOWSPEC Object Body Format</a>
1781 </figcaption></figure>
1782 </div>
1783 <span class="break"></span><dl class="dlParallel" id="section-5-7">
1784 <dt id="section-5-7.1">FS-ID (32 bits):</dt>
1785 <dd style="margin-left: 1.5em" id="section-5-7.2"> A PCEP-specific identifier for the FlowSpec information. A PCE
1786 or PCC creates an FS-ID for each FlowSpec that it originates, and the value is
1787 unique within the scope of that PCE or PCC and is constant for the lifetime of a
1788 PCEP session. All subsequent PCEP messages can identify the FlowSpec using the
1789 FS-ID. The values 0 and 0xFFFFFFFF are reserved and <span class="bcp14">MUST NOT</span> be used. Note
1790 that <span>[<a href="#I-D.gont-numeric-ids-sec-considerations" class="xref">NUMERIC-IDS-SEC</a>]</span> gives advice on
1791 assigning transient numeric identifiers such as the FS-ID so as to minimize
1792 security risks.<a href="#section-5-7.2" class="pilcrow">¶</a>
1793 </dd>
1794 <dd class="break"></dd>
1795 <dt id="section-5-7.3">AFI (16 bits):</dt>
1796 <dd style="margin-left: 1.5em" id="section-5-7.4"> Address Family Identifier as used in BGP <span>[<a href="#RFC4760" class="xref">RFC4760</a>]</span>
1797 (AFI=1 for IPv4 or VPNv4, AFI=2 for IPv6 and VPNv6 as per
1798 <span>[<a href="#RFC8956" class="xref">RFC8956</a>]</span>).<a href="#section-5-7.4" class="pilcrow">¶</a>
1799 </dd>
1800 <dd class="break"></dd>
1801 <dt id="section-5-7.5">Reserved (8 bits):</dt>
1802 <dd style="margin-left: 1.5em" id="section-5-7.6">
1803 <span class="bcp14">MUST</span> be set to zero on transmission and ignored on receipt.<a href="#section-5-7.6" class="pilcrow">¶</a>
1804 </dd>
1805 <dd class="break"></dd>
1806 <dt id="section-5-7.7">Flags (8 bits):</dt>
1807 <dd style="margin-left: 1.5em" id="section-5-7.8">
1808 <p id="section-5-7.8.1">Two flags are currently assigned:<a href="#section-5-7.8.1" class="pilcrow">¶</a></p>
1809 <span class="break"></span><dl class="dlParallel" id="section-5-7.8.2">
1810 <dt id="section-5-7.8.2.1">R bit:</dt>
1811 <dd style="margin-left: 1.5em" id="section-5-7.8.2.2">The Remove bit is set when a PCEP FLOWSPEC object is included in a PCEP
1812 message to indicate removal of the Flow Specification from the associated tunnel.
1813 If the bit is clear, the Flow Specification is being added or modified.<a href="#section-5-7.8.2.2" class="pilcrow">¶</a>
1814 </dd>
1815 <dd class="break"></dd>
1816 <dt id="section-5-7.8.2.3">L bit:</dt>
1817 <dd style="margin-left: 1.5em" id="section-5-7.8.2.4">The Longest Prefix Match (LPM) bit is set to indicate that the Flow
1818 Specification is to be installed as a route subject to LPM
1819 forwarding. If the bit is clear, the Flow Specification described by the
1820 Flow Filter TLV (see <a href="#tlv" class="xref">Section 6</a>) is to be installed as a Flow
1821 Specification. If the bit is set, only Flow Specifications that describe
1822 IPv4 or IPv6 destinations are meaningful in the Flow Filter TLV, and others are ignored.
1823
1824 If the L
1825 is set and the receiver does not support the use of Flow Specifications that
1826 are present in the Flow Filter TLV for the installation of a route subject to
1827 LPM forwarding, then the PCEP peer <span class="bcp14">MUST</span> respond with a PCErr
1828 message with Error-Type 30 (FlowSpec Error) and Error-value 5 (Unsupported
1829 LPM Route).<a href="#section-5-7.8.2.4" class="pilcrow">¶</a>
1830 </dd>
1831 <dd class="break"></dd>
1832 </dl>
1833 </dd>
1834 <dd class="break"></dd>
1835 </dl>
1836 <p id="section-5-8">Unassigned bits <span class="bcp14">MUST</span> be set to zero on transmission and ignored on receipt.<a href="#section-5-8" class="pilcrow">¶</a></p>
1837 <p id="section-5-9">If the PCEP speaker receives a message with the R bit set in the FLOWSPEC object and the Flow Specification
1838 identified with an FS-ID does not exist, it <span class="bcp14">MUST</span> generate a PCErr with Error-Type 30 (FlowSpec Error) and Error-value 4 (Unknown FlowSpec).<a href="#section-5-9" class="pilcrow">¶</a></p>
1839 <p id="section-5-10">If the PCEP speaker does not understand or support the AFI in the FLOWSPEC message, the PCEP peer
1840 <span class="bcp14">MUST</span> respond with a PCErr message with Error-Type 30 (FlowSpec Error) and Error-value 2
1841 (Malformed FlowSpec).<a href="#section-5-10" class="pilcrow">¶</a></p>
1842 <p id="section-5-11">The following TLVs can be used in the FLOWSPEC object:<a href="#section-5-11" class="pilcrow">¶</a></p>
1843 <span class="break"></span><dl class="dlParallel" id="section-5-12">
1844 <dt id="section-5-12.1">Speaker Entity Identifier TLV:</dt>
1845 <dd style="margin-left: 1.5em" id="section-5-12.2"> As specified in <span>[<a href="#RFC8232" class="xref">RFC8232</a>]</span>, the SPEAKER-ENTITY-ID TLV
1846 encodes a unique identifier for the node that does not change during the lifetime of the PCEP
1847 speaker. This is used to uniquely identify the FlowSpec originator and thus is used in conjunction
1848 with the FS-ID to uniquely identify the FlowSpec information. This TLV <span class="bcp14">MUST</span> be included. If the TLV
1849 is missing, the PCEP peer <span class="bcp14">MUST</span> respond with a PCErr message with Error-Type 30 (FlowSpec Error) and
1850 Error-value 2 (Malformed FlowSpec). If more than one instance of this TLV is present, the first <span class="bcp14">MUST</span> be
1851 processed, and subsequent instances <span class="bcp14">MUST</span> be ignored.<a href="#section-5-12.2" class="pilcrow">¶</a>
1852 </dd>
1853 <dd class="break"></dd>
1854 <dt id="section-5-12.3">Flow Filter TLV (variable):</dt>
1855 <dd style="margin-left: 1.5em" id="section-5-12.4"> One TLV <span class="bcp14">MAY</span> be included. The Flow Filter TLV is <span class="bcp14">OPTIONAL</span> when the R bit
1856 is set.<a href="#section-5-12.4" class="pilcrow">¶</a>
1857 </dd>
1858 <dd class="break"></dd>
1859 </dl>
1860 <p id="section-5-13">The Flow Filter TLV <span class="bcp14">MUST</span> be present when the R bit is clear. If the
1861 TLV is missing when the R bit is clear, the PCEP peer <span class="bcp14">MUST</span> respond with a PCErr message with
1862 Error-Type 30 (FlowSpec Error) and Error-value 2 (Malformed FlowSpec).<a href="#section-5-13" class="pilcrow">¶</a></p>
1863 <p id="section-5-14">Filtering based on the L2 fields is out of scope of this document.<a href="#section-5-14" class="pilcrow">¶</a></p>
1864 </section>
1865 <div id="tlv">
1866 <section id="section-6">
1867 <h2 id="name-flow-filter-tlv">
1868 <a href="#section-6" class="section-number selfRef">6. </a><a href="#name-flow-filter-tlv" class="section-name selfRef">Flow Filter TLV</a>
1869 </h2>
1870 <p id="section-6-1">One new PCEP TLV is defined to convey Flow Specification filtering rules that specify
1871 what traffic is carried on a path. The TLV follows the format of all PCEP TLVs as defined
1872 in <span>[<a href="#RFC5440" class="xref">RFC5440</a>]</span>. The Type field values come from the code point space for
1873 PCEP TLVs and has the value 52 for Flow Filter TLV.<a href="#section-6-1" class="pilcrow">¶</a></p>
1874 <p id="section-6-2">The Value field of the TLV contains one or more sub-TLVs (the Flow Specification TLVs) as defined in <a href="#subtlv" class="xref">Section 7</a>, and they represent the complete
1875 definition of a Flow Specification for traffic to be placed on the tunnel. This tunnel is
1876 indicated by the PCEP message in which the PCEP FLOWSPEC object is carried. The set of Flow
1877 Specification TLVs in a single instance of a Flow Filter TLV is
1878 combined to indicate the specific Flow Specification. Note that the PCEP FLOWSPEC object can
1879 include just one Flow Filter TLV.<a href="#section-6-2" class="pilcrow">¶</a></p>
1880 <p id="section-6-3">Further Flow Specifications can be included in a PCEP message by including additional
1881 FLOWSPEC objects.<a href="#section-6-3" class="pilcrow">¶</a></p>
1882 <p id="section-6-4"> In the future, there may be a desire to add support for L2 Flow
1883 Specifications (such as described in <span>[<a href="#I-D.ietf-idr-flowspec-l2vpn" class="xref">BGP-L2VPN</a>]</span>).<a href="#section-6-4" class="pilcrow">¶</a></p>
1884 </section>
1885 </div>
1886 <div id="subtlv">
1887 <section id="section-7">
1888 <h2 id="name-flow-specification-tlvs">
1889 <a href="#section-7" class="section-number selfRef">7. </a><a href="#name-flow-specification-tlvs" class="section-name selfRef">Flow Specification TLVs</a>
1890 </h2>
1891 <p id="section-7-1">The Flow Filter TLV carries one or more Flow Specification TLVs. The Flow Specification TLV
1892 follows the format of all PCEP TLVs as defined in <span>[<a href="#RFC5440" class="xref">RFC5440</a>]</span>. However, the Type values
1893 are selected from a separate IANA registry (see <a href="#iana" class="xref">Section 10.3</a>) rather than from the common
1894 PCEP TLV registry.<a href="#section-7-1" class="pilcrow">¶</a></p>
1895 <p id="section-7-2">Type values are chosen so that there can be commonality with Flow Specifications defined for use
1896 with BGP <span>[<a href="#RFC8955" class="xref">RFC8955</a>]</span> <span>[<a href="#RFC8956" class="xref">RFC8956</a>]</span>. This
1897 is possible because the BGP Flow Spec encoding uses a single octet to encode the type, whereas PCEP uses
1898 2 octets. Thus, the space of values for the Type field is partitioned as shown in <a href="#fspectlvs" class="xref">Table 1</a>.<a href="#section-7-2" class="pilcrow">¶</a></p>
1899 <span id="name-flow-specification-tlv-type"></span><div id="fspectlvs">
1900 <table class="center" id="table-1">
1901 <caption>
1902 <a href="#table-1" class="selfRef">Table 1</a>:
1903 <a href="#name-flow-specification-tlv-type" class="selfRef">Flow Specification TLV Type Ranges</a>
1904 </caption>
1905 <thead>
1906 <tr>
1907 <th class="text-left" rowspan="1" colspan="1">Range</th>
1908 <th class="text-left" rowspan="1" colspan="1">Description</th>
1909 </tr>
1910 </thead>
1911 <tbody>
1912 <tr>
1913 <td class="text-left" rowspan="1" colspan="1">0-255</td>
1914 <td class="text-left" rowspan="1" colspan="1">
1915 <p id="section-7-3.2.1.2.1">Per BGP Flow Spec registry defined by
1916 <span>[<a href="#RFC8955" class="xref">RFC8955</a>]</span> and
1917 <span>[<a href="#RFC8956" class="xref">RFC8956</a>]</span>.<a href="#section-7-3.2.1.2.1" class="pilcrow">¶</a></p>
1918 <p id="section-7-3.2.1.2.2"> Not to be allocated in this registry.<a href="#section-7-3.2.1.2.2" class="pilcrow">¶</a></p>
1919 </td>
1920 </tr>
1921 <tr>
1922 <td class="text-left" rowspan="1" colspan="1">256-65535</td>
1923 <td class="text-left" rowspan="1" colspan="1">New PCEP Flow Specifications allocated according
1924 to the registry defined in this document.</td>
1925 </tr>
1926 </tbody>
1927 </table>
1928 </div>
1929 <p id="section-7-4"><span>[<a href="#RFC8955" class="xref">RFC8955</a>]</span> is the reference for the "Flow Spec Component Types" registry and defines the allocations it contains. <span>[<a href="#RFC8956" class="xref">RFC8956</a>]</span> requested the creation of the "Flow Spec IPv6 Component Types" registry, as well as its initial allocations. If the AFI (in the
1930 FLOWSPEC object) is set to IPv4, the range 0..255 is as per "Flow Spec Component Types"
1931 <span>[<a href="#RFC8955" class="xref">RFC8955</a>]</span>; if the AFI is set to IPv6, the range 0..255 is as per "Flow
1932 Spec IPv6 Component Types" <span>[<a href="#RFC8956" class="xref">RFC8956</a>]</span>.<a href="#section-7-4" class="pilcrow">¶</a></p>
1933 <p id="section-7-5">The content of the Value field in each TLV is specific to the type/AFI and describes the parameters
1934 of the Flow Specification. The definition of the format of many of these Value fields is inherited
1935 from BGP specifications. Specifically, the inheritance is from <span>[<a href="#RFC8955" class="xref">RFC8955</a>]</span> and
1936 <span>[<a href="#RFC8956" class="xref">RFC8956</a>]</span>, but it may also be inherited from future BGP specifications.<a href="#section-7-5" class="pilcrow">¶</a></p>
1937 <p id="section-7-6">When multiple Flow Specification TLVs are present in a single Flow Filter TLV, they are combined to
1938 produce a more detailed specification of a flow. For examples and rules about how this is achieved,
1939 see <span>[<a href="#RFC8955" class="xref">RFC8955</a>]</span>. As described in <span>[<a href="#RFC8955" class="xref">RFC8955</a>]</span>,
1940 where it says "A given component type <span class="bcp14">MAY</span> (exactly once) be present in the Flow Specification", a Flow
1941 Filter TLV <span class="bcp14">MUST NOT</span> contain more than one Flow Specification TLV of the same type: an implementation
1942 that receives a PCEP message with a Flow Filter TLV that contains more than one Flow Specification TLV
1943 of the same type <span class="bcp14">MUST</span> respond with a PCErr message with Error-Type 30 (FlowSpec Error) and Error-value 2
1944 (Malformed FlowSpec) and <span class="bcp14">MUST NOT</span> install the Flow Specification.<a href="#section-7-6" class="pilcrow">¶</a></p>
1945 <p id="section-7-7">An implementation that receives a PCEP message carrying a Flow Specification TLV with a type value
1946 that it does not recognize or support <span class="bcp14">MUST</span> respond with a PCErr message with Error-Type 30
1947 (FlowSpec Error) and Error-value 1 (Unsupported FlowSpec) and <span class="bcp14">MUST NOT</span> install the Flow Specification.<a href="#section-7-7" class="pilcrow">¶</a></p>
1948 <p id="section-7-8">When used in other protocols (such as BGP), these Flow Specifications are also associated with actions
1949 to indicate how traffic matching the Flow Specification should be treated. In PCEP, however, the only
1950 action is to associate the traffic with a tunnel and to forward matching traffic onto that path, so
1951 no encoding of an action is needed.<a href="#section-7-8" class="pilcrow">¶</a></p>
1952 <p id="section-7-9"><a href="#priorities" class="xref">Section 8.7</a> describes how overlapping Flow Specifications are prioritized and
1953 handled.<a href="#section-7-9" class="pilcrow">¶</a></p>
1954 <p id="section-7-10">All Flow Specification TLVs with Types in the range 0 to 255 have values defined
1955 for use in BGP (for example, in <span>[<a href="#RFC8955" class="xref">RFC8955</a>]</span> and
1956 <span>[<a href="#RFC8956" class="xref">RFC8956</a>]</span>) and are set using the BGP encoding
1957 but without the type octet (the relevant information is in the
1958 Type field of the TLV). The Value field is padded with trailing
1959 zeros to achieve 4-byte alignment.<a href="#section-7-10" class="pilcrow">¶</a></p>
1960 <p id="section-7-11">This document defines the following new types:<a href="#section-7-11" class="pilcrow">¶</a></p>
1961 <span id="name-flow-specification-tlv-types"></span><div id="tlvFigthis">
1962 <table class="left" id="table-2">
1963 <caption>
1964 <a href="#table-2" class="selfRef">Table 2</a>:
1965 <a href="#name-flow-specification-tlv-types" class="selfRef">Flow Specification TLV Types Defined in this Document</a>
1966 </caption>
1967 <thead>
1968 <tr>
1969 <th class="text-left" rowspan="1" colspan="1"> Type </th>
1970 <th class="text-left" rowspan="1" colspan="1"> Description</th>
1971 <th class="text-left" rowspan="1" colspan="1"> Value Defined In</th>
1972 </tr>
1973 </thead>
1974 <tbody>
1975 <tr>
1976 <td class="text-left" rowspan="1" colspan="1">256</td>
1977 <td class="text-left" rowspan="1" colspan="1">Route Distinguisher</td>
1978 <td class="text-left" rowspan="1" colspan="1">RFC 9168</td>
1979 </tr>
1980 <tr>
1981 <td class="text-left" rowspan="1" colspan="1">257</td>
1982 <td class="text-left" rowspan="1" colspan="1">IPv4 Multicast Flow</td>
1983 <td class="text-left" rowspan="1" colspan="1">RFC 9168</td>
1984 </tr>
1985 <tr>
1986 <td class="text-left" rowspan="1" colspan="1">258</td>
1987 <td class="text-left" rowspan="1" colspan="1">IPv6 Multicast Flow</td>
1988 <td class="text-left" rowspan="1" colspan="1">RFC 9168</td>
1989 </tr>
1990 </tbody>
1991 </table>
1992 </div>
1993 <p id="section-7-13">To allow identification of a VPN in PCEP via a Route Distinguisher (RD) <span>[<a href="#RFC4364" class="xref">RFC4364</a>]</span>,
1994 a new TLV, ROUTE-DISTINGUISHER TLV, is defined in this document. A Flow Specification TLV with
1995 Type 256 (ROUTE-DISTINGUISHER TLV) carries an RD value, which is used to identify that other flow filter
1996 information (for example, an IPv4 destination prefix) is associated with a specific VPN identified
1997 by the RD. See <a href="#vpn-id" class="xref">Section 8.6</a> for further discussion of VPN identification.<a href="#section-7-13" class="pilcrow">¶</a></p>
1998 <span id="name-the-format-of-the-route-dis"></span><div id="rdtlv">
1999 <figure id="figure-3">
2000 <div class="alignLeft art-text artwork" id="section-7-14.1">
2001 <pre>
2002 0 1 2 3
2003 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
2004 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
2005 | Type=256 | Length=8 |
2006 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
2007 | Route Distinguisher |
2008 | |
2009 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
2010 </pre>
2011 </div>
2012 <figcaption><a href="#figure-3" class="selfRef">Figure 3</a>:
2013 <a href="#name-the-format-of-the-route-dis" class="selfRef">The Format of the ROUTE-DISTINGUISHER TLV</a>
2014 </figcaption></figure>
2015 </div>
2016 <p id="section-7-15">The format of the RD is as per <span>[<a href="#RFC4364" class="xref">RFC4364</a>]</span>.<a href="#section-7-15" class="pilcrow">¶</a></p>
2017 <p id="section-7-16">Although it may be possible to describe a multicast Flow Specification from the
2018 combination of other Flow Specification TLVs with specific values, it is more convenient
2019 to use a dedicated Flow Specification TLV. Flow Specification TLVs with Type
2020 values 257 and 258 are used to identify a multicast flow for IPv4 and IPv6, respectively.
2021 The Value field is encoded as shown in <a href="#mcastfig" class="xref">Figure 4</a>.<a href="#section-7-16" class="pilcrow">¶</a></p>
2022 <span id="name-multicast-flow-specificatio"></span><div id="mcastfig">
2023 <figure id="figure-4">
2024 <div class="alignLeft art-text artwork" id="section-7-17.1">
2025 <pre>
2026 0 1 2 3
2027 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
2028 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
2029 | Reserved |S|G| Src Mask Len | Grp Mask Len |
2030 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
2031 ~ Source Address ~
2032 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
2033 ~ Group multicast Address ~
2034 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
2035 </pre>
2036 </div>
2037 <figcaption><a href="#figure-4" class="selfRef">Figure 4</a>:
2038 <a href="#name-multicast-flow-specificatio" class="selfRef">Multicast Flow Specification TLV Encoding</a>
2039 </figcaption></figure>
2040 </div>
2041 <p id="section-7-18">The address fields and address mask lengths of the two Multicast Flow Specification TLVs
2042 contain source and group prefixes for matching against packet flows. Note that the two address
2043 fields are 32 bits for an IPv4 Multicast Flow and 128 bits for an IPv6 Multicast Flow.<a href="#section-7-18" class="pilcrow">¶</a></p>
2044 <p id="section-7-19">The Reserved field <span class="bcp14">MUST</span> be set to zero and ignored on receipt.<a href="#section-7-19" class="pilcrow">¶</a></p>
2045 <p id="section-7-20">Two bit flags (S and G) are defined to describe the multicast wildcarding in use.
2046 If the S bit is set, then source wildcarding is in use, and the values in the Source Mask Length
2047 and Source Address fields <span class="bcp14">MUST</span> be ignored. If the G bit is set, then group wildcarding is in
2048 use, and the values in the Group Mask Length and Group multicast Address fields <span class="bcp14">MUST</span> be ignored.
2049 The G bit <span class="bcp14">MUST NOT</span> be set unless the S bit is also set: if a Multicast Flow Specification TLV
2050 is received with S bit = 0 and G bit = 1, the receiver <span class="bcp14">MUST</span> respond with a PCErr with Error-Type 30 (FlowSpec Error) and Error-value 2 (Malformed FlowSpec).<a href="#section-7-20" class="pilcrow">¶</a></p>
2051 <p id="section-7-21">The three multicast mappings may be achieved as follows:<a href="#section-7-21" class="pilcrow">¶</a></p>
2052 <ul class="normal ulEmpty">
2053 <li class="normal ulEmpty" id="section-7-22.1">(S, G) - S bit = 0, G bit = 0, the Source Address and Group multicast Address prefixes are
2054 both used to define the multicast flow.<a href="#section-7-22.1" class="pilcrow">¶</a>
2055 </li>
2056 <li class="normal ulEmpty" id="section-7-22.2">(*, G) - S bit = 1, G bit = 0, the Group multicast Address prefix is used to define the
2057 multicast flow, but the Source Address prefix is ignored.<a href="#section-7-22.2" class="pilcrow">¶</a>
2058 </li>
2059 <li class="normal ulEmpty" id="section-7-22.3">(*, *) - S bit = 1, G bit = 1, the Source Address and Group multicast Address prefixes are
2060 both ignored.<a href="#section-7-22.3" class="pilcrow">¶</a>
2061 </li>
2062 </ul>
2063 </section>
2064 </div>
2065 <div id="detailed">
2066 <section id="section-8">
2067 <h2 id="name-detailed-procedures">
2068 <a href="#section-8" class="section-number selfRef">8. </a><a href="#name-detailed-procedures" class="section-name selfRef">Detailed Procedures</a>
2069 </h2>
2070 <p id="section-8-1">This section outlines some specific detailed procedures for using the protocol extensions
2071 defined in this document.<a href="#section-8-1" class="pilcrow">¶</a></p>
2072 <div id="default">
2073 <section id="section-8.1">
2074 <h3 id="name-default-behavior-and-backwa">
2075 <a href="#section-8.1" class="section-number selfRef">8.1. </a><a href="#name-default-behavior-and-backwa" class="section-name selfRef">Default Behavior and Backward Compatibility</a>
2076 </h3>
2077 <p id="section-8.1-1">The default behavior is that no Flow Specification is applied to a tunnel. That is,
2078 the default is that the FLOWSPEC object is not used, as is the case in all systems
2079 before the implementation of this specification.<a href="#section-8.1-1" class="pilcrow">¶</a></p>
2080 <p id="section-8.1-2">In this case, it is a local matter (such as through configuration) how tunnel head ends
2081 are instructed in terms of what traffic to place on a tunnel.<a href="#section-8.1-2" class="pilcrow">¶</a></p>
2082 <p id="section-8.1-3"><span>[<a href="#RFC5440" class="xref">RFC5440</a>]</span> describes how receivers respond when they see unknown PCEP
2083 objects.<a href="#section-8.1-3" class="pilcrow">¶</a></p>
2084 </section>
2085 </div>
2086 <div id="composite">
2087 <section id="section-8.2">
2088 <h3 id="name-composite-flow-specificatio">
2089 <a href="#section-8.2" class="section-number selfRef">8.2. </a><a href="#name-composite-flow-specificatio" class="section-name selfRef">Composite Flow Specifications</a>
2090 </h3>
2091 <p id="section-8.2-1">Flow Specifications may be represented by a single Flow Specification TLV or may require a
2092 more complex description using multiple Flow Specification TLVs. For example, a flow
2093 indicated by a source-destination pair of IPv6 addresses would be described by the
2094 combination of Destination IPv6 Prefix and Source IPv6 Prefix Flow Specification TLVs.<a href="#section-8.2-1" class="pilcrow">¶</a></p>
2095 </section>
2096 </div>
2097 <div id="modify">
2098 <section id="section-8.3">
2099 <h3 id="name-modifying-flow-specificatio">
2100 <a href="#section-8.3" class="section-number selfRef">8.3. </a><a href="#name-modifying-flow-specificatio" class="section-name selfRef">Modifying Flow Specifications</a>
2101 </h3>
2102 <p id="section-8.3-1">A PCE may want to modify a Flow Specification associated with a tunnel, or a PCC may
2103 want to report a change to the Flow Specification it is using with a tunnel.<a href="#section-8.3-1" class="pilcrow">¶</a></p>
2104 <p id="section-8.3-2">It is important to identify the specific Flow Specification so it is clear that
2105 this is a modification of an existing flow and not the addition of a new flow as described
2106 in <a href="#multiple" class="xref">Section 8.4</a>. The FS-ID field of the PCEP FLOWSPEC object is used to
2107 identify a specific Flow Specification in the context of the content of the Speaker Entity
2108 Identifier TLV.<a href="#section-8.3-2" class="pilcrow">¶</a></p>
2109 <p id="section-8.3-3">When modifying a Flow Specification, all Flow Specification TLVs for the intended specification
2110 of the flow <span class="bcp14">MUST</span> be included in the PCEP FLOWSPEC object. The FS-ID <span class="bcp14">MUST</span> be retained from the
2111 previous description of the flow, and the same Speaker Entity Identifier TLV <span class="bcp14">MUST</span> be used.<a href="#section-8.3-3" class="pilcrow">¶</a></p>
2112 </section>
2113 </div>
2114 <div id="multiple">
2115 <section id="section-8.4">
2116 <h3 id="name-multiple-flow-specification">
2117 <a href="#section-8.4" class="section-number selfRef">8.4. </a><a href="#name-multiple-flow-specification" class="section-name selfRef">Multiple Flow Specifications</a>
2118 </h3>
2119 <p id="section-8.4-1">It is possible that traffic from multiple flows will be placed on a single tunnel. In some cases,
2120 it is possible to define these within a single PCEP FLOWSPEC object by widening the scope of a Flow
2121 Specification TLV: for example, traffic to two destination IPv4 prefixes might be captured by a single
2122 Flow Specification TLV with type "Destination" with a suitably adjusted prefix. However, this is
2123 unlikely to be possible in most scenarios, and it must be recalled that it is not permitted to include
2124 two Flow Specification TLVs of the same type within one Flow Filter TLV.<a href="#section-8.4-1" class="pilcrow">¶</a></p>
2125 <p id="section-8.4-2">The normal procedure, therefore, is to carry each Flow Specification in its own PCEP FLOWSPEC object.
2126 Multiple objects may be present on a single PCEP message, or multiple PCEP messages may be used.<a href="#section-8.4-2" class="pilcrow">¶</a></p>
2127 </section>
2128 </div>
2129 <div id="addremove">
2130 <section id="section-8.5">
2131 <h3 id="name-adding-and-removing-flow-sp">
2132 <a href="#section-8.5" class="section-number selfRef">8.5. </a><a href="#name-adding-and-removing-flow-sp" class="section-name selfRef">Adding and Removing Flow Specifications</a>
2133 </h3>
2134 <p id="section-8.5-1">The Remove bit in the PCEP FLOWSPEC object is left clear when a Flow Specification is being
2135 added or modified.<a href="#section-8.5-1" class="pilcrow">¶</a></p>
2136 <p id="section-8.5-2">To remove a Flow Specification, a PCEP FLOWSPEC object is included with the FS-ID matching the
2137 one being removed, and the R bit is set to indicate removal. In this case, it is not necessary to
2138 include any Flow Specification TLVs.<a href="#section-8.5-2" class="pilcrow">¶</a></p>
2139 <p id="section-8.5-3">If the R bit is set and Flow Specification TLVs are present, an implementation <span class="bcp14">MAY</span> ignore them. If
2140 the implementation checks the Flow Specification TLVs against those recorded for the FS-ID and Speaker
2141 Entity Identifier of the Flow Specification being removed and finds a mismatch, the Flow Specification matching the FS-ID
2142 <span class="bcp14">MUST</span> still be removed, and the implementation <span class="bcp14">SHOULD</span> record a local exception or log.<a href="#section-8.5-3" class="pilcrow">¶</a></p>
2143 </section>
2144 </div>
2145 <div id="vpn-id">
2146 <section id="section-8.6">
2147 <h3 id="name-vpn-identifiers">
2148 <a href="#section-8.6" class="section-number selfRef">8.6. </a><a href="#name-vpn-identifiers" class="section-name selfRef">VPN Identifiers</a>
2149 </h3>
2150 <p id="section-8.6-1">VPN instances are identified in BGP using RDs <span>[<a href="#RFC4364" class="xref">RFC4364</a>]</span>. These
2151 values are not normally considered to have any meaning outside of the network, and they are not encoded
2152 in data packets belonging to the VPNs. However, RDs provide a useful way of identifying VPN instances
2153 and are often manually or automatically assigned to VPNs as they are provisioned.<a href="#section-8.6-1" class="pilcrow">¶</a></p>
2154 <p id="section-8.6-2">Thus, the RD provides a useful way to indicate that traffic for a particular VPN should be placed on a
2155 given tunnel. The tunnel head end will need to interpret this Flow Specification not as a filter on
2156 the fields of data packets but rather using the other mechanisms that it already uses to identify VPN traffic.
2157 These mechanisms could be based on the incoming port (for port-based VPNs) or may leverage knowledge of the VPN Routing and Forwarding (VRF) that
2158 is in use for the traffic.<a href="#section-8.6-2" class="pilcrow">¶</a></p>
2159 </section>
2160 </div>
2161 <div id="priorities">
2162 <section id="section-8.7">
2163 <h3 id="name-priorities-and-overlapping-">
2164 <a href="#section-8.7" class="section-number selfRef">8.7. </a><a href="#name-priorities-and-overlapping-" class="section-name selfRef">Priorities and Overlapping Flow Specifications</a>
2165 </h3>
2166 <p id="section-8.7-1">Flow Specifications can overlap. For example, two different Flow Specifications may be identical except
2167 for the length of the prefix in the destination address. In these cases, the PCC must determine how to
2168 prioritize the Flow Specifications so as to know which path to assign packets that match both Flow Specifications. That is, the PCC must assign a precedence to the Flow Specifications so that it checks
2169 each incoming packet for a match in a predictable order.<a href="#section-8.7-1" class="pilcrow">¶</a></p>
2170 <p id="section-8.7-2">The processing of BGP Flow Specifications is described in
2171 <span>[<a href="#RFC8955" class="xref">RFC8955</a>]</span>. Section <a href="https://www.rfc-editor.org/rfc/rfc8955#section-5.1" class="relref">5.1</a> of
2172 that document explains the order of traffic filtering rules to
2173 be executed by an implementation of that specification.<a href="#section-8.7-2" class="pilcrow">¶</a></p>
2174 <p id="section-8.7-3">PCCs <span class="bcp14">MUST</span> apply the same ordering rules as defined in <span>[<a href="#RFC8955" class="xref">RFC8955</a>]</span>.<a href="#section-8.7-3" class="pilcrow">¶</a></p>
2175 <p id="section-8.7-4">Furthermore, it is possible that Flow Specifications will be distributed
2176 by BGP as well as by PCEP as described in this document. In such
2177 cases, implementations supporting both approaches <span class="bcp14">MUST</span> apply the
2178 prioritization and ordering rules as set out in <span>[<a href="#RFC8955" class="xref">RFC8955</a>]</span>
2179 regardless of which protocol distributed the Flow Specifications.
2180 However, implementations <span class="bcp14">MAY</span> provide a configuration control to
2181 allow one protocol to take precedence over the other; this may be
2182 particularly useful if the Flow Specifications make identical matches
2183 on traffic but have different actions. It is <span class="bcp14">RECOMMENDED</span> that a message be
2184 logged for the operator to understand the behavior when
2185 two Flow Specifications distributed by different protocols overlap,
2186 especially when one acts to replace another.<a href="#section-8.7-4" class="pilcrow">¶</a></p>
2187 <p id="section-8.7-5"><a href="#mg-mxfspec" class="xref">Section 12.1</a> of this document covers manageability considerations relevant to the
2188 prioritized ordering of Flow Specifications.<a href="#section-8.7-5" class="pilcrow">¶</a></p>
2189 <p id="section-8.7-6">An implementation that receives a PCEP message carrying a Flow Specification that it cannot resolve
2190 against other Flow Specifications already installed (for example, because the new Flow Specification has
2191 irresolvable conflicts with other Flow Specifications that are already installed) <span class="bcp14">MUST</span> respond with a PCErr
2192 message with Error-Type 30 (FlowSpec Error) and Error-value 3 (Unresolvable Conflict) and <span class="bcp14">MUST NOT</span> install the
2193 Flow Specification.<a href="#section-8.7-6" class="pilcrow">¶</a></p>
2194 </section>
2195 </div>
2196 </section>
2197 </div>
2198 <div id="messages">
2199 <section id="section-9">
2200 <h2 id="name-pcep-messages">
2201 <a href="#section-9" class="section-number selfRef">9. </a><a href="#name-pcep-messages" class="section-name selfRef">PCEP Messages</a>
2202 </h2>
2203 <p id="section-9-1">This section describes the format of messages that contain FLOWSPEC objects. The
2204 only difference from previous message formats is the inclusion of that object.<a href="#section-9-1" class="pilcrow">¶</a></p>
2205 <p id="section-9-2">The figures in this section use the notation defined in <span>[<a href="#RFC5511" class="xref">RFC5511</a>]</span>.<a href="#section-9-2" class="pilcrow">¶</a></p>
2206 <p id="section-9-3">The FLOWSPEC object is <span class="bcp14">OPTIONAL</span> and <span class="bcp14">MAY</span> be carried in the PCEP messages.<a href="#section-9-3" class="pilcrow">¶</a></p>
2207 <p id="section-9-4">The PCInitiate message is defined in <span>[<a href="#RFC8281" class="xref">RFC8281</a>]</span> and updated
2208 as below:<a href="#section-9-4" class="pilcrow">¶</a></p>
2209 <div id="section-9-5">
2210 <pre class="lang-rbnf sourcecode">
2211 &lt;PCInitiate Message&gt; ::= &lt;Common Header&gt;
2212 &lt;PCE-initiated-lsp-list&gt;
2213
2214 Where:
2215 &lt;PCE-initiated-lsp-list&gt; ::= &lt;PCE-initiated-lsp-request&gt;
2216 [&lt;PCE-initiated-lsp-list&gt;]
2217
2218 &lt;PCE-initiated-lsp-request&gt; ::=
2219 ( &lt;PCE-initiated-lsp-instantiation&gt;|
2220 &lt;PCE-initiated-lsp-deletion&gt; )
2221
2222 &lt;PCE-initiated-lsp-instantiation&gt; ::= &lt;SRP&gt;
2223 &lt;LSP&gt;
2224 [&lt;END-POINTS&gt;]
2225 &lt;ERO&gt;
2226 [&lt;attribute-list&gt;]
2227 [&lt;flowspec-list&gt;]
2228
2229 Where:
2230 &lt;flowspec-list&gt; ::= &lt;FLOWSPEC&gt; [&lt;flowspec-list&gt;]
2231 </pre><a href="#section-9-5" class="pilcrow">¶</a>
2232 </div>
2233 <p id="section-9-6">The PCUpd message is defined in <span>[<a href="#RFC8231" class="xref">RFC8231</a>]</span> and
2234 updated as below:<a href="#section-9-6" class="pilcrow">¶</a></p>
2235 <div id="section-9-7">
2236 <pre class="lang-rbnf sourcecode">
2237 &lt;PCUpd Message&gt; ::= &lt;Common Header&gt;
2238 &lt;update-request-list&gt;
2239
2240 Where:
2241 &lt;update-request-list&gt; ::= &lt;update-request&gt;
2242 [&lt;update-request-list&gt;]
2243
2244 &lt;update-request&gt; ::= &lt;SRP&gt;
2245 &lt;LSP&gt;
2246 &lt;path&gt;
2247 [&lt;flowspec-list&gt;]
2248
2249 Where:
2250 &lt;path&gt;::= &lt;intended-path&gt;&lt;intended-attribute-list&gt;
2251
2252 &lt;flowspec-list&gt; ::= &lt;FLOWSPEC&gt; [&lt;flowspec-list&gt;]
2253 </pre><a href="#section-9-7" class="pilcrow">¶</a>
2254 </div>
2255 <p id="section-9-8">The PCRpt message is defined in <span>[<a href="#RFC8231" class="xref">RFC8231</a>]</span> and
2256 updated as below:<a href="#section-9-8" class="pilcrow">¶</a></p>
2257 <div id="section-9-9">
2258 <pre class="lang-rbnf sourcecode">
2259 &lt;PCRpt Message&gt; ::= &lt;Common Header&gt;
2260 &lt;state-report-list&gt;
2261
2262 Where:
2263 &lt;state-report-list&gt; ::= &lt;state-report&gt;[&lt;state-report-list&gt;]
2264
2265 &lt;state-report&gt; ::= [&lt;SRP&gt;]
2266 &lt;LSP&gt;
2267 &lt;path&gt;
2268 [&lt;flowspec-list&gt;]
2269
2270 Where:
2271 &lt;path&gt;::= &lt;intended-path&gt;
2272 [&lt;actual-attribute-list&gt;&lt;actual-path&gt;]
2273 &lt;intended-attribute-list&gt;
2274
2275 &lt;flowspec-list&gt; ::= &lt;FLOWSPEC&gt; [&lt;flowspec-list&gt;]
2276 </pre><a href="#section-9-9" class="pilcrow">¶</a>
2277 </div>
2278 <p id="section-9-10">The PCReq message is defined in <span>[<a href="#RFC5440" class="xref">RFC5440</a>]</span> and updated in <span>[<a href="#RFC8231" class="xref">RFC8231</a>]</span>;
2279 it is further updated below for a Flow Specification:<a href="#section-9-10" class="pilcrow">¶</a></p>
2280 <div id="section-9-11">
2281 <pre class="lang-rbnf sourcecode">
2282 &lt;PCReq Message&gt;::= &lt;Common Header&gt;
2283 [&lt;svec-list&gt;]
2284 &lt;request-list&gt;
2285
2286 Where:
2287 &lt;svec-list&gt;::= &lt;SVEC&gt;[&lt;svec-list&gt;]
2288
2289 &lt;request-list&gt;::= &lt;request&gt;[&lt;request-list&gt;]
2290
2291 &lt;request&gt;::= &lt;RP&gt;
2292 &lt;END-POINTS&gt;
2293 [&lt;LSP&gt;]
2294 [&lt;LSPA&gt;]
2295 [&lt;BANDWIDTH&gt;]
2296 [&lt;metric-list&gt;]
2297 [&lt;RRO&gt;[&lt;BANDWIDTH&gt;]]
2298 [&lt;IRO&gt;]
2299 [&lt;LOAD-BALANCING&gt;]
2300 [&lt;flowspec-list&gt;]
2301
2302 Where:
2303 &lt;flowspec-list&gt; ::= &lt;FLOWSPEC&gt; [&lt;flowspec-list&gt;]
2304 </pre><a href="#section-9-11" class="pilcrow">¶</a>
2305 </div>
2306 <p id="section-9-12">The PCRep message is defined in <span>[<a href="#RFC5440" class="xref">RFC5440</a>]</span> and updated in
2307 <span>[<a href="#RFC8231" class="xref">RFC8231</a>]</span>; it is further updated below for a Flow
2308 Specification:<a href="#section-9-12" class="pilcrow">¶</a></p>
2309 <div id="section-9-13">
2310 <pre class="lang-rbnf sourcecode">
2311 &lt;PCRep Message&gt; ::= &lt;Common Header&gt;
2312 &lt;response-list&gt;
2313
2314 Where:
2315 &lt;response-list&gt;::=&lt;response&gt;[&lt;response-list&gt;]
2316
2317 &lt;response&gt;::=&lt;RP&gt;
2318 [&lt;LSP&gt;]
2319 [&lt;NO-PATH&gt;]
2320 [&lt;attribute-list&gt;]
2321 [&lt;path-list&gt;]
2322 [&lt;flowspec-list&gt;]
2323
2324 Where:
2325 &lt;flowspec-list&gt; ::= &lt;FLOWSPEC&gt; [&lt;flowspec-list&gt;]
2326 </pre><a href="#section-9-13" class="pilcrow">¶</a>
2327 </div>
2328 </section>
2329 </div>
2330 <section id="section-10">
2331 <h2 id="name-iana-considerations">
2332 <a href="#section-10" class="section-number selfRef">10. </a><a href="#name-iana-considerations" class="section-name selfRef">IANA Considerations</a>
2333 </h2>
2334 <p id="section-10-1">This document requests that IANA allocate code points for the protocol elements
2335 defined in this document.<a href="#section-10-1" class="pilcrow">¶</a></p>
2336 <section id="section-10.1">
2337 <h3 id="name-pcep-objects">
2338 <a href="#section-10.1" class="section-number selfRef">10.1. </a><a href="#name-pcep-objects" class="section-name selfRef">PCEP Objects</a>
2339 </h3>
2340 <p id="section-10.1-1">IANA maintains a subregistry called "PCEP Objects" within the "Path Computation Element Protocol
2341 (PCEP) Numbers" registry. Each PCEP object has an Object-Class and an Object-Type, and IANA has allocated new code points in this subregistry as follows:<a href="#section-10.1-1" class="pilcrow">¶</a></p>
2342 <span id="name-pcep-objects-subregistry-ad"></span><table class="left" id="table-3">
2343 <caption>
2344 <a href="#table-3" class="selfRef">Table 3</a>:
2345 <a href="#name-pcep-objects-subregistry-ad" class="selfRef">PCEP Objects Subregistry Additions</a>
2346 </caption>
2347 <thead>
2348 <tr>
2349 <th class="text-left" rowspan="1" colspan="1">Object-Class Value</th>
2350 <th class="text-left" rowspan="1" colspan="1">Name</th>
2351 <th class="text-left" rowspan="1" colspan="1">Object-Type</th>
2352 <th class="text-left" rowspan="1" colspan="1">Reference</th>
2353 </tr>
2354 </thead>
2355 <tbody>
2356 <tr>
2357 <td class="text-left" rowspan="2" colspan="1">43</td>
2358 <td class="text-left" rowspan="2" colspan="1">FLOWSPEC</td>
2359 <td class="text-left" rowspan="1" colspan="1">0: Reserved</td>
2360 <td class="text-left" rowspan="1" colspan="1">RFC 9168</td>
2361 </tr>
2362 <tr>
2363 <td class="text-left" rowspan="1" colspan="1">1: Flow Specification</td>
2364 <td class="text-left" rowspan="1" colspan="1">RFC 9168</td>
2365 </tr>
2366 </tbody>
2367 </table>
2368 <section id="section-10.1.1">
2369 <h4 id="name-pcep-flowspec-object-flag-f">
2370 <a href="#section-10.1.1" class="section-number selfRef">10.1.1. </a><a href="#name-pcep-flowspec-object-flag-f" class="section-name selfRef">PCEP FLOWSPEC Object Flag Field</a>
2371 </h4>
2372 <p id="section-10.1.1-1">This document requests that a new subregistry, "FLOWSPEC Object
2373 Flag Field", be created within the "Path Computation Element Protocol
2374 (PCEP) Numbers" registry to manage the Flag field of the FLOWSPEC
2375 object. New values are to be assigned by Standards Action <span>[<a href="#RFC8126" class="xref">RFC8126</a>]</span>.
2376 Each bit should be tracked with the following qualities:<a href="#section-10.1.1-1" class="pilcrow">¶</a></p>
2377 <ul class="normal">
2378 <li class="normal" id="section-10.1.1-2.1">Bit number (counting from bit 0 as the most significant bit)<a href="#section-10.1.1-2.1" class="pilcrow">¶</a>
2379 </li>
2380 <li class="normal" id="section-10.1.1-2.2">Capability description<a href="#section-10.1.1-2.2" class="pilcrow">¶</a>
2381 </li>
2382 <li class="normal" id="section-10.1.1-2.3">Defining RFC<a href="#section-10.1.1-2.3" class="pilcrow">¶</a>
2383 </li>
2384 </ul>
2385 <p id="section-10.1.1-3">The initial population of this registry is as follows:<a href="#section-10.1.1-3" class="pilcrow">¶</a></p>
2386 <span id="name-initial-contents-of-the-flo"></span><table class="left" id="table-4">
2387 <caption>
2388 <a href="#table-4" class="selfRef">Table 4</a>:
2389 <a href="#name-initial-contents-of-the-flo" class="selfRef">Initial Contents of the FLOWSPEC Object Flag Field Registry</a>
2390 </caption>
2391 <thead>
2392 <tr>
2393 <th class="text-left" rowspan="1" colspan="1">Bit</th>
2394 <th class="text-left" rowspan="1" colspan="1">Description</th>
2395 <th class="text-left" rowspan="1" colspan="1">Reference</th>
2396 </tr>
2397 </thead>
2398 <tbody>
2399 <tr>
2400 <td class="text-left" rowspan="1" colspan="1">0-5</td>
2401 <td class="text-left" rowspan="1" colspan="1">Unassigned</td>
2402 <td class="text-left" rowspan="1" colspan="1"></td>
2403 </tr>
2404 <tr>
2405 <td class="text-left" rowspan="1" colspan="1">6</td>
2406 <td class="text-left" rowspan="1" colspan="1">LPM (L bit)</td>
2407 <td class="text-left" rowspan="1" colspan="1">RFC 9168</td>
2408 </tr>
2409 <tr>
2410 <td class="text-left" rowspan="1" colspan="1">7</td>
2411 <td class="text-left" rowspan="1" colspan="1"> Remove (R bit)</td>
2412 <td class="text-left" rowspan="1" colspan="1">RFC 9168</td>
2413 </tr>
2414 </tbody>
2415 </table>
2416 </section>
2417 </section>
2418 <section id="section-10.2">
2419 <h3 id="name-pcep-tlv-type-indicators">
2420 <a href="#section-10.2" class="section-number selfRef">10.2. </a><a href="#name-pcep-tlv-type-indicators" class="section-name selfRef">PCEP TLV Type Indicators</a>
2421 </h3>
2422 <p id="section-10.2-1">IANA maintains a subregistry called "PCEP TLV Type Indicators" within the "Path Computation Element Protocol (PCEP) Numbers" registry. IANA has made the following allocations in this subregistry:<a href="#section-10.2-1" class="pilcrow">¶</a></p>
2423 <span id="name-pcep-tlv-type-indicators-su"></span><table class="left" id="table-5">
2424 <caption>
2425 <a href="#table-5" class="selfRef">Table 5</a>:
2426 <a href="#name-pcep-tlv-type-indicators-su" class="selfRef">PCEP TLV Type Indicators Subregistry Additions</a>
2427 </caption>
2428 <thead>
2429 <tr>
2430 <th class="text-left" rowspan="1" colspan="1">Value</th>
2431 <th class="text-left" rowspan="1" colspan="1">Description</th>
2432 <th class="text-left" rowspan="1" colspan="1"> Reference</th>
2433 </tr>
2434 </thead>
2435 <tbody>
2436 <tr>
2437 <td class="text-left" rowspan="1" colspan="1">51</td>
2438 <td class="text-left" rowspan="1" colspan="1">PCE-FLOWSPEC-CAPABILITY TLV</td>
2439 <td class="text-left" rowspan="1" colspan="1">RFC 9168</td>
2440 </tr>
2441 <tr>
2442 <td class="text-left" rowspan="1" colspan="1">52</td>
2443 <td class="text-left" rowspan="1" colspan="1">FLOW FILTER TLV</td>
2444 <td class="text-left" rowspan="1" colspan="1">RFC 9168</td>
2445 </tr>
2446 </tbody>
2447 </table>
2448 </section>
2449 <div id="iana">
2450 <section id="section-10.3">
2451 <h3 id="name-flow-specification-tlv-type-">
2452 <a href="#section-10.3" class="section-number selfRef">10.3. </a><a href="#name-flow-specification-tlv-type-" class="section-name selfRef">Flow Specification TLV Type Indicators</a>
2453 </h3>
2454 <p id="section-10.3-1">IANA has created a new subregistry called "PCEP Flow Specification TLV Type Indicators" within the "Path Computation Element Protocol (PCEP) Numbers" registry.<a href="#section-10.3-1" class="pilcrow">¶</a></p>
2455 <p id="section-10.3-2">Allocations from this registry are to be made according to the following assignment policies <span>[<a href="#RFC8126" class="xref">RFC8126</a>]</span>:<a href="#section-10.3-2" class="pilcrow">¶</a></p>
2456 <span id="name-registration-procedures-for"></span><table class="left" id="table-6">
2457 <caption>
2458 <a href="#table-6" class="selfRef">Table 6</a>:
2459 <a href="#name-registration-procedures-for" class="selfRef">Registration Procedures for the PCEP Flow Specification TLV Type Indicators Subregistry</a>
2460 </caption>
2461 <thead>
2462 <tr>
2463 <th class="text-left" rowspan="1" colspan="1">Range</th>
2464 <th class="text-left" rowspan="1" colspan="1">Registration Procedures</th>
2465 </tr>
2466 </thead>
2467 <tbody>
2468 <tr>
2469 <td class="text-left" rowspan="1" colspan="1">0-255</td>
2470 <td class="text-left" rowspan="1" colspan="1">
2471 <p id="section-10.3-3.2.1.2.1">Reserved - must not be allocated.<a href="#section-10.3-3.2.1.2.1" class="pilcrow">¶</a></p>
2472 <p id="section-10.3-3.2.1.2.2">Usage mirrors the BGP Flow Spec registry
2473 <span>[<a href="#RFC8955" class="xref">RFC8955</a>]</span> <span>[<a href="#RFC8956" class="xref">RFC8956</a>]</span>.<a href="#section-10.3-3.2.1.2.2" class="pilcrow">¶</a></p>
2474 </td>
2475 </tr>
2476 <tr>
2477 <td class="text-left" rowspan="1" colspan="1">256-64506</td>
2478 <td class="text-left" rowspan="1" colspan="1">Specification Required</td>
2479 </tr>
2480 <tr>
2481 <td class="text-left" rowspan="1" colspan="1">64507-65531</td>
2482 <td class="text-left" rowspan="1" colspan="1">First Come First Served</td>
2483 </tr>
2484 <tr>
2485 <td class="text-left" rowspan="1" colspan="1">65532-65535</td>
2486 <td class="text-left" rowspan="1" colspan="1">Experimental Use</td>
2487 </tr>
2488 </tbody>
2489 </table>
2490 <p id="section-10.3-4">IANA has populated this registry with values defined in this
2491 document as follows, taking the new values from the range 256 to 64506:<a href="#section-10.3-4" class="pilcrow">¶</a></p>
2492 <span id="name-initial-contents-of-the-pce"></span><table class="left" id="table-7">
2493 <caption>
2494 <a href="#table-7" class="selfRef">Table 7</a>:
2495 <a href="#name-initial-contents-of-the-pce" class="selfRef">Initial Contents of the PCEP Flow Specification TLV Type Indicators Subregistry</a>
2496 </caption>
2497 <thead>
2498 <tr>
2499 <th class="text-left" rowspan="1" colspan="1">Value</th>
2500 <th class="text-left" rowspan="1" colspan="1">Meaning</th>
2501 </tr>
2502 </thead>
2503 <tbody>
2504 <tr>
2505 <td class="text-left" rowspan="1" colspan="1">256</td>
2506 <td class="text-left" rowspan="1" colspan="1">Route Distinguisher</td>
2507 </tr>
2508 <tr>
2509 <td class="text-left" rowspan="1" colspan="1">257</td>
2510 <td class="text-left" rowspan="1" colspan="1"> IPv4 Multicast</td>
2511 </tr>
2512 <tr>
2513 <td class="text-left" rowspan="1" colspan="1">258</td>
2514 <td class="text-left" rowspan="1" colspan="1">IPv6 Multicast</td>
2515 </tr>
2516 </tbody>
2517 </table>
2518 </section>
2519 </div>
2520 <section id="section-10.4">
2521 <h3 id="name-pcep-error-codes">
2522 <a href="#section-10.4" class="section-number selfRef">10.4. </a><a href="#name-pcep-error-codes" class="section-name selfRef">PCEP Error Codes</a>
2523 </h3>
2524 <p id="section-10.4-1">IANA maintains a subregistry called "PCEP-ERROR Object Error Types and Values" within the "Path Computation Element Protocol (PCEP) Numbers" registry. Entries
2525 in this subregistry are described by Error-Type and Error-value. IANA has added the following assignment to this subregistry:<a href="#section-10.4-1" class="pilcrow">¶</a></p>
2526 <span id="name-pcep-error-object-error-typ"></span><table class="left" id="table-8">
2527 <caption>
2528 <a href="#table-8" class="selfRef">Table 8</a>:
2529 <a href="#name-pcep-error-object-error-typ" class="selfRef">PCEP-ERROR Object Error Types and Values Subregistry Additions</a>
2530 </caption>
2531 <thead>
2532 <tr>
2533 <th class="text-left" rowspan="1" colspan="1">Error-Type</th>
2534 <th class="text-left" rowspan="1" colspan="1">Meaning</th>
2535 <th class="text-left" rowspan="1" colspan="1">Error-value</th>
2536 <th class="text-left" rowspan="1" colspan="1">Reference</th>
2537 </tr>
2538 </thead>
2539 <tbody>
2540 <tr>
2541 <td class="text-left" rowspan="7" colspan="1">30</td>
2542 <td class="text-left" rowspan="7" colspan="1">FlowSpec error</td>
2543 <td class="text-left" rowspan="1" colspan="1">0: Unassigned</td>
2544 <td class="text-left" rowspan="1" colspan="1">RFC 9168</td>
2545 </tr>
2546 <tr>
2547 <td class="text-left" rowspan="1" colspan="1">1: Unsupported FlowSpec</td>
2548 <td class="text-left" rowspan="1" colspan="1">RFC 9168</td>
2549 </tr>
2550 <tr>
2551 <td class="text-left" rowspan="1" colspan="1">2: Malformed FlowSpec</td>
2552 <td class="text-left" rowspan="1" colspan="1">RFC 9168</td>
2553 </tr>
2554 <tr>
2555 <td class="text-left" rowspan="1" colspan="1">3: Unresolvable Conflict</td>
2556 <td class="text-left" rowspan="1" colspan="1">RFC 9168</td>
2557 </tr>
2558 <tr>
2559 <td class="text-left" rowspan="1" colspan="1">4: Unknown FlowSpec</td>
2560 <td class="text-left" rowspan="1" colspan="1">RFC 9168</td>
2561 </tr>
2562 <tr>
2563 <td class="text-left" rowspan="1" colspan="1">5: Unsupported LPM Route</td>
2564 <td class="text-left" rowspan="1" colspan="1">RFC 9168</td>
2565 </tr>
2566 <tr>
2567 <td class="text-left" rowspan="1" colspan="1">6-255: Unassigned</td>
2568 <td class="text-left" rowspan="1" colspan="1">RFC 9168</td>
2569 </tr>
2570 </tbody>
2571 </table>
2572 </section>
2573 <section id="section-10.5">
2574 <h3 id="name-pce-capability-flag">
2575 <a href="#section-10.5" class="section-number selfRef">10.5. </a><a href="#name-pce-capability-flag" class="section-name selfRef">PCE Capability Flag</a>
2576 </h3>
2577 <p id="section-10.5-1">IANA has registered a new capability bit in the OSPF Parameters "Path Computation Element (PCE) Capability Flags" registry as follows:<a href="#section-10.5-1" class="pilcrow">¶</a></p>
2578 <span id="name-path-computation-element-pc"></span><table class="left" id="table-9">
2579 <caption>
2580 <a href="#table-9" class="selfRef">Table 9</a>:
2581 <a href="#name-path-computation-element-pc" class="selfRef">Path Computation Element (PCE) Capability Flags Registry Additions</a>
2582 </caption>
2583 <thead>
2584 <tr>
2585 <th class="text-left" rowspan="1" colspan="1">Bit</th>
2586 <th class="text-left" rowspan="1" colspan="1">Capability Description</th>
2587 <th class="text-left" rowspan="1" colspan="1">Reference</th>
2588 </tr>
2589 </thead>
2590 <tbody>
2591 <tr>
2592 <td class="text-left" rowspan="1" colspan="1">16</td>
2593 <td class="text-left" rowspan="1" colspan="1">FlowSpec</td>
2594 <td class="text-left" rowspan="1" colspan="1">RFC 9168</td>
2595 </tr>
2596 </tbody>
2597 </table>
2598 </section>
2599 </section>
2600 <div id="Security">
2601 <section id="section-11">
2602 <h2 id="name-security-considerations">
2603 <a href="#section-11" class="section-number selfRef">11. </a><a href="#name-security-considerations" class="section-name selfRef">Security Considerations</a>
2604 </h2>
2605 <p id="section-11-1">We may assume that a system that utilizes a remote PCE is subject to a number of
2606 vulnerabilities that could allow spurious LSPs or SR paths to be established or that
2607 could result in existing paths being modified or torn down. Such systems, therefore,
2608 apply security considerations as described in <span>[<a href="#RFC5440" class="xref">RFC5440</a>]</span>,
2609 <span><a href="https://www.rfc-editor.org/rfc/rfc6952#section-2.5" class="relref">Section 2.5</a> of [<a href="#RFC6952" class="xref">RFC6952</a>]</span>, <span>[<a href="#RFC8253" class="xref">RFC8253</a>]</span>, and
2610 <span>[<a href="#RFC8955" class="xref">RFC8955</a>]</span>.<a href="#section-11-1" class="pilcrow">¶</a></p>
2611 <p id="section-11-2">The description of Flow Specifications associated with paths set up or controlled by a
2612 PCE adds a further detail that could be attacked without tearing down LSPs or SR paths
2613 but causes traffic to be misrouted within the network. Therefore, the use of the security
2614 mechanisms for PCEP referenced above is important.<a href="#section-11-2" class="pilcrow">¶</a></p>
2615 <p id="section-11-3">Visibility into the information carried in PCEP does not have direct privacy concerns for
2616 end users' data; however, knowledge of how data is routed in a network may make that
2617 data more vulnerable. Of course, the ability to interfere with the way data is routed also
2618 makes the data more vulnerable. Furthermore, knowledge of the connected endpoints (such as
2619 multicast receivers or VPN sites) is usually considered private customer information. Therefore,
2620 implementations or deployments concerned with protecting privacy <span class="bcp14">MUST</span> apply the mechanisms described
2621 in the documents referenced above, in particular, to secure the PCEP session using IPsec per Sections
2622 <a href="https://www.rfc-editor.org/rfc/rfc5440#section-10.4" class="relref">10.4</a> to <a href="https://www.rfc-editor.org/rfc/rfc5440#section-10.6" class="relref">10.6</a> of <span>[<a href="#RFC5440" class="xref">RFC5440</a>]</span> or TLS per <span>[<a href="#RFC8253" class="xref">RFC8253</a>]</span>. Note that TCP-MD5
2623 security as originally suggested in <span>[<a href="#RFC5440" class="xref">RFC5440</a>]</span> does not provide sufficient security
2624 or privacy guarantees and <span class="bcp14">SHOULD NOT</span> be relied upon.<a href="#section-11-3" class="pilcrow">¶</a></p>
2625 <p id="section-11-4">Experience with Flow Specifications in BGP systems indicates that they can become complex and
2626 that the overlap of Flow Specifications installed in different orders can lead to unexpected
2627 results. Although this is not directly a security issue per se, the confusion and unexpected
2628 forwarding behavior may be engineered or exploited by an attacker. Furthermore, this complexity
2629 might give rise to a situation where the forwarding behaviors might create gaps in the monitoring
2630 and inspection of particular traffic or provide a path that avoids expected mitigations. Therefore,
2631 implementers and operators <span class="bcp14">SHOULD</span> pay careful attention to the manageability considerations described
2632 in <a href="#Manage" class="xref">Section 12</a> and familiarize themselves with the careful explanations in
2633 <span>[<a href="#RFC8955" class="xref">RFC8955</a>]</span>.<a href="#section-11-4" class="pilcrow">¶</a></p>
2634 </section>
2635 </div>
2636 <div id="Manage">
2637 <section id="section-12">
2638 <h2 id="name-manageability-consideration">
2639 <a href="#section-12" class="section-number selfRef">12. </a><a href="#name-manageability-consideration" class="section-name selfRef">Manageability Considerations</a>
2640 </h2>
2641 <p id="section-12-1">The feature introduced by this document enables operational manageability of networks operated in
2642 conjunction with a PCE and using PCEP. In the case of a stateful active
2643 PCE or with PCE-initiated services, in the absence of this feature, additional manual configuration is needed to tell the head ends
2644 what traffic to place on the network services (LSPs, SR paths, etc.).<a href="#section-12-1" class="pilcrow">¶</a></p>
2645 <p id="section-12-2">This section follows the advice and guidance of <span>[<a href="#RFC6123" class="xref">RFC6123</a>]</span>.<a href="#section-12-2" class="pilcrow">¶</a></p>
2646 <div id="mg-mxfspec">
2647 <section id="section-12.1">
2648 <h3 id="name-management-of-multiple-flow">
2649 <a href="#section-12.1" class="section-number selfRef">12.1. </a><a href="#name-management-of-multiple-flow" class="section-name selfRef">Management of Multiple Flow Specifications</a>
2650 </h3>
2651 <p id="section-12.1-1">Experience with Flow Specification in BGP suggests that there can be a lot of complexity when
2652 two or more Flow Specifications overlap. This can arise, for example, with addresses indicated
2653 using prefixes and could cause confusion about what traffic should be placed on which path. Unlike
2654 the behavior in a distributed routing system, it is not important to the routing stability and consistency
2655 of the network that each head-end implementation applies the same rules to disambiguate overlapping Flow
2656 Specifications, but it is important that:<a href="#section-12.1-1" class="pilcrow">¶</a></p>
2657 <ul class="normal">
2658 <li class="normal" id="section-12.1-2.1">a network operator can easily find out what traffic is being placed on which path and why. This
2659 will facilitate analysis of the network and diagnosis of faults.<a href="#section-12.1-2.1" class="pilcrow">¶</a>
2660 </li>
2661 <li class="normal" id="section-12.1-2.2">a PCE be able to correctly predict the effect of instructions it gives to a PCC. This will
2662 ensure that traffic is correctly placed on the network without causing congestion or other
2663 network inefficiencies and that traffic is correctly delivered.<a href="#section-12.1-2.2" class="pilcrow">¶</a>
2664 </li>
2665 </ul>
2666 <p id="section-12.1-3">To that end, a PCC <span class="bcp14">MUST</span> enable an operator to view the Flow Specifications that it has installed,
2667 and these <span class="bcp14">MUST</span> be presented in order of precedence such that when two Flow Specifications overlap,
2668 the one that will be serviced with higher precedence is presented to the operator first.<a href="#section-12.1-3" class="pilcrow">¶</a></p>
2669 <p id="section-12.1-4">A discussion of precedence ordering for Flow Specifications is found in <a href="#priorities" class="xref">Section 8.7</a>.<a href="#section-12.1-4" class="pilcrow">¶</a></p>
2670 </section>
2671 </div>
2672 <div id="mg-control">
2673 <section id="section-12.2">
2674 <h3 id="name-control-of-function-through">
2675 <a href="#section-12.2" class="section-number selfRef">12.2. </a><a href="#name-control-of-function-through" class="section-name selfRef">Control of Function through Configuration and Policy</a>
2676 </h3>
2677 <p id="section-12.2-1">Support for the function described in this document implies that a functional element that
2678 is capable of requesting that a PCE compute and control a path is also able to configure the
2679 specification of what traffic should be placed on that path. Where there is a human involved
2680 in this action, configuration of the Flow Specification must be available through an interface
2681 (such as a graphical user interface or a Command Line Interface). Where a distinct software
2682 component (i.e., one not co-implemented with the PCE) is used, a protocol mechanism will be
2683 required that could be PCEP itself or a data model, such as extensions to the YANG
2684 model for requesting path computation <span>[<a href="#I-D.ietf-teas-yang-path-computation" class="xref">TEAS-YANG-PATH</a>]</span>.<a href="#section-12.2-1" class="pilcrow">¶</a></p>
2685 <p id="section-12.2-2">Implementations <span class="bcp14">MAY</span> be constructed with a configurable switch to indicate whether they support
2686 the functions defined in this document. Otherwise, such implementations <span class="bcp14">MUST</span> indicate
2687 that they support the function as described in <a href="#cap" class="xref">Section 4</a>. If an implementation
2688 allows configurable support of this function, that support <span class="bcp14">MAY</span> be configurable per peer or
2689 once for the whole implementation.<a href="#section-12.2-2" class="pilcrow">¶</a></p>
2690 <p id="section-12.2-3">As mentioned in <a href="#mg-mxfspec" class="xref">Section 12.1</a>, a PCE implementation <span class="bcp14">SHOULD</span> provide a mechanism
2691 to configure variations in the precedence ordering of Flow Specifications per PCC.<a href="#section-12.2-3" class="pilcrow">¶</a></p>
2692 </section>
2693 </div>
2694 <div id="mg-model">
2695 <section id="section-12.3">
2696 <h3 id="name-information-and-data-models">
2697 <a href="#section-12.3" class="section-number selfRef">12.3. </a><a href="#name-information-and-data-models" class="section-name selfRef">Information and Data Models</a>
2698 </h3>
2699 <p id="section-12.3-1">The YANG model in <span>[<a href="#I-D.ietf-pce-pcep-yang" class="xref">PCE-PCEP-YANG</a>]</span> can be used to model and monitor
2700 PCEP states and messages. To make that YANG model useful for the extensions described in
2701 this document, it would need to be augmented to cover the new protocol elements.<a href="#section-12.3-1" class="pilcrow">¶</a></p>
2702 <p id="section-12.3-2">Similarly, as noted in <a href="#mg-control" class="xref">Section 12.2</a>, the YANG model defined in
2703 <span>[<a href="#I-D.ietf-teas-yang-path-computation" class="xref">TEAS-YANG-PATH</a>]</span> could be extended to allow the specification
2704 of Flow Specifications.<a href="#section-12.3-2" class="pilcrow">¶</a></p>
2705 <p id="section-12.3-3">Finally, as mentioned in <a href="#mg-mxfspec" class="xref">Section 12.1</a>, a PCC implementation <span class="bcp14">SHOULD</span> provide
2706 a mechanism to allow an operator to read the Flow Specifications from a PCC and to
2707 understand in what order they will be executed. This could be achieved using a new YANG
2708 model.<a href="#section-12.3-3" class="pilcrow">¶</a></p>
2709 </section>
2710 </div>
2711 <div id="mg-monitor">
2712 <section id="section-12.4">
2713 <h3 id="name-liveness-detection-and-moni">
2714 <a href="#section-12.4" class="section-number selfRef">12.4. </a><a href="#name-liveness-detection-and-moni" class="section-name selfRef">Liveness Detection and Monitoring</a>
2715 </h3>
2716 <p id="section-12.4-1">The extensions defined in this document do not require any additional liveness detection
2717 and monitoring support. See <span>[<a href="#RFC5440" class="xref">RFC5440</a>]</span> and <span>[<a href="#RFC5886" class="xref">RFC5886</a>]</span> for
2718 more information.<a href="#section-12.4-1" class="pilcrow">¶</a></p>
2719 </section>
2720 </div>
2721 <div id="mg-verify">
2722 <section id="section-12.5">
2723 <h3 id="name-verifying-correct-operation">
2724 <a href="#section-12.5" class="section-number selfRef">12.5. </a><a href="#name-verifying-correct-operation" class="section-name selfRef">Verifying Correct Operation</a>
2725 </h3>
2726 <p id="section-12.5-1">The chief element of operation that needs to be verified (in addition to the operation
2727 of the protocol elements as described in <span>[<a href="#RFC5440" class="xref">RFC5440</a>]</span>) is the installation,
2728 precedence, and correct operation of the Flow Specifications at a PCC.<a href="#section-12.5-1" class="pilcrow">¶</a></p>
2729 <p id="section-12.5-2">In addition to the YANG model, for reading Flow Specifications described in <a href="#mg-model" class="xref">Section 12.3</a>,
2730 tools may be needed to inject Operations and Management (OAM) traffic at the PCC that matches
2731 specific criteria so that it can be monitored while traveling along the desired path. Such tools are
2732 outside the scope of this document.<a href="#section-12.5-2" class="pilcrow">¶</a></p>
2733 </section>
2734 </div>
2735 <div id="mg-reqs">
2736 <section id="section-12.6">
2737 <h3 id="name-requirements-for-other-prot">
2738 <a href="#section-12.6" class="section-number selfRef">12.6. </a><a href="#name-requirements-for-other-prot" class="section-name selfRef">Requirements for Other Protocols and Functional Components</a>
2739 </h3>
2740 <p id="section-12.6-1">This document places no requirements on other protocols or components.<a href="#section-12.6-1" class="pilcrow">¶</a></p>
2741 </section>
2742 </div>
2743 <div id="mg-impact">
2744 <section id="section-12.7">
2745 <h3 id="name-impact-on-network-operation">
2746 <a href="#section-12.7" class="section-number selfRef">12.7. </a><a href="#name-impact-on-network-operation" class="section-name selfRef">Impact on Network Operation</a>
2747 </h3>
2748 <p id="section-12.7-1">The use of the features described in this document clearly have an important impact
2749 on network traffic since they cause traffic to be routed on specific paths in the
2750 network. However, in practice, these changes make no direct changes to the network
2751 operation because traffic is already placed on those paths using some pre-existing
2752 configuration mechanism. Thus, the significant change is the reduction in mechanisms
2753 that have to be applied rather than a change to how the traffic is passed through
2754 the network.<a href="#section-12.7-1" class="pilcrow">¶</a></p>
2755 </section>
2756 </div>
2757 </section>
2758 </div>
2759 <section id="section-13">
2760 <h2 id="name-references">
2761 <a href="#section-13" class="section-number selfRef">13. </a><a href="#name-references" class="section-name selfRef">References</a>
2762 </h2>
2763 <section id="section-13.1">
2764 <h3 id="name-normative-references">
2765 <a href="#section-13.1" class="section-number selfRef">13.1. </a><a href="#name-normative-references" class="section-name selfRef">Normative References</a>
2766 </h3>
2767 <dl class="references">
2768 <dt id="RFC2119">[RFC2119]</dt>
2769 <dd>
2770 <span class="refAuthor">Bradner, S.</span>, <span class="refTitle">"Key words for use in RFCs to Indicate Requirement Levels"</span>, <span class="seriesInfo">BCP 14</span>, <span class="seriesInfo">RFC 2119</span>, <span class="seriesInfo">DOI 10.17487/RFC2119</span>, <time datetime="1997-03" class="refDate">March 1997</time>, <span>&lt;<a href="https://www.rfc-editor.org/info/rfc2119">https://www.rfc-editor.org/info/rfc2119</a>&gt;</span>. </dd>
2771 <dd class="break"></dd>
2772 <dt id="RFC4364">[RFC4364]</dt>
2773 <dd>
2774 <span class="refAuthor">Rosen, E.</span> and <span class="refAuthor">Y. Rekhter</span>, <span class="refTitle">"BGP/MPLS IP Virtual Private Networks (VPNs)"</span>, <span class="seriesInfo">RFC 4364</span>, <span class="seriesInfo">DOI 10.17487/RFC4364</span>, <time datetime="2006-02" class="refDate">February 2006</time>, <span>&lt;<a href="https://www.rfc-editor.org/info/rfc4364">https://www.rfc-editor.org/info/rfc4364</a>&gt;</span>. </dd>
2775 <dd class="break"></dd>
2776 <dt id="RFC4760">[RFC4760]</dt>
2777 <dd>
2778 <span class="refAuthor">Bates, T.</span>, <span class="refAuthor">Chandra, R.</span>, <span class="refAuthor">Katz, D.</span>, and <span class="refAuthor">Y. Rekhter</span>, <span class="refTitle">"Multiprotocol Extensions for BGP-4"</span>, <span class="seriesInfo">RFC 4760</span>, <span class="seriesInfo">DOI 10.17487/RFC4760</span>, <time datetime="2007-01" class="refDate">January 2007</time>, <span>&lt;<a href="https://www.rfc-editor.org/info/rfc4760">https://www.rfc-editor.org/info/rfc4760</a>&gt;</span>. </dd>
2779 <dd class="break"></dd>
2780 <dt id="RFC5440">[RFC5440]</dt>
2781 <dd>
2782 <span class="refAuthor">Vasseur, JP., Ed.</span> and <span class="refAuthor">JL. Le Roux, Ed.</span>, <span class="refTitle">"Path Computation Element (PCE) Communication Protocol (PCEP)"</span>, <span class="seriesInfo">RFC 5440</span>, <span class="seriesInfo">DOI 10.17487/RFC5440</span>, <time datetime="2009-03" class="refDate">March 2009</time>, <span>&lt;<a href="https://www.rfc-editor.org/info/rfc5440">https://www.rfc-editor.org/info/rfc5440</a>&gt;</span>. </dd>
2783 <dd class="break"></dd>
2784 <dt id="RFC5511">[RFC5511]</dt>
2785 <dd>
2786 <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>
2787 <dd class="break"></dd>
2788 <dt id="RFC8174">[RFC8174]</dt>
2789 <dd>
2790 <span class="refAuthor">Leiba, B.</span>, <span class="refTitle">"Ambiguity of Uppercase vs Lowercase in RFC 2119 Key Words"</span>, <span class="seriesInfo">BCP 14</span>, <span class="seriesInfo">RFC 8174</span>, <span class="seriesInfo">DOI 10.17487/RFC8174</span>, <time datetime="2017-05" class="refDate">May 2017</time>, <span>&lt;<a href="https://www.rfc-editor.org/info/rfc8174">https://www.rfc-editor.org/info/rfc8174</a>&gt;</span>. </dd>
2791 <dd class="break"></dd>
2792 <dt id="RFC8231">[RFC8231]</dt>
2793 <dd>
2794 <span class="refAuthor">Crabbe, E.</span>, <span class="refAuthor">Minei, I.</span>, <span class="refAuthor">Medved, J.</span>, and <span class="refAuthor">R. Varga</span>, <span class="refTitle">"Path Computation Element Communication Protocol (PCEP) Extensions for Stateful PCE"</span>, <span class="seriesInfo">RFC 8231</span>, <span class="seriesInfo">DOI 10.17487/RFC8231</span>, <time datetime="2017-09" class="refDate">September 2017</time>, <span>&lt;<a href="https://www.rfc-editor.org/info/rfc8231">https://www.rfc-editor.org/info/rfc8231</a>&gt;</span>. </dd>
2795 <dd class="break"></dd>
2796 <dt id="RFC8232">[RFC8232]</dt>
2797 <dd>
2798 <span class="refAuthor">Crabbe, E.</span>, <span class="refAuthor">Minei, I.</span>, <span class="refAuthor">Medved, J.</span>, <span class="refAuthor">Varga, R.</span>, <span class="refAuthor">Zhang, X.</span>, and <span class="refAuthor">D. Dhody</span>, <span class="refTitle">"Optimizations of Label Switched Path State Synchronization Procedures for a Stateful PCE"</span>, <span class="seriesInfo">RFC 8232</span>, <span class="seriesInfo">DOI 10.17487/RFC8232</span>, <time datetime="2017-09" class="refDate">September 2017</time>, <span>&lt;<a href="https://www.rfc-editor.org/info/rfc8232">https://www.rfc-editor.org/info/rfc8232</a>&gt;</span>. </dd>
2799 <dd class="break"></dd>
2800 <dt id="RFC8253">[RFC8253]</dt>
2801 <dd>
2802 <span class="refAuthor">Lopez, D.</span>, <span class="refAuthor">Gonzalez de Dios, O.</span>, <span class="refAuthor">Wu, Q.</span>, and <span class="refAuthor">D. Dhody</span>, <span class="refTitle">"PCEPS: Usage of TLS to Provide a Secure Transport for the Path Computation Element Communication Protocol (PCEP)"</span>, <span class="seriesInfo">RFC 8253</span>, <span class="seriesInfo">DOI 10.17487/RFC8253</span>, <time datetime="2017-10" class="refDate">October 2017</time>, <span>&lt;<a href="https://www.rfc-editor.org/info/rfc8253">https://www.rfc-editor.org/info/rfc8253</a>&gt;</span>. </dd>
2803 <dd class="break"></dd>
2804 <dt id="RFC8281">[RFC8281]</dt>
2805 <dd>
2806 <span class="refAuthor">Crabbe, E.</span>, <span class="refAuthor">Minei, I.</span>, <span class="refAuthor">Sivabalan, S.</span>, and <span class="refAuthor">R. Varga</span>, <span class="refTitle">"Path Computation Element Communication Protocol (PCEP) Extensions for PCE-Initiated LSP Setup in a Stateful PCE Model"</span>, <span class="seriesInfo">RFC 8281</span>, <span class="seriesInfo">DOI 10.17487/RFC8281</span>, <time datetime="2017-12" class="refDate">December 2017</time>, <span>&lt;<a href="https://www.rfc-editor.org/info/rfc8281">https://www.rfc-editor.org/info/rfc8281</a>&gt;</span>. </dd>
2807 <dd class="break"></dd>
2808 <dt id="RFC8955">[RFC8955]</dt>
2809 <dd>
2810 <span class="refAuthor">Loibl, C.</span>, <span class="refAuthor">Hares, S.</span>, <span class="refAuthor">Raszuk, R.</span>, <span class="refAuthor">McPherson, D.</span>, and <span class="refAuthor">M. Bacher</span>, <span class="refTitle">"Dissemination of Flow Specification Rules"</span>, <span class="seriesInfo">RFC 8955</span>, <span class="seriesInfo">DOI 10.17487/RFC8955</span>, <time datetime="2020-12" class="refDate">December 2020</time>, <span>&lt;<a href="https://www.rfc-editor.org/info/rfc8955">https://www.rfc-editor.org/info/rfc8955</a>&gt;</span>. </dd>
2811 <dd class="break"></dd>
2812 <dt id="RFC8956">[RFC8956]</dt>
2813 <dd>
2814 <span class="refAuthor">Loibl, C., Ed.</span>, <span class="refAuthor">Raszuk, R., Ed.</span>, and <span class="refAuthor">S. Hares, Ed.</span>, <span class="refTitle">"Dissemination of Flow Specification Rules for IPv6"</span>, <span class="seriesInfo">RFC 8956</span>, <span class="seriesInfo">DOI 10.17487/RFC8956</span>, <time datetime="2020-12" class="refDate">December 2020</time>, <span>&lt;<a href="https://www.rfc-editor.org/info/rfc8956">https://www.rfc-editor.org/info/rfc8956</a>&gt;</span>. </dd>
2815 <dd class="break"></dd>
2816 </dl>
2817 </section>
2818 <section id="section-13.2">
2819 <h3 id="name-informative-references">
2820 <a href="#section-13.2" class="section-number selfRef">13.2. </a><a href="#name-informative-references" class="section-name selfRef">Informative References</a>
2821 </h3>
2822 <dl class="references">
2823 <dt id="I-D.ietf-idr-flowspec-l2vpn">[BGP-L2VPN]</dt>
2824 <dd>
2825 <span class="refAuthor">Hao, W.</span>, <span class="refAuthor">Eastlake, D. E.</span>, <span class="refAuthor">Litkowski, S.</span>, and <span class="refAuthor">S. Zhuang</span>, <span class="refTitle">"BGP Dissemination of L2 Flow Specification Rules"</span>, <span class="refContent">Work in Progress</span>, <span class="seriesInfo">Internet-Draft, draft-ietf-idr-flowspec-l2vpn-18</span>, <time datetime="2021-10-24" class="refDate">24 October 2021</time>, <span>&lt;<a href="https://datatracker.ietf.org/doc/html/draft-ietf-idr-flowspec-l2vpn-18">https://datatracker.ietf.org/doc/html/draft-ietf-idr-flowspec-l2vpn-18</a>&gt;</span>. </dd>
2826 <dd class="break"></dd>
2827 <dt id="I-D.gont-numeric-ids-sec-considerations">[NUMERIC-IDS-SEC]</dt>
2828 <dd>
2829 <span class="refAuthor">Gont, F.</span> and <span class="refAuthor">I. Arce</span>, <span class="refTitle">"Security Considerations for Transient Numeric Identifiers Employed in Network Protocols"</span>, <span class="refContent">Work in Progress</span>, <span class="seriesInfo">Internet-Draft, draft-gont-numeric-ids-sec-considerations-06</span>, <time datetime="2020-12-05" class="refDate">5 December 2020</time>, <span>&lt;<a href="https://datatracker.ietf.org/doc/html/draft-gont-numeric-ids-sec-considerations-06">https://datatracker.ietf.org/doc/html/draft-gont-numeric-ids-sec-considerations-06</a>&gt;</span>. </dd>
2830 <dd class="break"></dd>
2831 <dt id="I-D.ietf-pce-pcep-yang">[PCE-PCEP-YANG]</dt>
2832 <dd>
2833 <span class="refAuthor">Dhody, D.</span>, <span class="refAuthor">Hardwick, J.</span>, <span class="refAuthor">Beeram, V. P.</span>, and <span class="refAuthor">J. Tantsura</span>, <span class="refTitle">"A YANG Data Model for Path Computation Element Communications Protocol (PCEP)"</span>, <span class="refContent">Work in Progress</span>, <span class="seriesInfo">Internet-Draft, draft-ietf-pce-pcep-yang-17</span>, <time datetime="2021-10-23" class="refDate">23 October 2021</time>, <span>&lt;<a href="https://datatracker.ietf.org/doc/html/draft-ietf-pce-pcep-yang-17">https://datatracker.ietf.org/doc/html/draft-ietf-pce-pcep-yang-17</a>&gt;</span>. </dd>
2834 <dd class="break"></dd>
2835 <dt id="RFC4655">[RFC4655]</dt>
2836 <dd>
2837 <span class="refAuthor">Farrel, A.</span>, <span class="refAuthor">Vasseur, J.-P.</span>, and <span class="refAuthor">J. Ash</span>, <span class="refTitle">"A Path Computation Element (PCE)-Based Architecture"</span>, <span class="seriesInfo">RFC 4655</span>, <span class="seriesInfo">DOI 10.17487/RFC4655</span>, <time datetime="2006-08" class="refDate">August 2006</time>, <span>&lt;<a href="https://www.rfc-editor.org/info/rfc4655">https://www.rfc-editor.org/info/rfc4655</a>&gt;</span>. </dd>
2838 <dd class="break"></dd>
2839 <dt id="RFC5088">[RFC5088]</dt>
2840 <dd>
2841 <span class="refAuthor">Le Roux, JL., Ed.</span>, <span class="refAuthor">Vasseur, JP., Ed.</span>, <span class="refAuthor">Ikejiri, Y.</span>, and <span class="refAuthor">R. Zhang</span>, <span class="refTitle">"OSPF Protocol Extensions for Path Computation Element (PCE) Discovery"</span>, <span class="seriesInfo">RFC 5088</span>, <span class="seriesInfo">DOI 10.17487/RFC5088</span>, <time datetime="2008-01" class="refDate">January 2008</time>, <span>&lt;<a href="https://www.rfc-editor.org/info/rfc5088">https://www.rfc-editor.org/info/rfc5088</a>&gt;</span>. </dd>
2842 <dd class="break"></dd>
2843 <dt id="RFC5089">[RFC5089]</dt>
2844 <dd>
2845 <span class="refAuthor">Le Roux, JL., Ed.</span>, <span class="refAuthor">Vasseur, JP., Ed.</span>, <span class="refAuthor">Ikejiri, Y.</span>, and <span class="refAuthor">R. Zhang</span>, <span class="refTitle">"IS-IS Protocol Extensions for Path Computation Element (PCE) Discovery"</span>, <span class="seriesInfo">RFC 5089</span>, <span class="seriesInfo">DOI 10.17487/RFC5089</span>, <time datetime="2008-01" class="refDate">January 2008</time>, <span>&lt;<a href="https://www.rfc-editor.org/info/rfc5089">https://www.rfc-editor.org/info/rfc5089</a>&gt;</span>. </dd>
2846 <dd class="break"></dd>
2847 <dt id="RFC5886">[RFC5886]</dt>
2848 <dd>
2849 <span class="refAuthor">Vasseur, JP., Ed.</span>, <span class="refAuthor">Le Roux, JL.</span>, and <span class="refAuthor">Y. Ikejiri</span>, <span class="refTitle">"A Set of Monitoring Tools for Path Computation Element (PCE)-Based Architecture"</span>, <span class="seriesInfo">RFC 5886</span>, <span class="seriesInfo">DOI 10.17487/RFC5886</span>, <time datetime="2010-06" class="refDate">June 2010</time>, <span>&lt;<a href="https://www.rfc-editor.org/info/rfc5886">https://www.rfc-editor.org/info/rfc5886</a>&gt;</span>. </dd>
2850 <dd class="break"></dd>
2851 <dt id="RFC6123">[RFC6123]</dt>
2852 <dd>
2853 <span class="refAuthor">Farrel, A.</span>, <span class="refTitle">"Inclusion of Manageability Sections in Path Computation Element (PCE) Working Group Drafts"</span>, <span class="seriesInfo">RFC 6123</span>, <span class="seriesInfo">DOI 10.17487/RFC6123</span>, <time datetime="2011-02" class="refDate">February 2011</time>, <span>&lt;<a href="https://www.rfc-editor.org/info/rfc6123">https://www.rfc-editor.org/info/rfc6123</a>&gt;</span>. </dd>
2854 <dd class="break"></dd>
2855 <dt id="RFC6952">[RFC6952]</dt>
2856 <dd>
2857 <span class="refAuthor">Jethanandani, M.</span>, <span class="refAuthor">Patel, K.</span>, and <span class="refAuthor">L. Zheng</span>, <span class="refTitle">"Analysis of BGP, LDP, PCEP, and MSDP Issues According to the Keying and Authentication for Routing Protocols (KARP) Design Guide"</span>, <span class="seriesInfo">RFC 6952</span>, <span class="seriesInfo">DOI 10.17487/RFC6952</span>, <time datetime="2013-05" class="refDate">May 2013</time>, <span>&lt;<a href="https://www.rfc-editor.org/info/rfc6952">https://www.rfc-editor.org/info/rfc6952</a>&gt;</span>. </dd>
2858 <dd class="break"></dd>
2859 <dt id="RFC7399">[RFC7399]</dt>
2860 <dd>
2861 <span class="refAuthor">Farrel, A.</span> and <span class="refAuthor">D. King</span>, <span class="refTitle">"Unanswered Questions in the Path Computation Element Architecture"</span>, <span class="seriesInfo">RFC 7399</span>, <span class="seriesInfo">DOI 10.17487/RFC7399</span>, <time datetime="2014-10" class="refDate">October 2014</time>, <span>&lt;<a href="https://www.rfc-editor.org/info/rfc7399">https://www.rfc-editor.org/info/rfc7399</a>&gt;</span>. </dd>
2862 <dd class="break"></dd>
2863 <dt id="RFC8126">[RFC8126]</dt>
2864 <dd>
2865 <span class="refAuthor">Cotton, M.</span>, <span class="refAuthor">Leiba, B.</span>, and <span class="refAuthor">T. Narten</span>, <span class="refTitle">"Guidelines for Writing an IANA Considerations Section in RFCs"</span>, <span class="seriesInfo">BCP 26</span>, <span class="seriesInfo">RFC 8126</span>, <span class="seriesInfo">DOI 10.17487/RFC8126</span>, <time datetime="2017-06" class="refDate">June 2017</time>, <span>&lt;<a href="https://www.rfc-editor.org/info/rfc8126">https://www.rfc-editor.org/info/rfc8126</a>&gt;</span>. </dd>
2866 <dd class="break"></dd>
2867 <dt id="RFC8283">[RFC8283]</dt>
2868 <dd>
2869 <span class="refAuthor">Farrel, A., Ed.</span>, <span class="refAuthor">Zhao, Q., Ed.</span>, <span class="refAuthor">Li, Z.</span>, and <span class="refAuthor">C. Zhou</span>, <span class="refTitle">"An Architecture for Use of PCE and the PCE Communication Protocol (PCEP) in a Network with Central Control"</span>, <span class="seriesInfo">RFC 8283</span>, <span class="seriesInfo">DOI 10.17487/RFC8283</span>, <time datetime="2017-12" class="refDate">December 2017</time>, <span>&lt;<a href="https://www.rfc-editor.org/info/rfc8283">https://www.rfc-editor.org/info/rfc8283</a>&gt;</span>. </dd>
2870 <dd class="break"></dd>
2871 <dt id="RFC8664">[RFC8664]</dt>
2872 <dd>
2873 <span class="refAuthor">Sivabalan, S.</span>, <span class="refAuthor">Filsfils, C.</span>, <span class="refAuthor">Tantsura, J.</span>, <span class="refAuthor">Henderickx, W.</span>, and <span class="refAuthor">J. Hardwick</span>, <span class="refTitle">"Path Computation Element Communication Protocol (PCEP) Extensions for Segment Routing"</span>, <span class="seriesInfo">RFC 8664</span>, <span class="seriesInfo">DOI 10.17487/RFC8664</span>, <time datetime="2019-12" class="refDate">December 2019</time>, <span>&lt;<a href="https://www.rfc-editor.org/info/rfc8664">https://www.rfc-editor.org/info/rfc8664</a>&gt;</span>. </dd>
2874 <dd class="break"></dd>
2875 <dt id="I-D.ietf-teas-yang-path-computation">[TEAS-YANG-PATH]</dt>
2876 <dd>
2877 <span class="refAuthor">Busi, I.</span>, <span class="refAuthor">Belotti, S.</span>, <span class="refAuthor">Lopez, V.</span>, <span class="refAuthor">Sharma, A.</span>, and <span class="refAuthor">Y. Shi</span>, <span class="refTitle">"YANG Data Model for requesting Path Computation"</span>, <span class="refContent">Work in Progress</span>, <span class="seriesInfo">Internet-Draft, draft-ietf-teas-yang-path-computation-16</span>, <time datetime="2021-09-06" class="refDate">6 September 2021</time>, <span>&lt;<a href="https://datatracker.ietf.org/doc/html/draft-ietf-teas-yang-path-computation-16">https://datatracker.ietf.org/doc/html/draft-ietf-teas-yang-path-computation-16</a>&gt;</span>. </dd>
2878 <dd class="break"></dd>
2879 </dl>
2880 </section>
2881 </section>
2882 <section id="appendix-A">
2883 <h2 id="name-acknowledgements">
2884 <a href="#name-acknowledgements" class="section-name selfRef">Acknowledgements</a>
2885 </h2>
2886 <p id="appendix-A-1">Thanks to <span class="contact-name">Julian Lucek</span>, <span class="contact-name">Sudhir Cheruathur</span>, <span class="contact-name">Olivier Dugeon</span>, <span class="contact-name">Jayant Agarwal</span>, <span class="contact-name">Jeffrey Zhang</span>,
2887 <span class="contact-name">Acee Lindem</span>, <span class="contact-name">Vishnu Pavan Beeram</span>, <span class="contact-name">Julien Meuric</span>, <span class="contact-name">Deborah Brungard</span>, <span class="contact-name">Éric Vyncke</span>, <span class="contact-name">Erik Kline</span>,
2888 <span class="contact-name">Benjamin Kaduk</span>, <span class="contact-name">Martin Duke</span>, <span class="contact-name">Roman Danyliw</span>, and <span class="contact-name">Alvaro Retana</span> for useful discussions and
2889 comments.<a href="#appendix-A-1" class="pilcrow">¶</a></p>
2890 </section>
2891 <section id="appendix-B">
2892 <h2 id="name-contributors">
2893 <a href="#name-contributors" class="section-name selfRef">Contributors</a>
2894 </h2>
2895 <address class="vcard">
2896 <div dir="auto" class="left"><span class="fn nameRole">Shankara</span></div>
2897 <div dir="auto" class="left"><span class="org">Huawei Technologies</span></div>
2898 <div dir="auto" class="left"><span class="street-address">Divyashree Techno Park, Whitefield</span></div>
2899 <div dir="auto" class="left">
2900 <span class="locality">Bangalore</span> <span class="postal-code">560066</span>
2901 </div>
2902 <div dir="auto" class="left"><span class="region">Karnataka</span></div>
2903 <div dir="auto" class="left"><span class="country-name">India</span></div>
2904 <div class="email">
2905 <span>Email:</span>
2906 <a href="mailto:[email protected]" class="email">[email protected]</a>
2907 </div>
2908 </address>
2909 <address class="vcard">
2910 <div dir="auto" class="left"><span class="fn nameRole">Qiandeng Liang</span></div>
2911 <div dir="auto" class="left"><span class="org">Huawei Technologies</span></div>
2912 <div dir="auto" class="left"><span class="extended-address">Yuhuatai District</span></div>
2913 <div dir="auto" class="left"><span class="street-address">101 Software Avenue,</span></div>
2914 <div dir="auto" class="left">
2915 <span class="region">Nanjing</span>, <span class="postal-code">210012</span>
2916 </div>
2917 <div dir="auto" class="left"><span class="country-name">China</span></div>
2918 <div class="email">
2919 <span>Email:</span>
2920 <a href="mailto:[email protected]" class="email">[email protected]</a>
2921 </div>
2922 </address>
2923 <address class="vcard">
2924 <div dir="auto" class="left"><span class="fn nameRole">Cyril Margaria</span></div>
2925 <div dir="auto" class="left"><span class="org">Juniper Networks</span></div>
2926 <div dir="auto" class="left"><span class="street-address">200 Somerset Corporate Boulevard, Suite 4001</span></div>
2927 <div dir="auto" class="left">
2928 <span class="region">Bridgewater, NJ</span> <span class="postal-code">08807</span>
2929 </div>
2930 <div dir="auto" class="left"><span class="country-name">United States of America</span></div>
2931 <div class="email">
2932 <span>Email:</span>
2933 <a href="mailto:[email protected]" class="email">[email protected]</a>
2934 </div>
2935 </address>
2936 <address class="vcard">
2937 <div dir="auto" class="left"><span class="fn nameRole">Colby Barth</span></div>
2938 <div dir="auto" class="left"><span class="org">Juniper Networks</span></div>
2939 <div dir="auto" class="left"><span class="street-address">200 Somerset Corporate Boulevard, Suite 4001</span></div>
2940 <div dir="auto" class="left">
2941 <span class="region">Bridgewater, NJ</span> <span class="postal-code">08807</span>
2942 </div>
2943 <div dir="auto" class="left"><span class="country-name">United States of America</span></div>
2944 <div class="email">
2945 <span>Email:</span>
2946 <a href="mailto:[email protected]" class="email">[email protected]</a>
2947 </div>
2948 </address>
2949 <address class="vcard">
2950 <div dir="auto" class="left"><span class="fn nameRole">Xia Chen</span></div>
2951 <div dir="auto" class="left"><span class="org">Huawei Technologies</span></div>
2952 <div dir="auto" class="left"><span class="street-address">Huawei Bld., No. 156 Beiqing Rd.</span></div>
2953 <div dir="auto" class="left">
2954 <span class="region">Beijing</span>, <span class="postal-code">100095</span>
2955 </div>
2956 <div dir="auto" class="left"><span class="country-name">China</span></div>
2957 <div class="email">
2958 <span>Email:</span>
2959 <a href="mailto:[email protected]" class="email">[email protected]</a>
2960 </div>
2961 </address>
2962 <address class="vcard">
2963 <div dir="auto" class="left"><span class="fn nameRole">Shunwan Zhuang</span></div>
2964 <div dir="auto" class="left"><span class="org">Huawei Technologies</span></div>
2965 <div dir="auto" class="left"><span class="street-address">Huawei Bld., No. 156 Beiqing Rd.</span></div>
2966 <div dir="auto" class="left">
2967 <span class="region">Beijing</span>, <span class="postal-code">100095</span>
2968 </div>
2969 <div dir="auto" class="left"><span class="country-name">China</span></div>
2970 <div class="email">
2971 <span>Email:</span>
2972 <a href="mailto:[email protected]" class="email">[email protected]</a>
2973 </div>
2974 </address>
2975 <address class="vcard">
2976 <div dir="auto" class="left"><span class="fn nameRole">Cheng Li</span></div>
2977 <div dir="auto" class="left"><span class="org">Huawei Technologies</span></div>
2978 <div dir="auto" class="left"><span class="street-address">Huawei Campus, No. 156 Beiqing Rd.</span></div>
2979 <div dir="auto" class="left">
2980 <span class="region">Beijing</span>, <span class="postal-code">100095</span>
2981 </div>
2982 <div dir="auto" class="left"><span class="country-name">China</span></div>
2983 <div class="email">
2984 <span>Email:</span>
2985 <a href="mailto:[email protected]" class="email">[email protected]</a>
2986 </div>
2987 </address>
2988 </section>
2989 <div id="authors-addresses">
2990 <section id="appendix-C">
2991 <h2 id="name-authors-addresses">
2992 <a href="#name-authors-addresses" class="section-name selfRef">Authors' Addresses</a>
2993 </h2>
2994 <address class="vcard">
2995 <div dir="auto" class="left"><span class="fn nameRole">Dhruv Dhody</span></div>
2996 <div dir="auto" class="left"><span class="org">Huawei Technologies</span></div>
2997 <div dir="auto" class="left"><span class="street-address">Divyashree Techno Park, Whitefield</span></div>
2998 <div dir="auto" class="left">
2999 <span class="locality">Bangalore</span> <span class="postal-code">560066</span>
3000 </div>
3001 <div dir="auto" class="left"><span class="region">Karnataka</span></div>
3002 <div dir="auto" class="left"><span class="country-name">India</span></div>
3003 <div class="email">
3004 <span>Email:</span>
3005 <a href="mailto:[email protected]" class="email">[email protected]</a>
3006 </div>
3007 </address>
3008 <address class="vcard">
3009 <div dir="auto" class="left"><span class="fn nameRole">Adrian Farrel</span></div>
3010 <div dir="auto" class="left"><span class="org">Old Dog Consulting</span></div>
3011 <div class="email">
3012 <span>Email:</span>
3013 <a href="mailto:[email protected]" class="email">[email protected]</a>
3014 </div>
3015 </address>
3016 <address class="vcard">
3017 <div dir="auto" class="left"><span class="fn nameRole">Zhenbin Li</span></div>
3018 <div dir="auto" class="left"><span class="org">Huawei Technologies</span></div>
3019 <div dir="auto" class="left"><span class="street-address">Huawei Bldg., No. 156 Beiqing Rd.</span></div>
3020 <div dir="auto" class="left"><span class="locality">Beijing</span></div>
3021 <div dir="auto" class="left"><span class="postal-code">100095</span></div>
3022 <div dir="auto" class="left"><span class="country-name">China</span></div>
3023 <div class="email">
3024 <span>Email:</span>
3025 <a href="mailto:[email protected]" class="email">[email protected]</a>
3026 </div>
3027 </address>
3028 </section>
3029 </div>
3030 <script>const toc = document.getElementById("toc");
3031 toc.querySelector("h2").addEventListener("click", e => {
3032 toc.classList.toggle("active");
3033 });
3034 toc.querySelector("nav").addEventListener("click", e => {
3035 toc.classList.remove("active");
3036 });
3037 </script>
3038 </body>
3039 </html>