idnits 2.17.1 draft-ietf-ccamp-mw-yang-07.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 == Line 219 has weird spacing: '...ections uin...' == Line 237 has weird spacing: '...l-power pow...' == Line 240 has weird spacing: '...l-power pow...' == Line 248 has weird spacing: '...cted-cm ide...' == Line 251 has weird spacing: '...min-acm ide...' == (1 more instance...) == The document doesn't use any RFC 2119 keywords, yet seems to have RFC 2119 boilerplate text. -- The document date (June 30, 2018) is 2127 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) -- Possible downref: Non-RFC (?) normative reference: ref. 'EN301129' -- Possible downref: Non-RFC (?) normative reference: ref. 'EN302217-1' -- Possible downref: Non-RFC (?) normative reference: ref. 'EN302217-2' -- Possible downref: Non-RFC (?) normative reference: ref. 'G.808.1' -- Possible downref: Non-RFC (?) normative reference: ref. 'G.826' ** Obsolete normative reference: RFC 5246 (Obsoleted by RFC 8446) -- Possible downref: Non-RFC (?) normative reference: ref. 'TR102311' Summary: 1 error (**), 0 flaws (~~), 8 warnings (==), 7 comments (--). 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: January 1, 2019 Huawei Technologies 6 X. Li 7 NEC Laboratories Europe 8 D. Spreafico 9 Nokia - IT 10 M. Vaupotic 11 Aviat Networks 12 June 30, 2018 14 A YANG Data Model for Microwave Radio Link 15 draft-ietf-ccamp-mw-yang-07 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 January 1, 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 . . . . . . . . . . . . . . . . . 44 80 Appendix A. Example: 1+0 and 2+0 configuration instances . . . . 44 81 Appendix B. Contributors . . . . . . . . . . . . . . . . . . . . 49 82 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 50 84 1. Introduction 86 This document defines a YANG data model for management and control of 87 the radio link interface(s) and the relationship to packet (typically 88 Ethernet) and/or TDM interfaces in a microwave/millimeter wave node. 89 ETSI EN 302 217 series defines the characteristics and requirements 90 of microwave/millimeter wave equipment and antennas. Especially ETSI 91 EN 302 217-2 [EN302217-2] specifies the essential parameters for the 92 systems operating from 1.4GHz to 86GHz. The data model includes 93 configuration and state data according to the new Network Management 94 Datastore Architecture [RFC8342]. 96 The design of the data model follows the framework for management and 97 control of microwave and millimeter wave interface parameters defined 98 in [I-D.ietf-ccamp-microwave-framework]. This framework identifies 99 the need and the scope of the YANG data model, the use cases and 100 requirements that the model needs to support. Moreover, it provides 101 a detailed gap analysis to identify the missing parameters and 102 functionalities of the existing and established models to support the 103 specified use cases and requirements, and based on that recommends 104 how the gaps should be filled with the development of the new model. 105 According to the conclusion of the gap analysis, the structure of the 106 data model is based on the structure defined in 107 [I-D.ahlberg-ccamp-microwave-radio-link] and it augments [RFC8343] to 108 align with the same structure for management of the packet 109 interfaces. More specifically, the model will include interface 110 layering to manage the capacity provided by a radio link terminal for 111 the associated Ethernet and TDM interfaces, using the principles for 112 interface layering described in [RFC8343] as a basis. 114 The data nodes for management of the interface protection 115 functionality is broken out into a separate and generic YANG data 116 module in order to make it available also for other interface types. 118 The designed YANG data model uses established microwave equipment and 119 radio standards, such as ETSI EN 302 217-2, and the IETF: Radio Link 120 Model [I-D.ahlberg-ccamp-microwave-radio-link] and the ONF: Microwave 121 Modeling [ONF-model] as the basis for the definition of the detailed 122 leafs/parameters, and proposes new ones to cover identified gaps 123 which are analyzed in [I-D.ietf-ccamp-microwave-framework]. 125 1.1. Terminology and Definitions 127 The following terms are used in this document: 129 Carrier Termination (CT) is an interface for the capacity provided 130 over the air by a single carrier. It is typically defined by its 131 transmitting and receiving frequencies. 133 Radio Link Terminal (RLT) is an interface providing packet capacity 134 and/or TDM capacity to the associated Ethernet and/or TDM interfaces 135 in a node and used for setting up a transport service over a 136 microwave/millimeter wave link. 138 The following acronyms are used in this document: 140 ACM Adaptive Coding Modulation 142 ATPC Automatic Transmit Power Control 143 BPSK Binary Phase-Shift Keying 145 CM Coding Modulation 147 CT Carrier Termination 149 RLT Radio Link Terminal 151 RTPC Remote Transmit Power Control 153 XPIC Cross Polarization Interference Cancellation 155 MIMO Multiple-Input Multiple-Output 157 QAM Quadrature Amplitude Modulation 159 QPSK Quadrature Phase-Shift Keying 161 1.2. Tree Structure 163 A simplified graphical representation of the data model is used in 164 chapter 3.1 of this this document. The meaning of the symbols in 165 these diagrams is defined in [RFC8340]. 167 2. Requirements Language 169 The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", 170 "SHOULD", "SHOULD NOT", "RECOMMENDED", "NOT RECOMMENDED", "MAY", and 171 "OPTIONAL" in this document are to be interpreted as described in BCP 172 14 [RFC2119] [RFC8174] when, and only when, they appear in all 173 capitals, as shown here. 175 3. Microwave Radio Link YANG Data Model 177 3.1. YANG Tree 179 module: ietf-microwave-radio-link 180 +--rw radio-link-protection-groups 181 | +--rw protection-group* [name] 182 | +--rw name string 183 | +--rw protection-architecture-type? identityref 184 | +--rw members* if:interface-ref 185 | +--rw operation-type? enumeration 186 | +--rw working-entity* if:interface-ref 187 | +--rw revertive-wait-to-restore? uint16 188 | +--rw hold-off-timer? uint16 189 | +--ro status? identityref 190 | +---x manual-switch-working 191 | +---x manual-switch-protection 192 | +---x forced-switch 193 | +---x lockout-of-protection 194 | +---x freeze 195 | +---x exercise 196 | +---x clear 197 +--rw xpic-pairs {xpic}? 198 | +--rw xpic-pair* [name] 199 | +--rw name string 200 | +--rw enabled? boolean 201 | +--rw members* if:interface-ref 202 +--rw mimo-groups {mimo}? 203 +--rw mimo-group* [name] 204 +--rw name string 205 +--rw enabled? boolean 206 +--rw members* if:interface-ref 207 augment /if:interfaces/if:interface: 208 +--rw id? string 209 +--rw mode identityref 210 +--rw carrier-terminations* if:interface-ref 211 +--rw rlp-groups* 212 | -> /radio-link-protection-groups/protection-group/name 213 +--rw xpic-pairs* -> /xpic-pairs/xpic-pair/name 214 | {xpic}? 215 +--rw mimo-groups* -> /mimo-groups/mimo-group/name 216 | {mimo}? 217 +--rw tdm-connections* [tdm-type] {tdm}? 218 +--rw tdm-type identityref 219 +--rw tdm-connections uint16 220 augment /if:interfaces/if:interface: 221 +--rw carrier-id? string 222 +--rw tx-enabled? boolean 223 +--ro tx-oper-status? enumeration 224 +--rw tx-frequency uint32 225 +--rw (freq-or-distance) 226 | +--:(rx-frequency) 227 | | +--rw rx-frequency? uint32 228 | +--:(duplex-distance) 229 | +--rw duplex-distance? int32 230 +--ro actual-rx-frequency? uint32 231 +--ro actual-duplex-distance? uint32 232 +--rw channel-separation uint32 233 +--rw polarization? enumeration 234 +--rw (power-mode) 235 | +--:(rtpc) 236 | | +--rw rtpc 237 | | +--rw maximum-nominal-power power 238 | +--:(atpc) 239 | +--rw atpc 240 | +--rw maximum-nominal-power power 241 | +--rw atpc-lower-threshold power 242 | +--rw atpc-upper-threshold power 243 +--ro actual-transmitted-level? power 244 +--ro actual-received-level? power 245 +--rw (coding-modulation-mode) 246 | +--:(single) 247 | | +--rw single 248 | | +--rw selected-cm identityref 249 | +--:(adaptive) 250 | +--rw adaptive 251 | +--rw selected-min-acm identityref 252 | +--rw selected-max-acm identityref 253 +--ro actual-tx-cm? identityref 254 +--ro actual-snir? decimal64 255 +--ro actual-xpi? decimal64 {xpic}? 256 +--rw ct-performance-thresholds 257 | +--rw received-level-alarm-threshold? power 258 | +--rw transmitted-level-alarm-threshold? power 259 | +--rw ber-alarm-threshold? enumeration 260 +--rw if-loop? enumeration 261 +--rw rf-loop? enumeration 262 +--ro capabilities 263 | +--ro min-tx-frequency? uint32 264 | +--ro max-tx-frequency? uint32 265 | +--ro min-rx-frequency? uint32 266 | +--ro max-rx-frequency? uint32 267 | +--ro minimum-power? power 268 | +--ro maximum-available-power? power 269 | +--ro available-min-acm? identityref 270 | +--ro available-max-acm? identityref 271 +--ro error-performance-statistics 272 | +--ro bbe? yang:counter32 273 | +--ro es? yang:counter32 274 | +--ro ses? yang:counter32 275 | +--ro uas? yang:counter32 276 +--ro radio-performance-statistics 277 +--ro min-rltm? power 278 +--ro max-rltm? power 279 +--ro min-tltm? power 280 +--ro max-tltm? power 282 3.2. Explanation of the Microwave Data Model 284 The leafs in the Interface Management Module augmented by Radio Link 285 Terminal (RLT) and Carrier Termination (CT) are not always 286 applicable. 288 "/interfaces/interface/enabled" is not applicable for RLT. Enable 289 and disable of an interface is done in the constituent CTs. 291 The packet related measurements "in-octets", "in-unicast-pkts", "in- 292 broadcast-pkts", "in-multicast-pkts", "in-discards", "in-errors", 293 "in-unknown-protos", "out-octets", "out-unicast-pkts", "out- 294 broadcast-pkts", "out-multicast-pkts", "out-discards", "out-errors" 295 are not within the scope of the microwave radio link domain and 296 therefore not applicable for RLT and CT. 298 4. Microwave Radio Link YANG Module 300 This module imports typedefs and modules from [RFC6991], [RFC8343] 301 and [RFC7224], and it references [TR102311], [EN302217-1], 302 [EN301129], and [G.826]. 304 file "ietf-microwave-radio-link@2018-06-30.yang" 306 module ietf-microwave-radio-link { 307 yang-version 1.1; 308 namespace "urn:ietf:params:xml:ns:yang:ietf-microwave-radio-link"; 309 prefix mrl; 311 import ietf-yang-types { 312 prefix yang; 313 reference "RFC 6991"; 314 } 316 import ietf-interfaces { 317 prefix if; 318 reference "RFC 8343"; 319 } 321 import ietf-interface-protection { 322 prefix ifprot; 323 reference "RFC XXXX"; 324 } 326 import ietf-microwave-types { 327 prefix mw-types; 328 reference "RFC XXXX"; 330 } 332 organization 333 "Internet Engineering Task Force (IETF) CCAMP WG"; 335 contact 336 "WG List: 338 ID-draft editors: 339 // RFC Ed.: replace ID-draft editors with Editors and remove 340 // this note 341 Jonas Ahlberg (jonas.ahlberg@ericsson.com); 342 Min Ye (amy.yemin@huawei.com); 343 Xi Li (Xi.Li@neclab.eu); 344 Daniela Spreafico (daniela.spreafico@nokia.com) 345 Marko Vaupotic (Marko.Vaupotic@aviatnet.com)"; 347 description 348 "This is a module for the entities in 349 a generic microwave system. 351 Copyright (c) 2018 IETF Trust and the persons identified as 352 authors of the code. All rights reserved. 353 Redistribution and use in source and binary forms, with or 354 without modification, is permitted pursuant to, and subject 355 to the license terms contained in, the Simplified BSD License 356 set forth in Section 4.c of the IETF Trust's Legal Provisions 357 Relating to IETF Documents 358 (http://trustee.ietf.org/license-info). 360 This version of this YANG module is part of RFC XXXX; see 361 the RFC itself for full legal notices. 363 Copyright (c) 2018 IETF Trust and the persons identified as 364 authors of the code. All rights reserved."; 366 revision 2018-06-30 { 367 description "Initial revision."; 368 reference "RFC XXXX: A YANG Data Model for Microwave Radio Link"; 369 } 371 /* 372 * Features 373 */ 375 feature xpic { 376 description 377 "Indicates that the device supports XPIC."; 379 reference "ETSI TR 102 311"; 380 } 382 feature mimo { 383 description 384 "Indicates that the device supports MIMO."; 385 reference "ETSI TR 102 311"; 386 } 388 feature tdm { 389 description 390 "Indicates that the device supports TDM."; 391 } 393 /* 394 * Typedefs 395 */ 397 typedef power { 398 type decimal64 { 399 fraction-digits 1; 400 } 401 description 402 "Type used for power values, selected and measured."; 403 } 405 /* 406 * Radio Link Terminal (RLT) 407 */ 409 augment "/if:interfaces/if:interface" { 410 when "derived-from-or-self(if:type," 411 + "'mw-types:radio-link-terminal')"; 412 description 413 "Addition of data nodes for radio link terminal to 414 the standard Interface data model, for interfaces of 415 the type 'radio-link-terminal'."; 417 leaf id { 418 type string; 419 description 420 "Descriptive identity of the radio link terminal used by 421 far-end RLT to check that it's connected to the correct 422 near-end RLT. Does not need to be configured if this check 423 is not used."; 424 } 426 leaf mode { 427 type identityref { 428 base mw-types:rlt-mode; 429 } 430 mandatory true; 431 description 432 "A description of the mode in which the radio link 433 terminal is configured. The format is X plus Y. 434 X represent the number of bonded carrier terminations. 435 Y represent the number of protecting carrier 436 terminations."; 437 } 439 leaf-list carrier-terminations { 440 type if:interface-ref; 441 must "derived-from-or-self(/if:interfaces/if:interface" 442 + "[if:name = current()]" 443 + "/if:type, 'mw-types:carrier-termination')" { 444 description 445 "The type of interface must be 446 'carrier-termination'."; 447 } 448 min-elements 1; 449 description 450 "A list of references to carrier terminations 451 included in the radio link terminal."; 452 } 454 leaf-list rlp-groups { 455 type leafref { 456 path "/mrl:radio-link-protection-groups/" 457 + "mrl:protection-group/mrl:name"; 458 } 459 description 460 "A list of references to the carrier termination 461 groups configured for radio link protection in this 462 radio link terminal."; 463 } 465 leaf-list xpic-pairs { 466 if-feature xpic; 467 type leafref { 468 path "/mrl:xpic-pairs/mrl:xpic-pair/mrl:name"; 469 } 471 description 472 "A list of references to the XPIC pairs used in this 473 radio link terminal. One pair can be used by two 474 terminals."; 476 reference "ETSI TR 102 311"; 477 } 479 leaf-list mimo-groups { 480 if-feature mimo; 481 type leafref { 482 path "/mrl:mimo-groups/mrl:mimo-group/mrl:name"; 483 } 484 description 485 "A reference to the MIMO group used in this 486 radio link terminal. One group can be used by more 487 than one terminal."; 488 reference "ETSI TR 102 311"; 489 } 491 list tdm-connections { 492 if-feature tdm; 493 key "tdm-type"; 494 description 495 "A list stating the number of active TDM connections 496 of a specified tdm-type that is configured to be 497 supported by the RLT."; 498 leaf tdm-type { 499 type identityref { 500 base mw-types:tdm-type; 501 } 502 description 503 "The type of TDM connection, which also indicates 504 the supported capacity."; 505 } 506 leaf tdm-connections { 507 type uint16; 508 mandatory true; 509 description 510 "Number of connections of the specified type."; 511 } 512 } 513 } 515 /* 516 * Carrier Termination 517 */ 519 augment "/if:interfaces/if:interface" { 520 when "derived-from-or-self(if:type," 521 + "'mw-types:carrier-termination')"; 523 description 524 "Addition of data nodes for carrier termination to 525 the standard Interface data model, for interfaces 526 of the type 'carrier-termination'."; 528 leaf carrier-id { 529 type string; 530 default "A"; 531 description 532 "ID of the carrier. (e.g. A, B, C or D) 533 Used in XPIC & MIMO configurations to check that 534 the carrier termination is connected to the correct 535 far-end carrier termination. Should be the same 536 carrier ID on both sides of the hop. 537 Defaulted when not MIMO or XPIC."; 538 } 540 leaf tx-enabled { 541 type boolean; 542 default "false"; 543 description 544 "Disables (false) or enables (true) the transmitter. 545 Only applicable when the interface is enabled 546 (interface:enabled = true) otherwise it's always 547 disabled."; 548 } 550 leaf tx-oper-status { 551 type enumeration { 552 enum "off" { 553 description "Transmitter is off."; 554 } 555 enum "on" { 556 description "Transmitter is on."; 557 } 558 enum "standby" { 559 description "Transmitter is in standby."; 560 } 561 } 562 config false; 563 description 564 "Shows the operative status of the transmitter."; 565 } 567 leaf tx-frequency { 568 type uint32; 569 units "kHz"; 570 mandatory true; 571 description 572 "Selected transmitter frequency."; 573 } 575 choice freq-or-distance { 576 leaf rx-frequency { 577 type uint32; 578 units "kHz"; 579 description 580 "Selected receiver frequency."; 581 } 582 leaf duplex-distance { 583 type int32; 584 units "kHz"; 585 description 586 "Distance between transmitter and receiver frequencies."; 587 } 588 mandatory true; 589 description 590 "A choice to configure rx-frequency directly or by computing 591 it as tx-frequency subtracted with the configured 592 duplex-distance." ; 593 } 595 leaf actual-rx-frequency { 596 type uint32; 597 units "kHz"; 598 config false; 599 description 600 "Computed receiver frequency."; 601 } 603 leaf actual-duplex-distance { 604 type uint32; 605 units "kHz"; 606 config false; 607 description 608 "Computed distance between Tx & Rx frequencies."; 609 } 611 leaf channel-separation { 612 type uint32; 613 units "kHz"; 614 mandatory true; 615 description 616 "The amount of bandwidth allocated to a carrier. The distance 617 between adjacent channels in a radio frequency channels 618 arrangement"; 619 reference "ETSI EN 302 217-1"; 621 } 623 leaf polarization { 624 type enumeration { 625 enum "horizontal" { 626 description "Horizontal polarization."; 627 } 628 enum "vertical" { 629 description "Vertical polarization."; 630 } 631 enum "not-specified" { 632 description "Polarization not specified."; 633 } 634 } 636 default "not-specified"; 637 description 638 "Polarization - A textual description for info only."; 639 } 641 choice power-mode { 642 container rtpc { 643 description 644 "Remote Transmit Power Control (RTPC)."; 645 reference "ETSI EN 302 217-1"; 646 leaf maximum-nominal-power { 647 type power { 648 range "-99..99"; 649 } 650 units "dBm"; 651 mandatory true; 652 description 653 "Selected output power."; 654 reference "ETSI EN 302 217-1"; 655 } 656 } 657 container atpc { 658 description 659 "Automatic Transmit Power Control (ATPC)."; 660 reference "ETSI EN 302 217-1"; 662 leaf maximum-nominal-power { 663 type power { 664 range "-99..99"; 665 } 666 units "dBm"; 667 mandatory true; 668 description 669 "Selected maximum output power. Minimum output 670 power is the same as the system capability, 671 available-min-output-power."; 672 reference "ETSI EN 302 217-1"; 673 } 675 leaf atpc-lower-threshold { 676 type power { 677 range "-99..-30"; 678 } 679 units "dBm"; 680 must "current() <= ../atpc-upper-threshold"; 681 mandatory true; 682 description 683 "The lower threshold for the input power at far-end 684 used in the ATPC mode."; 685 reference "ETSI EN 302 217-1"; 686 } 688 leaf atpc-upper-threshold { 689 type power { 690 range "-99..-30"; 691 } 692 units "dBm"; 693 mandatory true; 694 description 695 "The upper threshold for the input power at far-end 696 used in the ATPC mode."; 697 reference "ETSI EN 302 217-1"; 698 } 699 } 700 mandatory true; 701 description 702 "A choice of Remote Transmit Power Control (RTPC) 703 or Automatic Transmit Power Control (ATPC)."; 704 } 706 leaf actual-transmitted-level { 707 type power { 708 range "-99..99"; 709 } 710 units "dBm"; 711 config false; 712 description 713 "Actual transmitted power level (0.1 dBm resolution)."; 714 reference "ETSI EN 301 129"; 715 } 716 leaf actual-received-level { 717 type power { 718 range "-99..-20"; 719 } 720 units "dBm"; 721 config false; 722 description 723 "Actual received power level (0.1 dBm resolution)."; 724 reference "ETSI EN 301 129"; 725 } 727 choice coding-modulation-mode { 728 container single { 729 description "A single modulation order only."; 730 reference "ETSI EN 302 217-1"; 732 leaf selected-cm { 733 type identityref { 734 base mw-types:coding-modulation; 735 } 736 mandatory true; 737 description 738 "Selected the single coding/modulation."; 739 } 740 } 742 container adaptive { 743 description "Adaptive coding/modulation."; 744 reference "ETSI EN 302 217-1"; 746 leaf selected-min-acm { 747 type identityref { 748 base mw-types:coding-modulation; 749 } 750 mandatory true; 751 description 752 "Selected minimum coding/modulation. 753 Adaptive coding/modulation shall not go 754 below this value."; 755 } 757 leaf selected-max-acm { 758 type identityref { 759 base mw-types:coding-modulation; 760 } 761 mandatory true; 762 description 763 "Selected maximum coding/modulation. 765 Adaptive coding/modulation shall not go 766 above this value."; 767 } 768 } 769 mandatory true; 770 description 771 "A selection of single or 772 adaptive coding/modulation mode."; 773 } 775 leaf actual-tx-cm { 776 type identityref { 777 base mw-types:coding-modulation; 778 } 779 config false; 780 description 781 "Actual coding/modulation in transmitting direction."; 782 } 784 leaf actual-snir { 785 type decimal64 { 786 fraction-digits 1; 787 range "0..99"; 788 } 789 units "dB"; 790 config false; 791 description 792 "Actual signal to noise plus interference ratio. 793 (0.1 dB resolution)."; 794 } 796 leaf actual-xpi { 797 if-feature xpic; 798 type decimal64 { 799 fraction-digits 1; 800 range "0..99"; 801 } 802 units "dB"; 803 config false; 804 description 805 "The actual carrier to cross-polar interference. 806 Only valid if XPIC is enabled. (0.1 dB resolution)."; 807 reference "ETSI TR 102 311"; 808 } 810 container ct-performance-thresholds { 811 description 812 "Specification of thresholds for when alarms should 813 be sent and cleared for various performance counters."; 815 leaf received-level-alarm-threshold { 816 type power { 817 range "-99..-30"; 818 } 819 units "dBm"; 820 default "-99"; 821 description 822 "An alarm is sent when the received power level is 823 below the specified threshold."; 824 reference "ETSI EN 301 129"; 825 } 827 leaf transmitted-level-alarm-threshold { 828 type power { 829 range "-99..99"; 830 } 831 units "dBm"; 832 default "-99"; 833 description 834 "An alarm is sent when the transmitted power level 835 is below the specified threshold."; 836 reference "ETSI EN 301 129"; 837 } 839 leaf ber-alarm-threshold { 840 type enumeration { 841 enum "1e-9" { 842 description "Threshold at 1e-9 (10^-9)."; 843 } 844 enum "1e-8" { 845 description "Threshold at 1e-8 (10^-8)."; 846 } 847 enum "1e-7" { 848 description "Threshold at 1e-7 (10^-7)."; 849 } 850 enum "1e-6" { 851 description "Threshold at 1e-6 (10^-6)."; 852 } 853 enum "1e-5" { 854 description "Threshold at 1e-5 (10^-5)."; 855 } 856 enum "1e-4" { 857 description "Threshold at 1e-4 (10^-4)."; 858 } 859 enum "1e-3" { 860 description "Threshold at 1e-3 (10^-3)."; 862 } 863 enum "1e-2" { 864 description "Threshold at 1e-2 (10^-2)."; 865 } 866 enum "1e-1" { 867 description "Threshold at 1e-1 (10^-1)."; 868 } 869 } 870 default "1e-6"; 871 description 872 "Specification of at which BER an alarm should 873 be raised."; 874 reference "ETSI EN 302 217-1"; 875 } 876 } 878 leaf if-loop { 879 type enumeration { 880 enum disabled { 881 description "Disables the IF Loop."; 882 } 883 enum client { 884 description 885 "Loops the signal back to the client side."; 886 } 887 enum radio { 888 description 889 "Loops the signal back to the radio side."; 890 } 891 } 892 default "disabled"; 893 description 894 "Enable (client/radio) or disable (disabled) 895 the IF loop, which loops the signal back to 896 the client side or the radio side."; 897 } 899 leaf rf-loop { 900 type enumeration { 901 enum disabled { 902 description "Disables the RF Loop."; 903 } 904 enum client { 905 description 906 "Loops the signal back to the client side."; 907 } 908 enum radio { 909 description 910 "Loops the signal back to the radio side."; 911 } 912 } 913 default "disabled"; 914 description 915 "Enable (client/radio) or disable (disabled) 916 the RF loop, which loops the signal back to 917 the client side or the radio side."; 918 } 920 container capabilities { 921 config false; 922 description 923 "Capabilities of the installed equipment and 924 some selected configurations."; 926 leaf min-tx-frequency { 927 type uint32; 928 units "kHz"; 929 description 930 "Minimum Tx frequency possible to use."; 931 } 933 leaf max-tx-frequency { 934 type uint32; 935 units "kHz"; 936 description 937 "Maximum Tx frequency possible to use."; 938 } 940 leaf min-rx-frequency { 941 type uint32; 942 units "kHz"; 943 description 944 "Minimum Rx frequency possible to use."; 945 } 947 leaf max-rx-frequency { 948 type uint32; 949 units "kHz"; 950 description 951 "Maximum Tx frequency possible to use."; 952 } 954 leaf minimum-power { 955 type power; 956 units "dBm"; 957 description 958 "The minimum output power supported."; 959 reference "ETSI EN 302 217-1"; 960 } 962 leaf maximum-available-power { 963 type power; 964 units "dBm"; 965 description 966 "The maximum output power supported."; 967 reference "ETSI EN 302 217-1"; 968 } 970 leaf available-min-acm { 971 type identityref { 972 base mw-types:coding-modulation; 973 } 974 description 975 "Minimum coding-modulation possible to use."; 976 } 978 leaf available-max-acm { 979 type identityref { 980 base mw-types:coding-modulation; 981 } 982 description 983 "Maximum coding-modulation possible to use."; 984 } 985 } 987 container error-performance-statistics { 988 config false; 989 description 990 "ITU-T G.826 error performance statistics relevant for 991 a microwave/millimeter wave carrier."; 993 leaf bbe { 994 type yang:counter32; 995 units "number of block errors"; 996 description 997 "Number of Background Block Errors (BBE) during the 998 interval. A BBE is an errored block not occurring as 999 part of an SES."; 1000 reference "ITU-T G.826"; 1001 } 1003 leaf es { 1004 type yang:counter32; 1005 units "seconds"; 1006 description 1007 "Number of Errored Seconds (ES) since last reset. 1008 An ES is a one-second period with one or more errored 1009 blocks or at least one defect."; 1010 reference "ITU-T G.826"; 1011 } 1013 leaf ses { 1014 type yang:counter32; 1015 units "seconds"; 1016 description 1017 "Number of Severely Errored Seconds (SES) during the 1018 interval. SES is a one-second period which contains 1019 equal or more than 30% errored blocks or at least 1020 one defect. SES is a subset of ES."; 1021 reference "ITU-T G.826"; 1022 } 1024 leaf uas { 1025 type yang:counter32; 1026 units "seconds"; 1027 description 1028 "Number of Unavailable Seconds (UAS), that is, the 1029 total time that the node has been unavailable during 1030 a fixed measurement interval."; 1031 reference "ITU-T G.826"; 1032 } 1033 } 1035 container radio-performance-statistics { 1036 config false; 1037 description 1038 "ETSI EN 301 129 radio physical interface statistics relevant 1039 for a carrier termination."; 1041 leaf min-rltm { 1042 type power { 1043 range "-99..-20"; 1044 } 1045 units "dBm"; 1046 description 1047 "Minimum received power level since last reset."; 1048 reference "ETSI EN 301 129"; 1049 } 1051 leaf max-rltm { 1052 type power { 1053 range "-99..-20"; 1055 } 1056 units "dBm"; 1057 description 1058 "Maximum received power level since last reset."; 1059 reference "ETSI EN 301 129"; 1060 } 1062 leaf min-tltm { 1063 type power { 1064 range "-99..99"; 1065 } 1066 units "dBm"; 1067 description 1068 "Minimum transmitted power level since last reset."; 1069 reference "ETSI EN 301 129"; 1070 } 1072 leaf max-tltm { 1073 type power { 1074 range "-99..99"; 1075 } 1076 units "dBm"; 1077 description 1078 "Maximum transmitted power level since last reset."; 1079 reference "ETSI EN 301 129"; 1080 } 1081 } 1082 } 1084 /* 1085 * Radio Link Protection Groups 1086 */ 1088 container radio-link-protection-groups { 1089 description 1090 "Configuration of radio link protected groups (1+1) of 1091 carrier terminations in a radio link. More than one 1092 protected group per radio-link-terminal is allowed."; 1094 uses ifprot:protection-groups { 1096 refine protection-group/members { 1097 must "derived-from-or-self(/if:interfaces/if:interface" 1098 + "[if:name = current()]" 1099 + "/if:type, 'mw-types:carrier-termination')" { 1100 description 1101 "The type of a protection member must be 1102 'carrier-termination'."; 1104 } 1105 } 1107 refine protection-group/working-entity { 1108 must "derived-from-or-self(/if:interfaces/if:interface" 1109 + "[if:name = current()]" 1110 + "/if:type, 'mw-types:carrier-termination')" { 1111 description 1112 "The type of a working-entity must be 1113 'carrier-termination'."; 1114 } 1115 } 1116 } 1117 } 1119 /* 1120 * XPIC & MIMO groups - Configuration data nodes 1121 */ 1123 container xpic-pairs { 1124 if-feature xpic; 1125 description 1126 "Configuration of carrier termination pairs 1127 for operation in XPIC mode."; 1128 reference "ETSI TR 102 311"; 1130 list xpic-pair { 1131 key "name"; 1132 description 1133 "List of carrier termination pairs in XPIC mode."; 1135 leaf name { 1136 type string; 1137 description 1138 "Name used for identification of the XPIC pair."; 1139 } 1141 leaf enabled { 1142 type boolean; 1143 default "false"; 1144 description 1145 "Enable(true)/disable(false) XPIC"; 1146 } 1148 leaf-list members { 1149 type if:interface-ref; 1150 must "derived-from-or-self(/if:interfaces/if:interface" 1151 + "[if:name = current()]" 1152 + "/if:type, 'mw-types:carrier-termination')" { 1153 description 1154 "The type of a member must be 'carrier-termination'."; 1155 } 1156 min-elements 2; 1157 max-elements 2; 1158 description 1159 "Association to XPIC pairs used in the radio link 1160 terminal."; 1161 } 1162 } 1163 } 1165 container mimo-groups { 1166 if-feature mimo; 1167 description 1168 "Configuration of carrier terminations 1169 for operation in MIMO mode."; 1170 reference "ETSI TR 102 311"; 1172 list mimo-group { 1173 key "name"; 1174 description 1175 "List of carrier terminations in MIMO mode."; 1177 leaf name { 1178 type string; 1179 description 1180 "Name used for identification of the MIMO group."; 1181 } 1183 leaf enabled { 1184 type boolean; 1185 default "false"; 1186 description 1187 "Enable(true)/disable(false) MIMO"; 1188 } 1190 leaf-list members { 1191 type if:interface-ref; 1192 must "derived-from-or-self(/if:interfaces/if:interface" 1193 + "[if:name = current()]" 1194 + "/if:type, 'mw-types:carrier-termination')" { 1195 description 1196 "The type of a member must be 'carrier-termination'."; 1197 } 1199 min-elements 2; 1200 description 1201 "Association to a MIMO group if used in the radio 1202 link terminal."; 1203 } 1204 } 1205 } 1206 } 1208 1210 5. Interface Protection YANG Module 1212 The data nodes for management of the interface protection 1213 functionality is broken out from the Microwave Radio Link Module into 1214 a separate and generic YANG data module in order to make it available 1215 also for other interface types. 1217 This module imports modules from [RFC8343], and it references 1218 [G.808.1]. 1220 file "ietf-interface-protection@2018-06-30.yang" 1222 module ietf-interface-protection { 1223 yang-version 1.1; 1224 namespace "urn:ietf:params:xml:ns:yang:ietf-interface-protection"; 1225 prefix ifprot; 1227 import ietf-interfaces { 1228 prefix if; 1229 reference "RFC8343"; 1230 } 1232 organization 1233 "Internet Engineering Task Force (IETF) CCAMP WG"; 1234 contact 1235 "WG List: 1237 ID-draft editors: 1238 Jonas Ahlberg (jonas.ahlberg@ericsson.com); 1239 Min Ye (amy.yemin@huawei.com); 1240 Xi Li (Xi.Li@neclab.eu); 1241 Daniela Spreafico (daniela.spreafico@nokia.com) 1242 Marko Vaupotic (Marko.Vaupotic@aviatnet.com)"; 1244 description 1245 "This is a module for the entities in 1246 a generic interface protection mechanism. 1248 Copyright (c) 2018 IETF Trust and the persons identified as 1249 authors of the code. All rights reserved. 1251 Redistribution and use in source and binary forms, with or 1252 without modification, is permitted pursuant to, and subject 1253 to the license terms contained in, the Simplified BSD License 1254 set forth in Section 4.c of the IETF Trust's Legal Provisions 1255 Relating to IETF Documents 1256 (http://trustee.ietf.org/license-info). 1258 This version of this YANG module is part of RFC XXXX; see 1259 the RFC itself for full legal notices. 1261 Copyright (c) 2018 IETF Trust and the persons identified as 1262 authors of the code. All rights reserved."; 1264 revision 2018-06-30 { 1265 description "Initial revision."; 1266 reference "RFC XXXX: A YANG Data Model for Microwave Radio Link"; 1267 } 1269 /* 1270 * Protection architecture type identities 1271 */ 1273 identity protection-architecture-type { 1274 description 1275 "protection architecture type"; 1276 reference "ITU-T G.808.1"; 1277 } 1279 identity one-plus-one-type { 1280 base protection-architecture-type; 1281 description 1282 "1+1, One interface protects 1283 another one interface."; 1284 reference "ITU-T G.808.1"; 1285 } 1287 identity one-to-n-type { 1288 base protection-architecture-type; 1289 description 1290 "1:N, One interface protects 1291 n other interfaces."; 1292 reference "ITU-T G.808.1"; 1293 } 1294 /* 1295 * Protection states identities 1296 */ 1298 identity protection-states { 1299 description 1300 "Identities describing the status of the protection, 1301 in a group of interfaces configured in 1302 a protection mode."; 1303 } 1305 identity unprotected { 1306 base protection-states; 1307 description "Not protected"; 1308 } 1310 identity protected { 1311 base protection-states; 1312 description "Protected"; 1313 } 1315 identity unable-to-protect { 1316 base protection-states; 1317 description "Unable to protect"; 1318 } 1320 /* 1321 * Protection Groups 1322 */ 1324 grouping protection-groups { 1325 description 1326 "Configuration of protected groups (1+1) of interfaces 1327 providing protection for each other. More than one protected 1328 group per higher-layer-interface is allowed."; 1330 list protection-group { 1331 key "name"; 1332 description 1333 "List of protected groups of interfaces 1334 in a higher-layer-interface."; 1336 leaf name { 1337 type string; 1338 description 1339 "Name used for identification of the protection group"; 1340 } 1341 leaf protection-architecture-type { 1342 type identityref{ 1343 base protection-architecture-type; 1344 } 1345 default "ifprot:one-plus-one-type"; 1346 description 1347 "The type of protection architecture used, e.g. one 1348 interface protecting one or several other interfaces."; 1349 reference "ITU-T G.808.1"; 1350 } 1352 leaf-list members { 1353 type if:interface-ref; 1354 min-elements 2; 1355 description 1356 "Association to a group of interfaces configured for 1357 protection and used by a higher-layer-interface."; 1358 } 1360 leaf operation-type { 1361 type enumeration { 1362 enum "non-revertive" { 1363 description 1364 "In non revertive operation, the traffic does not 1365 return to the working interface if the switch requests 1366 are terminated."; 1367 reference "ITU-T G.808.1"; 1368 } 1369 enum "revertive" { 1370 description 1371 "In revertive operation, the traffic always 1372 returns to (or remains on) the working interface 1373 if the switch requests are terminated."; 1374 reference "ITU-T G.808.1"; 1375 } 1376 } 1377 default "non-revertive"; 1378 description 1379 "The type of protection operation, i.e. revertive 1380 or non-revertive operation."; 1381 } 1383 leaf-list working-entity { 1384 when "../operation-type = 'revertive'"; 1385 type if:interface-ref; 1386 min-elements 1; 1387 description 1388 "The interfaces over which the traffic normally should 1389 be transported over when there is no need to use the 1390 protecting interface."; 1391 } 1393 leaf revertive-wait-to-restore { 1394 when "../operation-type = 'revertive'"; 1395 type uint16; 1396 units "seconds"; 1397 default "0"; 1398 description 1399 "The time to wait before switching back to the working 1400 interface if operation-type is revertive."; 1401 reference "ITU-T G.808.1"; 1402 } 1404 leaf hold-off-timer { 1405 type uint16; 1406 units "milliseconds"; 1407 default "0"; 1408 description 1409 "Time interval after the detection of a fault and its 1410 confirmation as a condition requiring the protection 1411 switching procedure."; 1412 reference "ITU-T G.808.1"; 1413 } 1415 leaf status { 1416 type identityref { 1417 base protection-states; 1418 } 1419 config false; 1420 description 1421 "Status of the protection, in a group of interfaces 1422 configured in a protection mode."; 1423 reference "ITU-T G.808.1"; 1424 } 1426 action manual-switch-working{ 1427 description 1428 "A switch action initiated by an operator command. 1429 It switches normal traffic signal to the working 1430 transport entity."; 1431 reference "ITU-T G.808.1"; 1432 } 1434 action manual-switch-protection{ 1435 description 1436 "A switch action initiated by an operator command. 1438 It switches normal traffic signal to the protection 1439 transport entity."; 1440 reference "ITU-T G.808.1"; 1441 } 1443 action forced-switch{ 1444 description 1445 "A switch action initiated by an operator command. 1446 It switches normal traffic signal to the protection 1447 transport entity and forces it to remain on that 1448 entity even when criteria for switching back to 1449 the original entity are fulfilled."; 1450 reference "ITU-T G.808.1"; 1451 } 1453 action lockout-of-protection{ 1454 description 1455 "A switch action temporarily disables access to the 1456 protection transport entity for all signals."; 1457 reference "ITU-T G.808.1"; 1458 } 1460 action freeze{ 1461 description 1462 "A switch action temporarily prevents any switch action 1463 to be taken and, as such, freezes the current state. 1464 Until the freeze is cleared, additional near-end external 1465 commands are rejected and fault condition changes and 1466 received APS messages are ignored.."; 1467 reference "ITU-T G.808.1"; 1468 } 1470 action exercise{ 1471 description 1472 "A switch action to test if the APS communication is 1473 operating correctly. It is lower priority than any 'real' 1474 switch request.."; 1475 reference "ITU-T G.808.1"; 1476 } 1478 action clear{ 1479 description 1480 "An action clears all switch commands."; 1481 reference "ITU-T G.808.1"; 1482 } 1483 } 1484 } 1485 } 1486 1488 6. Microwave Types YANG Module 1490 This module defines a collection of common data types using the YANG 1491 data modeling language. These common types are designed to be 1492 imported by other modules defined in the microwave area. 1494 file "ietf-microwave-types@2018-06-30.yang" 1496 module ietf-microwave-types { 1497 yang-version 1.1; 1498 namespace "urn:ietf:params:xml:ns:yang:ietf-microwave-types"; 1499 prefix mw-types; 1501 import iana-if-type { 1502 prefix ianaift; 1503 reference "RFC 7224"; 1504 } 1506 organization 1507 "Internet Engineering Task Force (IETF) CCAMP WG"; 1508 contact 1509 "WG List: 1511 ID-draft editors: 1512 Jonas Ahlberg (jonas.ahlberg@ericsson.com); 1513 Min Ye (amy.yemin@huawei.com); 1514 Xi Li (Xi.Li@neclab.eu); 1515 Daniela Spreafico (daniela.spreafico@nokia.com) 1516 Marko Vaupotic (Marko.Vaupotic@aviatnet.com)"; 1518 description 1519 "This module contains a collection of YANG data types 1520 considered generally useful for microwave interfaces. 1522 Copyright (c) 2018 IETF Trust and the persons identified as 1523 authors of the code. All rights reserved. 1525 Redistribution and use in source and binary forms, with or 1526 without modification, is permitted pursuant to, and subject 1527 to the license terms contained in, the Simplified BSD License 1528 set forth in Section 4.c of the IETF Trust's Legal Provisions 1529 Relating to IETF Documents 1530 (http://trustee.ietf.org/license-info). 1531 This version of this YANG module is part of RFC XXXX; see 1532 the RFC itself for full legal notices. 1534 Copyright (c) 2018 IETF Trust and the persons identified as 1535 authors of the code. All rights reserved."; 1537 revision 2018-06-30 { 1538 description "Initial revision."; 1539 reference "RFC XXXX: A YANG Data Model for Microwave Radio Link"; 1540 } 1542 /* 1543 * Interface identities 1544 */ 1546 identity radio-link-terminal { 1547 base ianaift:iana-interface-type; 1548 description 1549 "Interface identity for a radio link terminal."; 1550 } 1552 identity carrier-termination { 1553 base ianaift:iana-interface-type; 1554 description 1555 "Interface identity for a carrier termination."; 1556 } 1558 /* 1559 * Radio-link-terminal mode identities 1560 */ 1562 identity rlt-mode { 1563 description 1564 "A description of the mode in which the radio link 1565 terminal is configured. The format is X plus Y. 1566 X represent the number of bonded carrier terminations. 1567 Y represent the number of protecting carrier 1568 terminations."; 1569 } 1571 identity one-plus-zero { 1572 base rlt-mode; 1573 description 1574 "1 carrier termination only."; 1575 } 1577 identity one-plus-one { 1578 base rlt-mode; 1579 description 1580 "1 carrier termination 1581 and 1 protecting carrier termination."; 1582 } 1584 identity two-plus-zero { 1585 base rlt-mode; 1586 description 1587 "2 bonded carrier terminations."; 1588 } 1590 /* 1591 * Coding and modulation identities 1592 */ 1594 identity coding-modulation { 1595 description 1596 "The coding and modulation schemes."; 1597 } 1599 identity half-bpsk { 1600 base coding-modulation; 1601 description 1602 "Half BPSK coding and modulation scheme."; 1603 } 1605 identity half-bpsk-strong { 1606 base half-bpsk; 1607 description 1608 "Half BPSK strong coding and modulation scheme."; 1609 } 1611 identity half-bpsk-light { 1612 base half-bpsk; 1613 description 1614 "Half BPSK light coding and modulation scheme."; 1615 } 1617 identity bpsk { 1618 base coding-modulation; 1619 description 1620 "BPSK coding and modulation scheme."; 1621 } 1623 identity bpsk-strong { 1624 base bpsk; 1625 description 1626 "BPSK strong coding and modulation scheme."; 1628 } 1630 identity bpsk-light { 1631 base bpsk; 1632 description 1633 "BPSK light coding and modulation scheme."; 1634 } 1636 identity qpsk { 1637 base coding-modulation; 1638 description 1639 "QPSK coding and modulation scheme."; 1640 } 1642 identity qam-4 { 1643 base coding-modulation; 1644 description 1645 "4 QAM coding and modulation scheme."; 1646 } 1648 identity qam-4-strong { 1649 base qam-4; 1650 description 1651 "4 QAM strong coding and modulation scheme."; 1652 } 1654 identity qam-4-light { 1655 base qam-4; 1656 description 1657 "4 QAM light coding and modulation scheme."; 1658 } 1660 identity qam-16 { 1661 base coding-modulation; 1662 description 1663 "16 QAM coding and modulation scheme."; 1664 } 1666 identity qam-16-strong { 1667 base qam-16; 1668 description 1669 "16 QAM strong coding and modulation scheme."; 1670 } 1672 identity qam-16-light { 1673 base qam-16; 1674 description 1675 "16 QAM light coding and modulation scheme."; 1677 } 1679 identity qam-32 { 1680 base coding-modulation; 1681 description 1682 "32 QAM coding and modulation scheme."; 1683 } 1685 identity qam-32-strong { 1686 base qam-32; 1687 description 1688 "32 QAM strong coding and modulation scheme."; 1689 } 1691 identity qam-32-light { 1692 base qam-32; 1693 description 1694 "32 QAM light coding and modulation scheme."; 1695 } 1697 identity qam-64 { 1698 base coding-modulation; 1699 description 1700 "64 QAM coding and modulation scheme."; 1701 } 1703 identity qam-64-strong { 1704 base qam-64; 1705 description 1706 "64 QAM strong coding and modulation scheme."; 1707 } 1709 identity qam-64-light { 1710 base qam-64; 1711 description 1712 "64 QAM light coding and modulation scheme."; 1713 } 1715 identity qam-128 { 1716 base coding-modulation; 1717 description 1718 "128 QAM coding and modulation scheme."; 1719 } 1721 identity qam-128-strong { 1722 base qam-128; 1723 description 1724 "128 QAM strong coding and modulation scheme."; 1726 } 1728 identity qam-128-light { 1729 base qam-128; 1730 description 1731 "128 QAM light coding and modulation scheme."; 1732 } 1734 identity qam-256 { 1735 base coding-modulation; 1736 description 1737 "256 QAM coding and modulation scheme."; 1738 } 1740 identity qam-256-strong { 1741 base qam-256; 1742 description 1743 "256 QAM strong coding and modulation scheme."; 1744 } 1746 identity qam-256-light { 1747 base qam-256; 1748 description 1749 "256 QAM light coding and modulation scheme."; 1750 } 1752 identity qam-512 { 1753 base coding-modulation; 1754 description 1755 "512 QAM coding and modulation scheme."; 1756 } 1758 identity qam-512-strong { 1759 base qam-512; 1760 description 1761 "512 QAM strong coding and modulation scheme."; 1762 } 1764 identity qam-512-light { 1765 base qam-512; 1766 description 1767 "512 QAM light coding and modulation scheme."; 1768 } 1770 identity qam-1024 { 1771 base coding-modulation; 1772 description 1773 "1024 QAM coding and modulation scheme."; 1775 } 1777 identity qam-1024-strong { 1778 base qam-1024; 1779 description 1780 "1024 QAM strong coding and modulation scheme."; 1781 } 1783 identity qam-1024-light { 1784 base qam-1024; 1785 description 1786 "1024 QAM light coding and modulation scheme."; 1787 } 1789 identity qam-2048 { 1790 base coding-modulation; 1791 description 1792 "2048 QAM coding and modulation scheme."; 1793 } 1795 identity qam-2048-strong { 1796 base qam-2048; 1797 description 1798 "2048 QAM strong coding and modulation scheme."; 1799 } 1801 identity qam-2048-light { 1802 base qam-2048; 1803 description 1804 "2048 QAM light coding and modulation scheme."; 1805 } 1807 identity qam-4096 { 1808 base coding-modulation; 1809 description 1810 "4096 QAM coding and modulation scheme."; 1811 } 1813 identity qam-4096-strong { 1814 base qam-4096; 1815 description 1816 "4096 QAM strong coding and modulation scheme."; 1817 } 1819 identity qam-4096-light { 1820 base qam-4096; 1821 description 1822 "4096 QAM light coding and modulation scheme."; 1824 } 1826 /* 1827 * TDM-type identities 1828 */ 1830 identity tdm-type { 1831 description 1832 "A description of the type of TDM connection, 1833 also indicating the supported capacity of the 1834 connection."; 1835 } 1837 identity E1 { 1838 base tdm-type; 1839 description 1840 "E1 connection, 2.048 Mbit/s."; 1841 } 1843 identity STM-1 { 1844 base tdm-type; 1845 description 1846 "STM-1 connection, 155.52 Mbit/s."; 1847 } 1848 } 1850 1852 7. Security Considerations 1854 The YANG module specified in this document defines a schema for data 1855 that is designed to be accessed via network management protocols such 1856 as NETCONF [RFC6241] or RESTCONF [RFC8040]. The lowest NETCONF layer 1857 is the secure transport layer, and the mandatory-to-implement secure 1858 transport is Secure Shell (SSH) [RFC6242]. The lowest RESTCONF layer 1859 is HTTPS, and the mandatory-to-implement secure transport is TLS 1860 [RFC5246]. 1862 The NETCONF access control model [RFC8341] provides the means to 1863 restrict access for particular NETCONF or RESTCONF users to a 1864 preconfigured subset of all available NETCONF or RESTCONF protocol 1865 operations and content. 1867 There are a number of data nodes defined in this YANG module that are 1868 writable/creatable/deletable (i.e., config true, which is the 1869 default). These data nodes may be considered sensitive or vulnerable 1870 in some network environments. Write operations (e.g., edit-config) 1871 to these data nodes without proper protection can have a negative 1872 effect on network operations. These are the subtrees and data nodes 1873 and their sensitivity/vulnerability: 1875 Interfaces of type radio-link-terminal: 1877 /if:interfaces/if:interface/carrier-terminations, 1878 /if:interfaces/if:interface/rlp-groups, 1879 /if:interfaces/if:interface/xpic-pairs, 1880 /if:interfaces/if:interface/mimo-groups, and 1881 /if:interfaces/if:interface/tdm-connections: 1883 These lists represent the configuration of the radio-link-terminal 1884 and it need to match the configuration of the radio-link-terminal on 1885 the other side of the radio link. Unauthorized access to these data 1886 nodes could interrupt the ability to forward traffic. 1888 Interfaces of type carrier-termination: 1890 /if:interfaces/if:interface/carrier-id, 1891 /if:interfaces/if:interface/tx-enabled, 1892 /if:interfaces/if:interface/tx-frequency, 1893 /if:interfaces/if:interface/rx-frequency, 1894 /if:interfaces/if:interface/duplex-distance, 1895 /if:interfaces/if:interface/channel-separation, 1896 /if:interfaces/if:interface/rtpc/maximum-nominal-power, 1897 /if:interfaces/if:interface/atpc/maximum-nominal-power, 1898 /if:interfaces/if:interface/atpc/atpc-lower-threshold, 1899 /if:interfaces/if:interface/atpc/atpc-upper-threshold, 1900 /if:interfaces/if:interface/single/selected-cm, 1901 /if:interfaces/if:interface/adaptive/selected-min-acm, 1902 /if:interfaces/if:interface/adaptive/selected-max-acm, 1903 /if:interfaces/if:interface/if-loop, and 1904 /if:interfaces/if:interface/rf-loop: 1906 These data nodes represent the configuration of the carrier- 1907 termination and it need to match the configuration of the carrier- 1908 termination on the other side of the carrier. Unauthorized access to 1909 these data nodes could interrupt the ability to forward traffic. 1911 Radio link protection: 1913 /radio-link-protection-groups/protection-group: 1915 This list of protection groups and the constituent data nodes 1916 represents the configuration of the protection of carrier 1917 terminations. Unauthorized access to these data nodes could 1918 interrupt the ability to forward traffic or remove the ability to 1919 perform a necessary protection switch. 1921 XPIC: 1923 /xpic-pairs: 1925 This list represents the XPIC configuration of a pair carriers. 1926 Unauthorized access to these data nodes could interrupt the ability 1927 to forward traffic. 1929 MIMO: 1931 /mimo-groups: 1933 This list represents the MIMO configuration of multiple carriers. 1934 Unauthorized access to these data nodes could interrupt the ability 1935 to forward traffic. 1937 The security considerations of [RFC8343] also apply to this document. 1939 8. IANA Considerations 1941 It is proposed that IANA should assign new URIs from the "IETF XML 1942 Registry" [RFC3688] as follows: 1944 URI: urn:ietf:params:xml:ns:yang:ietf-microwave-radio-link 1945 Registrant Contact: The IESG 1946 XML: N/A; the requested URI is an XML namespace. 1948 URI: urn:ietf:params:xml:ns:yang:ietf-interface-protection 1949 Registrant Contact: The IESG 1950 XML: N/A; the requested URI is an XML namespace. 1952 It is proposed that IANA should record YANG module names in the "YANG 1953 Module Names" registry [RFC6020] as follows: 1955 Name: ietf-microwave-radio-link 1956 Namespace: urn:ietf:params:xml:ns:yang:ietf-microwave-radio-link 1957 Prefix: mrl 1958 Reference: RFC XXXX 1960 Name: ietf-interface-protection 1961 Namespace: urn:ietf:params:xml:ns:yang:ietf-interface-protection 1962 Prefix: ifprot 1963 Reference: RFC XXXX 1965 9. References 1967 9.1. Normative References 1969 [EN301129] 1970 "Transmission and Multiplexing (TM); Digital Radio Relay 1971 Systems (DRRS); Synchronous Digital Hierarchy (SDH); 1972 System performance monitoring parameters of SDH DRRS", EN 1973 301 129 V1.1.2 , May 1995. 1975 [EN302217-1] 1976 "Fixed Radio Systems; Characteristics and requirements for 1977 point-to-point equipment and antennas; Part 1: Overview, 1978 common characteristics and system-dependent requirements", 1979 EN 302 217-1 V3.0.5 , June 2016. 1981 [EN302217-2] 1982 "Fixed Radio Systems; Characteristics and requirements for 1983 point to-point equipment and antennas; Part 2: Digital 1984 systems operating in frequency bands from 1 GHz to 86 GHz; 1985 Harmonised Standard covering the essential requirements of 1986 article 3.2 of Directive 2014/53/EU", EN 302 217-2 1987 V3.1.1 , May 2017. 1989 [G.808.1] "SERIES G: TRANSMISSION SYSTEMS AND MEDIA, DIGITAL SYSTEMS 1990 AND NETWORKS; Digital networks ; General aspects Generic 1991 protection switching ; Linear trail and subnetwork 1992 protection", ITU-T Rec. G.808.1 , May 2014. 1994 [G.826] "SERIES G: TRANSMISSION SYSTEMS AND MEDIA, DIGITAL SYSTEMS 1995 AND NETWORKS; Digital networks ; Quality and availability 1996 targets End-to-end error performance parameters and 1997 objectives for international, constant bit-rate digital 1998 paths and connections", ITU-T Rec. G.826 , December 2002. 2000 [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate 2001 Requirement Levels", BCP 14, RFC 2119, 2002 DOI 10.17487/RFC2119, March 1997, 2003 . 2005 [RFC3688] Mealling, M., "The IETF XML Registry", BCP 81, RFC 3688, 2006 DOI 10.17487/RFC3688, January 2004, 2007 . 2009 [RFC5246] Dierks, T. and E. Rescorla, "The Transport Layer Security 2010 (TLS) Protocol Version 1.2", RFC 5246, 2011 DOI 10.17487/RFC5246, August 2008, 2012 . 2014 [RFC6020] Bjorklund, M., Ed., "YANG - A Data Modeling Language for 2015 the Network Configuration Protocol (NETCONF)", RFC 6020, 2016 DOI 10.17487/RFC6020, October 2010, 2017 . 2019 [RFC6241] Enns, R., Ed., Bjorklund, M., Ed., Schoenwaelder, J., Ed., 2020 and A. Bierman, Ed., "Network Configuration Protocol 2021 (NETCONF)", RFC 6241, DOI 10.17487/RFC6241, June 2011, 2022 . 2024 [RFC6242] Wasserman, M., "Using the NETCONF Protocol over Secure 2025 Shell (SSH)", RFC 6242, DOI 10.17487/RFC6242, June 2011, 2026 . 2028 [RFC6991] Schoenwaelder, J., Ed., "Common YANG Data Types", 2029 RFC 6991, DOI 10.17487/RFC6991, July 2013, 2030 . 2032 [RFC7224] Bjorklund, M., "IANA Interface Type YANG Module", 2033 RFC 7224, DOI 10.17487/RFC7224, May 2014, 2034 . 2036 [RFC8040] Bierman, A., Bjorklund, M., and K. Watsen, "RESTCONF 2037 Protocol", RFC 8040, DOI 10.17487/RFC8040, January 2017, 2038 . 2040 [RFC8174] Leiba, B., "Ambiguity of Uppercase vs Lowercase in RFC 2041 2119 Key Words", BCP 14, RFC 8174, DOI 10.17487/RFC8174, 2042 May 2017, . 2044 [RFC8341] Bierman, A. and M. Bjorklund, "Network Configuration 2045 Access Control Model", STD 91, RFC 8341, 2046 DOI 10.17487/RFC8341, March 2018, 2047 . 2049 [RFC8343] Bjorklund, M., "A YANG Data Model for Interface 2050 Management", RFC 8343, DOI 10.17487/RFC8343, March 2018, 2051 . 2053 [TR102311] 2054 "Fixed Radio Systems; Point-to-point equipment; Specific 2055 aspects of the spatial frequency reuse method", ETSI TR 2056 102 311 V1.2.1 , November 2015. 2058 9.2. Informative References 2060 [I-D.ahlberg-ccamp-microwave-radio-link] 2061 Ahlberg, J., Carlson, J., Lund, H., Olausson, T., Ye, M., 2062 and M. Vaupotic, "Microwave Radio Link YANG Data Models", 2063 draft-ahlberg-ccamp-microwave-radio-link-01 (work in 2064 progress), May 2016. 2066 [I-D.ietf-ccamp-microwave-framework] 2067 Ahlberg, J., Ye, M., Li, X., Contreras, L., and C. 2068 Bernardos, "A framework for Management and Control of 2069 microwave and millimeter wave interface parameters", 2070 draft-ietf-ccamp-microwave-framework-07 (work in 2071 progress), June 2018. 2073 [ONF-model] 2074 "Microwave Information Model", version 1.0 , December 2075 2016, 2076 . 2080 [RFC8340] Bjorklund, M. and L. Berger, Ed., "YANG Tree Diagrams", 2081 BCP 215, RFC 8340, DOI 10.17487/RFC8340, March 2018, 2082 . 2084 [RFC8342] Bjorklund, M., Schoenwaelder, J., Shafer, P., Watsen, K., 2085 and R. Wilton, "Network Management Datastore Architecture 2086 (NMDA)", RFC 8342, DOI 10.17487/RFC8342, March 2018, 2087 . 2089 Appendix A. Example: 1+0 and 2+0 configuration instances 2091 This section gives simple examples of 1+0 and 2+0 instance using the 2092 YANG module defined in this draft. The examples are not intended as 2093 a complete module for 1+0 and 2+0 configuration. 2095 A.1 1+0 instance 2096 Figure A-1 shows a 1+0 example. 2098 /--------- Radio Link ---------\ 2099 Near End Far End 2101 +---------------+ +---------------+ 2102 | Radio Link | | Radio Link | 2103 | Terminal - A | | Terminal - B | 2104 | | | | 2105 | | | | 2106 | +-----------+ | | +-----------+ | 2107 | | | | Carrier A | | | | 2108 | | Carrier | |<--------->| | Carrier | | 2109 | |Termination| | | |Termination| | 2110 | | -1 | | | | -1 | | 2111 | +-----------+ | | +-----------+ | 2112 | | | | 2113 | | | | 2114 +---------------+ +---------------+ 2116 \--- Microwave Node ---/ \--- Microwave Node ---/ 2117 Figure A-1 1+0 example 2119 The following instance shows the 1+0 configuration of 2120 Near End node. 2122 "interface": [ 2123 { 2124 //RLT-A 2125 "name": "RLT-A", 2126 "description": "Radio Link Terminal A", 2127 "type": "mrl:radio-link-terminal", 2128 "id": "RLT-A", 2129 "mode": "one-plus-zero", 2130 "carrier-terminations": [ 2131 "RLT-A:CT-1", 2132 ], 2133 "tdm-connections": [ 2134 "tdm-type": "E1", 2135 "tdm-connections": "4", 2136 ] 2137 } 2139 { 2140 //CT-1 2141 "name": "RLT-A:CT-1", 2142 "description": "Carrier Termination 1", 2143 "type": "mrl:carrier-termination", 2144 "carrier-id": "A", 2145 "tx-enabled": true, 2146 "tx-frequency": 10728000, 2147 "duplex-distance": 644000, 2148 "channel-separation": 28, 2149 "polarization": not-specified, 2150 "rtpc": { 2151 "maximum-nominal-power": 20, 2152 } 2153 "single":{ 2154 "selected-cm": "qam-512", 2155 } 2156 }, 2157 ] 2159 A.2 2+0 instance 2161 Figure A-2 shows a 2+0 example. 2163 /--------- Radio Link ---------\ 2164 Near End Far End 2166 +---------------+ +---------------+ 2167 | Radio Link | | Radio Link | 2168 | Terminal -A | | Terminal -B | 2169 | | | | 2170 | | | | 2171 | +-----------+ | | +-----------+ | 2172 | | | | Carrier A | | | | 2173 | | Carrier | |<--------->| | Carrier | | 2174 | |Termination| | | |Termination| | 2175 | | -1 | | | | -1 | | 2176 | +-----------+ | | +-----------+ | 2177 | | | | 2178 | +-----------+ | | +-----------+ | 2179 | | | | Carrier B | | | | 2180 | | Carrier | |<--------->| | Carrier | | 2181 | |Termination| | | |Termination| | 2182 | | -2 | | | | -2 | | 2183 | +-----------+ | | +-----------+ | 2184 | | | | 2185 +---------------+ +---------------+ 2187 \--- Microwave Node ---/ \--- Microwave Node ---/ 2188 Figure A-2 2+0 example 2190 The following instance shows the 2+0 configuration of 2191 Near End node. 2193 "interface": [ 2194 { 2195 //RLT-A 2196 "name": "RLT-A", 2197 "description": "Radio Link Terminal A", 2198 "type": "mrl:radio-link-terminal", 2199 "id": "RLT-A", 2200 "mode": "two-plus-zero", 2201 "carrier-terminations": [ 2202 "RLT-A:CT-1", 2203 "RLT-A:CT-2" 2204 ], 2205 "tdm-connections": [ 2206 "tdm-type": "E1", 2207 "tdm-connections": "4", 2208 ] 2209 } 2211 { 2212 //CT-1 2213 "name": "RLT-A:CT-1", 2214 "description": "Carrier Termination 1", 2215 "type": "mrl:carrier-termination", 2216 "carrier-id": "A", 2217 "tx-enabled": true, 2218 "tx-frequency": 10728000, 2219 "duplex-distance": 644000, 2220 "channel-separation": 28, 2221 "polarization": not-specified, 2222 "rtpc": { 2223 "maximum-nominal-power": 20, 2224 } 2225 "single":{ 2226 "selected-cm": "qam-512", 2227 } 2228 }, 2230 { 2231 //CT-2 2232 "name": "RLT-A:CT-2", 2233 "description": "Carrier Termination 2", 2234 "type": "mrl:carrier-termination", 2235 "carrier-id": "B", 2236 "tx-enabled": true, 2237 "tx-oper-status": on 2238 "tx-frequency": 10618000, 2239 "duplex-distance": 644000, 2240 "channel-separation": 28, 2241 "polarization": not-specified, 2242 "rtpc": { 2243 "maximum-nominal-power": 20, 2244 } 2245 "single":{ 2246 "selected-cm": "qam-512", 2247 } 2248 }, 2249 ] 2251 A.3 2+0 XPIC instance 2253 The following instance shows the XPIC configuration of 2254 Near End node. 2256 "interface": [ 2257 { 2258 //RLT-A 2259 "name": "RLT-A", 2260 "description": "Radio Link Terminal A", 2261 "type": "mrl:radio-link-terminal", 2262 "id": "RLT-A", 2263 "mode": "two-plus-zero", 2264 "carrier-terminations": [ 2265 "RLT-A:CT-1", 2266 "RLT-A:CT-2" 2267 ], 2268 "xpic-pairs": [ 2269 "RLT-A:CT-1", 2270 "RLT-A:CT-2" 2271 ] 2272 "tdm-connections": [ 2273 "tdm-type": "E1", 2274 "tdm-connections": "4", 2275 ] 2276 } 2278 { 2279 //CT-1 2280 "name": "RLT-A:CT-1", 2281 "description": "Carrier Termination 1", 2282 "type": "mrl:carrier-termination", 2283 "carrier-id": "A", 2284 "tx-enabled": true, 2285 "tx-frequency": 10728000, 2286 "duplex-distance": 644000, 2287 "channel-separation": 28, 2288 "polarization": not-specified, 2289 "rtpc": { 2290 "maximum-nominal-power": 20, 2291 } 2292 "single":{ 2293 "selected-cm": "qam-512", 2294 } 2295 }, 2297 { 2298 //CT-2 2299 "name": "RLT-A:CT-2", 2300 "description": "Carrier Termination 2", 2301 "type": "mrl:carrier-termination", 2302 "carrier-id": "B", 2303 "tx-enabled": true, 2304 "tx-oper-status": on 2305 "tx-frequency": 10618000, 2306 "duplex-distance": 644000, 2307 "channel-separation": 28, 2308 "polarization": not-specified, 2309 "rtpc": { 2310 "maximum-nominal-power": 20, 2311 } 2312 "single":{ 2313 "selected-cm": "qam-512", 2314 } 2315 }, 2316 ] 2318 Appendix B. Contributors 2319 Koji Kawada 2320 NEC Corporation 2321 1753, Shimonumabe Nakahara-ku 2322 Kawasaki, Kanagawa 211-8666 2323 Japan 2325 Email: k-kawada@ah.jp.nec.com 2327 Carlos J. Bernardos 2328 Universidad Carlos III de Madrid 2329 Av. Universidad, 30 2330 Leganes, Madrid 28911 2331 Spain (ESP) 2333 Email: cjbc@it.uc3m.es 2335 Authors' Addresses 2337 Jonas Ahlberg 2338 Ericsson AB 2339 Lindholmspiren 11 2340 Goteborg 417 56 2341 Sweden 2343 Email: jonas.ahlberg@ericsson.com 2345 Ye Min 2346 Huawei Technologies 2347 No.1899, Xiyuan Avenue 2348 Chengdu 611731 2349 P.R.China 2351 Email: amy.yemin@huawei.com 2353 Xi Li 2354 NEC Laboratories Europe 2355 Kurfursten-Anlage 36 2356 Heidelberg 69115 2357 Germany 2359 Email: Xi.Li@neclab.eu 2360 Daniela Spreafico 2361 Nokia - IT 2362 Via Energy Park, 14 2363 Vimercate (MI) 20871 2364 Italy 2366 Email: daniela.spreafico@nokia.com 2368 Marko Vaupotic 2369 Aviat Networks 2370 Motnica 9 2371 Trzin-Ljubljana 1236 2372 Slovenia 2374 Email: Marko.Vaupotic@Aviatnet.com