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