2 namespace "urn:mef:yang:TapiCommon";
4 organization "Metro Ethernet Forum (MEF)";
8 description "MEF NRP 1.0.alpha";
9 reference "ONF-TR-527, ONF-TR-512, ONF-TR-531, RFC 6020 and RFC 6087";
11 /***********************
12 * package object-classes
13 **********************/
14 grouping admin-state-pac {
15 leaf administrative-state {
16 type administrative-state;
19 leaf operational-state {
20 type operational-state;
23 leaf lifecycle-state {
27 description "Provides state attributes that are applicable to an entity that can be administered. Such an entity also has operational and lifecycle aspects.";
29 grouping global-class {
32 description "UUID: An identifier that is universally unique within an identifier space, where the identifier space is itself globally unique, and immutable. An UUID carries no semantics with respect to the purpose or state of the entity.
33 UUID here uses string representation as defined in RFC 4122. The canonical representation uses lowercase characters.
34 Pattern: [0-9a-fA-F]{8}-[0-9a-fA-F]{4}-[0-9a-fA-F]{4}-' + '[0-9a-fA-F]{4}-[0-9a-fA-F]{12}
35 Example of a UUID in string representation: f81d4fae-7dec-11d0-a765-00a0c91e6bf6";
40 description "List of names. A property of an entity with a value that is unique in some namespace but may change during the life of the entity. A name carries no semantics with respect to the purpose of the entity.";
45 description "List of labels.A property of an entity with a value that is not expected to be unique and is allowed to change. A label carries no semantics with respect to the purpose of the entity and has no effect on the entity behavior or state.";
47 description "The TAPI GlobalComponent serves as the super class for all TAPI entities that can be directly retrieved by their ID. As such, these are first class entities and their ID is expected to be globally unique. ";
49 grouping layer-protocol {
50 leaf layer-protocol-name {
51 type layer-protocol-name;
52 description "Indicate the specific layer-protocol described by the LayerProtocol entity.";
54 leaf termination-direction {
55 type termination-direction;
56 description "The overall directionality of the LP.
57 - A BIDIRECTIONAL LP will have some SINK and/or SOURCE flowss.
58 - A SINK LP can only contain elements with SINK flows or CONTRA_DIRECTION_SOURCE flows
59 - A SOURCE LP can only contain SOURCE flows or CONTRA_DIRECTION_SINK flows";
61 leaf termination-state {
62 type termination-state;
63 description "Indicates whether the layer is terminated and if so how.";
66 description "Each transport layer is represented by a LayerProtocol (LP) instance. The LayerProtocol instances it can be used for controlling termination and monitoring functionality.
67 It can also be used for controlling the adaptation (i.e. encapsulation and/or multiplexing of client signal), tandem connection monitoring, traffic conditioning and/or shaping functionality at an intermediate point along a connection.
68 Where the client – server relationship is fixed 1:1 and immutable, the layers can be encapsulated in a single LTP instance. Where the is a n:1 relationship between client and server, the layers must be split over two separate instances of LTP. ";
70 grouping lifecycle-state-pac {
71 leaf lifecycle-state {
75 description "Provides state attributes for an entity that has lifeccycle aspects only.";
77 grouping local-class {
85 description "List of names. A property of an entity with a value that is unique in some namespace but may change during the life of the entity. A name carries no semantics with respect to the purpose of the entity.";
87 description "The TAPI GlobalComponent serves as the super class for all TAPI entities that can be directly retrieved by their ID. As such, these are first class entities and their ID is expected to be globally unique. ";
89 grouping operational-state-pac {
90 leaf operational-state {
91 type operational-state;
94 leaf lifecycle-state {
98 description "Provides state attributes that are applicable to an entity that reflects operational aspects. Such an entity is expected to also have lifecycle aspects.";
100 grouping time-range {
115 grouping context-attrs {
116 list service-interface-point {
120 uses service-interface-point;
124 description "The Network Control Domain (NCD) object class represents the scope of control that a particular SDN controller has with respect to a particular network, (i.e., encompassing a designated set of interconnected (virtual) network elements).";
126 grouping resource-spec {
130 grouping service-spec {
134 grouping service-interface-point {
135 list layer-protocol {
144 uses lifecycle-state-pac;
148 type termination-direction;
153 description "The LogicalTerminationPoint (LTP) object class encapsulates the termination and adaptation functions of one or more transport layers.
154 The structure of LTP supports all transport protocols including circuit and packet forms.";
157 /***********************
158 * package type-definitions
159 **********************/
160 typedef administrative-state {
163 description "Users are administratively prohibited from making use of the resource.";
166 description "Users are allowed to use the resource";
169 description "The possible values of the administrativeState.";
171 typedef date-and-time {
173 description "This primitive type defines the date and time according to the following structure:
174 yyyyMMddhhmmss.s[Z|{+|-}HHMm] where:
181 s .0...9 tenth of second (set to .0 if EMS or NE cannot support this granularity)
182 Z Z indicates UTC (rather than local time)
183 {+|-} + or - delta from UTC
184 HH 00..23 time zone difference in hours
185 Mm 00..59 time zone difference in minutes.";
187 typedef directive-value {
207 typedef forwarding-direction {
210 description "The Fowarding entity supports both BIDIRECTIONAL flows at all Ports (i.e. all Ports have both an INPUT flow and an OUTPUT flow defined)";
212 enum unidirectional {
213 description "The Forwarding entity has Ports that are either INPUT or OUTPUT. It has no BIDIRECTIONAL Ports.";
215 enum undefined-or-unknown {
216 description "Not a normal state. The system is unable to determine the correct value.";
219 description "The directionality of a Forwarding entity.";
221 typedef layer-protocol-name {
236 description "Provides a controlled list of layer protocol names and indicates the naming authority.
237 Note that it is expected that attributes will be added to this structure to convey the naming authority name, the name of the layer protocol using a human readable string and any particular standard reference.
238 Layer protocol names include:
239 - Layer 1 (L1): OTU, ODU
240 - Layer 2 (L2): Carrier Grade Ethernet (ETY, ETH), MPLS-TP (MT)
243 typedef lifecycle-state {
246 description "The resource is planned but is not present in the network.";
249 description "The supporting resources are present in the network but are shared with other clients; or require further configuration before they can be used; or both.
250 o When a potential resource is configured and allocated to a client it is moved to the “installed” state for that client.
251 o If the potential resource has been consumed (e.g. allocated to another client) it is moved to the “planned” state for all other clients.";
254 description "The resource is present in the network and is capable of providing the service expected.";
256 enum pending-removal {
257 description "The resource has been marked for removal";
260 description "The possible values of the lifecycleState.";
262 grouping name-and-value {
265 description "The name of the value. The value need not have a name.";
269 description "The value";
271 description "A scoped name-value pair";
273 typedef operational-state {
276 description "The resource is unable to meet the SLA of the user of the resource. If no (explicit) SLA is defined the resource is disabled if it is totally inoperable and unable to provide service to the user.";
279 description "The resource is partially or fully operable and available for use";
282 description "The possible values of the operationalState.";
284 typedef port-direction {
287 description "The Port has both an INPUT flow and an OUTPUT flow defined.";
290 description "The Port only has definition for a flow into the Forwarding entity (i.e. an ingress flow).";
293 description "The Port only has definition for a flow out of the Forwarding entity (i.e. an egress flow).";
295 enum unidentified-or-unknown {
296 description "Not a normal state. The system is unable to determine the correct value.";
299 description "The orientation of flow at the Port of a Forwarding entity";
316 description "The role of an end in the context of the function of the forwarding entity that it bounds";
318 typedef termination-direction {
321 description "A Termination with both SINK and SOURCE flows.";
324 description "The flow is up the layer stack from the server side to the client side.
325 Considering an example of a Termination function within the termination entity, a SINK flow:
326 - will arrive at at the base of the termination function (the server side) where it is essentially at an INPUT to the termination component
327 - then will be decoded and deconstructed
328 - then relevant parts of the flow will be sent out of the termination function (the client side) where it is essentially at an OUTPUT from the termination component
329 A SINK termination is one that only supports a SINK flow.
330 A SINK termiation can be bound to an OUTPUT Port of a Forwarding entity";
333 description "The flow is down the layer stack from the server side to the client side.
334 Considering an example of a Termination function within the termination entity, a SOURCE flow:
335 - will arrive at at the top of the termination function (the client side) where it is essentially at an INPUT to the termination component
336 - then will be assembled with various overheads etc and will be coded
337 - then coded form of the assembly of flow will be sent out of the termination function (the server side) where it is essentially at an OUTPUT from the termination component
338 A SOURCE termination is one that only supports a SOURCE flow.
339 A SOURCE termiation can be bound to an INPUT Port of a Forwarding entity";
341 enum undefined-or-unknown {
342 description "Not a normal state. The system is unable to determine the correct value.";
345 description "The directionality of a termination entity";
347 typedef termination-state {
349 enum lp-can-never-terminate {
350 description "A non-flexible case that can never be terminated.";
352 enum lt-not-terminated {
353 description "A flexible termination that can terminate but is currently not terminated.";
355 enum terminated-server-to-client-flow {
356 description "A flexible termination that is currently terminated for server to client flow only.";
358 enum terminated-client-to-server-flow {
359 description "A flexible termination that is currently terminated for client to server flow only.";
361 enum terminated-bidirectional {
362 description "A flexible termination that is currently terminated in both directions of flow.";
364 enum lt-permenantly-terminated {
365 description "A non-flexible termination that is always terminated (in both directions of flow for a bidirectional case and in the one direction of flow for both unidirectional cases).";
367 enum termination-state-unknown {
368 description "There TerminationState cannot be determined.";
371 description "Provides support for the range of behaviours and specific states that an LP can take with respect to termination of the signal.
372 Indicates to what degree the LayerTermination is terminated.";
374 typedef universal-id {
376 description "The univeral ID value where the mechanism for generation is defned by some authority not directly referenced in the structure.
377 UUID here uses string representation as defined in RFC 4122. The canonical representation uses lowercase characters.
378 Pattern: [0-9a-fA-F]{8}-[0-9a-fA-F]{4}-[0-9a-fA-F]{4}-' + '[0-9a-fA-F]{4}-[0-9a-fA-F]{12}
379 Example of a UUID in string representation: f81d4fae-7dec-11d0-a765-00a0c91e6bf6";
382 /***********************
384 **********************/
385 rpc get-service-interface-point-details {
388 leaf sip-id-or-name {
395 uses service-interface-point;
400 rpc get-service-interface-point-list {
404 uses service-interface-point;