idnits 2.17.1 draft-ietf-ccamp-mw-yang-05.txt: Checking boilerplate required by RFC 5378 and the IETF Trust (see https://trustee.ietf.org/license-info): ---------------------------------------------------------------------------- No issues found here. Checking nits according to https://www.ietf.org/id-info/1id-guidelines.txt: ---------------------------------------------------------------------------- No issues found here. Checking nits according to https://www.ietf.org/id-info/checklist : ---------------------------------------------------------------------------- No issues found here. Miscellaneous warnings: ---------------------------------------------------------------------------- == The copyright year in the IETF Trust and authors Copyright Line does not match the current year == The document doesn't use any RFC 2119 keywords, yet seems to have RFC 2119 boilerplate text. -- The document date (March 30, 2018) is 2218 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' -- Possible downref: Non-RFC (?) normative reference: ref. 'TR102311' ** Obsolete normative reference: RFC 5246 (Obsoleted by RFC 8446) == Outdated reference: A later version (-07) exists of draft-ietf-ccamp-microwave-framework-05 Summary: 1 error (**), 0 flaws (~~), 3 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: October 1, 2018 Huawei Technologies 6 X. Li 7 NEC Laboratories Europe GmbH 8 D. Spreafico 9 Nokia - IT 10 M. Vaupotic 11 Aviat Networks 12 March 30, 2018 14 A YANG Data Model for Microwave Radio Link 15 draft-ietf-ccamp-mw-yang-05 17 Abstract 19 This document defines a YANG data model for control and management 20 of 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 Status of This Memo 28 This Internet-Draft is submitted in full conformance with the 29 provisions of BCP 78 and BCP 79. 31 Internet-Drafts are working documents of the Internet Engineering 32 Task Force (IETF). Note that other groups may also distribute 33 working documents as Internet-Drafts. The list of current Internet- 34 Drafts is at http://datatracker.ietf.org/drafts/current/. 36 Internet-Drafts are draft documents valid for a maximum of six months 37 and may be updated, replaced, or obsoleted by other documents at any 38 time. It is inappropriate to use Internet-Drafts as reference 39 material or to cite them other than as "work in progress". 41 This Internet-Draft will expire on October 1, 2018. 43 // RFC Ed.: replace all XXXX throughout the document with actual 44 // RFC numbers and remove this note 46 Copyright Notice 48 Copyright (c) 2018 IETF Trust and the persons identified as the 49 document authors. All rights reserved. 51 This document is subject to BCP 78 and the IETF Trust's Legal 52 Provisions Relating to IETF Documents 53 (http://trustee.ietf.org/license-info) in effect on the date of 54 publication of this document. Please review these documents 55 carefully, as they describe your rights and restrictions with respect 56 to this document. Code Components extracted from this document must 57 include Simplified BSD License text as described in Section 4.e of 58 the Trust Legal Provisions and are provided without warranty as 59 described in the Simplified BSD License. 61 Table of Contents 63 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 2 64 1.1. Terminology and Definitions . . . . . . . . . . . . . . . 3 65 1.2. Tree Structure . . . . . . . . . . . . . . . . . . . . . . 4 66 2. Requirements Language . . . . . . . . . . . . . . . . . . . . 4 67 3. Microwave Radio Link YANG Data Model. . . . . . . . . . . . . 4 68 3.1. YANG Tree . . . . . . . . . . . . . . . . . . . . . . . . 4 69 3.2. Explanation of the Microwave Data Model . . . . . . . . . 6 70 4. Microwave Radio Link YANG Module . . . . . . . . . . . . . . 6 71 5. Interface Protection YANG Module . . . . . . . . . . . . . . 24 72 6. Microwave Types YANG Module . . . . . . . . . . . . . . . . . 31 73 7. Security Considerations . . . . . . . . . . . . . . . . . . . 38 74 8. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 40 75 9. References . . . . . . . . . . . . . . . . . . . . . . . . . 40 76 9.1. Normative References . . . . . . . . . . . . . . . . . . 40 77 9.2. Informative References . . . . . . . . . . . . . . . . . 42 78 Appendix A. Example: 1+0 and 2+0 configuration instances. . . . . 43 79 Appendix B. Contributors. . . . . . . . . . . . . . . . . . . . . 46 80 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 46 82 1. Introduction 84 This document defines a YANG data model for management and control of 85 the radio link interface(s) and the relationship to packet (typically 86 Ethernet) and/or TDM interfaces in a microwave/millimeter wave node. 87 ETSI EN 302 217 series defines the characteristics and requirements 88 of microwave/millimeter wave equipment and antennas. Especially ETSI 89 EN 302 217-2 [EN302217-2] specifies the essential parameters for 90 the systems operating from 1.4GHz to 86GHz. The data model includes 91 configuration and state data according to the new Network Management 92 Datastore Architecture [RFC8342]. 94 The design of the data model follows the framework for management and 95 control of microwave and millimeter wave interface parameters defined 96 in [I-D.ietf-ccamp-microwave-framework]. This framework identifies 97 the need and the scope of the YANG data model, the use cases and 98 requirements that the model needs to support. Moreover, it provides 99 a detailed gap analysis to identify the missing parameters and 100 functionalities of the existing and established models to support the 101 specified use cases and requirements, and based on that recommends 102 how the gaps should be filled with the development of the new model. 103 According to the conclusion of the gap analysis, the structure of the 104 data model is based on the structure defined in 105 [I-D.ahlberg-ccamp-microwave-radio-link] and it augments [RFC8343] 106 to align with the same structure for management of the packet 107 interfaces. More specifically, the model will include interface 108 layering to manage the capacity provided by a radio link terminal for 109 the associated Ethernet and TDM interfaces, using the principles for 110 interface layering described in [RFC8343] as a basis. 112 The data nodes for management of the interface protection 113 functionality is broken out into a separate and generic YANG data 114 module in order to make it available also for other interface types. 116 The designed YANG data model uses established microwave equipment 117 and radio standards, such as ETSI EN 302 217-2, and the IETF: Radio 118 Link Model[I-D.ahlberg-ccamp-microwave-radio-link] and the ONF: 119 Microwave Modeling[ONF-model] as the basis for the definition of the 120 detailed leafs/parameters, and proposes new ones to cover identified 121 gaps which are analyzed in[I-D.ietf-ccamp-microwave-framework]. 123 1.1. Terminology and Definitions 125 The following terms are used in this document: 127 Carrier Termination (CT) is an interface for the capacity provided 128 over the air by a single carrier. It is typically defined by its 129 transmitting and receiving frequencies. 131 Radio Link Terminal (RLT) is an interface providing packet capacity 132 and/or TDM capacity to the associated Ethernet and/or TDM interfaces 133 in a node and used for setting up a transport service over a 134 microwave/millimeter wave link. 136 The following acronyms are used in this document: 138 ACM Adaptive Coding Modulation 140 ATPC Automatic Transmit Power Control 142 BPSK Binary Phase-Shift Keying 144 CM Coding Modulation 145 CT Carrier Termination 147 RLT Radio Link Terminal 149 RTPC Remote Transmit Power Control 151 XPIC Cross Polarization Interference Cancellation 153 MIMO Multiple-Input Multiple-Output 155 QAM Quadrature Amplitude Modulation 157 QPSK Quadrature Phase-Shift Keying 159 1.2. Tree Structure 161 A simplified graphical representation of the data model is used in 162 chapter 3.1 of this this document. The meaning of the symbols in 163 these diagrams is defined in [RFC8340]. 165 2. Requirements Language 167 The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", 168 "SHOULD", "SHOULD NOT", "RECOMMENDED", "NOT RECOMMENDED", "MAY", and 169 "OPTIONAL" in this document are to be interpreted as described in 170 BCP 14 [RFC2119] [RFC8174] when, and only when, they appear in all 171 capitals, as shown here. 173 3. Microwave Radio Link YANG Data Model 175 3.1. YANG Tree 177 module: ietf-microwave-radio-link 178 +--rw radio-link-protection-groups 179 | +--rw protection-group* [name] 180 | +--rw name string 181 | +--rw architecture-type? identityref 182 | +--rw members* if:interface-ref 183 | +--rw operation-type? enumeration 184 | +--rw working-entity* if:interface-ref 185 | +--rw revertive-wait-to-restore? uint16 186 | +--rw hold-off-timer? uint16 187 | +--rw status? identityref 188 | +---x external-commands 189 | +---w input 190 | +---w external-command? identityref 191 +--rw xpic-pairs {xpic}? 192 | +--rw xpic-pair* [name] 193 | +--rw name string 194 | +--rw enabled? boolean 195 | +--rw members* if:interface-ref 196 +--rw mimo-groups {mimo}? 197 +--rw mimo-group* [name] 198 +--rw name string 199 +--rw enabled? boolean 200 +--rw members* if:interface-ref 202 augment /if:interfaces/if:interface: 203 +--rw id? string 204 +--rw mode identityref 205 +--rw carrier-terminations* if:interface-ref 206 +--rw rlp-groups* 207 | -> /radio-link-protection-groups/protection-group/name 208 +--rw xpic-pairs* -> /xpic-pairs/xpic-pair/name 209 | {xpic}? 210 +--rw mimo-groups* -> /mimo-groups/mimo-group/name 211 | {mimo}? 212 +--rw tdm-connections* [tdm-type] {tdm}? 213 +--rw tdm-type identityref 214 +--rw tdm-connections uint16 216 augment /if:interfaces/if:interface: 217 +--rw carrier-id? string 218 +--rw tx-enabled? boolean 219 +--ro tx-oper-status? enumeration 220 +--rw tx-frequency uint32 221 +--rw rx-frequency? uint32 222 +--rw duplex-distance? uint32 223 +--rw channel-separation uint32 224 +--rw polarization? enumeration 225 +--rw power-mode enumeration 226 +--rw maximum-nominal-power power 227 +--rw atpc-lower-threshold power 228 +--rw atpc-upper-threshold power 229 +--ro actual-transmitted-level? power 230 +--ro actual-received-level? power 231 +--rw coding-modulation-mode enumeration 232 +--rw selected-cm identityref 233 +--rw selected-min-acm identityref 234 +--rw selected-max-acm identityref 235 +--ro actual-tx-cm? identityref 236 +--ro actual-snir? decimal64 237 +--ro actual-xpi? decimal64 {xpic}? 238 +--rw ct-performance-thresholds 239 | +--rw received-level-alarm-threshold? power 240 | +--rw transmitted-level-alarm-threshold? power 241 | +--rw ber-alarm-threshold? enumeration 242 +--rw if-loop? enumeration 243 +--rw rf-loop? enumeration 244 +--ro capabilities 245 | +--ro min-tx-frequency? uint32 246 | +--ro max-tx-frequency? uint32 247 | +--ro min-rx-frequency? uint32 248 | +--ro max-rx-frequency? uint32 249 | +--ro minimum-power? power 250 | +--ro maximum-available-power? power 251 | +--ro available-min-acm? identityref 252 | +--ro available-max-acm? identityref 253 +--ro error-performance-statistics 254 | +--ro bbe? yang:counter32 255 | +--ro es? yang:counter32 256 | +--ro ses? yang:counter32 257 | +--ro uas? yang:counter32 258 +--ro radio-performance-statistics 259 +--ro min-rltm? power 260 +--ro max-rltm? power 261 +--ro min-tltm? power 262 +--ro max-tltm? power 264 3.2. Explanation of the Microwave Data Model 266 The leafs in the Interface Management Module augmented by Radio Link 267 Terminal (RLT) and Carrier Termination (CT) are not always 268 applicable. 270 "/interfaces/interface/enabled" is not applicable for RLT. Enable 271 and disable of an interface is done in the constituent CTs. 273 The packet related measurements "in-octets", "in-unicast-pkts", "in- 274 broadcast-pkts", "in-multicast-pkts", "in-discards", "in-errors", 275 "in-unknown-protos", "out-octets", "out-unicast-pkts", "out- 276 broadcast-pkts", "out-multicast-pkts", "out-discards", "out-errors" 277 are not within the scope of the microwave radio link domain and 278 therefore not applicable for RLT and CT. 280 4. Microwave Radio Link YANG Module 282 This module imports typedefs and modules from [RFC6991], 283 [RFC8343] and [RFC7224], and it references [TR102311], 284 [EN302217-1], [EN301129], and [G.826]. 286 file "ietf-microwave-radio-link@2018-03-30.yang" 288 module ietf-microwave-radio-link { 289 yang-version 1.1; 290 namespace "urn:ietf:params:xml:ns:yang:ietf-microwave-radio-link"; 291 prefix mrl; 292 import ietf-yang-types { 293 prefix yang; 294 reference "RFC 6991"; 295 } 297 import ietf-interfaces { 298 prefix if; 299 reference "RFC 8343"; 300 } 302 import ietf-interface-protection { 303 prefix ifprot; 304 reference "RFC XXXX"; 305 } 307 import ietf-microwave-types { 308 prefix mw-types; 309 reference "RFC XXXX"; 310 } 312 organization 313 "Internet Engineering Task Force (IETF) CCAMP WG"; 315 contact 316 "WG List: 318 ID-draft editors: 319 // RFC Ed.: replace ID-draft editors with Editors and remove 320 // this note 321 Jonas Ahlberg (jonas.ahlberg@ericsson.com); 322 Min Ye (amy.yemin@huawei.com); 323 Xi Li (Xi.Li@neclab.eu); 324 Daniela Spreafico (daniela.spreafico@nokia.com) 325 Marko Vaupotic (Marko.Vaupotic@aviatnet.com)"; 327 description 328 "This is a module for the entities in 329 a generic microwave system. 331 Copyright (c) 2018 IETF Trust and the persons identified as 332 authors of the code. All rights reserved. 333 Redistribution and use in source and binary forms, with or 334 without modification, is permitted pursuant to, and subject 335 to the license terms contained in, the Simplified BSD License 336 set forth in Section 4.c of the IETF Trust's Legal Provisions 337 Relating to IETF Documents 338 (http://trustee.ietf.org/license-info). 340 This version of this YANG module is part of RFC XXXX; see 341 the RFC itself for full legal notices. 343 Copyright (c) 2018 IETF Trust and the persons identified as 344 authors of the code. All rights reserved."; 346 revision 2018-03-30 { 347 description "Initial revision."; 348 reference "RFC XXXX: A YANG Data Model for Microwave Radio Link"; 349 } 351 /* 352 * Features 353 */ 355 feature xpic { 356 description 357 "Indicates that the device supports XPIC."; 358 reference "ETSI TR 102 311"; 359 } 361 feature mimo { 362 description 363 "Indicates that the device supports MIMO."; 364 reference "ETSI TR 102 311"; 365 } 367 feature tdm { 368 description 369 "Indicates that the device supports TDM."; 370 } 372 /* 373 * Typedefs 374 */ 376 typedef power { 377 type decimal64 { 378 fraction-digits 1; 379 } 380 description 381 "Type used for power values, selected and measured."; 382 } 384 /* 385 * Radio Link Terminal (RLT) 386 */ 388 augment "/if:interfaces/if:interface" { 389 when "if:type = 'mw-types:radio-link-terminal'"; 390 description 391 "Addition of data nodes for radio link terminal to 392 the standard Interface data model, for interfaces of 393 the type 'radio-link-terminal'."; 395 leaf id { 396 type string; 397 default ""; 398 description 399 "ID of the radio link terminal. Used by far-end when 400 checking that it's connected to the correct RLT."; 401 } 403 leaf mode { 404 type identityref { 405 base mw-types:rlt-mode; 406 } 407 mandatory true; 408 description 409 "A description of the mode in which the radio link 410 terminal is configured. The format is X plus Y. 411 X represent the number of bonded carrier terminations. 412 Y represent the number of protecting carrier 413 terminations."; 414 } 416 leaf-list carrier-terminations { 417 type if:interface-ref; 418 must "/if:interfaces/if:interface[if:name = current()]" 419 + "/if:type = 'mw-types:carrier-termination'" { 420 description 421 "The type of interface must be 422 'carrier-termination'."; 423 } 424 min-elements 1; 425 description 426 "A list of references to carrier terminations 427 included in the radio link terminal."; 428 } 430 leaf-list rlp-groups { 431 type leafref { 432 path "/mrl:radio-link-protection-groups/" 433 + "mrl:protection-group/mrl:name"; 434 } 435 description 436 "A list of references to the carrier termination 437 groups configured for radio link protection in this 438 radio link terminal."; 439 } 441 leaf-list xpic-pairs { 442 if-feature xpic; 443 type leafref { 444 path "/mrl:xpic-pairs/mrl:xpic-pair/mrl:name"; 445 } 446 description 447 "A list of references to the XPIC pairs used in this 448 radio link terminal. One pair can be used by two 449 terminals."; 450 reference "ETSI TR 102 311"; 451 } 453 leaf-list mimo-groups { 454 if-feature mimo; 455 type leafref { 456 path "/mrl:mimo-groups/mrl:mimo-group/mrl:name"; 457 } 458 description 459 "A reference to the MIMO group used in this 460 radio link terminal. One group can be used by more 461 than one terminal."; 462 reference "ETSI TR 102 311"; 463 } 465 list tdm-connections { 466 if-feature tdm; 467 key "tdm-type"; 468 description 469 "A list stating the number of active TDM connections 470 of a specified tdm-type that is configured to be 471 supported by the RLT."; 472 leaf tdm-type { 473 type identityref { 474 base mw-types:tdm-type; 475 } 476 description 477 "The type of TDM connection, which also indicates 478 the supported capacity."; 479 } 480 leaf tdm-connections { 481 type uint16; 482 mandatory true; 483 description 484 "Number of connections of the specified type."; 485 } 486 } 487 } 489 /* 490 * Carrier Termination 491 */ 493 augment "/if:interfaces/if:interface" { 494 when "if:type = 'mw-types:carrier-termination'"; 495 description 496 "Addition of data nodes for carrier termination to 497 the standard Interface data model, for interfaces 498 of the type 'carrier-termination'."; 500 leaf carrier-id { 501 type string; 502 default "A"; 503 description 504 "ID of the carrier. (e.g. A, B, C or D) 505 Used in XPIC & MIMO configurations to check that 506 the carrier termination is connected to the correct 507 far-end carrier termination. Should be the same 508 carrier ID on both sides of the hop. 509 Defaulted when not MIMO or XPIC."; 510 } 512 leaf tx-enabled { 513 type boolean; 514 default "false"; 515 description 516 "Disables (false) or enables (true) the transmitter. 517 Only applicable when the interface is enabled 518 (interface:enabled = true) otherwise it's always 519 disabled."; 520 } 522 leaf tx-oper-status { 523 type enumeration { 524 enum "off" { 525 description "Transmitter is off."; 526 } 527 enum "on" { 528 description "Transmitter is on."; 529 } 530 enum "standby" { 531 description "Transmitter is in standby."; 532 } 533 } 534 config false; 535 description 536 "Shows the operative status of the transmitter."; 537 } 539 leaf tx-frequency { 540 type uint32; 541 units "kHz"; 542 mandatory true; 543 description 544 "Selected transmitter frequency."; 545 } 546 leaf rx-frequency { 547 type uint32; 548 units "kHz"; 549 description 550 "Selected receiver frequency. 551 Overrides existing value in duplex-distance. 552 Calculated from tx-frequency and duplex-distance if 553 only duplex-distance is configured. 554 Must match duplex-distance if both leaves are 555 configured in a single operation."; 556 } 558 leaf duplex-distance { 559 type uint32; 560 units "kHz"; 561 description 562 "Distance between Tx & Rx frequencies. 563 Used to calculate rx-frequency when 564 rx-frequency is not specifically configured. 565 Overrides existing value in rx-frequency. 566 Calculated from tx-frequency and rx-frequency if only 567 rx-frequency is configured. 568 Must match rx-frequency if both leaves are configured 569 in a single operation."; 570 } 572 leaf channel-separation { 573 type uint32; 574 units "kHz"; 575 mandatory true; 576 description 577 "The amount of bandwidth allocated to a carrier. The distance 578 between adjacent channels in a radio frequency channels 579 arrangement"; 580 reference "ETSI EN 302 217-1"; 581 } 583 leaf polarization { 584 type enumeration { 585 enum "horizontal" { 586 description "Horizontal polarization."; 587 } 588 enum "vertical" { 589 description "Vertical polarization."; 590 } 591 enum "not-specified" { 592 description "Polarization not specified."; 593 } 594 } 595 default "not-specified"; 596 description 597 "Polarization - A textual description for info only."; 598 } 600 leaf power-mode { 601 type enumeration { 602 enum rtpc { 603 description 604 "Remote Transmit Power Control (RTPC)."; 605 reference "ETSI EN 302 217-1"; 606 } 608 enum atpc { 609 description 610 "Automatic Transmit Power Control (ATPC)."; 611 reference "ETSI EN 302 217-1"; 612 } 613 } 614 mandatory true; 615 description 616 "A choice of Remote Transmit Power Control (RTPC) 617 or Automatic Transmit Power Control (ATPC)."; 618 } 620 leaf maximum-nominal-power { 621 type power { 622 range "-99..40"; 623 } 624 units "dBm"; 625 mandatory true; 626 description 627 "Selected output power in RTPC mode and selected 628 maximum output power in ATPC mode. Minimum output 629 power in ATPC mode is the same as the system 630 capability, available-min-output-power."; 631 reference "ETSI EN 302 217-1"; 632 } 634 leaf atpc-lower-threshold { 635 when "../power-mode = 'atpc'"; 636 type power { 637 range "-99..-30"; 638 } 639 units "dBm"; 640 mandatory true; 641 description 642 "The lower threshold for the input power at far-end 643 used in the ATPC mode."; 644 reference "ETSI EN 302 217-1"; 645 } 646 leaf atpc-upper-threshold { 647 when "../power-mode = 'atpc'"; 648 type power { 649 range "-99..-30"; 650 } 651 units "dBm"; 652 mandatory true; 653 description 654 "The upper threshold for the input power at far-end 655 used in the ATPC mode."; 656 reference "ETSI EN 302 217-1"; 657 } 659 leaf actual-transmitted-level { 660 type power { 661 range "-99..40"; 662 } 663 units "dBm"; 664 config false; 665 description 666 "Actual transmitted power level (0.1 dBm resolution)."; 667 reference "ETSI EN 301 129"; 668 } 670 leaf actual-received-level { 671 type power { 672 range "-99..-20"; 673 } 674 units "dBm"; 675 config false; 676 description 677 "Actual received power level (0.1 dBm resolution)."; 678 reference "ETSI EN 301 129"; 679 } 681 leaf coding-modulation-mode { 682 type enumeration { 683 enum single { 684 description "a single modulation order only."; 685 reference "ETSI EN 302 217-1"; 686 } 687 enum adaptive { 688 description "Adaptive coding/modulation."; 689 reference "ETSI EN 302 217-1"; 690 } 691 } 692 mandatory true; 693 description 694 "A selection of single or 695 adaptive coding/modulation mode."; 696 } 697 leaf selected-cm { 698 when "../coding-modulation-mode = 'single'"; 699 type identityref { 700 base mw-types:coding-modulation; 701 } 702 mandatory true; 703 description 704 "Selected the single coding/modulation."; 705 } 707 leaf selected-min-acm { 708 when "../coding-modulation-mode = 'adaptive'"; 709 type identityref { 710 base mw-types:coding-modulation; 711 } 712 mandatory true; 713 description 714 "Selected minimum coding/modulation. 715 Adaptive coding/modulation shall not go 716 below this value."; 717 } 719 leaf selected-max-acm { 720 when "../coding-modulation-mode = 'adaptive'"; 721 type identityref { 722 base mw-types:coding-modulation; 723 } 724 mandatory true; 725 description 726 "Selected maximum coding/modulation. 727 Adaptive coding/modulation shall not go 728 above this value."; 729 } 731 leaf actual-tx-cm { 732 type identityref { 733 base mw-types:coding-modulation; 734 } 735 config false; 736 description 737 "Actual coding/modulation in transmitting direction."; 738 } 740 leaf actual-snir { 741 type decimal64 { 742 fraction-digits 1; 743 range "0..99"; 744 } 745 units "dB"; 746 config false; 747 description 748 "Actual signal to noise plus interference ratio. 749 (0.1 dB resolution)."; 750 } 752 leaf actual-xpi { 753 if-feature xpic; 754 type decimal64 { 755 fraction-digits 1; 756 range "0..99"; 757 } 758 units "dB"; 759 config false; 760 description 761 "The actual carrier to cross-polar interference. 762 Only valid if XPIC is enabled. (0.1 dB resolution)."; 763 reference "ETSI TR 102 311"; 764 } 766 container ct-performance-thresholds { 767 description 768 "Specification of thresholds for when alarms should 769 be sent and cleared for various performance counters."; 771 leaf received-level-alarm-threshold { 772 type power { 773 range "-99..-30"; 774 } 775 units "dBm"; 776 default "-99"; 777 description 778 "An alarm is sent when the received power level is 779 below the specified threshold."; 780 reference "ETSI EN 301 129"; 781 } 783 leaf transmitted-level-alarm-threshold { 784 type power { 785 range "-99..40"; 786 } 787 units "dBm"; 788 default "-99"; 789 description 790 "An alarm is sent when the transmitted power level 791 is below the specified threshold."; 792 reference "ETSI EN 301 129"; 793 } 794 leaf ber-alarm-threshold { 795 type enumeration { 796 enum "10e-9" { 797 description "Threshold at 10e-9."; 798 } 799 enum "10e-8" { 800 description "Threshold at 10e-8."; 801 } 802 enum "10e-7" { 803 description "Threshold at 10e-7."; 804 } 805 enum "10e-6" { 806 description "Threshold at 10e-6."; 807 } 808 enum "10e-5" { 809 description "Threshold at 10e-5."; 810 } 811 enum "10e-4" { 812 description "Threshold at 10e-4."; 813 } 814 enum "10e-3" { 815 description "Threshold at 10e-3."; 816 } 817 enum "10e-2" { 818 description "Threshold at 10e-2."; 819 } 820 enum "10e-1" { 821 description "Threshold at 10e-1."; 822 } 823 } 824 default "10e-6"; 825 description 826 "Specification of at which BER an alarm should 827 be raised."; 828 reference "ETSI EN 302 217-1"; 829 } 830 } 832 leaf if-loop { 833 type enumeration { 834 enum disabled { 835 description "Disables the IF Loop."; 836 } 837 enum client { 838 description 839 "Loops the signal back to the client side."; 840 } 841 enum radio { 842 description 843 "Loops the signal back to the radio side."; 844 } 845 } 846 default "disabled"; 847 description 848 "Enable (client/radio) or disable (disabled) 849 the IF loop, which loops the signal back to 850 the client side or the radio side."; 851 } 853 leaf rf-loop { 854 type enumeration { 855 enum disabled { 856 description "Disables the RF Loop."; 857 } 858 enum client { 859 description 860 "Loops the signal back to the client side."; 861 } 862 enum radio { 863 description 864 "Loops the signal back to the radio side."; 865 } 866 } 867 default "disabled"; 868 description 869 "Enable (client/radio) or disable (disabled) 870 the RF loop, which loops the signal back to 871 the client side or the radio side."; 872 } 874 container capabilities { 875 config false; 876 description 877 "Capabilities of the installed equipment and 878 some selected configurations."; 880 leaf min-tx-frequency { 881 type uint32; 882 units "kHz"; 883 description 884 "Minimum Tx frequency possible to use."; 885 } 887 leaf max-tx-frequency { 888 type uint32; 889 units "kHz"; 890 description 891 "Maximum Tx frequency possible to use."; 892 } 893 leaf min-rx-frequency { 894 type uint32; 895 units "kHz"; 896 description 897 "Minimum Rx frequency possible to use."; 898 } 900 leaf max-rx-frequency { 901 type uint32; 902 units "kHz"; 903 description 904 "Maximum Tx frequency possible to use."; 905 } 907 leaf minimum-power { 908 type power; 909 units "dBm"; 910 description 911 "The minimum output power supported."; 912 reference "ETSI EN 302 217-1"; 913 } 915 leaf maximum-available-power { 916 type power; 917 units "dBm"; 918 description 919 "The maximum output power supported."; 920 reference "ETSI EN 302 217-1"; 921 } 923 leaf available-min-acm { 924 type identityref { 925 base mw-types:coding-modulation; 926 } 927 description 928 "Minimum coding-modulation possible to use."; 929 } 931 leaf available-max-acm { 932 type identityref { 933 base mw-types:coding-modulation; 934 } 935 description 936 "Maximum coding-modulation possible to use."; 937 } 938 } 940 container error-performance-statistics { 941 config false; 942 description 943 "ITU-T G.826 error performance statistics relevant for 944 a microwave/millimeter wave carrier."; 946 leaf bbe { 947 type yang:counter32; 948 units "number of block errors"; 949 description 950 "Number of Background Block Errors (BBE) during the 951 interval. A BBE is an errored block not occurring as 952 part of an SES."; 953 reference "ITU-T G.826"; 954 } 956 leaf es { 957 type yang:counter32; 958 units "seconds"; 959 description 960 "Number of Errored Seconds (ES) since last reset. 961 An ES is a one-second period with one or more errored 962 blocks or at least one defect."; 963 reference "ITU-T G.826"; 964 } 966 leaf ses { 967 type yang:counter32; 968 units "seconds"; 969 description 970 "Number of Severely Errored Seconds (SES) during the 971 interval. SES is a one-second period which contains 972 equal or more than 30% errored blocks or at least 973 one defect. SES is a subset of ES."; 974 reference "ITU-T G.826"; 975 } 977 leaf uas { 978 type yang:counter32; 979 units "seconds"; 980 description 981 "Number of Unavailable Seconds (UAS), that is, the 982 total time that the node has been unavailable during 983 a fixed measurement interval."; 984 reference "ITU-T G.826"; 985 } 986 } 988 container radio-performance-statistics { 989 config false; 990 description 991 "ETSI EN 301 129 radio physical interface statistics relevant 992 for a carrier termination."; 994 leaf min-rltm { 995 type power { 996 range "-99..-20"; 997 } 998 units "dBm"; 999 description 1000 "Minimum received power level since last reset."; 1001 reference "ETSI EN 301 129"; 1002 } 1004 leaf max-rltm { 1005 type power { 1006 range "-99..-20"; 1007 } 1008 units "dBm"; 1009 description 1010 "Maximum received power level since last reset."; 1011 reference "ETSI EN 301 129"; 1012 } 1014 leaf min-tltm { 1015 type power { 1016 range "-99..40"; 1017 } 1018 units "dBm"; 1019 description 1020 "Minimum transmitted power level since last reset."; 1021 reference "ETSI EN 301 129"; 1022 } 1024 leaf max-tltm { 1025 type power { 1026 range "-99..40"; 1027 } 1028 units "dBm"; 1029 description 1030 "Maximum transmitted power level since last reset."; 1031 reference "ETSI EN 301 129"; 1032 } 1033 } 1034 } 1036 /* 1037 * Radio Link Protection Groups 1038 */ 1040 container radio-link-protection-groups { 1041 description 1042 "Configuration of radio link protected groups (1+1) of 1043 carrier terminations in a radio link. More than one 1044 protected group per radio-link-terminal is allowed."; 1046 uses ifprot:protection-groups { 1048 refine protection-group/members { 1049 must "/if:interfaces/if:interface[if:name = current()]" 1050 + "/if:type = 'mw-types:carrier-termination'" { 1051 description 1052 "The type of a protection member must be 1053 'carrier-termination'."; 1054 } 1055 } 1057 refine protection-group/working-entity { 1058 must "/if:interfaces/if:interface[if:name = current()]" 1059 + "/if:type = 'mw-types:carrier-termination'" { 1060 description 1061 "The type of a working-entity must be 1062 'carrier-termination'."; 1063 } 1064 } 1065 } 1066 } 1068 /* 1069 * XPIC & MIMO groups - Configuration data nodes 1070 */ 1072 container xpic-pairs { 1073 if-feature xpic; 1074 description 1075 "Configuration of carrier termination pairs 1076 for operation in XPIC mode."; 1077 reference "ETSI TR 102 311"; 1079 list xpic-pair { 1080 key "name"; 1081 description 1082 "List of carrier termination pairs in XPIC mode."; 1084 leaf name { 1085 type string; 1086 description 1087 "Name used for identification of the XPIC pair."; 1088 } 1090 leaf enabled { 1091 type boolean; 1092 default "false"; 1093 description 1094 "Enable(true)/disable(false) XPIC"; 1095 } 1096 leaf-list members { 1097 type if:interface-ref; 1098 must "/if:interfaces/if:interface[if:name = current()]" 1099 + "/if:type = 'mw-types:carrier-termination'" { 1100 description 1101 "The type of a member must be 'carrier-termination'."; 1102 } 1103 min-elements 2; 1104 max-elements 2; 1105 description 1106 "Association to XPIC pairs used in the radio link 1107 terminal."; 1108 } 1109 } 1110 } 1112 container mimo-groups { 1113 if-feature mimo; 1114 description 1115 "Configuration of carrier terminations 1116 for operation in MIMO mode."; 1117 reference "ETSI TR 102 311"; 1119 list mimo-group { 1120 key "name"; 1121 description 1122 "List of carrier terminations in MIMO mode."; 1124 leaf name { 1125 type string; 1126 description 1127 "Name used for identification of the MIMO group."; 1128 } 1130 leaf enabled { 1131 type boolean; 1132 default "false"; 1133 description 1134 "Enable(true)/disable(false) MIMO"; 1135 } 1137 leaf-list members { 1138 type if:interface-ref; 1139 must "/if:interfaces/if:interface[if:name = current()]" 1140 + "/if:type = 'mw-types:carrier-termination'" { 1141 description 1142 "The type of a member must be 'carrier-termination'."; 1143 } 1144 min-elements 2; 1145 description 1146 "Association to a MIMO group if used in the radio 1147 link terminal."; 1148 } 1149 } 1150 } 1151 } 1153 1155 5. Interface Protection YANG Module 1157 The data nodes for management of the interface protection 1158 functionality is broken out from the Microwave Radio Link Module 1159 into a separate and generic YANG data module in order to make it 1160 available also for other interface types. 1162 This module imports modules from [RFC8343], and it references 1163 [G.808.1]. 1165 file "ietf-interface-protection@2018-03-30.yang" 1167 module ietf-interface-protection { 1168 yang-version 1.1; 1169 namespace "urn:ietf:params:xml:ns:yang:ietf-interface-protection"; 1170 prefix ifprot; 1172 import ietf-interfaces { 1173 prefix if; 1174 reference "RFC8343"; 1175 } 1177 organization 1178 "Internet Engineering Task Force (IETF) CCAMP WG"; 1179 contact 1180 "WG List: 1182 ID-draft editors: 1183 Jonas Ahlberg (jonas.ahlberg@ericsson.com); 1184 Min Ye (amy.yemin@huawei.com); 1185 Xi Li (Xi.Li@neclab.eu); 1186 Daniela Spreafico (daniela.spreafico@nokia.com) 1187 Marko Vaupotic (Marko.Vaupotic@aviatnet.com)"; 1189 description 1190 "This is a module for the entities in 1191 a generic interface protection mechanism. 1193 Copyright (c) 2018 IETF Trust and the persons identified as 1194 authors of the code. All rights reserved. 1196 Redistribution and use in source and binary forms, with or 1197 without modification, is permitted pursuant to, and subject 1198 to the license terms contained in, the Simplified BSD License 1199 set forth in Section 4.c of the IETF Trust's Legal Provisions 1200 Relating to IETF Documents 1201 (http://trustee.ietf.org/license-info). 1203 This version of this YANG module is part of RFC XXXX; see 1204 the RFC itself for full legal notices. 1206 Copyright (c) 2018 IETF Trust and the persons identified as 1207 authors of the code. All rights reserved."; 1209 revision 2018-03-30 { 1210 description "Initial revision."; 1211 reference "RFC XXXX: A YANG Data Model for Microwave Radio Link"; 1212 } 1214 /* 1215 * Protection architecture type identities 1216 */ 1218 identity protection-architecture-type { 1219 description 1220 "protection architecture type"; 1221 reference "ITU-T G.808.1"; 1222 } 1224 identity one-plus-one-type { 1225 base protection-architecture-type; 1226 description 1227 "1+1, One interface protects 1228 another one interface."; 1229 reference "ITU-T G.808.1"; 1230 } 1232 identity one-to-n-type { 1233 base protection-architecture-type; 1234 description 1235 "1:N, One interface protects 1236 n other interfaces."; 1237 reference "ITU-T G.808.1"; 1238 } 1239 /* 1240 * Protection states identities 1241 */ 1243 identity protection-states { 1244 description 1245 "Identities describing the status of the protection, 1246 in a group of interfaces configured in 1247 a protection mode."; 1248 } 1250 identity unprotected { 1251 base protection-states; 1252 description "Not protected"; 1253 } 1255 identity protected { 1256 base protection-states; 1257 description "Protected"; 1258 } 1260 identity unable-to-protect { 1261 base protection-states; 1262 description "Unable to protect"; 1263 } 1265 /* 1266 * protection-external-commands identities 1267 */ 1269 identity protection-external-commands{ 1270 description 1271 "Protection external commands for trouble shooting 1272 purpose."; 1273 reference "ITU-T G.808.1"; 1274 } 1276 identity manual-switch-working{ 1277 base protection-external-commands; 1278 description 1279 "A switch action initiated by an operator command. 1280 It switches normal traffic signal to the working 1281 transport entity."; 1282 reference "ITU-T G.808.1"; 1283 } 1284 identity manual-switch-protection{ 1285 base protection-external-commands; 1286 description 1287 "A switch action initiated by an operator command. 1288 It switches normal traffic signal to the protection 1289 transport entity."; 1290 reference "ITU-T G.808.1"; 1291 } 1293 identity forced-switch{ 1294 base protection-external-commands; 1295 description 1296 "A switch action initiated by an operator command. 1297 It switches normal traffic signal to the protection 1298 transport entity and forces it to remain on that 1299 entity even when criteria for switching back to 1300 the original entity are fulfilled."; 1301 reference "ITU-T G.808.1"; 1302 } 1304 identity lockout-of-protection{ 1305 base protection-external-commands; 1306 description 1307 "A switch action temporarily disables access to the 1308 protection transport entity for all signals."; 1309 reference "ITU-T G.808.1"; 1310 } 1312 identity freeze{ 1313 base protection-external-commands; 1314 description 1315 "A switch action temporarily prevents any switch action 1316 to be taken and, as such, freezes the current state. 1317 Until the freeze is cleared, additional near-end external 1318 commands are rejected and fault condition changes and 1319 received APS messages are ignored.."; 1320 reference "ITU-T G.808.1"; 1321 } 1323 identity exercise{ 1324 base protection-external-commands; 1325 description 1326 "A switch action to test if the APS communication is 1327 operating correctly. It is lower priority than any 'real' 1328 switch request.."; 1329 reference "ITU-T G.808.1"; 1330 } 1331 identity clear{ 1332 base protection-external-commands; 1333 description 1334 "An action clears all switch commands."; 1335 reference "ITU-T G.808.1"; 1336 } 1338 /* 1339 * Protection Groups 1340 */ 1342 grouping protection-groups { 1343 description 1344 "Configuration of protected groups (1+1) of interfaces 1345 providing protection for each other. More than one protected 1346 group per higher-layer-interface is allowed."; 1348 list protection-group { 1349 key "name"; 1350 description 1351 "List of protected groups of interfaces 1352 in a higher-layer-interface."; 1354 leaf name { 1355 type string; 1356 description 1357 "Name used for identification of the protection group"; 1358 } 1360 leaf protection-architecture-type { 1361 type identityref{ 1362 base protection-architecture-type; 1363 } 1364 default "ifprot:one-plus-one-type"; 1365 description 1366 "The type of protection architecture used, e.g. one 1367 interface protecting one or several other interfaces."; 1368 reference "ITU-T G.808.1"; 1369 } 1371 leaf-list members { 1372 type if:interface-ref; 1373 min-elements 2; 1374 description 1375 "Association to a group of interfaces configured for 1376 protection and used by a higher-layer-interface."; 1377 } 1378 leaf operation-type { 1379 type enumeration { 1380 enum "non-revertive" { 1381 description 1382 "In non revertive operation, the traffic does not 1383 return to the working interface if the switch requests 1384 are terminated."; 1385 reference "ITU-T G.808.1"; 1386 } 1387 enum "revertive" { 1388 description 1389 "In revertive operation, the traffic always 1390 returns to (or remains on) the working interface 1391 if the switch requests are terminated."; 1392 reference "ITU-T G.808.1"; 1393 } 1394 } 1395 default "non-revertive"; 1396 description 1397 "The type of protection operation, i.e. revertive 1398 or non-revertive operation."; 1399 } 1401 leaf-list working-entity { 1402 when "../operation-type = 'revertive'"; 1403 type if:interface-ref; 1404 min-elements 1; 1405 description 1406 "The interfaces over which the traffic normally should 1407 be transported over when there is no need to use the 1408 protecting interface."; 1409 } 1411 leaf revertive-wait-to-restore { 1412 when "../operation-type = 'revertive'"; 1413 type uint16; 1414 units "seconds"; 1415 default "0"; 1416 description 1417 "The time to wait before switching back to the working 1418 interface if operation-type is revertive."; 1419 reference "ITU-T G.808.1"; 1420 } 1421 leaf hold-off-timer { 1422 type uint16; 1423 units "milliseconds"; 1424 default "0"; 1425 description 1426 "Time interval after the detection of a fault and its 1427 confirmation as a condition requiring the protection 1428 switching procedure."; 1429 reference "ITU-T G.808.1"; 1430 } 1432 leaf status { 1433 type identityref { 1434 base protection-states; 1435 } 1436 description 1437 "Status of the protection, in a group of interfaces 1438 configured in a protection mode."; 1439 reference "ITU-T G.808.1"; 1440 } 1442 action external-commands { 1443 input { 1444 leaf external-command { 1445 type identityref { 1446 base protection-external-commands; 1447 } 1448 description 1449 "Execution of protection external commands for 1450 trouble shooting purpose."; 1451 } 1452 } 1453 } 1454 } 1455 } 1456 } 1458 1460 6. Microwave Types YANG Module 1462 This module defines a collection of common data types using the 1463 YANG data modeling language. These common types are designed 1464 to be imported by other modules defined in the microwave area. 1466 file "ietf-microwave-types@2018-03-30.yang" 1468 module ietf-microwave-types { 1469 yang-version 1.1; 1470 namespace "urn:ietf:params:xml:ns:yang:ietf-microwave-types"; 1471 prefix mw-types; 1473 import iana-if-type { 1474 prefix ianaift; 1475 reference "RFC 7224"; 1476 } 1478 organization 1479 "Internet Engineering Task Force (IETF) CCAMP WG"; 1480 contact 1481 "WG List: 1483 ID-draft editors: 1484 Jonas Ahlberg (jonas.ahlberg@ericsson.com); 1485 Min Ye (amy.yemin@huawei.com); 1486 Xi Li (Xi.Li@neclab.eu); 1487 Daniela Spreafico (daniela.spreafico@nokia.com) 1488 Marko Vaupotic (Marko.Vaupotic@aviatnet.com)"; 1490 description 1491 "This module contains a collection of YANG data types 1492 considered generally useful for microwave interfaces. 1494 Copyright (c) 2018 IETF Trust and the persons identified as 1495 authors of the code. All rights reserved. 1497 Redistribution and use in source and binary forms, with or 1498 without modification, is permitted pursuant to, and subject 1499 to the license terms contained in, the Simplified BSD License 1500 set forth in Section 4.c of the IETF Trust's Legal Provisions 1501 Relating to IETF Documents 1502 (http://trustee.ietf.org/license-info). 1504 This version of this YANG module is part of RFC XXXX; see 1505 the RFC itself for full legal notices. 1507 Copyright (c) 2018 IETF Trust and the persons identified as 1508 authors of the code. All rights reserved."; 1510 revision 2018-03-30 { 1511 description "Initial revision."; 1512 reference "RFC XXXX: A YANG Data Model for Microwave Radio Link"; 1513 } 1515 /* 1516 * Interface identities 1517 */ 1519 identity radio-link-terminal { 1520 base ianaift:iana-interface-type; 1521 description 1522 "Interface identity for a radio link terminal."; 1523 } 1525 identity carrier-termination { 1526 base ianaift:iana-interface-type; 1527 description 1528 "Interface identity for a carrier termination."; 1529 } 1531 /* 1532 * Radio-link-terminal mode identities 1533 */ 1535 identity rlt-mode { 1536 description 1537 "A description of the mode in which the radio link 1538 terminal is configured. The format is X plus Y. 1539 X represent the number of bonded carrier terminations. 1540 Y represent the number of protecting carrier 1541 terminations."; 1542 } 1544 identity one-plus-zero { 1545 base rlt-mode; 1546 description 1547 "1 carrier termination only."; 1548 } 1550 identity one-plus-one { 1551 base rlt-mode; 1552 description 1553 "1 carrier termination 1554 and 1 protecting carrier termination."; 1555 } 1556 identity two-plus-zero { 1557 base rlt-mode; 1558 description 1559 "2 bonded carrier terminations."; 1560 } 1562 /* 1563 * Coding and modulation identities 1564 */ 1566 identity coding-modulation { 1567 description 1568 "The coding and modulation schemes."; 1569 } 1571 identity half-bpsk-strong { 1572 base coding-modulation; 1573 description 1574 "Half BPSK strong coding and modulation scheme."; 1575 } 1577 identity half-bpsk { 1578 base coding-modulation; 1579 description 1580 "Half BPSK coding and modulation scheme."; 1581 } 1583 identity half-bpsk-light { 1584 base coding-modulation; 1585 description 1586 "Half BPSK light coding and modulation scheme."; 1587 } 1589 identity bpsk-strong { 1590 base coding-modulation; 1591 description 1592 "BPSK strong coding and modulation scheme."; 1593 } 1595 identity bpsk { 1596 base coding-modulation; 1597 description 1598 "BPSK coding and modulation scheme."; 1599 } 1601 identity bpsk-light { 1602 base coding-modulation; 1603 description 1604 "BPSK light coding and modulation scheme."; 1605 } 1606 identity qpsk { 1607 base coding-modulation; 1608 description 1609 "QPSK coding and modulation scheme."; 1610 } 1612 identity qam-4-strong { 1613 base coding-modulation; 1614 description 1615 "4 QAM strong coding and modulation scheme."; 1616 } 1618 identity qam-4 { 1619 base coding-modulation; 1620 description 1621 "4 QAM coding and modulation scheme."; 1622 } 1624 identity qam-4-light { 1625 base coding-modulation; 1626 description 1627 "4 QAM light coding and modulation scheme."; 1628 } 1630 identity qam-16-strong { 1631 base coding-modulation; 1632 description 1633 "16 QAM strong coding and modulation scheme."; 1634 } 1636 identity qam-16 { 1637 base coding-modulation; 1638 description 1639 "16 QAM coding and modulation scheme."; 1640 } 1642 identity qam-16-light { 1643 base coding-modulation; 1644 description 1645 "16 QAM light coding and modulation scheme."; 1646 } 1648 identity qam-32-strong { 1649 base coding-modulation; 1650 description 1651 "32 QAM strong coding and modulation scheme."; 1652 } 1653 identity qam-32 { 1654 base coding-modulation; 1655 description 1656 "32 QAM coding and modulation scheme."; 1657 } 1659 identity qam-32-light { 1660 base coding-modulation; 1661 description 1662 "32 QAM light coding and modulation scheme."; 1663 } 1665 identity qam-64-strong { 1666 base coding-modulation; 1667 description 1668 "64 QAM strong coding and modulation scheme."; 1669 } 1671 identity qam-64 { 1672 base coding-modulation; 1673 description 1674 "64 QAM coding and modulation scheme."; 1675 } 1677 identity qam-64-light { 1678 base coding-modulation; 1679 description 1680 "64 QAM light coding and modulation scheme."; 1681 } 1683 identity qam-128-strong { 1684 base coding-modulation; 1685 description 1686 "128 QAM strong coding and modulation scheme."; 1687 } 1689 identity qam-128 { 1690 base coding-modulation; 1691 description 1692 "128 QAM coding and modulation scheme."; 1693 } 1695 identity qam-128-light { 1696 base coding-modulation; 1697 description 1698 "128 QAM light coding and modulation scheme."; 1699 } 1700 identity qam-256-strong { 1701 base coding-modulation; 1702 description 1703 "256 QAM strong coding and modulation scheme."; 1704 } 1706 identity qam-256 { 1707 base coding-modulation; 1708 description 1709 "256 QAM coding and modulation scheme."; 1710 } 1712 identity qam-256-light { 1713 base coding-modulation; 1714 description 1715 "256 QAM light coding and modulation scheme."; 1716 } 1718 identity qam-512-strong { 1719 base coding-modulation; 1720 description 1721 "512 QAM strong coding and modulation scheme."; 1722 } 1724 identity qam-512 { 1725 base coding-modulation; 1726 description 1727 "512 QAM coding and modulation scheme."; 1728 } 1730 identity qam-512-light { 1731 base coding-modulation; 1732 description 1733 "512 QAM light coding and modulation scheme."; 1734 } 1736 identity qam-1024-strong { 1737 base coding-modulation; 1738 description 1739 "1024 QAM strong coding and modulation scheme."; 1740 } 1742 identity qam-1024 { 1743 base coding-modulation; 1744 description 1745 "1024 QAM coding and modulation scheme."; 1746 } 1747 identity qam-1024-light { 1748 base coding-modulation; 1749 description 1750 "1024 QAM light coding and modulation scheme."; 1751 } 1753 identity qam-2048-strong { 1754 base coding-modulation; 1755 description 1756 "2048 QAM strong coding and modulation scheme."; 1757 } 1759 identity qam-2048 { 1760 base coding-modulation; 1761 description 1762 "2048 QAM coding and modulation scheme."; 1763 } 1765 identity qam-2048-light { 1766 base coding-modulation; 1767 description 1768 "2048 QAM light coding and modulation scheme."; 1769 } 1771 identity qam-4096-strong { 1772 base coding-modulation; 1773 description 1774 "4096 QAM strong coding and modulation scheme."; 1775 } 1777 identity qam-4096 { 1778 base coding-modulation; 1779 description 1780 "4096 QAM coding and modulation scheme."; 1781 } 1783 identity qam-4096-light { 1784 base coding-modulation; 1785 description 1786 "4096 QAM light coding and modulation scheme."; 1787 } 1789 /* 1790 * TDM-type identities 1791 */ 1793 identity tdm-type { 1794 description 1795 "A description of the type of TDM connection, 1796 also indicating the supported capacity of the 1797 connection."; 1798 } 1799 identity E1 { 1800 base tdm-type; 1801 description 1802 "E1 connection, 2.048 Mbit/s."; 1803 } 1805 identity STM-1 { 1806 base tdm-type; 1807 description 1808 "STM-1 connection, 155.52 Mbit/s."; 1809 } 1810 } 1812 1814 7. Security Considerations 1816 The YANG module specified in this document defines a schema for data 1817 that is designed to be accessed via network management protocols such 1818 as NETCONF [RFC6241] or RESTCONF [RFC8040]. The lowest NETCONF layer 1819 is the secure transport layer, and the mandatory-to-implement secure 1820 transport is Secure Shell (SSH) [RFC6242]. The lowest RESTCONF layer 1821 is HTTPS, and the mandatory-to-implement secure transport is TLS 1822 [RFC5246]. 1824 The NETCONF access control model [RFC8341] provides the means to 1825 restrict access for particular NETCONF or RESTCONF users to a 1826 preconfigured subset of all available NETCONF or RESTCONF protocol 1827 operations and content. 1829 There are a number of data nodes defined in this YANG module that are 1830 writable/creatable/deletable (i.e., config true, which is the 1831 default). These data nodes may be considered sensitive or vulnerable 1832 in some network environments. Write operations (e.g., edit-config) 1833 to these data nodes without proper protection can have a negative 1834 effect on network operations. These are the subtrees and data nodes 1835 and their sensitivity/vulnerability: 1837 Interfaces of type radio-link-terminal: 1838 /if:interfaces/if:interface/carrier-terminations, 1839 /if:interfaces/if:interface/rlp-groups, 1840 /if:interfaces/if:interface/xpic-pairs, 1841 /if:interfaces/if:interface/mimo-groups, and 1842 /if:interfaces/if:interface/tdm-connections: 1843 These lists represent the configuration of the radio-link-terminal 1844 and it need to match the configuration of the radio-link-terminal 1845 on the other side of the radio link. Unauthorized access to these 1846 data nodes could interrupt the ability to forward traffic. 1848 Interfaces of type carrier-termination: 1849 /if:interfaces/if:interface/carrier-id, 1850 /if:interfaces/if:interface/tx-enabled, 1851 /if:interfaces/if:interface/tx-frequency, 1852 /if:interfaces/if:interface/rx-frequency, 1853 /if:interfaces/if:interface/duplex-distance, 1854 /if:interfaces/if:interface/channel-separation, 1855 /if:interfaces/if:interface/power-mode, 1856 /if:interfaces/if:interface/maximum-nominal-power, 1857 /if:interfaces/if:interface/atpc-lower-threshold, 1858 /if:interfaces/if:interface/atpc-upper-threshold, 1859 /if:interfaces/if:interface/coding-modulation-mode, 1860 /if:interfaces/if:interface/selected-cm, 1861 /if:interfaces/if:interface/selected-min-acm, 1862 /if:interfaces/if:interface/selected-max-acm, 1863 /if:interfaces/if:interface/if-loop, and 1864 /if:interfaces/if:interface/rf-loop: 1866 These data nodes represent the configuration of the 1867 carrier-termination and it need to match the configuration of the 1868 carrier-termination on the other side of the carrier. Unauthorized 1869 access to these data nodes could interrupt the ability to forward 1870 traffic. 1872 Radio link protection: 1873 /radio-link-protection-groups/protection-group: 1874 This list of protection groups and the constituent data nodes 1875 represents the configuration of the protection of carrier 1876 terminations. Unauthorized access to these data nodes could 1877 interrupt the ability to forward traffic or remove the ability to 1878 perform a necessary protection switch. 1880 XPIC: 1881 /xpic-pairs: 1882 This list represents the XPIC configuration of a pair carriers. 1883 Unauthorized access to these data nodes could interrupt the ability 1884 to forward traffic. 1886 MIMO: 1887 /mimo-groups: 1888 This list represents the MIMO configuration of multiple carriers. 1889 Unauthorized access to these data nodes could interrupt the ability 1890 to forward traffic. 1892 The security considerations of [RFC8343] also apply to this 1893 document. 1895 8. IANA Considerations 1897 It is proposed that IANA should assign new URIs from the 1898 "IETF XML Registry" [RFC3688] as follows: 1900 URI: urn:ietf:params:xml:ns:yang:ietf-microwave-radio-link 1901 Registrant Contact: The IESG 1902 XML: N/A; the requested URI is an XML namespace. 1904 URI: urn:ietf:params:xml:ns:yang:ietf-interface-protection 1905 Registrant Contact: The IESG 1906 XML: N/A; the requested URI is an XML namespace. 1908 It is proposed that IANA should record YANG module names in the 1909 "YANG Module Names" registry [RFC6020] as follows: 1911 Name: ietf-microwave-radio-link 1912 Namespace: urn:ietf:params:xml:ns:yang:ietf-microwave-radio-link 1913 Prefix: mrl 1914 Reference: RFC XXXX 1916 Name: ietf-interface-protection 1917 Namespace: urn:ietf:params:xml:ns:yang:ietf-interface-protection 1918 Prefix: ifprot 1919 Reference: RFC XXXX 1921 9. References 1923 9.1. Normative References 1925 [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate 1926 Requirement Levels", BCP 14, RFC 2119, 1927 DOI 10.17487/RFC2119, March 1997, 1928 . 1930 [RFC8174] Leiba, B., "Ambiguity of Uppercase vs Lowercase in RFC 1931 2119 Key Words", BCP 14, RFC 8174, DOI 10.17487/RFC8174, 1932 May 2017, . 1934 [RFC8343] Bjorklund, M., "A YANG Data Model for Interface 1935 Management", RFC 8343, DOI 10.17487/RFC8343, March 2018, 1936 . 1938 [EN301129] ETSI, "Transmission and Multiplexing (TM); Digital Radio 1939 Relay Systems (DRRS); Synchronous Digital Hierarchy (SDH); 1940 System performance monitoring parameters of SDH DRRS", 1941 EN 301 129 V1.1.2, May 1995. 1943 [EN302217-1] 1944 ETSI, "Fixed Radio Systems; Characteristics and 1945 requirements for point-to-point equipment and antennas; 1946 Part 1: Overview, common characteristics and system- 1947 dependent requirements", EN 302 217-1 V3.0.5, June 2016. 1949 [EN302217-2] 1950 ETSI, "Fixed Radio Systems; Characteristics and 1951 requirements for point to-point equipment and antennas; 1952 Part 2: Digital systems operating in frequency bands from 1953 1 GHz to 86 GHz; Harmonised Standard covering the 1954 essential requirements of article 3.2 of Directive 1955 2014/53/EU", EN 302 217-2 V3.1.1, May 2017. 1957 [G.808.1] ITU-T, "SERIES G: TRANSMISSION SYSTEMS AND MEDIA, DIGITAL 1958 SYSTEMS AND NETWORKS; Digital networks ; General aspects 1959 Generic protection switching ; Linear trail and subnetwork 1960 protection", ITU-T Rec. G.808.1, May 2014. 1962 [G.826] ITU-T, "SERIES G: TRANSMISSION SYSTEMS AND MEDIA, DIGITAL 1963 SYSTEMS AND NETWORKS; Digital networks ; Quality and 1964 availability targets End-to-end error performance 1965 parameters and objectives for international, constant 1966 bit-rate digital paths and connections", ITU-T Rec. G.826, 1967 December 2002. 1969 [TR102311] ETSI, "Fixed Radio Systems; Point-to-point equipment; 1970 Specific aspects of the spatial frequency reuse method", 1971 ETSI TR 102 311 V1.2.1, November 2015. 1973 [RFC3688] Mealling, M., "The IETF XML Registry", BCP 81, RFC 3688, 1974 DOI 10.17487/RFC3688, January 2004, . 1977 [RFC5246] Dierks, T. and E. Rescorla, "The Transport Layer Security 1978 (TLS) Protocol Version 1.2", RFC 5246, 1979 DOI 10.17487/RFC5246, August 2008, 1980 . 1982 [RFC6020] Bjorklund, M., Ed., "YANG - A Data Modeling Language for 1983 the Network Configuration Protocol (NETCONF)", RFC 6020, 1984 DOI 10.17487/RFC6020, October 2010, 1985 . 1987 [RFC6241] Enns, R., Bjorklund, M., Schoenwaelder, J., and A. 1988 Bierman, "Network Configuration Protocol (NETCONF)", 1989 RFC 6241, June 2011. 1991 [RFC6242] Wasserman, M., "Using the NETCONF Protocol over Secure 1992 Shell (SSH)", RFC 6242, June 2011. 1994 [RFC6991] Schoenwaelder, J., "Common YANG Data Types", RFC 6991, 1995 July 2013. 1997 [RFC7224] Bjorklund, M., "IANA Interface Type YANG Module", 1998 RFC 7224, May 2014. 2000 [RFC8040] Bierman, A., Bjorklund, M., and K. Watsen, "RESTCONF 2001 Protocol", RFC 8040, DOI 10.17487/RFC8040, January 2017, 2002 . 2004 [RFC8341] Bierman, A. and M. Bjorklund, "Network Configuration 2005 Access Control Model", STD 91, RFC 8341, 2006 DOI 10.17487/RFC8341, March 2018, . 2009 9.2. Informative References 2011 [RFC8342] Bjorklund, M., Schoenwaelder, J., Shafer, P., Watsen, K., 2012 and R. Wilton, "Network Management Datastore Architecture 2013 (NMDA)", RFC 8342, DOI 10.17487/RFC8342, March 2018, 2014 . 2016 [I-D.ahlberg-ccamp-microwave-radio-link] 2017 Ahlberg, J., Carlson, J., Lund, H., Olausson, T., Ye, M., 2018 and M. Vaupotic, "Microwave Radio Link YANG Data Models", 2019 draft-ahlberg-ccamp-microwave-radio-link-01 (work in 2020 progress), May 2016. 2022 [I-D.ietf-ccamp-microwave-framework] 2023 Ahlberg, J., Contreras, L., Ye, M., Vaupotic, M., 2024 Tantsura, J., Kawada, K., Li, X., Akiyoshi, I., C. 2025 Bernardos, and D. Spreafico, "A framework for Management 2026 and Control of microwave and millimeter wave interface 2027 parameters", draft-ietf-ccamp-microwave-framework-05 2028 (work in progress), October 2017. 2030 [ONF-model] "Microwave Modeling - ONF Wireless Transport Group", 2031 May 2016. 2033 [RFC6241] Enns, R., Ed., Bjorklund, M., Ed., Schoenwaelder, J., Ed., 2034 and A. Bierman, Ed., "Network Configuration Protocol 2035 (NETCONF)", RFC 6241, DOI 10.17487/RFC6241, June 2011, 2036 . 2038 [RFC6242] Wasserman, M., "Using the NETCONF Protocol over Secure 2039 Shell (SSH)", RFC 6242, DOI 10.17487/RFC6242, June 2011, 2040 . 2042 [RFC8340] Bjorklund, M. and L. Berger, Ed., "YANG Tree Diagrams", 2043 BCP 215, RFC 8340, DOI 10.17487/RFC8340, March 2018, 2044 . 2046 Appendix A. Example: 1+0 and 2+0 configuration instances 2048 This section gives simple examples of 1+0 and 2+0 instance using the 2049 YANG module defined in this draft. The examples are not intended as 2050 a complete module for 1+0 and 2+0 configuration. 2052 A.1 1+0 instance 2054 Figure A-1 shows a 1+0 example. 2056 /--------- Radio Link ---------\ 2057 Near End Far End 2059 +---------------+ +---------------+ 2060 | Radio Link | | Radio Link | 2061 | Terminal - A | | Terminal - B | 2062 | | | | 2063 | | | | 2064 | +-----------+ | | +-----------+ | 2065 | | | | Carrier A | | | | 2066 | | Carrier | |<--------->| | Carrier | | 2067 | |Termination| | | |Termination| | 2068 | | -1 | | | | -1 | | 2069 | +-----------+ | | +-----------+ | 2070 | | | | 2071 | | | | 2072 +---------------+ +---------------+ 2074 \--- Microwave Node ---/ \--- Microwave Node ---/ 2075 Figure A-1 1+0 example 2077 The following instance shows the 1+0 configuration of Near End node. 2079 "interface": [ 2080 { 2081 //RLT-A 2082 "name": "RLT-A", 2083 "description": "Radio Link Terminal A", 2084 "type": "mrl:radio-link-terminal", 2085 "id": "RLT-A", 2086 "mode": "one-plus-zero", 2087 "carrier-terminations": [ 2088 "RLT-A:CT-1", 2089 ], 2090 } 2091 { 2092 //CT-1 2093 "name": "RLT-A:CT-1", 2094 "description": "Carrier Termination 1", 2095 "type": "mrl:carrier-termination", 2096 "carrier-id": "A", 2097 "tx-enabled": true, 2098 "tx-oper-status": on 2099 "tx-frequency": 10728000, 2100 "duplex-distance": 644000, 2101 "channel-separation": 28, 2102 "polarization": not-specified, 2103 "power-mode": rtpc, 2104 "coding-modulation-mode": 0, 2105 "selected-cm": "qam-512" 2106 }, 2107 ] 2109 A.2 2+0 instance 2111 Figure A-2 shows a 2+0 example. 2113 /--------- Radio Link ---------\ 2114 Near End Far End 2116 +---------------+ +---------------+ 2117 | Radio Link | | Radio Link | 2118 | Terminal -A | | Terminal -B | 2119 | | | | 2120 | | | | 2121 | +-----------+ | | +-----------+ | 2122 | | | | Carrier A | | | | 2123 | | Carrier | |<--------->| | Carrier | | 2124 | |Termination| | | |Termination| | 2125 | | -1 | | | | -1 | | 2126 | +-----------+ | | +-----------+ | 2127 | | | | 2128 | +-----------+ | | +-----------+ | 2129 | | | | Carrier B | | | | 2130 | | Carrier | |<--------->| | Carrier | | 2131 | |Termination| | | |Termination| | 2132 | | -2 | | | | -2 | | 2133 | +-----------+ | | +-----------+ | 2134 | | | | 2135 +---------------+ +---------------+ 2137 \--- Microwave Node ---/ \--- Microwave Node ---/] 2138 Figure A-2 2+0 example 2140 The following instance shows the 2+0 configuration of Near End node. 2141 "interface": [ 2142 { 2143 //RLT-A 2144 "name": "RLT-A", 2145 "description": "Radio Link Terminal A", 2146 "type": "mrl:radio-link-terminal", 2147 "id": "RLT-A", 2148 "mode": "two-plus-zero", 2149 "carrier-terminations": [ 2150 "RLT-A:CT-1", 2151 "RLT-A:CT-2" 2152 ], 2153 } 2155 { 2156 //CT-1 2157 "name": "RLT-A:CT-1", 2158 "description": "Carrier Termination 1", 2159 "type": "mrl:carrier-termination", 2160 "carrier-id": "A", 2161 "tx-enabled": true, 2162 "tx-oper-status": on 2163 "tx-frequency": 10728000, 2164 "duplex-distance": 644000, 2165 "channel-separation": 28, 2166 "polarization": not-specified, 2167 "power-mode": rtpc, 2168 "coding-modulation-mode": 0, 2169 "selected-cm": "qam-512" 2170 }, 2172 { 2173 //CT-2 2174 "name": "RLT-A:CT-2", 2175 "description": "Carrier Termination 2", 2176 "type": "mrl:carrier-termination", 2177 "carrier-id": "B", 2178 "tx-enabled": true, 2179 "tx-oper-status": on 2180 "tx-frequency": 10618000, 2181 "duplex-distance": 644000, 2182 "channel-separation": 28, 2183 "polarization": not-specified, 2184 "power-mode": rtpc, 2185 "coding-modulation-mode": 0, 2186 "selected-cm": "qam-512" 2187 }, 2188 ] 2190 Appendix B. Contributors 2192 Koji Kawada 2193 NEC Corporation 2194 1753, Shimonumabe Nakahara-ku 2195 Kawasaki, Kanagawa 211-8666 2196 Japan (JPN) 2198 Email: k-kawada@ah.jp.nec.com 2200 Carlos J. Bernardos 2201 Universidad Carlos III de Madrid 2202 Av. Universidad, 30 2203 Leganes, Madrid 28911 2204 Spain (ESP) 2206 Email: cjbc@it.uc3m.es 2208 Authors' Addresses 2210 Jonas Ahlberg 2211 Ericsson AB 2212 Lindholmspiren 11 2213 Goeteborg 417 56 2214 Sweden (SWE) 2216 Email: jonas.ahlberg@ericsson.com 2218 Ye Min 2219 Huawei Technologies 2220 No.1899, Xiyuan Avenue 2221 Chengdu 611731 2222 P.R.China (CHN) 2224 Email: amy.yemin@huawei.com 2226 Xi Li 2227 NEC Laboratories Europe GmbH 2228 Kurfursten-Anlage 36 2229 69115 Heidelberg 2230 Germany (DEU) 2232 Email: Xi.Li@neclab.eu 2233 Daniela Spreafico 2234 Nokia - IT 2235 Via Energy Park, 14 2236 Vimercate (MI) 20871 2237 Italy (ITA) 2239 Email: daniela.spreafico@nokia.com 2241 Marko Vaupotic 2242 Aviat Networks 2243 Motnica 9 2244 Trzin-Ljubljana 1236 2245 Slovenia (SVN) 2247 Email: Marko.Vaupotic@Aviatnet.com