File: rfc8779.html

package info (click to toggle)
doc-rfc 20201128-1
  • links: PTS, VCS
  • area: non-free
  • in suites: bullseye
  • size: 1,307,124 kB
file content (4135 lines) | stat: -rw-r--r-- 232,413 bytes parent folder | download | duplicates (2)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
173
174
175
176
177
178
179
180
181
182
183
184
185
186
187
188
189
190
191
192
193
194
195
196
197
198
199
200
201
202
203
204
205
206
207
208
209
210
211
212
213
214
215
216
217
218
219
220
221
222
223
224
225
226
227
228
229
230
231
232
233
234
235
236
237
238
239
240
241
242
243
244
245
246
247
248
249
250
251
252
253
254
255
256
257
258
259
260
261
262
263
264
265
266
267
268
269
270
271
272
273
274
275
276
277
278
279
280
281
282
283
284
285
286
287
288
289
290
291
292
293
294
295
296
297
298
299
300
301
302
303
304
305
306
307
308
309
310
311
312
313
314
315
316
317
318
319
320
321
322
323
324
325
326
327
328
329
330
331
332
333
334
335
336
337
338
339
340
341
342
343
344
345
346
347
348
349
350
351
352
353
354
355
356
357
358
359
360
361
362
363
364
365
366
367
368
369
370
371
372
373
374
375
376
377
378
379
380
381
382
383
384
385
386
387
388
389
390
391
392
393
394
395
396
397
398
399
400
401
402
403
404
405
406
407
408
409
410
411
412
413
414
415
416
417
418
419
420
421
422
423
424
425
426
427
428
429
430
431
432
433
434
435
436
437
438
439
440
441
442
443
444
445
446
447
448
449
450
451
452
453
454
455
456
457
458
459
460
461
462
463
464
465
466
467
468
469
470
471
472
473
474
475
476
477
478
479
480
481
482
483
484
485
486
487
488
489
490
491
492
493
494
495
496
497
498
499
500
501
502
503
504
505
506
507
508
509
510
511
512
513
514
515
516
517
518
519
520
521
522
523
524
525
526
527
528
529
530
531
532
533
534
535
536
537
538
539
540
541
542
543
544
545
546
547
548
549
550
551
552
553
554
555
556
557
558
559
560
561
562
563
564
565
566
567
568
569
570
571
572
573
574
575
576
577
578
579
580
581
582
583
584
585
586
587
588
589
590
591
592
593
594
595
596
597
598
599
600
601
602
603
604
605
606
607
608
609
610
611
612
613
614
615
616
617
618
619
620
621
622
623
624
625
626
627
628
629
630
631
632
633
634
635
636
637
638
639
640
641
642
643
644
645
646
647
648
649
650
651
652
653
654
655
656
657
658
659
660
661
662
663
664
665
666
667
668
669
670
671
672
673
674
675
676
677
678
679
680
681
682
683
684
685
686
687
688
689
690
691
692
693
694
695
696
697
698
699
700
701
702
703
704
705
706
707
708
709
710
711
712
713
714
715
716
717
718
719
720
721
722
723
724
725
726
727
728
729
730
731
732
733
734
735
736
737
738
739
740
741
742
743
744
745
746
747
748
749
750
751
752
753
754
755
756
757
758
759
760
761
762
763
764
765
766
767
768
769
770
771
772
773
774
775
776
777
778
779
780
781
782
783
784
785
786
787
788
789
790
791
792
793
794
795
796
797
798
799
800
801
802
803
804
805
806
807
808
809
810
811
812
813
814
815
816
817
818
819
820
821
822
823
824
825
826
827
828
829
830
831
832
833
834
835
836
837
838
839
840
841
842
843
844
845
846
847
848
849
850
851
852
853
854
855
856
857
858
859
860
861
862
863
864
865
866
867
868
869
870
871
872
873
874
875
876
877
878
879
880
881
882
883
884
885
886
887
888
889
890
891
892
893
894
895
896
897
898
899
900
901
902
903
904
905
906
907
908
909
910
911
912
913
914
915
916
917
918
919
920
921
922
923
924
925
926
927
928
929
930
931
932
933
934
935
936
937
938
939
940
941
942
943
944
945
946
947
948
949
950
951
952
953
954
955
956
957
958
959
960
961
962
963
964
965
966
967
968
969
970
971
972
973
974
975
976
977
978
979
980
981
982
983
984
985
986
987
988
989
990
991
992
993
994
995
996
997
998
999
1000
1001
1002
1003
1004
1005
1006
1007
1008
1009
1010
1011
1012
1013
1014
1015
1016
1017
1018
1019
1020
1021
1022
1023
1024
1025
1026
1027
1028
1029
1030
1031
1032
1033
1034
1035
1036
1037
1038
1039
1040
1041
1042
1043
1044
1045
1046
1047
1048
1049
1050
1051
1052
1053
1054
1055
1056
1057
1058
1059
1060
1061
1062
1063
1064
1065
1066
1067
1068
1069
1070
1071
1072
1073
1074
1075
1076
1077
1078
1079
1080
1081
1082
1083
1084
1085
1086
1087
1088
1089
1090
1091
1092
1093
1094
1095
1096
1097
1098
1099
1100
1101
1102
1103
1104
1105
1106
1107
1108
1109
1110
1111
1112
1113
1114
1115
1116
1117
1118
1119
1120
1121
1122
1123
1124
1125
1126
1127
1128
1129
1130
1131
1132
1133
1134
1135
1136
1137
1138
1139
1140
1141
1142
1143
1144
1145
1146
1147
1148
1149
1150
1151
1152
1153
1154
1155
1156
1157
1158
1159
1160
1161
1162
1163
1164
1165
1166
1167
1168
1169
1170
1171
1172
1173
1174
1175
1176
1177
1178
1179
1180
1181
1182
1183
1184
1185
1186
1187
1188
1189
1190
1191
1192
1193
1194
1195
1196
1197
1198
1199
1200
1201
1202
1203
1204
1205
1206
1207
1208
1209
1210
1211
1212
1213
1214
1215
1216
1217
1218
1219
1220
1221
1222
1223
1224
1225
1226
1227
1228
1229
1230
1231
1232
1233
1234
1235
1236
1237
1238
1239
1240
1241
1242
1243
1244
1245
1246
1247
1248
1249
1250
1251
1252
1253
1254
1255
1256
1257
1258
1259
1260
1261
1262
1263
1264
1265
1266
1267
1268
1269
1270
1271
1272
1273
1274
1275
1276
1277
1278
1279
1280
1281
1282
1283
1284
1285
1286
1287
1288
1289
1290
1291
1292
1293
1294
1295
1296
1297
1298
1299
1300
1301
1302
1303
1304
1305
1306
1307
1308
1309
1310
1311
1312
1313
1314
1315
1316
1317
1318
1319
1320
1321
1322
1323
1324
1325
1326
1327
1328
1329
1330
1331
1332
1333
1334
1335
1336
1337
1338
1339
1340
1341
1342
1343
1344
1345
1346
1347
1348
1349
1350
1351
1352
1353
1354
1355
1356
1357
1358
1359
1360
1361
1362
1363
1364
1365
1366
1367
1368
1369
1370
1371
1372
1373
1374
1375
1376
1377
1378
1379
1380
1381
1382
1383
1384
1385
1386
1387
1388
1389
1390
1391
1392
1393
1394
1395
1396
1397
1398
1399
1400
1401
1402
1403
1404
1405
1406
1407
1408
1409
1410
1411
1412
1413
1414
1415
1416
1417
1418
1419
1420
1421
1422
1423
1424
1425
1426
1427
1428
1429
1430
1431
1432
1433
1434
1435
1436
1437
1438
1439
1440
1441
1442
1443
1444
1445
1446
1447
1448
1449
1450
1451
1452
1453
1454
1455
1456
1457
1458
1459
1460
1461
1462
1463
1464
1465
1466
1467
1468
1469
1470
1471
1472
1473
1474
1475
1476
1477
1478
1479
1480
1481
1482
1483
1484
1485
1486
1487
1488
1489
1490
1491
1492
1493
1494
1495
1496
1497
1498
1499
1500
1501
1502
1503
1504
1505
1506
1507
1508
1509
1510
1511
1512
1513
1514
1515
1516
1517
1518
1519
1520
1521
1522
1523
1524
1525
1526
1527
1528
1529
1530
1531
1532
1533
1534
1535
1536
1537
1538
1539
1540
1541
1542
1543
1544
1545
1546
1547
1548
1549
1550
1551
1552
1553
1554
1555
1556
1557
1558
1559
1560
1561
1562
1563
1564
1565
1566
1567
1568
1569
1570
1571
1572
1573
1574
1575
1576
1577
1578
1579
1580
1581
1582
1583
1584
1585
1586
1587
1588
1589
1590
1591
1592
1593
1594
1595
1596
1597
1598
1599
1600
1601
1602
1603
1604
1605
1606
1607
1608
1609
1610
1611
1612
1613
1614
1615
1616
1617
1618
1619
1620
1621
1622
1623
1624
1625
1626
1627
1628
1629
1630
1631
1632
1633
1634
1635
1636
1637
1638
1639
1640
1641
1642
1643
1644
1645
1646
1647
1648
1649
1650
1651
1652
1653
1654
1655
1656
1657
1658
1659
1660
1661
1662
1663
1664
1665
1666
1667
1668
1669
1670
1671
1672
1673
1674
1675
1676
1677
1678
1679
1680
1681
1682
1683
1684
1685
1686
1687
1688
1689
1690
1691
1692
1693
1694
1695
1696
1697
1698
1699
1700
1701
1702
1703
1704
1705
1706
1707
1708
1709
1710
1711
1712
1713
1714
1715
1716
1717
1718
1719
1720
1721
1722
1723
1724
1725
1726
1727
1728
1729
1730
1731
1732
1733
1734
1735
1736
1737
1738
1739
1740
1741
1742
1743
1744
1745
1746
1747
1748
1749
1750
1751
1752
1753
1754
1755
1756
1757
1758
1759
1760
1761
1762
1763
1764
1765
1766
1767
1768
1769
1770
1771
1772
1773
1774
1775
1776
1777
1778
1779
1780
1781
1782
1783
1784
1785
1786
1787
1788
1789
1790
1791
1792
1793
1794
1795
1796
1797
1798
1799
1800
1801
1802
1803
1804
1805
1806
1807
1808
1809
1810
1811
1812
1813
1814
1815
1816
1817
1818
1819
1820
1821
1822
1823
1824
1825
1826
1827
1828
1829
1830
1831
1832
1833
1834
1835
1836
1837
1838
1839
1840
1841
1842
1843
1844
1845
1846
1847
1848
1849
1850
1851
1852
1853
1854
1855
1856
1857
1858
1859
1860
1861
1862
1863
1864
1865
1866
1867
1868
1869
1870
1871
1872
1873
1874
1875
1876
1877
1878
1879
1880
1881
1882
1883
1884
1885
1886
1887
1888
1889
1890
1891
1892
1893
1894
1895
1896
1897
1898
1899
1900
1901
1902
1903
1904
1905
1906
1907
1908
1909
1910
1911
1912
1913
1914
1915
1916
1917
1918
1919
1920
1921
1922
1923
1924
1925
1926
1927
1928
1929
1930
1931
1932
1933
1934
1935
1936
1937
1938
1939
1940
1941
1942
1943
1944
1945
1946
1947
1948
1949
1950
1951
1952
1953
1954
1955
1956
1957
1958
1959
1960
1961
1962
1963
1964
1965
1966
1967
1968
1969
1970
1971
1972
1973
1974
1975
1976
1977
1978
1979
1980
1981
1982
1983
1984
1985
1986
1987
1988
1989
1990
1991
1992
1993
1994
1995
1996
1997
1998
1999
2000
2001
2002
2003
2004
2005
2006
2007
2008
2009
2010
2011
2012
2013
2014
2015
2016
2017
2018
2019
2020
2021
2022
2023
2024
2025
2026
2027
2028
2029
2030
2031
2032
2033
2034
2035
2036
2037
2038
2039
2040
2041
2042
2043
2044
2045
2046
2047
2048
2049
2050
2051
2052
2053
2054
2055
2056
2057
2058
2059
2060
2061
2062
2063
2064
2065
2066
2067
2068
2069
2070
2071
2072
2073
2074
2075
2076
2077
2078
2079
2080
2081
2082
2083
2084
2085
2086
2087
2088
2089
2090
2091
2092
2093
2094
2095
2096
2097
2098
2099
2100
2101
2102
2103
2104
2105
2106
2107
2108
2109
2110
2111
2112
2113
2114
2115
2116
2117
2118
2119
2120
2121
2122
2123
2124
2125
2126
2127
2128
2129
2130
2131
2132
2133
2134
2135
2136
2137
2138
2139
2140
2141
2142
2143
2144
2145
2146
2147
2148
2149
2150
2151
2152
2153
2154
2155
2156
2157
2158
2159
2160
2161
2162
2163
2164
2165
2166
2167
2168
2169
2170
2171
2172
2173
2174
2175
2176
2177
2178
2179
2180
2181
2182
2183
2184
2185
2186
2187
2188
2189
2190
2191
2192
2193
2194
2195
2196
2197
2198
2199
2200
2201
2202
2203
2204
2205
2206
2207
2208
2209
2210
2211
2212
2213
2214
2215
2216
2217
2218
2219
2220
2221
2222
2223
2224
2225
2226
2227
2228
2229
2230
2231
2232
2233
2234
2235
2236
2237
2238
2239
2240
2241
2242
2243
2244
2245
2246
2247
2248
2249
2250
2251
2252
2253
2254
2255
2256
2257
2258
2259
2260
2261
2262
2263
2264
2265
2266
2267
2268
2269
2270
2271
2272
2273
2274
2275
2276
2277
2278
2279
2280
2281
2282
2283
2284
2285
2286
2287
2288
2289
2290
2291
2292
2293
2294
2295
2296
2297
2298
2299
2300
2301
2302
2303
2304
2305
2306
2307
2308
2309
2310
2311
2312
2313
2314
2315
2316
2317
2318
2319
2320
2321
2322
2323
2324
2325
2326
2327
2328
2329
2330
2331
2332
2333
2334
2335
2336
2337
2338
2339
2340
2341
2342
2343
2344
2345
2346
2347
2348
2349
2350
2351
2352
2353
2354
2355
2356
2357
2358
2359
2360
2361
2362
2363
2364
2365
2366
2367
2368
2369
2370
2371
2372
2373
2374
2375
2376
2377
2378
2379
2380
2381
2382
2383
2384
2385
2386
2387
2388
2389
2390
2391
2392
2393
2394
2395
2396
2397
2398
2399
2400
2401
2402
2403
2404
2405
2406
2407
2408
2409
2410
2411
2412
2413
2414
2415
2416
2417
2418
2419
2420
2421
2422
2423
2424
2425
2426
2427
2428
2429
2430
2431
2432
2433
2434
2435
2436
2437
2438
2439
2440
2441
2442
2443
2444
2445
2446
2447
2448
2449
2450
2451
2452
2453
2454
2455
2456
2457
2458
2459
2460
2461
2462
2463
2464
2465
2466
2467
2468
2469
2470
2471
2472
2473
2474
2475
2476
2477
2478
2479
2480
2481
2482
2483
2484
2485
2486
2487
2488
2489
2490
2491
2492
2493
2494
2495
2496
2497
2498
2499
2500
2501
2502
2503
2504
2505
2506
2507
2508
2509
2510
2511
2512
2513
2514
2515
2516
2517
2518
2519
2520
2521
2522
2523
2524
2525
2526
2527
2528
2529
2530
2531
2532
2533
2534
2535
2536
2537
2538
2539
2540
2541
2542
2543
2544
2545
2546
2547
2548
2549
2550
2551
2552
2553
2554
2555
2556
2557
2558
2559
2560
2561
2562
2563
2564
2565
2566
2567
2568
2569
2570
2571
2572
2573
2574
2575
2576
2577
2578
2579
2580
2581
2582
2583
2584
2585
2586
2587
2588
2589
2590
2591
2592
2593
2594
2595
2596
2597
2598
2599
2600
2601
2602
2603
2604
2605
2606
2607
2608
2609
2610
2611
2612
2613
2614
2615
2616
2617
2618
2619
2620
2621
2622
2623
2624
2625
2626
2627
2628
2629
2630
2631
2632
2633
2634
2635
2636
2637
2638
2639
2640
2641
2642
2643
2644
2645
2646
2647
2648
2649
2650
2651
2652
2653
2654
2655
2656
2657
2658
2659
2660
2661
2662
2663
2664
2665
2666
2667
2668
2669
2670
2671
2672
2673
2674
2675
2676
2677
2678
2679
2680
2681
2682
2683
2684
2685
2686
2687
2688
2689
2690
2691
2692
2693
2694
2695
2696
2697
2698
2699
2700
2701
2702
2703
2704
2705
2706
2707
2708
2709
2710
2711
2712
2713
2714
2715
2716
2717
2718
2719
2720
2721
2722
2723
2724
2725
2726
2727
2728
2729
2730
2731
2732
2733
2734
2735
2736
2737
2738
2739
2740
2741
2742
2743
2744
2745
2746
2747
2748
2749
2750
2751
2752
2753
2754
2755
2756
2757
2758
2759
2760
2761
2762
2763
2764
2765
2766
2767
2768
2769
2770
2771
2772
2773
2774
2775
2776
2777
2778
2779
2780
2781
2782
2783
2784
2785
2786
2787
2788
2789
2790
2791
2792
2793
2794
2795
2796
2797
2798
2799
2800
2801
2802
2803
2804
2805
2806
2807
2808
2809
2810
2811
2812
2813
2814
2815
2816
2817
2818
2819
2820
2821
2822
2823
2824
2825
2826
2827
2828
2829
2830
2831
2832
2833
2834
2835
2836
2837
2838
2839
2840
2841
2842
2843
2844
2845
2846
2847
2848
2849
2850
2851
2852
2853
2854
2855
2856
2857
2858
2859
2860
2861
2862
2863
2864
2865
2866
2867
2868
2869
2870
2871
2872
2873
2874
2875
2876
2877
2878
2879
2880
2881
2882
2883
2884
2885
2886
2887
2888
2889
2890
2891
2892
2893
2894
2895
2896
2897
2898
2899
2900
2901
2902
2903
2904
2905
2906
2907
2908
2909
2910
2911
2912
2913
2914
2915
2916
2917
2918
2919
2920
2921
2922
2923
2924
2925
2926
2927
2928
2929
2930
2931
2932
2933
2934
2935
2936
2937
2938
2939
2940
2941
2942
2943
2944
2945
2946
2947
2948
2949
2950
2951
2952
2953
2954
2955
2956
2957
2958
2959
2960
2961
2962
2963
2964
2965
2966
2967
2968
2969
2970
2971
2972
2973
2974
2975
2976
2977
2978
2979
2980
2981
2982
2983
2984
2985
2986
2987
2988
2989
2990
2991
2992
2993
2994
2995
2996
2997
2998
2999
3000
3001
3002
3003
3004
3005
3006
3007
3008
3009
3010
3011
3012
3013
3014
3015
3016
3017
3018
3019
3020
3021
3022
3023
3024
3025
3026
3027
3028
3029
3030
3031
3032
3033
3034
3035
3036
3037
3038
3039
3040
3041
3042
3043
3044
3045
3046
3047
3048
3049
3050
3051
3052
3053
3054
3055
3056
3057
3058
3059
3060
3061
3062
3063
3064
3065
3066
3067
3068
3069
3070
3071
3072
3073
3074
3075
3076
3077
3078
3079
3080
3081
3082
3083
3084
3085
3086
3087
3088
3089
3090
3091
3092
3093
3094
3095
3096
3097
3098
3099
3100
3101
3102
3103
3104
3105
3106
3107
3108
3109
3110
3111
3112
3113
3114
3115
3116
3117
3118
3119
3120
3121
3122
3123
3124
3125
3126
3127
3128
3129
3130
3131
3132
3133
3134
3135
3136
3137
3138
3139
3140
3141
3142
3143
3144
3145
3146
3147
3148
3149
3150
3151
3152
3153
3154
3155
3156
3157
3158
3159
3160
3161
3162
3163
3164
3165
3166
3167
3168
3169
3170
3171
3172
3173
3174
3175
3176
3177
3178
3179
3180
3181
3182
3183
3184
3185
3186
3187
3188
3189
3190
3191
3192
3193
3194
3195
3196
3197
3198
3199
3200
3201
3202
3203
3204
3205
3206
3207
3208
3209
3210
3211
3212
3213
3214
3215
3216
3217
3218
3219
3220
3221
3222
3223
3224
3225
3226
3227
3228
3229
3230
3231
3232
3233
3234
3235
3236
3237
3238
3239
3240
3241
3242
3243
3244
3245
3246
3247
3248
3249
3250
3251
3252
3253
3254
3255
3256
3257
3258
3259
3260
3261
3262
3263
3264
3265
3266
3267
3268
3269
3270
3271
3272
3273
3274
3275
3276
3277
3278
3279
3280
3281
3282
3283
3284
3285
3286
3287
3288
3289
3290
3291
3292
3293
3294
3295
3296
3297
3298
3299
3300
3301
3302
3303
3304
3305
3306
3307
3308
3309
3310
3311
3312
3313
3314
3315
3316
3317
3318
3319
3320
3321
3322
3323
3324
3325
3326
3327
3328
3329
3330
3331
3332
3333
3334
3335
3336
3337
3338
3339
3340
3341
3342
3343
3344
3345
3346
3347
3348
3349
3350
3351
3352
3353
3354
3355
3356
3357
3358
3359
3360
3361
3362
3363
3364
3365
3366
3367
3368
3369
3370
3371
3372
3373
3374
3375
3376
3377
3378
3379
3380
3381
3382
3383
3384
3385
3386
3387
3388
3389
3390
3391
3392
3393
3394
3395
3396
3397
3398
3399
3400
3401
3402
3403
3404
3405
3406
3407
3408
3409
3410
3411
3412
3413
3414
3415
3416
3417
3418
3419
3420
3421
3422
3423
3424
3425
3426
3427
3428
3429
3430
3431
3432
3433
3434
3435
3436
3437
3438
3439
3440
3441
3442
3443
3444
3445
3446
3447
3448
3449
3450
3451
3452
3453
3454
3455
3456
3457
3458
3459
3460
3461
3462
3463
3464
3465
3466
3467
3468
3469
3470
3471
3472
3473
3474
3475
3476
3477
3478
3479
3480
3481
3482
3483
3484
3485
3486
3487
3488
3489
3490
3491
3492
3493
3494
3495
3496
3497
3498
3499
3500
3501
3502
3503
3504
3505
3506
3507
3508
3509
3510
3511
3512
3513
3514
3515
3516
3517
3518
3519
3520
3521
3522
3523
3524
3525
3526
3527
3528
3529
3530
3531
3532
3533
3534
3535
3536
3537
3538
3539
3540
3541
3542
3543
3544
3545
3546
3547
3548
3549
3550
3551
3552
3553
3554
3555
3556
3557
3558
3559
3560
3561
3562
3563
3564
3565
3566
3567
3568
3569
3570
3571
3572
3573
3574
3575
3576
3577
3578
3579
3580
3581
3582
3583
3584
3585
3586
3587
3588
3589
3590
3591
3592
3593
3594
3595
3596
3597
3598
3599
3600
3601
3602
3603
3604
3605
3606
3607
3608
3609
3610
3611
3612
3613
3614
3615
3616
3617
3618
3619
3620
3621
3622
3623
3624
3625
3626
3627
3628
3629
3630
3631
3632
3633
3634
3635
3636
3637
3638
3639
3640
3641
3642
3643
3644
3645
3646
3647
3648
3649
3650
3651
3652
3653
3654
3655
3656
3657
3658
3659
3660
3661
3662
3663
3664
3665
3666
3667
3668
3669
3670
3671
3672
3673
3674
3675
3676
3677
3678
3679
3680
3681
3682
3683
3684
3685
3686
3687
3688
3689
3690
3691
3692
3693
3694
3695
3696
3697
3698
3699
3700
3701
3702
3703
3704
3705
3706
3707
3708
3709
3710
3711
3712
3713
3714
3715
3716
3717
3718
3719
3720
3721
3722
3723
3724
3725
3726
3727
3728
3729
3730
3731
3732
3733
3734
3735
3736
3737
3738
3739
3740
3741
3742
3743
3744
3745
3746
3747
3748
3749
3750
3751
3752
3753
3754
3755
3756
3757
3758
3759
3760
3761
3762
3763
3764
3765
3766
3767
3768
3769
3770
3771
3772
3773
3774
3775
3776
3777
3778
3779
3780
3781
3782
3783
3784
3785
3786
3787
3788
3789
3790
3791
3792
3793
3794
3795
3796
3797
3798
3799
3800
3801
3802
3803
3804
3805
3806
3807
3808
3809
3810
3811
3812
3813
3814
3815
3816
3817
3818
3819
3820
3821
3822
3823
3824
3825
3826
3827
3828
3829
3830
3831
3832
3833
3834
3835
3836
3837
3838
3839
3840
3841
3842
3843
3844
3845
3846
3847
3848
3849
3850
3851
3852
3853
3854
3855
3856
3857
3858
3859
3860
3861
3862
3863
3864
3865
3866
3867
3868
3869
3870
3871
3872
3873
3874
3875
3876
3877
3878
3879
3880
3881
3882
3883
3884
3885
3886
3887
3888
3889
3890
3891
3892
3893
3894
3895
3896
3897
3898
3899
3900
3901
3902
3903
3904
3905
3906
3907
3908
3909
3910
3911
3912
3913
3914
3915
3916
3917
3918
3919
3920
3921
3922
3923
3924
3925
3926
3927
3928
3929
3930
3931
3932
3933
3934
3935
3936
3937
3938
3939
3940
3941
3942
3943
3944
3945
3946
3947
3948
3949
3950
3951
3952
3953
3954
3955
3956
3957
3958
3959
3960
3961
3962
3963
3964
3965
3966
3967
3968
3969
3970
3971
3972
3973
3974
3975
3976
3977
3978
3979
3980
3981
3982
3983
3984
3985
3986
3987
3988
3989
3990
3991
3992
3993
3994
3995
3996
3997
3998
3999
4000
4001
4002
4003
4004
4005
4006
4007
4008
4009
4010
4011
4012
4013
4014
4015
4016
4017
4018
4019
4020
4021
4022
4023
4024
4025
4026
4027
4028
4029
4030
4031
4032
4033
4034
4035
4036
4037
4038
4039
4040
4041
4042
4043
4044
4045
4046
4047
4048
4049
4050
4051
4052
4053
4054
4055
4056
4057
4058
4059
4060
4061
4062
4063
4064
4065
4066
4067
4068
4069
4070
4071
4072
4073
4074
4075
4076
4077
4078
4079
4080
4081
4082
4083
4084
4085
4086
4087
4088
4089
4090
4091
4092
4093
4094
4095
4096
4097
4098
4099
4100
4101
4102
4103
4104
4105
4106
4107
4108
4109
4110
4111
4112
4113
4114
4115
4116
4117
4118
4119
4120
4121
4122
4123
4124
4125
4126
4127
4128
4129
4130
4131
4132
4133
4134
4135
<!DOCTYPE html>
<html lang="en" class="RFC">
<head>
<meta charset="utf-8">
<meta content="Common,Latin" name="scripts">
<meta content="initial-scale=1.0" name="viewport">
<title>RFC 8779: Path Computation Element Communication Protocol (PCEP) Extensions for GMPLS</title>
<meta content="Cyril Margaria" name="author">
<meta content="Oscar Gonzalez de Dios" name="author">
<meta content="Fatai Zhang" name="author">
<meta content="
       A Path Computation Element (PCE) provides path computation functions
      for Multiprotocol Label Switching (MPLS) and Generalized MPLS (GMPLS)
      networks. Additional requirements for GMPLS are identified in
      RFC 7025.
       
        
        This memo provides extensions to the Path Computation Element
        Communication Protocol (PCEP) for the support of the GMPLS control plane
        to address those requirements.
       
    " name="description">
<meta content="xml2rfc 2.47.0" name="generator">
<meta content="RSVP-TE" name="keyword">
<meta content="GMPLS" name="keyword">
<meta content="PCE" name="keyword">
<meta content="8779" name="rfc.number">
<link href="rfc8779.xml" rel="alternate" type="application/rfc+xml">
<link href="#copyright" rel="license">
<style type="text/css">/*

  NOTE: Changes at the bottom of this file overrides some earlier settings.

  Once the style has stabilized and has been adopted as an official RFC style,
  this can be consolidated so that style settings occur only in one place, but
  for now the contents of this file consists first of the initial CSS work as
  provided to the RFC Formatter (xml2rfc) work, followed by itemized and
  commented changes found necssary during the development of the v3
  formatters.

*/

/* fonts */
@import url('https://fonts.googleapis.com/css?family=Noto+Sans'); /* Sans-serif */
@import url('https://fonts.googleapis.com/css?family=Noto+Serif'); /* Serif (print) */
@import url('https://fonts.googleapis.com/css?family=Roboto+Mono'); /* Monospace */

@viewport {
  zoom: 1.0;
  width: extend-to-zoom;
}
@-ms-viewport {
  width: extend-to-zoom;
  zoom: 1.0;
}
/* general and mobile first */
html {
}
body {
  max-width: 90%;
  margin: 1.5em auto;
  color: #222;
  background-color: #fff;
  font-size: 14px;
  font-family: 'Noto Sans', Arial, Helvetica, sans-serif;
  line-height: 1.6;
  scroll-behavior: smooth;
}
.ears {
  display: none;
}

/* headings */
#title, h1, h2, h3, h4, h5, h6 {
  margin: 1em 0 0.5em;
  font-weight: bold;
  line-height: 1.3;
}
#title {
  clear: both;
  border-bottom: 1px solid #ddd;
  margin: 0 0 0.5em 0;
  padding: 1em 0 0.5em;
}
.author {
  padding-bottom: 4px;
}
h1 {
  font-size: 26px;
  margin: 1em 0;
}
h2 {
  font-size: 22px;
  margin-top: -20px;  /* provide offset for in-page anchors */
  padding-top: 33px;
}
h3 {
  font-size: 18px;
  margin-top: -36px;  /* provide offset for in-page anchors */
  padding-top: 42px;
}
h4 {
  font-size: 16px;
  margin-top: -36px;  /* provide offset for in-page anchors */
  padding-top: 42px;
}
h5, h6 {
  font-size: 14px;
}
#n-copyright-notice {
  border-bottom: 1px solid #ddd;
  padding-bottom: 1em;
  margin-bottom: 1em;
}
/* general structure */
p {
  padding: 0;
  margin: 0 0 1em 0;
  text-align: left;
}
div, span {
  position: relative;
}
div {
  margin: 0;
}
.alignRight.art-text {
  background-color: #f9f9f9;
  border: 1px solid #eee;
  border-radius: 3px;
  padding: 1em 1em 0;
  margin-bottom: 1.5em;
}
.alignRight.art-text pre {
  padding: 0;
}
.alignRight {
  margin: 1em 0;
}
.alignRight > *:first-child {
  border: none;
  margin: 0;
  float: right;
  clear: both;
}
.alignRight > *:nth-child(2) {
  clear: both;
  display: block;
  border: none;
}
svg {
  display: block;
}
.alignCenter.art-text {
  background-color: #f9f9f9;
  border: 1px solid #eee;
  border-radius: 3px;
  padding: 1em 1em 0;
  margin-bottom: 1.5em;
}
.alignCenter.art-text pre {
  padding: 0;
}
.alignCenter {
  margin: 1em 0;
}
.alignCenter > *:first-child {
  border: none;
  /* this isn't optimal, but it's an existence proof.  PrinceXML doesn't
     support flexbox yet.
  */
  display: table;
  margin: 0 auto;
}

/* lists */
ol, ul {
  padding: 0;
  margin: 0 0 1em 2em;
}
ol ol, ul ul, ol ul, ul ol {
  margin-left: 1em;
}
li {
  margin: 0 0 0.25em 0;
}
.ulCompact li {
  margin: 0;
}
ul.empty, .ulEmpty {
  list-style-type: none;
}
ul.empty li, .ulEmpty li {
  margin-top: 0.5em;
}
ul.compact, .ulCompact,
ol.compact, .olCompact {
  line-height: 100%;
  margin: 0 0 0 2em;
}

/* definition lists */
dl {
}
dl > dt {
  float: left;
  margin-right: 1em;
}
/* 
dl.nohang > dt {
  float: none;
}
*/
dl > dd {
  margin-bottom: .8em;
  min-height: 1.3em;
}
dl.compact > dd, .dlCompact > dd {
  margin-bottom: 0em;
}
dl > dd > dl {
  margin-top: 0.5em;
  margin-bottom: 0em;
}

/* links */
a {
  text-decoration: none;
}
a[href] {
  color: #22e; /* Arlen: WCAG 2019 */
}
a[href]:hover {
  background-color: #f2f2f2;
}
figcaption a[href],
a[href].selfRef {
  color: #222;
}
/* XXX probably not this:
a.selfRef:hover {
  background-color: transparent;
  cursor: default;
} */

