-
Notifications
You must be signed in to change notification settings - Fork 0
/
ietf-pcep.yang
2612 lines (2538 loc) · 80.6 KB
/
ietf-pcep.yang
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
module ietf-pcep {
yang-version 1.1;
namespace "urn:ietf:params:xml:ns:yang:ietf-pcep";
prefix pcep;
import ietf-inet-types {
prefix inet;
reference
"RFC 6991: Common YANG Data Types";
}
import ietf-yang-types {
prefix yang;
reference
"RFC 6991: Common YANG Data Types";
}
import ietf-te {
prefix te;
reference
"I-D.ietf-teas-yang-te: A YANG Data Model for Traffic
Engineering Tunnels and Interfaces";
}
import ietf-te-types {
prefix te-types;
reference
"RFC 8776: Common YANG Data Types for Traffic Engineering";
}
import ietf-key-chain {
prefix key-chain;
reference
"RFC 8177: YANG Data Model for Key Chains";
}
import ietf-netconf-acm {
prefix nacm;
reference
"RFC 8341: Network Configuration Protocol (NETCONF) Access
Control Model";
}
import ietf-tls-server {
prefix tlss;
reference
"I-D.ietf-netconf-tls-client-server: YANG Groupings for TLS
Clients and TLS Servers";
}
import ietf-tls-client {
prefix tlsc;
reference
"I-D.ietf-netconf-tls-client-server: YANG Groupings for TLS
Clients and TLS Servers";
}
import ietf-ospf {
prefix ospf;
reference
"I-D.ietf-ospf-yang: YANG Data Model for OSPF Protocol";
}
import ietf-isis {
prefix isis;
reference
"I-D.ietf-isis-yang-isis-cfg: YANG Data Model for IS-IS
Protocol";
}
organization
"IETF PCE (Path Computation Element) Working Group";
contact
"WG Web: <https://tools.ietf.org/wg/pce/>
WG List: <mailto:pce@ietf.org>
Editor: Dhruv Dhody
<mailto:dhruv.ietf@gmail.com>";
description
"The YANG module defines a generic configuration and
operational model for PCEP.
The key words 'MUST', 'MUST NOT', 'REQUIRED', 'SHALL', 'SHALL
NOT', 'SHOULD', 'SHOULD NOT', 'RECOMMENDED', 'NOT RECOMMENDED',
'MAY', and 'OPTIONAL' in this document are to be interpreted as
described in BCP 14 (RFC 2119) (RFC 8174) when, and only when,
they appear in all capitals, as shown here.
Copyright (c) 2020 IETF Trust and the persons identified as
authors of the code. All rights reserved.
Redistribution and use in source and binary forms, with or
without modification, is permitted pursuant to, and subject
to the license terms contained in, the Simplified BSD License
set forth in Section 4.c of the IETF Trust's Legal Provisions
Relating to IETF Documents
(https://trustee.ietf.org/license-info).
This version of this YANG module is part of RFC XXXX; see the
RFC itself for full legal notices.";
revision 2020-07-08 {
description
"Initial revision.";
reference
"RFC XXXX: A YANG Data Model for Path Computation
Element Communications Protocol (PCEP)";
}
/*
* Typedefs
*/
typedef pcep-role {
type enumeration {
enum unknown {
value 0;
description
"An unknown role";
}
enum pcc {
value 1;
description
"The role of a Path Computation Client";
}
enum pce {
value 2;
description
"The role of Path Computation Element";
}
enum pcc-and-pce {
value 3;
description
"The role of both Path Computation Client and
Path Computation Element";
}
}
description
"The role of a PCEP speaker.
Takes one of the following values
- unknown(0): the role is not known.
- pcc(1): the role is of a Path Computation
Client (PCC).
- pce(2): the role is of a Path Computation
Server (PCE).
- pccAndPce(3): the role is of both a PCC and
a PCE.";
}
typedef pcep-oper-status {
type enumeration {
enum oper-status-up {
value 1;
description
"The PCEP entity is active";
}
enum oper-status-down {
value 2;
description
"The PCEP entity is inactive";
}
enum oper-status-going-up {
value 3;
description
"The PCEP entity is activating";
}
enum oper-status-going-down {
value 4;
description
"The PCEP entity is deactivating";
}
enum oper-status-failed {
value 5;
description
"The PCEP entity has failed and will recover
when possible.";
}
enum oper-status-failed-perm {
value 6;
description
"The PCEP entity has failed and will not recover
without operator intervention";
}
}
description
"The operational status of the PCEP entity.
Takes one of the following values
- oper-status-up(1): Active
- oper-status-down(2): Inactive
- oper-status-going-up(3): Activating
- oper-status-going-down(4): Deactivating
- oper-status-failed(5): Failed
- oper-status-failed-perm(6): Failed Permanantly";
reference
"RFC 5440: Path Computation Element (PCE) Communication
Protocol (PCEP)";
}
typedef pcep-initiator {
type enumeration {
enum local {
value 1;
description
"The local PCEP entity initiated the session";
}
enum remote {
value 2;
description
"The remote PCEP peer initiated the session";
}
}
description
"The initiator of the session, that is, whether the TCP
connection was initiated by the local PCEP entity or
the remote peer.
Takes one of the following values
- local(1): Initiated locally
- remote(2): Initiated remotely";
}
typedef pcep-sess-state {
type enumeration {
enum tcp-pending {
value 1;
description
"The tcp-pending state of PCEP session.";
}
enum open-wait {
value 2;
description
"The open-wait state of PCEP session.";
}
enum keep-wait {
value 3;
description
"The keep-wait state of PCEP session.";
}
enum session-up {
value 4;
description
"The session-up state of PCEP session.";
}
}
description
"The current state of the session.
The set of possible states excludes the idle state
since entries do not exist in the idle state.
Takes one of the following values
- tcp-pending(1): PCEP TCP Pending state
- open-wait(2): PCEP Open Wait state
- keep-wait(3): PCEP Keep Wait state
- session-up(4): PCEP Session Up state";
reference
"RFC 5440: Path Computation Element (PCE) Communication
Protocol (PCEP)";
}
typedef domain-type {
type enumeration {
enum ospf-area {
value 1;
description
"The OSPF area.";
}
enum isis-area {
value 2;
description
"The IS-IS area.";
}
enum as {
value 3;
description
"The Autonomous System (AS).";
}
}
description
"The PCE Domain Type";
}
typedef domain-ospf-area {
type ospf:area-id-type;
description
"OSPF Area ID.";
reference
"I-D.ietf-ospf-yang: YANG Data Model for OSPF Protocol";
}
typedef domain-isis-area {
type isis:area-address;
description
"IS-IS Area ID.";
reference
"I-D.ietf-isis-yang-isis-cfg: YANG Data Model for IS-IS
Protocol";
}
typedef domain-as {
type inet:as-number;
description
"Autonomous System number.";
}
typedef domain {
type union {
type domain-ospf-area;
type domain-isis-area;
type domain-as;
}
description
"The Domain Information";
}
typedef operational-state {
type enumeration {
enum down {
value 0;
description
"not active.";
}
enum up {
value 1;
description
"signalled.";
}
enum active {
value 2;
description
"up and carrying traffic.";
}
enum going-down {
value 3;
description
"LSP is being torn down, resources are
being released.";
}
enum going-up {
value 4;
description
"LSP is being signalled.";
}
}
description
"The operational status of the LSP";
reference
"RFC 8231: Path Computation Element Communication Protocol
(PCEP) Extensions for Stateful PCE";
}
typedef sync-state {
type enumeration {
enum pending {
value 0;
description
"The state synchronization
has not started.";
}
enum ongoing {
value 1;
description
"The state synchronization
is ongoing.";
}
enum finished {
value 2;
description
"The state synchronization
is finished.";
}
}
description
"The LSP-DB state synchronization operational
status.";
reference
"RFC 8231: Path Computation Element Communication Protocol
(PCEP) Extensions for Stateful PCE";
}
/*
* Features
*/
feature svec {
description
"Support synchronized path computation.";
reference
"RFC 5440: Path Computation Element (PCE) Communication
Protocol (PCEP)";
}
feature gmpls {
description
"Support GMPLS.";
reference
"I-D.ietf-pce-gmpls-pcep-extensions: PCEP extensions for
GMPLS";
}
feature objective-function {
description
"Support OF as per RFC 5541.";
reference
"RFC 5541: Encoding of Objective Functions in the Path
Computation Element Communication Protocol (PCEP)";
}
feature global-concurrent {
description
"Support GCO as per RFC 5557.";
reference
"RFC 5557: Path Computation Element Communication Protocol
(PCEP) Requirements and Protocol Extensions in Support of
Global Concurrent Optimization";
}
feature path-key {
description
"Support path-key as per RFC 5520.";
reference
"RFC 5520: Preserving Topology Confidentiality in Inter-
Domain Path Computation Using a Path-Key-Based Mechanism";
}
feature p2mp {
description
"Support P2MP as per RFC 8306.";
reference
"RFC 8306: Extensions to the Path Computation Element
Communication Protocol (PCEP) for Point-to-Multipoint
Traffic Engineering Label Switched Paths";
}
feature stateful {
description
"Support stateful PCE as per RFC 8231.";
reference
"RFC 8231: Path Computation Element Communication Protocol
(PCEP) Extensions for Stateful PCE";
}
feature sync-opt {
description
"Support stateful sync optimization
as per RFC 8232";
reference
"RFC 8232: Optimizations of Label Switched Path State
Synchronization Procedures for a Stateful PCE";
}
feature pce-initiated {
description
"Support PCE-Initiated LSP as per
RFC 8281.";
reference
"RFC 8281: Path Computation Element Communication Protocol
(PCEP) Extensions for PCE-Initiated LSP Setup in a Stateful
PCE Model";
}
feature tls {
description
"Support PCEP over TLS as per
RFC 8253.";
reference
"RFC 8253: PCEPS: Usage of TLS to Provide a Secure Transport
for the Path Computation Element Communication Protocol
(PCEP)";
}
feature sr {
description
"Support Segment Routing for PCE.";
reference
"RFC 8664: Path Computation Element Communication Protocol
(PCEP) Extensions for Segment Routing";
}
feature association {
description
"Support Association in PCEP.";
reference
"RFC 8697: Path Computation Element Communication Protocol
(PCEP) Extensions for Establishing Relationships between
Sets of Label Switched Paths (LSPs)";
}
/*
* Identities
*/
identity lsp-error {
if-feature "stateful";
description
"Base LSP error";
reference
"RFC 8231: Path Computation Element Communication Protocol
(PCEP) Extensions for Stateful PCE";
}
identity no-error-lsp-error {
if-feature "stateful";
base lsp-error;
description
"No error, LSP is fine.";
reference
"RFC 8231: Path Computation Element Communication Protocol
(PCEP) Extensions for Stateful PCE";
}
identity unknown-lsp-error {
if-feature "stateful";
base lsp-error;
description
"Unknown reason.";
reference
"RFC 8231: Path Computation Element Communication Protocol
(PCEP) Extensions for Stateful PCE";
}
identity limit-lsp-error {
if-feature "stateful";
base lsp-error;
description
"Limit reached for PCE-controlled LSPs.";
reference
"RFC 8231: Path Computation Element Communication Protocol
(PCEP) Extensions for Stateful PCE";
}
identity pending-lsp-error {
if-feature "stateful";
base lsp-error;
description
"Too many pending LSP update requests.";
reference
"RFC 8231: Path Computation Element Communication Protocol
(PCEP) Extensions for Stateful PCE";
}
identity unacceptable-lsp-error {
if-feature "stateful";
base lsp-error;
description
"Unacceptable parameters.";
reference
"RFC 8231: Path Computation Element Communication Protocol
(PCEP) Extensions for Stateful PCE";
}
identity internal-lsp-error {
if-feature "stateful";
base lsp-error;
description
"Internal error.";
reference
"RFC 8231: Path Computation Element Communication Protocol
(PCEP) Extensions for Stateful PCE";
}
identity admin-lsp-error {
if-feature "stateful";
base lsp-error;
description
"LSP administratively brought down.";
reference
"RFC 8231: Path Computation Element Communication Protocol
(PCEP) Extensions for Stateful PCE";
}
identity preempted-lsp-error {
if-feature "stateful";
base lsp-error;
description
"LSP preempted.";
reference
"RFC 8231: Path Computation Element Communication Protocol
(PCEP) Extensions for Stateful PCE";
}
identity rsvp-lsp-error {
if-feature "stateful";
base lsp-error;
description
"RSVP signaling error.";
reference
"RFC 8231: Path Computation Element Communication Protocol
(PCEP) Extensions for Stateful PCE";
}
/*
* Groupings
*/
grouping pce-scope {
description
"This grouping defines PCE path computation scope
information which maybe relevant to PCE selection.
This information corresponds to PCE auto-discovery
information.";
reference
"RFC 5088: OSPF Protocol Extensions for Path
Computation Element (PCE) Discovery
RFC 5089: IS-IS Protocol Extensions for Path
Computation Element (PCE) Discovery";
leaf path-scope {
type bits {
bit intra-area-scope {
description
"PCE can compute intra-area paths.";
}
bit inter-area-scope {
description
"PCE can compute inter-area paths.";
}
bit inter-area-scope-default {
description
"PCE can act as a default PCE for inter-area
path computation.";
}
bit inter-as-scope {
description
"PCE can compute inter-AS paths.";
}
bit inter-as-scope-default {
description
"PCE can act as a default PCE for inter-AS
path computation.";
}
bit inter-layer-scope {
description
"PCE can compute inter-layer paths.";
}
}
description
"The field corresponding to the path scope bits";
}
leaf intra-area-pref {
type uint8 {
range "0..7";
}
description
"The PCE's preference for intra-area TE LSP
computation.";
}
leaf inter-area-pref {
type uint8 {
range "0..7";
}
description
"The PCE's preference for inter-area TE LSP
computation.";
}
leaf inter-as-pref {
type uint8 {
range "0..7";
}
description
"The PCE's preference for inter-AS TE LSP
computation.";
}
leaf inter-layer-pref {
type uint8 {
range "0..7";
}
description
"The PCE's preference for inter-layer TE LSP
computation.";
}
}
//pce-scope
grouping domain {
description
"This grouping specifies a Domain where the
PCEP speaker has topology visibility.";
leaf domain-type {
type domain-type;
description
"The domain type.";
}
leaf domain {
type domain;
description
"The domain Information.";
}
}
//domain
grouping info {
description
"This grouping specifies all information which
maybe relevant to both PCC and PCE.
This information corresponds to PCE auto-discovery
information.";
container domain {
description
"The local domain for the PCEP entity";
list domain {
key "domain-type domain";
description
"The local domain.";
uses domain {
description
"The local domain for the PCEP entity.";
}
}
}
container capability {
description
"The PCEP entity capability information of local
PCEP entity. This maybe relevant to PCE selection
as well. This information corresponds to PCE auto-
discovery information.";
reference
"RFC 5088: OSPF Protocol Extensions for Path
Computation Element (PCE) Discovery
RFC 5089: IS-IS Protocol Extensions for Path
Computation Element (PCE) Discovery";
leaf capability {
type bits {
bit gmpls {
if-feature "gmpls";
description
"Path computation with GMPLS link
constraints.";
}
bit bi-dir {
description
"Bidirectional path computation.";
}
bit diverse {
description
"Diverse path computation.";
}
bit load-balance {
description
"Load-balanced path computation.";
}
bit synchronize {
if-feature "svec";
description
"Synchronized paths computation.";
}
bit objective-function {
if-feature "objective-function";
description
"Support for multiple objective functions.";
}
bit add-path-constraint {
description
"Support for additive path constraints (max
hop count, etc.).";
}
bit prioritization {
description
"Support for request prioritization.";
}
bit multi-request {
description
"Support for multiple requests per message.";
}
bit global-concurrent {
if-feature "global-concurrent";
description
"Support for Global Concurrent Optimization
(GCO).";
}
bit p2mp {
if-feature "p2mp";
description
"Support for P2MP path computation.";
}
bit active {
if-feature "stateful";
description
"Support for active stateful PCE.";
}
bit passive {
if-feature "stateful";
description
"Support for passive stateful PCE.";
}
bit p2mp-active {
if-feature "stateful";
if-feature "p2mp";
description
"Support for active stateful PCE for P2MP.";
}
bit p2mp-passive {
if-feature "stateful";
if-feature "p2mp";
description
"Support for passive stateful PCE for P2MP.";
}
bit p2mp-pce-initiated {
if-feature "stateful";
if-feature "pce-initiated";
if-feature "p2mp";
description
"Support for PCE-initiated LSP for P2MP.";
}
}
description
"The bits string indicating the capabiliies";
reference
"RFC 5088: OSPF Protocol Extensions for Path
Computation Element (PCE) Discovery
RFC 5089: IS-IS Protocol Extensions for Path
Computation Element (PCE) Discovery";
}
leaf pce-initiated {
if-feature "pce-initiated";
type boolean;
description
"Set to true if PCE-initiated LSP capability is
enabled.";
reference
"RFC 8281: Path Computation Element Communication
Protocol (PCEP) Extensions for PCE-Initiated LSP
Setup in a Stateful PCE Model";
}
leaf include-db-ver {
if-feature "stateful";
if-feature "sync-opt";
type boolean;
description
"Support inclusion of LSP-DB-VERSION
in LSP object";
reference
"RFC 8232: Optimizations of Label Switched Path State
Synchronization Procedures for a Stateful PCE";
}
leaf trigger-resync {
if-feature "stateful";
if-feature "sync-opt";
type boolean;
description
"Support PCE triggered re-synchronization";
reference
"RFC 8232: Optimizations of Label Switched Path State
Synchronization Procedures for a Stateful PCE";
}
leaf trigger-initial-sync {
if-feature "stateful";
if-feature "sync-opt";
type boolean;
description
"PCE triggered initial synchronization";
reference
"RFC 8232: Optimizations of Label Switched Path State
Synchronization Procedures for a Stateful PCE";
}
leaf incremental-sync {
if-feature "stateful";
if-feature "sync-opt";
type boolean;
description
"Support incremental (delta) sync";
reference
"RFC 8232: Optimizations of Label Switched Path State
Synchronization Procedures for a Stateful PCE";
}
container sr {
if-feature "sr";
description
"If segment routing is supported";
reference
"RFC 8664: Path Computation Element Communication Protocol
(PCEP) Extensions for Segment Routing";
leaf enabled {
type boolean;
description
"Set to true if SR is enabled";
}
leaf msd-limit {
type boolean;
default "false";
description
"True indicates no limit on MSD, the
leaf msd is ignored";
}
leaf nai {
type boolean;
default "false";
description
"True indicates capability to resolve NAI
to SID";
}
}
//sr
}
//capability
leaf msd {
if-feature "sr";
type uint8;
description
"Maximum SID Depth for SR";
reference
"RFC 8664: Path Computation Element Communication Protocol
(PCEP) Extensions for Segment Routing";
}
}
//info
grouping pce-info {
description
"This grouping specifies all PCE information
which maybe relevant to the PCE selection.
This information corresponds to PCE auto-discovery
information.";
container scope {
description
"The path computation scope";
uses pce-scope;
}
container neigh-domains {
description
"The list of neighbour PCE-Domain
toward which a PCE can compute
paths";
list domain {
key "domain-type domain";
description
"The neighbour domain.";
uses domain {
description
"The PCE neighbour domain.";
}
}
}
}
//pce-info
grouping notification-instance-hdr {
description
"This group describes common instance specific data
for notifications.";
leaf peer-addr {
type leafref {
path "/pcep/entity/peers/peer/addr";
}
description
"Reference to peer address";
}
}
// notification-instance-hdr
grouping notification-session-hdr {
description
"This group describes common session instance specific
data for notifications.";
leaf session-initiator {
type leafref {
path "/pcep/entity/peers/peer/sessions/"
+ "session/initiator";
}
description
"Reference to pcep session initiator leaf";
}
}
// notification-session-hdr
grouping of-list {
description
"List of OF";
reference
"RFC 5541: Encoding of Objective Functions in the Path
Computation Element Communication Protocol (PCEP)";
list objective-function {
key "of";
description
"The list of authorized OF";
leaf of {
type identityref {
base te-types:objective-function-type;
}
description
"The OF authorized";
}
}
}
/*
* Configuration data nodes
*/
container pcep {
presence "The PCEP is enabled";
description
"Parameters for list of configured PCEP entities
on the device.";
container entity {
description
"The configured PCEP entity on the device.";
leaf addr {
type inet:ip-address;
mandatory true;
description
"The local Internet address of this PCEP entity.
If operating as a PCE server, the PCEP entity
listens on this address. If operating as a PCC,
the PCEP entity binds outgoing TCP connections
to this address. It is possible for the PCEP entity
to operate both as a PCC and a PCE Server, in which
case it uses this address both to listen for incoming