idnits 2.17.1 draft-ietf-ccamp-dwdm-if-param-yang-03.txt: Checking boilerplate required by RFC 5378 and the IETF Trust (see https://trustee.ietf.org/license-info): ---------------------------------------------------------------------------- No issues found here. Checking nits according to https://www.ietf.org/id-info/1id-guidelines.txt: ---------------------------------------------------------------------------- No issues found here. Checking nits according to https://www.ietf.org/id-info/checklist : ---------------------------------------------------------------------------- ** The abstract seems to contain references ([ITU.G698.2]), which it shouldn't. Please replace those with straight textual mentions of the documents in question. Miscellaneous warnings: ---------------------------------------------------------------------------- == The copyright year in the IETF Trust and authors Copyright Line does not match the current year == Line 510 has weird spacing: '... leaf tca-t...' == Line 514 has weird spacing: '... leaf min-t...' == Line 520 has weird spacing: '... leaf max-t...' == Line 545 has weird spacing: '... leaf pre-f...' == Line 549 has weird spacing: '... leaf pre-f...' == (20 more instances...) == The document doesn't use any RFC 2119 keywords, yet seems to have RFC 2119 boilerplate text. -- The document date (March 9, 2020) is 1509 days in the past. Is this intentional? Checking references for intended status: Experimental ---------------------------------------------------------------------------- == Missing Reference: 'RFC6241' is mentioned on line 869, but not defined == Missing Reference: 'RFC6242' is mentioned on line 871, but not defined == Missing Reference: 'RFC6536' is mentioned on line 871, but not defined ** Obsolete undefined reference: RFC 6536 (Obsoleted by RFC 8341) == Missing Reference: 'RFC3688' is mentioned on line 879, but not defined == Missing Reference: 'RFC6020' is mentioned on line 893, but not defined == Unused Reference: 'ITU.G694.1' is defined on line 949, but no explicit reference was found in the text == Unused Reference: 'ITU.G709' is defined on line 960, but no explicit reference was found in the text == Unused Reference: 'ITU.G7710' is defined on line 965, but no explicit reference was found in the text == Unused Reference: 'ITU.G798' is defined on line 970, but no explicit reference was found in the text == Unused Reference: 'ITU.G8201' is defined on line 976, but no explicit reference was found in the text == Unused Reference: 'ITU.G826' is defined on line 982, but no explicit reference was found in the text == Unused Reference: 'ITU.G872' is defined on line 988, but no explicit reference was found in the text == Unused Reference: 'ITU.G874' is defined on line 993, but no explicit reference was found in the text == Unused Reference: 'ITU.G959.1' is defined on line 1004, but no explicit reference was found in the text == Unused Reference: 'RFC2578' is defined on line 1014, but no explicit reference was found in the text == Unused Reference: 'RFC2579' is defined on line 1020, but no explicit reference was found in the text == Unused Reference: 'RFC2580' is defined on line 1025, but no explicit reference was found in the text == Unused Reference: 'RFC2863' is defined on line 1030, but no explicit reference was found in the text == Unused Reference: 'RFC3591' is defined on line 1034, but no explicit reference was found in the text == Unused Reference: 'RFC6205' is defined on line 1039, but no explicit reference was found in the text == Unused Reference: 'RFC2629' is defined on line 1046, but no explicit reference was found in the text == Unused Reference: 'RFC4054' is defined on line 1056, but no explicit reference was found in the text == Unused Reference: 'RFC4181' is defined on line 1061, but no explicit reference was found in the text -- Obsolete informational reference (is this intentional?): RFC 2629 (Obsoleted by RFC 7749) Summary: 2 errors (**), 0 flaws (~~), 31 warnings (==), 2 comments (--). Run idnits with the --verbose option for more detailed information about the items above. -------------------------------------------------------------------------------- 2 Internet Engineering Task Force G. Galimberti, Ed. 3 Internet-Draft Cisco 4 Intended status: Experimental R. Kunze 5 Expires: September 10, 2020 A. Burk 6 Deutsche Telekom 7 D. Hiremagalur, Ed. 8 G. Grammel, Ed. 9 Juniper 10 March 9, 2020 12 A YANG model to manage the optical interface parameters for an external 13 transponder in a WDM network 14 draft-ietf-ccamp-dwdm-if-param-yang-03 16 Abstract 18 This memo defines a Yang model related to the Optical Transceiver 19 parameters characterising coherent 100G and above interfaces. 100G 20 and above Transceivers support coherent modulation, multiple 21 modulation formats, multiple FEC codes including some not yet 22 specified (or by in phase of specification by) ITU-T G.698.2 23 [ITU.G698.2] or any other ITU-T recommendation. More context about 24 the state of the Coherent transceivers is described in draft-many- 25 coherent-DWDM-if-control. Use cases are described in RFC7698. 27 The Yang model defined in this memo can be used for Optical 28 Parameters monitoring and/or configuration of the endpoints of a 29 multi-vendor IaDI optical link. The use of this model does not 30 guarantee interworking of transceivers over a DWDM. Optical path 31 feasibility and interoperability has to be determined by means 32 outside the scope of this document. The purpose of this model is to 33 program interface parameters to consistently configure the mode of 34 operation of transceivers. 36 Copyright Notice 38 Copyright (c) 2014 IETF Trust and the persons identified as the 39 document authors. All rights reserved. 41 Status of This Memo 43 This Internet-Draft is submitted in full conformance with the 44 provisions of BCP 78 and BCP 79. 46 Internet-Drafts are working documents of the Internet Engineering 47 Task Force (IETF). Note that other groups may also distribute 48 working documents as Internet-Drafts. The list of current Internet- 49 Drafts is at https://datatracker.ietf.org/drafts/current/. 51 Internet-Drafts are draft documents valid for a maximum of six months 52 and may be updated, replaced, or obsoleted by other documents at any 53 time. It is inappropriate to use Internet-Drafts as reference 54 material or to cite them other than as "work in progress." 56 This Internet-Draft will expire on September 10, 2020. 58 Copyright Notice 60 Copyright (c) 2020 IETF Trust and the persons identified as the 61 document authors. All rights reserved. 63 This document is subject to BCP 78 and the IETF Trust's Legal 64 Provisions Relating to IETF Documents 65 (https://trustee.ietf.org/license-info) in effect on the date of 66 publication of this document. Please review these documents 67 carefully, as they describe your rights and restrictions with respect 68 to this document. Code Components extracted from this document must 69 include Simplified BSD License text as described in Section 4.e of 70 the Trust Legal Provisions and are provided without warranty as 71 described in the Simplified BSD License. 73 Table of Contents 75 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 3 76 2. The Internet-Standard Management Framework . . . . . . . . . 3 77 3. Conventions . . . . . . . . . . . . . . . . . . . . . . . . . 4 78 4. Overview . . . . . . . . . . . . . . . . . . . . . . . . . . 4 79 4.1. Optical Parameters Description . . . . . . . . . . . . . 5 80 4.1.1. Parameters at Ss . . . . . . . . . . . . . . . . . . 5 81 4.1.2. Interface at point Rs . . . . . . . . . . . . . . . . 5 82 4.2. Use Cases . . . . . . . . . . . . . . . . . . . . . . . . 5 83 4.3. Optical Interface for external transponder in a WDM 84 network . . . . . . . . . . . . . . . . . . . . . . . . . 5 85 5. Structure of the Yang Module . . . . . . . . . . . . . . . . 7 86 6. Yang Module . . . . . . . . . . . . . . . . . . . . . . . . . 8 87 7. Security Considerations . . . . . . . . . . . . . . . . . . . 19 88 8. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 19 89 9. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 20 90 10. Contributors . . . . . . . . . . . . . . . . . . . . . . . . 20 91 11. References . . . . . . . . . . . . . . . . . . . . . . . . . 21 92 11.1. Normative References . . . . . . . . . . . . . . . . . . 21 93 11.2. Informative References . . . . . . . . . . . . . . . . . 23 94 Appendix A. Change Log . . . . . . . . . . . . . . . . . . . . . 23 95 Appendix B. Open Issues . . . . . . . . . . . . . . . . . . . . 23 96 Appendix C. Applicability examples . . . . . . . . . . . . . . . 23 97 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 24 99 1. Introduction 101 This memo defines a Yang model that translates and obsolete the SNMP 102 mib module defined in draft-galikunze-ccamp-dwdm-if-snmp-mib for 103 managing single channel optical interface parameters of DWDM 104 applications, using the approach specified in G.698.2. This model 105 supports parameters to characterize coherent transceivers found in 106 current implementations to specify the mode of operation. As 107 application identifiers like those specified in ITU-T G.874.1 108 [ITU.G874.1] are not available we use mode templates instead. A mode 109 template describes transceiver characteristics in detail and can be 110 identified by a mode-id. 112 This draft refers and supports the RFC7698 and draft-many-coherent- 113 DWDM-if-control. 115 The YANG model describing and extending the optical parameters allows 116 different vendors and operators to retrieve, provision and exchange 117 information across the multi-vendor IaDI interfaces in an abstract 118 manner. 120 The they concept introduced by this YANG model is the notion of a 121 mode. A mode is a combination of parameters or parameter ranges that 122 is supported by a transceiver. As an example, operating a device in 123 QPSK mode may use a different FEC and requires less OSNR to reach the 124 FEC limit than the same transceiver operating in QAM16 mode. Given 125 the number of parameters and their possible combinations it is 126 important for vendors to be able to qualify a set of combinations 127 which is the basis to define a mode. The YANG model furthermore 128 provides means to selecting one mode as current-mode from that pre- 129 defined list of modes supported by the transceiver module. Once 130 selected, current-opt-if-och-mode-params provide the means to 131 configure specific parameters at run time and retrieve actual 132 parameters from the module. For example, the frequency is a 133 parameter that can be set within min/max boundaries set by the 134 current mode. Laser Temperature however is a ro parameter available 135 at run-time that can be checked against the mode boundaries and may 136 trigger an event. 138 2. The Internet-Standard Management Framework 140 For a detailed overview of the documents that describe the current 141 Internet-Standard Management Framework, please refer to section 7 of 142 RFC 3410 [RFC3410]. 144 This memo specifies a Yang model for optical interfaces. 146 3. Conventions 148 The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", 149 "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this 150 document are to be interpreted as described in RFC 2119 [RFC2119] In 151 the description of OIDs the convention: Set (S) Get (G) and Trap (T) 152 conventions will describe the action allowed by the parameter. 154 4. Overview 156 Figure 1 shows a set of reference points, for single-channel 157 connection between transmitters (Tx) and receivers (Rx). Here the 158 DWDM network elements include an OM and an OD (which are used as a 159 pair with the opposing element), one or more optical amplifiers and 160 may also include one or more OADMs. 162 +-------------------------------------------------+ 163 Ss | DWDM Network Elements | Rs 164 +--+ | | | \ / | | | +--+ 165 Tx L1--|->| \ +------+ +------+ / |--|-->Rx L1 166 +---+ | | | | | +------+ | | | | | +--+ 167 +---+ | | | | | | | | | | | | +--+ 168 Tx L2--|->| OM |-->|------|->|ROADM |--|------|->| OD |--|-->Rx L2 169 +---+ | | | | | | | | | | | | +--+ 170 +---+ | | | | | +------+ | | | | | +--+ 171 Tx L3--|->| / | DWDM | | ^ | DWDM | \ |--|-->Rx L3 172 +---+ | | / | Link +----|--|----+ Link | \ | | +--+ 173 +-----------+ | | +----------+ 174 +--+ +--+ 175 | | 176 Rs v | Ss 177 +-----+ +-----+ 178 |RxLx | |TxLx | 179 +-----+ +-----+ 180 Ss = reference point at the DWDM network element tributary output 181 Rs = reference point at the DWDM network element tributary input 182 Lx = Lambda x 183 OM = Optical Mux 184 OD = Optical Demux 185 ROADM = Reconfigurable Optical Add Drop Mux 187 from Fig. 5.1/G.698.2 189 Figure 1: External transponder in WDM netwoks 191 4.1. Optical Parameters Description 193 The link between the external transponders through a WDM network 194 media channels are managed at the edges, i.e. at the transmitters 195 (Tx) and receivers (Rx) attached to the S and R reference points 196 respectively. 198 Definitions of the optical parameters are provided below to increase 199 the readability of the document. 201 4.1.1. Parameters at Ss 203 output-power: 204 The mean launched power at Ss is the average power (in dBm) of a 205 pseudo-random data sequence coupled into the DWDM link. 207 central frequency: 208 This parameter indicates the Central frequency value that Ss and 209 Rs will be set to work (in THz) 211 4.1.2. Interface at point Rs 213 input-power: 214 The average received power (in dBm) at point Rs. 216 Curr-OSNR: 217 Current Optical Signal to Noise Ratio (OSNR) estimated at Rx 218 Transceiver port. 220 Curr-q-factor: 221 "Q" factor estimated at Rx Transceiver port. 223 4.2. Use Cases 225 The use cases are described in draft-ietf-ccamp-dwdm-if-mng-ctrl-fwk 227 4.3. Optical Interface for external transponder in a WDM network 229 The ietf-ext-xponder-wdm-if is an augment to the ietf-interface. It 230 allows the user to set the operating mode of transceivers as well as 231 other operational parameters. The module provides also treshold 232 settings and notifications to supervise measured parameters and 233 notify the client. 235 module: ietf-ext-xponder-wdm-if 236 augment /if:interfaces/if:interface: 237 +--rw optIfOChRsSs 238 +--rw if-current-mode 239 | +--ro mode-id? string 240 | +--ro application-identifier? string 241 | +--ro min-central-frequency? frequency-thz 242 | +--ro max-central-frequency? frequency-thz 243 | +--ro min-input-power? dbm-t 244 | +--ro max-input-power? dbm-t 245 | +--ro min-output-power? dbm-t 246 | +--ro max-output-power? dbm-t 247 | +--ro min-osnr-margin? int32 248 | +--ro min-q-margin? int32 249 | +--ro fec-info? string 250 | +--ro fec-bitrate? string 251 | +--ro fec-gain? string 252 | +--ro fec-ber-mantissa-threshold? uint32 253 | +--ro fec-ber-exponent-threshold? int32 254 | +--ro number-of-lanes? uint32 255 | +--ro min-laser-temperature? int32 256 | +--ro max-laser-temperature? int32 257 | +--ro max-total-rx-optical-power? dbm-t 258 | +--ro max-chromatic-dispersion? int32 259 | +--ro max-diff-group-delay? int32 260 | +--ro modulation-format? string 261 | +--ro baud-rate? string 262 | +--ro bits-per-symbol? uint32 263 | +--ro num-symbols-in-alphabet? uint32 264 | +--ro symbols-index? uint32 265 +--ro if-supported-mode 266 | +--ro number-of-modes-supported? uint32 267 | +--ro mode-list* [mode-id] 268 | +--ro mode-id? string 269 | +--ro application-identifer? string 270 | +--ro min-central-frequency? frequency-thz 271 | +--ro max-central-frequency? frequency-thz 272 | +--ro min-channel-input-power? dbm-t 273 | +--ro max-channel-input-power? dbm-t 274 | +--ro min-channel-output-power? dbm-t 275 | +--ro max-channel-output-power? dbm-t 276 | +--ro min-osnr-margin? int32 277 | +--ro min-q-margin? int32 278 | +--ro fec-info? string 279 | +--ro fec-bitrate? string 280 | +--ro fec-gain? string 281 | +--ro pre-fec-ber-mantissa-threshold? uint32 282 | +--ro pre-fec-ber-exponent-threshold? int32 283 | +--ro number-of-lanes? uint32 284 | +--ro min-laser-temperature? int32 285 | +--ro max-laser-temperature? int32 286 | +--ro max-total-rx-optical-power? dbm-t 287 | +--ro max-chromatic-dispersion? int32 288 | +--ro max-diff-group-delay? int32 289 | +--ro modulation-format? string 290 | +--ro baud-rate? string 291 | +--ro bits-per-symbol? uint32 292 | +--ro num-symbols-in-alphabet? uint32 293 | +--ro symbols-index? uint32 294 +--rw current-opt-if-och-mode-params 295 +--rw mode-id? string 296 +--rw central-frequency? frequency-thz 297 +--rw channel-output-power? dbm-t 298 +--ro channel-input-power? dbm-t 299 +--ro total-input-power? dbm-t 300 +--rw min-fec-ber-mantissa-threshold? uint32 301 +--rw min-fec-ber-exponent-threshold? int32 302 +--rw max-fec-ber-mantissa-threshold? uint32 303 +--rw max-fec-ber-exponent-threshold? int32 304 +--rw number-of-tcas-supported? uint32 305 +--rw mode-list* [tca-type] 306 | +--rw tca-type opt-if-och-tca-types 307 | +--rw min-threshold? int32 308 | +--rw max-threshold? int32 309 +--ro cur-osnr? int32 310 +--ro cur-q-factor? int32 311 +--ro uncorrected-words? uint64 312 +--ro pre-fec-ber-mantissa? uint32 313 +--ro pre-fec-ber-exponent? int32 314 notifications: 315 +---n opt-if-och-central-frequency-change 316 | +--ro if-name? -> /if:interfaces/interface/name 317 | +--ro new-opt-if-och-central-frequency 318 | +--ro central-frequency? uint32 319 +---n opt-if-och-mode-change 320 | +--ro if-name? -> /if:interfaces/interface/name 321 | +--ro mode-id? string 322 +---n opt-if-och-min-tca 323 +--ro if-name? -> /if:interfaces/interface/name 324 +--ro tca-type? opt-if-och-tca-types 326 5. Structure of the Yang Module 328 ietf-ext-xponder-wdm-if is a top level model for the support of this 329 feature. 331 6. Yang Module 333 The ietf-ext-xponder-wdm-if is defined as an extension to ietf 334 interfaces. 336 file "ietf-ext-xponder-wdm-if.yang" 338 module draft-ietf-ccamp-dwdm-if-param-yang-03 { 339 namespace "urn:ietf:params:xml:ns:yang:ietf-ext-xponder-wdm-if"; 340 prefix ietf-ext-xponder-wdm-if; 342 import ietf-interfaces { 343 prefix if; 344 } 346 import ietf-layer0-types { 347 prefix "layer0-types"; 348 } 350 organization 351 "IETF CCAMP 352 Working Group"; 354 contact 355 "WG Web: 356 WG List: 358 Editor: Dharini Hiremagalur 359 "; 361 description 362 "This module contains a collection of YANG definitions for 363 configuring Optical interfaces. 365 Copyright (c) 2016 IETF Trust and the persons identified 366 as authors of the code. All rights reserved. 368 Redistribution and use in source and binary forms, with or 369 without modification, is permitted pursuant to, and 370 subject to the license terms contained in, the Simplified 371 BSD License set forth in Section 4.c of the IETF Trust's 372 Legal Provisions Relating to IETF Documents 373 (http://trustee.ietf.org/license-info)."; 375 revision "2020-03-09" { 376 description 377 "Revision 1.5"; 378 reference 379 ""; 380 } 382 revision "2019-11-04" { 383 description 384 "Revision 1.4"; 385 reference 386 ""; 387 } 389 revision "2019-07-08" { 390 description 391 "Revision 1.3"; 392 reference 393 ""; 394 } 395 revision "2018-10-22" { 396 description 397 "Revision 1.2"; 398 reference 399 ""; 400 } 401 revision "2018-03-06" { 402 description 403 "Revision 1.1"; 404 reference 405 ""; 406 } 407 revision "2017-03-06" { 408 description 409 "Revision 1.0"; 410 reference 411 ""; 412 } 413 revision "2016-03-17" { 414 description 415 "Initial revision."; 416 reference 417 ""; 418 } 420 typedef dbm-t { 421 type int32; 422 units ".01dbm"; 423 } 424 description " 425 Amplifiers and Transceivers Power in dBm"; 426 } 427 typedef opt-if-och-tca-types { 428 type enumeration { 429 enum max-laser-linewdt { 430 description "The maximum laser linewidth"; 431 } 432 enum min-tx-power-tca { 433 description "The min tx power TCA"; 434 } 435 enum max-tx-power-tca { 436 description "The min tx power TCA"; 437 } 438 enum min-rx-power-tca{ 439 description "The min tx power TCA"; 440 } 441 enum max-rx-power-tca{ 442 description "The min tx power TCA"; 443 } 444 enum max-pol-power-diff-tca{ 445 description "The power difference between polarization 446 TCA"; 447 } 448 enum max-pol-skew-diff-tca{ 449 description "The skew between the two polarization TCA"; 450 } 451 enum min-frequency-offset-tca{ 452 description "Min Frequency offset TCA"; 453 } 454 enum max-frequency-offset-tca{ 455 description "Max Frequency offset TCA"; 456 } 457 enum min-osnr-tca{ 458 description "Min OSNR TCA"; 459 } 460 enum max-osnr-tca{ 461 description "Max OSNR TCA"; 462 } 463 enum min-laser-temperature-tca{ 464 description "The min tx power TCA"; 465 } 466 enum max-laser-temperature-tca{ 467 description "Temperature TCA"; 468 } 469 enum min-fec-ber-tca{ 470 description "Min Pre Fec BER TCA"; 471 } 472 enum max-fec-ber-tca{ 473 description "Max Pre Fec BER TCA"; 474 } 475 enum min-q-tca{ 476 description "Min Q TCA"; 477 } 478 enum max-q-tca { 479 description "Max Q TCA"; 480 } 481 } 482 description "The different types of TCA's"; 483 } 485 grouping opt-if-och-power { 486 description "Interface optical Power"; 488 leaf channel-output-power { 489 type dbm-t; 490 description "The output power for this interface in .01 dBm. 491 The setting of the output power is optional"; 492 } 494 leaf channel-input-power { 495 type dbm-t; 496 config false; 497 description "The current channel input power of this 498 interface"; 499 } 501 leaf total-input-power { 502 type dbm-t; 503 config false; 504 description "The total input power of this interface"; 505 } 506 } 508 grouping opt-if-och-tca-thresholds { 509 description "Thresholds for TCA's"; 510 leaf tca-type { 511 type opt-if-och-tca-types; 512 description "type of the TCA eg TX Power"; 513 } 514 leaf min-threshold { 515 type int32; 516 description "A TCA is generated if the variable is less than 517 this value"; 519 } 520 leaf max-threshold { 521 type int32; 522 description "A TCA is generated if the variable is more than 523 this value"; 524 } 525 } 527 grouping opt-if-och-fec { 528 description "FEC info"; 530 leaf fec-info { 531 type string { length "1..255"; } 532 config false; 533 description "FEC Type - eg GFEC"; 534 } 535 leaf fec-bitrate { 536 type string { length "1..255"; } 537 config false; 538 description "FEC Overhead rate "; 539 } 540 leaf fec-gain { 541 type string { length "1..255"; } 542 config false; 543 description "FEC Overhead rate "; 544 } 545 leaf pre-fec-ber-mantissa-threshold { 546 type uint32; 547 description "Mantissa of the FEC BER threshold"; 548 } 549 leaf pre-fec-ber-exponent-threshold { 550 type int32; 551 description "Exponent of the FEC BER threshold"; 552 } 553 } 555 grouping opt-if-och-central-frequency { 556 description "Interface Central Frequency"; 557 leaf central-frequency { 558 type layer0-types:frequency-thz; 559 description "This parameter indicates the frequency of this 560 interface "; 561 } 562 } 564 grouping opt-if-och-modulation-params { 565 description "Optical modulation parameters for the lane"; 566 leaf modulation-format { 567 type string { length "1..255"; } 568 config false; 569 description "Modulation format for this mode"; 570 } 571 leaf baud-rate { 572 type uint32; 573 description "Baud-rate or symbol rate"; 574 } 575 leaf bits-per-symbol { 576 type uint32; 577 description "This parameter the bits per symbol for this 578 mode"; 579 } 580 leaf num-symbols-in-alphabet { 581 type uint32; 582 description "This parameter the bits per symbol for this 583 mode"; 584 } 585 leaf symbols-index { 586 type uint32; 587 description "This parameter is the symbol index this mode"; 588 } 589 } 591 grouping opt-if-och-lane-param { 592 description "Optical parameters for the lane"; 594 leaf number-of-lanes { 595 type uint32; 596 config false; 597 description "Number of optical lanes of this interface"; 598 } 599 leaf min-laser-temperature { 600 type int32; 601 units ".01C"; 602 config false; 603 description "Minimum Laser Temperature of this mode for 604 this lane"; 605 } 606 leaf max-laser-temperature { 607 type int32; 608 units ".01C"; 609 config false; 610 description "Maximum Laser Temperature of this mode for 611 this lane"; 612 } 613 leaf max-total-rx-optical-power { 614 type dbm-t; 615 config false; 616 description "Maximum rx optical power of this mode for this 617 lane"; 618 } 619 leaf max-chromatic-dispersion { 620 type int32; 621 config false; 622 description "Maximum chromatic dispersion of this mode for 623 this lane"; 624 } 625 leaf max-diff-group-delay { 626 type int32; 627 config false; 628 description "Maximum Differential group delay of this mode 629 for this lane"; 630 } 631 uses opt-if-och-modulation-params; 632 } 634 grouping opt-if-och-tca-list { 635 description "List of TCA's"; 636 leaf number-of-tcas-supported { 637 type uint32; 638 description "Number of TCAs supported by this interface"; 639 } 640 list mode-list { 641 key "tca-type"; 642 description "List of the TCAs"; 643 uses opt-if-och-tca-thresholds; 644 } 645 } 647 grouping opt-if-och-fec-tca-thresholds { 648 description "Pre FEC BER Thresholds for TCA's"; 649 leaf min-fec-ber-mantissa-threshold { 650 type uint32; 651 description "Min Mantissa of the FEC BER threshold"; 652 } 653 leaf min-fec-ber-exponent-threshold { 654 type int32; 655 description "Min Exponent of the FEC BER threshold"; 656 } 657 leaf max-fec-ber-mantissa-threshold { 658 type uint32; 659 description "Max Mantissa of the FEC BER threshold"; 660 } 661 leaf max-fec-ber-exponent-threshold { 662 type int32; 663 description "Max Exponent of the FEC BER threshold"; 664 } 665 } 667 grouping opt-if-och-mode-params { 668 description "OCh mode parameters"; 669 leaf mode-id { 670 type string { length "1..255"; } 671 description "ID for the OCh mode template"; 672 } 673 leaf min-osnr-margin { 674 type int32; 675 units "dB"; 676 config false; 677 description "OSNR margin to FEC threshold"; 678 } 679 leaf q-margin { 680 type int32; 681 units "dB"; 682 config false; 683 description "Q-Factor margin to FEC threshold"; 684 } 685 uses opt-if-och-central-frequency; 686 uses opt-if-och-power; 687 uses opt-if-och-fec-tca-thresholds; 688 uses opt-if-och-tca-list; 689 } 691 grouping opt-if-och-statistics { 692 description "OCh statistics"; 693 leaf cur-osnr { 694 type int32; 695 units "dB"; 696 config false; 697 description "OSNR margin to FEC threshold"; 698 } 699 leaf cur-q-factor { 700 type int32; 701 units "dB"; 702 config false; 703 description "Q-Factor of the interface"; 704 } 705 leaf uncorrected-words { 706 type uint64; 707 config false; 708 description "Post-FEC errored words"; 709 } 710 leaf pre-fec-ber-mantissa { 711 type uint32; 712 config false; 713 description "Pre-FEC errored words mantissa"; 714 } 715 leaf pre-fec-ber-exponent { 716 type int32; 717 config false; 718 description "Pre-FEC errored words exponent"; 719 } 720 } 722 grouping opt-if-och-mode { 723 description "OCh mode template"; 725 leaf mode-id { 726 type string { length "1..255"; } 727 config false; 728 description "ID for the OCh mode template"; 729 } 730 leaf application-identifier { 731 type uint32; 732 config false; 733 description "This parameter indicates the application 734 identifier according to G.698.2"; 735 } 737 leaf min-central-frequency { 738 type layer0-types:frequency-thz; 739 config false; 740 description 741 "his parameter indicates the minimum frequency for 742 this template"; 743 } 744 leaf max-central-frequency { 745 type layer0-types:frequency-thz; 746 config false; 747 description "This parameter indicates the minimum frequency 748 for this template"; 749 } 750 leaf min-channel-input-power { 751 type dbm-t; 752 config false; 753 description "The minimum input power of this interface"; 754 } 755 leaf max-channel-input-power { 756 type dbm-t; 757 config false; 758 description "The maximum input power of this interface"; 759 } 760 leaf min-channel-output-power { 761 type dbm-t; 762 config false; 763 description "The minimum output power of this interface"; 764 } 765 leaf max-channel-output-power { 766 type dbm-t; 767 config false; 768 description "The maximum output power of this interface"; 769 } 770 leaf osnr-margin { 771 type int32; 772 units "dB"; 773 config false; 774 description "OSNR margin to FEC threshold"; 775 } 776 leaf q-margin { 777 type int32; 778 units "dB"; 779 config false; 780 description "Q-Factor margin to FEC threshold"; 781 } 782 uses opt-if-och-fec; 783 uses opt-if-och-lane-param; 784 } 786 grouping opt-if-och-mode-list { 787 description "List of Mode list group"; 789 leaf number-of-modes-supported { 790 type uint32; 791 description "Number of modes supported by this interface"; 792 } 793 list mode-list { 794 key "mode-id"; 795 description "List of the modes"; 796 uses opt-if-och-mode; 797 } 798 } 800 notification opt-if-och-central-frequency-change { 801 description "A change of Central Frequency has been detected"; 803 leaf "if-name" { 804 type leafref { path "/if:interfaces/if:interface/if:name"; } 805 description "Interface name"; 806 } 807 container new-opt-if-och-central-frequency { 808 description "The new Central Frequency of the interface"; 809 uses opt-if-och-central-frequency; 810 } 811 } 813 notification opt-if-och-mode-change { 814 description "A change of Mode Template has been detected"; 816 leaf "if-name" { 817 type leafref { path "/if:interfaces/if:interface/if:name"; } 818 description "Interface name"; 819 } 820 leaf mode-id { 821 type string { length "1..255"; } 822 description "ID for the OCh mode template"; 823 } 824 } 826 notification opt-if-och-min-tca { 827 description "A min output TCA notification"; 829 leaf "if-name" { 830 type leafref { path "/if:interfaces/if:interface/if:name"; } 831 description "Interface name"; 832 } 833 leaf tca-type { 834 type opt-if-och-tca-types; 835 description "Type of TCA for eg min tx power TCA"; 836 } 837 } 839 augment "/if:interfaces/if:interface" { 840 description "Parameters for an optical interface"; 842 container optIfOChRsSs { 843 description "RsSs path configuration for an interface"; 845 container if-current-mode { 846 description "Current mode template of the interface"; 847 uses opt-if-och-mode; 848 } 849 container if-supported-mode { 850 config false; 851 description "Supported mode list of this interface"; 852 uses opt-if-och-mode-list; 854 } 855 container current-opt-if-och-mode-params { 856 description "Current parameters of this interface"; 857 uses opt-if-och-mode-params; 858 uses opt-if-och-statistics; 859 } 860 } 861 } 862 } 864 866 7. Security Considerations 868 The YANG module defined in this memo is designed to be accessed via 869 the NETCONF protocol [RFC6241]. he lowest NETCONF layer is the secure 870 transport layer and the mandatory-to-implement secure transport is 871 SSH [RFC6242]. The NETCONF access control model [RFC6536] provides 872 the means to restrict access for particular NETCONF users to a pre- 873 configured subset of all available NETCONF protocol operation and 874 content. 876 8. IANA Considerations 878 This document registers a URI in the IETF XML registry [RFC3688]. 879 Following the format in [RFC3688], the following registration is 880 requested to be made: 882 URI: urn:ietf:params:xml:ns:yang:ietf-interfaces:ietf-ext-xponder- 883 wdm-if 885 Registrant Contact: The IESG. 887 XML: N/A, the requested URI is an XML namespace. 889 This document registers a YANG module in the YANG Module Names 890 registry [RFC6020]. 892 This document registers a YANG module in the YANG Module Names 893 registry [RFC6020]. 895 prefix: ietf-ext-xponder-wdm-if reference: RFC XXXX 897 9. Acknowledgements 899 10. Contributors 901 Dean Bogdanovic 902 Westford 903 U.S.A. 904 email ivandean@gmail.com 906 Bernd Zeuner 907 Deutsche Telekom 908 Darmstadt 909 Germany 910 email B.Zeuner@telekom.de 912 Massimiliano Salsi 913 Juniper Networks 914 1133 Innovation Way 915 Sunnyvale, CA, 94089 916 U.S.A. 917 +1 408936847 918 email msalsi@google.com 920 Arnold Mattheus 921 Deutsche Telekom 922 Darmstadt 923 Germany 924 email a.mattheus@telekom.de 926 Manuel Paul 927 Deutsche Telekom 928 Berlin 929 Germany 930 email Manuel.Paul@telekom.de 932 Walid Wakim 933 Cisco 934 9501 Technology Blvd 935 ROSEMONT, ILLINOIS 60018 936 UNITED STATES 937 email wwakim@cisco.com 939 Kam Lam 940 Nokia 941 USA 942 +1 732 331 3476 943 kam.lam@nokia.com 945 11. References 947 11.1. Normative References 949 [ITU.G694.1] 950 International Telecommunications Union, "Spectral grids 951 for WDM applications: DWDM frequency grid", 952 ITU-T Recommendation G.694.1, February 2012. 954 [ITU.G698.2] 955 International Telecommunications Union, "Amplified 956 multichannel dense wavelength division multiplexing 957 applications with single channel optical interfaces", 958 ITU-T Recommendation G.698.2, November 2009. 960 [ITU.G709] 961 International Telecommunications Union, "Interface for the 962 Optical Transport Network (OTN)", ITU-T Recommendation 963 G.709, June 2016. 965 [ITU.G7710] 966 International Telecommunications Union, "Common equipment 967 management function requirements", ITU-T Recommendation 968 G.7710, August 2017. 970 [ITU.G798] 971 International Telecommunications Union, "Characteristics 972 of optical transport network hierarchy equipment 973 functional blocks", ITU-T Recommendation G.798, Devember 974 2017. 976 [ITU.G8201] 977 International Telecommunications Union, "Error performance 978 parameters and objectives for multi-operator international 979 paths within the Optical Transport Network (OTN)", 980 ITU-T Recommendation G.8201, April 2011. 982 [ITU.G826] 983 International Telecommunications Union, "End-to-end error 984 performance parameters and objectives for international, 985 constant bit-rate digital paths and connections", 986 ITU-T Recommendation G.826, December 2002. 988 [ITU.G872] 989 International Telecommunications Union, "Architecture of 990 optical transport networks", ITU-T Recommendation G.872, 991 January 2017. 993 [ITU.G874] 994 International Telecommunications Union, "Management 995 aspects of optical transport network elements", 996 ITU-T Recommendation G.874, July 2010. 998 [ITU.G874.1] 999 International Telecommunications Union, "Optical transport 1000 network (OTN): Protocol-neutral management information 1001 model for the network element view", ITU-T Recommendation 1002 G.874.1, November 2016. 1004 [ITU.G959.1] 1005 International Telecommunications Union, "Optical transport 1006 network physical layer interfaces", ITU-T Recommendation 1007 G.959.1, November 2009. 1009 [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate 1010 Requirement Levels", BCP 14, RFC 2119, 1011 DOI 10.17487/RFC2119, March 1997, 1012 . 1014 [RFC2578] McCloghrie, K., Ed., Perkins, D., Ed., and J. 1015 Schoenwaelder, Ed., "Structure of Management Information 1016 Version 2 (SMIv2)", STD 58, RFC 2578, 1017 DOI 10.17487/RFC2578, April 1999, 1018 . 1020 [RFC2579] McCloghrie, K., Ed., Perkins, D., Ed., and J. 1021 Schoenwaelder, Ed., "Textual Conventions for SMIv2", 1022 STD 58, RFC 2579, DOI 10.17487/RFC2579, April 1999, 1023 . 1025 [RFC2580] McCloghrie, K., Ed., Perkins, D., Ed., and J. 1026 Schoenwaelder, Ed., "Conformance Statements for SMIv2", 1027 STD 58, RFC 2580, DOI 10.17487/RFC2580, April 1999, 1028 . 1030 [RFC2863] McCloghrie, K. and F. Kastenholz, "The Interfaces Group 1031 MIB", RFC 2863, DOI 10.17487/RFC2863, June 2000, 1032 . 1034 [RFC3591] Lam, H-K., Stewart, M., and A. Huynh, "Definitions of 1035 Managed Objects for the Optical Interface Type", RFC 3591, 1036 DOI 10.17487/RFC3591, September 2003, 1037 . 1039 [RFC6205] Otani, T., Ed. and D. Li, Ed., "Generalized Labels for 1040 Lambda-Switch-Capable (LSC) Label Switching Routers", 1041 RFC 6205, DOI 10.17487/RFC6205, March 2011, 1042 . 1044 11.2. Informative References 1046 [RFC2629] Rose, M., "Writing I-Ds and RFCs using XML", RFC 2629, 1047 DOI 10.17487/RFC2629, June 1999, 1048 . 1050 [RFC3410] Case, J., Mundy, R., Partain, D., and B. Stewart, 1051 "Introduction and Applicability Statements for Internet- 1052 Standard Management Framework", RFC 3410, 1053 DOI 10.17487/RFC3410, December 2002, 1054 . 1056 [RFC4054] Strand, J., Ed. and A. Chiu, Ed., "Impairments and Other 1057 Constraints on Optical Layer Routing", RFC 4054, 1058 DOI 10.17487/RFC4054, May 2005, 1059 . 1061 [RFC4181] Heard, C., Ed., "Guidelines for Authors and Reviewers of 1062 MIB Documents", BCP 111, RFC 4181, DOI 10.17487/RFC4181, 1063 September 2005, . 1065 Appendix A. Change Log 1067 This optional section should be removed before the internet draft is 1068 submitted to the IESG for publication as an RFC. 1070 Note to RFC Editor: please remove this appendix before publication as 1071 an RFC. 1073 Appendix B. Open Issues 1075 Note to RFC Editor: please remove this appendix before publication as 1076 an RFC. 1078 Appendix C. Applicability examples 1080 As an examample here below is the way and OpenROADM compliant 1081 equipment could be managed using the Yang models described in thei 1082 draft. 1084 In OpenROADM MSA there is a limited number of DWDM interfaces 1085 supported. Basically only the 100G Staircase FEC and 400G oFEC are 1086 supported and these two kind of interfaces can be easily summarized 1087 with the "mode-id" and the "application-identifier" strings. 1089 the models below are enough to identify the interface and few working 1090 parameters: 1092 module: ietf-ext-xponder-wdm-if 1093 augment /if:interfaces/if:interface: 1094 +--rw optIfOChRsSs 1095 +--rw if-current-mode 1096 | +--ro mode-id? string 1097 | +--ro application-identifier? string 1098 . 1099 . 1100 . 1101 +--rw current-opt-if-och-mode-params 1102 +--rw mode-id? string 1103 +--rw central-frequency? frequency-thz 1104 +--rw channel-output-power? dbm-t 1105 +--ro channel-input-power? dbm-t 1106 . 1107 . 1108 . 1109 +--ro cur-osnr? int32 1110 +--ro cur-q-factor? int32 1111 +--ro uncorrected-words? uint64 1112 +--ro pre-fec-ber-mantissa? uint32 1113 +--ro pre-fec-ber-exponent? int32 1115 Authors' Addresses 1117 Gabriele Galimberti (editor) 1118 Cisco 1119 Via Santa Maria Molgora, 48 c 1120 20871 - Vimercate 1121 Italy 1123 Phone: +390392091462 1124 Email: ggalimbe@cisco.com 1125 Ruediger Kunze 1126 Deutsche Telekom 1127 Winterfeldtstr. 21-27 1128 10781 Berlin 1129 Germany 1131 Phone: +491702275321 1132 Email: RKunze@telekom.de 1134 Andreas Burk 1135 Deutsche Telekom 1136 Germany 1138 Phone: +49 1139 Email: andreas.burk@telekom.de 1141 Dharini Hiremagalur (editor) 1142 Juniper 1143 1133 Innovation Way 1144 Sunnyvale - 94089 California 1145 USA 1147 Email: dharinih@juniper.net 1149 Gert Grammel (editor) 1150 Juniper 1151 Oskar-Schlemmer Str. 15 1152 80807 Muenchen 1153 Germany 1155 Phone: +49 1725186386 1156 Email: ggrammel@juniper.net