/* Figures */
tt, code, pre, code {
  background-color: #f9f9f9;
  font-family: 'Roboto Mono', monospace;
}
pre {
  border: 1px solid #eee;
  margin: 0;
  padding: 1em;
}
img {
  max-width: 100%;
}
figure {
  margin: 0;
}
figure blockquote {
  margin: 0.8em 0.4em 0.4em;
}
figcaption {
  font-style: italic;
  margin: 0 0 1em 0;
}
@media screen {
  pre {
    overflow-x: auto;
    max-width: 100%;
    max-width: calc(100% - 22px);
  }
}

/* aside, blockquote */
aside, blockquote {
  margin-left: 0;
  padding: 1.2em 2em;
}
blockquote {
  background-color: #f9f9f9;
  color: #111; /* Arlen: WCAG 2019 */
  border: 1px solid #ddd;
  border-radius: 3px;
  margin: 1em 0;
}
cite {
  display: block;
  text-align: right;
  font-style: italic;
}

/* tables */
table {
  width: 100%;
  margin: 0 0 1em;
  border-collapse: collapse;
  border: 1px solid #eee;
}
th, td {
  text-align: left;
  vertical-align: top;
  padding: 0.5em 0.75em;
}
th {
  text-align: left;
  background-color: #e9e9e9;
}
tr:nth-child(2n+1) > td {
  background-color: #f5f5f5;
}
table caption {
  font-style: italic;
  margin: 0;
  padding: 0;
  text-align: left;
}
table p {
  /* XXX to avoid bottom margin on table row signifiers. If paragraphs should
     be allowed within tables more generally, it would be far better to select on a class. */
  margin: 0;
}

/* pilcrow */
a.pilcrow {
  color: #666; /* Arlen: AHDJ 2019 */
  text-decoration: none;
  visibility: hidden;
  user-select: none;
  -ms-user-select: none;
  -o-user-select:none;
  -moz-user-select: none;
  -khtml-user-select: none;
  -webkit-user-select: none;
  -webkit-touch-callout: none;
}
@media screen {
  aside:hover > a.pilcrow,
  p:hover > a.pilcrow,
  blockquote:hover > a.pilcrow,
  div:hover > a.pilcrow,
  li:hover > a.pilcrow,
  pre:hover > a.pilcrow {
    visibility: visible;
  }
  a.pilcrow:hover {
    background-color: transparent;
  }
}

/* misc */
hr {
  border: 0;
  border-top: 1px solid #eee;
}
.bcp14 {
  font-variant: small-caps;
}

.role {
  font-variant: all-small-caps;
}

/* info block */
#identifiers {
  margin: 0;
  font-size: 0.9em;
}
#identifiers dt {
  width: 3em;
  clear: left;
}
#identifiers dd {
  float: left;
  margin-bottom: 0;
}
#identifiers .authors .author {
  display: inline-block;
  margin-right: 1.5em;
}
#identifiers .authors .org {
  font-style: italic;
}

/* The prepared/rendered info at the very bottom of the page */
.docInfo {
  color: #666; /* Arlen: WCAG 2019 */
  font-size: 0.9em;
  font-style: italic;
  margin-top: 2em;
}
.docInfo .prepared {
  float: left;
}
.docInfo .prepared {
  float: right;
}

/* table of contents */
#toc  {
  padding: 0.75em 0 2em 0;
  margin-bottom: 1em;
}
nav.toc ul {
  margin: 0 0.5em 0 0;
  padding: 0;
  list-style: none;
}
nav.toc li {
  line-height: 1.3em;
  margin: 0.75em 0;
  padding-left: 1.2em;
  text-indent: -1.2em;
}
/* references */
.references dt {
  text-align: right;
  font-weight: bold;
  min-width: 7em;
}
.references dd {
  margin-left: 8em;
  overflow: auto;
}

.refInstance {
  margin-bottom: 1.25em;
}

.references .ascii {
  margin-bottom: 0.25em;
}

/* index */
.index ul {
  margin: 0 0 0 1em;
  padding: 0;
  list-style: none;
}
.index ul ul {
  margin: 0;
}
.index li {
  margin: 0;
  text-indent: -2em;
  padding-left: 2em;
  padding-bottom: 5px;
}
.indexIndex {
  margin: 0.5em 0 1em;
}
.index a {
  font-weight: 700;
}
/* make the index two-column on all but the smallest screens */
@media (min-width: 600px) {
  .index ul {
    -moz-column-count: 2;
    -moz-column-gap: 20px;
  }
  .index ul ul {
    -moz-column-count: 1;
    -moz-column-gap: 0;
  }
}

/* authors */
address.vcard {
  font-style: normal;
  margin: 1em 0;
}

address.vcard .nameRole {
  font-weight: 700;
  margin-left: 0;
}
address.vcard .label {
  font-family: "Noto Sans",Arial,Helvetica,sans-serif;
  margin: 0.5em 0;
}
address.vcard .type {
  display: none;
}
.alternative-contact {
  margin: 1.5em 0 1em;
}
hr.addr {
  border-top: 1px dashed;
  margin: 0;
  color: #ddd;
  max-width: calc(100% - 16px);
}

/* temporary notes */
.rfcEditorRemove::before {
  position: absolute;
  top: 0.2em;
  right: 0.2em;
  padding: 0.2em;
  content: "The RFC Editor will remove this note";
  color: #9e2a00; /* Arlen: WCAG 2019 */
  background-color: #ffd; /* Arlen: WCAG 2019 */
}
.rfcEditorRemove {
  position: relative;
  padding-top: 1.8em;
  background-color: #ffd; /* Arlen: WCAG 2019 */
  border-radius: 3px;
}
.cref {
  background-color: #ffd; /* Arlen: WCAG 2019 */
  padding: 2px 4px;
}
.crefSource {
  font-style: italic;
}
/* alternative layout for smaller screens */
@media screen and (max-width: 1023px) {
  body {
    padding-top: 2em;
  }
  #title {
    padding: 1em 0;
  }
  h1 {
    font-size: 24px;
  }
  h2 {
    font-size: 20px;
    margin-top: -18px;  /* provide offset for in-page anchors */
    padding-top: 38px;
  }
  #identifiers dd {
    max-width: 60%;
  }
  #toc {
    position: fixed;
    z-index: 2;
    top: 0;
    right: 0;
    padding: 0;
    margin: 0;
    background-color: inherit;
    border-bottom: 1px solid #ccc;
  }
  #toc h2 {
    margin: -1px 0 0 0;
    padding: 4px 0 4px 6px;
    padding-right: 1em;
    min-width: 190px;
    font-size: 1.1em;
    text-align: right;
    background-color: #444;
    color: white;
    cursor: pointer;
  }
  #toc h2::before { /* css hamburger */
    float: right;
    position: relative;
    width: 1em;
    height: 1px;
    left: -164px;
    margin: 6px 0 0 0;
    background: white none repeat scroll 0 0;
    box-shadow: 0 4px 0 0 white, 0 8px 0 0 white;
    content: "";
  }
  #toc nav {
    display: none;
    padding: 0.5em 1em 1em;
    overflow: auto;
    height: calc(100vh - 48px);
    border-left: 1px solid #ddd;
  }
}

/* alternative layout for wide screens */
@media screen and (min-width: 1024px) {
  body {
    max-width: 724px;
    margin: 42px auto;
    padding-left: 1.5em;
    padding-right: 29em;
  }
  #toc {
    position: fixed;
    top: 42px;
    right: 42px;
    width: 25%;
    margin: 0;
    padding: 0 1em;
    z-index: 1;
  }
  #toc h2 {
    border-top: none;
    border-bottom: 1px solid #ddd;
    font-size: 1em;
    font-weight: normal;
    margin: 0;
    padding: 0.25em 1em 1em 0;
  }
  #toc nav {
    display: block;
    height: calc(90vh - 84px);
    bottom: 0;
    padding: 0.5em 0 0;
    overflow: auto;
  }
  img { /* future proofing */
    max-width: 100%;
    height: auto;
  }
}

/* pagination */
@media print {
  body {

    width: 100%;
  }
  p {
    orphans: 3;
    widows: 3;
  }
  #n-copyright-notice {
    border-bottom: none;
  }
  #toc, #n-introduction {
    page-break-before: always;
  }
  #toc {
    border-top: none;
    padding-top: 0;
  }
  figure, pre {
    page-break-inside: avoid;
  }
  figure {
    overflow: scroll;
  }
  h1, h2, h3, h4, h5, h6 {
    page-break-after: avoid;
  }
  h2+*, h3+*, h4+*, h5+*, h6+* {
    page-break-before: avoid;
  }
  pre {
    white-space: pre-wrap;
    word-wrap: break-word;
    font-size: 10pt;
  }
  table {
    border: 1px solid #ddd;
  }
  td {
    border-top: 1px solid #ddd;
  }
}

/* This is commented out here, as the string-set: doesn't
   pass W3C validation currently */
/*
.ears thead .left {
  string-set: ears-top-left content();
}

.ears thead .center {
  string-set: ears-top-center content();
}

.ears thead .right {
  string-set: ears-top-right content();
}

.ears tfoot .left {
  string-set: ears-bottom-left content();
}

.ears tfoot .center {
  string-set: ears-bottom-center content();
}

.ears tfoot .right {
  string-set: ears-bottom-right content();
}
*/

@page :first {
  padding-top: 0;
  @top-left {
    content: normal;
    border: none;
  }
  @top-center {
    content: normal;
    border: none;
  }
  @top-right {
    content: normal;
    border: none;
  }
}

@page {
  size: A4;
  margin-bottom: 45mm;
  padding-top: 20px;
  /* The follwing is commented out here, but set appropriately by in code, as
     the content depends on the document */
  /*
  @top-left {
    content: 'Internet-Draft';
    vertical-align: bottom;
    border-bottom: solid 1px #ccc;
  }
  @top-left {
    content: string(ears-top-left);
    vertical-align: bottom;
    border-bottom: solid 1px #ccc;
  }
  @top-center {
    content: string(ears-top-center);
    vertical-align: bottom;
    border-bottom: solid 1px #ccc;
  }
  @top-right {
    content: string(ears-top-right);
    vertical-align: bottom;
    border-bottom: solid 1px #ccc;
  }
  @bottom-left {
    content: string(ears-bottom-left);
    vertical-align: top;
    border-top: solid 1px #ccc;
  }
  @bottom-center {
    content: string(ears-bottom-center);
    vertical-align: top;
    border-top: solid 1px #ccc;
  }
  @bottom-right {
      content: '[Page ' counter(page) ']';
      vertical-align: top;
      border-top: solid 1px #ccc;
  }
  */

}

/* Changes introduced to fix issues found during implementation */
/* Make sure links are clickable even if overlapped by following H* */
a {
  z-index: 2;
}
/* Separate body from document info even without intervening H1 */
section {
  clear: both;
}


/* Top align author divs, to avoid names without organization dropping level with org names */
.author {
  vertical-align: top;
}

/* Leave room in document info to show Internet-Draft on one line */
#identifiers dt {
  width: 8em;
}

/* Don't waste quite as much whitespace between label and value in doc info */
#identifiers dd {
  margin-left: 1em;
}

/* Give floating toc a background color (needed when it's a div inside section */
#toc {
  background-color: white;
}

/* Make the collapsed ToC header render white on gray also when it's a link */
@media screen and (max-width: 1023px) {
  #toc h2 a,
  #toc h2 a:link,
  #toc h2 a:focus,
  #toc h2 a:hover,
  #toc a.toplink,
  #toc a.toplink:hover {
    color: white;
    background-color: #444;
    text-decoration: none;
  }
}

/* Give the bottom of the ToC some whitespace */
@media screen and (min-width: 1024px) {
  #toc {
    padding: 0 0 1em 1em;
  }
}

/* Style section numbers with more space between number and title */
.section-number {
  padding-right: 0.5em;
}

/* prevent monospace from becoming overly large */
tt, code, pre, code {
  font-size: 95%;
}

/* Fix the height/width aspect for ascii art*/
pre.sourcecode,
.art-text pre {
  line-height: 1.12;
}


/* Add styling for a link in the ToC that points to the top of the document */
a.toplink {
  float: right;
  margin-right: 0.5em;
}

/* Fix the dl styling to match the RFC 7992 attributes */
dl > dt,
dl.dlParallel > dt {
  float: left;
  margin-right: 1em;
}
dl.dlNewline > dt {
  float: none;
}

/* Provide styling for table cell text alignment */
table td.text-left,
table th.text-left {
  text-align: left;
}
table td.text-center,
table th.text-center {
  text-align: center;
}
table td.text-right,
table th.text-right {
  text-align: right;
}

/* Make the alternative author contact informatio look less like just another
   author, and group it closer with the primary author contact information */
.alternative-contact {
  margin: 0.5em 0 0.25em 0;
}
address .non-ascii {
  margin: 0 0 0 2em;
}

/* With it being possible to set tables with alignment
  left, center, and right, { width: 100%; } does not make sense */
table {
  width: auto;
}

/* Avoid reference text that sits in a block with very wide left margin,
   because of a long floating dt label.*/
.references dd {
  overflow: visible;
}

/* Control caption placement */
caption {
  caption-side: bottom;
}

/* Limit the width of the author address vcard, so names in right-to-left
   script don't end up on the other side of the page. */

address.vcard {
  max-width: 30em;
  margin-right: auto;
}

/* For address alignment dependent on LTR or RTL scripts */
address div.left {
  text-align: left;
}
address div.right {
  text-align: right;
}

/* Provide table alignment support.  We can't use the alignX classes above
   since they do unwanted things with caption and other styling. */
table.right {
 margin-left: auto;
 margin-right: 0;
}
table.center {
 margin-left: auto;
 margin-right: auto;
}
table.left {
 margin-left: 0;
 margin-right: auto;
}

/* Give the table caption label the same styling as the figcaption */
caption a[href] {
  color: #222;
}

@media print {
  .toplink {
    display: none;
  }

  /* avoid overwriting the top border line with the ToC header */
  #toc {
    padding-top: 1px;
  }

  /* Avoid page breaks inside dl and author address entries */
  .vcard {
    page-break-inside: avoid;
  }

}
/* Tweak the bcp14 keyword presentation */
.bcp14 {
  font-variant: small-caps;
  font-weight: bold;
  font-size: 0.9em;
}
/* Tweak the invisible space above H* in order not to overlay links in text above */
 h2 {
  margin-top: -18px;  /* provide offset for in-page anchors */
  padding-top: 31px;
 }
 h3 {
  margin-top: -18px;  /* provide offset for in-page anchors */
  padding-top: 24px;
 }
 h4 {
  margin-top: -18px;  /* provide offset for in-page anchors */
  padding-top: 24px;
 }
/* Float artwork pilcrow to the right */
@media screen {
  .artwork a.pilcrow {
    display: block;
    line-height: 0.7;
    margin-top: 0.15em;
  }
}
/* Make pilcrows on dd visible */
@media screen {
  dd:hover > a.pilcrow {
    visibility: visible;
  }
}
/* Make the placement of figcaption match that of a table's caption
   by removing the figure's added bottom margin */
.alignLeft.art-text,
.alignCenter.art-text,
.alignRight.art-text {
   margin-bottom: 0;
}
.alignLeft,
.alignCenter,
.alignRight {
  margin: 1em 0 0 0;
}
/* In print, the pilcrow won't show on hover, so prevent it from taking up space,
   possibly even requiring a new line */
@media print {
  a.pilcrow {
    display: none;
  }
}
/* Styling for the external metadata */
div#external-metadata {
  background-color: #eee;
  padding: 0.5em;
  margin-bottom: 0.5em;
  display: none;
}
div#internal-metadata {
  padding: 0.5em;                       /* to match the external-metadata padding */
}
/* Styling for title RFC Number */
h1#rfcnum {
  clear: both;
  margin: 0 0 -1em;
  padding: 1em 0 0 0;
}
/* Make .olPercent look the same as <ol><li> */
dl.olPercent > dd {
  margin-bottom: 0.25em;
  min-height: initial;
}
/* Give aside some styling to set it apart */
aside {
  border-left: 1px solid #ddd;
  margin: 1em 0 1em 2em;
  padding: 0.2em 2em;
}
aside > dl,
aside > ol,
aside > ul,
aside > table,
aside > p {
  margin-bottom: 0.5em;
}
/* Additional page break settings */
@media print {
  figcaption, table caption {
    page-break-before: avoid;
  }
}
/* Font size adjustments for print */
@media print {
  body  { font-size: 10pt;      line-height: normal; max-width: 96%; }
  h1    { font-size: 1.72em;    padding-top: 1.5em; } /* 1*1.2*1.2*1.2 */
  h2    { font-size: 1.44em;    padding-top: 1.5em; } /* 1*1.2*1.2 */
  h3    { font-size: 1.2em;     padding-top: 1.5em; } /* 1*1.2 */
  h4    { font-size: 1em;       padding-top: 1.5em; }
  h5, h6 { font-size: 1em;      margin: initial; padding: 0.5em 0 0.3em; }
}
/* Sourcecode margin in print, when there's no pilcrow */
@media print {
  .artwork,
  .sourcecode {
    margin-bottom: 1em;
  }
}
/* Avoid narrow tables forcing too narrow table captions, which may render badly */
table {
  min-width: 20em;
}
/* ol type a */
ol.type-a { list-style-type: lower-alpha; }
ol.type-A { list-style-type: upper-alpha; }
ol.type-i { list-style-type: lower-roman; }
ol.type-I { list-style-type: lower-roman; }
/* Apply the print table and row borders in general, on request from the RPC,
and increase the contrast between border and odd row background sligthtly */
table {
  border: 1px solid #ddd;
}
td {
  border-top: 1px solid #ddd;
}
tr:nth-child(2n+1) > td {
  background-color: #f8f8f8;
}
/* Use style rules to govern display of the TOC. */
@media screen and (max-width: 1023px) {
  #toc nav { display: none; }
  #toc.active nav { display: block; }
}
/* Add support for keepWithNext */
.keepWithNext {
  break-after: avoid-page;
  break-after: avoid-page;
}
/* Add support for keepWithPrevious */
.keepWithPrevious {
  break-before: avoid-page;
}
/* Change the approach to avoiding breaks inside artwork etc. */
figure, pre, table, .artwork, .sourcecode  {
  break-before: avoid-page;
  break-after: auto;
}
/* Avoid breaks between <dt> and <dd> */
dl {
  break-before: auto;
  break-inside: auto;
}
dt {
  break-before: auto;
  break-after: avoid-page;
}
dd {
  break-before: avoid-page;
  break-after: auto;
  orphans: 3;
  widows: 3
}
span.break, dd.break {
  margin-bottom: 0;
  min-height: 0;
  break-before: auto;
  break-inside: auto;
  break-after: auto;
}
/* Undo break-before ToC */
@media print {
  #toc {
    break-before: auto;
  }
}
/* Text in compact lists should not get extra bottim margin space,
   since that would makes the list not compact */
ul.compact p, .ulCompact p,
ol.compact p, .olCompact p {
 margin: 0;
}
/* But the list as a whole needs the extra space at the end */
section ul.compact,
section .ulCompact,
section ol.compact,
section .olCompact {
  margin-bottom: 1em;                    /* same as p not within ul.compact etc. */
}
/* The tt and code background above interferes with for instance table cell
   backgrounds.  Changed to something a bit more selective. */
tt, code {
  background-color: transparent;
}
p tt, p code, li tt, li code {
  background-color: #f8f8f8;
}
/* Tweak the pre margin -- 0px doesn't come out well */
pre {
   margin-top: 0.5px;
}
/* Tweak the comact list text */
ul.compact, .ulCompact,
ol.compact, .olCompact {
  line-height: normal;
}
/* Don't add top margin for nested lists */
li > ul, li > ol, li > dl,
dd > ul, dd > ol, dd > dl,
dl > dd > dl {
  margin-top: initial;
}</style>
<link href="rfc-local.css" rel="stylesheet" type="text/css">
<link href="https://dx.doi.org/10.17487/rfc8779" rel="alternate">
  <link href="urn:issn:2070-1721" rel="alternate">
  <link href="https://datatracker.ietf.org/doc/draft-ietf-pce-gmpls-pcep-extensions-16" rel="prev">
  </head>
<body>
<script src="https://www.rfc-editor.org/js/metadata.min.js"></script>
<table class="ears">
<thead><tr>
<td class="left">RFC 8779</td>
<td class="center">PCEP Extensions for GMPLS</td>
<td class="right">July 2020</td>
</tr></thead>
<tfoot><tr>
<td class="left">Margaria, et al.</td>
<td class="center">Standards Track</td>
<td class="right">[Page]</td>
</tr></tfoot>
</table>
<div id="external-metadata" class="document-information"></div>
<div id="internal-metadata" class="document-information">
<dl id="identifiers">
<dt class="label-stream">Stream:</dt>
<dd class="stream">Internet Engineering Task Force (IETF)</dd>
<dt class="label-rfc">RFC:</dt>
<dd class="rfc"><a href="https://www.rfc-editor.org/rfc/rfc8779" class="eref">8779</a></dd>
<dt class="label-category">Category:</dt>
<dd class="category">Standards Track</dd>
<dt class="label-published">Published:</dt>
<dd class="published">
<time datetime="2020-07" class="published">July 2020</time>
    </dd>
<dt class="label-issn">ISSN:</dt>
<dd class="issn">2070-1721</dd>
<dt class="label-authors">Authors:</dt>
<dd class="authors">
<div class="author">
      <div class="author-name">C. Margaria, <span class="editor">Ed.</span>
</div>
<div class="org">Juniper</div>
</div>
<div class="author">
      <div class="author-name">O. Gonzalez de Dios, <span class="editor">Ed.</span>
</div>
<div class="org">Telefonica Investigacion y Desarrollo</div>
</div>
<div class="author">
      <div class="author-name">F. Zhang, <span class="editor">Ed.</span>
</div>
<div class="org">Huawei Technologies</div>
</div>
</dd>
</dl>
</div>
<h1 id="rfcnum">RFC 8779</h1>
<h1 id="title">Path Computation Element Communication Protocol (PCEP) Extensions for GMPLS</h1>
<section id="section-abstract">
      <h2 id="abstract"><a href="#abstract" class="selfRef">Abstract</a></h2>
<p id="section-abstract-1">A Path Computation Element (PCE) provides path computation functions
      for Multiprotocol Label Switching (MPLS) and Generalized MPLS (GMPLS)
      networks. Additional requirements for GMPLS are identified in
      RFC 7025.<a href="#section-abstract-1" class="pilcrow">¶</a></p>
<p id="section-abstract-2"> 
        This memo provides extensions to the Path Computation Element
        Communication Protocol (PCEP) for the support of the GMPLS control plane
        to address those requirements.<a href="#section-abstract-2" class="pilcrow">¶</a></p>
</section>
<div id="status-of-memo">
<section id="section-boilerplate.1">
        <h2 id="name-status-of-this-memo">
<a href="#name-status-of-this-memo" class="section-name selfRef">Status of This Memo</a>
        </h2>
<p id="section-boilerplate.1-1">
            This is an Internet Standards Track document.<a href="#section-boilerplate.1-1" class="pilcrow">¶</a></p>
<p id="section-boilerplate.1-2">
            This document is a product of the Internet Engineering Task Force
            (IETF).  It represents the consensus of the IETF community.  It has
            received public review and has been approved for publication by
            the Internet Engineering Steering Group (IESG).  Further
            information on Internet Standards is available in Section 2 of 
            RFC 7841.<a href="#section-boilerplate.1-2" class="pilcrow">¶</a></p>
<p id="section-boilerplate.1-3">
            Information about the current status of this document, any
            errata, and how to provide feedback on it may be obtained at
            <span><a href="https://www.rfc-editor.org/info/rfc8779">https://www.rfc-editor.org/info/rfc8779</a></span>.<a href="#section-boilerplate.1-3" class="pilcrow">¶</a></p>
</section>
</div>
<div id="copyright">
<section id="section-boilerplate.2">
        <h2 id="name-copyright-notice">
<a href="#name-copyright-notice" class="section-name selfRef">Copyright Notice</a>
        </h2>
<p id="section-boilerplate.2-1">
            Copyright (c) 2020 IETF Trust and the persons identified as the
            document authors. All rights reserved.<a href="#section-boilerplate.2-1" class="pilcrow">¶</a></p>
