idnits 2.17.1 draft-galimbe-ccamp-iv-yang-02.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 : ---------------------------------------------------------------------------- No issues found here. Miscellaneous warnings: ---------------------------------------------------------------------------- == The copyright year in the IETF Trust and authors Copyright Line does not match the current year == The document doesn't use any RFC 2119 keywords, yet seems to have RFC 2119 boilerplate text. -- The document date (March 13, 2017) is 2598 days in the past. Is this intentional? Checking references for intended status: Informational ---------------------------------------------------------------------------- == Missing Reference: 'RFC6566' is mentioned on line 158, but not defined == Missing Reference: 'ITU.G680' is mentioned on line 157, but not defined == Missing Reference: 'RFC6241' is mentioned on line 743, but not defined == Missing Reference: 'RFC6242' is mentioned on line 745, but not defined == Missing Reference: 'RFC6536' is mentioned on line 745, but not defined ** Obsolete undefined reference: RFC 6536 (Obsoleted by RFC 8341) == Missing Reference: 'RFC3688' is mentioned on line 753, but not defined == Missing Reference: 'RFC6020' is mentioned on line 767, but not defined == Unused Reference: 'RFC2863' is defined on line 810, but no explicit reference was found in the text == Unused Reference: 'RFC2578' is defined on line 819, but no explicit reference was found in the text == Unused Reference: 'RFC2579' is defined on line 825, but no explicit reference was found in the text == Unused Reference: 'RFC2580' is defined on line 830, but no explicit reference was found in the text == Unused Reference: 'RFC3591' is defined on line 835, but no explicit reference was found in the text == Unused Reference: 'RFC6205' is defined on line 840, but no explicit reference was found in the text == Unused Reference: 'ITU.G709' is defined on line 851, but no explicit reference was found in the text == Unused Reference: 'ITU.G872' is defined on line 856, but no explicit reference was found in the text == Unused Reference: 'ITU.G798' is defined on line 861, but no explicit reference was found in the text == Unused Reference: 'ITU.G874' is defined on line 867, but no explicit reference was found in the text == Unused Reference: 'ITU.G874.1' is defined on line 872, but no explicit reference was found in the text == Unused Reference: 'ITU.G959.1' is defined on line 878, but no explicit reference was found in the text == Unused Reference: 'ITU.G826' is defined on line 883, but no explicit reference was found in the text == Unused Reference: 'ITU.G8201' is defined on line 889, but no explicit reference was found in the text == Unused Reference: 'ITU.G694.1' is defined on line 895, but no explicit reference was found in the text == Unused Reference: 'ITU.G7710' is defined on line 900, but no explicit reference was found in the text == Unused Reference: 'RFC2629' is defined on line 913, but no explicit reference was found in the text == Unused Reference: 'RFC4181' is defined on line 917, but no explicit reference was found in the text == Unused Reference: 'I-D.ietf-ccamp-dwdm-if-mng-ctrl-fwk' is defined on line 921, but no explicit reference was found in the text == Unused Reference: 'RFC4054' is defined on line 927, but no explicit reference was found in the text -- Obsolete informational reference (is this intentional?): RFC 2629 (Obsoleted by RFC 7749) == Outdated reference: A later version (-13) exists of draft-ietf-ccamp-dwdm-if-mng-ctrl-fwk-00 Summary: 1 error (**), 0 flaws (~~), 30 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: Informational R.Kunze 5 Expires: September 14, 2017 Deutsche Telekom 6 D. Hiremagalur, Ed. 7 G. G.Grammel, Ed. 8 Juniper 9 March 13, 2017 11 A YANG model to manage the optical optical parameters for in a WDM 12 network 13 draft-galimbe-ccamp-iv-yang-02 15 Abstract 17 This memo defines a Yang model that translate the information model 18 to support Impairment-Aware (IA) Routing and Wavelength Assignment 19 (RWA) functionality. The information model is defined in draft-ietf- 20 ccamp-wson-iv-info and draft-martinelli-ccamp-wson-iv-encode. This 21 document defines proper encoding and extend to the models defined in 22 draft-lee-ccamp-wson-yang tu support Impairment-Aware (IA) Routing 23 and Wavelength Assignment (RWA) functions 25 The Yang model defined in this memo can be used for Optical 26 Parameters monitoring and/or configuration of the multivendor 27 Endpoints and ROADMs 29 Copyright Notice 31 Copyright (c) 2014 IETF Trust and the persons identified as the 32 document authors. All rights reserved. 34 Status of This Memo 36 This Internet-Draft is submitted in full conformance with the 37 provisions of BCP 78 and BCP 79. 39 Internet-Drafts are working documents of the Internet Engineering 40 Task Force (IETF). Note that other groups may also distribute 41 working documents as Internet-Drafts. The list of current Internet- 42 Drafts is at http://datatracker.ietf.org/drafts/current/. 44 Internet-Drafts are draft documents valid for a maximum of six months 45 and may be updated, replaced, or obsoleted by other documents at any 46 time. It is inappropriate to use Internet-Drafts as reference 47 material or to cite them other than as "work in progress." 48 This Internet-Draft will expire on September 14, 2017. 50 Copyright Notice 52 Copyright (c) 2017 IETF Trust and the persons identified as the 53 document authors. All rights reserved. 55 This document is subject to BCP 78 and the IETF Trust's Legal 56 Provisions Relating to IETF Documents 57 (http://trustee.ietf.org/license-info) in effect on the date of 58 publication of this document. Please review these documents 59 carefully, as they describe your rights and restrictions with respect 60 to this document. Code Components extracted from this document must 61 include Simplified BSD License text as described in Section 4.e of 62 the Trust Legal Provisions and are provided without warranty as 63 described in the Simplified BSD License. 65 Table of Contents 67 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 3 68 2. The Internet-Standard Management Framework . . . . . . . . . 3 69 3. Conventions . . . . . . . . . . . . . . . . . . . . . . . . . 4 70 4. Definition . . . . . . . . . . . . . . . . . . . . . . . . . 4 71 5. Applicability . . . . . . . . . . . . . . . . . . . . . . . . 4 72 6. Properties . . . . . . . . . . . . . . . . . . . . . . . . . 4 73 7. Overview . . . . . . . . . . . . . . . . . . . . . . . . . . 4 74 7.1. Optical Parameters Description . . . . . . . . . . . . . 5 75 7.1.1. Optical path from point Ss to Rs . . . . . . . . . . 6 76 7.1.2. Rs and Ss Configuration . . . . . . . . . . . . . . . 7 77 7.1.3. Table of Application Codes . . . . . . . . . . . . . 7 78 7.2. Use Cases . . . . . . . . . . . . . . . . . . . . . . . . 7 79 7.3. Optical Parameters for impairment validation in a WDM 80 network . . . . . . . . . . . . . . . . . . . . . . . . . 7 81 8. Structure of the Yang Module . . . . . . . . . . . . . . . . 8 82 9. Yang Module . . . . . . . . . . . . . . . . . . . . . . . . . 8 83 10. Security Considerations . . . . . . . . . . . . . . . . . . . 17 84 11. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 17 85 12. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 18 86 13. Contributors . . . . . . . . . . . . . . . . . . . . . . . . 18 87 14. References . . . . . . . . . . . . . . . . . . . . . . . . . 18 88 14.1. Normative References . . . . . . . . . . . . . . . . . . 18 89 14.2. Informative References . . . . . . . . . . . . . . . . . 20 90 Appendix A. Change Log . . . . . . . . . . . . . . . . . . . . . 21 91 Appendix B. Open Issues . . . . . . . . . . . . . . . . . . . . 21 92 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 21 94 1. Introduction 96 This memo defines a Yang model that translates the existing mib 97 module defined in draft-ietf-ccamp-wson-iv-info and draft-martinelli- 98 ccamp-wson-iv-encode to provide the network impairment information to 99 an SDN controller. One of the key SND controller features is tu 100 support multi vendor network and support the service calculation and 101 deployment in multilayer topologies, for the DWDM mayer it is 102 fundamentad the SDN controller is aware of the optical impairments to 103 verify the feasibility of new circuits before their provisioning. 104 Although SDN controller will not apply exhaustive and accurate 105 algorithms and the optical channel feasibility verification may have 106 a degree of unreliability this function can work on a multivendor 107 common set of parameter and algorithms to ensure the operator the 108 best change to set a circuit. This document follows the same 109 impairment definition and applicability of draft-ietf-ccamp-wson-iv- 110 info. 112 For the optical impairments related to the DWDM Transceiver the draft 113 draft-dharini-ccamp-if-param-yang. Applications are defined in 114 G.698.2 [ITU.G698.2] using optical interface parameters at the 115 single-channel connection points between optical transmitters and the 116 optical multiplexer, as well as between optical receivers and the 117 optical demultiplexer in the DWDM system. This Recommendation uses a 118 methodology which explicitly specify the details of the optical 119 network between reference point Ss and Rs, e.g., the passive and 120 active elements or details of the design. 122 This draft refers and supports the draft-ietf-ccamp-dwdm-if-mng-ctrl- 123 fwk 125 The building of a yang model describing the optical parameters allows 126 the different vendors and operator to retrieve, provision and 127 exchange information across multi-vendor domains in a standardized 128 way. In addition to the parameters specified in ITU recommendations 129 the Yang models support also the "vendor specific parameters". 131 2. The Internet-Standard Management Framework 133 For a detailed overview of the documents that describe the current 134 Internet-Standard Management Framework, please refer to section 7 of 135 RFC 3410 [RFC3410]. 137 This memo specifies a Yang model for optical interfaces. 139 3. Conventions 141 The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", 142 "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this 143 document are to be interpreted as described in RFC 2119 [RFC2119] In 144 the description of OIDs the convention: Set (S) Get (G) and Trap (T) 145 conventions will describe the action allowed by the parameter. 147 4. Definition 149 For a detailed definition this draft refers to draft-ietf-ccamp-wson- 150 iv-info. 152 5. Applicability 154 This document targets at Scenario C defined in [RFC6566] section 155 4.1.1. as approximate impairment estimation. The Approximate 156 concept refer to the fact that this Information Model covers 157 information mainly provided by [ITU.G680] Computational Model. 158 Although the [RFC6566] provides no or little approximation the 159 parameters described in this draft can be applied to the algorithms 160 verifying the circuit feasibility in the new coherent non compensated 161 DWDM networks In this case the impairments verification can reach a 162 good reliability and accuracy. This draft does not address 163 computational matters but provides all the information suitable to 164 cover most of the full coherent network algoritms, not being 165 exhaustive the information can give a acceptable or even good 166 approximation in therm of connection feasibility. This may not be 167 true for legacy compensated network. 169 6. Properties 171 For the signal properties this traft refers the draft-ietf-ccamp- 172 wson-iv-info Ch.2.3 with some extension of the parameters. 174 7. Overview 175 Figure 1 shows a set of reference points, for single-channel 176 connection between transmitters (Tx) and receivers (Rx). Here the 177 DWDM network elements include an OM and an OD (which are used as a 178 pair with the opposing element), one or more optical amplifiers and 179 may also include one or more OADMs. 181 +-------------------------------------------------+ 182 Ss | DWDM Network | Rs 183 +--+ | | | \ / | | | +--+ 184 Tx L1--|->| \ / |--|-->Rx L1 185 +---+ | | | +------+ | | | +--+ 186 +---+ | | | | | | | | +--+ 187 Tx L2--|->| OM |------------>| OADM |-- -------->| OD |--|-->Rx L2 188 +---+ | | | DWDM | | DWDM | | | +--+ 189 +---+ | | | Link +------+ Link | | | +--+ 190 Tx L3--|->| / | ^ \ |--|-->Rx L3 191 +---+ | | / | | \ | | +--+ 192 +-----------------------|--|----------------------+ 193 +--+ +--+ 194 | | 195 Rs v | Ss 196 +-----+ +-----+ 197 |RxLx | |TxLx | 198 +-----+ +-----+ 199 Ss = reference point at the DWDM network element tributary output 200 Rs = reference point at the DWDM network element tributary input 201 Lx = Lambda x 202 OM = Optical Mux 203 OD = Optical Demux 204 OADM = Optical Add Drop Mux 206 from Fig. 5.1/G.698.2 208 Figure 1: External transponder in WDM netwoks 210 7.1. Optical Parameters Description 212 The link between the external transponders through a WDM network 213 media channels are managed at the edges, i.e. at the transmitters 214 (Tx) and receivers (Rx) attached to the S and R reference points 215 respectively. The set of parameters that could be managed are 216 defined by the "application code" notation 218 The definitions of the optical parameters are provided below to 219 increase the readability of the document, where the definition is 220 ended by (R) the parameter can be retrieve with a read, when (W) it 221 can be provisioned by a write, (R,W) can be either read or written. 223 7.1.1. Optical path from point Ss to Rs 225 The following parameters for the optical path from point S and R are 226 defined in G.698.2 [ITU.G698.2]. 228 Maximum and minimum (residual) chromatic dispersion: 229 These parameters define the maximum and minimum value of the 230 optical path "end to end chromatic dispersion" (in ps/nm) that the 231 system shall be able to tolerate. (R) 233 Minimum optical return loss at Ss: 234 These parameter defines minimum optical return loss (in dB) of the 235 cable plant at the source reference point (Ss), including any 236 connectors (R) 238 Maximum discrete reflectance between Ss and Rs: 239 Optical reflectance is defined to be the ratio of the reflected 240 optical power present at a point, to the optical power incident to 241 that point. Control of reflections is discussed extensively in 242 ITU-T Rec. G.957 (R) 244 Maximum differential group delay: 245 Differential group delay (DGD) is the time difference between the 246 fractions of a pulse that are transmitted in the two principal 247 states of polarization of an optical signal. For distances 248 greater than several kilometres, and assuming random (strong) 249 polarization mode coupling, DGD in a fibre can be statistically 250 modelled as having a Maxwellian distribution. (R) 252 Maximum polarization dependent loss: 253 The polarization dependent loss (PDL) is the difference (in dB) 254 between the maximum and minimum values of the channel insertion 255 loss (or gain) of the black link from point SS to RS due to a 256 variation of the state of polarization (SOP) over all SOPs. (R) 258 Maximum inter-channel crosstalk: 259 Inter-channel crosstalk is defined as the ratio of total power in 260 all of the disturbing channels to that in the wanted channel, 261 where the wanted and disturbing channels are at different 262 wavelengths. The parameter specify the isolation of a link 263 conforming to the "black link" approach such that under the worst- 264 case operating conditions the inter-channel crosstalk at any 265 reference point RS is less than the maximum inter-channel 266 crosstalk value (R) 268 Maximum interferometric crosstalk: 269 This parameter places a requirement on the isolation of a link 270 conforming to the "black link" approach such that under the worst 271 case operating conditions the interferometric crosstalk at any 272 reference point RS is less than the maximum interferometric 273 crosstalk value. (R) 275 Maximum optical path OSNR penalty: 276 The optical path OSNR penalty is defined as the difference between 277 the Lowest OSNR at Rs and Lowest OSNR at Ss that meets the BER 278 requirement (R) 280 Maximum ripple: 281 Although is defined in G.698.2 (R). 283 7.1.2. Rs and Ss Configuration 285 For the Rs and Ss configuration this draft refers the draft-dharini- 286 ccamp-dwdm-if-param-yang while for the Rs-Ss extended parameters for 287 coherent transmission interfaces refer to draft-dharini-ccamp-dwdm- 288 if-param-yang 290 7.1.3. Table of Application Codes 292 For Application Codes configuration this draft refers the draft- 293 dharini-ccamp-dwdm-if-param-yang 295 7.2. Use Cases 297 The use cases are described in draft-ietf-ccamp-dwdm-if-mng-ctrl-fwk 299 7.3. Optical Parameters for impairment validation in a WDM network 301 The ietf-opt-parameters-wdm is an augment to the ????. It allows the 302 user to get and set the application Optical Parameters of a DWDM 303 network. 305 module: ietf-opt-parameters-wdm 306 +--rw gain-degrade-high? dbm-t 307 augment /if:interfaces/if:interface: 308 +--rw optical-transport 309 | +--rw attenuator-value? attenuator-t 310 | +--rw offset? decimal64 311 | +--rw channel-power-ref? decimal64 312 | +--rw tilt-calibration? tilt-t 313 +--rw channel-t 314 | +--rw grid? uint32 315 | +--rw channel-spacing? uint32 316 | +--rw identifier? uint32 317 | +--rw n? uint32 318 +--rw channel-n-m 319 +--rw grid? uint32 320 +--rw channel-spacing? uint32 321 +--rw n? uint32 322 +--rw m? uint32 324 8. Structure of the Yang Module 326 ietf-opt-parameters-wdm is a top level model for the support of this 327 feature. 329 9. Yang Module 331 The ietf-opt-parameters-wdm is defined as an extension to ietf 332 interfaces ????. 334 file "ietf-opt-parameters-wdm.yang" 336 module ietf-opt-parameters-wdm { 337 namespace "urn:ietf:params:xml:ns:yang:ietf-opt-parameters-wdm"; 338 prefix iietf-opt-parameters-wdm; 340 import ietf-interfaces { 341 prefix if; 342 } 344 import iana-if-type { 345 prefix ianaift; 346 } 347 organization 348 "IETF CCAMP 349 Working Group"; 351 contact 352 "WG Web: 353 WG List: 355 Editor: Gabriele Galimberti 356 "; 358 description 359 "This module contains a collection of YANG definitions for 360 collecting and configuring Optical Parameters 361 in Optical Networks and calculate the circuit feasibility. 363 Copyright (c) 2016 IETF Trust and the persons identified 364 as authors of the code. All rights reserved. 366 Redistribution and use in source and binary forms, with or 367 without modification, is permitted pursuant to, and 368 subject to the license terms contained in, the Simplified 369 BSD License set forth in Section 4.c of the IETF Trust's 370 Legal Provisions Relating to IETF Documents 371 (http://trustee.ietf.org/license-info)."; 373 revision "2016-10-30" { 374 description 375 "Initial revision."; 376 reference 377 "RFC XXXX: A YANG Data Model for Optical Paramenters 378 of DWDM Networks 379 "; 380 } 382 typedef tilt-t { 383 type decimal64 { 384 fraction-digits 2; 385 range "-5..5"; 386 } 387 description "Tilt Type"; 388 } 390 typedef signal-output-power-t { 391 type decimal64 { 392 fraction-digits 2; 393 range "-10..30"; 394 } 395 description " 396 Amplifier Power provisioning "; 397 } 399 typedef active-channel-t { 400 type union { 401 type uint8 { 402 range "0..200"; 403 } 404 } 405 description " 406 Number of channels active on a span - and on an amplifier"; 407 } 409 typedef dbm-t { 410 type decimal64 { 411 fraction-digits 2; 412 range "-50..-30 | -10..5 | 10000000"; 413 } 414 description " 415 Amplifier Power in dBm "; 416 } 418 typedef attenuator-t { 419 type decimal64 { 420 fraction-digits 2; 421 range "-15..-5"; 422 } 423 description " 424 Attenuation value (attenuator) applied after the Amplifier"; 425 } 427 augment "/if:interfaces/if:interface" { 428 when "if:type = 'ianaift:opticalTransport'" { 429 description "Specific optical-transport Interface Data"; 430 } 431 description "Specific optical-transport Interface Data"; 432 container optical-transport { 433 description "Specific optical-transport Data"; 435 leaf attenuator-value { 436 type attenuator-t; 437 description "External attenuator value "; 438 } 439 leaf offset { 440 type decimal64 { 441 fraction-digits 2; 442 range "-30..30"; 443 } 444 description "Raman and power amplifiers offset"; 445 } 447 leaf channel-power-ref { 448 type decimal64 { 449 fraction-digits 2; 450 range "-10..15"; 451 } 452 description "Optical power per channel"; 453 } 455 leaf tilt-calibration { 456 type tilt-t; 457 description "Amplifier Tilt tuning"; 458 } 459 } 460 } 462 grouping opwr-threshold-warning-grp { 463 description " 464 Minimum Optical Power threshold 465 - this is used to rise Power alarm "; 467 leaf opwr-min { 468 type dbm-t; 469 units "dBm"; 470 default -1; 471 description "Minimum Power Value"; 472 } 474 leaf opwr-min-clear { 475 type dbm-t; 476 units "dBm"; 477 default -1; 478 description "threshold to clear Minimum Power value Alarm"; 479 } 481 leaf opwr-max { 482 type dbm-t; 483 units "dBm"; 484 default 1; 485 description " 486 Maximum Optical Power threshold 487 - this is used to rise Power alarm "; 488 } 489 } 491 grouping gain-degrade-alarm-grp { 492 description " 493 Low Optical Power gain threshold 494 - this is used to rise Power alarm "; 496 leaf gain-degrade-low { 497 type dbm-t; 498 units "dBm"; 499 default -1; 500 description "Low Gain Degrade Value"; 501 } 502 } 504 leaf gain-degrade-high { 505 type dbm-t; 506 units "dBm"; 507 default 1; 508 description " 509 High Optical Power gain threshold 510 - this is used to rise Power alarm "; 511 } 512 } 514 grouping power-degrade-high-alarm-grp { 515 description " 516 High Optical Power gain alarm "; 518 leaf gain-degrade-high { 519 type dbm-t; 520 units "dBm"; 521 default 1; 522 description "Low Gain Degrade Value"; 523 } 524 } 526 grouping power-degrade-low-alarm-grp { 527 description " 528 Low Optical Power gain alarm "; 530 leaf power-degrade-low { 531 type dbm-t; 532 units "dBm"; 533 default -1; 534 description "High Gain Degrade Value"; 536 } 537 } 539 grouping noise { 540 leaf noise { 541 type decimal64 { 542 fraction-digits 2; 543 } 544 units "dB"; 545 description "Noise feasibility - reference ITU-T G.680 546 OSNR added to the signal by the OMS. The noise is intended 547 per channel and is independent of the number of active 548 channels in OMS"; 549 } 550 description "Noise feasibility"; 551 } 553 grouping noise-sigma { 554 leaf noise-sigma { 555 type decimal64 { 556 fraction-digits 2; 557 } 558 units "dB"; 559 description "Noise Sigma feasibility - accuracy of the 560 OSNR added to 561 the signal by the OMS"; 562 } 563 description "Noise Sigma feasibility"; 564 } 566 grouping chromatic-dispersion { 567 leaf chromatic-dispersion { 568 type decimal64 { 569 fraction-digits 2; 570 } 571 units "ps/nm"; 572 description "Chromatic Dispersion (CD) related to the OMS"; 573 } 574 description "Chromatic Dispersion (CD) feasibility"; 575 } 577 grouping chromatic-dispersion-slope { 578 leaf chromatic-dispersion-slope { 579 type decimal64 { 580 fraction-digits 2; 581 } 582 units "ps/nm^2"; 583 description "Chromatic Dispersion (CD) Slope related to 584 the OMS"; 585 } 586 description "Chromatic Dispersion (CD) Slope feasibility"; 587 } 589 grouping pmd { 590 leaf pmd { 591 type decimal64 { 592 fraction-digits 2; 593 } 594 units "ps"; 595 description "Polarization Mode Dispersion (PMD) relared 596 to OMS"; 597 } 598 description "Polarization Mode Dispersion (PMD) feasibility"; 599 } 601 grouping pdl { 602 leaf pdl { 603 type decimal64 { 604 fraction-digits 2; 605 } 606 units "dB"; 607 description "Polarization Dependent Loss (PDL) related to 608 the OMS"; 609 } 610 description "Polarization Dependent Loss (PDL) feasibility"; 611 } 613 grouping drop-power { 614 leaf drop-power { 615 type decimal64 { 616 fraction-digits 2; 617 } 618 units "dBm"; 619 description "Drop Power value at the DWDM Transceiver RX 620 side"; 621 } 622 description "Drop Power feasibility"; 623 } 625 grouping drop-power-sigma { 626 leaf drop-power-sigma { 627 type decimal64 { 628 fraction-digits 2; 629 } 630 units "db"; 631 description "Drop Power Sigma value at the DWDM Transceiver 632 RX side"; 633 } 634 description "Drop Power Sigma feasibility"; 635 } 637 grouping ripple { 638 leaf ripple { 639 type decimal64 { 640 fraction-digits 2; 641 } 642 units "db"; 643 description "Channel Ripple"; 644 } 645 description "Channel Ripple"; 646 } 648 grouping ch-noise-figure { 649 list ch-noise-figure { 650 description "Channel signal-spontaneous noise figure"; 652 leaf input-to-output { 653 type decimal64 { 654 fraction-digits 2; 655 } 656 units "dB"; 657 description "from input port to output port"; 658 } 660 leaf input-to-drop { 661 type decimal64 { 662 fraction-digits 2; 663 } 664 units "dB"; 665 description "from input port to drop port"; 666 } 668 leaf add-to-output { 669 type decimal64 { 670 fraction-digits 2; 671 } 672 units "dB"; 673 description "from add port to output port"; 674 } 675 } 676 description "Channel signal-spontaneous noise figure"; 677 } 678 grouping dgd { 679 leaf dgd { 680 type decimal64 { 681 fraction-digits 2; 682 } 683 units "db"; 684 description "differential group delay"; 685 } 686 description "differential group delay"; 687 } 689 grouping ch-isolation { 690 list ch-isolation { 691 description "adjacent and not adjacent channel isolation"; 693 leaf ad-ch-isol { 694 type decimal64 { 695 fraction-digits 2; 696 } 697 units "dB"; 698 description "adjecent channel isolation"; 699 } 701 leaf no-ad-ch-iso { 702 type decimal64 { 703 fraction-digits 2; 704 } 705 units "dB"; 706 description "non adjecent channel isolation"; 707 } 708 } 709 description "djacent and not adjacent channel isolation"; 710 } 712 grouping ch-extinction { 713 leaf cer { 714 type decimal64 { 715 fraction-digits 2; 716 } 717 units "db"; 718 description "channel extinction"; 719 } 720 description "channel extinction"; 721 } 723 grouping att-coefficient { 724 leaf att { 725 type decimal64 { 726 fraction-digits 2; 727 } 728 units "db"; 729 description "Attenuation coefficient (for a fibre segment)"; 730 } 731 description "Attenuation coefficient (for a fibre segment)"; 732 } 734 } 736 } 738 740 10. Security Considerations 742 The YANG module defined in this memo is designed to be accessed via 743 the NETCONF protocol [RFC6241]. he lowest NETCONF layer is the secure 744 transport layer and the mandatory-to-implement secure transport is 745 SSH [RFC6242]. The NETCONF access control model [RFC6536] provides 746 the means to restrict access for particular NETCONF users to a pre- 747 configured subset of all available NETCONF protocol operation and 748 content. 750 11. IANA Considerations 752 This document registers a URI in the IETF XML registry [RFC3688]. 753 Following the format in [RFC3688], the following registration is 754 requested to be made: 756 URI: urn:ietf:params:xml:ns:yang:ietf-interfaces:ietf-ext-xponder- 757 wdm-if 759 Registrant Contact: The IESG. 761 XML: N/A, the requested URI is an XML namespace. 763 This document registers a YANG module in the YANG Module Names 764 registry [RFC6020]. 766 This document registers a YANG module in the YANG Module Names 767 registry [RFC6020]. 769 prefix: ietf-ext-xponder-wdm-if reference: RFC XXXX 771 12. Acknowledgements 773 Marco Cardani. 775 13. Contributors 777 Dean Bogdanovic 778 Juniper Networks 779 Westford 780 U.S.A. 781 email deanb@juniper.net 783 Walid Wakim 784 Cisco 785 9501 Technology Blvd 786 ROSEMONT, ILLINOIS 60018 787 UNITED STATES 788 email wwakim@cisco.com 790 Marco Cardani 791 Cisco 792 vis S.Maria Molgora, 46b 793 20871 - Vimercate 794 Monza Brianza 795 Italy 796 email mcardani@cisco.com 798 Giovanni Martinelli 799 Cisco 800 vis S.Maria Molgora, 46b 801 20871 - Vimercate 802 Monza Brianza 803 Italy 804 email giomarti@cisco.com 806 14. References 808 14.1. Normative References 810 [RFC2863] McCloghrie, K. and F. Kastenholz, "The Interfaces Group 811 MIB", RFC 2863, DOI 10.17487/RFC2863, June 2000, 812 . 814 [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate 815 Requirement Levels", BCP 14, RFC 2119, 816 DOI 10.17487/RFC2119, March 1997, 817 . 819 [RFC2578] McCloghrie, K., Ed., Perkins, D., Ed., and J. 820 Schoenwaelder, Ed., "Structure of Management Information 821 Version 2 (SMIv2)", STD 58, RFC 2578, 822 DOI 10.17487/RFC2578, April 1999, 823 . 825 [RFC2579] McCloghrie, K., Ed., Perkins, D., Ed., and J. 826 Schoenwaelder, Ed., "Textual Conventions for SMIv2", 827 STD 58, RFC 2579, DOI 10.17487/RFC2579, April 1999, 828 . 830 [RFC2580] McCloghrie, K., Ed., Perkins, D., Ed., and J. 831 Schoenwaelder, Ed., "Conformance Statements for SMIv2", 832 STD 58, RFC 2580, DOI 10.17487/RFC2580, April 1999, 833 . 835 [RFC3591] Lam, H-K., Stewart, M., and A. Huynh, "Definitions of 836 Managed Objects for the Optical Interface Type", RFC 3591, 837 DOI 10.17487/RFC3591, September 2003, 838 . 840 [RFC6205] Otani, T., Ed. and D. Li, Ed., "Generalized Labels for 841 Lambda-Switch-Capable (LSC) Label Switching Routers", 842 RFC 6205, DOI 10.17487/RFC6205, March 2011, 843 . 845 [ITU.G698.2] 846 International Telecommunications Union, "Amplified 847 multichannel dense wavelength division multiplexing 848 applications with single channel optical interfaces", 849 ITU-T Recommendation G.698.2, November 2009. 851 [ITU.G709] 852 International Telecommunications Union, "Interface for the 853 Optical Transport Network (OTN)", ITU-T Recommendation 854 G.709, March 2003. 856 [ITU.G872] 857 International Telecommunications Union, "Architecture of 858 optical transport networks", ITU-T Recommendation G.872, 859 November 2001. 861 [ITU.G798] 862 International Telecommunications Union, "Characteristics 863 of optical transport network hierarchy equipment 864 functional blocks", ITU-T Recommendation G.798, October 865 2010. 867 [ITU.G874] 868 International Telecommunications Union, "Management 869 aspects of optical transport network elements", 870 ITU-T Recommendation G.874, July 2010. 872 [ITU.G874.1] 873 International Telecommunications Union, "Optical transport 874 network (OTN): Protocol-neutral management information 875 model for the network element view", ITU-T Recommendation 876 G.874.1, January 2002. 878 [ITU.G959.1] 879 International Telecommunications Union, "Optical transport 880 network physical layer interfaces", ITU-T Recommendation 881 G.959.1, November 2009. 883 [ITU.G826] 884 International Telecommunications Union, "End-to-end error 885 performance parameters and objectives for international, 886 constant bit-rate digital paths and connections", 887 ITU-T Recommendation G.826, November 2009. 889 [ITU.G8201] 890 International Telecommunications Union, "Error performance 891 parameters and objectives for multi-operator international 892 paths within the Optical Transport Network (OTN)", 893 ITU-T Recommendation G.8201, April 2011. 895 [ITU.G694.1] 896 International Telecommunications Union, "Spectral grids 897 for WDM applications: DWDM frequency grid", 898 ITU-T Recommendation G.694.1, June 2002. 900 [ITU.G7710] 901 International Telecommunications Union, "Common equipment 902 management function requirements", ITU-T Recommendation 903 G.7710, May 2008. 905 14.2. Informative References 907 [RFC3410] Case, J., Mundy, R., Partain, D., and B. Stewart, 908 "Introduction and Applicability Statements for Internet- 909 Standard Management Framework", RFC 3410, 910 DOI 10.17487/RFC3410, December 2002, 911 . 913 [RFC2629] Rose, M., "Writing I-Ds and RFCs using XML", RFC 2629, 914 DOI 10.17487/RFC2629, June 1999, 915 . 917 [RFC4181] Heard, C., Ed., "Guidelines for Authors and Reviewers of 918 MIB Documents", BCP 111, RFC 4181, DOI 10.17487/RFC4181, 919 September 2005, . 921 [I-D.ietf-ccamp-dwdm-if-mng-ctrl-fwk] 922 Kunze, R., Grammel, G., Beller, D., and G. Galimberti, "A 923 framework for Management and Control of DWDM optical 924 interface parameters", draft-ietf-ccamp-dwdm-if-mng-ctrl- 925 fwk-00 (work in progress), April 2016. 927 [RFC4054] Strand, J., Ed. and A. Chiu, Ed., "Impairments and Other 928 Constraints on Optical Layer Routing", RFC 4054, 929 DOI 10.17487/RFC4054, May 2005, 930 . 932 Appendix A. Change Log 934 This optional section should be removed before the internet draft is 935 submitted to the IESG for publication as an RFC. 937 Note to RFC Editor: please remove this appendix before publication as 938 an RFC. 940 Appendix B. Open Issues 942 Note to RFC Editor: please remove this appendix before publication as 943 an RFC. 945 Authors' Addresses 947 Gabriele Galimberti (editor) 948 Cisco 949 Via Santa Maria Molgora, 48 c 950 20871 - Vimercate 951 Italy 953 Phone: +390392091462 954 Email: ggalimbe@cisco.com 955 Ruediger Kunze 956 Deutsche Telekom 957 Dddd, xx 958 Berlin 959 Germany 961 Phone: +49xxxxxxxxxx 962 Email: RKunze@telekom.de 964 Dharini Hiremagalur (editor) 965 Juniper 966 1194 N Mathilda Avenue 967 Sunnyvale - 94089 California 968 USA 970 Email: dharinih@juniper.net 972 Gert Grammel (editor) 973 Juniper 974 Oskar-Schlemmer Str. 15 975 80807 Muenchen 976 Germany 978 Phone: +49 1725186386 979 Email: ggrammel@juniper.net