Newer
Older
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
module tapi-common {
namespace "urn:onf:otcc:yang:tapi-common";
prefix tapi-common;
organization "ONF OTCC (Open Transport Configuration & Control) Project";
contact "
Project Web: <https://wiki.opennetworking.org/display/OTCC/TAPI>
Project List: <mailto:transport-api@opennetworking.org>
Editor: Karthik Sethuraman
<mailto:karthik.sethuraman@necam.com>";
description "
This module contains TAPI Common Model definitions.
Source: TapiCommon.uml
Copyright (c) 2018 Open Networking Foundation (ONF). All rights reserved.
License: This module is distributed under the Apache License 2.0
- The TAPI YANG models included in this TAPI release are a *normative* part of the TAPI SDK.
- The YANG specifications have been generated from the corresponding UML model using the [ONF EAGLE UML2YANG mapping tool]
<https://github.com/OpenNetworkingFoundation/EagleUmlYang>
and further edited manually to comply with the [ONF IISOMI UML2YANG mapping guidelines]
<https://wiki.opennetworking.org/display/OIMT/UML+-+YANG+Guidelines>
- Status of YANG model artifacts can be determined by referring to the corresponding UML artifacts.
As described in the UML models, some artifacts are considered *experimental*, and thus the corresponding YANG artifacts.
- The ONF TAPI release process does not guarantee backward compatibility of YANG models across major versions of TAPI releases.
The YANG model backward compatibility criteria are outlined in section 11 of <https://tools.ietf.org/html/rfc7950>.
YANG models included in this release may not be backward compatible with previous TAPI releases.";
revision 2019-03-31 {
description "ONF Transport API version 2.2-RC1.
Changes included in this TAPI release (v2.2) are listed in
<https://github.com/OpenNetworkingFoundation/TAPI/blob/develop/CHANGE_LOG/change-log.2.2.md>";
reference "ONF-TR-527, ONF-TR-512, ONF-TR-531, RFC 7950, RFC 6087 and ONF TAPI UML model
<https://github.com/OpenNetworkingFoundation/TAPI/tree/v2.2.0/UML>";
}
revision 2018-12-10 {
description "ONF Transport API version 2.1.1.
Changes included in this TAPI release (v2.1.1) are listed in
<https://github.com/OpenNetworkingFoundation/TAPI/blob/develop/CHANGE_LOG/change-log.2.1.1.md>";
reference "ONF-TR-527, ONF-TR-512, ONF-TR-531, RFC 7950, RFC 6087 and ONF TAPI UML model
<https://github.com/OpenNetworkingFoundation/TAPI/tree/v2.1.1/UML>";
}
revision 2018-10-16 {
description "ONF Transport API version 2.1.0.
Changes included in this TAPI release (v2.1.0) are listed in
<https://github.com/OpenNetworkingFoundation/TAPI/blob/develop/CHANGE_LOG/change-log.2.1.0.md>";
reference "ONF-TR-527, ONF-TR-512, ONF-TR-531, RFC 7950, RFC 6087 and ONF TAPI UML model
<https://github.com/OpenNetworkingFoundation/TAPI/tree/v2.1.0/UML>";
}
revision 2018-03-07 {
description "ONF Transport API version 2.0.2
This YANG module has been generated from the TAPI UML Model using the IISOMI-Eagle xmi2yang mapping tool.
Changes in this revision: <https://github.com/OpenNetworkingFoundation/TAPI/blob/develop/CHANGE_LOG/change-log.2.0.2.md>";
reference "ONF-TR-527, ONF-TR-512, ONF-TR-531, RFC 6020, RFC 6087 and ONF TAPI UML model
<https://github.com/OpenNetworkingFoundation/TAPI/tree/v2.0.2/UML>";
}
revision 2018-02-16 {
description "ONF Transport API version 2.0.1
This YANG module has been generated from the TAPI UML Model using the IISOMI-Eagle xmi2yang mapping tool.
Changes in this revision: <https://github.com/OpenNetworkingFoundation/TAPI/blob/develop/CHANGE_LOG/change-log.2.0.1.md>";
reference "ONF-TR-527, ONF-TR-512, ONF-TR-531, RFC 6020, RFC 6087 and ONF TAPI UML model
<https://github.com/OpenNetworkingFoundation/TAPI/tree/v2.0.1/UML>";
}
revision 2018-01-02 {
description "ONF Transport API version 2.0.0
This YANG module has been generated from the TAPI UML Model using the IISOMI-Eagle xmi2yang mapping tool.
Changes in this revision: <https://github.com/OpenNetworkingFoundation/TAPI/blob/develop/CHANGE_LOG/change-log.2.0.0.md>";
reference "ONF-TR-527, ONF-TR-512, ONF-TR-531, RFC 6020, RFC 6087 and ONF TAPI UML model
<https://github.com/OpenNetworkingFoundation/TAPI/tree/v2.0.0/UML>";
}
/**************************
* definitions of references
**************************/
grouping service-interface-point-ref {
leaf service-interface-point-uuid {
type leafref {
path '/tapi-common:context/tapi-common:service-interface-point/tapi-common:uuid';
}
description "none";
}
description "none";
}
/**************************
* package object-classes
**************************/
grouping admin-state-pac {
leaf administrative-state {
type administrative-state;
description "The administration of managed objects operates independently of the operability and usage of managed objects and is described by the administrative state attribute. The administrative state is used by the operator to make a resource available for service, or to remove a resource from service.";
}
leaf operational-state {
type operational-state;
config false;
description "The operational state gives the information about the real capability of a resource to provide or not provide service.";
}
leaf lifecycle-state {
type lifecycle-state;
config false;
description "Used to track the planned deployment, allocation to clients and withdrawal of resources.";
}
description "Provides state attributes that are applicable to an entity that can be administered. Such an entity also has operational and lifecycle aspects.";
}
grouping global-class {
leaf uuid {
type uuid;
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.
UUID here uses string representation as defined in RFC 4122. The canonical representation uses lowercase characters.
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}
Example of a UUID in string representation: f81d4fae-7dec-11d0-a765-00a0c91e6bf6";
}
list name {
key 'value-name';
uses name-and-value;
description "List of names. This value 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.";
}
description "This class 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. ";
}
grouping lifecycle-state-pac {
leaf lifecycle-state {
type lifecycle-state;
config false;
description "Used to track the planned deployment, allocation to clients and withdrawal of resources.";
}
description "Provides state attributes for an entity that has lifecycle aspects only.";
}
grouping local-class {
leaf local-id {
type string;
description "An identifier that is unique in the context of the GlobalClass from which it is inseparable.";
}
list name {
key 'value-name';
uses name-and-value;
description "List of names. This value 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.";
}
description "This class serves as the super class for all TAPI entities that are ancillary of first class entities, i.e. their ID is not expected to be globally unique. ";
}
grouping operational-state-pac {
leaf operational-state {
type operational-state;
config false;
description "The operational state gives the information about the real capability of a resource to provide or not provide service.";
}
leaf lifecycle-state {
type lifecycle-state;
config false;
description "Used to track the planned deployment, allocation to clients and withdrawal of resources.";
}
description "Provides state attributes that are applicable to an entity that reflects operational aspects. Such an entity is expected to also have lifecycle aspects.";
}
container context {
uses tapi-context;
presence "Root container for all TAPI interaction";
description "none";
}
grouping tapi-context {
list service-interface-point {
key 'uuid';
uses service-interface-point;
description "none";
}
uses global-class;
description "This object class represents the scope of control that a particular SDN controller has with re-spect to a particular network, (i.e., encompassing a designated set of interconnected (virtual) network elements).
This class includes the list of Service Interface Points.";
}
grouping service-interface-point {
leaf layer-protocol-name {
type layer-protocol-name;
config false;
description "Usage of layerProtocolName [>1] in the ServiceInterfacePoint should be considered experimental";
}
leaf-list supported-layer-protocol-qualifier {
type layer-protocol-qualifier;
config false;
min-elements 1;
description "The supported sub-layer(s) or rate(s) of Layer Protocol.";
}
leaf direction {
type port-direction;
description "If direction attribute is missing the SIP instance is to be intended as 'BIDIRECTIONAL'";
}
uses global-class;
uses admin-state-pac;
uses capacity-pac;
description "A Service Interface Point represents the network-interface-facing aspects of the edge-port functions that access the forwarding capabilities provided by the Node. Hence it provides a limited, simplified view of interest to external clients (e.g. shared addressing, capacity, resource availability, etc.), that enable the clients to request connectivity without the need to understand the provider network internals.";
}
grouping capacity-pac {
container total-potential-capacity {
config false;
uses capacity;
description "An optimistic view of the capacity of the entity assuming that any shared capacity is available to be taken.";
}
container available-capacity {
config false;
uses capacity;
description "Capacity available to be assigned.";
}
description "Provides capacity related attributes.";
}
grouping termination-pac {
leaf termination-direction {
type termination-direction;
config false;
description "The overall directionality of the entity.
- A BIDIRECTIONAL entity will have some SINK and/or SOURCE flows.
- A SINK entity can only contain elements with SINK flows or CONTRA_DIRECTION_SOURCE flows.
- A SOURCE entity can only contain SOURCE flows or CONTRA_DIRECTION_SINK flows.";
}
leaf termination-state {
type termination-state;
config false;
description "Indicates whether the layer is terminated and if so how.";
}
description "This object class is associated to a Connection End Point to specify its direction and layer termination function.";
}
/**************************
* package type-definitions
**************************/
identity LAYER_PROTOCOL_QUALIFIER {
description "none";
}
identity LAYER_PROTOCOL_QUALIFIER_UNSPECIFIED {
base LAYER_PROTOCOL_QUALIFIER;
description "none";
}
identity OBJECT_TYPE {
description "none";
}
identity OBJECT_TYPE_SERVICE_INTERFACE_POINT {
base OBJECT_TYPE;
description "none";
}
typedef administrative-state {
type enumeration {
enum LOCKED {
description "Users are administratively prohibited from making use of the resource.";
}
enum UNLOCKED {
description "Users are allowed to use the resource";
}
}
description "The possible values of the administrativeState.";
}
typedef date-and-time {
type string;
description "This primitive type defines the date and time according to the following structure:
yyyyMMddhhmmss.s[Z|{+|-}HHMm] where:
yyyy 0000..9999 year
MM 01..12 month
dd 01..31 day
hh 00..23 hour
mm 00..59 minute
ss 00..59 second
s .0...9 tenth of second (set to .0 if EMS or NE cannot support this granularity)
Z Z indicates UTC (rather than local time)
{+|-} + or - delta from UTC
HH 00..23 time zone difference in hours
Mm 00..59 time zone difference in minutes.";
}
typedef directive-value {
type enumeration {
enum MINIMIZE {
description "none";
}
enum MAXIMIZE {
description "none";
}
enum ALLOW {
description "none";
}
enum DISALLOW {
description "none";
}
enum DONT_CARE {
description "none";
}
}
description "none";
}
typedef forwarding-direction {
type enumeration {
enum BIDIRECTIONAL {
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)";
}
enum UNIDIRECTIONAL {
description "The Forwarding entity has Ports that are either INPUT or OUTPUT. It has no BIDIRECTIONAL Ports.";
}
enum UNDEFINED_OR_UNKNOWN {
description "Not a normal state. The system is unable to determine the correct value.";
}
}
description "The directionality of a Forwarding entity.";
}
typedef layer-protocol-name {
type enumeration {
enum ODU {
description "Models the ODU layer as per ITU-T G.872";
}
enum ETH {
description "Models the ETH layer as per ITU-T G.8010";
}
enum DSR {
description "Models a Digital Signal of an unspecified rate. This value can be used when the intent is to respresent an generic digital layer signal without making any statement on its format or overhead (processing) capabilities.";
}
enum PHOTONIC_MEDIA {
description "Models the OCH, OTSi, OTSiA, OTSiG, OMS, OTS and Media channels as per ITU-T G.872 (2017) version 4";
}
}
description "Provides a controlled list of layer protocol names and indicates the naming authority.
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.
Layer protocol names include:
- Layer 1 (L1): OTU, ODU
- Layer 2 (L2): Carrier Grade Ethernet (ETY, ETH), MPLS-TP (MT)
";
}
typedef lifecycle-state {
type enumeration {
enum PLANNED {
description "The resource is planned but is not present in the network.";
}
enum POTENTIAL_AVAILABLE {
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.
o When a potential resource is configured and allocated to a client it is moved to the INSTALLED state for that client.
o If the potential resource has been consumed (e.g. allocated to another client) it is moved to the POTENTIAL_BUSY state for all other clients.";
}
enum POTENTIAL_BUSY {
description "The supporting resources are present in the network but have been allocated to other clients.";
}
enum INSTALLED {
description "The resource is present in the network and is capable of providing the service expected.";
}
enum PENDING_REMOVAL {
description "The resource has been marked for removal";
}
}
description "The possible values of the lifecycleState.";
}
grouping name-and-value {
leaf value-name {
type string;
description "The name of the value. The value need not have a name.";
}
leaf value {
type string;
description "The value";
}
description "A scoped name-value pair.";
}
typedef operational-state {
type enumeration {
enum DISABLED {
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.";
}
enum ENABLED {
description "The resource is partially or fully operable and available for use.";
}
}
description "The possible values of the operationalState.";
}
typedef port-direction {
type enumeration {
enum BIDIRECTIONAL {
description "The Port has both an INPUT flow and an OUTPUT flow defined.";
}
enum INPUT {
description "The Port only has definition for a flow into the Forwarding entity, (i.e. an ingress flow of the Link or Connection, hence egress flow of NEP or CEP, CSEP etc.).";
}
enum OUTPUT {
description "The Port only has definition for a flow out of the Forwarding entity ((i.e. an egress flow of the Link or Connection, hence ingress flow of NEP or CEP, CSEP etc.)";
}
enum UNIDENTIFIED_OR_UNKNOWN {
description "Not a normal state. The system is unable to determine the correct value.";
}
}
description "The orientation of flow at the Port of a Forwarding entity";
}
typedef port-role {
type enumeration {
enum SYMMETRIC {
description "none";
}
enum ROOT {
description "none";
}
enum LEAF {
description "none";
}
enum TRUNK {
description "none";
}
enum UNKNOWN {
description "none";
}
}
description "The role of an end in the context of the function of the forwarding entity that it bounds";
}
typedef termination-direction {
type enumeration {
enum BIDIRECTIONAL {
description "A Termination with both SINK and SOURCE flows.";
}
enum SINK {
description "The flow is up the layer stack from the server side to the client side.
Considering an example of a Termination function within the termination entity, a SINK flow:
- will arrive at at the base of the termination function (the server side) where it is essentially at an INPUT to the termination component
- then will be decoded and deconstructed
- 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
A SINK termination is one that only supports a SINK flow.
A SINK termiation can be bound to an OUTPUT Port of a Forwarding entity";
}
enum SOURCE {
description "The flow is down the layer stack from the server side to the client side.
Considering an example of a Termination function within the termination entity, a SOURCE flow:
- will arrive at at the top of the termination function (the client side) where it is essentially at an INPUT to the termination component
- then will be assembled with various overheads etc and will be coded
- 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
A SOURCE termination is one that only supports a SOURCE flow.
A SOURCE termiation can be bound to an INPUT Port of a Forwarding entity";
}
enum UNDEFINED_OR_UNKNOWN {
description "Not a normal state. The system is unable to determine the correct value.";
}
}
description "The directionality of a termination entity";
}
typedef termination-state {
type enumeration {
enum LP_CAN_NEVER_TERMINATE {
description "A non-flexible case that can never be terminated.";
}
enum LT_NOT_TERMINATED {
description "A flexible termination that can terminate but is currently not terminated.";
}
enum TERMINATED_SERVER_TO_CLIENT_FLOW {
description "A flexible termination that is currently terminated for server to client flow only.";
}
enum TERMINATED_CLIENT_TO_SERVER_FLOW {
description "A flexible termination that is currently terminated for client to server flow only.";
}
enum TERMINATED_BIDIRECTIONAL {
description "A flexible termination that is currently terminated in both directions of flow.";
}
enum LT_PERMENANTLY_TERMINATED {
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).";
}
enum TERMINATION_STATE_UNKNOWN {
description "There TerminationState cannot be determined.";
}
}
description "Provides support for the range of behaviours and specific states that an LP can take with respect to termination of the signal.
Indicates to what degree the LayerTermination is terminated.";
}
typedef uuid {
type string;
description "The univeral ID value where the mechanism for generation is defned by some authority not directly referenced in the structure.
UUID here uses string representation as defined in RFC 4122. The canonical representation uses lowercase characters.
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}
Example of a UUID in string representation: f81d4fae-7dec-11d0-a765-00a0c91e6bf6";
}
grouping capacity {
container total-size {
uses capacity-value;
description "Total capacity of the entity. In case of bandwidthProfile, this is expected to same as the committedInformationRate.";
}
description "Information on capacity of a particular entity.";
}
grouping capacity-value {
leaf value {
type uint64;
description "none";
}
leaf unit {
type capacity-unit;
description "none";
}
description "The Capacity (Bandwidth) values that are applicable for digital layers.";
}
typedef capacity-unit {
type enumeration {
enum TB {
description "Indicates that the integer CapacityValue is in TeraBytes";
}
enum TBPS {
description "Indicates that the integer CapacityValue is in Terabit-per-second";
}
enum GB {
description "Indicates that the integer CapacityValue is in GigaBytes";
}
enum GBPS {
description "Indicates that the integer CapacityValue is in Gigabit-per-second";
}
enum MB {
description "Indicates that the integer CapacityValue is in MegaBytes";
}
enum MBPS {
description "Indicates that the integer CapacityValue is in Megabit-per-second";
}
enum KB {
description "Indicates that the integer CapacityValue is in KiloBytes";
}
enum KBPS {
description "Indicates that the integer CapacityValue is in Kilobit-per-second";
}
enum GHz {
description "none";
}
enum MHz {
description "none";
}
}
description "none";
}
grouping time-range {
leaf end-time {
type date-and-time;
description "none";
}
leaf start-time {
type date-and-time;
description "none";
}
description "none";
}
grouping time-period {
leaf value {
type uint64;
description "none";
}
leaf unit {
type time-unit;
description "none";
}
description "none";
}
typedef time-unit {
type enumeration {
enum YEARS {
description "none";
}
enum MONTHS {
description "none";
}
enum DAYS {
description "none";
}
enum HOURS {
description "none";
}
enum MINUTES {
description "none";
}
enum SECONDS {
description "none";
}
enum MILLISECONDS {
description "none";
}
enum MICROSECONDS {
description "none";
}
enum NANOSECONDS {
description "none";
}
enum PICOSECONDS {
description "none";
}
}
description "none";
}
grouping time-interval {
list period {
key 'unit';
min-elements 1;
max-elements 5;
uses time-period;
description "none";
}
description "none";
}
typedef layer-protocol-qualifier {
type identityref {
base LAYER_PROTOCOL_QUALIFIER;
}
description "This enumeration is used to qualify the sub-layers (if applicable) for a specific LayerProtocol.
This extensible enumeration is intentionally empty in the common module and will be augmented with layer-specific values in the respective technology-specific modules.
Examples:
- LayerProtocolName := OPTICAL_DATA_UNIT
LayerProtocolQualifier := 'ODU_FLEX', 'ODU_0', 'ODU_1', 'ODU_2', 'ODU_2E', 'ODU_3', 'ODU_4'', 'ODU_CBR'', 'ODU_GFP'', 'ODU_GFP_HAO', etc
- LayerProtocolName := DIGITAL_SIGNAL_RATE
LayerProtocolQualifier := 'GBE', '10_GBE_WAN', '10_GBE_LAN', '100_GBE', 'FC_100', 'FC_200', 'FC_400', 'FC_800', 'FC_1200', 'FC_1600', 'FC_3200', 'STM_1', 'STM_4', 'STM_16', 'STM_64', 'STM_256', 'OC_3', 'OC_12', 'OC_48', 'OC_192', 'OC_768', 'OTU_1', 'OTU_2', 'OTU_2E', 'OTU_3', 'OTU_4', 'GPON', 'XGPON', 'IB_SDR', 'IB_DDR', 'IB_QDR', 'SBCON_ESCON', 'DVB_ASI', 'SDI', 'SDI_1G5', 'SDI_3G', etc
- LayerProtocolName := PHOTONIC_MEDIA
LayerProtocolQualifier := OCH, OTSi, OTSiA, NMC, NMCA, SMC, SMCA, OMS, OTS
";
}
typedef mac-address {
type string;
description "pattern '[0-9a-fA-F]{2}(-[0-9a-fA-F]{2}){5}'
description
'The mac-address type represents a MAC address in the canonical
format and hexadecimal format specified by IEEE Std 802. The
hexidecimal representation uses uppercase characters.'";
}
typedef binary-type {
type string;
description "Represents any binary data, i.e., a sequence of octets.
A binary type can be restricted by a length which defines the number of octets it contains.";
}
typedef timeticks {
type string;
description "type uint32
The timeticks type represents a non-negative integer that represents the time, modulo 2^32 (4294967296 decimal), in hundredths of a second between two epochs.";
}
typedef object-type {
type identityref {
base OBJECT_TYPE;
}
description "The list of TAPI Common Object types/classes.";
}
/**************************
* package interfaces
**************************/
rpc get-service-interface-point-details {
description "none";
input {
leaf uuid {
type uuid;
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.
UUID here uses string representation as defined in RFC 4122. The canonical representation uses lowercase characters.
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}
Example of a UUID in string representation: f81d4fae-7dec-11d0-a765-00a0c91e6bf6";
}
}
output {
container sip {
uses service-interface-point;
description "none";
}
}
}
rpc get-service-interface-point-list {
description "none";
output {
list sip {
key 'uuid';
uses service-interface-point;
description "none";
}
}
}
rpc update-service-interface-point {
description "none";
input {
leaf uuid {
type uuid;
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.
UUID here uses string representation as defined in RFC 4122. The canonical representation uses lowercase characters.
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}
Example of a UUID in string representation: f81d4fae-7dec-11d0-a765-00a0c91e6bf6";
}
leaf state {
type administrative-state;
description "none";
}
}
}
}