<p id="section-boilerplate.2-2">
            This document is subject to BCP 78 and the IETF Trust's Legal
            Provisions Relating to IETF Documents
            (<span><a href="https://trustee.ietf.org/license-info">https://trustee.ietf.org/license-info</a></span>) in effect on the date of
            publication of this document. Please review these documents
            carefully, as they describe your rights and restrictions with
            respect to this document. Code Components extracted from this
            document must include Simplified BSD License text as described in
            Section 4.e of the Trust Legal Provisions and are provided without
            warranty as described in the Simplified BSD License.<a href="#section-boilerplate.2-2" class="pilcrow">¶</a></p>
</section>
</div>
<div id="toc">
<section id="section-toc.1">
        <a href="#" onclick="scroll(0,0)" class="toplink">▲</a><h2 id="name-table-of-contents">
<a href="#name-table-of-contents" class="section-name selfRef">Table of Contents</a>
        </h2>
<nav class="toc"><ul class="ulEmpty compact toc">
<li class="ulEmpty compact toc" id="section-toc.1-1.1">
            <p id="section-toc.1-1.1.1"><a href="#section-1" class="xref">1</a>.  <a href="#name-introduction" class="xref">Introduction</a><a href="#section-toc.1-1.1.1" class="pilcrow">¶</a></p>
<ul class="ulEmpty compact toc">
<li class="ulEmpty compact toc" id="section-toc.1-1.1.2.1">
                <p id="section-toc.1-1.1.2.1.1" class="keepWithNext"><a href="#section-1.1" class="xref">1.1</a>.  <a href="#name-terminology" class="xref">Terminology</a><a href="#section-toc.1-1.1.2.1.1" class="pilcrow">¶</a></p>
</li>
              <li class="ulEmpty compact toc" id="section-toc.1-1.1.2.2">
                <p id="section-toc.1-1.1.2.2.1" class="keepWithNext"><a href="#section-1.2" class="xref">1.2</a>.  <a href="#name-pcep-requirements-for-gmpls" class="xref">PCEP Requirements for GMPLS</a><a href="#section-toc.1-1.1.2.2.1" class="pilcrow">¶</a></p>
</li>
              <li class="ulEmpty compact toc" id="section-toc.1-1.1.2.3">
                <p id="section-toc.1-1.1.2.3.1"><a href="#section-1.3" class="xref">1.3</a>.  <a href="#name-requirements-applicability" class="xref">Requirements Applicability</a><a href="#section-toc.1-1.1.2.3.1" class="pilcrow">¶</a></p>
<ul class="ulEmpty compact toc">
<li class="ulEmpty compact toc" id="section-toc.1-1.1.2.3.2.1">
                    <p id="section-toc.1-1.1.2.3.2.1.1" class="keepWithNext"><a href="#section-1.3.1" class="xref">1.3.1</a>.  <a href="#name-requirements-on-the-path-co" class="xref">Requirements on the Path Computation Request</a><a href="#section-toc.1-1.1.2.3.2.1.1" class="pilcrow">¶</a></p>
</li>
                  <li class="ulEmpty compact toc" id="section-toc.1-1.1.2.3.2.2">
                    <p id="section-toc.1-1.1.2.3.2.2.1"><a href="#section-1.3.2" class="xref">1.3.2</a>.  <a href="#name-requirements-on-the-path-com" class="xref">Requirements on the Path Computation Response</a><a href="#section-toc.1-1.1.2.3.2.2.1" class="pilcrow">¶</a></p>
</li>
                </ul>
</li>
              <li class="ulEmpty compact toc" id="section-toc.1-1.1.2.4">
                <p id="section-toc.1-1.1.2.4.1"><a href="#section-1.4" class="xref">1.4</a>.  <a href="#name-existing-support-and-limita" class="xref">Existing Support and Limitations for GMPLS in Base PCEP Objects</a><a href="#section-toc.1-1.1.2.4.1" class="pilcrow">¶</a></p>
</li>
            </ul>
</li>
          <li class="ulEmpty compact toc" id="section-toc.1-1.2">
            <p id="section-toc.1-1.2.1"><a href="#section-2" class="xref">2</a>.  <a href="#name-pcep-objects-and-extensions" class="xref">PCEP Objects and Extensions</a><a href="#section-toc.1-1.2.1" class="pilcrow">¶</a></p>
<ul class="ulEmpty compact toc">
<li class="ulEmpty compact toc" id="section-toc.1-1.2.2.1">
                <p id="section-toc.1-1.2.2.1.1"><a href="#section-2.1" class="xref">2.1</a>.  <a href="#name-gmpls-capability-advertisem" class="xref">GMPLS Capability Advertisement</a><a href="#section-toc.1-1.2.2.1.1" class="pilcrow">¶</a></p>
<ul class="ulEmpty compact toc">
<li class="ulEmpty compact toc" id="section-toc.1-1.2.2.1.2.1">
                    <p id="section-toc.1-1.2.2.1.2.1.1"><a href="#section-2.1.1" class="xref">2.1.1</a>.  <a href="#name-gmpls-computation-tlv-in-th" class="xref">GMPLS Computation TLV in the Existing PCE Discovery Protocol</a><a href="#section-toc.1-1.2.2.1.2.1.1" class="pilcrow">¶</a></p>
</li>
                  <li class="ulEmpty compact toc" id="section-toc.1-1.2.2.1.2.2">
                    <p id="section-toc.1-1.2.2.1.2.2.1"><a href="#section-2.1.2" class="xref">2.1.2</a>.  <a href="#name-open-object-extension-gmpls" class="xref">OPEN Object Extension GMPLS-CAPABILITY TLV</a><a href="#section-toc.1-1.2.2.1.2.2.1" class="pilcrow">¶</a></p>
</li>
                </ul>
</li>
              <li class="ulEmpty compact toc" id="section-toc.1-1.2.2.2">
                <p id="section-toc.1-1.2.2.2.1"><a href="#section-2.2" class="xref">2.2</a>.  <a href="#name-rp-object-extension" class="xref">RP Object Extension</a><a href="#section-toc.1-1.2.2.2.1" class="pilcrow">¶</a></p>
</li>
              <li class="ulEmpty compact toc" id="section-toc.1-1.2.2.3">
                <p id="section-toc.1-1.2.2.3.1"><a href="#section-2.3" class="xref">2.3</a>.  <a href="#name-bandwidth-object-extensions" class="xref">BANDWIDTH Object Extensions</a><a href="#section-toc.1-1.2.2.3.1" class="pilcrow">¶</a></p>
</li>
              <li class="ulEmpty compact toc" id="section-toc.1-1.2.2.4">
                <p id="section-toc.1-1.2.2.4.1"><a href="#section-2.4" class="xref">2.4</a>.  <a href="#name-load-balancing-object-exten" class="xref">LOAD-BALANCING Object Extensions</a><a href="#section-toc.1-1.2.2.4.1" class="pilcrow">¶</a></p>
</li>
              <li class="ulEmpty compact toc" id="section-toc.1-1.2.2.5">
                <p id="section-toc.1-1.2.2.5.1"><a href="#section-2.5" class="xref">2.5</a>.  <a href="#name-end-points-object-extension" class="xref">END-POINTS Object Extensions</a><a href="#section-toc.1-1.2.2.5.1" class="pilcrow">¶</a></p>
<ul class="ulEmpty compact toc">
<li class="ulEmpty compact toc" id="section-toc.1-1.2.2.5.2.1">
                    <p id="section-toc.1-1.2.2.5.2.1.1"><a href="#section-2.5.1" class="xref">2.5.1</a>.  <a href="#name-generalized-endpoint-object" class="xref">Generalized Endpoint Object Type</a><a href="#section-toc.1-1.2.2.5.2.1.1" class="pilcrow">¶</a></p>
</li>
                  <li class="ulEmpty compact toc" id="section-toc.1-1.2.2.5.2.2">
                    <p id="section-toc.1-1.2.2.5.2.2.1"><a href="#section-2.5.2" class="xref">2.5.2</a>.  <a href="#name-end-points-tlv-extensions" class="xref">END-POINTS TLV Extensions</a><a href="#section-toc.1-1.2.2.5.2.2.1" class="pilcrow">¶</a></p>
</li>
                </ul>
</li>
              <li class="ulEmpty compact toc" id="section-toc.1-1.2.2.6">
                <p id="section-toc.1-1.2.2.6.1"><a href="#section-2.6" class="xref">2.6</a>.  <a href="#name-iro-extension" class="xref">IRO Extension</a><a href="#section-toc.1-1.2.2.6.1" class="pilcrow">¶</a></p>
</li>
              <li class="ulEmpty compact toc" id="section-toc.1-1.2.2.7">
                <p id="section-toc.1-1.2.2.7.1"><a href="#section-2.7" class="xref">2.7</a>.  <a href="#name-xro-extension" class="xref">XRO Extension</a><a href="#section-toc.1-1.2.2.7.1" class="pilcrow">¶</a></p>
</li>
              <li class="ulEmpty compact toc" id="section-toc.1-1.2.2.8">
                <p id="section-toc.1-1.2.2.8.1"><a href="#section-2.8" class="xref">2.8</a>.  <a href="#name-lspa-extensions" class="xref">LSPA Extensions</a><a href="#section-toc.1-1.2.2.8.1" class="pilcrow">¶</a></p>
</li>
              <li class="ulEmpty compact toc" id="section-toc.1-1.2.2.9">
                <p id="section-toc.1-1.2.2.9.1"><a href="#section-2.9" class="xref">2.9</a>.  <a href="#name-no-path-object-extension" class="xref">NO-PATH Object Extension</a><a href="#section-toc.1-1.2.2.9.1" class="pilcrow">¶</a></p>
<ul class="ulEmpty compact toc">
<li class="ulEmpty compact toc" id="section-toc.1-1.2.2.9.2.1">
                    <p id="section-toc.1-1.2.2.9.2.1.1"><a href="#section-2.9.1" class="xref">2.9.1</a>.  <a href="#name-extensions-to-no-path-vecto" class="xref">Extensions to NO-PATH-VECTOR TLV</a><a href="#section-toc.1-1.2.2.9.2.1.1" class="pilcrow">¶</a></p>
</li>
                </ul>
</li>
            </ul>
</li>
          <li class="ulEmpty compact toc" id="section-toc.1-1.3">
            <p id="section-toc.1-1.3.1"><a href="#section-3" class="xref">3</a>.  <a href="#name-additional-error-types-and-" class="xref">Additional Error-Types and Error-Values Defined</a><a href="#section-toc.1-1.3.1" class="pilcrow">¶</a></p>
</li>
          <li class="ulEmpty compact toc" id="section-toc.1-1.4">
            <p id="section-toc.1-1.4.1"><a href="#section-4" class="xref">4</a>.  <a href="#name-manageability-consideration" class="xref">Manageability Considerations</a><a href="#section-toc.1-1.4.1" class="pilcrow">¶</a></p>
<ul class="ulEmpty compact toc">
<li class="ulEmpty compact toc" id="section-toc.1-1.4.2.1">
                <p id="section-toc.1-1.4.2.1.1"><a href="#section-4.1" class="xref">4.1</a>.  <a href="#name-control-of-function-through" class="xref">Control of Function through Configuration and Policy</a><a href="#section-toc.1-1.4.2.1.1" class="pilcrow">¶</a></p>
</li>
              <li class="ulEmpty compact toc" id="section-toc.1-1.4.2.2">
                <p id="section-toc.1-1.4.2.2.1"><a href="#section-4.2" class="xref">4.2</a>.  <a href="#name-information-and-data-models" class="xref">Information and Data Models</a><a href="#section-toc.1-1.4.2.2.1" class="pilcrow">¶</a></p>
</li>
              <li class="ulEmpty compact toc" id="section-toc.1-1.4.2.3">
                <p id="section-toc.1-1.4.2.3.1"><a href="#section-4.3" class="xref">4.3</a>.  <a href="#name-liveness-detection-and-moni" class="xref">Liveness Detection and Monitoring</a><a href="#section-toc.1-1.4.2.3.1" class="pilcrow">¶</a></p>
</li>
              <li class="ulEmpty compact toc" id="section-toc.1-1.4.2.4">
                <p id="section-toc.1-1.4.2.4.1"><a href="#section-4.4" class="xref">4.4</a>.  <a href="#name-verifying-correct-operation" class="xref">Verifying Correct Operation</a><a href="#section-toc.1-1.4.2.4.1" class="pilcrow">¶</a></p>
</li>
              <li class="ulEmpty compact toc" id="section-toc.1-1.4.2.5">
                <p id="section-toc.1-1.4.2.5.1"><a href="#section-4.5" class="xref">4.5</a>.  <a href="#name-requirements-on-other-proto" class="xref">Requirements on Other Protocols and Functional Components</a><a href="#section-toc.1-1.4.2.5.1" class="pilcrow">¶</a></p>
</li>
              <li class="ulEmpty compact toc" id="section-toc.1-1.4.2.6">
                <p id="section-toc.1-1.4.2.6.1"><a href="#section-4.6" class="xref">4.6</a>.  <a href="#name-impact-on-network-operation" class="xref">Impact on Network Operation</a><a href="#section-toc.1-1.4.2.6.1" class="pilcrow">¶</a></p>
</li>
            </ul>
</li>
          <li class="ulEmpty compact toc" id="section-toc.1-1.5">
            <p id="section-toc.1-1.5.1"><a href="#section-5" class="xref">5</a>.  <a href="#name-iana-considerations" class="xref">IANA Considerations</a><a href="#section-toc.1-1.5.1" class="pilcrow">¶</a></p>
<ul class="ulEmpty compact toc">
<li class="ulEmpty compact toc" id="section-toc.1-1.5.2.1">
                <p id="section-toc.1-1.5.2.1.1"><a href="#section-5.1" class="xref">5.1</a>.  <a href="#name-pcep-objects" class="xref">PCEP Objects</a><a href="#section-toc.1-1.5.2.1.1" class="pilcrow">¶</a></p>
</li>
              <li class="ulEmpty compact toc" id="section-toc.1-1.5.2.2">
                <p id="section-toc.1-1.5.2.2.1"><a href="#section-5.2" class="xref">5.2</a>.  <a href="#name-endpoint-type-field-in-the-" class="xref">Endpoint Type Field in the Generalized END-POINTS Object</a><a href="#section-toc.1-1.5.2.2.1" class="pilcrow">¶</a></p>
</li>
              <li class="ulEmpty compact toc" id="section-toc.1-1.5.2.3">
                <p id="section-toc.1-1.5.2.3.1"><a href="#section-5.3" class="xref">5.3</a>.  <a href="#name-new-pcep-tlvs" class="xref">New PCEP TLVs</a><a href="#section-toc.1-1.5.2.3.1" class="pilcrow">¶</a></p>
</li>
              <li class="ulEmpty compact toc" id="section-toc.1-1.5.2.4">
                <p id="section-toc.1-1.5.2.4.1"><a href="#section-5.4" class="xref">5.4</a>.  <a href="#name-rp-object-flag-field" class="xref">RP Object Flag Field</a><a href="#section-toc.1-1.5.2.4.1" class="pilcrow">¶</a></p>
</li>
              <li class="ulEmpty compact toc" id="section-toc.1-1.5.2.5">
                <p id="section-toc.1-1.5.2.5.1"><a href="#section-5.5" class="xref">5.5</a>.  <a href="#name-new-pcep-error-codes" class="xref">New PCEP Error Codes</a><a href="#section-toc.1-1.5.2.5.1" class="pilcrow">¶</a></p>
</li>
              <li class="ulEmpty compact toc" id="section-toc.1-1.5.2.6">
                <p id="section-toc.1-1.5.2.6.1"><a href="#section-5.6" class="xref">5.6</a>.  <a href="#name-new-bits-in-no-path-vector-" class="xref">New Bits in NO-PATH-VECTOR TLV</a><a href="#section-toc.1-1.5.2.6.1" class="pilcrow">¶</a></p>
</li>
              <li class="ulEmpty compact toc" id="section-toc.1-1.5.2.7">
                <p id="section-toc.1-1.5.2.7.1"><a href="#section-5.7" class="xref">5.7</a>.  <a href="#name-new-subobject-for-the-inclu" class="xref">New Subobject for the Include Route Object</a><a href="#section-toc.1-1.5.2.7.1" class="pilcrow">¶</a></p>
</li>
              <li class="ulEmpty compact toc" id="section-toc.1-1.5.2.8">
                <p id="section-toc.1-1.5.2.8.1"><a href="#section-5.8" class="xref">5.8</a>.  <a href="#name-new-subobject-for-the-exclu" class="xref">New Subobject for the Exclude Route Object</a><a href="#section-toc.1-1.5.2.8.1" class="pilcrow">¶</a></p>
</li>
              <li class="ulEmpty compact toc" id="section-toc.1-1.5.2.9">
                <p id="section-toc.1-1.5.2.9.1"><a href="#section-5.9" class="xref">5.9</a>.  <a href="#name-new-gmpls-capability-tlv-fl" class="xref">New GMPLS-CAPABILITY TLV Flag Field</a><a href="#section-toc.1-1.5.2.9.1" class="pilcrow">¶</a></p>
</li>
            </ul>
</li>
          <li class="ulEmpty compact toc" id="section-toc.1-1.6">
            <p id="section-toc.1-1.6.1"><a href="#section-6" class="xref">6</a>.  <a href="#name-security-considerations" class="xref">Security Considerations</a><a href="#section-toc.1-1.6.1" class="pilcrow">¶</a></p>
</li>
          <li class="ulEmpty compact toc" id="section-toc.1-1.7">
            <p id="section-toc.1-1.7.1"><a href="#section-7" class="xref">7</a>.  <a href="#name-references" class="xref">References</a><a href="#section-toc.1-1.7.1" class="pilcrow">¶</a></p>
<ul class="ulEmpty compact toc">
<li class="ulEmpty compact toc" id="section-toc.1-1.7.2.1">
                <p id="section-toc.1-1.7.2.1.1"><a href="#section-7.1" class="xref">7.1</a>.  <a href="#name-normative-references" class="xref">Normative References</a><a href="#section-toc.1-1.7.2.1.1" class="pilcrow">¶</a></p>
</li>
              <li class="ulEmpty compact toc" id="section-toc.1-1.7.2.2">
                <p id="section-toc.1-1.7.2.2.1"><a href="#section-7.2" class="xref">7.2</a>.  <a href="#name-informative-references" class="xref">Informative References</a><a href="#section-toc.1-1.7.2.2.1" class="pilcrow">¶</a></p>
</li>
            </ul>
</li>
          <li class="ulEmpty compact toc" id="section-toc.1-1.8">
            <p id="section-toc.1-1.8.1"><a href="#section-appendix.a" class="xref">Appendix A</a>.  <a href="#name-load-balancing-usage-for-sd" class="xref">LOAD-BALANCING Usage for SDH Virtual Concatenation</a><a href="#section-toc.1-1.8.1" class="pilcrow">¶</a></p>
</li>
          <li class="ulEmpty compact toc" id="section-toc.1-1.9">
            <p id="section-toc.1-1.9.1"><a href="#section-appendix.b" class="xref"></a><a href="#name-acknowledgments" class="xref">Acknowledgments</a><a href="#section-toc.1-1.9.1" class="pilcrow">¶</a></p>
</li>
          <li class="ulEmpty compact toc" id="section-toc.1-1.10">
            <p id="section-toc.1-1.10.1"><a href="#section-appendix.c" class="xref"></a><a href="#name-contributors" class="xref">Contributors</a><a href="#section-toc.1-1.10.1" class="pilcrow">¶</a></p>
</li>
          <li class="ulEmpty compact toc" id="section-toc.1-1.11">
            <p id="section-toc.1-1.11.1"><a href="#section-appendix.d" class="xref"></a><a href="#name-authors-addresses" class="xref">Authors' Addresses</a><a href="#section-toc.1-1.11.1" class="pilcrow">¶</a></p>
</li>
        </ul>
</nav>
</section>
</div>
<section id="section-1">
      <h2 id="name-introduction">
<a href="#section-1" class="section-number selfRef">1. </a><a href="#name-introduction" class="section-name selfRef">Introduction</a>
      </h2>
<p id="section-1-1">Although the PCE architecture and framework for both MPLS and GMPLS networks are defined in <span>[<a href="#RFC4655" class="xref">RFC4655</a>]</span>, most pre-existing PCEP RFCs, such as <span>[<a href="#RFC5440" class="xref">RFC5440</a>]</span>, <span>[<a href="#RFC5521" class="xref">RFC5521</a>]</span>, <span>[<a href="#RFC5541" class="xref">RFC5541</a>]</span>, and <span>[<a href="#RFC5520" class="xref">RFC5520</a>]</span>, are focused on MPLS networks and do not cover the wide range of GMPLS networks. This document complements these RFCs by addressing the extensions required for GMPLS applications and routing requests, for example, for Optical Transport Networks (OTNs) and Wavelength Switched Optical Networks (WSONs).<a href="#section-1-1" class="pilcrow">¶</a></p>
<p id="section-1-2">The functional requirements to be addressed by the PCEP
      extensions to support these applications are fully described in <span>[<a href="#RFC7025" class="xref">RFC7025</a>]</span> and <span>[<a href="#RFC7449" class="xref">RFC7449</a>]</span>.<a href="#section-1-2" class="pilcrow">¶</a></p>
<section id="section-1.1">
        <h3 id="name-terminology">
<a href="#section-1.1" class="section-number selfRef">1.1. </a><a href="#name-terminology" class="section-name selfRef">Terminology</a>
        </h3>
<p id="section-1.1-1">  
 This document uses terminologies from the PCE architecture document <span>[<a href="#RFC4655" class="xref">RFC4655</a>]</span>; the PCEP documents including <span>[<a href="#RFC5440" class="xref">RFC5440</a>]</span>, <span>[<a href="#RFC5521" class="xref">RFC5521</a>]</span>, <span>[<a href="#RFC5541" class="xref">RFC5541</a>]</span>, <span>[<a href="#RFC5520" class="xref">RFC5520</a>]</span>, <span>[<a href="#RFC7025" class="xref">RFC7025</a>]</span>, and <span>[<a href="#RFC7449" class="xref">RFC7449</a>]</span>; 
 and the GMPLS documents such as <span>[<a href="#RFC3471" class="xref">RFC3471</a>]</span>, <span>[<a href="#RFC3473" class="xref">RFC3473</a>]</span>, and so
                on.  Note that the reader is expected to be familiar
                with these documents.
                The following abbreviations are used in this document:<a href="#section-1.1-1" class="pilcrow">¶</a></p>
<span class="break"></span><dl class="dlParallel" id="section-1.1-2">
          <dt id="section-1.1-2.1">ERO:</dt>
          <dd style="margin-left: 5.0em" id="section-1.1-2.2">Explicit Route Object<a href="#section-1.1-2.2" class="pilcrow">¶</a>
</dd>
          <dd class="break"></dd>
<dt id="section-1.1-2.3">IRO:</dt>
          <dd style="margin-left: 5.0em" id="section-1.1-2.4">Include Route Object<a href="#section-1.1-2.4" class="pilcrow">¶</a>
</dd>
          <dd class="break"></dd>
<dt id="section-1.1-2.5">L2SC:</dt>
          <dd style="margin-left: 5.0em" id="section-1.1-2.6">Layer 2 Switch Capable <span>[<a href="#RFC3471" class="xref">RFC3471</a>]</span><a href="#section-1.1-2.6" class="pilcrow">¶</a>
</dd>
          <dd class="break"></dd>
<dt id="section-1.1-2.7">LSC:</dt>
          <dd style="margin-left: 5.0em" id="section-1.1-2.8">Lambda Switch Capable <span>[<a href="#RFC3471" class="xref">RFC3471</a>]</span><a href="#section-1.1-2.8" class="pilcrow">¶</a>
</dd>
          <dd class="break"></dd>
<dt id="section-1.1-2.9">LSP:</dt>
          <dd style="margin-left: 5.0em" id="section-1.1-2.10">Label Switched Path<a href="#section-1.1-2.10" class="pilcrow">¶</a>
</dd>
          <dd class="break"></dd>
<dt id="section-1.1-2.11">LSPA:</dt>
          <dd style="margin-left: 5.0em" id="section-1.1-2.12">LSP Attribute<a href="#section-1.1-2.12" class="pilcrow">¶</a>
</dd>
          <dd class="break"></dd>
<dt id="section-1.1-2.13">MEF:</dt>
          <dd style="margin-left: 5.0em" id="section-1.1-2.14">Metro Ethernet Forum<a href="#section-1.1-2.14" class="pilcrow">¶</a>
</dd>
          <dd class="break"></dd>
<dt id="section-1.1-2.15">MT:</dt>
          <dd style="margin-left: 5.0em" id="section-1.1-2.16">Multiplier <span>[<a href="#RFC4328" class="xref">RFC4328</a>]</span> <span>[<a href="#RFC4606" class="xref">RFC4606</a>]</span><a href="#section-1.1-2.16" class="pilcrow">¶</a>
</dd>
          <dd class="break"></dd>
<dt id="section-1.1-2.17">NCC:</dt>
          <dd style="margin-left: 5.0em" id="section-1.1-2.18">Number of Contiguous Components <span>[<a href="#RFC4606" class="xref">RFC4606</a>]</span><a href="#section-1.1-2.18" class="pilcrow">¶</a>
</dd>
          <dd class="break"></dd>
<dt id="section-1.1-2.19">NVC:</dt>
          <dd style="margin-left: 5.0em" id="section-1.1-2.20">Number of Virtual Components <span>[<a href="#RFC4328" class="xref">RFC4328</a>]</span> <span>[<a href="#RFC4606" class="xref">RFC4606</a>]</span><a href="#section-1.1-2.20" class="pilcrow">¶</a>
</dd>
          <dd class="break"></dd>
<dt id="section-1.1-2.21">ODU:</dt>
          <dd style="margin-left: 5.0em" id="section-1.1-2.22">Optical Data Unit <span>[<a href="#G.709-v3" class="xref">G.709-v3</a>]</span><a href="#section-1.1-2.22" class="pilcrow">¶</a>
</dd>
          <dd class="break"></dd>
<dt id="section-1.1-2.23">OTN:</dt>
          <dd style="margin-left: 5.0em" id="section-1.1-2.24">Optical Transport Network <span>[<a href="#G.709-v3" class="xref">G.709-v3</a>]</span><a href="#section-1.1-2.24" class="pilcrow">¶</a>
</dd>
          <dd class="break"></dd>
<dt id="section-1.1-2.25">P2MP:</dt>
          <dd style="margin-left: 5.0em" id="section-1.1-2.26">Point-to-Multipoint<a href="#section-1.1-2.26" class="pilcrow">¶</a>
</dd>
          <dd class="break"></dd>
<dt id="section-1.1-2.27">PCC:</dt>
          <dd style="margin-left: 5.0em" id="section-1.1-2.28">Path Computation Client<a href="#section-1.1-2.28" class="pilcrow">¶</a>
</dd>
          <dd class="break"></dd>
<dt id="section-1.1-2.29">PCRep:</dt>
          <dd style="margin-left: 5.0em" id="section-1.1-2.30">Path Computation Reply  <span>[<a href="#RFC5440" class="xref">RFC5440</a>]</span><a href="#section-1.1-2.30" class="pilcrow">¶</a>
</dd>
          <dd class="break"></dd>
<dt id="section-1.1-2.31">PCReq:</dt>
          <dd style="margin-left: 5.0em" id="section-1.1-2.32">Path Computation Request <span>[<a href="#RFC5440" class="xref">RFC5440</a>]</span><a href="#section-1.1-2.32" class="pilcrow">¶</a>
</dd>
          <dd class="break"></dd>
<dt id="section-1.1-2.33">RCC:</dt>
          <dd style="margin-left: 5.0em" id="section-1.1-2.34">Requested Contiguous Concatenation <span>[<a href="#RFC4606" class="xref">RFC4606</a>]</span><a href="#section-1.1-2.34" class="pilcrow">¶</a>
</dd>
          <dd class="break"></dd>
<dt id="section-1.1-2.35">RRO:</dt>
          <dd style="margin-left: 5.0em" id="section-1.1-2.36">Record Route Object<a href="#section-1.1-2.36" class="pilcrow">¶</a>
</dd>
          <dd class="break"></dd>
<dt id="section-1.1-2.37">RSVP-TE:</dt>
          <dd style="margin-left: 5.0em" id="section-1.1-2.38">Resource Reservation Protocol - Traffic  Engineering<a href="#section-1.1-2.38" class="pilcrow">¶</a>
</dd>
          <dd class="break"></dd>
<dt id="section-1.1-2.39">SDH:</dt>
          <dd style="margin-left: 5.0em" id="section-1.1-2.40">Synchronous Digital Hierarchy<a href="#section-1.1-2.40" class="pilcrow">¶</a>
</dd>
          <dd class="break"></dd>
<dt id="section-1.1-2.41">SONET:</dt>
          <dd style="margin-left: 5.0em" id="section-1.1-2.42">Synchronous Optical Network<a href="#section-1.1-2.42" class="pilcrow">¶</a>
</dd>
          <dd class="break"></dd>
<dt id="section-1.1-2.43">SRLG:</dt>
          <dd style="margin-left: 5.0em" id="section-1.1-2.44">Shared Risk Link Group<a href="#section-1.1-2.44" class="pilcrow">¶</a>
</dd>
          <dd class="break"></dd>
<dt id="section-1.1-2.45">SSON:</dt>
          <dd style="margin-left: 5.0em" id="section-1.1-2.46">Spectrum-Switched Optical Network<a href="#section-1.1-2.46" class="pilcrow">¶</a>
</dd>
          <dd class="break"></dd>
<dt id="section-1.1-2.47">TDM:</dt>
          <dd style="margin-left: 5.0em" id="section-1.1-2.48">Time-Division Multiplex Capable <span>[<a href="#RFC3471" class="xref">RFC3471</a>]</span><a href="#section-1.1-2.48" class="pilcrow">¶</a>
</dd>
          <dd class="break"></dd>
<dt id="section-1.1-2.49">TE-LSP:</dt>
          <dd style="margin-left: 5.0em" id="section-1.1-2.50">Traffic Engineered LSP<a href="#section-1.1-2.50" class="pilcrow">¶</a>
</dd>
          <dd class="break"></dd>
<dt id="section-1.1-2.51">XRO:</dt>
          <dd style="margin-left: 5.0em" id="section-1.1-2.52">Exclude Route Object<a href="#section-1.1-2.52" class="pilcrow">¶</a>
</dd>
        <dd class="break"></dd>
</dl>
<p id="section-1.1-3">  
  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>", "<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
         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, they appear in all capitals, as shown here.<a href="#section-1.1-3" class="pilcrow">¶</a></p>
</section>
<section id="section-1.2">
        <h3 id="name-pcep-requirements-for-gmpls">
<a href="#section-1.2" class="section-number selfRef">1.2. </a><a href="#name-pcep-requirements-for-gmpls" class="section-name selfRef">PCEP Requirements for GMPLS</a>
        </h3>
<p id="section-1.2-1"><span>[<a href="#RFC7025" class="xref">RFC7025</a>]</span> describes the set of PCEP
        requirements that support GMPLS TE-LSPs. This document assumes a
        significant familiarity with <span>[<a href="#RFC7025" class="xref">RFC7025</a>]</span>
        and existing PCEP extensions.  As a short overview, those requirements
        can be broken down into the following categories.<a href="#section-1.2-1" class="pilcrow">¶</a></p>
<ul class="normal">
<li class="normal" id="section-1.2-2.1">Which data flow is switched by the LSP: a combination
            of a switching type (for instance, 
            L2SC or TDM), an LSP encoding
            type (e.g., Ethernet, SONET/SDH), and sometimes the signal
            type (e.g., in case of a TDM or an LSC switching capability).<a href="#section-1.2-2.1" class="pilcrow">¶</a>
</li>
          <li class="normal" id="section-1.2-2.2">Data-flow-specific traffic parameters, which are
            technology specific. For instance, in SDH/SONET and OTN networks <span>[<a href="#G.709-v3" class="xref">G.709-v3</a>]</span>, the concatenation type and the concatenation number have an influence on the switched data and on which link it can be supported.<a href="#section-1.2-2.2" class="pilcrow">¶</a>
</li>
          <li class="normal" id="section-1.2-2.3">Support for asymmetric bandwidth requests.<a href="#section-1.2-2.3" class="pilcrow">¶</a>
</li>
          <li class="normal" id="section-1.2-2.4">Support for unnumbered interface identifiers, as
            defined in <span>[<a href="#RFC3477" class="xref">RFC3477</a>]</span>.<a href="#section-1.2-2.4" class="pilcrow">¶</a>
</li>
          <li class="normal" id="section-1.2-2.5">Label information and technology-specific label(s) such
            as wavelength labels as defined in <span>[<a href="#RFC6205" class="xref">RFC6205</a>]</span>. A PCC should also be able to
            specify a label restriction similar to the one supported
            by RSVP-TE in  <span>[<a href="#RFC3473" class="xref">RFC3473</a>]</span>.<a href="#section-1.2-2.5" class="pilcrow">¶</a>
</li>
          <li class="normal" id="section-1.2-2.6">Ability to indicate the requested granularity for the
            path ERO: node, link, or label. This is to allow the use of the explicit label control feature of RSVP-TE.<a href="#section-1.2-2.6" class="pilcrow">¶</a>
</li>
        </ul>
<p id="section-1.2-3">
          The requirements of <span>[<a href="#RFC7025" class="xref">RFC7025</a>]</span> apply to several objects conveyed by PCEP; this is described in <a href="#requirement-map" class="xref">Section 1.3</a>.          
          Some of the requirements of <span>[<a href="#RFC7025" class="xref">RFC7025</a>]</span> are
          already supported in existing documents, as described in
          <a href="#existing-support" class="xref">Section 1.4</a>.<a href="#section-1.2-3" class="pilcrow">¶</a></p>
<p id="section-1.2-4">
        This document describes a set of PCEP
        extensions, including new object types, TLVs, encodings, error
        codes, and procedures, in order to fulfill the aforementioned
        requirements not covered in existing RFCs.<a href="#section-1.2-4" class="pilcrow">¶</a></p>
</section>
<div id="requirement-map">
<section id="section-1.3">
        <h3 id="name-requirements-applicability">
<a href="#section-1.3" class="section-number selfRef">1.3. </a><a href="#name-requirements-applicability" class="section-name selfRef">Requirements Applicability</a>
        </h3>
<p id="section-1.3-1"> This section follows the organization of <span>[<a href="#RFC7025" class="xref">RFC7025</a>], <a href="https://www.rfc-editor.org/rfc/rfc7025#section-3" class="relref">Section 3</a></span> and indicates, for each requirement, the affected piece of information carried by PCEP and its scope.<a href="#section-1.3-1" class="pilcrow">¶</a></p>
<section id="section-1.3.1">
          <h4 id="name-requirements-on-the-path-co">
<a href="#section-1.3.1" class="section-number selfRef">1.3.1. </a><a href="#name-requirements-on-the-path-co" class="section-name selfRef">Requirements on the Path Computation Request</a>
          </h4>
<span class="break"></span><dl class="olPercent" id="section-1.3.1-1">
            <dt>(1)</dt>
<dd id="section-1.3.1-1.1">Switching capability/type: As described in <span>[<a href="#RFC3471" class="xref">RFC3471</a>]</span>, this piece of information is used
              with the encoding type and signal type to fully describe
              the switching technology and data carried by the
              TE-LSP. This is applicable to the TE-LSP itself and also to the TE-LSP endpoint (carried in the END-POINTS object for MPLS networks in <span>[<a href="#RFC5440" class="xref">RFC5440</a>]</span>) when considering multiple network layers.

 Inter-layer path computation requirements are addressed in <span>[<a href="#RFC8282" class="xref">RFC8282</a>]</span>, which focuses on the TE-LSP itself but
 does not address the TE-LSP endpoints.<a href="#section-1.3.1-1.1" class="pilcrow">¶</a>
</dd>
            <dd class="break"></dd>
<dt>(2)</dt>
<dd id="section-1.3.1-1.2">Encoding type: See (1).<a href="#section-1.3.1-1.2" class="pilcrow">¶</a>
</dd>
            <dd class="break"></dd>
<dt>(3)</dt>
<dd id="section-1.3.1-1.3">Signal type: See (1).<a href="#section-1.3.1-1.3" class="pilcrow">¶</a>
</dd>
            <dd class="break"></dd>
<dt>(4)</dt>
<dd id="section-1.3.1-1.4">Concatenation type: This parameter and the concatenation
              number (see (5)) are specific to some TDM (SDH and ODU)
              switching technologies. They <span class="bcp14">MUST</span> be described together
              and are used to derive the requested resource allocation
              for the TE-LSP. It is scoped to the TE-LSP and is related
              to the BANDWIDTH object <span>[<a href="#RFC5440" class="xref">RFC5440</a>]</span> in MPLS networks. See concatenation
              information in <span>[<a href="#RFC4606" class="xref">RFC4606</a>]</span> and <span>[<a href="#RFC4328" class="xref">RFC4328</a>]</span>.<a href="#section-1.3.1-1.4" class="pilcrow">¶</a>
</dd>
            <dd class="break"></dd>
<dt>(5)</dt>
<dd id="section-1.3.1-1.5">Concatenation number: See (4).<a href="#section-1.3.1-1.5" class="pilcrow">¶</a>
</dd>
            <dd class="break"></dd>
<dt>(6)</dt>
<dd id="section-1.3.1-1.6">Technology-specific label(s): As described in <span>[<a href="#RFC3471" class="xref">RFC3471</a>]</span>, the GMPLS labels are specific to each switching technology. They can be specified on each link and also on the TE-LSP endpoints, in WSON networks, for instance, as described in <span>[<a href="#RFC6163" class="xref">RFC6163</a>]</span>. The label restriction can apply to endpoints, and on each hop, the related PCEP objects are END-POINTS, IRO, XRO, and RRO.<a href="#section-1.3.1-1.6" class="pilcrow">¶</a>
</dd>
            <dd class="break"></dd>
<dt>(7)</dt>
<dd id="section-1.3.1-1.7">End-to-End (E2E) path protection type: As defined in <span>[<a href="#RFC4872" class="xref">RFC4872</a>]</span>, this is applicable to the TE-LSP. In MPLS networks, the related PCEP object is LSPA (carrying local protection information).<a href="#section-1.3.1-1.7" class="pilcrow">¶</a>
</dd>
            <dd class="break"></dd>
<dt>(8)</dt>
<dd id="section-1.3.1-1.8">Administrative group: As defined in <span>[<a href="#RFC3630" class="xref">RFC3630</a>]</span>, this information is already carried in the LSPA object.<a href="#section-1.3.1-1.8" class="pilcrow">¶</a>
</dd>
            <dd class="break"></dd>
<dt>(9)</dt>
<dd id="section-1.3.1-1.9">Link protection type: As defined in <span>[<a href="#RFC4872" class="xref">RFC4872</a>]</span>, this is applicable to the TE-LSP and is carried in association with the E2E path protection type.<a href="#section-1.3.1-1.9" class="pilcrow">¶</a>
</dd>
            <dd class="break"></dd>
<dt>(10)</dt>
<dd id="section-1.3.1-1.10">Support for unnumbered interfaces: As defined in <span>[<a href="#RFC3477" class="xref">RFC3477</a>]</span>. Its scope and related objects are the same as labels.<a href="#section-1.3.1-1.10" class="pilcrow">¶</a>
</dd>
            <dd class="break"></dd>
<dt>(11)</dt>
<dd id="section-1.3.1-1.11">Support for asymmetric bandwidth requests: As defined in <span>[<a href="#RFC6387" class="xref">RFC6387</a>]</span>, the scope is similar to (4).<a href="#section-1.3.1-1.11" class="pilcrow">¶</a>
</dd>
            <dd class="break"></dd>
<dt>(12)</dt>
<dd id="section-1.3.1-1.12">Support for explicit label control during the path
     computation: This affects the TE-LSP and the amount of information
     returned in the ERO.<a href="#section-1.3.1-1.12" class="pilcrow">¶</a>
</dd>
            <dd class="break"></dd>
<dt>(13)</dt>
<dd id="section-1.3.1-1.13"> Support of label restrictions in the requests/responses:
              This is described in (6).<a href="#section-1.3.1-1.13" class="pilcrow">¶</a>
</dd>
          <dd class="break"></dd>
</dl>
</section>
<section id="section-1.3.2">
          <h4 id="name-requirements-on-the-path-com">
<a href="#section-1.3.2" class="section-number selfRef">1.3.2. </a><a href="#name-requirements-on-the-path-com" class="section-name selfRef">Requirements on the Path Computation Response</a>
          </h4>
<span class="break"></span><dl class="olPercent" id="section-1.3.2-1">
            <dt>(1)</dt>
<dd id="section-1.3.2-1.1">Path computation with concatenation: This is related to
            the Path Computation request requirement (4). In addition,
            there is a specific type of concatenation, called virtual
            concatenation, that allows different routes to be used
            between the endpoints. It is similar to the semantic and scope of the LOAD-BALANCING in MPLS networks.<a href="#section-1.3.2-1.1" class="pilcrow">¶</a>
</dd>
            <dd class="break"></dd>
<dt>(2)</dt>
<dd id="section-1.3.2-1.2">Label constraint: The PCE should be able to include labels in the path returned to the PCC; the related object is the ERO object.<a href="#section-1.3.2-1.2" class="pilcrow">¶</a>
</dd>
            <dd class="break"></dd>
<dt>(3)</dt>
<dd id="section-1.3.2-1.3">Roles of the routes: As defined in <span>[<a href="#RFC4872" class="xref">RFC4872</a>]</span>, this is applicable to the TE-LSP and is carried in association with the E2E path protection type.<a href="#section-1.3.2-1.3" class="pilcrow">¶</a>
</dd>
          <dd class="break"></dd>
</dl>
</section>
</section>
</div>
<div id="existing-support">
<section id="section-1.4">
        <h3 id="name-existing-support-and-limita">
<a href="#section-1.4" class="section-number selfRef">1.4. </a><a href="#name-existing-support-and-limita" class="section-name selfRef">Existing Support and Limitations for GMPLS in Base PCEP Objects</a>
        </h3>
<p id="section-1.4-1"> The support provided by specifications in <span>[<a href="#RFC8282" class="xref">RFC8282</a>]</span> and <span>[<a href="#RFC5440" class="xref">RFC5440</a>]</span>  for the
          requirements listed in <span>[<a href="#RFC7025" class="xref">RFC7025</a>]</span> is summarized in Tables <a href="#rfc7025_pcreq_reqss" class="xref">1</a> and <a href="#rfc7025_pcrep_reqss" class="xref">2</a>.  In
          some cases, the support may not be complete, as noted, and additional support
          needs to be provided as indicated in this specification.<a href="#section-1.4-1" class="pilcrow">¶</a></p>
<span id="name-requirements-support-per-rf"></span><div id="rfc7025_pcreq_reqss">
<table class="center" id="table-1">
          <caption>
<a href="#table-1" class="selfRef">Table 1</a>:
<a href="#name-requirements-support-per-rf" class="selfRef">Requirements Support per RFC 7025, Section 3.1</a>
          </caption>
<thead>
            <tr>
              <th class="text-left" rowspan="1" colspan="1">Req.</th>
              <th class="text-left" rowspan="1" colspan="1">Name</th>
              <th class="text-left" rowspan="1" colspan="1">Support</th>
            </tr>
          </thead>
          <tbody>
            <tr>
              <td class="text-left" rowspan="1" colspan="1"> 1   </td>
              <td class="text-left" rowspan="1" colspan="1"> Switching capability/type                                      </td>
              <td class="text-left" rowspan="1" colspan="1"> SWITCH-LAYER (RFC 8282) </td>
            </tr>
            <tr>
              <td class="text-left" rowspan="1" colspan="1"> 2   </td>
              <td class="text-left" rowspan="1" colspan="1"> Encoding type                                                  </td>
              <td class="text-left" rowspan="1" colspan="1"> SWITCH-LAYER (RFC 8282) </td>
            </tr>
            <tr>
              <td class="text-left" rowspan="1" colspan="1"> 3   </td>
              <td class="text-left" rowspan="1" colspan="1"> Signal type                                                    </td>
              <td class="text-left" rowspan="1" colspan="1"> SWITCH-LAYER (RFC 8282) </td>
            </tr>
            <tr>
              <td class="text-left" rowspan="1" colspan="1"> 4   </td>
              <td class="text-left" rowspan="1" colspan="1"> Concatenation type                                             </td>
              <td class="text-left" rowspan="1" colspan="1"> No                     </td>
            </tr>
            <tr>
              <td class="text-left" rowspan="1" colspan="1"> 5   </td>
              <td class="text-left" rowspan="1" colspan="1"> Concatenation number                                           </td>
              <td class="text-left" rowspan="1" colspan="1"> No                     </td>
            </tr>
            <tr>
              <td class="text-left" rowspan="1" colspan="1"> 6   </td>
              <td class="text-left" rowspan="1" colspan="1"> Technology-specific label                                      </td>
              <td class="text-left" rowspan="1" colspan="1"> (Partial) ERO (RFC 5440)</td>
            </tr>
            <tr>
              <td class="text-left" rowspan="1" colspan="1"> 7   </td>
              <td class="text-left" rowspan="1" colspan="1"> End-to-End (E2E) path protection type                          </td>
              <td class="text-left" rowspan="1" colspan="1"> No </td>
            </tr>
            <tr>
              <td class="text-left" rowspan="1" colspan="1"> 8   </td>
              <td class="text-left" rowspan="1" colspan="1"> Administrative group                                           </td>
              <td class="text-left" rowspan="1" colspan="1"> LSPA (RFC 5440) </td>
            </tr>
            <tr>
              <td class="text-left" rowspan="1" colspan="1"> 9   </td>
              <td class="text-left" rowspan="1" colspan="1"> Link protection type                                           </td>
              <td class="text-left" rowspan="1" colspan="1"> No </td>
            </tr>
            <tr>
              <td class="text-left" rowspan="1" colspan="1"> 10  </td>
              <td class="text-left" rowspan="1" colspan="1"> Support for unnumbered interfaces                              </td>
              <td class="text-left" rowspan="1" colspan="1"> (Partial) ERO (RFC 5440)</td>
            </tr>
            <tr>
              <td class="text-left" rowspan="1" colspan="1"> 11  </td>
              <td class="text-left" rowspan="1" colspan="1"> Support for asymmetric bandwidth requests                      </td>
              <td class="text-left" rowspan="1" colspan="1"> No </td>
            </tr>
            <tr>
              <td class="text-left" rowspan="1" colspan="1"> 12  </td>
              <td class="text-left" rowspan="1" colspan="1"> Support for explicit label control during the path computation </td>
              <td class="text-left" rowspan="1" colspan="1"> No</td>
            </tr>
            <tr>
              <td class="text-left" rowspan="1" colspan="1"> 13  </td>
              <td class="text-left" rowspan="1" colspan="1"> Support of label restrictions in the requests/responses        </td>
              <td class="text-left" rowspan="1" colspan="1"> No </td>
            </tr>
          </tbody>
        </table>
</div>
<span id="name-requirements-support-per-rfc"></span><div id="rfc7025_pcrep_reqss">
<table class="center" id="table-2">
          <caption>
<a href="#table-2" class="selfRef">Table 2</a>:
<a href="#name-requirements-support-per-rfc" class="selfRef">Requirements Support per RFC 7025, Section 3.2</a>
          </caption>
<thead>
            <tr>
              <th class="text-left" rowspan="1" colspan="1">Req.</th>
              <th class="text-left" rowspan="1" colspan="1">Name</th>
              <th class="text-left" rowspan="1" colspan="1">Support</th>
            </tr>
          </thead>
          <tbody>
            <tr>
              <td class="text-left" rowspan="1" colspan="1">1</td>
              <td class="text-left" rowspan="1" colspan="1">Path computation with concatenation </td>
              <td class="text-left" rowspan="1" colspan="1"> No      </td>
            </tr>
            <tr>
              <td class="text-left" rowspan="1" colspan="1">2</td>
              <td class="text-left" rowspan="1" colspan="1">Label constraint                    </td>
              <td class="text-left" rowspan="1" colspan="1"> No      </td>
            </tr>
            <tr>
              <td class="text-left" rowspan="1" colspan="1">3</td>
              <td class="text-left" rowspan="1" colspan="1">Roles of the routes                 </td>
              <td class="text-left" rowspan="1" colspan="1"> No      </td>
            </tr>
          </tbody>
        </table>
</div>
<p id="section-1.4-4">Per <a href="#requirement-map" class="xref">Section 1.3</a>, PCEP (as
        described in <span>[<a href="#RFC5440" class="xref">RFC5440</a>]</span>, <span>[<a href="#RFC5521" class="xref">RFC5521</a>]</span>, and <span>[<a href="#RFC8282" class="xref">RFC8282</a>]</span>) supports the following objects, included in
        requests and responses, that are related to the described
        requirements.<a href="#section-1.4-4" class="pilcrow">¶</a></p>
<p id="section-1.4-5">From <span>[<a href="#RFC5440" class="xref">RFC5440</a>]</span>:<a href="#section-1.4-5" class="pilcrow">¶</a></p>
<ul class="ulEmpty normal">
<li class="ulEmpty normal" id="section-1.4-6.1">
            <span class="break"></span><dl class="dlParallel" id="section-1.4-6.1.1">
              <dt id="section-1.4-6.1.1.1">END-POINTS:</dt>
              <dd id="section-1.4-6.1.1.2">related to requirements 1, 2, 3, 6, 10, and 13. The object only supports numbered endpoints. The context specifies whether they are node identifiers or numbered interfaces.<a href="#section-1.4-6.1.1.2" class="pilcrow">¶</a>
</dd>
              <dd class="break"></dd>
<dt id="section-1.4-6.1.1.3">BANDWIDTH:</dt>
              <dd id="section-1.4-6.1.1.4">related to requirements 4, 5, and 11. The data rate is encoded in the BANDWIDTH object (as an IEEE 32-bit float). <span>[<a href="#RFC5440" class="xref">RFC5440</a>]</span> does not include the ability to convey an encoding proper to all GMPLS-controlled networks.<a href="#section-1.4-6.1.1.4" class="pilcrow">¶</a>
</dd>
              <dd class="break"></dd>
<dt id="section-1.4-6.1.1.5">ERO:</dt>
              <dd id="section-1.4-6.1.1.6">related to requirements 6, 10, 12, and 13. The ERO
          content is defined in RSVP in
          <span>[<a href="#RFC3209" class="xref">RFC3209</a>]</span>, <span>[<a href="#RFC3473" class="xref">RFC3473</a>]</span>, <span>[<a href="#RFC3477" class="xref">RFC3477</a>]</span>, and <span>[<a href="#RFC7570" class="xref">RFC7570</a>]</span> and
          already supports all of the requirements.<a href="#section-1.4-6.1.1.6" class="pilcrow">¶</a>
</dd>
              <dd class="break"></dd>
<dt id="section-1.4-6.1.1.7">LSPA:</dt>
              <dd id="section-1.4-6.1.1.8">related to requirements 7, 8, and 9. Requirement 8 (Administrative group) is already supported.<a href="#section-1.4-6.1.1.8" class="pilcrow">¶</a>
</dd>
            <dd class="break"></dd>
</dl>
</li>
        </ul>
<p id="section-1.4-7">From <span>[<a href="#RFC5521" class="xref">RFC5521</a>]</span>:<a href="#section-1.4-7" class="pilcrow">¶</a></p>
<ul class="ulEmpty normal">
<li class="ulEmpty normal" id="section-1.4-8.1">
            <p id="section-1.4-8.1.1">XRO:<a href="#section-1.4-8.1.1" class="pilcrow">¶</a></p>
<ul class="normal">
<li class="normal" id="section-1.4-8.1.2.1">This object allows excluding (strict or not) resources and is related to requirements 6, 10, and 13. It also includes the requested diversity (node, link, or SRLG).<a href="#section-1.4-8.1.2.1" class="pilcrow">¶</a>
</li>
              <li class="normal" id="section-1.4-8.1.2.2">When the F bit is set, the request indicates that the
            existing path has failed, and the resources present in the RRO can be reused.<a href="#section-1.4-8.1.2.2" class="pilcrow">¶</a>
</li>
            </ul>
</li>
        </ul>
<p id="section-1.4-9">From <span>[<a href="#RFC8282" class="xref">RFC8282</a>]</span>:<a href="#section-1.4-9" class="pilcrow">¶</a></p>
<ul class="ulEmpty normal">
<li class="ulEmpty normal" id="section-1.4-10.1">
            <span class="break"></span><dl class="dlParallel" id="section-1.4-10.1.1">
              <dt id="section-1.4-10.1.1.1">SWITCH-LAYER:</dt>
              <dd id="section-1.4-10.1.1.2">addresses requirements 1, 2, and 3 for the TE-LSP and indicates which layer(s) should be considered. The object can be used to represent the RSVP-TE Generalized Label Request. It does not address the endpoints case of requirements 1, 2, and 3.<a href="#section-1.4-10.1.1.2" class="pilcrow">¶</a>
</dd>
              <dd class="break"></dd>
<dt id="section-1.4-10.1.1.3">REQ-ADAP-CAP:</dt>
              <dd id="section-1.4-10.1.1.4">indicates the adaptation capabilities requested; it can also be used for the endpoints in case of mono-layer computation.<a href="#section-1.4-10.1.1.4" class="pilcrow">¶</a>
</dd>
            <dd class="break"></dd>
</dl>
</li>
        </ul>
<p id="section-1.4-11">
          The gaps in functional coverage of the base PCEP objects are:<a href="#section-1.4-11" class="pilcrow">¶</a></p>
<ul class="normal">
<li class="normal" id="section-1.4-12.1">The BANDWIDTH and LOAD-BALANCING objects do not describe the details of the traffic request (requirements 4 and 5, for example, NVC and multiplier) in the context of GMPLS networks, for instance, in TDM or OTN networks.<a href="#section-1.4-12.1" class="pilcrow">¶</a>
</li>
          <li class="normal" id="section-1.4-12.2">The END-POINTS object does not allow specifying an unnumbered interface, nor potential label restrictions on the interface (requirements 6, 10, and 13). Those parameters are of interest in case of switching constraints.<a href="#section-1.4-12.2" class="pilcrow">¶</a>
</li>
          <li class="normal" id="section-1.4-12.3">The IROs/XROs do not allow the inclusion/exclusion of labels (requirements 6, 10, and 13).<a href="#section-1.4-12.3" class="pilcrow">¶</a>
</li>
          <li class="normal" id="section-1.4-12.4">Base attributes do not allow expressing the requested link protection level and/or the end-to-end protection attributes.<a href="#section-1.4-12.4" class="pilcrow">¶</a>
</li>
        </ul>
<p id="section-1.4-13">As defined later in this document, the PCEP extensions that cover the gaps are:<a href="#section-1.4-13" class="pilcrow">¶</a></p>
<ul class="normal">
<li class="normal" id="section-1.4-14.1">Two new object types are defined for the BANDWIDTH object
   (Generalized bandwidth and Generalized bandwidth of an existing TE-LSP for which a reoptimization is requested).<a href="#section-1.4-14.1" class="pilcrow">¶</a>
</li>
          <li class="normal" id="section-1.4-14.2">A new object type is defined for the
                  LOAD-BALANCING object (Generalized Load Balancing).<a href="#section-1.4-14.2" class="pilcrow">¶</a>
</li>
          <li class="normal" id="section-1.4-14.3">A new object type is defined for the END-POINTS object (Generalized Endpoint).<a href="#section-1.4-14.3" class="pilcrow">¶</a>
</li>
          <li class="normal" id="section-1.4-14.4">A new TLV is added to the Open message for capability negotiation.<a href="#section-1.4-14.4" class="pilcrow">¶</a>
</li>
          <li class="normal" id="section-1.4-14.5">A new TLV is added to the LSPA object.<a href="#section-1.4-14.5" class="pilcrow">¶</a>
</li>
          <li class="normal" id="section-1.4-14.6">The Label subobject is now allowed in the IRO and XRO objects.<a href="#section-1.4-14.6" class="pilcrow">¶</a>
</li>
          <li class="normal" id="section-1.4-14.7">In order to indicate the routing granularity used in the response, a new flag is added in the RP object.<a href="#section-1.4-14.7" class="pilcrow">¶</a>
</li>
        </ul>
</section>
</div>
</section>
<section id="section-2">
      <h2 id="name-pcep-objects-and-extensions">
<a href="#section-2" class="section-number selfRef">2. </a><a href="#name-pcep-objects-and-extensions" class="section-name selfRef">PCEP Objects and Extensions</a>
      </h2>
<p id="section-2-1">
        This section describes the necessary PCEP objects and extensions. The PCReq and PCRep messages are defined in <span>[<a href="#RFC5440" class="xref">RFC5440</a>]</span>. This document does not change the existing grammar.<a href="#section-2-1" class="pilcrow">¶</a></p>
<div id="capability">
<section id="section-2.1">
        <h3 id="name-gmpls-capability-advertisem">
<a href="#section-2.1" class="section-number selfRef">2.1. </a><a href="#name-gmpls-capability-advertisem" class="section-name selfRef">GMPLS Capability Advertisement</a>
        </h3>
<div id="IGP-discovery">
<section id="section-2.1.1">
          <h4 id="name-gmpls-computation-tlv-in-th">
<a href="#section-2.1.1" class="section-number selfRef">2.1.1. </a><a href="#name-gmpls-computation-tlv-in-th" class="section-name selfRef">GMPLS Computation TLV in the Existing PCE Discovery Protocol</a>
          </h4>
<p id="section-2.1.1-1">
    IGP-based PCE Discovery (PCED) is defined in <span>[<a href="#RFC5088" class="xref">RFC5088</a>]</span> and <span>[<a href="#RFC5089" class="xref">RFC5089</a>]</span> for the
         OSPF and IS-IS protocols. Those documents have defined bit 0
         in the PCE-CAP-FLAGS Sub-TLV of the PCED TLV as "Path computation
         with GMPLS link constraints". This capability is optional and
         can be used to detect GMPLS-capable PCEs. PCEs that set the bit to indicate support of GMPLS path computation
<span class="bcp14">MUST</span> follow the procedures in <a href="#open-extensions" class="xref">Section 2.1.2</a> to further qualify the level of support during PCEP session establishment.<a href="#section-2.1.1-1" class="pilcrow">¶</a></p>
</section>
</div>
<div id="open-extensions">
<section id="section-2.1.2">
          <h4 id="name-open-object-extension-gmpls">
<a href="#section-2.1.2" class="section-number selfRef">2.1.2. </a><a href="#name-open-object-extension-gmpls" class="section-name selfRef">OPEN Object Extension GMPLS-CAPABILITY TLV</a>
          </h4>
<p id="section-2.1.2-1">
    In addition to the IGP advertisement, a PCEP speaker <span class="bcp14">MUST</span> be able to discover the other peer GMPLS capabilities during the Open message exchange. This capability is also useful to avoid misconfigurations. This document defines a GMPLS-CAPABILITY TLV for use in the OPEN object to negotiate the GMPLS capability. The inclusion of this TLV in the Open message indicates that the PCEP speaker supports the PCEP extensions defined in the document.
    A PCEP speaker that is able to support the GMPLS extensions
           defined in this document <span class="bcp14">MUST</span> include the GMPLS-CAPABILITY
           TLV in the Open message.
           If one of the PCEP peers does not include the GMPLS-CAPABILITY TLV
           in the Open message, the peers <span class="bcp14">MUST NOT</span> make use of the objects and TLVs defined in this document.<a href="#section-2.1.2-1" class="pilcrow">¶</a></p>
<p id="section-2.1.2-2">
           If the PCEP speaker
           supports the extensions of this specification but did not advertise
           the GMPLS-CAPABILITY capability, upon receipt of a message
           from the PCE including an extension defined in this document,
           it <span class="bcp14">MUST</span> generate a PCEP Error (PCErr) with Error-Type=10
           (Reception of an invalid object) and Error-value=31
           (Missing GMPLS-CAPABILITY TLV), and it
           <span class="bcp14">SHOULD</span> terminate the PCEP session.<a href="#section-2.1.2-2" class="pilcrow">¶</a></p>
<p id="section-2.1.2-3">
    As documented in <a href="#iana-tlvs" class="xref">Section 5.3</a> ("New
    PCEP TLVs"), IANA has allocated value 45 (GMPLS-CAPABILITY) from
    the "PCEP TLV Type Indicators" sub-registry.
    The format for the GMPLS-CAPABILITY TLV is shown in the following figure.<a href="#section-2.1.2-3" class="pilcrow">¶</a></p>
<div class="artwork art-text alignLeft" id="section-2.1.2-4">
<pre>
  0                   1                   2                   3
  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
 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
 |               Type=45         |           Length              |
 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
 |                             Flags                             |
 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
</pre><a href="#section-2.1.2-4" class="pilcrow">¶</a>
</div>
<p id="section-2.1.2-5">
              No flags are defined in this document; they are reserved for future use. Unassigned flags
 <span class="bcp14">MUST</span> be set to zero on transmission and  <span class="bcp14">MUST</span> be ignored on receipt.<a href="#section-2.1.2-5" class="pilcrow">¶</a></p>
</section>
</div>
</section>
</div>
<div id="rp-extensions">
<section id="section-2.2">
        <h3 id="name-rp-object-extension">
<a href="#section-2.2" class="section-number selfRef">2.2. </a><a href="#name-rp-object-extension" class="section-name selfRef">RP Object Extension</a>
        </h3>
<p id="section-2.2-1">
      Explicit Label Control (ELC) is a procedure supported by RSVP-TE,
         where the outgoing labels are encoded in the ERO.  As a consequence,
         the PCE can provide such labels directly in the path ERO.
         Depending on the policies or switching layer, it might be necessary for the PCC to use
         explicit label control or explicit link ids; thus, it needs to
         indicate in the PCReq which granularity it is expecting in the ERO.
         This corresponds to requirement 12 in <span><a href="https://www.rfc-editor.org/rfc/rfc7025#section-3.1" class="relref">Section 3.1</a> of [<a href="#RFC7025" class="xref">RFC7025</a>]</span>.
         The possible granularities can be node, link, or label. The
         granularities are interdependent, in the sense that link granularity implies the
         presence of node information in the ERO; similarly, a label granularity implies that the ERO contains node, link, and label information.<a href="#section-2.2-1" class="pilcrow">¶</a></p>
<p id="section-2.2-2">A new 2-bit Routing Granularity (RG) flag (bits 15-16) is defined in
         the RP object. The values are defined as follows:<a href="#section-2.2-2" class="pilcrow">¶</a></p>
<ul class="ulEmpty normal">
<li class="ulEmpty normal" id="section-2.2-3.1">
            <span class="break"></span><dl class="dlParallel" id="section-2.2-3.1.1">
              <dt id="section-2.2-3.1.1.1">0:</dt>
              <dd id="section-2.2-3.1.1.2">reserved<a href="#section-2.2-3.1.1.2" class="pilcrow">¶</a>
</dd>
              <dd class="break"></dd>
<dt id="section-2.2-3.1.1.3">1:</dt>
              <dd id="section-2.2-3.1.1.4">node<a href="#section-2.2-3.1.1.4" class="pilcrow">¶</a>
</dd>
              <dd class="break"></dd>
<dt id="section-2.2-3.1.1.5">2:</dt>
              <dd id="section-2.2-3.1.1.6">link<a href="#section-2.2-3.1.1.6" class="pilcrow">¶</a>
</dd>
              <dd class="break"></dd>
<dt id="section-2.2-3.1.1.7">3:</dt>
              <dd id="section-2.2-3.1.1.8">label<a href="#section-2.2-3.1.1.8" class="pilcrow">¶</a>
</dd>
            <dd class="break"></dd>
</dl>
</li>
        </ul>
<p id="section-2.2-4">The RG flag in the RP object indicates the requested
            route granularity. The PCE <span class="bcp14">SHOULD</span> follow this granularity and <span class="bcp14">MAY</span> return a NO-PATH if the requested granularity cannot be provided. The PCE <span class="bcp14">MAY</span> return any granularity on the route based on its policy. The PCC can decide if the ERO is acceptable based on its content.<a href="#section-2.2-4" class="pilcrow">¶</a></p>
<p id="section-2.2-5">    If a PCE honored the requested routing granularity for a request, it <span class="bcp14">MUST</span> indicate the selected routing
     granularity in the RP object included in the response. Otherwise, the PCE <span class="bcp14">MUST</span> use the reserved RG to leave the check of the ERO to the PCC. The RG flag is backward compatible with <span>[<a href="#RFC5440" class="xref">RFC5440</a>]</span>: the value sent by an implementation (PCC or PCE) not supporting it will indicate a reserved value.<a href="#section-2.2-5" class="pilcrow">¶</a></p>
</section>
</div>
<div id="generalized-bandwidth">
<section id="section-2.3">
        <h3 id="name-bandwidth-object-extensions">
<a href="#section-2.3" class="section-number selfRef">2.3. </a><a href="#name-bandwidth-object-extensions" class="section-name selfRef">BANDWIDTH Object Extensions</a>
        </h3>
<p id="section-2.3-1">
    Per <span>[<a href="#RFC5440" class="xref">RFC5440</a>]</span>, the object carrying
    the requested size for the TE-LSP is the BANDWIDTH object. Object
    types 1 and 2 defined in <span>[<a href="#RFC5440" class="xref">RFC5440</a>]</span>
    do not provide enough information to describe the TE-LSP bandwidth
    in GMPLS networks. The BANDWIDTH object encoding has to be extended
    to allow the object to express the bandwidth as described in <span>[<a href="#RFC7025" class="xref">RFC7025</a>]</span>.  RSVP-TE extensions for GMPLS
    provide a set of encodings that allow such representation in an
    unambiguous way; this is encoded in the RSVP-TE Traffic
    Specification (TSpec) and Flow Specification (FlowSpec)
    objects. This document extends the BANDWIDTH object with new object
    types reusing the RSVP-TE encoding.<a href="#section-2.3-1" class="pilcrow">¶</a></p>
<p id="section-2.3-2">The following possibilities are supported by the extended encoding:<a href="#section-2.3-2" class="pilcrow">¶</a></p>
<ul class="normal">
<li class="normal" id="section-2.3-3.1">Asymmetric bandwidth (different bandwidth in forward and reverse direction), as described in <span>[<a href="#RFC6387" class="xref">RFC6387</a>]</span>.<a href="#section-2.3-3.1" class="pilcrow">¶</a>
</li>
          <li class="normal" id="section-2.3-3.2">GMPLS (SDH/SONET, G.709, ATM, MEF, etc.) parameters.<a href="#section-2.3-3.2" class="pilcrow">¶</a>
</li>
        </ul>
<p id="section-2.3-4">
         This corresponds to requirements 3, 4, 5, and 11 in <span><a href="https://www.rfc-editor.org/rfc/rfc7025#section-3.1" class="relref">Section 3.1</a> of [<a href="#RFC7025" class="xref">RFC7025</a>]</span>.<a href="#section-2.3-4" class="pilcrow">¶</a></p>
<p id="section-2.3-5">
  This document defines two object types for the BANDWIDTH object:<a href="#section-2.3-5" class="pilcrow">¶</a></p>
<ul class="ulEmpty normal">
<li class="ulEmpty normal" id="section-2.3-6.1">
            <span class="break"></span><dl class="dlParallel" id="section-2.3-6.1.1">
              <dt id="section-2.3-6.1.1.1">3:</dt>
              <dd id="section-2.3-6.1.1.2">Generalized bandwidth<a href="#section-2.3-6.1.1.2" class="pilcrow">¶</a>
</dd>
              <dd class="break"></dd>
<dt id="section-2.3-6.1.1.3">4:</dt>
              <dd id="section-2.3-6.1.1.4">Generalized bandwidth of an existing TE-LSP for which a
          reoptimization is requested<a href="#section-2.3-6.1.1.4" class="pilcrow">¶</a>
</dd>
            <dd class="break"></dd>
</dl>
</li>
        </ul>
<p id="section-2.3-7">
   The definitions below apply for object types 3 and 4. The body is as follows:<a href="#section-2.3-7" class="pilcrow">¶</a></p>
<div class="artwork art-text alignLeft" id="section-2.3-8">
<pre>
    0                   1                   2                   3
    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
   +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
   |    Bandwidth Spec Length      | Rev. Bandwidth Spec Length    |
   +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
   | Bw Spec Type  |   Reserved                                    |
   +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
   |                                                               |
   ~                     Generalized Bandwidth                     ~
   |                                                               |
   +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
   |                                                               |
   ~            Reverse Generalized Bandwidth (optional)           ~
   |                                                               |
   +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
   |                                                               |
   ~                       Optional TLVs                           ~
   |                                                               |
   +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
</pre><a href="#section-2.3-8" class="pilcrow">¶</a>
</div>
<p id="section-2.3-9">BANDWIDTH object types 3 and 4 have a variable length.
  The 16-bit Bandwidth Spec Length field indicates the length of the Generalized Bandwidth field.
  The Bandwidth Spec Length <span class="bcp14">MUST</span> be strictly greater than 0.
  The 16-bit Reverse Bandwidth Spec Length field indicates the
  length of the Reverse Generalized Bandwidth field.
  The Reverse Bandwidth Spec Length <span class="bcp14">MAY</span> be equal to 0.<a href="#section-2.3-9" class="pilcrow">¶</a></p>
<p id="section-2.3-10">The Bw Spec Type field determines which type of bandwidth is represented by the object.<a href="#section-2.3-10" class="pilcrow">¶</a></p>
<p id="section-2.3-11">The Bw Spec Type corresponds to the RSVP-TE SENDER_TSPEC (Object Class 12) C-Types.<a href="#section-2.3-11" class="pilcrow">¶</a></p>
<p id="section-2.3-12"> The encoding of the Generalized Bandwidth and Reverse Generalized
        Bandwidth fields is the same as the traffic parameters carried in
        RSVP-TE; they can be found in the following references.

         Note that the RSVP-TE traffic specification <span class="bcp14">MAY</span> also
         include TLVs that are different from the PCEP TLVs (e.g., the TLVs defined in <span>[<a href="#RFC6003" class="xref">RFC6003</a>]</span>).<a href="#section-2.3-12" class="pilcrow">¶</a></p>
<span id="name-generalized-bandwidth-and-r"></span><div id="TSpec_encoding">
<table class="center" id="table-3">
          <caption>
<a href="#table-3" class="selfRef">Table 3</a>:
<a href="#name-generalized-bandwidth-and-r" class="selfRef">Generalized Bandwidth and Reverse Generalized Bandwidth Field Encoding</a>
          </caption>
<thead>
            <tr>
              <th class="text-left" rowspan="1" colspan="1">Bw Spec Type</th>
              <th class="text-left" rowspan="1" colspan="1">Name </th>
              <th class="text-left" rowspan="1" colspan="1">Reference</th>
            </tr>
          </thead>
          <tbody>
            <tr>
              <td class="text-left" rowspan="1" colspan="1">2</td>
              <td class="text-left" rowspan="1" colspan="1">Intserv</td>
              <td class="text-left" rowspan="1" colspan="1">
                <span>[<a href="#RFC2210" class="xref">RFC2210</a>]</span>
</td>
            </tr>
            <tr>
              <td class="text-left" rowspan="1" colspan="1">4</td>
              <td class="text-left" rowspan="1" colspan="1">SONET/SDH</td>
              <td class="text-left" rowspan="1" colspan="1">
                <span>[<a href="#RFC4606" class="xref">RFC4606</a>]</span>
</td>
            </tr>
            <tr>
              <td class="text-left" rowspan="1" colspan="1">5</td>
              <td class="text-left" rowspan="1" colspan="1">G.709</td>
              <td class="text-left" rowspan="1" colspan="1">
                <span>[<a href="#RFC4328" class="xref">RFC4328</a>]</span>
</td>
            </tr>
            <tr>
              <td class="text-left" rowspan="1" colspan="1">6</td>
              <td class="text-left" rowspan="1" colspan="1">Ethernet</td>
              <td class="text-left" rowspan="1" colspan="1">
                <span>[<a href="#RFC6003" class="xref">RFC6003</a>]</span>
</td>
            </tr>
            <tr>
              <td class="text-left" rowspan="1" colspan="1">7</td>
              <td class="text-left" rowspan="1" colspan="1">OTN-TDM</td>
              <td class="text-left" rowspan="1" colspan="1">
                <span>[<a href="#RFC7139" class="xref">RFC7139</a>]</span>
</td>
            </tr>
            <tr>
              <td class="text-left" rowspan="1" colspan="1">8</td>
              <td class="text-left" rowspan="1" colspan="1">SSON</td>
              <td class="text-left" rowspan="1" colspan="1">
                <span>[<a href="#RFC7792" class="xref">RFC7792</a>]</span>
</td>
            </tr>
          </tbody>
        </table>
</div>
<p id="section-2.3-14">
           When a PCC requests a bidirectional path with symmetric bandwidth,
   it <span class="bcp14">SHOULD</span> only specify the Generalized Bandwidth field and set the Reverse Bandwidth Spec
   Length to 0.

 When a PCC needs to request a bidirectional path with
        asymmetric bandwidth, it <span class="bcp14">SHOULD</span> specify the different bandwidth in the forward and reverse directions with Generalized Bandwidth and Reverse Generalized Bandwidth fields.<a href="#section-2.3-14" class="pilcrow">¶</a></p>
<p id="section-2.3-15">The procedure described in <span>[<a href="#RFC5440" class="xref">RFC5440</a>]</span> for the PCRep is unchanged: a PCE <span class="bcp14">MAY</span> include the BANDWIDTH objects in the response to indicate the BANDWIDTH of the path.<a href="#section-2.3-15" class="pilcrow">¶</a></p>
<p id="section-2.3-16">As specified in <span>[<a href="#RFC5440" class="xref">RFC5440</a>]</span>, in the case of the reoptimization of a TE-LSP, the bandwidth of the
   existing TE-LSP <span class="bcp14">MUST</span> also be included in addition to the requested
   bandwidth if and only if the two values differ.  The object type 4 <span class="bcp14">MAY</span> be used instead of the previously specified object
   type 2 to indicate the existing TE-LSP bandwidth, which was originally specified with
   object type 3. A PCC that requested a path with a BANDWIDTH object of
   object type 1 <span class="bcp14">MUST</span> use object type 2 to represent the existing TE-LSP
   bandwidth.<a href="#section-2.3-16" class="pilcrow">¶</a></p>
<p id="section-2.3-17">Optional TLVs <span class="bcp14">MAY</span> be included within the object body to specify
         more specific bandwidth requirements. No TLVs for object types 3 and 4 are defined by this document.<a href="#section-2.3-17" class="pilcrow">¶</a></p>
</section>
</div>
<div id="generalized-load-balancing">
<section id="section-2.4">
        <h3 id="name-load-balancing-object-exten">
<a href="#section-2.4" class="section-number selfRef">2.4. </a><a href="#name-load-balancing-object-exten" class="section-name selfRef">LOAD-BALANCING Object Extensions</a>
        </h3>
<p id="section-2.4-1">
         The LOAD-BALANCING object <span>[<a href="#RFC5440" class="xref">RFC5440</a>]</span>
         is used to request a set of at most Max-LSP TE-LSPs having in total
         the bandwidth specified in BANDWIDTH, with each TE-LSP having at
         least a specified minimum bandwidth.

 The LOAD-BALANCING object follows the bandwidth
         encoding of the BANDWIDTH object; thus, the existing definition from
         <span>[<a href="#RFC5440" class="xref">RFC5440</a>]</span> does not describe enough
         details for the bandwidth specification expected by GMPLS.<a href="#section-2.4-1" class="pilcrow">¶</a></p>
<p id="section-2.4-2">
    Similar to the BANDWIDTH object, a new object type is defined to allow a PCC to represent the bandwidth types supported by GMPLS networks.<a href="#section-2.4-2" class="pilcrow">¶</a></p>
<p id="section-2.4-3">
     This document defines object type 2 (Generalized Load Balancing) for the
     LOAD-BALANCING object.  The Generalized Load Balancing object type has a
     variable length.<a href="#section-2.4-3" class="pilcrow">¶</a></p>
<p id="section-2.4-4">The format of the Generalized Load Balancing object type is as follows:<a href="#section-2.4-4" class="pilcrow">¶</a></p>
<div class="artwork art-text alignLeft" id="section-2.4-5">
<pre>
    0                   1                   2                   3
    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
   +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
   |    Bandwidth Spec Length      | Reverse Bandwidth Spec Length |
   +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
   | Bw Spec Type  |  Max-LSP      | Reserved                      |
   +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
   |        Min Bandwidth Spec                                     |
   +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
   |        Min Reverse Bandwidth Spec (optional)                  |
   +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
   |                                                               |
   ~                      Optional TLVs                            ~
   |                                                               |
   +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
</pre><a href="#section-2.4-5" class="pilcrow">¶</a>
</div>
<span class="break"></span><dl class="dlParallel" id="section-2.4-6">
          <dt id="section-2.4-6.1">Bandwidth Spec Length (16 bits):</dt>
          <dd id="section-2.4-6.2">the total length of
         the Min Bandwidth Spec field. The length <span class="bcp14">MUST</span> be strictly greater than 0.<a href="#section-2.4-6.2" class="pilcrow">¶</a>
</dd>
          <dd class="break"></dd>
<dt id="section-2.4-6.3">Reverse Bandwidth Spec Length (16 bits):</dt>
          <dd id="section-2.4-6.4">the total
         length of the Min Reverse Bandwidth Spec field. It <span class="bcp14">MAY</span> be equal to 0.<a href="#section-2.4-6.4" class="pilcrow">¶</a>
</dd>
          <dd class="break"></dd>
<dt id="section-2.4-6.5">Bw Spec Type (8 bits):</dt>
          <dd id="section-2.4-6.6">the bandwidth specification type; it corresponds to RSVP-TE SENDER_TSPEC (Object Class 12) C-Types.<a href="#section-2.4-6.6" class="pilcrow">¶</a>
</dd>
          <dd class="break"></dd>
<dt id="section-2.4-6.7">Max-LSP (8 bits):</dt>
          <dd id="section-2.4-6.8">the maximum number of TE-LSPs in the set.<a href="#section-2.4-6.8" class="pilcrow">¶</a>
</dd>
          <dd class="break"></dd>
<dt id="section-2.4-6.9">Min Bandwidth Spec (variable):</dt>
          <dd id="section-2.4-6.10">specifies the minimum bandwidth specification of each
  element of the TE-LSP set.<a href="#section-2.4-6.10" class="pilcrow">¶</a>
</dd>
          <dd class="break"></dd>
<dt id="section-2.4-6.11">Min Reverse Bandwidth Spec (variable):</dt>
          <dd id="section-2.4-6.12">specifies the minimum reverse bandwidth specification of each
  element of the TE-LSP set.<a href="#section-2.4-6.12" class="pilcrow">¶</a>
</dd>
        <dd class="break"></dd>
</dl>
<p id="section-2.4-7">The encoding of the Min Bandwidth Spec and Min
        Reverse Bandwidth Spec fields is the same as in the RSVP-TE SENDER_TSPEC
        object; it can be found in <a href="#TSpec_encoding" class="xref">Table 3</a>
        in <a href="#generalized-bandwidth" class="xref">Section 2.3</a> of this document.<a href="#section-2.4-7" class="pilcrow">¶</a></p>
<p id="section-2.4-8">
  When a PCC requests a bidirectional path with symmetric
         bandwidth while specifying load-balancing constraints, it <span class="bcp14">SHOULD</span>
         specify the Min Bandwidth Spec field and set the Reverse
         Bandwidth Spec Length to 0. When a PCC needs to request a bidirectional path with
         asymmetric bandwidth while specifying load-balancing
         constraints, it <span class="bcp14">MUST</span> specify the different bandwidth in
         forward and reverse directions through Min Bandwidth Spec
         and Min Reverse Bandwidth Spec fields.<a href="#section-2.4-8" class="pilcrow">¶</a></p>
<p id="section-2.4-9">Optional TLVs <span class="bcp14">MAY</span> be included within the object body to specify
         more specific bandwidth requirements. No TLVs for the Generalized Load Balancing object type are defined by this document.<a href="#section-2.4-9" class="pilcrow">¶</a></p>
<p id="section-2.4-10">The semantic of the LOAD-BALANCING object is not changed. If a PCC
        requests the computation of a set of TE-LSPs with at most N
        TE-LSPs so that it can carry Generalized bandwidth X, each TE-LSP must at least transport bandwidth B; it inserts a
        BANDWIDTH object specifying X as the required bandwidth and a LOAD-BALANCING object with the Max-LSP and Min Bandwidth Spec fields set
        to N and B, respectively. When the BANDWIDTH and Min Bandwidth Spec can be summarized as scalars, the sum of the bandwidth for all TE-LSPs in the set is greater than X.
        The mapping of the X over N path with (at least) bandwidth B is technology and possibly node specific.
        Each standard definition of the transport technology is defining those mappings and are not repeated in this document. 
        A simplified example for SDH is described in <a href="#appendix" class="xref">Appendix A</a>.<a href="#section-2.4-10" class="pilcrow">¶</a></p>
<p id="section-2.4-11">
          In all other cases, including technologies based on statistical
          multiplexing (e.g., InterServ and Ethernet), the exact bandwidth
          management (e.g., the Ethernet's Excessive Rate) is left to the PCE's
          policies, according to the operator's configuration. If required,
          further documents may introduce a new mechanism to finely express
          complex load-balancing policies within PCEP.<a href="#section-2.4-11" class="pilcrow">¶</a></p>
<p id="section-2.4-12">The BANDWIDTH and LOAD-BALANCING Bw Spec Type can be different depending on the architecture of the endpoint node. When the PCE is not able to handle those two Bw Spec Types, it <span class="bcp14">MUST</span> return a NO-PATH with the bit "LOAD-BALANCING could not be performed with the bandwidth constraints" set in the  NO-PATH-VECTOR TLV.<a href="#section-2.4-12" class="pilcrow">¶</a></p>
</section>
</div>
<div id="endpoints_extensions">
<section id="section-2.5">
        <h3 id="name-end-points-object-extension">
<a href="#section-2.5" class="section-number selfRef">2.5. </a><a href="#name-end-points-object-extension" class="section-name selfRef">END-POINTS Object Extensions</a>
        </h3>
<p id="section-2.5-1">
           The END-POINTS object is used in a PCEP request message to specify the
           source and the destination of the path for which a path computation is requested.
           Per <span>[<a href="#RFC5440" class="xref">RFC5440</a>]</span>, the source IP address and the destination IP address are used to identify those.
           A new object type is defined to address the following possibilities:<a href="#section-2.5-1" class="pilcrow">¶</a></p>
<ul class="normal">
<li class="normal" id="section-2.5-2.1">Different source and destination endpoint types.<a href="#section-2.5-2.1" class="pilcrow">¶</a>
</li>
          <li class="normal" id="section-2.5-2.2">Label restrictions on the endpoint.<a href="#section-2.5-2.2" class="pilcrow">¶</a>
</li>
          <li class="normal" id="section-2.5-2.3">Specification of unnumbered endpoints type as seen in GMPLS networks.<a href="#section-2.5-2.3" class="pilcrow">¶</a>
</li>
        </ul>
<p id="section-2.5-3">
           The object encoding is described in the following sections.<a href="#section-2.5-3" class="pilcrow">¶</a></p>
<p id="section-2.5-4">In path computation within a GMPLS context, the endpoints can:<a href="#section-2.5-4" class="pilcrow">¶</a></p>
<ul class="normal">
<li class="normal" id="section-2.5-5.1">Be unnumbered as described in <span>[<a href="#RFC3477" class="xref">RFC3477</a>]</span>.<a href="#section-2.5-5.1" class="pilcrow">¶</a>
</li>
          <li class="normal" id="section-2.5-5.2">Have labels associated to them, specifying a set of constraints on the allocation of labels.<a href="#section-2.5-5.2" class="pilcrow">¶</a>
</li>
          <li class="normal" id="section-2.5-5.3">Have different switching capabilities.<a href="#section-2.5-5.3" class="pilcrow">¶</a>
</li>
        </ul>
<p id="section-2.5-6">
           The IPv4 and IPv6 endpoints are used to represent the source and destination IP addresses.
           The scope of the IP address (node or numbered link) is not explicitly stated.
           It is also possible to request a path between a numbered link and an unnumbered link, or a P2MP path between different types of endpoints.<a href="#section-2.5-6" class="pilcrow">¶</a></p>
<p id="section-2.5-7">           
           This document defines object type 5 (Generalized Endpoint) for the
           END-POINTS object.  This new type also supports the specification
           of constraints on the endpoint label to be used.  The PCE might
           know the interface restrictions, but this is not a requirement.
           This corresponds to requirements 6 and 10 in <span><a href="https://www.rfc-editor.org/rfc/rfc7025#section-3.1" class="relref">Section 3.1</a> of [<a href="#RFC7025" class="xref">RFC7025</a>]</span>.<a href="#section-2.5-7" class="pilcrow">¶</a></p>
<div id="endpoints_generalized">
<section id="section-2.5.1">
          <h4 id="name-generalized-endpoint-object">
<a href="#section-2.5.1" class="section-number selfRef">2.5.1. </a><a href="#name-generalized-endpoint-object" class="section-name selfRef">Generalized Endpoint Object Type</a>
          </h4>
<p id="section-2.5.1-1">
            The Generalized Endpoint object type format consists of a body and a list of TLVs scoped to this object. The TLVs give the details of the endpoints and are described in <a href="#endpoints_tlvs" class="xref">Section 2.5.2</a>. 
For each endpoint type, a different grammar is defined.


            The TLVs defined to describe an endpoint are:<a href="#section-2.5.1-1" class="pilcrow">¶</a></p>
<ol start="1" type="1" class="normal type-1" id="section-2.5.1-2">
            <li id="section-2.5.1-2.1">IPV4-ADDRESS<a href="#section-2.5.1-2.1" class="pilcrow">¶</a>
</li>
            <li id="section-2.5.1-2.2">IPV6-ADDRESS<a href="#section-2.5.1-2.2" class="pilcrow">¶</a>
</li>
            <li id="section-2.5.1-2.3">UNNUMBERED-ENDPOINT<a href="#section-2.5.1-2.3" class="pilcrow">¶</a>
</li>
            <li id="section-2.5.1-2.4">LABEL-REQUEST<a href="#section-2.5.1-2.4" class="pilcrow">¶</a>
</li>
            <li id="section-2.5.1-2.5">LABEL-SET<a href="#section-2.5.1-2.5" class="pilcrow">¶</a>
</li>
          </ol>
<p id="section-2.5.1-3">
    The  LABEL-SET TLV is used to restrict or suggest the label
    allocation in the PCE. This TLV expresses the set of restrictions
    that may apply to signaling. Label restriction support can be an
    explicit or a suggested value (LABEL-SET describing one label, with
    the L bit cleared or set, respectively), mandatory range
    restrictions (LABEL-SET with the L bit cleared), and optional range
    restriction (LABEL-SET with the L bit set).  Endpoints label
    restriction may not be part of the RRO or IRO. They can be
    included when following <span>[<a href="#RFC4003" class="xref">RFC4003</a>]</span>
    in signaling for the egress endpoint, but ingress endpoint
    properties can be local to the PCC and not signaled. To support
    this case, the  LABEL-SET allows indication of which labels are used
    in case of reoptimization.

    The label range restrictions are valid in GMPLS-controlled 
           networks, depending on either the PCC policy or the switching 
           technology used, for instance, on a given Ethernet or ODU 
           equipment having limited hardware capabilities restricting 
           the label range. Label
    set restriction also applies to WSON networks where the optical
    senders and receivers are limited in their frequency tunability
    ranges, consequently restricting the possible label ranges on the
    interface in GMPLS. The END-POINTS object with the Generalized
    Endpoint object type is encoded as follows:<a href="#section-2.5.1-3" class="pilcrow">¶</a></p>
<div class="artwork art-text alignLeft" id="section-2.5.1-4">
<pre>
    0                   1                   2                   3
    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
   +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
   |      Reserved                                 | Endpoint Type |
   +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
   |                                                               |
   ~                           TLVs                                ~
   |                                                               |
   +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
</pre><a href="#section-2.5.1-4" class="pilcrow">¶</a>
</div>
<p id="section-2.5.1-5">Reserved bits <span class="bcp14">SHOULD</span> be set to 0 when a message is sent and ignored when the message is received.<a href="#section-2.5.1-5" class="pilcrow">¶</a></p>
<p id="section-2.5.1-6">The values for the Endpoint Type field are defined as follows:<a href="#section-2.5.1-6" class="pilcrow">¶</a></p>
<span id="name-generalized-endpoint-types"></span><div id="endpoints_generalized_endpoint-type">
<table class="center" id="table-4">
            <caption>
<a href="#table-4" class="selfRef">Table 4</a>:
<a href="#name-generalized-endpoint-types" class="selfRef">Generalized Endpoint Types</a>
            </caption>
<thead>
              <tr>
                <th class="text-left" rowspan="1" colspan="1">Value</th>
                <th class="text-left" rowspan="1" colspan="1">Type</th>
              </tr>
            </thead>
            <tbody>
              <tr>
                <td class="text-left" rowspan="1" colspan="1">0</td>
                <td class="text-left" rowspan="1" colspan="1">Point-to-Point</td>
              </tr>
              <tr>
                <td class="text-left" rowspan="1" colspan="1">1</td>
                <td class="text-left" rowspan="1" colspan="1">Point-to-Multipoint with leaf type 1</td>
              </tr>
              <tr>
                <td class="text-left" rowspan="1" colspan="1">2</td>
                <td class="text-left" rowspan="1" colspan="1">Point-to-Multipoint with leaf type 2</td>
              </tr>
              <tr>
                <td class="text-left" rowspan="1" colspan="1">3</td>
                <td class="text-left" rowspan="1" colspan="1">Point-to-Multipoint with leaf type 3</td>
              </tr>
              <tr>
                <td class="text-left" rowspan="1" colspan="1">4</td>
                <td class="text-left" rowspan="1" colspan="1">Point-to-Multipoint with leaf type 4</td>
              </tr>
              <tr>
                <td class="text-left" rowspan="1" colspan="1">5-244</td>
                <td class="text-left" rowspan="1" colspan="1">Unassigned</td>
              </tr>
              <tr>
                <td class="text-left" rowspan="1" colspan="1">245-255</td>
                <td class="text-left" rowspan="1" colspan="1">Experimental Use</td>
              </tr>
            </tbody>
          </table>
</div>
<p id="section-2.5.1-8">
     The Endpoint Type field is used to cover both point-to-point and
     different point-to-multipoint endpoints.  A PCE may only accept
     endpoint type 0; endpoint types 1-4 apply if the PCE
     implementation supports P2MP path calculation.  The leaf types for P2MP are as per <span>[<a href="#RFC8306" class="xref">RFC8306</a>]</span>. A PCE not
     supporting a given endpoint type <span class="bcp14">SHOULD</span> respond
     with a PCErr with Error-Type=4 (Not supported object) and
     Error-value=7 (Unsupported endpoint type in END-POINTS
     Generalized Endpoint object type).
            As per <span>[<a href="#RFC5440" class="xref">RFC5440</a>]</span>, a PCE unable to
            process Generalized Endpoints may respond with
            Error-Type=3 (Unknown Object) and Error-value=2 (Unrecognized object
            type) or with Error-Type=4 (Not supported object) and
            Error-value=2 (Not supported object Type).

            The TLVs present in the request object body <span class="bcp14">MUST</span> follow
            the grammar per <span>[<a href="#RFC5511" class="xref">RFC5511</a>]</span>:<a href="#section-2.5.1-8" class="pilcrow">¶</a></p>
<div id="section-2.5.1-9">
<pre class="sourcecode lang-rbnf">
  &lt;generalized-endpoint-tlvs&gt;::=
    &lt;p2p-endpoints&gt; | &lt;p2mp-endpoints&gt;

  &lt;p2p-endpoints&gt; ::=
    &lt;endpoint&gt; [&lt;endpoint-restriction-list&gt;]
    &lt;endpoint&gt; [&lt;endpoint-restriction-list&gt;]

  &lt;p2mp-endpoints&gt; ::=
    &lt;endpoint&gt; [&lt;endpoint-restriction-list&gt;]
    &lt;endpoint&gt; [&lt;endpoint-restriction-list&gt;]
    [&lt;endpoint&gt; [&lt;endpoint-restriction-list&gt;]]...
</pre><a href="#section-2.5.1-9" class="pilcrow">¶</a>
</div>
<p id="section-2.5.1-10">For endpoint type Point-to-Point, two endpoint TLVs <span class="bcp14">MUST</span>
   be present in the message. The first endpoint is the source, and the
   second is the destination.<a href="#section-2.5.1-10" class="pilcrow">¶</a></p>
<p id="section-2.5.1-11">For endpoint type Point-to-Multipoint, several END-POINTS objects <span class="bcp14">MAY</span>
   be present in the message, and the exact meaning depends on the
   endpoint type defined for the object. The first endpoint TLV is the
   root, and other endpoint TLVs are the leaves. The root endpoint
   <span class="bcp14">MUST</span> be the same for all END-POINTS objects for that P2MP tree
   request.
   If the root endpoint is not the same for all END-POINTS, a
   PCErr with Error-Type=17 (P2MP END-POINTS Error) and Error-value=4 (The PCE cannot satisfy the
   request due to inconsistent END-POINTS) <span class="bcp14">MUST</span> be returned. The
   procedure defined in <span>[<a href="#RFC8306" class="xref">RFC8306</a>], <a href="https://www.rfc-editor.org/rfc/rfc8306#section-3.10" class="relref">Section 3.10</a></span> also applies
   to the Generalized Endpoint with Point-to-Multipoint endpoint types.<a href="#section-2.5.1-11" class="pilcrow">¶</a></p>
<p id="section-2.5.1-12">An endpoint is defined as follows:<a href="#section-2.5.1-12" class="pilcrow">¶</a></p>
<div id="section-2.5.1-13">
<pre class="sourcecode">
 &lt;endpoint&gt;::=&lt;IPV4-ADDRESS&gt;|&lt;IPV6-ADDRESS&gt;|&lt;UNNUMBERED-ENDPOINT&gt;
 &lt;endpoint-restriction-list&gt; ::= &lt;endpoint-restriction&gt;
                  [&lt;endpoint-restriction-list&gt;]

 &lt;endpoint-restriction&gt; ::=
                  [&lt;LABEL-REQUEST&gt;][&lt;label-restriction-list&gt;]

 &lt;label-restriction-list&gt; ::= &lt;label-restriction&gt;
                              [&lt;label-restriction-list&gt;]
 &lt;label-restriction&gt; ::= &lt;LABEL-SET&gt;
</pre><a href="#section-2.5.1-13" class="pilcrow">¶</a>
</div>
<p id="section-2.5.1-14">The different TLVs are described in the following sections.  A PCE <span class="bcp14">MAY</span> support any or all of the IPV4-ADDRESS, IPV6-ADDRESS, and UNNUMBERED-ENDPOINT TLVs.


          When receiving a PCReq, a PCE unable to resolve the identifier in one of
          those TLVs <span class="bcp14">MUST</span> respond by using a PCRep with NO-PATH and setting the bit
          "Unknown destination" or "Unknown source" in the NO-PATH-VECTOR TLV.
          The response <span class="bcp14">SHOULD</span> include the END-POINTS object with only the unsupported TLV(s).<a href="#section-2.5.1-14" class="pilcrow">¶</a></p>
<p id="section-2.5.1-15">
            A PCE <span class="bcp14">MAY</span> support either or both of the
            LABEL-REQUEST and LABEL-SET TLVs.

            If a PCE finds a non-supported TLV in the END-POINTS, the PCE
            <span class="bcp14">MUST</span> respond with a PCErr message with Error-Type=4
            (Not supported object) and Error-value=8 (Unsupported TLV present
            in END-POINTS Generalized Endpoint object type), and the message
            <span class="bcp14">SHOULD</span> include the END-POINTS object in the
            response with only the endpoint and endpoint restriction TLV it
            did not understand.  A PCE supporting those TLVs but not being
            able to fulfill the label restriction <span class="bcp14">MUST</span> send a
            response with a NO-PATH object that has the bit "No endpoint label
            resource" or "No endpoint label resource in range" set in the
            NO-PATH-VECTOR TLV.  The response <span class="bcp14">SHOULD</span> include an
            END-POINTS object containing only the TLV(s) related to the
            constraints the PCE could not meet.<a href="#section-2.5.1-15" class="pilcrow">¶</a></p>
</section>
</div>
<div id="endpoints_tlvs">
<section id="section-2.5.2">
          <h4 id="name-end-points-tlv-extensions">
<a href="#section-2.5.2" class="section-number selfRef">2.5.2. </a><a href="#name-end-points-tlv-extensions" class="section-name selfRef">END-POINTS TLV Extensions</a>
          </h4>
<p id="section-2.5.2-1">All endpoint TLVs have the standard PCEP TLV header as defined in <span>[<a href="#RFC5440" class="xref">RFC5440</a>], <a href="https://www.rfc-editor.org/rfc/rfc5440#section-7.1" class="relref">Section 7.1</a></span>. For the Generalized Endpoint object type, the TLVs <span class="bcp14">MUST</span> follow the ordering defined in <a href="#endpoints_generalized" class="xref">Section 2.5.1</a>.<a href="#section-2.5.2-1" class="pilcrow">¶</a></p>
<div id="endpoints_tlvs_ipv4">
<section id="section-2.5.2.1">
            <h5 id="name-ipv4-address-tlv">
<a href="#section-2.5.2.1" class="section-number selfRef">2.5.2.1. </a><a href="#name-ipv4-address-tlv" class="section-name selfRef">IPV4-ADDRESS TLV</a>
            </h5>
<p id="section-2.5.2.1-1">The IPV4-ADDRESS TLV (Type 39) represents a numbered endpoint
            using IPv4 numbering. The format of the TLV value is as follows:<a href="#section-2.5.2.1-1" class="pilcrow">¶</a></p>
<div class="artwork art-text alignLeft" id="section-2.5.2.1-2">
<pre>
   0                   1                   2                   3
   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
  +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
  |                          IPv4 address                         |
  +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
</pre><a href="#section-2.5.2.1-2" class="pilcrow">¶</a>
</div>
<p id="section-2.5.2.1-3">
            This TLV <span class="bcp14">MAY</span> be ignored, in which case a PCRep with NO-PATH <span class="bcp14">SHOULD</span> be returned, as described in <a href="#endpoints_generalized" class="xref">Section 2.5.1</a>.<a href="#section-2.5.2.1-3" class="pilcrow">¶</a></p>
</section>
</div>
<div id="endpoints_tlvs_ipv6">
<section id="section-2.5.2.2">
            <h5 id="name-ipv6-address-tlv">
<a href="#section-2.5.2.2" class="section-number selfRef">2.5.2.2. </a><a href="#name-ipv6-address-tlv" class="section-name selfRef">IPV6-ADDRESS TLV</a>
            </h5>
<p id="section-2.5.2.2-1">The IPv6-ADDRESS TLV (Type 40) represents a numbered endpoint
            using IPV6 numbering.  The format of the TLV value is as follows:<a href="#section-2.5.2.2-1" class="pilcrow">¶</a></p>
<div class="artwork art-text alignLeft" id="section-2.5.2.2-2">
<pre>
   0                   1                   2                   3
   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
  +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
  |              IPv6 address (16 bytes)                          |
  |                                                               |
  |                                                               |
  |                                                               |
  +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
</pre><a href="#section-2.5.2.2-2" class="pilcrow">¶</a>
</div>
<p id="section-2.5.2.2-3">
            This TLV <span class="bcp14">MAY</span> be ignored, in which case a PCRep with NO-PATH <span class="bcp14">SHOULD</span> be returned, as described in <a href="#endpoints_generalized" class="xref">Section 2.5.1</a>.<a href="#section-2.5.2.2-3" class="pilcrow">¶</a></p>
</section>
</div>
<div id="endpoints_tlvs_unnumbered-if">
<section id="section-2.5.2.3">
            <h5 id="name-unnumbered-endpoint-tlv">
<a href="#section-2.5.2.3" class="section-number selfRef">2.5.2.3. </a><a href="#name-unnumbered-endpoint-tlv" class="section-name selfRef">UNNUMBERED-ENDPOINT TLV</a>
            </h5>
<p id="section-2.5.2.3-1">The UNNUMBERED-ENDPOINT TLV (Type 41) represents an unnumbered interface. This TLV has the
            same semantic as in <span>[<a href="#RFC3477" class="xref">RFC3477</a>]</span>.
            The TLV value is encoded as follows:<a href="#section-2.5.2.3-1" class="pilcrow">¶</a></p>
<div class="artwork art-text alignLeft" id="section-2.5.2.3-2">
<pre>
   0                   1                   2                   3
   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
  +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
  |                          LSR's Router ID                      |
  +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
  |                       Interface ID (32 bits)                  |
  +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
</pre><a href="#section-2.5.2.3-2" class="pilcrow">¶</a>
</div>
<p id="section-2.5.2.3-3">
            This TLV <span class="bcp14">MAY</span> be ignored, in which case a PCRep with NO-PATH <span class="bcp14">SHOULD</span> be returned, as described in <a href="#endpoints_generalized" class="xref">Section 2.5.1</a>.<a href="#section-2.5.2.3-3" class="pilcrow">¶</a></p>
</section>
</div>
<div id="endpoints_tlvs_label-request">
<section id="section-2.5.2.4">
            <h5 id="name-label-request-tlv">
<a href="#section-2.5.2.4" class="section-number selfRef">2.5.2.4. </a><a href="#name-label-request-tlv" class="section-name selfRef">LABEL-REQUEST TLV</a>
            </h5>
<p id="section-2.5.2.4-1">The LABEL-REQUEST TLV (Type 42) indicates the switching
            capability and encoding type of the following label restriction
            list for the endpoint. The value format and encoding is the same
            as described in <span><a href="https://www.rfc-editor.org/rfc/rfc3471#section-3.1" class="relref">Section 3.1</a> of [<a href="#RFC3471" class="xref">RFC3471</a>]</span> for the Generalized Label Request. The LSP
            Encoding Type field indicates the encoding type, e.g., SONET, SDH,
            GigE, etc., of the LSP with which the data is associated. The
            Switching Type field indicates the type of switching that is being
            requested on the endpoint. The Generalized Protocol Identifier
            (G-PID) field identifies the payload. This TLV and the following
            one are defined to satisfy requirement 13 in <span><a href="https://www.rfc-editor.org/rfc/rfc7025#section-3.1" class="relref">Section 3.1</a> of [<a href="#RFC7025" class="xref">RFC7025</a>]</span> for the
            endpoint. It is not directly related to the TE-LSP label request,
            which is expressed by the SWITCH-LAYER object.<a href="#section-2.5.2.4-1" class="pilcrow">¶</a></p>
<p id="section-2.5.2.4-2">
            On the path calculation request, only the GENERALIZED-BANDWIDTH and SWITCH-LAYER need to be coherent; the endpoint labels could be different (supporting a different LABEL-REQUEST). Hence, the label restrictions include a Generalized Label Request in order to interpret the labels.
            This TLV <span class="bcp14">MAY</span> be ignored, in which case a PCRep with NO-PATH <span class="bcp14">SHOULD</span> be returned, as described in <a href="#endpoints_generalized" class="xref">Section 2.5.1</a>.<a href="#section-2.5.2.4-2" class="pilcrow">¶</a></p>
</section>
</div>
<div id="endpoints_tlvs_labels">
<section id="section-2.5.2.5">
            <h5 id="name-label-set-tlv">
<a href="#section-2.5.2.5" class="section-number selfRef">2.5.2.5. </a><a href="#name-label-set-tlv" class="section-name selfRef">LABEL-SET TLV</a>
            </h5>
<p id="section-2.5.2.5-1">Label or label range restrictions can be specified for the
            TE-LSP endpoints. Those are encoded using the LABEL-SET TLV. The
            label value needs to be interpreted with a description on the
            encoding and switching type. The REQ-ADAP-CAP object <span>[<a href="#RFC8282" class="xref">RFC8282</a>]</span> can be used in case of a
            mono-layer request; however, in case of a multi-layer request, it
            is possible to have more than one object, so it is better to have
            a dedicated TLV for the label and label request.  These TLVs
            <span class="bcp14">MAY</span> be ignored, in which case a response with
            NO-PATH <span class="bcp14">SHOULD</span> be returned, as described in <a href="#endpoints_generalized" class="xref">Section 2.5.1</a>.  Per <span>[<a href="#RFC5440" class="xref">RFC5440</a>]</span>, the LABEL-SET TLV is encoded as follows.
            The type of the LABEL-SET TLV is 43. The TLV Length is
            variable, and the value encoding follows <span><a href="https://www.rfc-editor.org/rfc/rfc3471#section-3.5" class="relref">Section 3.5</a> of [<a href="#RFC3471" class="xref">RFC3471</a>]</span>, with
            the addition of a U bit, O bit, and L bit. 

            The L bit is
            used to represent a suggested set of labels, following
              the semantic of Suggested Label as defined by <span>[<a href="#RFC3471" class="xref">RFC3471</a>]</span>.<a href="#section-2.5.2.5-1" class="pilcrow">¶</a></p>
<div class="artwork art-text alignLeft" id="section-2.5.2.5-2">
<pre>
  0                   1                   2                   3
  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
 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
 |    Action     |    Reserved |L|O|U|        Label Type         |
 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
 |                          Subchannel 1                         |
 |                              ...                              |
 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
 :                               :                               :
 :                               :                               :
 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
 |                          Subchannel N                         |
 |                              ...                              |
 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
</pre><a href="#section-2.5.2.5-2" class="pilcrow">¶</a>
</div>
<p id="section-2.5.2.5-3">
       A LABEL-SET TLV represents a set of possible labels that
              can be used on an interface. If the L bit is cleared,
              the label allocated on the first endpoint <span class="bcp14">MUST</span> be within the label set range. The Action parameter in the LABEL-SET indicates the type of list provided. These parameters are described by <span>[<a href="#RFC3471" class="xref">RFC3471</a>], <a href="https://www.rfc-editor.org/rfc/rfc3471#section-3.5.1" class="relref">Section 3.5.1</a></span>.<a href="#section-2.5.2.5-3" class="pilcrow">¶</a></p>
<p id="section-2.5.2.5-4">
              The U, O, and L bits are defined as follows:<a href="#section-2.5.2.5-4" class="pilcrow">¶</a></p>
<ul class="ulEmpty normal">
<li class="ulEmpty normal" id="section-2.5.2.5-5.1">
                <span class="break"></span><dl class="dlParallel" id="section-2.5.2.5-5.1.1">
                  <dt id="section-2.5.2.5-5.1.1.1">U:</dt>
                  <dd style="margin-left: 2.5em" id="section-2.5.2.5-5.1.1.2">Upstream direction. Set for the upstream (reverse)
                  direction in case of bidirectional LSP.<a href="#section-2.5.2.5-5.1.1.2" class="pilcrow">¶</a>
</dd>
                  <dd class="break"></dd>
<dt id="section-2.5.2.5-5.1.1.3">O:</dt>
                  <dd style="margin-left: 2.5em" id="section-2.5.2.5-5.1.1.4">Old label. Set when the TLV represents the old
                (previously allocated) label in case of reoptimization.  The R
                bit of the RP object <span class="bcp14">MUST</span> be set to 1. If the L
                bit is set, this bit <span class="bcp14">SHOULD</span> be set to 0 and
                ignored on receipt.  When this bit is set, the Action field
                <span class="bcp14">MUST</span> be set to 0 (Inclusive List), and the
                 LABEL-SET <span class="bcp14">MUST</span> contain one subchannel.<a href="#section-2.5.2.5-5.1.1.4" class="pilcrow">¶</a>
</dd>
                  <dd class="break"></dd>
<dt id="section-2.5.2.5-5.1.1.5">L:</dt>
                  <dd style="margin-left: 2.5em" id="section-2.5.2.5-5.1.1.6">Loose label. Set when the TLV indicates to the
               PCE that a set of preferred (ordered) labels are to be
               used. The PCE <span class="bcp14">MAY</span> use those labels for label
               allocation.<a href="#section-2.5.2.5-5.1.1.6" class="pilcrow">¶</a>
</dd>
                <dd class="break"></dd>
</dl>
</li>
            </ul>
<p id="section-2.5.2.5-6">
              Several LABEL_SET TLVs <span class="bcp14">MAY</span> be present with the O bit
              cleared; LABEL_SET TLVs with the L bit set can
              be combined with a LABEL_SET TLV with the L bit cleared.

              There <span class="bcp14">MUST NOT</span> be more than two LABEL_SET TLVs present with the
              O bit set. If there are two LABEL_SET TLVs present, there <span class="bcp14">MUST NOT</span>
              be more than one with the U bit set, and there <span class="bcp14">MUST NOT</span> be more
              than one with the U bit cleared. For a
              given U bit value, if more than one LABEL_SET TLV with the O bit set
              is present, the first TLV <span class="bcp14">MUST</span> be processed, and the following TLVs
              that have the same U and O bits <span class="bcp14">MUST</span> be ignored.<a href="#section-2.5.2.5-6" class="pilcrow">¶</a></p>
<p id="section-2.5.2.5-7">
              A LABEL-SET TLV with the O and L bits set <span class="bcp14">MUST</span> trigger a
              PCErr message with Error-Type=10 (Reception of an invalid
              object) and Error-value=29 (Wrong LABEL-SET TLV present with O
              and L bits set).<a href="#section-2.5.2.5-7" class="pilcrow">¶</a></p>
<p id="section-2.5.2.5-8">
              A LABEL-SET TLV that has the O bit set and an Action field
              not set to 0 (Inclusive List) or that contains more than
              one subchannel <span class="bcp14">MUST</span> trigger a PCErr message with Error-Type=10 (Reception of an invalid object) and Error-value=30 (Wrong
              LABEL-SET TLV present with O bit set and wrong format).<a href="#section-2.5.2.5-8" class="pilcrow">¶</a></p>
<p id="section-2.5.2.5-9">If a LABEL-SET TLV is present with the O bit set, the R bit of
            the RP object <span class="bcp14">MUST</span> be set; otherwise, a PCErr
            message <span class="bcp14">MUST</span> be sent with Error-Type=10 (Reception
            of an invalid object) and Error-value=28 (LABEL-SET TLV
            present with O bit set but without R bit set in RP).<a href="#section-2.5.2.5-9" class="pilcrow">¶</a></p>
</section>
</div>
</section>
</div>
</section>
</div>
<div id="iro-label">
<section id="section-2.6">
        <h3 id="name-iro-extension">
<a href="#section-2.6" class="section-number selfRef">2.6. </a><a href="#name-iro-extension" class="section-name selfRef">IRO Extension</a>
        </h3>
<p id="section-2.6-1">The IRO as defined in <span>[<a href="#RFC5440" class="xref">RFC5440</a>]</span> is used to
  include specific objects in the path. RSVP-TE allows the inclusion of a
  label definition. In order to fulfill requirement 13 in <span><a href="https://www.rfc-editor.org/rfc/rfc7025#section-3.1" class="relref">Section 3.1</a> of [<a href="#RFC7025" class="xref">RFC7025</a>]</span>, the IRO needs to support the new subobject type as defined in <span>[<a href="#RFC3473" class="xref">RFC3473</a>]</span>:<a href="#section-2.6-1" class="pilcrow">¶</a></p>
<table class="center" id="table-5">
          <caption><a href="#table-5" class="selfRef">Table 5</a></caption>
<thead>
            <tr>
              <th class="text-left" rowspan="1" colspan="1">Type</th>
              <th class="text-left" rowspan="1" colspan="1">Subobject</th>
            </tr>
          </thead>
          <tbody>
            <tr>
              <td class="text-left" rowspan="1" colspan="1">10</td>
              <td class="text-left" rowspan="1" colspan="1">Label</td>
            </tr>
          </tbody>
        </table>
<p id="section-2.6-3">The Label subobject <span class="bcp14">MUST</span> follow a subobject
        identifying a link, currently an IP address subobject (Type 1 or 2) or
        an interface ID (Type 4) subobject.  If an IP address subobject is
        used, then the given IP address <span class="bcp14">MUST</span> be associated with
        a link.  More than one Label subobject <span class="bcp14">MAY</span> follow each
        subobject identifying a link.  The procedure associated with this subobject is as
        follows.<a href="#section-2.6-3" class="pilcrow">¶</a></p>
<p id="section-2.6-4">
 If the PCE is able to allocate labels (e.g., via explicit label control), the
 PCE <span class="bcp14">MUST</span> allocate one label from within the set of label
 values for the given link.  If the PCE does not assign labels, then it sends
 a response with a NO-PATH object, containing a NO-PATH-VECTOR TLV with the
 bit "No label resource in range" set.<a href="#section-2.6-4" class="pilcrow">¶</a></p>
</section>
</div>
<div id="xro-label">
<section id="section-2.7">
        <h3 id="name-xro-extension">
<a href="#section-2.7" class="section-number selfRef">2.7. </a><a href="#name-xro-extension" class="section-name selfRef">XRO Extension</a>
        </h3>
<p id="section-2.7-1">The XRO as defined in <span>[<a href="#RFC5521" class="xref">RFC5521</a>]</span> is used to
  exclude specific objects in the path. RSVP-TE allows the exclusion of certain
  labels <span>[<a href="#RFC6001" class="xref">RFC6001</a>]</span>. In order to fulfill requirement
  13 in <span><a href="https://www.rfc-editor.org/rfc/rfc7025#section-3.1" class="relref">Section 3.1</a> of [<a href="#RFC7025" class="xref">RFC7025</a>]</span>, the PCEP's XRO needs to
  support a new subobject to enable label exclusion.<a href="#section-2.7-1" class="pilcrow">¶</a></p>
<p id="section-2.7-2">
   The encoding of the XRO Label subobject follows the encoding
   of the ERO Label subobject defined in <span>[<a href="#RFC3473" class="xref">RFC3473</a>]</span> and the XRO subobject defined in <span>[<a href="#RFC5521" class="xref">RFC5521</a>]</span>. The
   XRO Label subobject (Type 10) represents one label and is defined as follows:<a href="#section-2.7-2" class="pilcrow">¶</a></p>
<div class="artwork art-text alignLeft" id="section-2.7-3">
<pre>
 0                   1                   2                   3
 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
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|X|    Type=10  |    Length     |U|   Reserved  |   C-Type      |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|                             Label                             |
|                              ...                              |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
</pre><a href="#section-2.7-3" class="pilcrow">¶</a>
</div>
<span class="break"></span><dl class="dlParallel" id="section-2.7-4">
          <dt id="section-2.7-4.1">X (1 bit):</dt>
          <dd id="section-2.7-4.2">See <span>[<a href="#RFC5521" class="xref">RFC5521</a>]</span>.  The X bit indicates whether the exclusion is
          mandatory or desired.  0 indicates that the resource specified
          <span class="bcp14">MUST</span> be excluded from the path computed by the PCE. 1
          indicates that the resource specified <span class="bcp14">SHOULD</span> be
          excluded from the path computed by the PCE, but it
          <span class="bcp14">MAY</span> be included subject to the PCE policy and the
          absence of a viable path that meets the other constraints and
          excludes the resource.<a href="#section-2.7-4.2" class="pilcrow">¶</a>
</dd>
          <dd class="break"></dd>
<dt id="section-2.7-4.3">Type (7 bits):</dt>
          <dd id="section-2.7-4.4">The type of the XRO Label subobject is
   10.<a href="#section-2.7-4.4" class="pilcrow">¶</a>
</dd>
          <dd class="break"></dd>
<dt id="section-2.7-4.5">Length (8 bits):</dt>
          <dd id="section-2.7-4.6">See <span>[<a href="#RFC5521" class="xref">RFC5521</a>]</span>. The total length of the subobject in bytes
          (including the Type and Length fields). The length is always
          divisible by 4.<a href="#section-2.7-4.6" class="pilcrow">¶</a>
</dd>
          <dd class="break"></dd>
<dt id="section-2.7-4.7">U (1 bit):</dt>
          <dd id="section-2.7-4.8">See <span>[<a href="#RFC3471" class="xref">RFC3471</a>], <a href="https://www.rfc-editor.org/rfc/rfc3471#section-6.1" class="relref">Section 6.1</a></span>.<a href="#section-2.7-4.8" class="pilcrow">¶</a>
</dd>
          <dd class="break"></dd>
<dt id="section-2.7-4.9">C-Type (8 bits):</dt>
          <dd id="section-2.7-4.10">The C-Type of the included Label object
   as defined in <span>[<a href="#RFC3473" class="xref">RFC3473</a>]</span>.<a href="#section-2.7-4.10" class="pilcrow">¶</a>
</dd>
          <dd class="break"></dd>
<dt id="section-2.7-4.11">Label:</dt>
          <dd id="section-2.7-4.12">See <span>[<a href="#RFC3471" class="xref">RFC3471</a>]</span>.<a href="#section-2.7-4.12" class="pilcrow">¶</a>
</dd>
        <dd class="break"></dd>
</dl>
<p id="section-2.7-5">
    The Label subobject <span class="bcp14">MUST</span> follow a subobject identifying a link,
   currently an IP address subobject (Type 1 or 2) or an interface ID
   (Type 4) subobject. If an IP address subobject is used, the
   given IP address <span class="bcp14">MUST</span> be associated with a link. More than one
   label subobject <span class="bcp14">MAY</span> follow a subobject identifying a link.<a href="#section-2.7-5" class="pilcrow">¶</a></p>
<table class="center" id="table-6">
          <caption><a href="#table-6" class="selfRef">Table 6</a></caption>
<thead>
            <tr>
              <th class="text-left" rowspan="1" colspan="1">Type</th>
              <th class="text-left" rowspan="1" colspan="1">Subobject</th>
            </tr>
          </thead>
          <tbody>
            <tr>
              <td class="text-left" rowspan="1" colspan="1">10</td>
              <td class="text-left" rowspan="1" colspan="1">Label</td>
            </tr>
          </tbody>
        </table>
</section>
</div>
<div id="lspa">
<section id="section-2.8">
        <h3 id="name-lspa-extensions">
<a href="#section-2.8" class="section-number selfRef">2.8. </a><a href="#name-lspa-extensions" class="section-name selfRef">LSPA Extensions</a>
        </h3>
<p id="section-2.8-1">
          The LSPA carries the LSP attributes. In the end-to-end
          recovery context, this also includes the protection state information.
          A new TLV is defined to fulfill requirement 7 in <span><a href="https://www.rfc-editor.org/rfc/rfc7025#section-3.1" class="relref">Section 3.1</a> of [<a href="#RFC7025" class="xref">RFC7025</a>]</span> and requirement 3 in <span><a href="https://www.rfc-editor.org/rfc/rfc7025#section-3.2" class="relref">Section 3.2</a> of [<a href="#RFC7025" class="xref">RFC7025</a>]</span>. This TLV contains the information of the PROTECTION object defined by <span>[<a href="#RFC4872" class="xref">RFC4872</a>]</span> and can be used as a policy input.
          The LSPA object <span class="bcp14">MAY</span> carry a PROTECTION-ATTRIBUTE TLV
 (Type 44), which is defined as follows:<a href="#section-2.8-1" class="pilcrow">¶</a></p>
<div class="artwork art-text alignLeft" id="section-2.8-2">
<pre>
   0                   1                   2                   3
   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
  +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
  |         Type                  |  Length                       |
  +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
  |S|P|N|O|  Reserved | LSP Flags |     Reserved      | Link Flags|
  +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
  |I|R|   Reserved    | Seg.Flags |           Reserved            |
  +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
</pre><a href="#section-2.8-2" class="pilcrow">¶</a>
</div>
<p id="section-2.8-3">The content is as defined in <span>[<a href="#RFC4872" class="xref">RFC4872</a>], <a href="https://www.rfc-editor.org/rfc/rfc4872#section-14" class="relref">Section 14</a></span> and <span>[<a href="#RFC4873" class="xref">RFC4873</a>], <a href="https://www.rfc-editor.org/rfc/rfc4873#section-6.1" class="relref">Section 6.1</a></span>.<a href="#section-2.8-3" class="pilcrow">¶</a></p>
<p id="section-2.8-4">The LSP (protection) Flags field or the Link Flags field can be used by a
        PCE implementation for routing policy input. The other attributes are only meaningful for a stateful PCE.<a href="#section-2.8-4" class="pilcrow">¶</a></p>
<p id="section-2.8-5">This TLV is <span class="bcp14">OPTIONAL</span> and <span class="bcp14">MAY</span> be ignored by the PCE. If ignored by the PCE, it
   <span class="bcp14">MUST NOT</span> include the TLV in the LSPA of the response.
        When the TLV is used by the PCE, an LSPA object and the PROTECTION-ATTRIBUTE TLV <span class="bcp14">MUST</span> be included in the response. Fields that were not considered <span class="bcp14">MUST</span> be set to 0.<a href="#section-2.8-5" class="pilcrow">¶</a></p>
</section>
</div>
<section id="section-2.9">
        <h3 id="name-no-path-object-extension">
<a href="#section-2.9" class="section-number selfRef">2.9. </a><a href="#name-no-path-object-extension" class="section-name selfRef">NO-PATH Object Extension</a>
        </h3>
<p id="section-2.9-1">
          The NO-PATH object is used in PCRep messages in response to an
          unsuccessful Path Computation Request (the PCE could not find a path
           satisfying the set of constraints). In this scenario, the PCE <span class="bcp14">MUST</span>
          include a NO-PATH object in the PCRep message.

          The NO-PATH object <span class="bcp14">MAY</span> carry the NO-PATH-VECTOR TLV that specifies more
          information on the reasons that led to a negative reply. In case of
          GMPLS networks, there could be some additional constraints that
          led to the failure such as protection mismatch, lack of resources, and
          so on. Several new flags have been defined in the 32-bit Flag field of the
          NO-PATH-VECTOR TLV, but no modifications have been made in the NO-PATH
          object.<a href="#section-2.9-1" class="pilcrow">¶</a></p>
<div id="no-path_bits">
<section id="section-2.9.1">
          <h4 id="name-extensions-to-no-path-vecto">
<a href="#section-2.9.1" class="section-number selfRef">2.9.1. </a><a href="#name-extensions-to-no-path-vecto" class="section-name selfRef">Extensions to NO-PATH-VECTOR TLV</a>
          </h4>
<p id="section-2.9.1-1">
            The modified NO-PATH-VECTOR TLV carrying the additional information
            is as follows:<a href="#section-2.9.1-1" class="pilcrow">¶</a></p>
<ul class="ulEmpty normal">
<li class="ulEmpty normal" id="section-2.9.1-2.1">
              <span class="break"></span><dl class="dlParallel" id="section-2.9.1-2.1.1">
                <dt id="section-2.9.1-2.1.1.1">Bit number 18:</dt>
                <dd id="section-2.9.1-2.1.1.2">Protection Mismatch (1 bit). Specifies the mismatch of the protection type in the PROTECTION-ATTRIBUTE TLV in the request.<a href="#section-2.9.1-2.1.1.2" class="pilcrow">¶</a>
</dd>
                <dd class="break"></dd>
<dt id="section-2.9.1-2.1.1.3">Bit number 17:</dt>
                <dd id="section-2.9.1-2.1.1.4">No Resource (1 bit). Specifies that the resources are not currently sufficient to provide the path.<a href="#section-2.9.1-2.1.1.4" class="pilcrow">¶</a>
</dd>
                <dd class="break"></dd>
<dt id="section-2.9.1-2.1.1.5">Bit number 16:</dt>
                <dd id="section-2.9.1-2.1.1.6">Granularity not supported
              (1 bit). Specifies that the PCE is not able to provide a
              path with the requested granularity.<a href="#section-2.9.1-2.1.1.6" class="pilcrow">¶</a>
</dd>
                <dd class="break"></dd>
<dt id="section-2.9.1-2.1.1.7">Bit number 15:</dt>
                <dd id="section-2.9.1-2.1.1.8">No endpoint label resource (1 bit). Specifies that the PCE is not able to provide a path because of the endpoint label restriction.<a href="#section-2.9.1-2.1.1.8" class="pilcrow">¶</a>
</dd>
                <dd class="break"></dd>
<dt id="section-2.9.1-2.1.1.9">Bit number 14:</dt>
                <dd id="section-2.9.1-2.1.1.10">No endpoint label resource in range (1 bit). Specifies that the PCE is not able to provide a path because of the endpoint label set restriction.<a href="#section-2.9.1-2.1.1.10" class="pilcrow">¶</a>
</dd>
                <dd class="break"></dd>
<dt id="section-2.9.1-2.1.1.11">Bit number 13:</dt>
                <dd id="section-2.9.1-2.1.1.12">No label resource in range (1
            bit). Specifies that the PCE is not able to provide a path because
            of the label set restriction.<a href="#section-2.9.1-2.1.1.12" class="pilcrow">¶</a>
</dd>
                <dd class="break"></dd>
<dt id="section-2.9.1-2.1.1.13">Bit number 12:</dt>
                <dd id="section-2.9.1-2.1.1.14">LOAD-BALANCING could not be performed
            with the bandwidth constraints (1 bit).  Specifies that the PCE is
            not able to provide a path because it could not map the BANDWIDTH
            into the parameters specified by the LOAD-BALANCING.<a href="#section-2.9.1-2.1.1.14" class="pilcrow">¶</a>
</dd>
              <dd class="break"></dd>
</dl>
</li>
          </ul>
</section>
</div>
</section>
</section>
<div id="error-codes">
<section id="section-3">
      <h2 id="name-additional-error-types-and-">
<a href="#section-3" class="section-number selfRef">3. </a><a href="#name-additional-error-types-and-" class="section-name selfRef">Additional Error-Types and Error-Values Defined</a>
      </h2>
<p id="section-3-1">
        A PCEP-ERROR object is used to report a PCEP error and is
        characterized by an Error-Type that specifies the type of error and an
        Error-value that provides additional information about the error. An
        additional Error-Type and several Error-values are defined to
        represent some of the errors related to the newly identified objects,
        which are related to GMPLS networks.

        For each PCEP error, an Error-Type and an Error-value are defined.
        Error-Types 1 to 10 are already defined in <span>[<a href="#RFC5440" class="xref">RFC5440</a>]</span>. Additional Error-values are defined for
 Error-Types 4 and 10. A new Error-Type 29 (Path computation failure)
        is defined in this document.<a href="#section-3-1" class="pilcrow">¶</a></p>
<p id="section-3-2">
        Error-Type 29 (Path computation failure) is used to reflect
        constraints not understood by the PCE, for instance, when the PCE is
        not able to understand the Generalized bandwidth. If the constraints
        are understood, but the PCE is unable to find those constraints,
        NO-PATH is to be used.<a href="#section-3-2" class="pilcrow">¶</a></p>
<table class="center" id="table-7">
        <caption><a href="#table-7" class="selfRef">Table 7</a></caption>
<thead>
          <tr>
            <th class="text-left" rowspan="1" colspan="1">Error-Type</th>
            <th class="text-left" rowspan="1" colspan="1">Meaning</th>
            <th class="text-left" rowspan="1" colspan="1">Error-value</th>
          </tr>
        </thead>
        <tbody>
          <tr>
            <td class="text-left" rowspan="1" colspan="1">4</td>
            <td class="text-left" rowspan="1" colspan="1">Not supported object</td>
            <td class="text-left" rowspan="1" colspan="1"></td>
          </tr>
          <tr>
            <td class="text-left" rowspan="1" colspan="1"></td>
            <td class="text-left" rowspan="1" colspan="1"></td>
            <td class="text-left" rowspan="1" colspan="1">6: BANDWIDTH object type 3 or 4 not supported</td>
          </tr>
          <tr>
            <td class="text-left" rowspan="1" colspan="1"></td>
            <td class="text-left" rowspan="1" colspan="1"></td>
            <td class="text-left" rowspan="1" colspan="1">7: Unsupported endpoint type in END-POINTS
              Generalized Endpoint object type</td>
          </tr>
          <tr>
            <td class="text-left" rowspan="1" colspan="1"></td>
            <td class="text-left" rowspan="1" colspan="1"></td>
            <td class="text-left" rowspan="1" colspan="1">8: Unsupported TLV present in END-POINTS
              Generalized Endpoint object type</td>
          </tr>
          <tr>
            <td class="text-left" rowspan="1" colspan="1"></td>
            <td class="text-left" rowspan="1" colspan="1"></td>
            <td class="text-left" rowspan="1" colspan="1">9: Unsupported granularity in the RP object
       flags</td>
          </tr>
          <tr>
            <td class="text-left" rowspan="1" colspan="1">10</td>
            <td class="text-left" rowspan="1" colspan="1">Reception of an invalid object </td>
            <td class="text-left" rowspan="1" colspan="1"></td>
          </tr>
          <tr>
            <td class="text-left" rowspan="1" colspan="1"></td>
            <td class="text-left" rowspan="1" colspan="1"></td>
            <td class="text-left" rowspan="1" colspan="1">24: Bad BANDWIDTH object type 3 or 4</td>
          </tr>
          <tr>
            <td class="text-left" rowspan="1" colspan="1"></td>
            <td class="text-left" rowspan="1" colspan="1"></td>
            <td class="text-left" rowspan="1" colspan="1">25: Unsupported LSP Protection Flags in
              PROTECTION-ATTRIBUTE TLV</td>
          </tr>
          <tr>
            <td class="text-left" rowspan="1" colspan="1"></td>
            <td class="text-left" rowspan="1" colspan="1"></td>
            <td class="text-left" rowspan="1" colspan="1">26: Unsupported Secondary LSP Protection Flags
              in PROTECTION-ATTRIBUTE TLV</td>
          </tr>
          <tr>
            <td class="text-left" rowspan="1" colspan="1"></td>
            <td class="text-left" rowspan="1" colspan="1"></td>
            <td class="text-left" rowspan="1" colspan="1">27: Unsupported Link Protection Type in
              PROTECTION-ATTRIBUTE TLV</td>
          </tr>
          <tr>
            <td class="text-left" rowspan="1" colspan="1"></td>
            <td class="text-left" rowspan="1" colspan="1"></td>
            <td class="text-left" rowspan="1" colspan="1">28: LABEL-SET TLV present with O bit set but
              without R bit set in RP</td>
          </tr>
          <tr>
            <td class="text-left" rowspan="1" colspan="1"></td>
            <td class="text-left" rowspan="1" colspan="1"></td>
            <td class="text-left" rowspan="1" colspan="1">29: Wrong LABEL-SET TLV present with O and L
       bits set</td>
          </tr>
          <tr>
            <td class="text-left" rowspan="1" colspan="1"></td>
            <td class="text-left" rowspan="1" colspan="1"></td>
            <td class="text-left" rowspan="1" colspan="1">30: Wrong LABEL-SET TLV present with O bit set and wrong
       format</td>
          </tr>
          <tr>
            <td class="text-left" rowspan="1" colspan="1"></td>
            <td class="text-left" rowspan="1" colspan="1"></td>
            <td class="text-left" rowspan="1" colspan="1">31: Missing GMPLS-CAPABILITY TLV</td>
          </tr>
          <tr>
            <td class="text-left" rowspan="1" colspan="1">29</td>
            <td class="text-left" rowspan="1" colspan="1">Path computation failure</td>
            <td class="text-left" rowspan="1" colspan="1"></td>
          </tr>
          <tr>
            <td class="text-left" rowspan="1" colspan="1"></td>
            <td class="text-left" rowspan="1" colspan="1"></td>
            <td class="text-left" rowspan="1" colspan="1">0: Unassigned</td>
          </tr>
          <tr>
            <td class="text-left" rowspan="1" colspan="1"></td>
            <td class="text-left" rowspan="1" colspan="1"></td>
            <td class="text-left" rowspan="1" colspan="1">1: Unacceptable request message</td>
          </tr>
          <tr>
            <td class="text-left" rowspan="1" colspan="1"></td>
            <td class="text-left" rowspan="1" colspan="1"></td>
            <td class="text-left" rowspan="1" colspan="1">2: Generalized bandwidth value not
       supported</td>
          </tr>
          <tr>
            <td class="text-left" rowspan="1" colspan="1"></td>
            <td class="text-left" rowspan="1" colspan="1"></td>
            <td class="text-left" rowspan="1" colspan="1">3: Label set constraint could not be met</td>
          </tr>
          <tr>
            <td class="text-left" rowspan="1" colspan="1"></td>
            <td class="text-left" rowspan="1" colspan="1"></td>
            <td class="text-left" rowspan="1" colspan="1">4: Label constraint could not be met</td>
          </tr>
        </tbody>
      </table>
</section>
</div>
<section id="section-4">
      <h2 id="name-manageability-consideration">
<a href="#section-4" class="section-number selfRef">4. </a><a href="#name-manageability-consideration" class="section-name selfRef">Manageability Considerations</a>
      </h2>
<p id="section-4-1">This section follows the guidance of <span>[<a href="#RFC6123" class="xref">RFC6123</a>]</span>.<a href="#section-4-1" class="pilcrow">¶</a></p>
<section id="section-4.1">
        <h3 id="name-control-of-function-through">
<a href="#section-4.1" class="section-number selfRef">4.1. </a><a href="#name-control-of-function-through" class="section-name selfRef">Control of Function through Configuration and Policy</a>
        </h3>
<p id="section-4.1-1">
          This document makes no change to the basic operation of PCEP, so
          the requirements described in
          <span>[<a href="#RFC5440" class="xref">RFC5440</a>], <a href="https://www.rfc-editor.org/rfc/rfc5440#section-8.1" class="relref">Section 8.1</a></span> also apply to this document.
          In addition to those requirements, a PCEP implementation may allow the
          configuration of the following parameters:<a href="#section-4.1-1" class="pilcrow">¶</a></p>
<ul class="normal">
<li class="normal" id="section-4.1-2.1">Accepted RG in the RP object.<a href="#section-4.1-2.1" class="pilcrow">¶</a>
</li>
          <li class="normal" id="section-4.1-2.2">Default RG to use (overriding the one present in the PCReq).<a href="#section-4.1-2.2" class="pilcrow">¶</a>
</li>
          <li class="normal" id="section-4.1-2.3">Accepted BANDWIDTH object type 3 and 4 parameters in the
   request and default mapping to use when not specified in the request.<a href="#section-4.1-2.3" class="pilcrow">¶</a>
</li>
          <li class="normal" id="section-4.1-2.4">Accepted LOAD-BALANCING object type 2 parameters in request.<a href="#section-4.1-2.4" class="pilcrow">¶</a>
</li>
          <li class="normal" id="section-4.1-2.5">Accepted endpoint type and allowed TLVs in object END-POINTS with the object type Generalized Endpoint.<a href="#section-4.1-2.5" class="pilcrow">¶</a>
</li>
          <li class="normal" id="section-4.1-2.6">Accepted range for label restrictions in END-POINTS or IRO/XRO objects.<a href="#section-4.1-2.6" class="pilcrow">¶</a>
</li>
          <li class="normal" id="section-4.1-2.7">Acceptance and suppression of the PROTECTION-ATTRIBUTE TLV.<a href="#section-4.1-2.7" class="pilcrow">¶</a>
</li>
        </ul>
<p id="section-4.1-3">
          The configuration of the above parameters is applicable to the different sessions as described in <span>[<a href="#RFC5440" class="xref">RFC5440</a>], <a href="https://www.rfc-editor.org/rfc/rfc5440#section-8.1" class="relref">Section 8.1</a></span> (by default, per PCEP peer, etc.).<a href="#section-4.1-3" class="pilcrow">¶</a></p>
</section>
<section id="section-4.2">
        <h3 id="name-information-and-data-models">
<a href="#section-4.2" class="section-number selfRef">4.2. </a><a href="#name-information-and-data-models" class="section-name selfRef">Information and Data Models</a>
        </h3>
<p id="section-4.2-1">
          This document makes no change to the basic operation of PCEP, so
          the requirements described in
          <span>[<a href="#RFC5440" class="xref">RFC5440</a>], <a href="https://www.rfc-editor.org/rfc/rfc5440#section-8.2" class="relref">Section 8.2</a></span> also apply to this document.
          This document  does not introduce any new ERO subobjects; the ERO information model is already covered in <span>[<a href="#RFC4802" class="xref">RFC4802</a>]</span>.<a href="#section-4.2-1" class="pilcrow">¶</a></p>
</section>
<section id="section-4.3">
        <h3 id="name-liveness-detection-and-moni">
<a href="#section-4.3" class="section-number selfRef">4.3. </a><a href="#name-liveness-detection-and-moni" class="section-name selfRef">Liveness Detection and Monitoring</a>
        </h3>
<p id="section-4.3-1">
          This document makes no change to the basic operation of PCEP, so
          there are no changes to the requirements for liveness detection and
          monitoring in <span>[<a href="#RFC4657" class="xref">RFC4657</a>]</span> and <span>[<a href="#RFC5440" class="xref">RFC5440</a>], <a href="https://www.rfc-editor.org/rfc/rfc5440#section-8.3" class="relref">Section 8.3</a></span>.<a href="#section-4.3-1" class="pilcrow">¶</a></p>
</section>
<section id="section-4.4">
        <h3 id="name-verifying-correct-operation">
<a href="#section-4.4" class="section-number selfRef">4.4. </a><a href="#name-verifying-correct-operation" class="section-name selfRef">Verifying Correct Operation</a>
        </h3>
<p id="section-4.4-1">
          This document makes no change to the basic operations of PCEP and the considerations described in <span>[<a href="#RFC5440" class="xref">RFC5440</a>], <a href="https://www.rfc-editor.org/rfc/rfc5440#section-8.4" class="relref">Section 8.4</a></span>.
          New errors defined by this document should satisfy the requirement to log error events.<a href="#section-4.4-1" class="pilcrow">¶</a></p>
</section>
<section id="section-4.5">
        <h3 id="name-requirements-on-other-proto">
<a href="#section-4.5" class="section-number selfRef">4.5. </a><a href="#name-requirements-on-other-proto" class="section-name selfRef">Requirements on Other Protocols and Functional Components</a>
        </h3>
<p id="section-4.5-1">No new requirements on other protocols and functional
        components are made by this document. This document does not
        require ERO object extensions. Any new ERO subobject defined
        in the TEAS or CCAMP Working Groups can be adopted without modifying the operations defined in this document.<a href="#section-4.5-1" class="pilcrow">¶</a></p>
</section>
<section id="section-4.6">
        <h3 id="name-impact-on-network-operation">
<a href="#section-4.6" class="section-number selfRef">4.6. </a><a href="#name-impact-on-network-operation" class="section-name selfRef">Impact on Network Operation</a>
        </h3>
<p id="section-4.6-1">This document makes no change to the basic operations of PCEP and the considerations described in <span>[<a href="#RFC5440" class="xref">RFC5440</a>], <a href="https://www.rfc-editor.org/rfc/rfc5440#section-8.6" class="relref">Section 8.6</a></span>.
        In addition to the limit on the rate of messages sent by a PCEP speaker, a limit <span class="bcp14">MAY</span> be placed on the size of the PCEP messages.<a href="#section-4.6-1" class="pilcrow">¶</a></p>
</section>
</section>
<section id="section-5">
      <h2 id="name-iana-considerations">
<a href="#section-5" class="section-number selfRef">5. </a><a href="#name-iana-considerations" class="section-name selfRef">IANA Considerations</a>
      </h2>
<p id="section-5-1">
        IANA assigns values to PCEP objects and TLVs. IANA has
        made allocations for the newly defined objects and
        TLVs defined in this document. In addition, IANA manages
        the space of flags that have been newly added in the TLVs.<a href="#section-5-1" class="pilcrow">¶</a></p>
<section id="section-5.1">
        <h3 id="name-pcep-objects">
<a href="#section-5.1" class="section-number selfRef">5.1. </a><a href="#name-pcep-objects" class="section-name selfRef">PCEP Objects</a>
        </h3>
<p id="section-5.1-1">New object types are defined in Sections <a href="#generalized-bandwidth" class="xref">2.3</a>, <a href="#generalized-load-balancing" class="xref">2.4</a>, and <a href="#endpoints_generalized" class="xref">2.5.1</a>.  IANA has made
        the following Object-Type allocations in the "PCEP Objects"
        subregistry.<a href="#section-5.1-1" class="pilcrow">¶</a></p>
<div id="iana_gen_bw">
<table class="center" id="table-8">
          <caption><a href="#table-8" class="selfRef">Table 8</a></caption>
<thead>
            <tr>
              <th class="text-left" rowspan="1" colspan="1">Object-Class Value</th>
              <th class="text-left" rowspan="1" colspan="1">Name</th>
              <th class="text-left" rowspan="1" colspan="1">Object-Type</th>
              <th class="text-left" rowspan="1" colspan="1">Reference</th>
            </tr>
          </thead>
          <tbody>
            <tr>
              <td class="text-left" rowspan="1" colspan="1">5</td>
              <td class="text-left" rowspan="1" colspan="1">BANDWIDTH</td>
              <td class="text-left" rowspan="1" colspan="1">3: Generalized bandwidth</td>
              <td class="text-left" rowspan="1" colspan="1">RFC 8779, <a href="#generalized-bandwidth" class="xref">Section 2.3</a>
</td>
            </tr>
            <tr>
              <td class="text-left" rowspan="1" colspan="1"></td>
              <td class="text-left" rowspan="1" colspan="1"></td>
              <td class="text-left" rowspan="1" colspan="1">4: Generalized bandwidth of an existing TE-LSP
              for which a reoptimization is requested</td>
              <td class="text-left" rowspan="1" colspan="1">RFC 8779, <a href="#generalized-bandwidth" class="xref">Section 2.3</a>
</td>
            </tr>
            <tr>
              <td class="text-left" rowspan="1" colspan="1">14</td>
              <td class="text-left" rowspan="1" colspan="1">LOAD-BALANCING</td>
              <td class="text-left" rowspan="1" colspan="1">2: Generalized Load Balancing</td>
              <td class="text-left" rowspan="1" colspan="1">RFC 8779, <a href="#generalized-load-balancing" class="xref">Section 2.4</a>
</td>
            </tr>
            <tr>
              <td class="text-left" rowspan="1" colspan="1">4</td>
              <td class="text-left" rowspan="1" colspan="1">END-POINTS</td>
              <td class="text-left" rowspan="1" colspan="1">5: Generalized Endpoint</td>
              <td class="text-left" rowspan="1" colspan="1">RFC 8779, <a href="#endpoints_extensions" class="xref">Section 2.5</a>
</td>
            </tr>
          </tbody>
        </table>
</div>
</section>
<section id="section-5.2">
        <h3 id="name-endpoint-type-field-in-the-">
<a href="#section-5.2" class="section-number selfRef">5.2. </a><a href="#name-endpoint-type-field-in-the-" class="section-name selfRef">Endpoint Type Field in the Generalized END-POINTS Object</a>
        </h3>
<p id="section-5.2-1">IANA has created a new "Generalized Endpoint Types" registry to
        manage the Endpoint Type field of the END-POINTS object, the object
        type Generalized Endpoint, and the code space.<a href="#section-5.2-1" class="pilcrow">¶</a></p>
<p id="section-5.2-2">New endpoint types in the Unassigned range are assigned by
        Standards Action <span>[<a href="#RFC8126" class="xref">RFC8126</a>]</span>. Each
        endpoint type should be tracked with the following attributes:<a href="#section-5.2-2" class="pilcrow">¶</a></p>
<ul class="normal">
<li class="normal" id="section-5.2-3.1">Value<a href="#section-5.2-3.1" class="pilcrow">¶</a>
</li>
          <li class="normal" id="section-5.2-3.2">Type<a href="#section-5.2-3.2" class="pilcrow">¶</a>
</li>
          <li class="normal" id="section-5.2-3.3">Defining RFC<a href="#section-5.2-3.3" class="pilcrow">¶</a>
</li>
        </ul>
<p id="section-5.2-4">New endpoint types in the Experimental Use range will not be
        registered with IANA and <span class="bcp14">MUST NOT</span> be mentioned by any
        RFCs.<a href="#section-5.2-4" class="pilcrow">¶</a></p>
<p id="section-5.2-5">The following values are defined by this document
    (see <a href="#endpoints_generalized_endpoint-type" class="xref">Table 4</a> in <a href="#endpoints_generalized" class="xref">Section 2.5.1</a>):<a href="#section-5.2-5" class="pilcrow">¶</a></p>
<table class="center" id="table-9">
          <caption><a href="#table-9" class="selfRef">Table 9</a></caption>
<thead>
            <tr>
              <th class="text-left" rowspan="1" colspan="1">Value</th>
              <th class="text-left" rowspan="1" colspan="1">Type</th>
            </tr>
          </thead>
          <tbody>
            <tr>
              <td class="text-left" rowspan="1" colspan="1">0</td>
              <td class="text-left" rowspan="1" colspan="1">Point-to-Point</td>
            </tr>
            <tr>
              <td class="text-left" rowspan="1" colspan="1">1</td>
              <td class="text-left" rowspan="1" colspan="1">Point-to-Multipoint with leaf type 1</td>
            </tr>
            <tr>
              <td class="text-left" rowspan="1" colspan="1">2</td>
              <td class="text-left" rowspan="1" colspan="1">Point-to-Multipoint with leaf type 2</td>
            </tr>
            <tr>
              <td class="text-left" rowspan="1" colspan="1">3</td>
              <td class="text-left" rowspan="1" colspan="1">Point-to-Multipoint with leaf type 3</td>
            </tr>
            <tr>
              <td class="text-left" rowspan="1" colspan="1">4</td>
              <td class="text-left" rowspan="1" colspan="1">Point-to-Multipoint with leaf type 4</td>
            </tr>
            <tr>
              <td class="text-left" rowspan="1" colspan="1">5-244</td>
              <td class="text-left" rowspan="1" colspan="1">Unassigned</td>
            </tr>
            <tr>
              <td class="text-left" rowspan="1" colspan="1">245-255</td>
              <td class="text-left" rowspan="1" colspan="1">Experimental Use</td>
            </tr>
          </tbody>
        </table>
</section>
<div id="iana-tlvs">
<section id="section-5.3">
        <h3 id="name-new-pcep-tlvs">
<a href="#section-5.3" class="section-number selfRef">5.3. </a><a href="#name-new-pcep-tlvs" class="section-name selfRef">New PCEP TLVs</a>
        </h3>
<p id="section-5.3-1">
   IANA manages a registry for PCEP TLV code points (see <span>[<a href="#RFC5440" class="xref">RFC5440</a>]</span>), which
   is maintained as the "PCEP TLV Type Indicators" subregistry of the
   "Path Computation Element Protocol (PCEP) Numbers" registry.

   IANA has allocated the following per this document:<a href="#section-5.3-1" class="pilcrow">¶</a></p>
<table class="center" id="table-10">
          <caption><a href="#table-10" class="selfRef">Table 10</a></caption>
<thead>
            <tr>
              <th class="text-center" rowspan="1" colspan="1">Value</th>
              <th class="text-left" rowspan="1" colspan="1">Meaning</th>
              <th class="text-left" rowspan="1" colspan="1">Reference</th>
            </tr>
          </thead>
          <tbody>
            <tr>
              <td class="text-center" rowspan="1" colspan="1">39</td>
              <td class="text-left" rowspan="1" colspan="1">IPV4-ADDRESS</td>
              <td class="text-left" rowspan="1" colspan="1">RFC 8779, <a href="#endpoints_tlvs_ipv4" class="xref">Section 2.5.2.1</a>
</td>
            </tr>
            <tr>
              <td class="text-center" rowspan="1" colspan="1">40</td>
              <td class="text-left" rowspan="1" colspan="1">IPV6-ADDRESS</td>
              <td class="text-left" rowspan="1" colspan="1">RFC 8779, <a href="#endpoints_tlvs_ipv6" class="xref">Section 2.5.2.2</a>
</td>
            </tr>
            <tr>
              <td class="text-center" rowspan="1" colspan="1">41</td>
              <td class="text-left" rowspan="1" colspan="1">UNNUMBERED-ENDPOINT</td>
              <td class="text-left" rowspan="1" colspan="1">RFC 8779, <a href="#endpoints_tlvs_unnumbered-if" class="xref">Section 2.5.2.3</a>
</td>
            </tr>
            <tr>
              <td class="text-center" rowspan="1" colspan="1">42</td>
              <td class="text-left" rowspan="1" colspan="1">LABEL-REQUEST</td>
              <td class="text-left" rowspan="1" colspan="1">RFC 8779, <a href="#endpoints_tlvs_label-request" class="xref">Section 2.5.2.4</a>
</td>
            </tr>
            <tr>
              <td class="text-center" rowspan="1" colspan="1">43</td>
              <td class="text-left" rowspan="1" colspan="1">LABEL-SET</td>
              <td class="text-left" rowspan="1" colspan="1">RFC 8779, <a href="#endpoints_tlvs_labels" class="xref">Section 2.5.2.5</a>
</td>
            </tr>
            <tr>
              <td class="text-center" rowspan="1" colspan="1">44 </td>
              <td class="text-left" rowspan="1" colspan="1">PROTECTION-ATTRIBUTE</td>
              <td class="text-left" rowspan="1" colspan="1">RFC 8779, <a href="#lspa" class="xref">Section 2.8</a>
</td>
            </tr>
            <tr>
              <td class="text-center" rowspan="1" colspan="1">45</td>
              <td class="text-left" rowspan="1" colspan="1">GMPLS-CAPABILITY</td>
              <td class="text-left" rowspan="1" colspan="1">RFC 8779, <a href="#open-extensions" class="xref">Section 2.1.2</a>
</td>
            </tr>
          </tbody>
        </table>
</section>
</div>
<section id="section-5.4">
        <h3 id="name-rp-object-flag-field">
<a href="#section-5.4" class="section-number selfRef">5.4. </a><a href="#name-rp-object-flag-field" class="section-name selfRef">RP Object Flag Field</a>
        </h3>
<p id="section-5.4-1">
   A new flag is defined in <a href="#rp-extensions" class="xref">Section 2.2</a> for the Flags field of the RP object.  IANA has
   made the following allocation in the "RP Object Flag
   Field" subregistry:<a href="#section-5.4-1" class="pilcrow">¶</a></p>
<table class="center" id="table-11">
          <caption><a href="#table-11" class="selfRef">Table 11</a></caption>
<thead>
            <tr>
              <th class="text-center" rowspan="1" colspan="1">Bit</th>
              <th class="text-left" rowspan="1" colspan="1">Description</th>
              <th class="text-left" rowspan="1" colspan="1">Reference</th>
            </tr>
          </thead>
          <tbody>
            <tr>
              <td class="text-center" rowspan="1" colspan="1">15-16</td>
              <td class="text-left" rowspan="1" colspan="1">Routing Granularity (RG)</td>
              <td class="text-left" rowspan="1" colspan="1">RFC 8779, <a href="#rp-extensions" class="xref">Section 2.2</a>
</td>
            </tr>
          </tbody>
        </table>
</section>
<section id="section-5.5">
        <h3 id="name-new-pcep-error-codes">
<a href="#section-5.5" class="section-number selfRef">5.5. </a><a href="#name-new-pcep-error-codes" class="section-name selfRef">New PCEP Error Codes</a>
        </h3>
<p id="section-5.5-1">New PCEP Error-Types and Error-values are defined in <a href="#error-codes" class="xref">Section 3</a>. IANA has made the
        following allocations in the "PCEP-ERROR Object Error Types and Values"
        registry:<a href="#section-5.5-1" class="pilcrow">¶</a></p>
<table class="center" id="table-12">
          <caption><a href="#table-12" class="selfRef">Table 12</a></caption>
<thead>
            <tr>
              <th class="text-left" rowspan="1" colspan="1">Error-Type</th>
              <th class="text-left" rowspan="1" colspan="1">Meaning</th>
              <th class="text-left" rowspan="1" colspan="1">Error-value</th>
              <th class="text-left" rowspan="1" colspan="1">Reference</th>
            </tr>
          </thead>
          <tbody>
            <tr>
              <td class="text-left" rowspan="1" colspan="1">4</td>
              <td class="text-left" rowspan="1" colspan="1">Not supported object</td>
              <td class="text-left" rowspan="1" colspan="1"></td>
              <td class="text-left" rowspan="1" colspan="1">
                <span>[<a href="#RFC5440" class="xref">RFC5440</a>]</span>
</td>
            </tr>
            <tr>
              <td class="text-left" rowspan="1" colspan="1"></td>
              <td class="text-left" rowspan="1" colspan="1"></td>
              <td class="text-left" rowspan="1" colspan="1">6: BANDWIDTH object type 3 or 4 not supported</td>
              <td class="text-left" rowspan="1" colspan="1">RFC 8779</td>
            </tr>
            <tr>
              <td class="text-left" rowspan="1" colspan="1"></td>
              <td class="text-left" rowspan="1" colspan="1"></td>
              <td class="text-left" rowspan="1" colspan="1">7: Unsupported endpoint type in END-POINTS
              Generalized Endpoint object type</td>
              <td class="text-left" rowspan="1" colspan="1">RFC 8779</td>
            </tr>
            <tr>
              <td class="text-left" rowspan="1" colspan="1"></td>
              <td class="text-left" rowspan="1" colspan="1"></td>
              <td class="text-left" rowspan="1" colspan="1">8: Unsupported TLV present in END-POINTS
              Generalized Endpoint object type</td>
              <td class="text-left" rowspan="1" colspan="1">RFC 8779</td>
            </tr>
            <tr>
              <td class="text-left" rowspan="1" colspan="1"></td>
              <td class="text-left" rowspan="1" colspan="1"></td>
              <td class="text-left" rowspan="1" colspan="1">9: Unsupported granularity in the RP object flags</td>
              <td class="text-left" rowspan="1" colspan="1">RFC 8779</td>
            </tr>
            <tr>
              <td class="text-left" rowspan="1" colspan="1">10</td>
              <td class="text-left" rowspan="1" colspan="1">Reception of an invalid object </td>
              <td class="text-left" rowspan="1" colspan="1"></td>
              <td class="text-left" rowspan="1" colspan="1">
                <span>[<a href="#RFC5440" class="xref">RFC5440</a>]</span>
</td>
            </tr>
            <tr>
              <td class="text-left" rowspan="1" colspan="1"></td>
              <td class="text-left" rowspan="1" colspan="1"></td>
              <td class="text-left" rowspan="1" colspan="1">24: Bad BANDWIDTH object type 3 or 4</td>
              <td class="text-left" rowspan="1" colspan="1">RFC 8779</td>
            </tr>
            <tr>
              <td class="text-left" rowspan="1" colspan="1"></td>
              <td class="text-left" rowspan="1" colspan="1"></td>
              <td class="text-left" rowspan="1" colspan="1">25: Unsupported LSP Protection Flags in
              PROTECTION-ATTRIBUTE TLV</td>
              <td class="text-left" rowspan="1" colspan="1">RFC 8779</td>
            </tr>
            <tr>
              <td class="text-left" rowspan="1" colspan="1"></td>
              <td class="text-left" rowspan="1" colspan="1"></td>
              <td class="text-left" rowspan="1" colspan="1">26: Unsupported Secondary LSP Protection Flags
              in PROTECTION-ATTRIBUTE TLV</td>
              <td class="text-left" rowspan="1" colspan="1">RFC 8779</td>
            </tr>
            <tr>
              <td class="text-left" rowspan="1" colspan="1"></td>
              <td class="text-left" rowspan="1" colspan="1"></td>
              <td class="text-left" rowspan="1" colspan="1">27: Unsupported Link Protection Type in
              PROTECTION-ATTRIBUTE TLV</td>
              <td class="text-left" rowspan="1" colspan="1">RFC 8779</td>
            </tr>
            <tr>
              <td class="text-left" rowspan="1" colspan="1"></td>
              <td class="text-left" rowspan="1" colspan="1"></td>
              <td class="text-left" rowspan="1" colspan="1">28: LABEL-SET TLV present with O bit set but
              without R bit set in RP</td>
              <td class="text-left" rowspan="1" colspan="1">RFC 8779</td>
            </tr>
            <tr>
              <td class="text-left" rowspan="1" colspan="1"></td>
              <td class="text-left" rowspan="1" colspan="1"></td>
              <td class="text-left" rowspan="1" colspan="1">29: Wrong LABEL-SET TLV present with O and L bits set</td>
              <td class="text-left" rowspan="1" colspan="1">RFC 8779</td>
            </tr>
            <tr>
              <td class="text-left" rowspan="1" colspan="1"></td>
              <td class="text-left" rowspan="1" colspan="1"></td>
              <td class="text-left" rowspan="1" colspan="1">30: Wrong LABEL-SET TLV present with O bit set and wrong format</td>
              <td class="text-left" rowspan="1" colspan="1">RFC 8779</td>
            </tr>
            <tr>
              <td class="text-left" rowspan="1" colspan="1"></td>
              <td class="text-left" rowspan="1" colspan="1"></td>
              <td class="text-left" rowspan="1" colspan="1">31: Missing GMPLS-CAPABILITY TLV</td>
              <td class="text-left" rowspan="1" colspan="1">RFC 8779</td>
            </tr>
            <tr>
              <td class="text-left" rowspan="1" colspan="1">29</td>
              <td class="text-left" rowspan="1" colspan="1">Path computation failure</td>
              <td class="text-left" rowspan="1" colspan="1"></td>
              <td class="text-left" rowspan="1" colspan="1">RFC 8779</td>
            </tr>
            <tr>
              <td class="text-left" rowspan="1" colspan="1"></td>
              <td class="text-left" rowspan="1" colspan="1"></td>
              <td class="text-left" rowspan="1" colspan="1">0: Unassigned</td>
              <td class="text-left" rowspan="1" colspan="1">RFC 8779</td>
            </tr>
            <tr>
              <td class="text-left" rowspan="1" colspan="1"></td>
              <td class="text-left" rowspan="1" colspan="1"></td>
              <td class="text-left" rowspan="1" colspan="1">1: Unacceptable request message</td>
              <td class="text-left" rowspan="1" colspan="1">RFC 8779</td>
            </tr>
            <tr>
              <td class="text-left" rowspan="1" colspan="1"></td>
              <td class="text-left" rowspan="1" colspan="1"></td>
              <td class="text-left" rowspan="1" colspan="1">2: Generalized bandwidth value not supported</td>
              <td class="text-left" rowspan="1" colspan="1">RFC 8779</td>
            </tr>
            <tr>
              <td class="text-left" rowspan="1" colspan="1"></td>
              <td class="text-left" rowspan="1" colspan="1"></td>
              <td class="text-left" rowspan="1" colspan="1">3: Label set constraint could not be met</td>
              <td class="text-left" rowspan="1" colspan="1">RFC 8779</td>
            </tr>
            <tr>
              <td class="text-left" rowspan="1" colspan="1"></td>
              <td class="text-left" rowspan="1" colspan="1"></td>
              <td class="text-left" rowspan="1" colspan="1">4: Label constraint could not be met</td>
              <td class="text-left" rowspan="1" colspan="1">RFC 8779</td>
            </tr>
          </tbody>
        </table>
</section>
<section id="section-5.6">
        <h3 id="name-new-bits-in-no-path-vector-">
<a href="#section-5.6" class="section-number selfRef">5.6. </a><a href="#name-new-bits-in-no-path-vector-" class="section-name selfRef">New Bits in NO-PATH-VECTOR TLV</a>
        </h3>
<p id="section-5.6-1">New NO-PATH-VECTOR TLV bits are defined in <a href="#no-path_bits" class="xref">Section 2.9.1</a>.  IANA has made the
        following allocations in the "NO-PATH-VECTOR TLV Flag Field"
        subregistry:<a href="#section-5.6-1" class="pilcrow">¶</a></p>
<div id="no-path-vector-iana">
<table class="center" id="table-13">
          <caption><a href="#table-13" class="selfRef">Table 13</a></caption>
<thead>
            <tr>
              <th class="text-left" rowspan="1" colspan="1">Bit</th>
              <th class="text-left" rowspan="1" colspan="1">Description</th>
              <th class="text-left" rowspan="1" colspan="1">Reference</th>
            </tr>
          </thead>
          <tbody>
            <tr>
              <td class="text-left" rowspan="1" colspan="1">18</td>
              <td class="text-left" rowspan="1" colspan="1">Protection Mismatch</td>
              <td class="text-left" rowspan="1" colspan="1">RFC 8779</td>
            </tr>
            <tr>
              <td class="text-left" rowspan="1" colspan="1">17</td>
              <td class="text-left" rowspan="1" colspan="1">No Resource</td>
              <td class="text-left" rowspan="1" colspan="1">RFC 8779</td>
            </tr>
            <tr>
              <td class="text-left" rowspan="1" colspan="1">16</td>
              <td class="text-left" rowspan="1" colspan="1">Granularity not supported</td>
              <td class="text-left" rowspan="1" colspan="1">RFC 8779</td>
            </tr>
            <tr>
              <td class="text-left" rowspan="1" colspan="1">15</td>
              <td class="text-left" rowspan="1" colspan="1">No endpoint label resource</td>
              <td class="text-left" rowspan="1" colspan="1">RFC 8779</td>
            </tr>
            <tr>
              <td class="text-left" rowspan="1" colspan="1">14</td>
              <td class="text-left" rowspan="1" colspan="1">No endpoint label resource in range</td>
              <td class="text-left" rowspan="1" colspan="1">RFC 8779</td>
            </tr>
            <tr>
              <td class="text-left" rowspan="1" colspan="1">13</td>
              <td class="text-left" rowspan="1" colspan="1">No label resource in range</td>
              <td class="text-left" rowspan="1" colspan="1">RFC 8779</td>
            </tr>
            <tr>
              <td class="text-left" rowspan="1" colspan="1">12</td>
              <td class="text-left" rowspan="1" colspan="1">LOAD-BALANCING could not be performed with the bandwidth constraints</td>
              <td class="text-left" rowspan="1" colspan="1">RFC 8779</td>
            </tr>
          </tbody>
        </table>
</div>
</section>
<section id="section-5.7">
        <h3 id="name-new-subobject-for-the-inclu">
<a href="#section-5.7" class="section-number selfRef">5.7. </a><a href="#name-new-subobject-for-the-inclu" class="section-name selfRef">New Subobject for the Include Route Object</a>
        </h3>
<p id="section-5.7-1">IANA has added a new subobject in the "IRO Subobjects" subregistry of the
   "Path Computation Element Protocol (PCEP) Numbers" registry.<a href="#section-5.7-1" class="pilcrow">¶</a></p>
<p id="section-5.7-2">
          IANA has added a new subobject that can be carried in the IRO as
          follows:<a href="#section-5.7-2" class="pilcrow">¶</a></p>
<table class="center" id="table-14">
          <caption><a href="#table-14" class="selfRef">Table 14</a></caption>
<thead>
            <tr>
              <th class="text-left" rowspan="1" colspan="1">Value</th>
              <th class="text-left" rowspan="1" colspan="1">Description</th>
              <th class="text-left" rowspan="1" colspan="1">Reference</th>
            </tr>
          </thead>
          <tbody>
            <tr>
              <td class="text-left" rowspan="1" colspan="1">10</td>
              <td class="text-left" rowspan="1" colspan="1">Label</td>
              <td class="text-left" rowspan="1" colspan="1">RFC 8779</td>
            </tr>
          </tbody>
        </table>
</section>
<section id="section-5.8">
        <h3 id="name-new-subobject-for-the-exclu">
<a href="#section-5.8" class="section-number selfRef">5.8. </a><a href="#name-new-subobject-for-the-exclu" class="section-name selfRef">New Subobject for the Exclude Route Object</a>
        </h3>
<p id="section-5.8-1">IANA has added a new subobject in the "XRO Subobjects" subregistry of the
        "Path Computation Element Protocol (PCEP) Numbers" registry.<a href="#section-5.8-1" class="pilcrow">¶</a></p>
<p id="section-5.8-2">
          IANA has added a new subobject that can be carried in the XRO as
          follows:<a href="#section-5.8-2" class="pilcrow">¶</a></p>
<table class="center" id="table-15">
          <caption><a href="#table-15" class="selfRef">Table 15</a></caption>
<thead>
            <tr>
              <th class="text-left" rowspan="1" colspan="1">Value</th>
              <th class="text-left" rowspan="1" colspan="1">Description</th>
              <th class="text-left" rowspan="1" colspan="1">Reference</th>
            </tr>
          </thead>
          <tbody>
            <tr>
              <td class="text-left" rowspan="1" colspan="1">10</td>
              <td class="text-left" rowspan="1" colspan="1">Label</td>
              <td class="text-left" rowspan="1" colspan="1">RFC 8779</td>
            </tr>
          </tbody>
        </table>
</section>
<section id="section-5.9">
        <h3 id="name-new-gmpls-capability-tlv-fl">
<a href="#section-5.9" class="section-number selfRef">5.9. </a><a href="#name-new-gmpls-capability-tlv-fl" class="section-name selfRef">New GMPLS-CAPABILITY TLV Flag Field</a>
        </h3>
<p id="section-5.9-1">IANA has created a new "GMPLS-CAPABILITY TLV Flag Field"
        subregistry within the "Path Computation Element Protocol (PCEP)
        Numbers" registry to manage the Flag field of the GMPLS-CAPABILITY TLV.<a href="#section-5.9-1" class="pilcrow">¶</a></p>
<p id="section-5.9-2">New bit numbers are to be assigned by Standards Action <span>[<a href="#RFC8126" class="xref">RFC8126</a>]</span>. 
   Each bit should be tracked with the following qualities:<a href="#section-5.9-2" class="pilcrow">¶</a></p>
<ul class="normal">
<li class="normal" id="section-5.9-3.1">Bit number (counting from bit 0 as the most significant bit)<a href="#section-5.9-3.1" class="pilcrow">¶</a>
</li>
          <li class="normal" id="section-5.9-3.2">Capability description<a href="#section-5.9-3.2" class="pilcrow">¶</a>
</li>
          <li class="normal" id="section-5.9-3.3">Defining RFC<a href="#section-5.9-3.3" class="pilcrow">¶</a>
</li>
        </ul>
<p id="section-5.9-4">The initial contents of the subregistry are empty, with bits 0-31
   marked as Unassigned.<a href="#section-5.9-4" class="pilcrow">¶</a></p>
</section>
</section>
<section id="section-6">
      <h2 id="name-security-considerations">
<a href="#section-6" class="section-number selfRef">6. </a><a href="#name-security-considerations" class="section-name selfRef">Security Considerations</a>
      </h2>
<p id="section-6-1">
 GMPLS controls multiple technologies and types of network elements. The LSPs
 that are established using GMPLS, whose paths can be computed using the PCEP
 extensions to support GMPLS described in this document, can carry a high volume
 of traffic and can be a critical part of a network infrastructure. The PCE can then
 play a key role in the use of the resources and in determining the physical paths
 of the LSPs; thus, it is important to ensure the identity of the PCE and PCC, as well
 as the communication channel. In many deployments, there will be a completely
 isolated network where an external attack is of very low probability. However,
 there are other deployment cases in which the PCC-PCE communication can
 be more exposed, and there could be more security considerations. There are three main
 situations in case an attack in the GMPLS PCE context happens:<a href="#section-6-1" class="pilcrow">¶</a></p>
<ul class="ulEmpty normal">
<li class="ulEmpty normal" id="section-6-2.1">
          <span class="break"></span><dl class="dlParallel" id="section-6-2.1.1">
            <dt id="section-6-2.1.1.1">PCE Identity theft:</dt>
            <dd id="section-6-2.1.1.2">A legitimate PCC could request a path for a GMPLS LSP to
     a malicious PCE, which poses as a legitimate PCE.
            The response may be that the LSP traverses some geographical place
            known to the attacker where confidentiality (sniffing), integrity
            (traffic modification), or availability (traffic drop) attacks
            could be performed by use of an attacker-controlled middlebox
            device. 

            Also, the resulting LSP can omit constraints given in the
     requests (e.g., excluding certain fibers and avoiding some SRLGs), which could make
     the LSP that will be set up later look perfectly fine, but it will be in a risky
     situation. Also, the result can lead to the creation of an LSP that does not provide the
     desired quality and gives less resources than necessary.<a href="#section-6-2.1.1.2" class="pilcrow">¶</a>
</dd>
            <dd class="break"></dd>
<dt id="section-6-2.1.1.3">
     PCC Identity theft:</dt>
            <dd id="section-6-2.1.1.4">A malicious PCC, acting as a legitimate PCC, requesting LSP
     paths to a legitimate PCE can obtain a good knowledge of the physical topology of
     a critical infrastructure. It could learn enough details to plan a later physical
     attack.<a href="#section-6-2.1.1.4" class="pilcrow">¶</a>
</dd>
            <dd class="break"></dd>
<dt id="section-6-2.1.1.5">
     Message inspection:</dt>
            <dd id="section-6-2.1.1.6">As in the previous case, knowledge of an infrastructure can
     be obtained by sniffing PCEP messages.<a href="#section-6-2.1.1.6" class="pilcrow">¶</a>
</dd>
          <dd class="break"></dd>
</dl>
</li>
      </ul>
<p id="section-6-3">

 The security mechanisms can provide authentication and
        confidentiality for those scenarios where PCC-PCE communication
        cannot be completely trusted.  <span>[<a href="#RFC8253" class="xref">RFC8253</a>]</span> provides origin
        verification, message integrity, and replay protection, and it ensures
        that a third party cannot decipher the contents of a
        message.<a href="#section-6-3" class="pilcrow">¶</a></p>
<p id="section-6-4">
        In order to protect against the malicious PCE case, the PCC
        <span class="bcp14">SHOULD</span> have policies in place to accept or not accept the path provided by
        the PCE. Those policies can verify if the path follows the provided
        constraints. In addition, a technology-specific data-plane mechanism
        can be used (following <span>[<a href="#RFC5920" class="xref">RFC5920</a>], <a href="https://www.rfc-editor.org/rfc/rfc5920#section-5.8" class="relref">Section 5.8</a></span>) to verify the data-plane connectivity and deviation from constraints.<a href="#section-6-4" class="pilcrow">¶</a></p>
<p id="section-6-5">
 The usage of Transport Layer
 Security (TLS) to enhance PCEP security is described in <span>[<a href="#RFC8253" class="xref">RFC8253</a>]</span>. The document describes the initiation
 of TLS procedures, the TLS handshake mechanisms, the TLS methods for peer
 authentication, the applicable TLS ciphersuites for data exchange, and the handling
 of errors in the security checks. PCE and PCC <span class="bcp14">SHOULD</span> use the mechanism in <span>[<a href="#RFC8253" class="xref">RFC8253</a>]</span> to protect against malicious
        PCC and PCE.<a href="#section-6-5" class="pilcrow">¶</a></p>
<p id="section-6-6">
 Finally, as mentioned by <span>[<a href="#RFC7025" class="xref">RFC7025</a>]</span>, the PCEP extensions that support GMPLS should
 be considered under the same security as current PCE work, and this extension
 will not change the underlying security issues. However, given the critical
 nature of the network infrastructures under control by GMPLS, the security issues
 described above should be seriously considered when deploying a GMPLS-PCE-based
 control plane for such networks. For an overview of the security considerations, not only related to PCE/PCEP, and vulnerabilities of a GMPLS control plane, see <span>[<a href="#RFC5920" class="xref">RFC5920</a>]</span>.<a href="#section-6-6" class="pilcrow">¶</a></p>
</section>
<section id="section-7">
      <h2 id="name-references">
<a href="#section-7" class="section-number selfRef">7. </a><a href="#name-references" class="section-name selfRef">References</a>
      </h2>
<section id="section-7.1">
        <h3 id="name-normative-references">
<a href="#section-7.1" class="section-number selfRef">7.1. </a><a href="#name-normative-references" class="section-name selfRef">Normative References</a>
        </h3>
<dl class="references">
<dt id="G.709-v3">[G.709-v3]</dt>
        <dd>
<span class="refAuthor">ITU-T</span>, <span class="refTitle">"Interfaces for the optical transport network"</span>, <span class="refContent">Recommendation G.709/Y.1331</span>, <time datetime="2016-06" class="refDate">June 2016</time>, <span>&lt;<a href="https://www.itu.int/rec/T-REC-G.709-201606-I/en">https://www.itu.int/rec/T-REC-G.709-201606-I/en</a>&gt;</span>. </dd>
<dd class="break"></dd>
<dt id="RFC2119">[RFC2119]</dt>
        <dd>
<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>
<dd class="break"></dd>
<dt id="RFC2210">[RFC2210]</dt>
        <dd>
<span class="refAuthor">Wroclawski, J.</span>, <span class="refTitle">"The Use of RSVP with IETF Integrated Services"</span>, <span class="seriesInfo">RFC 2210</span>, <span class="seriesInfo">DOI 10.17487/RFC2210</span>, <time datetime="1997-09" class="refDate">September 1997</time>, <span>&lt;<a href="https://www.rfc-editor.org/info/rfc2210">https://www.rfc-editor.org/info/rfc2210</a>&gt;</span>. </dd>
<dd class="break"></dd>
<dt id="RFC3209">[RFC3209]</dt>
        <dd>
<span class="refAuthor">Awduche, D.</span><span class="refAuthor">, Berger, L.</span><span class="refAuthor">, Gan, D.</span><span class="refAuthor">, Li, T.</span><span class="refAuthor">, Srinivasan, V.</span><span class="refAuthor">, and G. Swallow</span>, <span class="refTitle">"RSVP-TE: Extensions to RSVP for LSP Tunnels"</span>, <span class="seriesInfo">RFC 3209</span>, <span class="seriesInfo">DOI 10.17487/RFC3209</span>, <time datetime="2001-12" class="refDate">December 2001</time>, <span>&lt;<a href="https://www.rfc-editor.org/info/rfc3209">https://www.rfc-editor.org/info/rfc3209</a>&gt;</span>. </dd>
<dd class="break"></dd>
<dt id="RFC3471">[RFC3471]</dt>
        <dd>
<span class="refAuthor">Berger, L., Ed.</span>, <span class="refTitle">"Generalized Multi-Protocol Label Switching (GMPLS) Signaling Functional Description"</span>, <span class="seriesInfo">RFC 3471</span>, <span class="seriesInfo">DOI 10.17487/RFC3471</span>, <time datetime="2003-01" class="refDate">January 2003</time>, <span>&lt;<a href="https://www.rfc-editor.org/info/rfc3471">https://www.rfc-editor.org/info/rfc3471</a>&gt;</span>. </dd>
<dd class="break"></dd>
<dt id="RFC3473">[RFC3473]</dt>
        <dd>
<span class="refAuthor">Berger, L., Ed.</span>, <span class="refTitle">"Generalized Multi-Protocol Label Switching (GMPLS) Signaling Resource ReserVation Protocol-Traffic Engineering (RSVP-TE) Extensions"</span>, <span class="seriesInfo">RFC 3473</span>, <span class="seriesInfo">DOI 10.17487/RFC3473</span>, <time datetime="2003-01" class="refDate">January 2003</time>, <span>&lt;<a href="https://www.rfc-editor.org/info/rfc3473">https://www.rfc-editor.org/info/rfc3473</a>&gt;</span>. </dd>
<dd class="break"></dd>
<dt id="RFC3477">[RFC3477]</dt>
        <dd>
<span class="refAuthor">Kompella, K.</span><span class="refAuthor"> and Y. Rekhter</span>, <span class="refTitle">"Signalling Unnumbered Links in Resource ReSerVation Protocol - Traffic Engineering (RSVP-TE)"</span>, <span class="seriesInfo">RFC 3477</span>, <span class="seriesInfo">DOI 10.17487/RFC3477</span>, <time datetime="2003-01" class="refDate">January 2003</time>, <span>&lt;<a href="https://www.rfc-editor.org/info/rfc3477">https://www.rfc-editor.org/info/rfc3477</a>&gt;</span>. </dd>
<dd class="break"></dd>
<dt id="RFC3630">[RFC3630]</dt>
        <dd>
<span class="refAuthor">Katz, D.</span><span class="refAuthor">, Kompella, K.</span><span class="refAuthor">, and D. Yeung</span>, <span class="refTitle">"Traffic Engineering (TE) Extensions to OSPF Version 2"</span>, <span class="seriesInfo">RFC 3630</span>, <span class="seriesInfo">DOI 10.17487/RFC3630</span>, <time datetime="2003-09" class="refDate">September 2003</time>, <span>&lt;<a href="https://www.rfc-editor.org/info/rfc3630">https://www.rfc-editor.org/info/rfc3630</a>&gt;</span>. </dd>
<dd class="break"></dd>
<dt id="RFC4003">[RFC4003]</dt>
        <dd>
<span class="refAuthor">Berger, L.</span>, <span class="refTitle">"GMPLS Signaling Procedure for Egress Control"</span>, <span class="seriesInfo">RFC 4003</span>, <span class="seriesInfo">DOI 10.17487/RFC4003</span>, <time datetime="2005-02" class="refDate">February 2005</time>, <span>&lt;<a href="https://www.rfc-editor.org/info/rfc4003">https://www.rfc-editor.org/info/rfc4003</a>&gt;</span>. </dd>
<dd class="break"></dd>
<dt id="RFC4328">[RFC4328]</dt>
        <dd>
<span class="refAuthor">Papadimitriou, D., Ed.</span>, <span class="refTitle">"Generalized Multi-Protocol Label Switching (GMPLS) Signaling Extensions for G.709 Optical Transport Networks Control"</span>, <span class="seriesInfo">RFC 4328</span>, <span class="seriesInfo">DOI 10.17487/RFC4328</span>, <time datetime="2006-01" class="refDate">January 2006</time>, <span>&lt;<a href="https://www.rfc-editor.org/info/rfc4328">https://www.rfc-editor.org/info/rfc4328</a>&gt;</span>. </dd>
<dd class="break"></dd>
<dt id="RFC4606">[RFC4606]</dt>
        <dd>
<span class="refAuthor">Mannie, E.</span><span class="refAuthor"> and D. Papadimitriou</span>, <span class="refTitle">"Generalized Multi-Protocol Label Switching (GMPLS) Extensions for Synchronous Optical Network (SONET) and Synchronous Digital Hierarchy (SDH) Control"</span>, <span class="seriesInfo">RFC 4606</span>, <span class="seriesInfo">DOI 10.17487/RFC4606</span>, <time datetime="2006-08" class="refDate">August 2006</time>, <span>&lt;<a href="https://www.rfc-editor.org/info/rfc4606">https://www.rfc-editor.org/info/rfc4606</a>&gt;</span>. </dd>
<dd class="break"></dd>
<dt id="RFC4802">[RFC4802]</dt>
        <dd>
<span class="refAuthor">Nadeau, T., Ed.</span><span class="refAuthor"> and A. Farrel, Ed.</span>, <span class="refTitle">"Generalized Multiprotocol Label Switching (GMPLS) Traffic Engineering Management Information Base"</span>, <span class="seriesInfo">RFC 4802</span>, <span class="seriesInfo">DOI 10.17487/RFC4802</span>, <time datetime="2007-02" class="refDate">February 2007</time>, <span>&lt;<a href="https://www.rfc-editor.org/info/rfc4802">https://www.rfc-editor.org/info/rfc4802</a>&gt;</span>. </dd>
<dd class="break"></dd>
<dt id="RFC4872">[RFC4872]</dt>
        <dd>
<span class="refAuthor">Lang, J.P., Ed.</span><span class="refAuthor">, Rekhter, Y., Ed.</span><span class="refAuthor">, and D. Papadimitriou, Ed.</span>, <span class="refTitle">"RSVP-TE Extensions in Support of End-to-End Generalized Multi-Protocol Label Switching (GMPLS) Recovery"</span>, <span class="seriesInfo">RFC 4872</span>, <span class="seriesInfo">DOI 10.17487/RFC4872</span>, <time datetime="2007-05" class="refDate">May 2007</time>, <span>&lt;<a href="https://www.rfc-editor.org/info/rfc4872">https://www.rfc-editor.org/info/rfc4872</a>&gt;</span>. </dd>
<dd class="break"></dd>
<dt id="RFC4873">[RFC4873]</dt>
        <dd>
<span class="refAuthor">Berger, L.</span><span class="refAuthor">, Bryskin, I.</span><span class="refAuthor">, Papadimitriou, D.</span><span class="refAuthor">, and A. Farrel</span>, <span class="refTitle">"GMPLS Segment Recovery"</span>, <span class="seriesInfo">RFC 4873</span>, <span class="seriesInfo">DOI 10.17487/RFC4873</span>, <time datetime="2007-05" class="refDate">May 2007</time>, <span>&lt;<a href="https://www.rfc-editor.org/info/rfc4873">https://www.rfc-editor.org/info/rfc4873</a>&gt;</span>. </dd>
<dd class="break"></dd>
<dt id="RFC5088">[RFC5088]</dt>
        <dd>
<span class="refAuthor">Le Roux, JL., Ed.</span><span class="refAuthor">, Vasseur, JP., Ed.</span><span class="refAuthor">, Ikejiri, Y.</span><span class="refAuthor">, and 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>
<dd class="break"></dd>
<dt id="RFC5089">[RFC5089]</dt>
        <dd>
<span class="refAuthor">Le Roux, JL., Ed.</span><span class="refAuthor">, Vasseur, JP., Ed.</span><span class="refAuthor">, Ikejiri, Y.</span><span class="refAuthor">, and 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>
<dd class="break"></dd>
<dt id="RFC5440">[RFC5440]</dt>
        <dd>
<span class="refAuthor">Vasseur, JP., Ed.</span><span class="refAuthor"> and 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>
<dd class="break"></dd>
<dt id="RFC5511">[RFC5511]</dt>
        <dd>
<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>
<dd class="break"></dd>
<dt id="RFC5520">[RFC5520]</dt>
        <dd>
<span class="refAuthor">Bradford, R., Ed.</span><span class="refAuthor">, Vasseur, JP.</span><span class="refAuthor">, and A. Farrel</span>, <span class="refTitle">"Preserving Topology Confidentiality in Inter-Domain Path Computation Using a Path-Key-Based Mechanism"</span>, <span class="seriesInfo">RFC 5520</span>, <span class="seriesInfo">DOI 10.17487/RFC5520</span>, <time datetime="2009-04" class="refDate">April 2009</time>, <span>&lt;<a href="https://www.rfc-editor.org/info/rfc5520">https://www.rfc-editor.org/info/rfc5520</a>&gt;</span>. </dd>
<dd class="break"></dd>
<dt id="RFC5521">[RFC5521]</dt>
        <dd>
<span class="refAuthor">Oki, E.</span><span class="refAuthor">, Takeda, T.</span><span class="refAuthor">, and A. Farrel</span>, <span class="refTitle">"Extensions to the Path Computation Element Communication Protocol (PCEP) for Route Exclusions"</span>, <span class="seriesInfo">RFC 5521</span>, <span class="seriesInfo">DOI 10.17487/RFC5521</span>, <time datetime="2009-04" class="refDate">April 2009</time>, <span>&lt;<a href="https://www.rfc-editor.org/info/rfc5521">https://www.rfc-editor.org/info/rfc5521</a>&gt;</span>. </dd>
<dd class="break"></dd>
<dt id="RFC5541">[RFC5541]</dt>
        <dd>
<span class="refAuthor">Le Roux, JL.</span><span class="refAuthor">, Vasseur, JP.</span><span class="refAuthor">, and Y. Lee</span>, <span class="refTitle">"Encoding of Objective Functions in the Path Computation Element Communication Protocol (PCEP)"</span>, <span class="seriesInfo">RFC 5541</span>, <span class="seriesInfo">DOI 10.17487/RFC5541</span>, <time datetime="2009-06" class="refDate">June 2009</time>, <span>&lt;<a href="https://www.rfc-editor.org/info/rfc5541">https://www.rfc-editor.org/info/rfc5541</a>&gt;</span>. </dd>
<dd class="break"></dd>
<dt id="RFC6001">[RFC6001]</dt>
        <dd>
<span class="refAuthor">Papadimitriou, D.</span><span class="refAuthor">, Vigoureux, M.</span><span class="refAuthor">, Shiomoto, K.</span><span class="refAuthor">, Brungard, D.</span><span class="refAuthor">, and JL. Le Roux</span>, <span class="refTitle">"Generalized MPLS (GMPLS) Protocol Extensions for Multi-Layer and Multi-Region Networks (MLN/MRN)"</span>, <span class="seriesInfo">RFC 6001</span>, <span class="seriesInfo">DOI 10.17487/RFC6001</span>, <time datetime="2010-10" class="refDate">October 2010</time>, <span>&lt;<a href="https://www.rfc-editor.org/info/rfc6001">https://www.rfc-editor.org/info/rfc6001</a>&gt;</span>. </dd>
<dd class="break"></dd>
<dt id="RFC6003">[RFC6003]</dt>
        <dd>
<span class="refAuthor">Papadimitriou, D.</span>, <span class="refTitle">"Ethernet Traffic Parameters"</span>, <span class="seriesInfo">RFC 6003</span>, <span class="seriesInfo">DOI 10.17487/RFC6003</span>, <time datetime="2010-10" class="refDate">October 2010</time>, <span>&lt;<a href="https://www.rfc-editor.org/info/rfc6003">https://www.rfc-editor.org/info/rfc6003</a>&gt;</span>. </dd>
<dd class="break"></dd>
<dt id="RFC6205">[RFC6205]</dt>
        <dd>
<span class="refAuthor">Otani, T., Ed.</span><span class="refAuthor"> and D. Li, Ed.</span>, <span class="refTitle">"Generalized Labels for Lambda-Switch-Capable (LSC) Label Switching Routers"</span>, <span class="seriesInfo">RFC 6205</span>, <span class="seriesInfo">DOI 10.17487/RFC6205</span>, <time datetime="2011-03" class="refDate">March 2011</time>, <span>&lt;<a href="https://www.rfc-editor.org/info/rfc6205">https://www.rfc-editor.org/info/rfc6205</a>&gt;</span>. </dd>
<dd class="break"></dd>
<dt id="RFC6387">[RFC6387]</dt>
        <dd>
<span class="refAuthor">Takacs, A.</span><span class="refAuthor">, Berger, L.</span><span class="refAuthor">, Caviglia, D.</span><span class="refAuthor">, Fedyk, D.</span><span class="refAuthor">, and J. Meuric</span>, <span class="refTitle">"GMPLS Asymmetric Bandwidth Bidirectional Label Switched Paths (LSPs)"</span>, <span class="seriesInfo">RFC 6387</span>, <span class="seriesInfo">DOI 10.17487/RFC6387</span>, <time datetime="2011-09" class="refDate">September 2011</time>, <span>&lt;<a href="https://www.rfc-editor.org/info/rfc6387">https://www.rfc-editor.org/info/rfc6387</a>&gt;</span>. </dd>
<dd class="break"></dd>
<dt id="RFC7139">[RFC7139]</dt>
        <dd>
<span class="refAuthor">Zhang, F., Ed.</span><span class="refAuthor">, Zhang, G.</span><span class="refAuthor">, Belotti, S.</span><span class="refAuthor">, Ceccarelli, D.</span><span class="refAuthor">, and K. Pithewan</span>, <span class="refTitle">"GMPLS Signaling Extensions for Control of Evolving G.709 Optical Transport Networks"</span>, <span class="seriesInfo">RFC 7139</span>, <span class="seriesInfo">DOI 10.17487/RFC7139</span>, <time datetime="2014-03" class="refDate">March 2014</time>, <span>&lt;<a href="https://www.rfc-editor.org/info/rfc7139">https://www.rfc-editor.org/info/rfc7139</a>&gt;</span>. </dd>
<dd class="break"></dd>
<dt id="RFC7570">[RFC7570]</dt>
        <dd>
<span class="refAuthor">Margaria, C., Ed.</span><span class="refAuthor">, Martinelli, G.</span><span class="refAuthor">, Balls, S.</span><span class="refAuthor">, and B. Wright</span>, <span class="refTitle">"Label Switched Path (LSP) Attribute in the Explicit Route Object (ERO)"</span>, <span class="seriesInfo">RFC 7570</span>, <span class="seriesInfo">DOI 10.17487/RFC7570</span>, <time datetime="2015-07" class="refDate">July 2015</time>, <span>&lt;<a href="https://www.rfc-editor.org/info/rfc7570">https://www.rfc-editor.org/info/rfc7570</a>&gt;</span>. </dd>
<dd class="break"></dd>
<dt id="RFC7792">[RFC7792]</dt>
        <dd>
<span class="refAuthor">Zhang, F.</span><span class="refAuthor">, Zhang, X.</span><span class="refAuthor">, Farrel, A.</span><span class="refAuthor">, Gonzalez de Dios, O.</span><span class="refAuthor">, and D. Ceccarelli</span>, <span class="refTitle">"RSVP-TE Signaling Extensions in Support of Flexi-Grid Dense Wavelength Division Multiplexing (DWDM) Networks"</span>, <span class="seriesInfo">RFC 7792</span>, <span class="seriesInfo">DOI 10.17487/RFC7792</span>, <time datetime="2016-03" class="refDate">March 2016</time>, <span>&lt;<a href="https://www.rfc-editor.org/info/rfc7792">https://www.rfc-editor.org/info/rfc7792</a>&gt;</span>. </dd>
<dd class="break"></dd>
<dt id="RFC8126">[RFC8126]</dt>
        <dd>
<span class="refAuthor">Cotton, M.</span><span class="refAuthor">, Leiba, B.</span><span class="refAuthor">, and 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>
<dd class="break"></dd>
<dt id="RFC8174">[RFC8174]</dt>
        <dd>
<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>
<dd class="break"></dd>
<dt id="RFC8253">[RFC8253]</dt>
        <dd>
<span class="refAuthor">Lopez, D.</span><span class="refAuthor">, Gonzalez de Dios, O.</span><span class="refAuthor">, Wu, Q.</span><span class="refAuthor">, and 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>
<dd class="break"></dd>
<dt id="RFC8282">[RFC8282]</dt>
        <dd>
<span class="refAuthor">Oki, E.</span><span class="refAuthor">, Takeda, T.</span><span class="refAuthor">, Farrel, A.</span><span class="refAuthor">, and F. Zhang</span>, <span class="refTitle">"Extensions to the Path Computation Element Communication Protocol (PCEP) for Inter-Layer MPLS and GMPLS Traffic Engineering"</span>, <span class="seriesInfo">RFC 8282</span>, <span class="seriesInfo">DOI 10.17487/RFC8282</span>, <time datetime="2017-12" class="refDate">December 2017</time>, <span>&lt;<a href="https://www.rfc-editor.org/info/rfc8282">https://www.rfc-editor.org/info/rfc8282</a>&gt;</span>. </dd>
<dd class="break"></dd>
<dt id="RFC8306">[RFC8306]</dt>
      <dd>
<span class="refAuthor">Zhao, Q.</span><span class="refAuthor">, Dhody, D., Ed.</span><span class="refAuthor">, Palleti, R.</span><span class="refAuthor">, and D. King</span>, <span class="refTitle">"Extensions to the Path Computation Element Communication Protocol (PCEP) for Point-to-Multipoint Traffic Engineering Label Switched Paths"</span>, <span class="seriesInfo">RFC 8306</span>, <span class="seriesInfo">DOI 10.17487/RFC8306</span>, <time datetime="2017-11" class="refDate">November 2017</time>, <span>&lt;<a href="https://www.rfc-editor.org/info/rfc8306">https://www.rfc-editor.org/info/rfc8306</a>&gt;</span>. </dd>
<dd class="break"></dd>
</dl>
</section>
<section id="section-7.2">
        <h3 id="name-informative-references">
<a href="#section-7.2" class="section-number selfRef">7.2. </a><a href="#name-informative-references" class="section-name selfRef">Informative References</a>
        </h3>
<dl class="references">
<dt id="RFC4655">[RFC4655]</dt>
        <dd>
<span class="refAuthor">Farrel, A.</span><span class="refAuthor">, Vasseur, J.-P.</span><span class="refAuthor">, and 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>
<dd class="break"></dd>
<dt id="RFC4657">[RFC4657]</dt>
        <dd>
<span class="refAuthor">Ash, J., Ed.</span><span class="refAuthor"> and J.L. Le Roux, Ed.</span>, <span class="refTitle">"Path Computation Element (PCE) Communication Protocol Generic Requirements"</span>, <span class="seriesInfo">RFC 4657</span>, <span class="seriesInfo">DOI 10.17487/RFC4657</span>, <time datetime="2006-09" class="refDate">September 2006</time>, <span>&lt;<a href="https://www.rfc-editor.org/info/rfc4657">https://www.rfc-editor.org/info/rfc4657</a>&gt;</span>. </dd>
<dd class="break"></dd>
<dt id="RFC5920">[RFC5920]</dt>
        <dd>
<span class="refAuthor">Fang, L., Ed.</span>, <span class="refTitle">"Security Framework for MPLS and GMPLS Networks"</span>, <span class="seriesInfo">RFC 5920</span>, <span class="seriesInfo">DOI 10.17487/RFC5920</span>, <time datetime="2010-07" class="refDate">July 2010</time>, <span>&lt;<a href="https://www.rfc-editor.org/info/rfc5920">https://www.rfc-editor.org/info/rfc5920</a>&gt;</span>. </dd>
<dd class="break"></dd>
<dt id="RFC6123">[RFC6123]</dt>
        <dd>
<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>
<dd class="break"></dd>
<dt id="RFC6163">[RFC6163]</dt>
        <dd>
<span class="refAuthor">Lee, Y., Ed.</span><span class="refAuthor">, Bernstein, G., Ed.</span><span class="refAuthor">, and W. Imajuku</span>, <span class="refTitle">"Framework for GMPLS and Path Computation Element (PCE) Control of Wavelength Switched Optical Networks (WSONs)"</span>, <span class="seriesInfo">RFC 6163</span>, <span class="seriesInfo">DOI 10.17487/RFC6163</span>, <time datetime="2011-04" class="refDate">April 2011</time>, <span>&lt;<a href="https://www.rfc-editor.org/info/rfc6163">https://www.rfc-editor.org/info/rfc6163</a>&gt;</span>. </dd>
<dd class="break"></dd>
<dt id="RFC7025">[RFC7025]</dt>
        <dd>
<span class="refAuthor">Otani, T.</span><span class="refAuthor">, Ogaki, K.</span><span class="refAuthor">, Caviglia, D.</span><span class="refAuthor">, Zhang, F.</span><span class="refAuthor">, and C. Margaria</span>, <span class="refTitle">"Requirements for GMPLS Applications of PCE"</span>, <span class="seriesInfo">RFC 7025</span>, <span class="seriesInfo">DOI 10.17487/RFC7025</span>, <time datetime="2013-09" class="refDate">September 2013</time>, <span>&lt;<a href="https://www.rfc-editor.org/info/rfc7025">https://www.rfc-editor.org/info/rfc7025</a>&gt;</span>. </dd>
<dd class="break"></dd>
<dt id="RFC7449">[RFC7449]</dt>
      <dd>
<span class="refAuthor">Lee, Y., Ed.</span><span class="refAuthor">, Bernstein, G., Ed.</span><span class="refAuthor">, Martensson, J.</span><span class="refAuthor">, Takeda, T.</span><span class="refAuthor">, Tsuritani, T.</span><span class="refAuthor">, and O. Gonzalez de Dios</span>, <span class="refTitle">"Path Computation Element Communication Protocol (PCEP) Requirements for Wavelength Switched Optical Network (WSON) Routing and Wavelength Assignment"</span>, <span class="seriesInfo">RFC 7449</span>, <span class="seriesInfo">DOI 10.17487/RFC7449</span>, <time datetime="2015-02" class="refDate">February 2015</time>, <span>&lt;<a href="https://www.rfc-editor.org/info/rfc7449">https://www.rfc-editor.org/info/rfc7449</a>&gt;</span>. </dd>
<dd class="break"></dd>
</dl>
</section>
</section>
<div id="appendix">
<section id="section-appendix.a">
      <h2 id="name-load-balancing-usage-for-sd">
<a href="#section-appendix.a" class="section-number selfRef">Appendix A. </a><a href="#name-load-balancing-usage-for-sd" class="section-name selfRef">LOAD-BALANCING Usage for SDH Virtual Concatenation</a>
      </h2>
<p id="section-appendix.a-1">As an example, a request for one co-signaled n x VC-4 TE-LSP
      will not use LOAD-BALANCING. 
      In case the VC-4 components can
      use different paths, the BANDWIDTH with object type 3 will
      contain the complete n x VC-4 traffic specification,
      and the LOAD-BALANCING object will contain the minimum
      co-signaled VC-4.
      For an SDH network, a request for a TE-LSP group with 10 VC-4 
   containers, with each path using at minimum 2 x VC-4 containers, can 
   be represented with a BANDWIDTH object with object type 3, the Bw Spec Type 
   set to 4, and the content of the Generalized Bandwidth field with ST=6, 
   RCC=0, NCC=0, NVC=10, and MT=1.

    The LOAD-BALANCING with object type 2 with the Bw Spec Type set
    to 4 and Max-LSP=5, Min Bandwidth Spec is ST=6, RCC=0, NCC=0, NVC=2, MT=1.
 
      The PCE can respond with a maximum of 5 paths, with each path having a 
      BANDWIDTH object type 3 and a Generalized Bandwidth field matching the Min Bandwidth 
      Spec from the LOAD-BALANCING object of the corresponding request.<a href="#section-appendix.a-1" class="pilcrow">¶</a></p>
</section>
</div>
<section id="section-appendix.b">
      <h2 id="name-acknowledgments">
<a href="#name-acknowledgments" class="section-name selfRef">Acknowledgments</a>
      </h2>
<p id="section-appendix.b-1">
        The research of <span class="contact-name">Ramon Casellas</span>, <span class="contact-name">Francisco Javier Jimenez Chico</span>, <span class="contact-name">Oscar         Gonzalez de Dios</span>, <span class="contact-name">Cyril Margaria</span>, and
        <span class="contact-name">Franz Rambach</span> that led to the results in this
        document received funding from the European Community's Seventh
        Framework Program FP7/2007-2013 under grant agreement no. 247674 and
        no. 317999.<a href="#section-appendix.b-1" class="pilcrow">¶</a></p>
<p id="section-appendix.b-2">
        The authors would like to thank <span class="contact-name">Julien Meuric</span>,
        <span class="contact-name">Lyndon Ong</span>, <span class="contact-name">Giada Lander</span>,
        <span class="contact-name">Jonathan Hardwick</span>, <span class="contact-name">Diego         Lopez</span>, <span class="contact-name">David Sinicrope</span>, <span class="contact-name">Vincent Roca</span>, <span class="contact-name">Dhruv Dhody</span>, <span class="contact-name">Adrian Farrel</span>, and <span class="contact-name">Tianran Zhou</span> for
        their review and useful comments.<a href="#section-appendix.b-2" class="pilcrow">¶</a></p>
<p id="section-appendix.b-3"> Thanks to <span class="contact-name">Alisa Cooper</span>, <span class="contact-name">Benjamin Kaduk</span>, <span class="contact-name">Elwyn Davies</span>,
      <span class="contact-name">Martin Vigoureux</span>, <span class="contact-name">Roman       Danyliw</span>, and <span class="contact-name">Suresh Krishnan</span> for the
      IESG-related comments.<a href="#section-appendix.b-3" class="pilcrow">¶</a></p>
</section>
<section id="section-appendix.c">
      <h2 id="name-contributors">
<a href="#name-contributors" class="section-name selfRef">Contributors</a>
      </h2>
<address class="vcard">
        <div dir="auto" class="left"><span class="fn nameRole">Elie Sfeir</span></div>
<div dir="auto" class="left"><span class="org">Coriant</span></div>
<div dir="auto" class="left"><span class="street-address">St. Martin Strasse 76</span></div>
<div dir="auto" class="left">
<span class="postal-code">81541</span> <span class="locality">Munich</span>
</div>
<div dir="auto" class="left"><span class="country-name">Germany</span></div>
<div class="email">
<span>Email:</span>
<a href="mailto:elie.sfeir@coriant.com" class="email">elie.sfeir@coriant.com</a>
</div>
</address>
<address class="vcard">
        <div dir="auto" class="left"><span class="fn nameRole">Franz Rambach</span></div>
<div dir="auto" class="left"><span class="street-address">Nockherstrasse 2-4</span></div>
<div dir="auto" class="left">
<span class="postal-code">81541</span> <span class="locality">Munich</span>
</div>
<div dir="auto" class="left"><span class="country-name">Germany</span></div>
<div class="tel">
<span>Phone:</span>
<a href="tel:+49%20178%208855738" class="tel">+49 178 8855738</a>
</div>
<div class="email">
<span>Email:</span>
<a href="mailto:franz.rambach@cgi.com" class="email">franz.rambach@cgi.com</a>
</div>
</address>
<address class="vcard">
        <div dir="auto" class="left"><span class="fn nameRole">Francisco Javier Jimenez Chico</span></div>
<div dir="auto" class="left"><span class="org">Telefonica Investigacion y Desarrollo</span></div>
<div dir="auto" class="left"><span class="street-address">C/ Emilio Vargas 6</span></div>
<div dir="auto" class="left">
<span class="postal-code">28043</span> <span class="locality">Madrid</span> </div>
<div dir="auto" class="left"><span class="country-name">Spain</span></div>
<div class="tel">
<span>Phone:</span>
<a href="tel:+34%2091%203379037" class="tel">+34 91 3379037</a>
</div>
<div class="email">
<span>Email:</span>
<a href="mailto:fjjc@tid.es" class="email">fjjc@tid.es</a>
</div>
</address>
<address class="vcard">
        <div dir="auto" class="left"><span class="fn nameRole">Suresh Babu</span></div>
<div class="email">
<span>Email:</span>
<a href="mailto:sureshhimnish@gmail.com" class="email">sureshhimnish@gmail.com</a>
</div>
</address>
<address class="vcard">
        <div dir="auto" class="left"><span class="fn nameRole">Young Lee</span></div>
<div dir="auto" class="left"><span class="org">Samsung Electronics</span></div>
<div class="email">
<span>Email:</span>
<a href="mailto:younglee.tx@gmail.com" class="email">younglee.tx@gmail.com</a>
</div>
</address>
<address class="vcard">
        <div dir="auto" class="left"><span class="fn nameRole">Senthil Kumar S</span></div>
<div class="email">
<span>Email:</span>
<a href="mailto:ssenthilkumar@gmail.com" class="email">ssenthilkumar@gmail.com</a>
</div>
</address>
<address class="vcard">
        <div dir="auto" class="left"><span class="fn nameRole">Jun Sun</span></div>
<div dir="auto" class="left"><span class="org">Huawei Technologies</span></div>
<div dir="auto" class="left"><span class="locality">Shenzhen</span></div>
<div dir="auto" class="left"><span class="country-name">China</span></div>
<div class="email">
<span>Email:</span>
<a href="mailto:johnsun@huawei.com" class="email">johnsun@huawei.com</a>
</div>
</address>
<address class="vcard">
        <div dir="auto" class="left"><span class="fn nameRole">Ramon Casellas</span></div>
<div dir="auto" class="left"><span class="org">CTTC - Centre Tecnologic de Telecomunicacions de Catalunya</span></div>
<div dir="auto" class="left"><span class="street-address">PMT Ed B4 Av. Carl Friedrich Gauss 7</span></div>
<div dir="auto" class="left">
<span class="postal-code">08660</span> <span class="locality">Castelldefels,</span> <span class="region">Barcelona</span>
</div>
<div dir="auto" class="left"><span class="country-name">Spain</span></div>
<div class="tel">
<span>Phone:</span>
<a href="tel:+34%2093%206452916" class="tel">+34 93 6452916</a>
</div>
<div class="email">
<span>Email:</span>
<a href="mailto:ramon.casellas@cttc.e" class="email">ramon.casellas@cttc.e</a>
</div>
</address>
</section>
<div id="authors-addresses">
<section id="section-appendix.d">
      <h2 id="name-authors-addresses">
<a href="#name-authors-addresses" class="section-name selfRef">Authors' Addresses</a>
      </h2>
<address class="vcard">
        <div dir="auto" class="left"><span class="fn nameRole">Cyril Margaria (<span class="role">editor</span>)</span></div>
<div dir="auto" class="left"><span class="org">Juniper</span></div>
<div class="email">
<span>Email:</span>
<a href="mailto:cmargaria@juniper.net" class="email">cmargaria@juniper.net</a>
</div>
</address>
<address class="vcard">
        <div dir="auto" class="left"><span class="fn nameRole">Oscar Gonzalez de Dios (<span class="role">editor</span>)</span></div>
<div dir="auto" class="left"><span class="org">Telefonica Investigacion y Desarrollo</span></div>
<div dir="auto" class="left"><span class="street-address">C/ Ronda de la Comunicacion</span></div>
<div dir="auto" class="left">
<span class="postal-code">28050</span> <span class="locality">Madrid</span> </div>
<div dir="auto" class="left"><span class="country-name">Spain</span></div>
<div class="tel">
<span>Phone:</span>
<a href="tel:+34%2091%204833441" class="tel">+34 91 4833441</a>
</div>
<div class="email">
<span>Email:</span>
<a href="mailto:oscar.gonzalezdedios@telefonica.com" class="email">oscar.gonzalezdedios@telefonica.com</a>
</div>
</address>
<address class="vcard">
        <div dir="auto" class="left"><span class="fn nameRole">Fatai Zhang (<span class="role">editor</span>)</span></div>
<div dir="auto" class="left"><span class="org">Huawei Technologies</span></div>
<div dir="auto" class="left"><span class="street-address">F3-5-B R&amp;D Center, Huawei Base</span></div>
<div dir="auto" class="left"><span class="locality">Bantian, Longgang District</span></div>
<div dir="auto" class="left"><span class="locality">Shenzhen</span></div>
<div dir="auto" class="left"><span class="postal-code">518129</span></div>
<div dir="auto" class="left"><span class="country-name">China</span></div>
<div class="email">
<span>Email:</span>
<a href="mailto:zhangfatai@huawei.com" class="email">zhangfatai@huawei.com</a>
</div>
</address>
</section>
</div>
<script>const toc = document.getElementById("toc");
toc.querySelector("h2").addEventListener("click", e => {
  toc.classList.toggle("active");
});
toc.querySelector("nav").addEventListener("click", e => {
  toc.classList.remove("active");
});
</script>
</body>
</html>