-
Notifications
You must be signed in to change notification settings - Fork 652
/
openconfig-terminal-device.yang
1720 lines (1426 loc) · 51.5 KB
/
openconfig-terminal-device.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 openconfig-terminal-device {
yang-version "1";
// namespace
namespace "http://openconfig.net/yang/terminal-device";
prefix "oc-opt-term";
import openconfig-types { prefix oc-types; }
import openconfig-transport-types { prefix oc-opt-types; }
import openconfig-if-ethernet { prefix oc-eth; }
import openconfig-interfaces { prefix oc-if; }
import openconfig-platform { prefix oc-platform; }
import openconfig-platform-transceiver { prefix oc-transceiver; }
import openconfig-lldp { prefix oc-lldp; }
import openconfig-extensions { prefix oc-ext; }
import ietf-yang-types { prefix yang; }
import openconfig-yang-types { prefix oc-yang; }
// meta
organization "OpenConfig working group";
contact
"OpenConfig working group
www.openconfig.net";
description
"This module describes a terminal optics device model for
managing the terminal systems (client and line side) in a
DWDM transport network.
Elements of the model:
physical port: corresponds to a physical, pluggable client
port on the terminal device. Examples includes 10G, 40G, 100G
(e.g., 10x10G, 4x25G or 1x100G) and 400G/1T in the future.
Physical client ports will have associated operational state or
PMs.
physical channel: a physical lane or channel in the
physical client port. Each physical client port has 1 or more
channels. An example is 100GBASE-LR4 client physical port having
4x25G channels. Channels have their own optical PMs and can be
monitored independently within a client physical port (e.g.,
channel power). Physical client channels are defined in the
model as part of a physical client port, and are modeled
primarily for reading their PMs.
logical channel: a logical grouping of logical grooming elements
that may be assigned to subsequent grooming stages for
multiplexing / de-multiplexing, or to an optical channel for
line side transmission. The logical channels can represent, for
example, an ODU/OTU logical packing of the client
data onto the line side. Tributaries are similarly logical
groupings of demand that can be represented in this structure and
assigned to an optical channel. Note that different types of
logical channels may be present, each with their corresponding
PMs.
optical channel: corresponds to an optical carrier and is
assigned a wavelength/frequency. Optical channels have PMs
such as power, BER, and operational mode.
Directionality:
To maintain simplicity in the model, the configuration is
described from client-to-line direction. The assumption is that
equivalent reverse configuration is implicit, resulting in
the same line-to-client configuration.
Physical layout:
The model does not assume a particular physical layout of client
and line ports on the terminal device (e.g., such as number of
ports per linecard, separate linecards for client and line ports,
etc.).";
oc-ext:openconfig-version "1.9.2";
revision "2024-06-12" {
description
"Add a state leaf to optical channels to reference their logical
channel assignment.";
reference "1.9.2";
}
revision "2023-12-13" {
description
"Add reference to the terminal-device-properties-guide.md doc for
operational-mode.";
reference "1.9.1";
}
revision "2021-07-29" {
description
"Add several coherent performance monitors to optical channel.
Re-group and add PHY-related performance monitors to optical
channel and logical channel.";
reference "1.9.0";
}
revision "2021-02-23" {
description
"Small additions to support ZR transceivers. Adds a new
ingress type of interface and a client mapping mode leaf.";
reference "1.8.0";
}
revision "2020-05-09" {
description
"Remove references from read-write contexts to read-only
contexts in when statements.";
reference "1.7.3";
}
revision "2019-11-28" {
description
"Additional xpath fixes in when statement";
reference "1.7.2";
}
revision "2019-10-12" {
description
"Fix when statement paths";
reference "1.7.1";
}
revision "2019-08-08" {
description
"Add ALS config to logical-channel/ethernet/config and remove
legacy interfaces augment for this config. Client FEC was
previosuly migrated to the components model and should not
be here anymore.";
reference "1.7.0";
}
revision "2019-07-26" {
description
"Add support for LLDP natively on logical-channels.";
reference "1.6.0";
}
revision "2018-11-21" {
description
"Add OpenConfig module metadata extensions.";
reference "1.5.1";
}
revision "2018-10-23" {
description
"Adds support of logical-channel tributary slot allocation to
logical-channel-assignments with different channel speeds.
Enables logical channel mapping procedure specification.";
reference "1.5.0";
}
revision "2018-08-28" {
description
"Adds terminal device related Ethernet counters";
reference "1.4.0";
}
revision "2018-07-30" {
description
"Adds lldp snooping config leaf and augmented it to oc-lldp";
reference "1.3.0";
}
revision "2018-07-26" {
description
"Adds OTN protocol counter stats of errored-blocks and
fec-uncorrectable-blocks, adds ethernet-config-ext grouping
and uses it to augment oc-eth";
reference "1.2.0";
}
revision "2018-07-17" {
description
"Adds testing enum to link-state";
reference "1.1.0";
}
revision "2017-07-08" {
description
"Adds test-signal";
reference "1.0.0";
}
revision "2016-12-22" {
description
"Fixes and additions to terminal optics model";
reference "0.4.0";
}
// OpenConfig specific extensions for module metadata.
oc-ext:regexp-posix;
oc-ext:catalog-organization "openconfig";
oc-ext:origin "openconfig";
grouping terminal-input-optical-power {
description
"Reusable leaves related to input optical power";
leaf input-power {
type decimal64 {
fraction-digits 2;
}
units dBm;
description
"The input optical power of this port in units of 0.01dBm.
If the port is an aggregate of multiple physical channels,
this attribute is the total power or sum of all channels.";
}
}
grouping terminal-ethernet-protocol-config {
description
"Configuration data for logical channels with Ethernet
framing";
leaf client-als {
type enumeration {
enum NONE {
description
"The client port will do nothing when a failure is
detected on the line port or the remote client port";
}
enum LASER_SHUTDOWN {
description
"The client port will shut down the laser to notify the
subtending Ethernet equipment of the failure detected on
the line port or the remote client port.";
}
enum ETHERNET {
description
"The client port will propagate the local fault or remote
fault signal to the subtending Ethernet equipment.";
}
}
default ETHERNET;
description
"Sets the client port behavior that defines if the actions
of automatic laser shutdown (als), ethernet fault
propagation, or nothing will be done upon the detection
of a failure on the line port or the upstream remote
client port.";
}
leaf als-delay {
type uint32;
units milliseconds;
default 0;
description
"The timer to delay the client-als actions on the client
port when a local or remote fault is detected on the line
port. The delay will only be valid when the client-als is
set to LASER_SHUTDOWN";
}
}
grouping terminal-ethernet-protocol-state {
description
"Ethernet-specific counters when logical channel
is using Ethernet protocol framing, e.g., 10GE, 100GE";
uses oc-eth:ethernet-interface-state-counters;
uses terminal-ethernet-protocol-state-counters;
uses terminal-phy-protocol-stats {
description
"When 400ZR/ZR+ transceivers are plugged in switches or routers,
this grouping will be attached to logical channel with Ethernet
protocol framing, in order to involve host-side fec-related
error performances.";
}
}
grouping terminal-ethernet-protocol-state-counters {
description
"Ethernet-specific counters for terminal devices when
logical channel is using Ethernet protocol framing,
e.g., 10GE, 100GE";
// ingress counters
leaf in-pcs-bip-errors {
type oc-yang:counter64;
description
"The number of received bit interleaved parity (BIP) errors
at the physical coding sublayer (PCS). If the interface
consists of multiple lanes, this will be the sum of all
errors on the lane";
}
leaf in-pcs-errored-seconds {
type oc-yang:counter64;
description
"The number of seconds that physical coding sublayer (PCS)
errors have crossed a sytem defined threshold indicating the
link is erroring";
}
leaf in-pcs-severely-errored-seconds {
type oc-yang:counter64;
description
"The number of seconds that physical coding sublayer (PCS)
errors have crossed a system defined threshold indicating the
link is severely erroring";
}
leaf in-pcs-unavailable-seconds {
type oc-yang:counter64;
description
"The number of seconds that physical coding sublayer (PCS)
errors have crossed a system defined threshold indicating the
link is unavailable";
}
// egress counters
leaf out-pcs-bip-errors {
type oc-yang:counter64;
description
"The number of transmitted bit interleaved parity (BIP) errors
at the physical coding sublayer (PCS). If the interface
consists of multiple lanes, this will be the sum of all
errors on the lane";
}
leaf out-crc-errors {
type oc-yang:counter64;
description
"Number of FCS/CRC error check failures sent on the interface";
}
leaf out-block-errors {
type oc-yang:counter64;
description
"The number of transmitted errored blocks. Error detection
codes are capable of detecting whether one or more errors have
occurred in a given sequence of bits – the block. It is
normally not possible to determine the exact number of errored
bits within the block";
}
}
grouping terminal-ethernet-protocol-top {
description
"Top-level grouping for data related to Ethernet protocol
framing on logical channels";
container ethernet {
description
"Top level container for data related to Ethernet framing
for the logical channel";
container config {
description
"Configuration data for Ethernet protocol framing on
logical channels";
uses terminal-ethernet-protocol-config;
}
container state {
config false;
description
"Operational state data for Ethernet protocol framing
on logical channels";
uses terminal-ethernet-protocol-config;
uses terminal-ethernet-protocol-state;
}
uses lldp-logical-channel-top;
}
}
grouping lldp-logical-channel-top {
description
"Top-level grouping for LLDP data for a logical channel";
container lldp {
description
"LLDP data for logical channels";
container config {
description
"LLDP configuration data for logical channels";
uses lldp-logical-channel-config;
}
container state {
config false;
description
"LLDP operational state data for logical channels";
uses lldp-logical-channel-config;
uses oc-lldp:lldp-interface-state;
}
uses lldp-logical-channel-neighbor-top;
}
}
grouping lldp-logical-channel-config {
description
"Configuration data for LLDP for logical-channels";
leaf enabled {
type boolean;
default "false";
description
"Enable or disable the LLDP protocol on the logical channel.";
}
leaf snooping {
type boolean;
default "false";
description
"If true, LLDP PDUs are only received and processed on
the logical-channel, but are not originated by the local
agent. The PDUs are not dropped by the logical channel after
processing, but relayed to the downstream link layer
neighbors. The snooping mode is valid only when LLDP is
enabled on the logical channel. The snooping mode is useful
when a logical channel does not want its link layer neighbors
to discover itself since, for example, it is a lower-layer
logical channel.";
}
}
grouping lldp-logical-channel-neighbor-top {
description
"Top-level grouping for the LLDP neighbor list";
container neighbors {
config false;
description
"Enclosing container for list of LLDP neighbors on
a logical channel";
list neighbor {
key "id";
description
"List of LLDP neighbors. If the implementation only
supports one neighbor, this would always be a list with
one item. If the device and neighbor supported multiple
neighbors, which can be achieved via LLDP forwarding, then
this would be supported";
reference
"IEEE Std 802.1AB-2016, section 7.1, Destination address";
leaf id {
type leafref {
path "../state/id";
}
description
"System generated identifier for the neighbor on
the logical channel.";
}
container config {
description
"Configuration data ";
uses lldp-logical-channel-neighbor-config;
}
container state {
config false;
description
"Operational state data ";
uses oc-lldp:lldp-system-info-config;
uses oc-lldp:lldp-system-info-state;
uses oc-lldp:lldp-neighbor-config;
uses oc-lldp:lldp-neighbor-state;
}
uses oc-lldp:lldp-custom-tlv-top;
}
}
}
grouping lldp-logical-channel-neighbor-config {
description
"Configuration data for LLDP neighbors";
}
grouping terminal-otn-protocol-config {
description
"OTU configuration when logical channel
framing is using an OTU protocol, e.g., OTU1, OTU3, etc.";
leaf tti-msg-transmit {
type string;
description
"Trail trace identifier (TTI) message transmitted";
}
leaf tti-msg-expected {
type string;
description
"Trail trace identifier (TTI) message expected";
}
leaf tti-msg-auto {
type boolean;
description
"Trail trace identifier (TTI) transmit message automatically
created. If true, then setting a custom transmit message
would be invalid.";
}
leaf tributary-slot-granularity {
type identityref {
base oc-opt-types:TRIBUTARY_SLOT_GRANULARITY;
}
description
"Granularity value of OPUk or OPUCn tributary slots for OTN
signal allocation. The currently defined values follow the
existing ITU-T G.709 standard, which can be extended as
needed in future.";
}
}
grouping terminal-otn-protocol-counter-stats {
description
"Counter based statistics containers for logical channels
using OTN framing";
leaf errored-seconds {
type yang:counter64;
description
"The number of seconds that at least one errored blocks
occurs, at least one code violation occurs, loss of sync is
detected or loss of signal is detected";
}
leaf severely-errored-seconds {
type yang:counter64;
description
"The number of seconds that loss of frame is detected OR
the number of errored blocks, code violations, loss of sync
or loss of signal is detected exceeds a predefined
threshold";
}
leaf unavailable-seconds {
type yang:counter64;
description
"The number of seconds during which the link is unavailable";
}
leaf code-violations {
type yang:counter64;
description
"For ethernet or fiberchannel links, the number of 8b/10b
coding violations. For SONET/SDH, the number of BIP (bit
interleaved parity) errors";
}
leaf errored-blocks {
type yang:counter64;
description
"The number of errored blocks. Error detection codes are
capable to detect whether one or more errors have occurred
in a given sequence of bits – the block. It is normally not
possible to determine the exact number of errored bits within
the block.";
reference "ITU-T Rec. G.826";
}
leaf fec-uncorrectable-words {
type yang:counter64;
description
"The number of words that were uncorrectable by the FEC";
}
leaf fec-corrected-bytes {
type yang:counter64;
description
"The number of bytes that were corrected by the FEC";
}
leaf fec-corrected-bits {
type yang:counter64;
description
"The number of bits that were corrected by the FEC";
}
leaf background-block-errors {
type yang:counter64;
description
"The number of background block errors";
}
}
grouping terminal-phy-protocol-stats {
description
"Counters and multi-value statistics for FEC-related error
performance";
leaf fec-uncorrectable-blocks {
type yang:counter64;
description
"The number of blocks or frames that were uncorrectable by
the FEC";
}
container pre-fec-ber {
description
"Bit error rate before forward error correction -- computed
value with 18 decimal precision. Note that decimal64
supports values as small as i x 10^-18 where i is an
integer. Values smaller than this should be reported as 0
to inidicate error free or near error free performance.
Values include the instantaneous, average, minimum, and
maximum statistics. If avg/min/max statistics are not
supported, the target is expected to just supply the
instant value";
uses oc-opt-types:avg-min-max-instant-stats-precision18-ber;
}
container post-fec-ber {
description
"Bit error rate after forward error correction -- computed
value with 18 decimal precision. Note that decimal64
supports values as small as i x 10^-18 where i is an
integer. Values smaller than this should be reported as 0
to inidicate error free or near error free performance.
Values include the instantaneous, average, minimum, and
maximum statistics. If avg/min/max statistics are not
supported, the target is expected to just supply the
instant value";
uses oc-opt-types:avg-min-max-instant-stats-precision18-ber;
}
container q-value {
description
"Quality value (factor) in dB of a channel with two
decimal precision. Values include the instantaneous,
average, minimum, and maximum statistics. If avg/min/max
statistics are not supported, the target is expected
to just supply the instant value";
uses oc-types:avg-min-max-instant-stats-precision2-dB;
}
container esnr {
description
"Electrical signal to noise ratio. Baud rate
normalized signal to noise ratio based on
error vector magnitude in dB with two decimal
precision. Values include the instantaneous, average,
minimum, and maximum statistics. If avg/min/max
statistics are not supported, the target is expected
to just supply the instant value";
uses oc-types:avg-min-max-instant-stats-precision2-dB;
}
}
grouping terminal-otn-protocol-state {
description
"OTU operational state when logical channel
framing is using an OTU protocol, e.g., OTU1, OTU3, etc.";
leaf tti-msg-recv {
type string;
description
"Trail trace identifier (TTI) message received";
}
leaf rdi-msg {
type string;
description
"Remote defect indication (RDI) message received";
}
uses terminal-otn-protocol-counter-stats;
uses terminal-phy-protocol-stats {
description
"This grouping may be used when the logical-channel-type
is 'PROT_OTN.";
}
}
grouping terminal-otn-protocol-top {
description
"Top-level grouping for data related to OTN protocol framing";
container otn {
description
"Top level container for OTU configuration when logical
channel framing is using an OTU protocol, e.g., OTU1, OTU3,
etc.";
container config {
description
"Configuration data for OTN protocol framing";
uses terminal-otn-protocol-config;
}
container state {
config false;
description
"Operational state data for OTN protocol PMs, statistics,
etc.";
uses terminal-otn-protocol-config;
uses terminal-otn-protocol-state;
}
}
}
grouping terminal-client-port-assignment-config {
description
"Configuration data for assigning physical client ports to
logical channels";
leaf index {
type uint32;
description
"Index of the client port assignment";
}
leaf description {
type string;
description
"Descriptive name for the client port-to-logical channel
mapping";
}
leaf logical-channel {
type leafref {
path "/oc-opt-term:terminal-device/oc-opt-term:logical-channels" +
"/oc-opt-term:channel/oc-opt-term:index";
}
description
"Reference to the logical channel for this
assignment";
}
leaf allocation {
type decimal64 {
fraction-digits 3;
}
units Gbps;
description
"Allocation of the client physical port to the assigned
logical channel expressed in Gbps. In most cases,
the full client physical port rate is assigned to a single
logical channel.";
}
}
grouping terminal-client-port-assignment-state {
description
"Operational state data for assigning physical client ports
to logical channels";
}
grouping terminal-client-port-assignment-top {
description
"Top-level grouping for the assigment of client physical ports
to logical channels";
//TODO: this grouping could be removed, instead reusing a common
//grouping for logical client assignment pointers
container logical-channel-assignments {
description
"Enclosing container for client port to logical client
mappings";
list assignment {
key "index";
description
"List of assignments to logical clients";
leaf index {
type leafref {
path "../config/index";
}
description
"Reference to the index of this logical client
assignment";
}
container config {
description
"Configuration data for the logical client assignment";
uses terminal-client-port-assignment-config;
}
container state {
config false;
description
"Operational state data for the logical client
assignment";
uses terminal-client-port-assignment-config;
uses terminal-client-port-assignment-state;
}
}
}
}
grouping terminal-logical-chan-assignment-config {
description
"Configuration data for assigning client logical channels
to line-side tributaries";
leaf index {
type uint32;
description
"Index of the current logical client channel to tributary
mapping";
}
leaf description {
type string;
description
"Name assigned to the logical client channel";
}
leaf assignment-type {
type enumeration {
enum LOGICAL_CHANNEL {
description
"Subsequent channel is a logical channel";
}
enum OPTICAL_CHANNEL {
description
"Subsequent channel is a optical channel / carrier";
}
}
description
"Each logical channel element may be assigned to subsequent
stages of logical elements to implement further grooming, or
can be assigned to a line-side optical channel for
transmission. Each assignment also has an associated
bandwidth allocation.";
}
leaf logical-channel {
type leafref {
path "/oc-opt-term:terminal-device/" +
"oc-opt-term:logical-channels/oc-opt-term:channel/" +
"oc-opt-term:index";
}
must "../assignment-type = 'LOGICAL_CHANNEL'" {
description
"The assignment-type must be set to LOGICAL_CHANNEL for
this leaf to be valid";
}
description
"Reference to another stage of logical channel elements.";
}
leaf optical-channel {
type leafref {
path "/oc-platform:components/oc-platform:component/" +
"oc-platform:name";
}
must "../assignment-type = 'OPTICAL_CHANNEL'" {
description
"The assignment-type must be set to OPTICAL_CHANNEL for
this leaf to be valid";
}
description
"Reference to the line-side optical channel that should
carry the current logical channel element. Use this
reference to exit the logical element stage.";
}
leaf allocation {
type decimal64 {
fraction-digits 3;
}
units Gbps;
description
"Allocation of the logical client channel to the tributary
or sub-channel, expressed in Gbps. Please note that if the
assignment is to an OTN logical channel, the allocation must
be an integer multiplication to tributary-slot-granularity
of the OTN logical channel.";
}
leaf tributary-slot-index {
type int32;
description
"Indicates the first tributary slot index allocated to the
client signal or logical channel in the assignment. Valid
only when the assignment is to an OTN logical channel.";
}
leaf mapping {
type identityref {
base oc-opt-types:FRAME_MAPPING_PROTOCOL;
}
description
"Logical channel mapping procedure. Valid only when the
assignment is to an OTN logical channel.";
}
}
grouping terminal-logical-chan-assignment-state {
description
"Operational state data for the assignment of logical client
channel to line-side tributary";
}
grouping terminal-logical-chan-assignment-top {
description
"Top-level grouping for the list of logical client channel-to-
tributary assignments";
container logical-channel-assignments {
//TODO: we need a commonly understood name for this logical
//channel structure
description
"Enclosing container for tributary assignments";
list assignment {
key "index";
description
"Logical channel elements may be assigned directly to
optical channels for line-side transmission, or can be
further groomed into additional stages of logical channel
elements. The grooming can multiplex (i.e., split the
current element into multiple elements in the subsequent
stage) or de-multiplex (i.e., combine the current element
with other elements into the same element in the subsequent
stage) logical elements in each stage.
Note that to support the ability to groom the logical
elements, the list of logical channel elements should be
populated with an entry for the logical elements at
each stage, starting with the initial assignment from the
respective client physical port.
Each logical element assignment consists of a pointer to
an element in the next stage, or to an optical channel,
along with a bandwidth allocation for the corresponding
assignment (e.g., to split or combine signal).";
leaf index {
type leafref {
path "../config/index";
}
description
"Reference to the index for the current tributary
assignment";
}
container config {
description
"Configuration data for tributary assignments";
uses terminal-logical-chan-assignment-config;
}
container state {
config false;
description
"Operational state data for tributary assignments";
uses terminal-logical-chan-assignment-config;
uses terminal-logical-chan-assignment-state;
}
}
}
}
grouping terminal-logical-channel-ingress-config {
description
"Configuration data for ingress signal to logical channel";
leaf transceiver {
type leafref {
path "/oc-platform:components/oc-platform:component/" +
"oc-platform:name";