idnits 2.17.1 draft-ietf-ccamp-mw-yang-10.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 (October 03, 2018) is 2032 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) No issues found here. Summary: 0 errors (**), 0 flaws (~~), 2 warnings (==), 1 comment (--). Run idnits with the --verbose option for more detailed information about the items above. -------------------------------------------------------------------------------- 2 CCAMP Working Group J. Ahlberg 3 Internet-Draft Ericsson AB 4 Intended status: Standards Track M. Ye 5 Expires: April 6, 2019 Huawei Technologies 6 X. Li 7 NEC Laboratories Europe 8 D. Spreafico 9 Nokia - IT 10 M. Vaupotic 11 Aviat Networks 12 October 03, 2018 14 A YANG Data Model for Microwave Radio Link 15 draft-ietf-ccamp-mw-yang-10 17 Abstract 19 This document defines a YANG data model for control and management of 20 the radio link interfaces, and their connectivity to packet 21 (typically Ethernet) interfaces in a microwave/millimeter wave node. 22 The data nodes for management of the interface protection 23 functionality is broken out into a separate and generic YANG data 24 model in order to make it available also for other interface types. 26 RFC Ed. Note 28 // RFC Ed.: replace all XXXX throughout the document with actual RFC 29 numbers and remove this note 31 Status of This Memo 33 This Internet-Draft is submitted in full conformance with the 34 provisions of BCP 78 and BCP 79. 36 Internet-Drafts are working documents of the Internet Engineering 37 Task Force (IETF). Note that other groups may also distribute 38 working documents as Internet-Drafts. The list of current Internet- 39 Drafts is at https://datatracker.ietf.org/drafts/current/. 41 Internet-Drafts are draft documents valid for a maximum of six months 42 and may be updated, replaced, or obsoleted by other documents at any 43 time. It is inappropriate to use Internet-Drafts as reference 44 material or to cite them other than as "work in progress." 46 This Internet-Draft will expire on April 6, 2019. 48 Copyright Notice 50 Copyright (c) 2018 IETF Trust and the persons identified as the 51 document authors. All rights reserved. 53 This document is subject to BCP 78 and the IETF Trust's Legal 54 Provisions Relating to IETF Documents 55 (https://trustee.ietf.org/license-info) in effect on the date of 56 publication of this document. Please review these documents 57 carefully, as they describe your rights and restrictions with respect 58 to this document. Code Components extracted from this document must 59 include Simplified BSD License text as described in Section 4.e of 60 the Trust Legal Provisions and are provided without warranty as 61 described in the Simplified BSD License. 63 Table of Contents 65 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 2 66 1.1. Terminology and Definitions . . . . . . . . . . . . . . . 3 67 1.2. Tree Structure . . . . . . . . . . . . . . . . . . . . . 4 68 2. Requirements Language . . . . . . . . . . . . . . . . . . . . 4 69 3. Microwave Radio Link YANG Data Model . . . . . . . . . . . . 4 70 3.1. YANG Tree . . . . . . . . . . . . . . . . . . . . . . . . 4 71 3.2. Explanation of the Microwave Data Model . . . . . . . . . 7 72 4. Microwave Radio Link YANG Module . . . . . . . . . . . . . . 7 73 5. Interface Protection YANG Module . . . . . . . . . . . . . . 26 74 6. Microwave Types YANG Module . . . . . . . . . . . . . . . . . 32 75 7. Security Considerations . . . . . . . . . . . . . . . . . . . 39 76 8. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 41 77 9. References . . . . . . . . . . . . . . . . . . . . . . . . . 42 78 9.1. Normative References . . . . . . . . . . . . . . . . . . 42 79 9.2. Informative References . . . . . . . . . . . . . . . . . 43 80 Appendix A. Example: 1+0 and 2+0 configuration instances . . . . 45 81 A.1. 1+0 instance . . . . . . . . . . . . . . . . . . . . . . 45 82 A.2. 2+0 instance . . . . . . . . . . . . . . . . . . . . . . 46 83 A.3. 2+0 XPIC instance . . . . . . . . . . . . . . . . . . . . 48 84 Appendix B. Contributors . . . . . . . . . . . . . . . . . . . . 50 85 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 50 87 1. Introduction 89 This document defines a YANG data model for management and control of 90 the radio link interface(s) and the relationship to packet (typically 91 Ethernet) and/or TDM interfaces in a microwave/millimeter wave node. 92 ETSI EN 302 217 series defines the characteristics and requirements 93 of microwave/millimeter wave equipment and antennas. Especially ETSI 94 EN 302 217-2 [EN302217-2] specifies the essential parameters for the 95 systems operating from 1.4GHz to 86GHz. The data model includes 96 configuration and state data according to the new Network Management 97 Datastore Architecture [RFC8342]. 99 The design of the data model follows the framework for management and 100 control of microwave and millimeter wave interface parameters defined 101 in [I-D.ietf-ccamp-microwave-framework]. This framework identifies 102 the need and the scope of the YANG data model, the use cases and 103 requirements that the model needs to support. Moreover, it provides 104 a detailed gap analysis to identify the missing parameters and 105 functionalities of the existing and established models to support the 106 specified use cases and requirements, and based on that recommends 107 how the gaps should be filled with the development of the new model. 108 According to the conclusion of the gap analysis, the structure of the 109 data model is based on the structure defined in 110 [I-D.ahlberg-ccamp-microwave-radio-link] and it augments [RFC8343] to 111 align with the same structure for management of the packet 112 interfaces. More specifically, the model will include interface 113 layering to manage the capacity provided by a radio link terminal for 114 the associated Ethernet and TDM interfaces, using the principles for 115 interface layering described in [RFC8343] as a basis. 117 The data nodes for management of the interface protection 118 functionality is broken out into a separate and generic YANG data 119 module in order to make it available also for other interface types. 121 The designed YANG data model uses established microwave equipment and 122 radio standards, such as ETSI EN 302 217-2, and the IETF: Radio Link 123 Model [I-D.ahlberg-ccamp-microwave-radio-link] and the ONF: Microwave 124 Modeling [ONF-model] as the basis for the definition of the detailed 125 leafs/parameters, and proposes new ones to cover identified gaps 126 which are analyzed in [I-D.ietf-ccamp-microwave-framework]. 128 1.1. Terminology and Definitions 130 The following terms are used in this document: 132 Carrier Termination (CT) is an interface for the capacity provided 133 over the air by a single carrier. It is typically defined by its 134 transmitting and receiving frequencies. 136 Radio Link Terminal (RLT) is an interface providing packet capacity 137 and/or TDM capacity to the associated Ethernet and/or TDM interfaces 138 in a node and used for setting up a transport service over a 139 microwave/millimeter wave link. 141 The following acronyms are used in this document: 143 ACM Adaptive Coding Modulation 144 ATPC Automatic Transmit Power Control 146 BPSK Binary Phase-Shift Keying 148 CM Coding Modulation 150 CT Carrier Termination 152 RLT Radio Link Terminal 154 RTPC Remote Transmit Power Control 156 XPIC Cross Polarization Interference Cancellation 158 MIMO Multiple-Input Multiple-Output 160 QAM Quadrature Amplitude Modulation 162 QPSK Quadrature Phase-Shift Keying 164 1.2. Tree Structure 166 A simplified graphical representation of the data model is used in 167 chapter 3.1 of this this document. The meaning of the symbols in 168 these diagrams is defined in [RFC8340]. 170 2. Requirements Language 172 The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", 173 "SHOULD", "SHOULD NOT", "RECOMMENDED", "NOT RECOMMENDED", "MAY", and 174 "OPTIONAL" in this document are to be interpreted as described in BCP 175 14 [RFC2119] [RFC8174] when, and only when, they appear in all 176 capitals, as shown here. 178 3. Microwave Radio Link YANG Data Model 180 3.1. YANG Tree 182 module: ietf-microwave-radio-link 183 +--rw radio-link-protection-groups 184 | +--rw protection-group* [name] 185 | +--rw name string 186 | +--rw protection-architecture-type? identityref 187 | +--rw members* if:interface-ref 188 | +--rw operation-type? enumeration 189 | +--rw working-entity* if:interface-ref 190 | +--rw revertive-wait-to-restore? uint16 191 | +--rw hold-off-timer? uint16 192 | +--ro status? identityref 193 | +---x manual-switch-working 194 | +---x manual-switch-protection 195 | +---x forced-switch 196 | +---x lockout-of-protection 197 | +---x freeze 198 | +---x exercise 199 | +---x clear 200 +--rw xpic-pairs {xpic}? 201 | +--rw xpic-pair* [name] 202 | +--rw name string 203 | +--rw enabled? boolean 204 | +--rw members* if:interface-ref 205 +--rw mimo-groups {mimo}? 206 +--rw mimo-group* [name] 207 +--rw name string 208 +--rw enabled? boolean 209 +--rw members* if:interface-ref 210 augment /if:interfaces/if:interface: 211 +--rw id? string 212 +--rw mode identityref 213 +--rw carrier-terminations* if:interface-ref 214 +--rw rlp-groups* 215 | -> /radio-link-protection-groups/protection-group/name 216 +--rw xpic-pairs* -> /xpic-pairs/xpic-pair/name 217 | {xpic}? 218 +--rw mimo-groups* -> /mimo-groups/mimo-group/name 219 | {mimo}? 220 +--rw tdm-connections* [tdm-type] {tdm}? 221 +--rw tdm-type identityref 222 +--rw tdm-connections uint16 223 augment /if:interfaces/if:interface: 224 +--rw carrier-id? string 225 +--rw tx-enabled? boolean 226 +--ro tx-oper-status? enumeration 227 +--rw tx-frequency uint32 228 +--rw (freq-or-distance) 229 | +--:(rx-frequency) 230 | | +--rw rx-frequency? uint32 231 | +--:(duplex-distance) 232 | +--rw duplex-distance? int32 233 +--ro actual-rx-frequency? uint32 234 +--ro actual-duplex-distance? uint32 235 +--rw channel-separation uint32 236 +--rw polarization? enumeration 237 +--rw (power-mode) 238 | +--:(rtpc) 239 | | +--rw rtpc 240 | | +--rw maximum-nominal-power power 241 | +--:(atpc) 242 | +--rw atpc 243 | +--rw maximum-nominal-power power 244 | +--rw atpc-lower-threshold power 245 | +--rw atpc-upper-threshold power 246 +--ro actual-transmitted-level? power 247 +--ro actual-received-level? power 248 +--rw (coding-modulation-mode) 249 | +--:(single) 250 | | +--rw single 251 | | +--rw selected-cm identityref 252 | +--:(adaptive) 253 | +--rw adaptive 254 | +--rw selected-min-acm identityref 255 | +--rw selected-max-acm identityref 256 +--ro actual-tx-cm? identityref 257 +--ro actual-snir? decimal64 258 +--ro actual-xpi? decimal64 {xpic}? 259 +--rw ct-performance-thresholds 260 | +--rw received-level-alarm-threshold? power 261 | +--rw transmitted-level-alarm-threshold? power 262 | +--rw ber-alarm-threshold? enumeration 263 +--rw if-loop? enumeration 264 +--rw rf-loop? enumeration 265 +--ro capabilities 266 | +--ro min-tx-frequency? uint32 267 | +--ro max-tx-frequency? uint32 268 | +--ro min-rx-frequency? uint32 269 | +--ro max-rx-frequency? uint32 270 | +--ro minimum-power? power 271 | +--ro maximum-available-power? power 272 | +--ro available-min-acm? identityref 273 | +--ro available-max-acm? identityref 274 +--ro error-performance-statistics 275 | +--ro bbe? yang:counter32 276 | +--ro es? yang:counter32 277 | +--ro ses? yang:counter32 278 | +--ro uas? yang:counter32 279 +--ro radio-performance-statistics 280 +--ro min-rltm? power 281 +--ro max-rltm? power 282 +--ro min-tltm? power 283 +--ro max-tltm? power 285 3.2. Explanation of the Microwave Data Model 287 The leafs in the Interface Management Module augmented by Radio Link 288 Terminal (RLT) and Carrier Termination (CT) are not always 289 applicable. 291 "/interfaces/interface/enabled" is not applicable for RLT. Enable 292 and disable of an interface is done in the constituent CTs. 294 The packet related measurements "in-octets", "in-unicast-pkts", "in- 295 broadcast-pkts", "in-multicast-pkts", "in-discards", "in-errors", 296 "in-unknown-protos", "out-octets", "out-unicast-pkts", "out- 297 broadcast-pkts", "out-multicast-pkts", "out-discards", "out-errors" 298 are not within the scope of the microwave radio link domain and 299 therefore not applicable for RLT and CT. 301 4. Microwave Radio Link YANG Module 303 This module imports typedefs and modules from [RFC6991], [RFC8343] 304 and [RFC7224], and it references [TR102311], [EN302217-1], 305 [EN301129], and [G.826]. 307 file "ietf-microwave-radio-link@2018-10-03.yang" 309 module ietf-microwave-radio-link { 310 yang-version 1.1; 311 namespace "urn:ietf:params:xml:ns:yang:ietf-microwave-radio-link"; 312 prefix mrl; 314 import ietf-yang-types { 315 prefix yang; 316 reference "RFC 6991"; 317 } 319 import ietf-interfaces { 320 prefix if; 321 reference "RFC 8343"; 322 } 324 import ietf-interface-protection { 325 prefix ifprot; 326 reference "RFC XXXX"; 327 } 329 import ietf-microwave-types { 330 prefix mw-types; 331 reference "RFC XXXX"; 333 } 335 organization 336 "Internet Engineering Task Force (IETF) CCAMP WG"; 338 contact 339 "WG List: 341 ID-draft editors: 342 // RFC Ed.: replace ID-draft editors with Editors and remove 343 // this note 344 Jonas Ahlberg (jonas.ahlberg@ericsson.com); 345 Min Ye (amy.yemin@huawei.com); 346 Xi Li (Xi.Li@neclab.eu); 347 Daniela Spreafico (daniela.spreafico@nokia.com) 348 Marko Vaupotic (Marko.Vaupotic@aviatnet.com)"; 350 description 351 "This is a module for the entities in 352 a generic microwave system. 354 Copyright (c) 2018 IETF Trust and the persons identified as 355 authors of the code. All rights reserved. 356 Redistribution and use in source and binary forms, with or 357 without modification, is permitted pursuant to, and subject 358 to the license terms contained in, the Simplified BSD License 359 set forth in Section 4.c of the IETF Trust's Legal Provisions 360 Relating to IETF Documents 361 (http://trustee.ietf.org/license-info). 363 This version of this YANG module is part of RFC XXXX; see 364 the RFC itself for full legal notices. 366 Copyright (c) 2018 IETF Trust and the persons identified as 367 authors of the code. All rights reserved."; 369 revision 2018-10-03 { 370 description "Initial revision."; 371 reference "RFC XXXX: A YANG Data Model for Microwave Radio Link"; 372 } 374 /* 375 * Features 376 */ 378 feature xpic { 379 description 380 "Indicates that the device supports XPIC."; 382 reference "ETSI TR 102 311"; 383 } 385 feature mimo { 386 description 387 "Indicates that the device supports MIMO."; 388 reference "ETSI TR 102 311"; 389 } 391 feature tdm { 392 description 393 "Indicates that the device supports TDM."; 394 } 396 /* 397 * Typedefs 398 */ 400 typedef power { 401 type decimal64 { 402 fraction-digits 1; 403 } 404 description 405 "Type used for power values, selected and measured."; 406 } 408 /* 409 * Radio Link Terminal (RLT) 410 */ 412 augment "/if:interfaces/if:interface" { 413 when "derived-from-or-self(if:type," 414 + "'mw-types:radio-link-terminal')"; 415 description 416 "Addition of data nodes for radio link terminal to 417 the standard Interface data model, for interfaces of 418 the type 'radio-link-terminal'."; 420 leaf id { 421 type string; 422 description 423 "Descriptive identity of the radio link terminal used by 424 far-end RLT to check that it's connected to the correct 425 near-end RLT. Does not need to be configured if this check 426 is not used."; 427 } 429 leaf mode { 430 type identityref { 431 base mw-types:rlt-mode; 432 } 433 mandatory true; 434 description 435 "A description of the mode in which the radio link 436 terminal is configured. The format is X plus Y. 437 X represent the number of bonded carrier terminations. 438 Y represent the number of protecting carrier 439 terminations."; 440 } 442 leaf-list carrier-terminations { 443 type if:interface-ref; 444 must "derived-from-or-self(/if:interfaces/if:interface" 445 + "[if:name = current()]" 446 + "/if:type, 'mw-types:carrier-termination')" { 447 description 448 "The type of interface must be 449 'carrier-termination'."; 450 } 451 min-elements 1; 452 description 453 "A list of references to carrier terminations 454 included in the radio link terminal."; 455 } 457 leaf-list rlp-groups { 458 type leafref { 459 path "/mrl:radio-link-protection-groups/" 460 + "mrl:protection-group/mrl:name"; 461 } 462 description 463 "A list of references to the carrier termination 464 groups configured for radio link protection in this 465 radio link terminal."; 466 } 468 leaf-list xpic-pairs { 469 if-feature xpic; 470 type leafref { 471 path "/mrl:xpic-pairs/mrl:xpic-pair/mrl:name"; 472 } 474 description 475 "A list of references to the XPIC pairs used in this 476 radio link terminal. One pair can be used by two 477 terminals."; 479 reference "ETSI TR 102 311"; 480 } 482 leaf-list mimo-groups { 483 if-feature mimo; 484 type leafref { 485 path "/mrl:mimo-groups/mrl:mimo-group/mrl:name"; 486 } 487 description 488 "A reference to the MIMO group used in this 489 radio link terminal. One group can be used by more 490 than one terminal."; 491 reference "ETSI TR 102 311"; 492 } 494 list tdm-connections { 495 if-feature tdm; 496 key "tdm-type"; 497 description 498 "A list stating the number of active TDM connections 499 of a specified tdm-type that is configured to be 500 supported by the RLT."; 501 leaf tdm-type { 502 type identityref { 503 base mw-types:tdm-type; 504 } 505 description 506 "The type of TDM connection, which also indicates 507 the supported capacity."; 508 } 509 leaf tdm-connections { 510 type uint16; 511 mandatory true; 512 description 513 "Number of connections of the specified type."; 514 } 515 } 516 } 518 /* 519 * Carrier Termination 520 */ 522 augment "/if:interfaces/if:interface" { 523 when "derived-from-or-self(if:type," 524 + "'mw-types:carrier-termination')"; 526 description 527 "Addition of data nodes for carrier termination to 528 the standard Interface data model, for interfaces 529 of the type 'carrier-termination'."; 531 leaf carrier-id { 532 type string; 533 default "A"; 534 description 535 "ID of the carrier. (e.g. A, B, C or D) 536 Used in XPIC & MIMO configurations to check that 537 the carrier termination is connected to the correct 538 far-end carrier termination. Should be the same 539 carrier ID on both sides of the hop. 540 Defaulted when not MIMO or XPIC."; 541 } 543 leaf tx-enabled { 544 type boolean; 545 default "false"; 546 description 547 "Disables (false) or enables (true) the transmitter. 548 Only applicable when the interface is enabled 549 (interface:enabled = true) otherwise it's always 550 disabled."; 551 } 553 leaf tx-oper-status { 554 type enumeration { 555 enum "off" { 556 description "Transmitter is off."; 557 } 558 enum "on" { 559 description "Transmitter is on."; 560 } 561 enum "standby" { 562 description "Transmitter is in standby."; 563 } 564 } 565 config false; 566 description 567 "Shows the operative status of the transmitter."; 568 } 570 leaf tx-frequency { 571 type uint32; 572 units "kHz"; 573 mandatory true; 574 description 575 "Selected transmitter frequency."; 576 } 578 choice freq-or-distance { 579 leaf rx-frequency { 580 type uint32; 581 units "kHz"; 582 description 583 "Selected receiver frequency."; 584 } 585 leaf duplex-distance { 586 type int32; 587 units "kHz"; 588 description 589 "Distance between transmitter and receiver frequencies."; 590 } 591 mandatory true; 592 description 593 "A choice to configure rx-frequency directly or by computing 594 it as tx-frequency subtracted with the configured 595 duplex-distance." ; 596 } 598 leaf actual-rx-frequency { 599 type uint32; 600 units "kHz"; 601 config false; 602 description 603 "Computed receiver frequency."; 604 } 606 leaf actual-duplex-distance { 607 type uint32; 608 units "kHz"; 609 config false; 610 description 611 "Computed distance between Tx & Rx frequencies."; 612 } 614 leaf channel-separation { 615 type uint32; 616 units "kHz"; 617 mandatory true; 618 description 619 "The amount of bandwidth allocated to a carrier. The distance 620 between adjacent channels in a radio frequency channels 621 arrangement"; 622 reference "ETSI EN 302 217-1"; 624 } 626 leaf polarization { 627 type enumeration { 628 enum "horizontal" { 629 description "Horizontal polarization."; 630 } 631 enum "vertical" { 632 description "Vertical polarization."; 633 } 634 enum "not-specified" { 635 description "Polarization not specified."; 636 } 637 } 639 default "not-specified"; 640 description 641 "Polarization - A textual description for info only."; 642 } 644 choice power-mode { 645 container rtpc { 646 description 647 "Remote Transmit Power Control (RTPC)."; 648 reference "ETSI EN 302 217-1"; 649 leaf maximum-nominal-power { 650 type power { 651 range "-99..99"; 652 } 653 units "dBm"; 654 mandatory true; 655 description 656 "Selected output power."; 657 reference "ETSI EN 302 217-1"; 658 } 659 } 660 container atpc { 661 description 662 "Automatic Transmit Power Control (ATPC)."; 663 reference "ETSI EN 302 217-1"; 665 leaf maximum-nominal-power { 666 type power { 667 range "-99..99"; 668 } 669 units "dBm"; 670 mandatory true; 671 description 672 "Selected maximum output power. Minimum output 673 power is the same as the system capability, 674 available-min-output-power."; 675 reference "ETSI EN 302 217-1"; 676 } 678 leaf atpc-lower-threshold { 679 type power { 680 range "-99..-30"; 681 } 682 units "dBm"; 683 must "current() <= ../atpc-upper-threshold"; 684 mandatory true; 685 description 686 "The lower threshold for the input power at far-end 687 used in the ATPC mode."; 688 reference "ETSI EN 302 217-1"; 689 } 691 leaf atpc-upper-threshold { 692 type power { 693 range "-99..-30"; 694 } 695 units "dBm"; 696 mandatory true; 697 description 698 "The upper threshold for the input power at far-end 699 used in the ATPC mode."; 700 reference "ETSI EN 302 217-1"; 701 } 702 } 703 mandatory true; 704 description 705 "A choice of Remote Transmit Power Control (RTPC) 706 or Automatic Transmit Power Control (ATPC)."; 707 } 709 leaf actual-transmitted-level { 710 type power { 711 range "-99..99"; 712 } 713 units "dBm"; 714 config false; 715 description 716 "Actual transmitted power level (0.1 dBm resolution)."; 717 reference "ETSI EN 301 129"; 718 } 719 leaf actual-received-level { 720 type power { 721 range "-99..-20"; 722 } 723 units "dBm"; 724 config false; 725 description 726 "Actual received power level (0.1 dBm resolution)."; 727 reference "ETSI EN 301 129"; 728 } 730 choice coding-modulation-mode { 731 container single { 732 description "A single modulation order only."; 733 reference "ETSI EN 302 217-1"; 735 leaf selected-cm { 736 type identityref { 737 base mw-types:coding-modulation; 738 } 739 mandatory true; 740 description 741 "Selected the single coding/modulation."; 742 } 743 } 745 container adaptive { 746 description "Adaptive coding/modulation."; 747 reference "ETSI EN 302 217-1"; 749 leaf selected-min-acm { 750 type identityref { 751 base mw-types:coding-modulation; 752 } 753 mandatory true; 754 description 755 "Selected minimum coding/modulation. 756 Adaptive coding/modulation shall not go 757 below this value."; 758 } 760 leaf selected-max-acm { 761 type identityref { 762 base mw-types:coding-modulation; 763 } 764 mandatory true; 765 description 766 "Selected maximum coding/modulation. 768 Adaptive coding/modulation shall not go 769 above this value."; 770 } 771 } 772 mandatory true; 773 description 774 "A selection of single or 775 adaptive coding/modulation mode."; 776 } 778 leaf actual-tx-cm { 779 type identityref { 780 base mw-types:coding-modulation; 781 } 782 config false; 783 description 784 "Actual coding/modulation in transmitting direction."; 785 } 787 leaf actual-snir { 788 type decimal64 { 789 fraction-digits 1; 790 range "0..99"; 791 } 792 units "dB"; 793 config false; 794 description 795 "Actual signal to noise plus interference ratio. 796 (0.1 dB resolution)."; 797 } 799 leaf actual-xpi { 800 if-feature xpic; 801 type decimal64 { 802 fraction-digits 1; 803 range "0..99"; 804 } 805 units "dB"; 806 config false; 807 description 808 "The actual carrier to cross-polar interference. 809 Only valid if XPIC is enabled. (0.1 dB resolution)."; 810 reference "ETSI TR 102 311"; 811 } 813 container ct-performance-thresholds { 814 description 815 "Specification of thresholds for when alarms should 816 be sent and cleared for various performance counters."; 818 leaf received-level-alarm-threshold { 819 type power { 820 range "-99..-30"; 821 } 822 units "dBm"; 823 default "-99"; 824 description 825 "An alarm is sent when the received power level is 826 below the specified threshold."; 827 reference "ETSI EN 301 129"; 828 } 830 leaf transmitted-level-alarm-threshold { 831 type power { 832 range "-99..99"; 833 } 834 units "dBm"; 835 default "-99"; 836 description 837 "An alarm is sent when the transmitted power level 838 is below the specified threshold."; 839 reference "ETSI EN 301 129"; 840 } 842 leaf ber-alarm-threshold { 843 type enumeration { 844 enum "1e-9" { 845 description "Threshold at 1e-9 (10^-9)."; 846 } 847 enum "1e-8" { 848 description "Threshold at 1e-8 (10^-8)."; 849 } 850 enum "1e-7" { 851 description "Threshold at 1e-7 (10^-7)."; 852 } 853 enum "1e-6" { 854 description "Threshold at 1e-6 (10^-6)."; 855 } 856 enum "1e-5" { 857 description "Threshold at 1e-5 (10^-5)."; 858 } 859 enum "1e-4" { 860 description "Threshold at 1e-4 (10^-4)."; 861 } 862 enum "1e-3" { 863 description "Threshold at 1e-3 (10^-3)."; 865 } 866 enum "1e-2" { 867 description "Threshold at 1e-2 (10^-2)."; 868 } 869 enum "1e-1" { 870 description "Threshold at 1e-1 (10^-1)."; 871 } 872 } 873 default "1e-6"; 874 description 875 "Specification of at which BER an alarm should 876 be raised."; 877 reference "ETSI EN 302 217-1"; 878 } 879 } 881 leaf if-loop { 882 type enumeration { 883 enum disabled { 884 description "Disables the IF Loop."; 885 } 886 enum client { 887 description 888 "Loops the signal back to the client side."; 889 } 890 enum radio { 891 description 892 "Loops the signal back to the radio side."; 893 } 894 } 895 default "disabled"; 896 description 897 "Enable (client/radio) or disable (disabled) 898 the IF loop, which loops the signal back to 899 the client side or the radio side."; 900 } 902 leaf rf-loop { 903 type enumeration { 904 enum disabled { 905 description "Disables the RF Loop."; 906 } 907 enum client { 908 description 909 "Loops the signal back to the client side."; 910 } 911 enum radio { 912 description 913 "Loops the signal back to the radio side."; 914 } 915 } 916 default "disabled"; 917 description 918 "Enable (client/radio) or disable (disabled) 919 the RF loop, which loops the signal back to 920 the client side or the radio side."; 921 } 923 container capabilities { 924 config false; 925 description 926 "Capabilities of the installed equipment and 927 some selected configurations."; 929 leaf min-tx-frequency { 930 type uint32; 931 units "kHz"; 932 description 933 "Minimum Tx frequency possible to use."; 934 } 936 leaf max-tx-frequency { 937 type uint32; 938 units "kHz"; 939 description 940 "Maximum Tx frequency possible to use."; 941 } 943 leaf min-rx-frequency { 944 type uint32; 945 units "kHz"; 946 description 947 "Minimum Rx frequency possible to use."; 948 } 950 leaf max-rx-frequency { 951 type uint32; 952 units "kHz"; 953 description 954 "Maximum Tx frequency possible to use."; 955 } 957 leaf minimum-power { 958 type power; 959 units "dBm"; 960 description 961 "The minimum output power supported."; 962 reference "ETSI EN 302 217-1"; 963 } 965 leaf maximum-available-power { 966 type power; 967 units "dBm"; 968 description 969 "The maximum output power supported."; 970 reference "ETSI EN 302 217-1"; 971 } 973 leaf available-min-acm { 974 type identityref { 975 base mw-types:coding-modulation; 976 } 977 description 978 "Minimum coding-modulation possible to use."; 979 } 981 leaf available-max-acm { 982 type identityref { 983 base mw-types:coding-modulation; 984 } 985 description 986 "Maximum coding-modulation possible to use."; 987 } 988 } 990 container error-performance-statistics { 991 config false; 992 description 993 "ITU-T G.826 error performance statistics relevant for 994 a microwave/millimeter wave carrier."; 996 leaf bbe { 997 type yang:counter32; 998 units "number of block errors"; 999 description 1000 "Number of Background Block Errors (BBE) during the 1001 interval. A BBE is an errored block not occurring as 1002 part of an SES."; 1003 reference "ITU-T G.826"; 1004 } 1006 leaf es { 1007 type yang:counter32; 1008 units "seconds"; 1009 description 1010 "Number of Errored Seconds (ES) since last reset. 1011 An ES is a one-second period with one or more errored 1012 blocks or at least one defect."; 1013 reference "ITU-T G.826"; 1014 } 1016 leaf ses { 1017 type yang:counter32; 1018 units "seconds"; 1019 description 1020 "Number of Severely Errored Seconds (SES) during the 1021 interval. SES is a one-second period which contains 1022 equal or more than 30% errored blocks or at least 1023 one defect. SES is a subset of ES."; 1024 reference "ITU-T G.826"; 1025 } 1027 leaf uas { 1028 type yang:counter32; 1029 units "seconds"; 1030 description 1031 "Number of Unavailable Seconds (UAS), that is, the 1032 total time that the node has been unavailable during 1033 a fixed measurement interval."; 1034 reference "ITU-T G.826"; 1035 } 1036 } 1038 container radio-performance-statistics { 1039 config false; 1040 description 1041 "ETSI EN 301 129 radio physical interface statistics relevant 1042 for a carrier termination."; 1044 leaf min-rltm { 1045 type power { 1046 range "-99..-20"; 1047 } 1048 units "dBm"; 1049 description 1050 "Minimum received power level since last reset."; 1051 reference "ETSI EN 301 129"; 1052 } 1054 leaf max-rltm { 1055 type power { 1056 range "-99..-20"; 1058 } 1059 units "dBm"; 1060 description 1061 "Maximum received power level since last reset."; 1062 reference "ETSI EN 301 129"; 1063 } 1065 leaf min-tltm { 1066 type power { 1067 range "-99..99"; 1068 } 1069 units "dBm"; 1070 description 1071 "Minimum transmitted power level since last reset."; 1072 reference "ETSI EN 301 129"; 1073 } 1075 leaf max-tltm { 1076 type power { 1077 range "-99..99"; 1078 } 1079 units "dBm"; 1080 description 1081 "Maximum transmitted power level since last reset."; 1082 reference "ETSI EN 301 129"; 1083 } 1084 } 1085 } 1087 /* 1088 * Radio Link Protection Groups 1089 */ 1091 container radio-link-protection-groups { 1092 description 1093 "Configuration of radio link protected groups (1+1) of 1094 carrier terminations in a radio link. More than one 1095 protected group per radio-link-terminal is allowed."; 1097 uses ifprot:protection-groups { 1099 refine protection-group/members { 1100 must "derived-from-or-self(/if:interfaces/if:interface" 1101 + "[if:name = current()]" 1102 + "/if:type, 'mw-types:carrier-termination')" { 1103 description 1104 "The type of a protection member must be 1105 'carrier-termination'."; 1107 } 1108 } 1110 refine protection-group/working-entity { 1111 must "derived-from-or-self(/if:interfaces/if:interface" 1112 + "[if:name = current()]" 1113 + "/if:type, 'mw-types:carrier-termination')" { 1114 description 1115 "The type of a working-entity must be 1116 'carrier-termination'."; 1117 } 1118 } 1119 } 1120 } 1122 /* 1123 * XPIC & MIMO groups - Configuration data nodes 1124 */ 1126 container xpic-pairs { 1127 if-feature xpic; 1128 description 1129 "Configuration of carrier termination pairs 1130 for operation in XPIC mode."; 1131 reference "ETSI TR 102 311"; 1133 list xpic-pair { 1134 key "name"; 1135 description 1136 "List of carrier termination pairs in XPIC mode."; 1138 leaf name { 1139 type string; 1140 description 1141 "Name used for identification of the XPIC pair."; 1142 } 1144 leaf enabled { 1145 type boolean; 1146 default "false"; 1147 description 1148 "Enable(true)/disable(false) XPIC"; 1149 } 1151 leaf-list members { 1152 type if:interface-ref; 1153 must "derived-from-or-self(/if:interfaces/if:interface" 1154 + "[if:name = current()]" 1155 + "/if:type, 'mw-types:carrier-termination')" { 1156 description 1157 "The type of a member must be 'carrier-termination'."; 1158 } 1159 min-elements 2; 1160 max-elements 2; 1161 description 1162 "Association to XPIC pairs used in the radio link 1163 terminal."; 1164 } 1165 } 1166 } 1168 container mimo-groups { 1169 if-feature mimo; 1170 description 1171 "Configuration of carrier terminations 1172 for operation in MIMO mode."; 1173 reference "ETSI TR 102 311"; 1175 list mimo-group { 1176 key "name"; 1177 description 1178 "List of carrier terminations in MIMO mode."; 1180 leaf name { 1181 type string; 1182 description 1183 "Name used for identification of the MIMO group."; 1184 } 1186 leaf enabled { 1187 type boolean; 1188 default "false"; 1189 description 1190 "Enable(true)/disable(false) MIMO"; 1191 } 1193 leaf-list members { 1194 type if:interface-ref; 1195 must "derived-from-or-self(/if:interfaces/if:interface" 1196 + "[if:name = current()]" 1197 + "/if:type, 'mw-types:carrier-termination')" { 1198 description 1199 "The type of a member must be 'carrier-termination'."; 1200 } 1202 min-elements 2; 1203 description 1204 "Association to a MIMO group if used in the radio 1205 link terminal."; 1206 } 1207 } 1208 } 1209 } 1211 1213 5. Interface Protection YANG Module 1215 The data nodes for management of the interface protection 1216 functionality is broken out from the Microwave Radio Link Module into 1217 a separate and generic YANG data module in order to make it available 1218 also for other interface types. 1220 This module imports modules from [RFC8343], and it references 1221 [G.808.1]. 1223 file "ietf-interface-protection@2018-10-03.yang" 1225 module ietf-interface-protection { 1226 yang-version 1.1; 1227 namespace "urn:ietf:params:xml:ns:yang:ietf-interface-protection"; 1228 prefix ifprot; 1230 import ietf-interfaces { 1231 prefix if; 1232 reference "RFC8343"; 1233 } 1235 organization 1236 "Internet Engineering Task Force (IETF) CCAMP WG"; 1237 contact 1238 "WG List: 1240 ID-draft editors: 1241 Jonas Ahlberg (jonas.ahlberg@ericsson.com); 1242 Min Ye (amy.yemin@huawei.com); 1243 Xi Li (Xi.Li@neclab.eu); 1244 Daniela Spreafico (daniela.spreafico@nokia.com) 1245 Marko Vaupotic (Marko.Vaupotic@aviatnet.com)"; 1247 description 1248 "This is a module for the entities in 1249 a generic interface protection mechanism. 1251 Copyright (c) 2018 IETF Trust and the persons identified as 1252 authors of the code. All rights reserved. 1254 Redistribution and use in source and binary forms, with or 1255 without modification, is permitted pursuant to, and subject 1256 to the license terms contained in, the Simplified BSD License 1257 set forth in Section 4.c of the IETF Trust's Legal Provisions 1258 Relating to IETF Documents 1259 (http://trustee.ietf.org/license-info). 1261 This version of this YANG module is part of RFC XXXX; see 1262 the RFC itself for full legal notices. 1264 Copyright (c) 2018 IETF Trust and the persons identified as 1265 authors of the code. All rights reserved."; 1267 revision 2018-10-03 { 1268 description "Initial revision."; 1269 reference "RFC XXXX: A YANG Data Model for Microwave Radio Link"; 1270 } 1272 /* 1273 * Protection architecture type identities 1274 */ 1276 identity protection-architecture-type { 1277 description 1278 "protection architecture type"; 1279 reference "ITU-T G.808.1"; 1280 } 1282 identity one-plus-one-type { 1283 base protection-architecture-type; 1284 description 1285 "1+1, One interface protects 1286 another one interface."; 1287 reference "ITU-T G.808.1"; 1288 } 1290 identity one-to-n-type { 1291 base protection-architecture-type; 1292 description 1293 "1:N, One interface protects 1294 n other interfaces."; 1295 reference "ITU-T G.808.1"; 1296 } 1297 /* 1298 * Protection states identities 1299 */ 1301 identity protection-states { 1302 description 1303 "Identities describing the status of the protection, 1304 in a group of interfaces configured in 1305 a protection mode."; 1306 } 1308 identity unprotected { 1309 base protection-states; 1310 description "Not protected"; 1311 } 1313 identity protected { 1314 base protection-states; 1315 description "Protected"; 1316 } 1318 identity unable-to-protect { 1319 base protection-states; 1320 description "Unable to protect"; 1321 } 1323 /* 1324 * Protection Groups 1325 */ 1327 grouping protection-groups { 1328 description 1329 "Configuration of protected groups (1+1) of interfaces 1330 providing protection for each other. More than one protected 1331 group per higher-layer-interface is allowed."; 1333 list protection-group { 1334 key "name"; 1335 description 1336 "List of protected groups of interfaces 1337 in a higher-layer-interface."; 1339 leaf name { 1340 type string; 1341 description 1342 "Name used for identification of the protection group"; 1343 } 1344 leaf protection-architecture-type { 1345 type identityref { 1346 base protection-architecture-type; 1347 } 1348 default "ifprot:one-plus-one-type"; 1349 description 1350 "The type of protection architecture used, e.g. one 1351 interface protecting one or several other interfaces."; 1352 reference "ITU-T G.808.1"; 1353 } 1355 leaf-list members { 1356 type if:interface-ref; 1357 min-elements 2; 1358 description 1359 "Association to a group of interfaces configured for 1360 protection and used by a higher-layer-interface."; 1361 } 1363 leaf operation-type { 1364 type enumeration { 1365 enum "non-revertive" { 1366 description 1367 "In non revertive operation, the traffic does not 1368 return to the working interface if the switch requests 1369 are terminated."; 1370 reference "ITU-T G.808.1"; 1371 } 1372 enum "revertive" { 1373 description 1374 "In revertive operation, the traffic always 1375 returns to (or remains on) the working interface 1376 if the switch requests are terminated."; 1377 reference "ITU-T G.808.1"; 1378 } 1379 } 1380 default "non-revertive"; 1381 description 1382 "The type of protection operation, i.e. revertive 1383 or non-revertive operation."; 1384 } 1386 leaf-list working-entity { 1387 when "../operation-type = 'revertive'"; 1388 type if:interface-ref; 1389 min-elements 1; 1390 description 1391 "The interfaces over which the traffic normally should 1392 be transported over when there is no need to use the 1393 protecting interface."; 1394 } 1396 leaf revertive-wait-to-restore { 1397 when "../operation-type = 'revertive'"; 1398 type uint16; 1399 units "seconds"; 1400 default "0"; 1401 description 1402 "The time to wait before switching back to the working 1403 interface if operation-type is revertive."; 1404 reference "ITU-T G.808.1"; 1405 } 1407 leaf hold-off-timer { 1408 type uint16; 1409 units "milliseconds"; 1410 default "0"; 1411 description 1412 "Time interval after the detection of a fault and its 1413 confirmation as a condition requiring the protection 1414 switching procedure."; 1415 reference "ITU-T G.808.1"; 1416 } 1418 leaf status { 1419 type identityref { 1420 base protection-states; 1421 } 1422 config false; 1423 description 1424 "Status of the protection, in a group of interfaces 1425 configured in a protection mode."; 1426 reference "ITU-T G.808.1"; 1427 } 1429 action manual-switch-working { 1430 description 1431 "A switch action initiated by an operator command. 1432 It switches normal traffic signal to the working 1433 transport entity."; 1434 reference "ITU-T G.808.1"; 1435 } 1437 action manual-switch-protection { 1438 description 1439 "A switch action initiated by an operator command. 1441 It switches normal traffic signal to the protection 1442 transport entity."; 1443 reference "ITU-T G.808.1"; 1444 } 1446 action forced-switch { 1447 description 1448 "A switch action initiated by an operator command. 1449 It switches normal traffic signal to the protection 1450 transport entity and forces it to remain on that 1451 entity even when criteria for switching back to 1452 the original entity are fulfilled."; 1453 reference "ITU-T G.808.1"; 1454 } 1456 action lockout-of-protection { 1457 description 1458 "A switch action temporarily disables access to the 1459 protection transport entity for all signals."; 1460 reference "ITU-T G.808.1"; 1461 } 1463 action freeze { 1464 description 1465 "A switch action temporarily prevents any switch action 1466 to be taken and, as such, freezes the current state. 1467 Until the freeze is cleared, additional near-end external 1468 commands are rejected and fault condition changes and 1469 received APS messages are ignored.."; 1470 reference "ITU-T G.808.1"; 1471 } 1473 action exercise { 1474 description 1475 "A switch action to test if the APS communication is 1476 operating correctly. It is lower priority than any 'real' 1477 switch request.."; 1478 reference "ITU-T G.808.1"; 1479 } 1481 action clear { 1482 description 1483 "An action clears all switch commands."; 1484 reference "ITU-T G.808.1"; 1485 } 1486 } 1487 } 1488 } 1489 1491 6. Microwave Types YANG Module 1493 This module defines a collection of common data types using the YANG 1494 data modeling language. These common types are designed to be 1495 imported by other modules defined in the microwave area. 1497 file "ietf-microwave-types@2018-10-03.yang" 1499 module ietf-microwave-types { 1500 yang-version 1.1; 1501 namespace "urn:ietf:params:xml:ns:yang:ietf-microwave-types"; 1502 prefix mw-types; 1504 import iana-if-type { 1505 prefix ianaift; 1506 reference "RFC 7224"; 1507 } 1509 organization 1510 "Internet Engineering Task Force (IETF) CCAMP WG"; 1511 contact 1512 "WG List: 1514 ID-draft editors: 1515 Jonas Ahlberg (jonas.ahlberg@ericsson.com); 1516 Min Ye (amy.yemin@huawei.com); 1517 Xi Li (Xi.Li@neclab.eu); 1518 Daniela Spreafico (daniela.spreafico@nokia.com) 1519 Marko Vaupotic (Marko.Vaupotic@aviatnet.com)"; 1521 description 1522 "This module contains a collection of YANG data types 1523 considered generally useful for microwave interfaces. 1525 Copyright (c) 2018 IETF Trust and the persons identified as 1526 authors of the code. All rights reserved. 1528 Redistribution and use in source and binary forms, with or 1529 without modification, is permitted pursuant to, and subject 1530 to the license terms contained in, the Simplified BSD License 1531 set forth in Section 4.c of the IETF Trust's Legal Provisions 1532 Relating to IETF Documents 1533 (http://trustee.ietf.org/license-info). 1534 This version of this YANG module is part of RFC XXXX; see 1535 the RFC itself for full legal notices. 1537 Copyright (c) 2018 IETF Trust and the persons identified as 1538 authors of the code. All rights reserved."; 1540 revision 2018-10-03 { 1541 description "Initial revision."; 1542 reference "RFC XXXX: A YANG Data Model for Microwave Radio Link"; 1543 } 1545 /* 1546 * Interface identities 1547 */ 1549 identity radio-link-terminal { 1550 base ianaift:iana-interface-type; 1551 description 1552 "Interface identity for a radio link terminal."; 1553 } 1555 identity carrier-termination { 1556 base ianaift:iana-interface-type; 1557 description 1558 "Interface identity for a carrier termination."; 1559 } 1561 /* 1562 * Radio-link-terminal mode identities 1563 */ 1565 identity rlt-mode { 1566 description 1567 "A description of the mode in which the radio link 1568 terminal is configured. The format is X plus Y. 1569 X represent the number of bonded carrier terminations. 1570 Y represent the number of protecting carrier 1571 terminations."; 1572 } 1574 identity one-plus-zero { 1575 base rlt-mode; 1576 description 1577 "1 carrier termination only."; 1578 } 1580 identity one-plus-one { 1581 base rlt-mode; 1582 description 1583 "1 carrier termination 1584 and 1 protecting carrier termination."; 1585 } 1587 identity two-plus-zero { 1588 base rlt-mode; 1589 description 1590 "2 bonded carrier terminations."; 1591 } 1593 /* 1594 * Coding and modulation identities 1595 */ 1597 identity coding-modulation { 1598 description 1599 "The coding and modulation schemes."; 1600 } 1602 identity half-bpsk { 1603 base coding-modulation; 1604 description 1605 "Half BPSK coding and modulation scheme."; 1606 } 1608 identity half-bpsk-strong { 1609 base half-bpsk; 1610 description 1611 "Half BPSK strong coding and modulation scheme."; 1612 } 1614 identity half-bpsk-light { 1615 base half-bpsk; 1616 description 1617 "Half BPSK light coding and modulation scheme."; 1618 } 1620 identity bpsk { 1621 base coding-modulation; 1622 description 1623 "BPSK coding and modulation scheme."; 1624 } 1626 identity bpsk-strong { 1627 base bpsk; 1628 description 1629 "BPSK strong coding and modulation scheme."; 1631 } 1633 identity bpsk-light { 1634 base bpsk; 1635 description 1636 "BPSK light coding and modulation scheme."; 1637 } 1639 identity qpsk { 1640 base coding-modulation; 1641 description 1642 "QPSK coding and modulation scheme."; 1643 } 1645 identity qam-4 { 1646 base coding-modulation; 1647 description 1648 "4 QAM coding and modulation scheme."; 1649 } 1651 identity qam-4-strong { 1652 base qam-4; 1653 description 1654 "4 QAM strong coding and modulation scheme."; 1655 } 1657 identity qam-4-light { 1658 base qam-4; 1659 description 1660 "4 QAM light coding and modulation scheme."; 1661 } 1663 identity qam-16 { 1664 base coding-modulation; 1665 description 1666 "16 QAM coding and modulation scheme."; 1667 } 1669 identity qam-16-strong { 1670 base qam-16; 1671 description 1672 "16 QAM strong coding and modulation scheme."; 1673 } 1675 identity qam-16-light { 1676 base qam-16; 1677 description 1678 "16 QAM light coding and modulation scheme."; 1680 } 1682 identity qam-32 { 1683 base coding-modulation; 1684 description 1685 "32 QAM coding and modulation scheme."; 1686 } 1688 identity qam-32-strong { 1689 base qam-32; 1690 description 1691 "32 QAM strong coding and modulation scheme."; 1692 } 1694 identity qam-32-light { 1695 base qam-32; 1696 description 1697 "32 QAM light coding and modulation scheme."; 1698 } 1700 identity qam-64 { 1701 base coding-modulation; 1702 description 1703 "64 QAM coding and modulation scheme."; 1704 } 1706 identity qam-64-strong { 1707 base qam-64; 1708 description 1709 "64 QAM strong coding and modulation scheme."; 1710 } 1712 identity qam-64-light { 1713 base qam-64; 1714 description 1715 "64 QAM light coding and modulation scheme."; 1716 } 1718 identity qam-128 { 1719 base coding-modulation; 1720 description 1721 "128 QAM coding and modulation scheme."; 1722 } 1724 identity qam-128-strong { 1725 base qam-128; 1726 description 1727 "128 QAM strong coding and modulation scheme."; 1729 } 1731 identity qam-128-light { 1732 base qam-128; 1733 description 1734 "128 QAM light coding and modulation scheme."; 1735 } 1737 identity qam-256 { 1738 base coding-modulation; 1739 description 1740 "256 QAM coding and modulation scheme."; 1741 } 1743 identity qam-256-strong { 1744 base qam-256; 1745 description 1746 "256 QAM strong coding and modulation scheme."; 1747 } 1749 identity qam-256-light { 1750 base qam-256; 1751 description 1752 "256 QAM light coding and modulation scheme."; 1753 } 1755 identity qam-512 { 1756 base coding-modulation; 1757 description 1758 "512 QAM coding and modulation scheme."; 1759 } 1761 identity qam-512-strong { 1762 base qam-512; 1763 description 1764 "512 QAM strong coding and modulation scheme."; 1765 } 1767 identity qam-512-light { 1768 base qam-512; 1769 description 1770 "512 QAM light coding and modulation scheme."; 1771 } 1773 identity qam-1024 { 1774 base coding-modulation; 1775 description 1776 "1024 QAM coding and modulation scheme."; 1778 } 1780 identity qam-1024-strong { 1781 base qam-1024; 1782 description 1783 "1024 QAM strong coding and modulation scheme."; 1784 } 1786 identity qam-1024-light { 1787 base qam-1024; 1788 description 1789 "1024 QAM light coding and modulation scheme."; 1790 } 1792 identity qam-2048 { 1793 base coding-modulation; 1794 description 1795 "2048 QAM coding and modulation scheme."; 1796 } 1798 identity qam-2048-strong { 1799 base qam-2048; 1800 description 1801 "2048 QAM strong coding and modulation scheme."; 1802 } 1804 identity qam-2048-light { 1805 base qam-2048; 1806 description 1807 "2048 QAM light coding and modulation scheme."; 1808 } 1810 identity qam-4096 { 1811 base coding-modulation; 1812 description 1813 "4096 QAM coding and modulation scheme."; 1814 } 1816 identity qam-4096-strong { 1817 base qam-4096; 1818 description 1819 "4096 QAM strong coding and modulation scheme."; 1820 } 1822 identity qam-4096-light { 1823 base qam-4096; 1824 description 1825 "4096 QAM light coding and modulation scheme."; 1827 } 1829 /* 1830 * TDM-type identities 1831 */ 1833 identity tdm-type { 1834 description 1835 "A description of the type of TDM connection, 1836 also indicating the supported capacity of the 1837 connection."; 1838 } 1840 identity E1 { 1841 base tdm-type; 1842 description 1843 "E1 connection, 2.048 Mbit/s."; 1844 } 1846 identity STM-1 { 1847 base tdm-type; 1848 description 1849 "STM-1 connection, 155.52 Mbit/s."; 1850 } 1851 } 1853 1855 7. Security Considerations 1857 The YANG module specified in this document defines a schema for data 1858 that is designed to be accessed via network management protocols such 1859 as NETCONF [RFC6241] or RESTCONF [RFC8040]. The lowest NETCONF layer 1860 is the secure transport layer, and the mandatory-to-implement secure 1861 transport is Secure Shell (SSH) [RFC6242]. The lowest RESTCONF layer 1862 is HTTPS, and the mandatory-to-implement secure transport is TLS 1863 [RFC8446]. 1865 The NETCONF access control model [RFC8341] provides the means to 1866 restrict access for particular NETCONF or RESTCONF users to a 1867 preconfigured subset of all available NETCONF or RESTCONF protocol 1868 operations and content. 1870 There are a number of data nodes defined in this YANG module that are 1871 writable/creatable/deletable (i.e., config true, which is the 1872 default). These data nodes may be considered sensitive or vulnerable 1873 in some network environments. Write operations (e.g., edit-config) 1874 to these data nodes without proper protection can have a negative 1875 effect on network operations. These are the subtrees and data nodes 1876 and their sensitivity/vulnerability: 1878 Interfaces of type radio-link-terminal: 1880 /if:interfaces/if:interface/carrier-terminations, 1881 /if:interfaces/if:interface/rlp-groups, 1882 /if:interfaces/if:interface/xpic-pairs, 1883 /if:interfaces/if:interface/mimo-groups, and 1884 /if:interfaces/if:interface/tdm-connections: 1886 These lists represent the configuration of the radio-link-terminal 1887 and it need to match the configuration of the radio-link-terminal on 1888 the other side of the radio link. Unauthorized access to these data 1889 nodes could interrupt the ability to forward traffic. 1891 Interfaces of type carrier-termination: 1893 /if:interfaces/if:interface/carrier-id, 1894 /if:interfaces/if:interface/tx-enabled, 1895 /if:interfaces/if:interface/tx-frequency, 1896 /if:interfaces/if:interface/rx-frequency, 1897 /if:interfaces/if:interface/duplex-distance, 1898 /if:interfaces/if:interface/channel-separation, 1899 /if:interfaces/if:interface/rtpc/maximum-nominal-power, 1900 /if:interfaces/if:interface/atpc/maximum-nominal-power, 1901 /if:interfaces/if:interface/atpc/atpc-lower-threshold, 1902 /if:interfaces/if:interface/atpc/atpc-upper-threshold, 1903 /if:interfaces/if:interface/single/selected-cm, 1904 /if:interfaces/if:interface/adaptive/selected-min-acm, 1905 /if:interfaces/if:interface/adaptive/selected-max-acm, 1906 /if:interfaces/if:interface/if-loop, and 1907 /if:interfaces/if:interface/rf-loop: 1909 These data nodes represent the configuration of the carrier- 1910 termination and it need to match the configuration of the carrier- 1911 termination on the other side of the carrier. Unauthorized access to 1912 these data nodes could interrupt the ability to forward traffic. 1914 Radio link protection: 1916 /radio-link-protection-groups/protection-group: 1918 This list of protection groups and the constituent data nodes 1919 represents the configuration of the protection of carrier 1920 terminations. Unauthorized access to these data nodes could 1921 interrupt the ability to forward traffic or remove the ability to 1922 perform a necessary protection switch. 1924 XPIC: 1926 /xpic-pairs: 1928 This list represents the XPIC configuration of a pair carriers. 1929 Unauthorized access to these data nodes could interrupt the ability 1930 to forward traffic. 1932 MIMO: 1934 /mimo-groups: 1936 This list represents the MIMO configuration of multiple carriers. 1937 Unauthorized access to these data nodes could interrupt the ability 1938 to forward traffic. 1940 The security considerations of [RFC8343] also apply to this document. 1942 8. IANA Considerations 1944 It is proposed that IANA should assign new URIs from the "IETF XML 1945 Registry" [RFC3688] as follows: 1947 URI: urn:ietf:params:xml:ns:yang:ietf-microwave-radio-link 1948 Registrant Contact: The IESG 1949 XML: N/A; the requested URI is an XML namespace. 1951 URI: urn:ietf:params:xml:ns:yang:ietf-interface-protection 1952 Registrant Contact: The IESG 1953 XML: N/A; the requested URI is an XML namespace. 1955 URI: urn:ietf:params:xml:ns:yang:ietf-microwave-types 1956 Registrant Contact: The IESG 1957 XML: N/A; the requested URI is an XML namespace. 1959 It is proposed that IANA should record YANG module names in the "YANG 1960 Module Names" registry [RFC6020] as follows: 1962 Name: ietf-microwave-radio-link 1963 Maintained by IANA?: N 1964 Namespace: urn:ietf:params:xml:ns:yang:ietf-microwave-radio-link 1965 Prefix: mrl 1966 Reference: RFC XXXX 1968 Name: ietf-interface-protection 1969 Maintained by IANA?: N 1970 Namespace: urn:ietf:params:xml:ns:yang:ietf-interface-protection 1971 Prefix: ifprot 1972 Reference: RFC XXXX 1974 Name: ietf-microwave-types 1975 Maintained by IANA?: N 1976 Namespace: urn:ietf:params:xml:ns:yang:ietf-microwave-types 1977 Prefix: mw-types 1978 Reference: RFC XXXX 1980 9. References 1982 9.1. Normative References 1984 [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate 1985 Requirement Levels", BCP 14, RFC 2119, 1986 DOI 10.17487/RFC2119, March 1997, 1987 . 1989 [RFC3688] Mealling, M., "The IETF XML Registry", BCP 81, RFC 3688, 1990 DOI 10.17487/RFC3688, January 2004, 1991 . 1993 [RFC6020] Bjorklund, M., Ed., "YANG - A Data Modeling Language for 1994 the Network Configuration Protocol (NETCONF)", RFC 6020, 1995 DOI 10.17487/RFC6020, October 2010, 1996 . 1998 [RFC6241] Enns, R., Ed., Bjorklund, M., Ed., Schoenwaelder, J., Ed., 1999 and A. Bierman, Ed., "Network Configuration Protocol 2000 (NETCONF)", RFC 6241, DOI 10.17487/RFC6241, June 2011, 2001 . 2003 [RFC6242] Wasserman, M., "Using the NETCONF Protocol over Secure 2004 Shell (SSH)", RFC 6242, DOI 10.17487/RFC6242, June 2011, 2005 . 2007 [RFC6991] Schoenwaelder, J., Ed., "Common YANG Data Types", 2008 RFC 6991, DOI 10.17487/RFC6991, July 2013, 2009 . 2011 [RFC7224] Bjorklund, M., "IANA Interface Type YANG Module", 2012 RFC 7224, DOI 10.17487/RFC7224, May 2014, 2013 . 2015 [RFC8040] Bierman, A., Bjorklund, M., and K. Watsen, "RESTCONF 2016 Protocol", RFC 8040, DOI 10.17487/RFC8040, January 2017, 2017 . 2019 [RFC8174] Leiba, B., "Ambiguity of Uppercase vs Lowercase in RFC 2020 2119 Key Words", BCP 14, RFC 8174, DOI 10.17487/RFC8174, 2021 May 2017, . 2023 [RFC8341] Bierman, A. and M. Bjorklund, "Network Configuration 2024 Access Control Model", STD 91, RFC 8341, 2025 DOI 10.17487/RFC8341, March 2018, 2026 . 2028 [RFC8343] Bjorklund, M., "A YANG Data Model for Interface 2029 Management", RFC 8343, DOI 10.17487/RFC8343, March 2018, 2030 . 2032 [RFC8446] Rescorla, E., "The Transport Layer Security (TLS) Protocol 2033 Version 1.3", RFC 8446, DOI 10.17487/RFC8446, August 2018, 2034 . 2036 9.2. Informative References 2038 [EN301129] 2039 "Transmission and Multiplexing (TM); Digital Radio Relay 2040 Systems (DRRS); Synchronous Digital Hierarchy (SDH); 2041 System performance monitoring parameters of SDH DRRS", EN 2042 301 129 V1.1.2 , May 1995. 2044 [EN302217-1] 2045 "Fixed Radio Systems; Characteristics and requirements for 2046 point-to-point equipment and antennas; Part 1: Overview, 2047 common characteristics and system-dependent requirements", 2048 EN 302 217-1 V3.0.5 , June 2016. 2050 [EN302217-2] 2051 "Fixed Radio Systems; Characteristics and requirements for 2052 point to-point equipment and antennas; Part 2: Digital 2053 systems operating in frequency bands from 1 GHz to 86 GHz; 2054 Harmonised Standard covering the essential requirements of 2055 article 3.2 of Directive 2014/53/EU", EN 302 217-2 2056 V3.1.1 , May 2017. 2058 [G.808.1] "SERIES G: TRANSMISSION SYSTEMS AND MEDIA, DIGITAL SYSTEMS 2059 AND NETWORKS; Digital networks ; General aspects Generic 2060 protection switching ; Linear trail and subnetwork 2061 protection", ITU-T Rec. G.808.1 , May 2014. 2063 [G.826] "SERIES G: TRANSMISSION SYSTEMS AND MEDIA, DIGITAL SYSTEMS 2064 AND NETWORKS; Digital networks ; Quality and availability 2065 targets End-to-end error performance parameters and 2066 objectives for international, constant bit-rate digital 2067 paths and connections", ITU-T Rec. G.826 , December 2002. 2069 [I-D.ahlberg-ccamp-microwave-radio-link] 2070 Ahlberg, J., Carlson, J., Lund, H., Olausson, T., Ye, M., 2071 and M. Vaupotic, "Microwave Radio Link YANG Data Models", 2072 draft-ahlberg-ccamp-microwave-radio-link-01 (work in 2073 progress), May 2016. 2075 [I-D.ietf-ccamp-microwave-framework] 2076 Ahlberg, J., Ye, M., Li, X., Contreras, L., and C. 2077 Bernardos, "A framework for Management and Control of 2078 microwave and millimeter wave interface parameters", 2079 draft-ietf-ccamp-microwave-framework-07 (work in 2080 progress), June 2018. 2082 [ONF-model] 2083 "Microwave Information Model", version 1.0 , December 2084 2016, 2085 . 2089 [RFC8340] Bjorklund, M. and L. Berger, Ed., "YANG Tree Diagrams", 2090 BCP 215, RFC 8340, DOI 10.17487/RFC8340, March 2018, 2091 . 2093 [RFC8342] Bjorklund, M., Schoenwaelder, J., Shafer, P., Watsen, K., 2094 and R. Wilton, "Network Management Datastore Architecture 2095 (NMDA)", RFC 8342, DOI 10.17487/RFC8342, March 2018, 2096 . 2098 [TR102311] 2099 "Fixed Radio Systems; Point-to-point equipment; Specific 2100 aspects of the spatial frequency reuse method", ETSI TR 2101 102 311 V1.2.1 , November 2015. 2103 Appendix A. Example: 1+0 and 2+0 configuration instances 2105 This section gives simple examples of 1+0 and 2+0 instance using the 2106 YANG module defined in this draft. The examples are not intended as 2107 a complete module for 1+0 and 2+0 configuration. 2109 A.1. 1+0 instance 2111 /--------- Radio Link ---------\ 2112 Near End Far End 2114 +---------------+ +---------------+ 2115 | Radio Link | | Radio Link | 2116 | Terminal - A | | Terminal - B | 2117 | | | | 2118 | | | | 2119 | +-----------+ | | +-----------+ | 2120 | | | | Carrier A | | | | 2121 | | Carrier | |<--------->| | Carrier | | 2122 | |Termination| | | |Termination| | 2123 | | -1 | | | | -1 | | 2124 | +-----------+ | | +-----------+ | 2125 | | | | 2126 | | | | 2127 +---------------+ +---------------+ 2129 \--- Microwave Node ---/ \--- Microwave Node ---/ 2130 Figure A-1 1+0 example 2132 Figure A-1 shows a 1+0 example. The following instance 2133 shows the 1+0 configuration of Near End node. 2135 "interface": [ 2136 { 2137 "name": "RLT-A", 2138 "description": "Radio Link Terminal A", 2139 "type": "mrl:radio-link-terminal", 2140 "id": "RLT-A", 2141 "mode": "one-plus-zero", 2142 "carrier-terminations": [ 2143 "RLT-A:CT-1" 2144 ], 2145 "tdm-connections": [ 2146 "tdm-type": "E1", 2147 "tdm-connections": "4" 2148 ] 2149 }, 2151 { 2152 "name": "RLT-A:CT-1", 2153 "description": "Carrier Termination 1", 2154 "type": "mrl:carrier-termination", 2155 "carrier-id": "A", 2156 "tx-enabled": true, 2157 "tx-frequency": 10728000, 2158 "duplex-distance": 644000, 2159 "channel-separation": 28, 2160 "polarization": not-specified, 2161 "rtpc": { 2162 "maximum-nominal-power": 20 2163 }, 2164 "single": { 2165 "selected-cm": "qam-512" 2166 } 2167 } 2168 ] 2170 A.2. 2+0 instance 2172 Figure A-2 shows a 2+0 example. 2174 /--------- Radio Link ---------\ 2175 Near End Far End 2177 +---------------+ +---------------+ 2178 | Radio Link | | Radio Link | 2179 | Terminal -A | | Terminal -B | 2180 | | | | 2181 | | | | 2182 | +-----------+ | | +-----------+ | 2183 | | | | Carrier A | | | | 2184 | | Carrier | |<--------->| | Carrier | | 2185 | |Termination| | | |Termination| | 2186 | | -1 | | | | -1 | | 2187 | +-----------+ | | +-----------+ | 2188 | | | | 2189 | +-----------+ | | +-----------+ | 2190 | | | | Carrier B | | | | 2191 | | Carrier | |<--------->| | Carrier | | 2192 | |Termination| | | |Termination| | 2193 | | -2 | | | | -2 | | 2194 | +-----------+ | | +-----------+ | 2195 | | | | 2196 +---------------+ +---------------+ 2198 \--- Microwave Node ---/ \--- Microwave Node ---/ 2199 Figure A-2 2+0 example 2201 The following instance shows the 2+0 configuration of 2202 Near End node. 2204 "interface": [ 2205 { 2206 "name": "RLT-A", 2207 "description": "Radio Link Terminal A", 2208 "type": "mrl:radio-link-terminal", 2209 "id": "RLT-A", 2210 "mode": "two-plus-zero", 2211 "carrier-terminations": [ 2212 "RLT-A:CT-1", 2213 "RLT-A:CT-2" 2214 ], 2215 "tdm-connections": [ 2216 "tdm-type": "E1", 2217 "tdm-connections": "4" 2218 ] 2219 }, 2221 { 2222 "name": "RLT-A:CT-1", 2223 "description": "Carrier Termination 1", 2224 "type": "mrl:carrier-termination", 2225 "carrier-id": "A", 2226 "tx-enabled": true, 2227 "tx-frequency": 10728000, 2228 "duplex-distance": 644000, 2229 "channel-separation": 28, 2230 "polarization": not-specified, 2231 "rtpc": { 2232 "maximum-nominal-power": 20 2233 }, 2234 "single": { 2235 "selected-cm": "qam-512" 2236 } 2237 }, 2239 { 2240 "name": "RLT-A:CT-2", 2241 "description": "Carrier Termination 2", 2242 "type": "mrl:carrier-termination", 2243 "carrier-id": "B", 2244 "tx-enabled": true, 2245 "tx-oper-status": on, 2246 "tx-frequency": 10618000, 2247 "duplex-distance": 644000, 2248 "channel-separation": 28, 2249 "polarization": not-specified, 2250 "rtpc": { 2251 "maximum-nominal-power": 20 2252 }, 2253 "single": { 2254 "selected-cm": "qam-512" 2255 } 2256 } 2257 ] 2259 A.3. 2+0 XPIC instance 2261 The following instance shows the XPIC configuration of 2262 Near End node. 2264 "interface": [ 2265 { 2266 "name": "RLT-A", 2267 "description": "Radio Link Terminal A", 2268 "type": "mrl:radio-link-terminal", 2269 "id": "RLT-A", 2270 "mode": "two-plus-zero", 2271 "carrier-terminations": [ 2272 "RLT-A:CT-1", 2273 "RLT-A:CT-2" 2274 ], 2275 "xpic-pairs": [ 2276 "RLT-A:CT-1", 2277 "RLT-A:CT-2" 2278 ], 2279 "tdm-connections": [ 2280 "tdm-type": "E1", 2281 "tdm-connections": "4" 2282 ] 2283 }, 2285 { 2286 "name": "RLT-A:CT-1", 2287 "description": "Carrier Termination 1", 2288 "type": "mrl:carrier-termination", 2289 "carrier-id": "A", 2290 "tx-enabled": true, 2291 "tx-frequency": 10728000, 2292 "duplex-distance": 644000, 2293 "channel-separation": 28, 2294 "polarization": not-specified, 2295 "rtpc": { 2296 "maximum-nominal-power": 20 2297 }, 2298 "single": { 2299 "selected-cm": "qam-512" 2300 } 2301 }, 2303 { 2304 "name": "RLT-A:CT-2", 2305 "description": "Carrier Termination 2", 2306 "type": "mrl:carrier-termination", 2307 "carrier-id": "B", 2308 "tx-enabled": true, 2309 "tx-oper-status": on, 2310 "tx-frequency": 10618000, 2311 "duplex-distance": 644000, 2312 "channel-separation": 28, 2313 "polarization": not-specified, 2314 "rtpc": { 2315 "maximum-nominal-power": 20 2316 }, 2317 "single": { 2318 "selected-cm": "qam-512" 2319 } 2320 } 2321 ] 2323 Appendix B. Contributors 2325 Koji Kawada 2326 NEC Corporation 2327 1753, Shimonumabe Nakahara-ku 2328 Kawasaki, Kanagawa 211-8666 2329 Japan 2331 Email: k-kawada@ah.jp.nec.com 2333 Carlos J. Bernardos 2334 Universidad Carlos III de Madrid 2335 Av. Universidad, 30 2336 Leganes, Madrid 28911 2337 Spain 2339 Email: cjbc@it.uc3m.es 2341 Authors' Addresses 2343 Jonas Ahlberg 2344 Ericsson AB 2345 Lindholmspiren 11 2346 Goteborg 417 56 2347 Sweden 2349 Email: jonas.ahlberg@ericsson.com 2351 Ye Min 2352 Huawei Technologies 2353 No.1899, Xiyuan Avenue 2354 Chengdu 611731 2355 P.R.China 2357 Email: amy.yemin@huawei.com 2358 Xi Li 2359 NEC Laboratories Europe 2360 Kurfursten-Anlage 36 2361 Heidelberg 69115 2362 Germany 2364 Email: Xi.Li@neclab.eu 2366 Daniela Spreafico 2367 Nokia - IT 2368 Via Energy Park, 14 2369 Vimercate (MI) 20871 2370 Italy 2372 Email: daniela.spreafico@nokia.com 2374 Marko Vaupotic 2375 Aviat Networks 2376 Motnica 9 2377 Trzin-Ljubljana 1236 2378 Slovenia 2380 Email: Marko.Vaupotic@Aviatnet.com