idnits 2.17.1 draft-esdih-ccamp-layer0-types-ext-00.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 draft header indicates that this document updates draft-ietf-ccamp-layer0-types, but the abstract doesn't seem to mention this, which it should. Miscellaneous warnings: ---------------------------------------------------------------------------- == The copyright year in the IETF Trust and authors Copyright Line does not match the current year == Line 806 has weird spacing: '... leaf min-O...' == Line 816 has weird spacing: '... leaf min-Q...' == The document doesn't use any RFC 2119 keywords, yet seems to have RFC 2119 boilerplate text. -- The document date (22 February 2021) is 1152 days in the past. Is this intentional? Checking references for intended status: Proposed Standard ---------------------------------------------------------------------------- (See RFCs 3967 and 4897 for information about using normative references to lower-maturity documents in RFCs) == Unused Reference: 'I-D.ietf-ccamp-layer0-types' is defined on line 1051, but no explicit reference was found in the text == Unused Reference: 'I-D.ietf-ccamp-optical-impairment-topology-yang' is defined on line 1058, but no explicit reference was found in the text == Unused Reference: 'I-D.ietf-ccamp-wson-yang' is defined on line 1066, but no explicit reference was found in the text == Unused Reference: 'RFC8795' is defined on line 1088, but no explicit reference was found in the text == Unused Reference: 'RFC2629' is defined on line 1105, but no explicit reference was found in the text == Outdated reference: A later version (-15) exists of draft-ietf-ccamp-optical-impairment-topology-yang-05 == Outdated reference: A later version (-10) exists of draft-ietf-ccamp-dwdm-if-param-yang-05 -- Obsolete informational reference (is this intentional?): RFC 2629 (Obsoleted by RFC 7749) -- Obsolete informational reference (is this intentional?): RFC 5226 (Obsoleted by RFC 8126) Summary: 0 errors (**), 0 flaws (~~), 11 warnings (==), 4 comments (--). Run idnits with the --verbose option for more detailed information about the items above. -------------------------------------------------------------------------------- 2 CCAMP D. Beller, Ed. 3 Internet-Draft S. Belotti, Ed. 4 Updates: draft-ietf-ccamp-layer0-types (if Nokia 5 approved) H. Zheng 6 Intended status: Standards Track I. Busi 7 Expires: 26 August 2021 Huawei 8 E. Le Rouzic 9 Orange 10 22 February 2021 12 A YANG Data Model for Layer 0 Types - Revision 2 13 draft-esdih-ccamp-layer0-types-ext-00 15 Abstract 17 This document defines a collection of common data types and groupings 18 in the YANG data modeling language, which are used in several YANG 19 modules for wavelength Division multiplexing (WDM) transport 20 networks. The YANG module ietf-layer0-types-ext updates ietf- 21 layer0-types defined in draft-ietf-ccamp-layer0-types, which has been 22 reduced in scope prior to publication to only cover spectrum 23 management related aspects required for the YANG module ietf-wson- 24 topology defined in draft-ietf-ccamp-wson-yang. 26 To be completed 28 Status of This Memo 30 This Internet-Draft is submitted in full conformance with the 31 provisions of BCP 78 and BCP 79. 33 Internet-Drafts are working documents of the Internet Engineering 34 Task Force (IETF). Note that other groups may also distribute 35 working documents as Internet-Drafts. The list of current Internet- 36 Drafts is at https://datatracker.ietf.org/drafts/current/. 38 Internet-Drafts are draft documents valid for a maximum of six months 39 and may be updated, replaced, or obsoleted by other documents at any 40 time. It is inappropriate to use Internet-Drafts as reference 41 material or to cite them other than as "work in progress." 43 This Internet-Draft will expire on 26 August 2021. 45 Copyright Notice 47 Copyright (c) 2021 IETF Trust and the persons identified as the 48 document authors. All rights reserved. 50 This document is subject to BCP 78 and the IETF Trust's Legal 51 Provisions Relating to IETF Documents (https://trustee.ietf.org/ 52 license-info) in effect on the date of publication of this document. 53 Please review these documents carefully, as they describe your rights 54 and restrictions with respect to this document. Code Components 55 extracted from this document must include Simplified BSD License text 56 as described in Section 4.e of the Trust Legal Provisions and are 57 provided without warranty as described in the Simplified BSD License. 59 Table of Contents 61 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 2 62 1.1. Requirements Language . . . . . . . . . . . . . . . . . . 2 63 1.2. Terminology . . . . . . . . . . . . . . . . . . . . . . . 3 64 2. Extensions for the Layer 0 Types Module . . . . . . . . . . . 3 65 3. Layer0 Types Revision 2 YANG CODE . . . . . . . . . . . . . . 4 66 4. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 22 67 5. Contributors . . . . . . . . . . . . . . . . . . . . . . . . 22 68 6. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 22 69 7. Security Considerations . . . . . . . . . . . . . . . . . . . 22 70 8. References . . . . . . . . . . . . . . . . . . . . . . . . . 22 71 8.1. Normative References . . . . . . . . . . . . . . . . . . 22 72 8.2. Informative References . . . . . . . . . . . . . . . . . 23 73 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 24 75 1. Introduction 77 YANG [RFC7950] is a data modeling language used to model 78 configuration data, state data, Remote Procedure Calls, and 79 notifications for network management protocols such as NETCONF 80 [RFC6241]. The YANG language supports a small set of built-in data 81 types and provides mechanisms to derive other types from the built-in 82 types. 84 This document introduces a collection of common data types derived 85 from the built-in YANG data types. The derived types and groupings 86 are designed to be the common types applicable for modeling Traffic 87 Engineering (TE) features as well as non-TE features (e.g., physical 88 network configuration aspect) for Layer 0 optical networks in 89 model(s) defined outside of this document. 91 1.1. Requirements Language 93 The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", 94 "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this 95 document are to be interpreted as described in RFC 2119 [RFC2119]. 97 1.2. Terminology 99 2. Extensions for the Layer 0 Types Module 101 This document defines YANG module extensions for common Layer 0 102 types. named ietf-layer0-types-ext. This module can be used for 103 both WSON and Flexi-grid DWDM networks but in particular is adding 104 common types used in the context of optical impairment aware topology 105 model in WSON and SSONs. The ietf-layer0-types-ext module contains 106 the following YANG identities, types and groupings that can be reused 107 in other YANG modules: 109 transceiver-capabilities: 111 a YANG grouping to define the transceiver capabilities (also called 112 "modes") needed to determine optical signal compatibility. 114 standard-mode: 116 a YANG grouping for ITU-T G.698.2 standard mode that guarantees 117 interoperability. 119 organizational-mode: 121 a YANG grouping to define transponder operational mode supported by 122 organizations or vendors. 124 common-explicit-mode: 126 a YANG grouping to define the list of attributes related to optical 127 impairments limits in case of transceiver explicit mode. This 128 grouping should be the same used in 129 [I-D.ietf-ccamp-dwdm-if-param-yang]. 131 common-organizational-explicit-mode: 133 a YANG grouping to define the common capabilities attributes limit 134 range in case of operational mode and explicit mode. Also this 135 grouping should be used in [I-D.ietf-ccamp-dwdm-if-param-yang]. 137 cd-pmd-penalty: 139 a YANG grouping to define the triplet used as entries in the list 140 optional penalty associated with a given accumulated CD and PMD. 141 This list of triplet cd, pmd, penalty can be used to sample the 142 function penalty = f(CD, PMD). 144 [Editor's note: There is still stuff from the xml template that needs 145 to be removed] 147 3. Layer0 Types Revision 2 YANG CODE 149 The YANG code is developed on GitHub and can also be found in the 150 following CCAMP repository: 152 https://github.com/ietf-ccamp-wg/ietf-ccamp-layer0-types-ext 154 [Editor's note: YANG code below has to be updated before submitting a 155 new revision!] 157 158 module ietf-layer0-types-ext { 159 namespace "urn:ietf:params:xml:ns:yang:ietf-layer0-types-ext"; 160 prefix "l0-types-ext"; 162 organization 163 "IETF CCAMP Working Group"; 164 contact 165 "WG Web: 166 WG List: 168 Editor: Dieter Beller 169 171 Editor: Sergio Belotti 172 174 Editor: Italo Busi 175 177 Editor: Haomian Zheng 178 "; 180 // Additional contacts TBA (contributors) 182 description 183 "Description to be added!!! 185 Copyright (c) 2021 IETF Trust and the persons identified 186 as authors of the code. All rights reserved. 188 Redistribution and use in source and binary forms, with 189 or without modification, is permitted pursuant to, and 190 subject to the license terms contained in, the Simplified 191 BSD License set forth in Section 4.c of the IETF Trust's 192 Legal Provisions Relating to IETF Documents 193 (http://trustee.ietf.org/license-info). 195 This version of this YANG module is part of RFC XXXX; see 196 the RFC itself for full legal notices."; 198 revision "2021-02-12" { 199 description 200 "Initial Version"; 201 reference 202 "RFC XXXX: A YANG Data Model for Layer 0 Types - Revision 2"; 203 } 205 /* 206 * Identities 207 */ 209 identity modulation { 210 description "base identity for modulation type"; 211 } 213 identity QPSK { 214 base modulation; 215 description 216 "QPSK (Quadrature Phase Shift Keying) modulation"; 217 } 219 identity DP-QPSK { 220 base modulation; 221 description 222 "DP-QPSK (Dual Polarization Quadrature 223 Phase Shift Keying) modulation"; 224 } 226 identity QAM8 { 227 base modulation; 228 description 229 "8QAM (8-State Quadrature Amplitude Modulation) modulation"; 230 } 232 identity QAM16 { 233 base modulation; 234 description 235 "QAM16 (Quadrature Amplitude Modulation)"; 236 } 238 identity DP-QAM8 { 239 base modulation; 240 description 241 "DP-QAM8 (Dual Polarization Quadrature Amplitude Modulation)"; 242 } 244 identity DC-DP-QAM8 { 245 base modulation; 246 description 247 "DC DP-QAM8 (Dual Carrier Dual Polarization Quadrature 248 Amplitude Modulation)"; 249 } 251 identity DP-QAM16 { 252 base modulation; 253 description 254 "DP-QAM16 (Dual Polarization Quadrature Amplitude 255 Modulation)"; 256 } 258 identity DC-DP-QAM16 { 259 base modulation; 260 description 261 "DC DP-QAM16 (Dual Carrier Dual Polarization Quadrature 262 Amplitude Modulation)"; 263 } 265 identity fec-type { 266 description 267 "Base identity from which specific FEC 268 (Forward Error Correction) type identities are derived."; 269 } 271 identity g-fec { 272 base fec-type; 273 description 274 "G-FEC (Generic-FEC)"; 275 } 276 identity e-fec { 277 base fec-type; 278 description 279 "E-FEC (Enhanced-FEC)"; 280 } 281 identity no-fec { 282 base fec-type; 283 description 284 "No FEC"; 285 } 287 identity reed-solomon { 288 base fec-type; 289 description 290 "Reed-Solomon error correction"; 291 } 293 identity hamming-code { 294 base fec-type; 295 description 296 "Hamming Code error correction"; 297 } 299 identity golay { 300 base fec-type; 301 description "Golay error correction"; 302 } 304 identity line-coding { 305 description 306 "base line-coding class"; 307 reference 308 "ITU-T G.698.2-201811 section 7"; 309 } 311 identity line-coding-NRZ-2p5G { 312 base line-coding; 313 description 314 "ITU-T G.698.2-201811 section 7 table 8-1"; 315 } 317 identity line-coding-NRZ-OTU1 { 318 base line-coding; 319 description 320 "ITU-T G.698.2-201811 section 7 table 8-2"; 321 } 323 identity line-coding-NRZ-10G { 324 base line-coding; 325 description 326 "ITU-T G.698.2-201811 section 7 table 8-3/8-5"; 327 } 329 identity line-coding-NRZ-OTU2 { 330 base line-coding; 331 description 332 "ITU-T G.698.2-201811 section 7 table 8-4/8-6"; 333 } 335 identity wavelength-assignment { 336 description 337 "Wavelength selection base"; 338 reference 339 "RFC6163:Framework for GMPLS and Path Computation Element 340 (PCE) Control of Wavelength Switched Optical Networks (WSONs)"; 341 } 343 identity unspecified-wavelength-assignment { 344 base wavelength-assignment; 345 description 346 "No method specified"; 347 } 349 identity first-fit-wavelength-assignment { 350 base wavelength-assignment; 351 description 352 "All the available wavelengths are numbered, 353 and this WA (Wavelength Assignment) method chooses 354 the available wavelength with the lowest index"; 355 } 357 identity random-wavelength-assignment { 358 base wavelength-assignment; 359 description 360 "This WA method chooses an available 361 wavelength randomly"; 362 } 364 identity least-loaded-wavelength-assignment { 365 base wavelength-assignment; 366 description 367 "This WA method selects the wavelength that 368 has the largest residual capacity on the most loaded 369 link along the route (in multi-fiber networks)"; 370 } 372 identity term-type { 373 description 374 "Termination type"; 375 reference 376 "ITU-T G.709: Interfaces for the Optical Transport Network"; 377 } 379 identity term-phys { 380 base term-type; 381 description 382 "Physical layer termination"; 383 } 384 identity term-otu { 385 base term-type; 386 description 387 "OTU (Optical Transport Unit) termination"; 388 } 390 identity term-odu { 391 base term-type; 392 description 393 "ODU (Optical Data Unit) termination"; 394 } 396 identity term-opu { 397 base term-type; 398 description 399 "OPU (Optical Payload Unit) termination"; 400 } 402 identity otu-type { 403 description 404 "Base identity from which specific OTU identities are derived"; 405 reference 406 "ITU-T G.709: Interfaces for the Optical Transport Network"; 407 } 409 identity OTU1 { 410 base otu-type; 411 description 412 "OTU1 (2.66 Gb/s)"; 413 } 415 identity OTU1e { 416 base otu-type; 417 description 418 "OTU1e (11.04 Gb/s)"; 419 } 421 identity OTU1f { 422 base otu-type; 423 description 424 "OTU1f (11.27 Gb/s)"; 425 } 427 identity OTU2 { 428 base otu-type; 429 description 430 "OTU2 (10.70 Gb/s)"; 431 } 432 identity OTU2e { 433 base otu-type; 434 description 435 "OTU2e (11.09 Gb/s)"; 436 } 438 identity OTU2f { 439 base otu-type; 440 description 441 "OTU2f (11.31G)"; 442 } 444 identity OTU3 { 445 base otu-type; 446 description 447 "OTU3 (43.01 Gb/s)"; 448 } 450 identity OTU3e1 { 451 base otu-type; 452 description 453 "OTU3e1 (44.57 Gb/s)"; 454 } 456 identity OTU3e2 { 457 base otu-type; 458 description 459 "OTU3e2 (44.58 Gb/s)"; 460 } 462 identity OTU4 { 463 base otu-type; 464 description 465 "OTU4 (111.80 Gb/s)"; 466 } 468 identity OTUCn { 469 base otu-type; 470 description 471 "OTUCn (n x 105.25 Gb/s)"; 472 } 474 /* 475 * Typedefs 476 */ 478 typedef operational-mode { 479 type string; 480 description 481 "Organization/vendor specific mode that guarantees 482 interoperability."; 483 reference "ITU-T G.698.2 (11/2018)"; 484 } 486 typedef standard-mode { 487 type string; 488 description 489 "ITU-T G.698.2 standard mode that guarantees 490 interoperability. 491 It must be an string with the following format: 492 B-DScW-ytz(v) where all these attributes 493 are conformant 494 to the ITU-T recomendation"; 495 reference "ITU-T G.698.2 (11/2018)"; 496 } 498 typedef organization-identifier { 499 type string; 500 description 501 "vendor/organization identifier that uses a private mode 502 out of already defined in G.698.2 ITU-T application-code"; 503 reference 504 "RFC7581: Routing and Wavelength Assignment Information 505 Encoding for Wavelength Switched Optical Networks"; 506 } 508 typedef frequency-thz { 509 type decimal64 { 510 fraction-digits 6; 511 } 512 units THz; 513 description 514 "The DWDM frequency in THz, e.g., 193.112500"; 515 reference 516 "RFC6205: Generalized Labels for 517 Lambda-Switch-Capable (LSC) Label Switching Routers"; 518 } 519 typedef frequency-ghz { 520 type decimal64 { 521 fraction-digits 3; 522 } 523 units GHz; 524 description 525 "The DWDM frequency in GHz, e.g., 193112.500"; 526 reference 527 "RFC6205: Generalized Labels for 528 Lambda-Switch-Capable (LSC) Label Switching Routers"; 529 } 531 typedef dbm-t { 532 type int32; 533 units ".01dbm"; 534 description 535 "Amplifiers and Transceivers Power in dBm."; 536 } 538 typedef snr { 539 type decimal64 { 540 fraction-digits 2; 541 } 542 units "dB@0.1nm"; 543 description 544 "(Optical) Signal to Noise Ratio measured over 0.1 nm 545 resolution bandwidth"; 546 } 548 /* 549 * Groupings 550 */ 552 /* supported inverse multiplexing capabilities such as 553 max. OTSiG:OTSi cardinality 554 It is a transponder attribute not transceiver 555 */ 557 /* leaf multiplexing-cap { 558 type uint32; 559 config false; 560 description "supported inverse multiplexing capabilities 561 such as max. OTSiG:OTSi cardinality"; 562 } 563 */ 565 grouping transceiver-capabilities { 566 description 567 "This grouping is intended to be use for reporting the 568 capabilities of a transceiver."; 570 container supported-modes { 571 description 572 "Transceiver's supported modes."; 573 list supported-mode { 574 key "mode-id"; 575 config false; 576 description "list of supported transceiver's modes."; 577 leaf mode-id { 578 type string { 579 length "1..255"; 580 } 581 description "ID for the supported transceiver's mode."; 582 } 583 choice mode { 584 mandatory true; 585 description 586 "Indicates whether the transceiver's mode is a standard 587 mode, an organizational mode or an explicit mode."; 588 case G.698.2 { 589 uses standard-mode; 590 } 591 case organizational-mode { 592 container organizational-mode { 593 description 594 "The set of attributes for an organizational mode"; 595 uses organizational-mode; 596 uses common-organizational-explicit-mode; 597 } // container organizational-mode 598 } 599 case explicit-mode { 600 container explicit-mode { 601 description 602 "The set of attributes for an explicit mode"; 603 container supported-modes { 604 description 605 "Container for all the standard and organizational 606 modes supported by the transceiver's explicit 607 mode."; 608 leaf-list supported-application-codes { 609 type leafref { 610 path "../../../mode-id"; 611 } 612 must "../../../../" 613 + "supported-mode[mode-id=current()]/" 614 + "standard-mode" { 615 description 616 "The pointer is only for application codes 617 supported by transceiver."; 618 } 619 description 620 "List of pointers to the application codes 621 supported by the transceiver's explicit mode."; 622 } 623 leaf-list supported-organizational-modes { 624 type leafref { 625 path "../../../mode-id"; 626 } 627 must "../../../../" 628 + "supported-mode[mode-id=current()]/" 629 + "organizational-mode" { 630 description 631 "The pointer is only for organizational modes 632 supported by transceiver."; 633 } 634 description 635 "List of pointers to the organizational modes 636 supported by the transceiver's explicit mode."; 637 } 638 } // container supported-modes 639 uses common-explicit-mode; 640 uses common-organizational-explicit-mode; 641 } // container explicit-mode 642 } // end of case explicit-mode 643 } // end of choice 644 } // list supported-modes 645 } // container supported-modes 646 } // grouping transceiver-capabilities 648 grouping standard-mode { 649 description 650 "ITU-T G.698.2 standard mode that guarantees interoperability. 651 It must be an string with the following format: 652 B-DScW-ytz(v) where all these attributes are conformant 653 to the ITU-T recomendation"; 655 leaf standard-mode { 656 type standard-mode; 657 config false; 658 description 659 "G.698.2 standard mode"; 660 } 661 } 663 grouping organizational-mode { 664 description 665 "Transponder operational mode supported by organizations or 666 vendor"; 668 leaf operational-mode { 669 type operational-mode; 670 config false; 671 description 672 "configured organization- or vendor-specific 673 application identifiers (AI) supported by the transponder"; 674 } 676 leaf organization-identifier { 677 type organization-identifier; 678 config false; 679 description 680 "organization identifier that uses organizational 681 mode"; 683 } 684 } 686 grouping cd-pmd-penalty { 687 description "entries of table; triplet chromatic 688 dispersion, polarization mode dispersion and 689 associated penalty"; 691 leaf chromatic-dispersion { 692 type decimal64 { 693 fraction-digits 2; 694 range "0..max"; 695 } 696 units "ps/nm"; 697 config false; 698 mandatory true; 699 description "chromatic dispersion"; 700 } 702 leaf polarization-mode-dispersion { 703 type decimal64 { 704 fraction-digits 2; 705 range "0..max"; 706 } 707 units "ps"; 708 config false; 709 mandatory true; 710 description "Polarization mode dispersion"; 711 } 713 leaf penalty { 714 type decimal64 { 715 fraction-digits 2; 716 range "0..max"; 717 } 718 units "dB"; 719 config false; 720 mandatory true; 721 description "Associated penalty on the receiver"; 722 } 723 } 725 /* 726 * This grouping represent the list of attributes related to 727 * optical impairment limits for explicit mode 728 * (min OSNR, max PMD, max CD, max PDL, Q-factor limit, etc.) 729 * In case of standard and operational mode the attributes are 730 * implicit 731 */ 733 grouping common-explicit-mode { 734 description "Attributes capabilities related to 735 explicit mode of an optical transceiver"; 737 leaf line-coding-bitrate { 738 type identityref { 739 base line-coding; 740 } 741 config false; 742 description "Bit rate/line coding of optical tributary signal"; 743 reference 744 "ITU-T G.698.2 section 7.1.2"; 745 } 746 leaf max-polarization-mode-dispersion { 747 type decimal64 { 748 fraction-digits 2; 749 range "0..max"; 750 } 751 units "ps"; 752 config false; 753 description 754 "Maximum acceptable accumulated polarization mode 755 dispersion on the receiver"; 756 } 757 leaf max-chromatic-dispersion { 758 type decimal64 { 759 fraction-digits 2; 760 range "0..max"; 761 } 762 units "ps/nm"; 763 config false; 764 description 765 "Maximum acceptable accumulated chromatic dispersion 766 on the receiver"; 767 } 768 list chromatic-and-polarization-dispersion-penalty { 769 config false; 770 description 771 "Optional penalty associated with a given accumulated 772 CD and PMD. 773 This list of triplet cd, pmd, penalty can be used to 774 sample the function penalty = f(CD, PMD)."; 775 uses cd-pmd-penalty ; 776 } 777 leaf max-diff-group-delay { 778 type int32; 779 config false; 780 description "Maximum Differential group delay of this mode 781 for this lane"; 782 } 783 leaf max-polarization-dependent-loss { 784 type decimal64 { 785 fraction-digits 2; 786 } 787 units dB ; 788 description 789 "Maximum acceptable accumulate polarization dependent loss"; 790 } 791 leaf available-modulation-type { 792 type identityref { 793 base modulation; 794 } 795 config false; 796 description 797 "Modulation type the specific transceiver in the list 798 can support"; 799 } 800 leaf OTSi-carrier-bandwidth { 801 type frequency-ghz; 802 config false; 803 description 804 "Carrier bandwidth occupancy"; 805 } 806 leaf min-OSNR { 807 type snr; 808 config false; 809 description "min OSNR measured over 0.1 nm 810 resolution bandwidth: 811 if received OSNR at minimum Rx-power is lower than MIN-OSNR, 812 an increased level of bit-errors post-FEC needs 813 to be expected."; 814 // change resolution BW from 12.5 GHz to 0.1 nm 815 } 816 leaf min-Q-factor { 817 type int32; 818 units "dB"; 819 config false; 820 description "min Qfactor at FEC threshold"; 821 } 822 leaf available-baud-rate { 823 type uint32; 824 units Bd; 825 config false; 826 description 827 "Baud-rate the specific transceiver in 828 the list can support. 829 Baud-rate is the unit for 830 symbol rate or modulation rate 831 in symbols per second or 832 pulses per second. 833 It is the number of distinct symbol 834 changes (signal events) made to the 835 transmission medium 836 per second in a digitally 837 modulated signal or a line code"; 838 } 839 leaf available-fec-type { 840 type identityref { 841 base fec-type; 842 } 843 config false; 844 description "Available FEC"; 845 } 846 leaf fec-code-rate { 847 type decimal64 { 848 fraction-digits 8; 849 range "0..max"; 850 } 851 config false; 852 description "FEC-code-rate"; 853 } 854 leaf fec-threshold { 855 type decimal64 { 856 fraction-digits 8; 857 range "0..max"; 858 } 859 config false; 860 description 861 "Threshold on the BER, for which FEC 862 is able to correct errors"; 863 } 864 } // grouping common-explicit-mode 866 grouping common-organizational-explicit-mode { 867 description "Common capability attributes limit range 868 in case of operational mode and explicit mode. 869 These attributes are supported separately in 870 case of application codes"; 872 /* transmitter tuning range (f_tx-min, f_tx-max) */ 874 leaf min-central-frequency { 875 type frequency-thz; 876 config false; 877 description 878 "This parameter indicates the minimum frequency for 879 this transceiver."; 880 } 881 leaf max-central-frequency { 882 type frequency-thz; 883 config false; 884 description 885 "This parameter indicates the maximum frequency 886 for this transceiver."; 887 } 889 /* transmitter-tunability-grid */ 891 leaf minimum-channel-spacing { 892 type frequency-ghz; 893 config false; 894 description 895 "This paramenter represents the minumum difference in 896 frequency between two adjacent channels 897 (ref. G.698.2 sec.7.1.1). 898 This free value is to permit OTSi's central frequency not 899 to stay on the G.694.1 grid."; 900 } 902 /* supported transmitter power range [p_tx-min, p_tx_max] */ 904 leaf tx-channel-power-min { 905 type dbm-t; 906 config false; 907 description "The minimum output power of this interface"; 908 } 909 leaf tx-channel-power-max { 910 type dbm-t; 911 config false; 912 description "The maximum output power of this interface"; 913 } 915 /* supported receiver power range [p_rx-min, p_rx_max] */ 917 leaf rx-channel-power-min { 918 type dbm-t; 919 config false; 920 description "The minimum input power of this interface"; 921 } 922 leaf rx-channel-power-max { 923 type dbm-t; 924 config false; 925 description "The maximum input power of this interface"; 926 } 928 leaf rx-total-power-max { 929 type dbm-t; 930 config false; 931 description "Maximum rx optical power for 932 all the channels"; 933 } 935 } // grouping common-organizational-explicit-mode 937 /* This grouping represent the list of configured parameters */ 938 /* values independent of operational mode */ 940 grouping common-transceiver-configured-param { 941 description "Capability of an optical transceiver"; 943 leaf OTSi-carrier-frequency { 944 type frequency-thz; 945 description 946 "OTSi carrier frequency, equivalent to the 947 actual configured transmitter frequency"; 948 } 950 leaf tx-channel-power { 951 type dbm-t; 952 description "The current channel transmit power"; 953 } 955 leaf rx-channel-power { 956 type dbm-t; 957 config false; 958 description "The current channel received power "; 959 } 961 leaf rx-total-power { 962 type dbm-t; 963 config false; 964 description "Current total received power"; 965 } 967 } // grouping for configured attributes out of mode 969 grouping l0-tunnel-attributes { 970 description 971 "Parameters for Layer0 (WSON or Flexi-Grid) Tunnels."; 972 leaf fec-type { 973 type identityref { 974 base fec-type; 975 } 976 description 977 "FEC type."; 978 } 979 leaf termination-type { 980 type identityref { 981 base term-type; 982 } 983 description 984 "Termination type."; 985 } 986 leaf bit-stuffing { 987 type boolean; 988 description 989 "Bit stuffing enabled/disabled."; 990 } 991 } 993 grouping l0-path-constraints { 994 description 995 "Global named path constraints configuration 996 grouping for Layer0 (WSON or Flexi-Grid) paths."; 997 leaf wavelength-assignment { 998 type identityref { 999 base wavelength-assignment; 1000 } 1001 description "Wavelength Allocation Method"; 1002 } 1003 } 1005 } 1006 1008 Figure 1 1010 4. Acknowledgements 1012 To be added if any. 1014 5. Contributors 1016 Gabriele Galimberti 1017 Cisco 1019 Email: ggalimbe@cisco.com 1021 Enrico Griseri 1022 Nokia 1024 Email: Enrico.Griseri@nokia.com 1026 Aihua Guo 1027 Futurewei 1029 Email: aihuaguo@futurewei.com 1031 6. IANA Considerations 1033 This memo includes no request to IANA. 1035 All drafts are required to have an IANA considerations section (see 1036 Guidelines for Writing an IANA Considerations Section in RFCs 1037 [RFC5226] for a guide). If the draft does not require IANA to do 1038 anything, the section contains an explicit statement that this is the 1039 case (as above). If there are no requirements for IANA, the section 1040 will be removed during conversion into an RFC by the RFC Editor. 1042 7. Security Considerations 1044 All drafts are required to have a security considerations section. 1045 See RFC 3552 [RFC3552] for a guide. 1047 8. References 1049 8.1. Normative References 1051 [I-D.ietf-ccamp-layer0-types] 1052 Zheng, H., Lee, Y., Guo, A., Lopez, V., and D. King, "A 1053 YANG Data Model for Layer 0 Types", Work in Progress, 1054 Internet-Draft, draft-ietf-ccamp-layer0-types-09, 29 1055 December 2020, . 1058 [I-D.ietf-ccamp-optical-impairment-topology-yang] 1059 Lee, Y., Auge, L., Lopez, V., Galimberti, G., and D. 1060 Beller, "A Yang Data Model for Optical Impairment-aware 1061 Topology", Work in Progress, Internet-Draft, draft-ietf- 1062 ccamp-optical-impairment-topology-yang-05, 2 November 1063 2020, . 1066 [I-D.ietf-ccamp-wson-yang] 1067 Zheng, H., Lee, Y., Guo, A., Lopez, V., and D. King, "A 1068 YANG Data Model for WSON (Wavelength Switched Optical 1069 Networks)", Work in Progress, Internet-Draft, draft-ietf- 1070 ccamp-wson-yang-28, 29 December 2020, 1071 . 1074 [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate 1075 Requirement Levels", BCP 14, RFC 2119, 1076 DOI 10.17487/RFC2119, March 1997, 1077 . 1079 [RFC6241] Enns, R., Ed., Bjorklund, M., Ed., Schoenwaelder, J., Ed., 1080 and A. Bierman, Ed., "Network Configuration Protocol 1081 (NETCONF)", RFC 6241, DOI 10.17487/RFC6241, June 2011, 1082 . 1084 [RFC7950] Bjorklund, M., Ed., "The YANG 1.1 Data Modeling Language", 1085 RFC 7950, DOI 10.17487/RFC7950, August 2016, 1086 . 1088 [RFC8795] Liu, X., Bryskin, I., Beeram, V., Saad, T., Shah, H., and 1089 O. Gonzalez de Dios, "YANG Data Model for Traffic 1090 Engineering (TE) Topologies", RFC 8795, 1091 DOI 10.17487/RFC8795, August 2020, 1092 . 1094 8.2. Informative References 1096 [I-D.ietf-ccamp-dwdm-if-param-yang] 1097 Galimberti, G., Kunze, R., Burk, A., Hiremagalur, D., and 1098 G. Grammel, "A YANG model to manage the optical interface 1099 parameters for an external transponder in a WDM network", 1100 Work in Progress, Internet-Draft, draft-ietf-ccamp-dwdm- 1101 if-param-yang-05, 18 November 2020, 1102 . 1105 [RFC2629] Rose, M., "Writing I-Ds and RFCs using XML", RFC 2629, 1106 DOI 10.17487/RFC2629, June 1999, 1107 . 1109 [RFC3552] Rescorla, E. and B. Korver, "Guidelines for Writing RFC 1110 Text on Security Considerations", BCP 72, RFC 3552, 1111 DOI 10.17487/RFC3552, July 2003, 1112 . 1114 [RFC5226] Narten, T. and H. Alvestrand, "Guidelines for Writing an 1115 IANA Considerations Section in RFCs", RFC 5226, 1116 DOI 10.17487/RFC5226, May 2008, 1117 . 1119 Authors' Addresses 1121 Dieter Beller (editor) 1122 Nokia 1124 Email: Dieter.Beller@nokia.com 1126 Sergio Belotti (editor) 1127 Nokia 1129 Email: Sergio.Belotti@nokia.com 1131 Haomian Zheng 1132 Huawei 1134 Email: ZhengHaomian@huawei.com 1136 Italo Busi 1137 Huawei 1139 Email: Italo.Busi@huawei.com 1140 Esther Le Rouzic 1141 Orange 1143 Email: esther.lerouzic@orange.com