1 module transportpce-pce {
2 namespace "http://org/transportpce/B-interface/pce";
3 prefix transportpce-pce;
5 import ietf-yang-types {
8 import transportpce-routing-constraints {
9 prefix transportpce-routing-constraints;
10 revision-date 2017-10-17;
12 import org-openroadm-common-service-types {
13 prefix org-openroadm-common-service-types;
15 import transportpce-common-service-path-types {
16 prefix transportpce-common-service-path-types;
17 revision-date 2017-10-16;
19 import transportpce-pathDescription {
20 prefix transportpce-pathDescription;
21 revision-date 2017-10-17;
23 import transportpce-pathDescription {
24 prefix transportpce-pathDescription;
30 "transportPCE committers - ODL";
32 "YANG definitions of B interface (transportPCE). Adapted from service definition (openroadm)
33 Copyright © 2017 Orange, Inc. and others. All rights reserved.
36 Copyright of the Members of the Open ROADM MSA Agreement dated (c) 2016,
37 AT&T Intellectual Property. All other rights reserved.
39 Redistribution and use in source and binary forms, with or without modification,
40 are permitted provided that the following conditions are met:
42 * Redistributions of source code must retain the above copyright notice, this
43 list of conditions and the following disclaimer.
44 * Redistributions in binary form must reproduce the above copyright notice,
45 this list of conditions and the following disclaimer in the documentation and/or
46 other materials provided with the distribution.
47 * Neither the Members of the Open ROADM MSA Agreement nor the names of its
48 contributors may be used to endorse or promote products derived from this software
49 without specific prior written permission.
51 THIS SOFTWARE IS PROVIDED BY THE MEMBERS OF THE OPEN ROADM MSA AGREEMENT ''AS IS''
52 AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED
53 WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED.
54 IN NO EVENT THE MEMBERS OF THE OPEN ROADM MSA AGREEMENT BE LIABLE FOR ANY DIRECT,
55 INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT
56 NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA,
57 OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY,
58 WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE)
59 ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE
60 POSSIBILITY OF SUCH DAMAGE";
67 rpc path-computation-request {
72 "Identifier for the service to be created in
73 the ROADM network, e.g., CLFI, CLCI, etc. This is reported against the service, but may not get reflected in the service in the network.";
76 leaf resource-reserve {
79 "indicates if resources (from local PCE topology) must be reserved until further notice (cancel-resource-reserve or topology update)";
82 uses transportpce-common-service-path-types:service-handler-header;
83 container service-a-end {
84 uses transportpce-common-service-path-types:service-endpoint-sp;
86 container service-z-end {
87 uses transportpce-common-service-path-types:service-endpoint-sp;
89 uses transportpce-routing-constraints:routing-constraints-sp;
92 uses org-openroadm-common-service-types:configuration-response-common;
93 uses transportpce-common-service-path-types:response-parameters-sp;
97 rpc cancel-resource-reserve {
103 uses transportpce-common-service-path-types:service-handler-header;
106 uses org-openroadm-common-service-types:configuration-response-common;
110 notification service-path-rpc-result {
112 "This Notification indicates result of service RPC";
113 leaf notification-type {
114 type transportpce-common-service-path-types:service-path-notification-types;
116 container path-description {
117 uses transportpce-pathDescription:path-description;
119 uses transportpce-common-service-path-types:rpc-response-status-ex;
120 uses org-openroadm-common-service-types:service-notification-result;
123 grouping stubpce-path-description {
127 "Identifier for the pathDescription to be created in
128 the ROADM network, e.g., CLFI, CLCI, etc.";
131 uses transportpce-pathDescription:path-description;
134 container path-description-list {
136 "List of pathDescription. Can only be created, deleted, modified, etc. using special RPCs.";
137 list pathDescriptions {
139 uses stubpce-path-description;