idnits 2.17.1 draft-ietf-ccamp-mw-yang-03.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 (February 26, 2018) is 2244 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: Normative reference to a draft: ref. 'RFC7223bis' -- Possible downref: Non-RFC (?) normative reference: ref. 'EN302217-2' ** Obsolete normative reference: RFC 5246 (Obsoleted by RFC 8446) ** Obsolete normative reference: RFC 6536 (Obsoleted by RFC 8341) == Outdated reference: A later version (-07) exists of draft-ietf-ccamp-microwave-framework-05 Summary: 2 errors (**), 0 flaws (~~), 3 warnings (==), 3 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: August 30, 2018 Huawei Technologies 6 X. Li 7 NEC Laboratories Europe 8 D. Spreafico 9 Nokia - IT 10 M. Vaupotic 11 Aviat Networks 12 February 26, 2018 14 A YANG Data Model for Microwave Radio Link 15 draft-ietf-ccamp-mw-yang-03 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 August 30, 2018. 43 Copyright Notice 45 Copyright (c) 2018 IETF Trust and the persons identified as the 46 document authors. All rights reserved. 48 This document is subject to BCP 78 and the IETF Trust's Legal 49 Provisions Relating to IETF Documents 50 (http://trustee.ietf.org/license-info) in effect on the date of 51 publication of this document. Please review these documents 52 carefully, as they describe your rights and restrictions with respect 53 to this document. Code Components extracted from this document must 54 include Simplified BSD License text as described in Section 4.e of 55 the Trust Legal Provisions and are provided without warranty as 56 described in the Simplified BSD License. 58 Table of Contents 60 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 2 61 1.1. Terminology and Definitions . . . . . . . . . . . . . . . 3 62 1.2. Tree Structure . . . . . . . . . . . . . . . . . . . . . . 4 63 2. Requirements Language . . . . . . . . . . . . . . . . . . . . 4 64 3. Microwave Radio Link YANG Data Model. . . . . . . . . . . . . 4 65 3.1. YANG Tree . . . . . . . . . . . . . . . . . . . . . . . . 4 66 3.2. Explanation of the Microwave Data Model . . . . . . . . . 6 67 4. Microwave Radio Link YANG Module . . . . . . . . . . . . . . 6 68 5. Interface Protection YANG Module . . . . . . . . . . . . . . 30 69 6. Security Considerations . . . . . . . . . . . . . . . . . . . 36 70 7. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 37 71 8. References . . . . . . . . . . . . . . . . . . . . . . . . . 38 72 8.1. Normative References . . . . . . . . . . . . . . . . . . 38 73 8.2. Informative References . . . . . . . . . . . . . . . . . 39 74 Appendix A. Example: 1+0 and 2+0 configuration instances. . . . . 40 75 Appendix B. Contributors. . . . . . . . . . . . . . . . . . . . . 43 76 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 43 78 1. Introduction 80 This document defines a YANG data model for management and control of 81 the radio link interface(s) and the relationship to packet (typically 82 Ethernet) and/or TDM interfaces in a microwave/millimeter wave node. 83 ETSI EN 302 217 series defines the characteristics and requirements 84 of microwave/millimeter wave equipment and antennas. Especially ETSI 85 EN 302 217-2 [EN302217-2] specifies the essential parameters for 86 the systems operating from 1.4GHz to 86GHz. The data model includes 87 configuration and state data according to the new Network Management 88 Datastore Architecture [NMDA]. 90 The design of the data model follows the framework for management and 91 control of microwave and millimeter wave interface parameters defined 92 in [I-D.ietf-ccamp-microwave-framework]. This framework identifies 93 the need and the scope of the YANG data model, the use cases and 94 requirements that the model needs to support. Moreover, it provides 95 a detailed gap analysis to identify the missing parameters and 96 functionalities of the existing and established models to support the 97 specified use cases and requirements, and based on that recommends 98 how the gaps should be filled with the development of the new model. 99 According to the conclusion of the gap analysis, the structure of the 100 data model is based on the structure defined in 101 [I-D.ahlberg-ccamp-microwave-radio-link] and it augments [RFC7223bis] 102 to align with the same structure for management of the packet 103 interfaces. More specifically, the model will include interface 104 layering to manage the capacity provided by a radio link terminal for 105 the associated Ethernet and TDM interfaces, using the principles for 106 interface layering described in [RFC7223bis] as a basis. 108 The data nodes for management of the interface protection 109 functionality is broken out into a separate and generic YANG data 110 module in order to make it available also for other interface types. 112 The designed YANG data model uses established microwave equipment 113 and radio standards, such as ETSI EN 302 217-2, and the IETF: Radio 114 Link Model[I-D.ahlberg-ccamp-microwave-radio-link] and the ONF: 115 Microwave Modeling[ONF-model] as the basis for the definition of the 116 detailed leafs/parameters, and proposes new ones to cover identified 117 gaps which are analyzed in[I-D.ietf-ccamp-microwave-framework]. 119 1.1. Terminology and Definitions 121 The following terms are used in this document: 123 Carrier Termination (CT) is an interface for the capacity provided 124 over the air by a single carrier. It is typically defined by its 125 transmitting and receiving frequencies. 127 Radio Link Terminal (RLT) is an interface providing packet capacity 128 and/or TDM capacity to the associated Ethernet and/or TDM interfaces 129 in a node and used for setting up a transport service over a 130 microwave/millimeter wave link. 132 The following acronyms are used in this document: 134 ACM Adaptive Coding Modulation 136 ATPC Automatic Transmit Power Control 138 CM Coding Modulation 140 CT Carrier Termination 141 RLT Radio Link Terminal 143 RTPC Remote Transmit Power Control 145 XPIC Cross Polarization Interference Cancellation 147 MIMO Multiple-Input Multiple-Output 149 1.2. Tree Structure 151 A simplified graphical representation of the data model is used in 152 chapter 3.1 of this this document. The meaning of the symbols in 153 these diagrams is defined in [YANG-TREE]. 155 2. Requirements Language 157 The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", 158 "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this 159 document are to be interpreted as described in [RFC2119]. 161 3. Microwave Radio Link YANG Data Model 163 3.1. YANG Tree 165 module: ietf-microwave-radio-link 166 +--rw radio-link-protection-groups 167 | +--rw protection-group* [name] 168 | +--rw name string 169 | +--rw architecture-type? identityref 170 | +--rw members* if:interface-ref 171 | +--rw operation-type? enumeration 172 | +--rw working-entity* if:interface-ref 173 | +--rw revertive-wait-to-restore? uint16 174 | +--rw hold-off-timer? uint16 175 | +--rw status? identityref 176 | +---x external-commands 177 | +---w input 178 | +---w external-command? identityref 179 +--rw xpic-pairs {xpic}? 180 | +--rw xpic-pair* [name] 181 | +--rw name string 182 | +--rw enabled? boolean 183 | +--rw members* if:interface-ref 184 +--rw mimo-groups {mimo}? 185 +--rw mimo-group* [name] 186 +--rw name string 187 +--rw enabled? boolean 188 +--rw members* if:interface-ref 190 augment /if:interfaces/if:interface: 191 +--rw id? string 192 +--rw mode identityref 193 +--rw carrier-terminations* if:interface-ref 194 +--rw rlp-groups* 195 | -> /radio-link-protection-groups/protection-group/name 196 +--rw xpic-pairs* -> /xpic-pairs/xpic-pair/name 197 | {xpic}? 198 +--rw mimo-groups* -> /mimo-groups/mimo-group/name 199 | {mimo}? 200 +--rw tdm-connections* [tdm-type] {tdm}? 201 +--rw tdm-type identityref 202 +--rw tdm-connections uint16 203 augment /if:interfaces/if:interface: 204 +--rw carrier-id? string 205 +--rw tx-enabled? boolean 206 +--ro tx-oper-status? enumeration 207 +--rw tx-frequency uint32 208 +--rw rx-frequency? uint32 209 +--rw duplex-distance? uint32 210 +--rw channel-separation uint32 211 +--rw polarization? enumeration 212 +--rw power-mode enumeration 213 +--rw maximum-nominal-power power 214 +--rw atpc-lower-threshold power 215 +--rw atpc-upper-threshold power 216 +--ro actual-transmitted-level? power 217 +--ro actual-received-level? power 218 +--rw coding-modulation-mode enumeration 219 +--rw selected-cm identityref 220 +--rw selected-min-acm identityref 221 +--rw selected-max-acm identityref 222 +--ro actual-tx-cm? identityref 223 +--ro actual-snir? decimal64 224 +--ro actual-xpi? decimal64 {xpic}? 225 +--rw ct-performance-thresholds 226 | +--rw received-level-alarm-threshold? power 227 | +--rw transmitted-level-alarm-threshold? power 228 | +--rw ber-alarm-threshold? enumeration 229 +--rw if-loop? enumeration 230 +--rw rf-loop? enumeration 231 +--ro capabilities 232 | +--ro min-tx-frequency? uint32 233 | +--ro max-tx-frequency? uint32 234 | +--ro min-rx-frequency? uint32 235 | +--ro max-rx-frequency? uint32 236 | +--ro minimum-power? power 237 | +--ro maximum-available-power? power 238 | +--ro available-min-acm? identityref 239 | +--ro available-max-acm? identityref 240 +--ro error-performance-statistics 241 | +--ro bbe? yang:counter32 242 | +--ro es? yang:counter32 243 | +--ro ses? yang:counter32 244 | +--ro uas? yang:counter32 245 +--ro radio-performance-statistics 246 +--ro min-rltm? power 247 +--ro max-rltm? power 248 +--ro min-tltm? power 249 +--ro max-tltm? power 251 3.2. Explanation of the Microwave Data Model 253 The leafs in the Interface Management Module augmented by Radio Link 254 Terminal (RLT) and Carrier Termination (CT) are not always 255 applicable. 257 "/interfaces/interface/enabled" is not applicable for RLT. Enable 258 and disable of an interface is done in the constituent CTs. 260 The packet related measurements "in-octets", "in-unicast-pkts", "in- 261 broadcast-pkts", "in-multicast-pkts", "in-discards", "in-errors", 262 "in-unknown-protos", "out-octets", "out-unicast-pkts", "out- 263 broadcast-pkts", "out-multicast-pkts", "out-discards", "out-errors" 264 are not within the scope of the microwave radio link domain and 265 therefore not applicable for RLT and CT. 267 4. Microwave Radio Link YANG Module 269 file "ietf-microwave-radio-link@2018-02-26.yang" 271 module ietf-microwave-radio-link { 272 yang-version 1.1; 273 namespace "urn:ietf:params:xml:ns:yang:ietf-microwave-radio-link"; 274 prefix mrl; 276 import ietf-yang-types { 277 prefix yang; 278 } 280 import ietf-interfaces { 281 prefix if; 282 reference "RFC7223bis"; 283 } 285 import ietf-interface-protection { 286 prefix ifprot; 287 } 289 import iana-if-type { 290 prefix ianaift; 291 } 293 organization 294 "Internet Engineering Task Force (IETF) CCAMP WG"; 296 contact 297 "WG List: 299 ID-draft authors: 300 Jonas Ahlberg (jonas.ahlberg@ericsson.com); 301 Min Ye (amy.yemin@huawei.com); 302 Xi Li (Xi.Li@neclab.eu); 303 Daniela Spreafico (daniela.spreafico@nokia.com) 304 Marko Vaupotic (Marko.Vaupotic@aviatnet.com)"; 306 description 307 "This is a module for the entities in 308 a generic microwave system. 310 Copyright (c) 2018 IETF Trust and the persons identified as 311 authors of the code. All rights reserved."; 313 revision 2018-02-26 { 314 description "Update with respect to the YANG Guideline"; 315 reference "RFC XXXX: A YANG Data Model for Microwave Radio Link"; 316 } 318 /* 319 * Features 320 */ 322 feature xpic { 323 description 324 "Indicates that the device supports XPIC."; 325 reference "ETSI TR 102 311"; 326 } 328 feature mimo { 329 description 330 "Indicates that the device supports MIMO."; 331 reference "ETSI TR 102 311"; 332 } 334 feature tdm { 335 description 336 "Indicates that the device supports TDM."; 337 } 339 /* 340 * Interface identities 341 */ 343 identity radio-link-terminal { 344 base ianaift:iana-interface-type; 345 description 346 "Interface identity for a radio link terminal."; 347 } 349 identity carrier-termination { 350 base ianaift:iana-interface-type; 351 description 352 "Interface identity for a carrier termination."; 353 } 355 /* 356 * Radio-link-terminal mode identities 357 */ 359 identity rlt-mode { 360 description 361 "A description of the mode in which the radio link 362 terminal is configured. The format is X plus Y. 363 X represent the number of bonded carrier terminations. 364 Y represent the number of protecting carrier 365 terminations."; 366 } 368 identity one-plus-zero { 369 base rlt-mode; 370 description 371 "1 carrier termination only."; 372 } 374 identity one-plus-one { 375 base rlt-mode; 376 description 377 "1 carrier termination 378 and 1 protecting carrier termination."; 379 } 381 identity two-plus-zero { 382 base rlt-mode; 383 description 384 "2 bonded carrier terminations."; 385 } 387 /* 388 * Coding and modulation identities 389 */ 391 identity coding-modulation { 392 description 393 "The coding and modulation schemes."; 394 } 395 identity half-bpsk-strong { 396 base coding-modulation; 397 description 398 "Half BPSK strong coding and modulation scheme."; 399 } 401 identity half-bpsk { 402 base coding-modulation; 403 description 404 "Half BPSK coding and modulation scheme."; 405 } 407 identity half-bpsk-light { 408 base coding-modulation; 409 description 410 "Half BPSK light coding and modulation scheme."; 411 } 413 identity bpsk-strong { 414 base coding-modulation; 415 description 416 "BPSK strong coding and modulation scheme."; 417 } 419 identity bpsk { 420 base coding-modulation; 421 description 422 "BPSK coding and modulation scheme."; 423 } 425 identity bpsk-light { 426 base coding-modulation; 427 description 428 "BPSK light coding and modulation scheme."; 429 } 431 identity qpsk { 432 base coding-modulation; 433 description 434 "QPSK coding and modulation scheme."; 435 } 437 identity qam-4-strong { 438 base coding-modulation; 439 description 440 "4 QAM strong coding and modulation scheme."; 441 } 442 identity qam-4 { 443 base coding-modulation; 444 description 445 "4 QAM coding and modulation scheme."; 446 } 448 identity qam-4-light { 449 base coding-modulation; 450 description 451 "4 QAM light coding and modulation scheme."; 452 } 454 identity qam-16-strong { 455 base coding-modulation; 456 description 457 "16 QAM strong coding and modulation scheme."; 458 } 460 identity qam-16 { 461 base coding-modulation; 462 description 463 "16 QAM coding and modulation scheme."; 464 } 466 identity qam-16-light { 467 base coding-modulation; 468 description 469 "16 QAM light coding and modulation scheme."; 470 } 472 identity qam-32-strong { 473 base coding-modulation; 474 description 475 "32 QAM strong coding and modulation scheme."; 476 } 478 identity qam-32 { 479 base coding-modulation; 480 description 481 "32 QAM coding and modulation scheme."; 482 } 484 identity qam-32-light { 485 base coding-modulation; 486 description 487 "32 QAM light coding and modulation scheme."; 488 } 489 identity qam-64-strong { 490 base coding-modulation; 491 description 492 "64 QAM strong coding and modulation scheme."; 493 } 495 identity qam-64 { 496 base coding-modulation; 497 description 498 "64 QAM coding and modulation scheme."; 499 } 501 identity qam-64-light { 502 base coding-modulation; 503 description 504 "64 QAM light coding and modulation scheme."; 505 } 507 identity qam-128-strong { 508 base coding-modulation; 509 description 510 "128 QAM strong coding and modulation scheme."; 511 } 513 identity qam-128 { 514 base coding-modulation; 515 description 516 "128 QAM coding and modulation scheme."; 517 } 519 identity qam-128-light { 520 base coding-modulation; 521 description 522 "128 QAM light coding and modulation scheme."; 523 } 525 identity qam-256-strong { 526 base coding-modulation; 527 description 528 "256 QAM strong coding and modulation scheme."; 529 } 531 identity qam-256 { 532 base coding-modulation; 533 description 534 "256 QAM coding and modulation scheme."; 535 } 536 identity qam-256-light { 537 base coding-modulation; 538 description 539 "256 QAM light coding and modulation scheme."; 540 } 542 identity qam-512-strong { 543 base coding-modulation; 544 description 545 "512 QAM strong coding and modulation scheme."; 546 } 548 identity qam-512 { 549 base coding-modulation; 550 description 551 "512 QAM coding and modulation scheme."; 552 } 554 identity qam-512-light { 555 base coding-modulation; 556 description 557 "512 QAM light coding and modulation scheme."; 558 } 560 identity qam-1024-strong { 561 base coding-modulation; 562 description 563 "1024 QAM strong coding and modulation scheme."; 564 } 566 identity qam-1024 { 567 base coding-modulation; 568 description 569 "1024 QAM coding and modulation scheme."; 570 } 572 identity qam-1024-light { 573 base coding-modulation; 574 description 575 "1024 QAM light coding and modulation scheme."; 576 } 578 identity qam-2048-strong { 579 base coding-modulation; 580 description 581 "2048 QAM strong coding and modulation scheme."; 582 } 583 identity qam-2048 { 584 base coding-modulation; 585 description 586 "2048 QAM coding and modulation scheme."; 587 } 589 identity qam-2048-light { 590 base coding-modulation; 591 description 592 "2048 QAM light coding and modulation scheme."; 593 } 595 identity qam-4096-strong { 596 base coding-modulation; 597 description 598 "4096 QAM strong coding and modulation scheme."; 599 } 601 identity qam-4096 { 602 base coding-modulation; 603 description 604 "4096 QAM coding and modulation scheme."; 605 } 607 identity qam-4096-light { 608 base coding-modulation; 609 description 610 "4096 QAM light coding and modulation scheme."; 611 } 613 /* 614 * TDM-type identities 615 */ 617 identity tdm-type { 618 description 619 "A description of the type of TDM connection, 620 also indicating the supported capacity of the 621 connection."; 622 } 624 identity E1 { 625 base tdm-type; 626 description 627 "E1 connection, 2,048 Mbit/s."; 628 } 630 identity STM-1 { 631 base tdm-type; 632 description 633 "STM-1 connection, 155,52 Mbit/s."; 634 } 635 /* 636 * Typedefs 637 */ 639 typedef power { 640 type decimal64 { 641 fraction-digits 1; 642 } 643 description 644 "Type used for power values, selected and measured."; 645 } 647 /* 648 * Radio Link Terminal (RLT) 649 */ 651 augment "/if:interfaces/if:interface" { 652 when "if:type = 'mrl:radio-link-terminal'"; 653 description 654 "Addition of data nodes for radio link terminal to 655 the standard Interface data model, for interfaces of 656 the type 'radio-link-terminal'."; 658 leaf id { 659 type string; 660 default ""; 661 description 662 "ID of the radio link terminal. Used by far-end when 663 checking that it's connected to the correct RLT."; 664 } 666 leaf mode { 667 type identityref { 668 base rlt-mode; 669 } 670 mandatory true; 671 description 672 "A description of the mode in which the radio link 673 terminal is configured. The format is X plus Y. 674 X represent the number of bonded carrier terminations. 675 Y represent the number of protecting carrier 676 terminations."; 677 } 678 leaf-list carrier-terminations { 679 type if:interface-ref; 680 must "/if:interfaces/if:interface[if:name = current()]" 681 + "/if:type = 'mrl:carrier-termination'" { 682 description 683 "The type of interface must be 684 'carrier-termination'."; 685 } 686 min-elements 1; 687 description 688 "A list of references to carrier terminations 689 included in the radio link terminal."; 690 } 692 leaf-list rlp-groups { 693 type leafref { 694 path "/mrl:radio-link-protection-groups/" 695 + "mrl:protection-group/mrl:name"; 696 } 697 description 698 "A list of references to the carrier termination 699 groups configured for radio link protection in this 700 radio link terminal."; 701 } 703 leaf-list xpic-pairs { 704 if-feature xpic; 705 type leafref { 706 path "/mrl:xpic-pairs/mrl:xpic-pair/mrl:name"; 707 } 708 description 709 "A list of references to the XPIC pairs used in this 710 radio link terminal. One pair can be used by two 711 terminals."; 712 reference "ETSI TR 102 311"; 713 } 715 leaf-list mimo-groups { 716 if-feature mimo; 717 type leafref { 718 path "/mrl:mimo-groups/mrl:mimo-group/mrl:name"; 719 } 720 description 721 "A reference to the MIMO group used in this 722 radio link terminal. One group can be used by more 723 than one terminal."; 724 reference "ETSI TR 102 311"; 725 } 726 list tdm-connections { 727 if-feature tdm; 728 key "tdm-type"; 729 description 730 "A list stating the number of active TDM connections 731 of a specified tdm-type that is configured to be 732 supported by the RLT."; 733 leaf tdm-type { 734 type identityref { 735 base tdm-type; 736 } 737 description 738 "The type of TDM connection, which also indicates 739 the supported capacity."; 740 } 741 leaf tdm-connections { 742 type uint16; 743 mandatory true; 744 description 745 "Number of connections of the specified type."; 746 } 747 } 748 } 750 /* 751 * Carrier Termination 752 */ 754 augment "/if:interfaces/if:interface" { 755 when "if:type = 'mrl:carrier-termination'"; 756 description 757 "Addition of data nodes for carrier termination to 758 the standard Interface data model, for interfaces 759 of the type 'carrier-termination'."; 761 leaf carrier-id { 762 type string; 763 default "A"; 764 description 765 "ID of the carrier. (e.g. A, B, C or D) 766 Used in XPIC & MIMO configurations to check that 767 the carrier termination is connected to the correct 768 far-end carrier termination. Should be the same 769 carrier ID on both sides of the hop. 770 Defaulted when not MIMO or XPIC."; 771 } 772 leaf tx-enabled { 773 type boolean; 774 default "false"; 775 description 776 "Disables (false) or enables (true) the transmitter. 777 Only applicable when the interface is enabled 778 (interface:enabled = true) otherwise it's always 779 disabled."; 780 } 782 leaf tx-oper-status { 783 type enumeration { 784 enum "off" { 785 description "Transmitter is off."; 786 } 787 enum "on" { 788 description "Transmitter is on."; 789 } 790 enum "standby" { 791 description "Transmitter is in standby."; 792 } 793 } 794 config false; 795 description 796 "Shows the operative status of the transmitter."; 797 } 799 leaf tx-frequency { 800 type uint32; 801 units "kHz"; 802 mandatory true; 803 description 804 "Selected transmitter frequency."; 805 } 807 leaf rx-frequency { 808 type uint32; 809 units "kHz"; 810 description 811 "Selected receiver frequency. 812 Overrides existing value in duplex-distance. 813 Calculated from tx-frequency and duplex-distance if 814 only duplex-distance is configured. 815 Must match duplex-distance if both leaves are 816 configured in a single operation."; 817 } 818 leaf duplex-distance { 819 type uint32; 820 units "kHz"; 821 description 822 "Distance between Tx & Rx frequencies. 823 Used to calculate rx-frequency when 824 rx-frequency is not specifically configured. 825 Overrides existing value in rx-frequency. 826 Calculated from tx-frequency and rx-frequency if only 827 rx-frequency is configured. 828 Must match rx-frequency if both leaves are configured 829 in a single operation."; 830 } 832 leaf channel-separation { 833 type uint32; 834 units "kHz"; 835 mandatory true; 836 description 837 "The amount of bandwidth allocated to a carrier. The distance 838 between adjacent channels in a radio frequency channels 839 arrangement"; 840 reference "ETSI EN 302 217-1"; 841 } 843 leaf polarization { 844 type enumeration { 845 enum "horizontal" { 846 description "Horizontal polarization."; 847 } 848 enum "vertical" { 849 description "Vertical polarization."; 850 } 851 enum "not-specified" { 852 description "Polarization not specified."; 853 } 854 } 855 default "not-specified"; 856 description 857 "Polarization - A textual description for info only."; 858 } 860 leaf power-mode { 861 type enumeration { 862 enum rtpc { 863 description 864 "Remote Transmit Power Control (RTPC)."; 865 reference "ETSI EN 302 217-1"; 866 } 867 enum atpc { 868 description 869 "Automatic Transmit Power Control (ATPC)."; 870 reference "ETSI EN 302 217-1"; 871 } 872 } 873 mandatory true; 874 description 875 "A choice of Remote Transmit Power Control (RTPC) 876 or Automatic Transmit Power Control (ATPC)."; 877 } 879 leaf maximum-nominal-power { 880 type power { 881 range "-99..40"; 882 } 883 units "dBm"; 884 mandatory true; 885 description 886 "Selected output power in RTPC mode and selected 887 maximum output power in ATPC mode. Minimum output 888 power in ATPC mode is the same as the system 889 capability, available-min-output-power."; 890 reference "ETSI EN 302 217-1"; 891 } 893 leaf atpc-lower-threshold { 894 when "../power-mode = 'atpc'"; 895 type power { 896 range "-99..-30"; 897 } 898 units "dBm"; 899 mandatory true; 900 description 901 "The lower threshold for the input power at far-end 902 used in the ATPC mode."; 903 reference "ETSI EN 302 217-1"; 904 } 906 leaf atpc-upper-threshold { 907 when "../power-mode = 'atpc'"; 908 type power { 909 range "-99..-30"; 910 } 911 units "dBm"; 912 mandatory true; 913 description 914 "The upper threshold for the input power at far-end 915 used in the ATPC mode."; 916 reference "ETSI EN 302 217-1"; 917 } 918 leaf actual-transmitted-level { 919 type power { 920 range "-99..40"; 921 } 922 units "dBm"; 923 config false; 924 description 925 "Actual transmitted power level (0.1 dBm resolution)."; 926 reference "ETSI EN 301 129"; 927 } 929 leaf actual-received-level { 930 type power { 931 range "-99..-20"; 932 } 933 units "dBm"; 934 config false; 935 description 936 "Actual received power level (0.1 dBm resolution)."; 937 reference "ETSI EN 301 129"; 938 } 940 leaf coding-modulation-mode { 941 type enumeration { 942 enum single { 943 description "a single modulation order only."; 944 reference "ETSI EN 302 217-1"; 945 } 946 enum adaptive { 947 description "Adaptive coding/modulation."; 948 reference "ETSI EN 302 217-1"; 949 } 950 } 951 mandatory true; 952 description 953 "A selection of single or 954 adaptive coding/modulation mode."; 955 } 957 leaf selected-cm { 958 when "../coding-modulation-mode = 'single'"; 959 type identityref { 960 base coding-modulation; 961 } 962 mandatory true; 963 description 964 "Selected the single coding/modulation."; 965 } 966 leaf selected-min-acm { 967 when "../coding-modulation-mode = 'adaptive'"; 968 type identityref { 969 base coding-modulation; 970 } 971 mandatory true; 972 description 973 "Selected minimum coding/modulation. 974 Adaptive coding/modulation shall not go 975 below this value."; 976 } 978 leaf selected-max-acm { 979 when "../coding-modulation-mode = 'adaptive'"; 980 type identityref { 981 base coding-modulation; 982 } 983 mandatory true; 984 description 985 "Selected maximum coding/modulation. 986 Adaptive coding/modulation shall not go 987 above this value."; 988 } 990 leaf actual-tx-cm { 991 type identityref { 992 base coding-modulation; 993 } 994 config false; 995 description 996 "Actual coding/modulation in transmitting direction."; 997 } 999 leaf actual-snir { 1000 type decimal64 { 1001 fraction-digits 1; 1002 range "0..99"; 1003 } 1004 units "dB"; 1005 config false; 1006 description 1007 "Actual signal to noise plus interference ratio. 1008 (0.1 dB resolution)."; 1009 } 1011 leaf actual-xpi { 1012 if-feature xpic; 1013 type decimal64 { 1014 fraction-digits 1; 1015 range "0..99"; 1016 } 1017 units "dB"; 1018 config false; 1019 description 1020 "The actual carrier to cross-polar interference. 1021 Only valid if XPIC is enabled. (0.1 dB resolution)."; 1022 reference "ETSI TR 102 311"; 1023 } 1025 container ct-performance-thresholds { 1026 description 1027 "Specification of thresholds for when alarms should 1028 be sent and cleared for various performance counters."; 1030 leaf received-level-alarm-threshold { 1031 type power { 1032 range "-99..-30"; 1033 } 1034 units "dBm"; 1035 default "-99"; 1036 description 1037 "An alarm is sent when the received power level is 1038 below the specified threshold."; 1039 reference "ETSI EN 301 129"; 1040 } 1042 leaf transmitted-level-alarm-threshold { 1043 type power { 1044 range "-99..40"; 1045 } 1046 units "dBm"; 1047 default "-99"; 1048 description 1049 "An alarm is sent when the transmitted power level 1050 is below the specified threshold."; 1051 reference "ETSI EN 301 129"; 1052 } 1054 leaf ber-alarm-threshold { 1055 type enumeration { 1056 enum "10e-9" { 1057 description "Threshold at 10e-9."; 1058 } 1059 enum "10e-8" { 1060 description "Threshold at 10e-8."; 1061 } 1062 enum "10e-7" { 1063 description "Threshold at 10e-7."; 1064 } 1065 enum "10e-6" { 1066 description "Threshold at 10e-6."; 1067 } 1068 enum "10e-5" { 1069 description "Threshold at 10e-5."; 1070 } 1071 enum "10e-4" { 1072 description "Threshold at 10e-4."; 1073 } 1074 enum "10e-3" { 1075 description "Threshold at 10e-3."; 1076 } 1077 enum "10e-2" { 1078 description "Threshold at 10e-2."; 1079 } 1080 enum "10e-1" { 1081 description "Threshold at 10e-1."; 1082 } 1083 } 1084 default "10e-6"; 1085 description 1086 "Specification of at which BER an alarm should 1087 be raised."; 1088 reference "ETSI EN 302 217-1"; 1089 } 1090 } 1092 leaf if-loop { 1093 type enumeration { 1094 enum disabled { 1095 description "Disables the IF Loop."; 1096 } 1097 enum client { 1098 description 1099 "Loops the signal back to the client side."; 1100 } 1101 enum radio { 1102 description 1103 "Loops the signal back to the radio side."; 1104 } 1105 } 1106 default "disabled"; 1107 description 1108 "Enable (client/radio) or disable (disabled) 1109 the IF loop, which loops the signal back to 1110 the client side or the radio side."; 1111 } 1113 leaf rf-loop { 1114 type enumeration { 1115 enum disabled { 1116 description "Disables the RF Loop."; 1117 } 1118 enum client { 1119 description 1120 "Loops the signal back to the client side."; 1121 } 1122 enum radio { 1123 description 1124 "Loops the signal back to the radio side."; 1125 } 1126 } 1127 default "disabled"; 1128 description 1129 "Enable (client/radio) or disable (disabled) 1130 the RF loop, which loops the signal back to 1131 the client side or the radio side."; 1132 } 1134 container capabilities { 1135 config false; 1136 description 1137 "Capabilities of the installed equipment and 1138 some selected configurations."; 1140 leaf min-tx-frequency { 1141 type uint32; 1142 units "kHz"; 1143 description 1144 "Minimum Tx frequency possible to use."; 1145 } 1147 leaf max-tx-frequency { 1148 type uint32; 1149 units "kHz"; 1150 description 1151 "Maximum Tx frequency possible to use."; 1152 } 1154 leaf min-rx-frequency { 1155 type uint32; 1156 units "kHz"; 1157 description 1158 "Minimum Rx frequency possible to use."; 1159 } 1161 leaf max-rx-frequency { 1162 type uint32; 1163 units "kHz"; 1164 description 1165 "Maximum Tx frequency possible to use."; 1166 } 1167 leaf minimum-power { 1168 type power; 1169 units "dBm"; 1170 description 1171 "The minimum output power supported."; 1172 reference "ETSI EN 302 217-1"; 1173 } 1175 leaf maximum-available-power { 1176 type power; 1177 units "dBm"; 1178 description 1179 "The maximum output power supported."; 1180 reference "ETSI EN 302 217-1"; 1181 } 1183 leaf available-min-acm { 1184 type identityref { 1185 base coding-modulation; 1186 } 1187 description 1188 "Minimum coding-modulation possible to use."; 1189 } 1191 leaf available-max-acm { 1192 type identityref { 1193 base coding-modulation; 1194 } 1195 description 1196 "Maximum coding-modulation possible to use."; 1197 } 1198 } 1200 container error-performance-statistics { 1201 config false; 1202 description 1203 "ITU-T G.826 error performance statistics relevant for 1204 a microwave/millimeter wave carrier."; 1206 leaf bbe { 1207 type yang:counter32; 1208 units "number of block errors"; 1209 description 1210 "Number of Background Block Errors (BBE) during the 1211 interval. A BBE is an errored block not occurring as 1212 part of an SES."; 1213 reference "ITU-T G.826"; 1214 } 1215 leaf es { 1216 type yang:counter32; 1217 units "seconds"; 1218 description 1219 "Number of Errored Seconds (ES) since last reset. 1220 An ES is a one-second period with one or more errored 1221 blocks or at least one defect."; 1222 reference "ITU-T G.826"; 1223 } 1225 leaf ses { 1226 type yang:counter32; 1227 units "seconds"; 1228 description 1229 "Number of Severely Errored Seconds (SES) during the 1230 interval. SES is a one-second period which contains 1231 equal or more than 30% errored blocks or at least 1232 one defect. SES is a subset of ES."; 1233 reference "ITU-T G.826"; 1234 } 1236 leaf uas { 1237 type yang:counter32; 1238 units "seconds"; 1239 description 1240 "Number of Unavailable Seconds (UAS), that is, the 1241 total time that the node has been unavailable during 1242 a fixed measurement interval."; 1243 reference "ITU-T G.826"; 1244 } 1245 } 1247 container radio-performance-statistics { 1248 config false; 1249 description 1250 "ETSI EN 301 129 radio physical interface statistics relevant 1251 for a carrier termination."; 1253 leaf min-rltm { 1254 type power { 1255 range "-99..-20"; 1256 } 1257 units "dBm"; 1258 description 1259 "Minimum received power level since last reset."; 1260 reference "ETSI EN 301 129"; 1261 } 1262 leaf max-rltm { 1263 type power { 1264 range "-99..-20"; 1265 } 1266 units "dBm"; 1267 description 1268 "Maximum received power level since last reset."; 1269 reference "ETSI EN 301 129"; 1270 } 1272 leaf min-tltm { 1273 type power { 1274 range "-99..40"; 1275 } 1276 units "dBm"; 1277 description 1278 "Minimum transmitted power level since last reset."; 1279 reference "ETSI EN 301 129"; 1280 } 1282 leaf max-tltm { 1283 type power { 1284 range "-99..40"; 1285 } 1286 units "dBm"; 1287 description 1288 "Maximum transmitted power level since last reset."; 1289 reference "ETSI EN 301 129"; 1290 } 1291 } 1292 } 1294 /* 1295 * Radio Link Protection Groups 1296 */ 1298 container radio-link-protection-groups { 1299 description 1300 "Configuration of radio link protected groups (1+1) of 1301 carrier terminations in a radio link. More than one 1302 protected group per radio-link-terminal is allowed."; 1304 uses ifprot:protection-groups { 1306 refine protection-group/members { 1307 must "/if:interfaces/if:interface[if:name = current()]" 1308 + "/if:type = 'mrl:carrier-termination'" { 1309 description 1310 "The type of a protection member must be 1311 'carrier-termination'."; 1312 } 1313 } 1314 refine protection-group/working-entity { 1315 must "/if:interfaces/if:interface[if:name = current()]" 1316 + "/if:type = 'mrl:carrier-termination'" { 1317 description 1318 "The type of a working-entity must be 1319 'carrier-termination'."; 1320 } 1321 } 1322 } 1323 } 1325 /* 1326 * XPIC & MIMO groups - Configuration data nodes 1327 */ 1329 container xpic-pairs { 1330 if-feature xpic; 1331 description 1332 "Configuration of carrier termination pairs 1333 for operation in XPIC mode."; 1334 reference "ETSI TR 102 311"; 1336 list xpic-pair { 1337 key "name"; 1338 description 1339 "List of carrier termination pairs in XPIC mode."; 1341 leaf name { 1342 type string; 1343 description 1344 "Name used for identification of the XPIC pair."; 1345 } 1347 leaf enabled { 1348 type boolean; 1349 default "false"; 1350 description 1351 "Enable(true)/disable(false) XPIC"; 1352 } 1354 leaf-list members { 1355 type if:interface-ref; 1356 must "/if:interfaces/if:interface[if:name = current()]" 1357 + "/if:type = 'mrl:carrier-termination'" { 1358 description 1359 "The type of a member must be 'carrier-termination'."; 1360 } 1361 min-elements 2; 1362 max-elements 2; 1363 description 1364 "Association to XPIC pairs used in the radio link 1365 terminal."; 1366 } 1367 } 1368 } 1370 container mimo-groups { 1371 if-feature mimo; 1372 description 1373 "Configuration of carrier terminations 1374 for operation in MIMO mode."; 1375 reference "ETSI TR 102 311"; 1377 list mimo-group { 1378 key "name"; 1379 description 1380 "List of carrier terminations in MIMO mode."; 1382 leaf name { 1383 type string; 1384 description 1385 "Name used for identification of the MIMO group."; 1386 } 1388 leaf enabled { 1389 type boolean; 1390 default "false"; 1391 description 1392 "Enable(true)/disable(false) MIMO"; 1393 } 1395 leaf-list members { 1396 type if:interface-ref; 1397 must "/if:interfaces/if:interface[if:name = current()]" 1398 + "/if:type = 'mrl:carrier-termination'" { 1399 description 1400 "The type of a member must be 'carrier-termination'."; 1401 } 1402 min-elements 2; 1403 description 1404 "Association to a MIMO group if used in the radio 1405 link terminal."; 1406 } 1407 } 1408 } 1409 } 1411 1413 5. Interface Protection YANG Module 1415 The data nodes for management of the interface protection 1416 functionality is broken out from the Microwave Radio Link Module 1417 into a separate and generic YANG data module in order to make it 1418 available also for other interface types. 1420 file "ietf-interface-protection@2018-02-26.yang" 1422 module ietf-interface-protection { 1423 yang-version 1.1; 1424 namespace "urn:ietf:params:xml:ns:yang:ietf-interface-protection"; 1425 prefix ifprot; 1427 import ietf-interfaces { 1428 prefix if; 1429 reference "RFC7223bis"; 1430 } 1432 organization 1433 "Internet Engineering Task Force (IETF) CCAMP WG"; 1434 contact 1435 "WG List: 1437 ID-draft authors: 1438 Jonas Ahlberg (jonas.ahlberg@ericsson.com); 1439 Min Ye (amy.yemin@huawei.com); 1440 Xi Li (Xi.Li@neclab.eu); 1441 Daniela Spreafico (daniela.spreafico@nokia.com) 1442 Marko Vaupotic (Marko.Vaupotic@aviatnet.com)"; 1444 description 1445 "This is a module for the entities in 1446 a generic interface protection mechanism. 1447 Copyright (c) 2018 IETF Trust and the persons identified as 1448 authors of the code. All rights reserved."; 1450 revision 2018-02-26 { 1451 description "Update with respect to the YANG Guideline"; 1452 reference "RFC XXXX: A YANG Data Model for Microwave Radio Link"; 1453 } 1455 /* 1456 * Protection architecture type identities 1457 */ 1459 identity protection-architecture-type { 1460 description 1461 "protection architecture type"; 1462 reference "ITU-T Rec. G.808.1"; 1463 } 1464 identity one-plus-one-type { 1465 base protection-architecture-type; 1466 description 1467 "1+1, One interface protects 1468 another one interface."; 1469 reference "ITU-T Rec. G.808.1"; 1470 } 1472 identity one-to-n-type { 1473 base protection-architecture-type; 1474 description 1475 "1:N, One interface protects 1476 n other interfaces."; 1477 reference "ITU-T Rec. G.808.1"; 1478 } 1480 /* 1481 * Protection states identities 1482 */ 1484 identity protection-states { 1485 description 1486 "Identities describing the status of the protection, 1487 in a group of interfaces configured in 1488 a protection mode."; 1489 } 1491 identity unprotected { 1492 base protection-states; 1493 description "Not protected"; 1494 } 1496 identity protected { 1497 base protection-states; 1498 description "Protected"; 1499 } 1501 identity unable-to-protect { 1502 base protection-states; 1503 description "Unable to protect"; 1504 } 1506 /* 1507 * protection-external-commands identities 1508 */ 1510 identity protection-external-commands{ 1511 description 1512 "Protection external commands for trouble shooting 1513 purpose."; 1514 reference "ITU-T Rec. G.808.1"; 1515 } 1516 identity manual-switch-working{ 1517 base protection-external-commands; 1518 description 1519 "A switch action initiated by an operator command. 1520 It switches normal traffic signal to the working 1521 transport entity."; 1522 reference "ITU-T Rec. G.808.1"; 1523 } 1525 identity manual-switch-protection{ 1526 base protection-external-commands; 1527 description 1528 "A switch action initiated by an operator command. 1529 It switches normal traffic signal to the protection 1530 transport entity."; 1531 reference "ITU-T Rec. G.808.1"; 1532 } 1534 identity forced-switch{ 1535 base protection-external-commands; 1536 description 1537 "A switch action initiated by an operator command. 1538 It switches normal traffic signal to the protection 1539 transport entity and forces it to remain on that 1540 entity even when criteria for switching back to 1541 the original entity are fulfilled."; 1542 reference "ITU-T Rec. G.808.1"; 1543 } 1545 identity lockout-of-protection{ 1546 base protection-external-commands; 1547 description 1548 "A switch action temporarily disables access to the 1549 protection transport entity for all signals."; 1550 reference "ITU-T Rec. G.808.1"; 1551 } 1553 identity freeze{ 1554 base protection-external-commands; 1555 description 1556 "A switch action temporarily prevents any switch action 1557 to be taken and, as such, freezes the current state. 1558 Until the freeze is cleared, additional near-end external 1559 commands are rejected and fault condition changes and 1560 received APS messages are ignored.."; 1561 reference "ITU-T Rec. G.808.1"; 1562 } 1563 identity exercise{ 1564 base protection-external-commands; 1565 description 1566 "A switch action to test if the APS communication is 1567 operating correctly. It is lower priority than any 'real' 1568 switch request.."; 1569 reference "ITU-T Rec. G.808.1"; 1570 } 1572 identity clear{ 1573 base protection-external-commands; 1574 description 1575 "An action clears all switch commands."; 1576 reference "ITU-T Rec. G.808.1"; 1577 } 1579 /* 1580 * Protection Groups 1581 */ 1583 grouping protection-groups { 1584 description 1585 "Configuration of protected groups (1+1) of interfaces 1586 providing protection for each other. More than one protected 1587 group per higher-layer-interface is allowed."; 1589 list protection-group { 1590 key "name"; 1591 description 1592 "List of protected groups of interfaces 1593 in a higher-layer-interface."; 1595 leaf name { 1596 type string; 1597 description 1598 "Name used for identification of the protection group"; 1599 } 1601 leaf protection-architecture-type { 1602 type identityref{ 1603 base protection-architecture-type; 1604 } 1605 default "ifprot:one-plus-one-type"; 1606 description 1607 "The type of protection architecture used, e.g. one 1608 interface protecting one or several other interfaces."; 1609 reference "ITU-T Rec. G.808.1"; 1610 } 1611 leaf-list members { 1612 type if:interface-ref; 1613 min-elements 2; 1614 description 1615 "Association to a group of interfaces configured for 1616 protection and used by a higher-layer-interface."; 1617 } 1619 leaf operation-type { 1620 type enumeration { 1621 enum "non-revertive" { 1622 description 1623 "In non revertive operation, the traffic does not 1624 return to the working interface if the switch requests 1625 are terminated."; 1626 reference "ITU-T Rec. G.808.1"; 1627 } 1628 enum "revertive" { 1629 description 1630 "In revertive operation, the traffic always 1631 returns to (or remains on) the working interface 1632 if the switch requests are terminated."; 1633 reference "ITU-T Rec. G.808.1"; 1634 } 1635 } 1636 default "non-revertive"; 1637 description 1638 "The type of protection operation, i.e. revertive 1639 or non-revertive operation."; 1640 } 1642 leaf-list working-entity { 1643 when "../operation-type = 'revertive'"; 1644 type if:interface-ref; 1645 min-elements 1; 1646 description 1647 "The interfaces over which the traffic normally should 1648 be transported over when there is no need to use the 1649 protecting interface."; 1650 } 1652 leaf revertive-wait-to-restore { 1653 when "../operation-type = 'revertive'"; 1654 type uint16; 1655 units "seconds"; 1656 default "0"; 1657 description 1658 "The time to wait before switching back to the working 1659 interface if operation-type is revertive."; 1660 reference "ITU-T Rec. G.808.1"; 1661 } 1662 leaf hold-off-timer { 1663 type uint16; 1664 units "milliseconds"; 1665 default "0"; 1666 description 1667 "Time interval after the detection of a fault and its 1668 confirmation as a condition requiring the protection 1669 switching procedure."; 1670 reference "ITU-T Rec. G.808.1"; 1671 } 1673 leaf status { 1674 type identityref { 1675 base protection-states; 1676 } 1677 description 1678 "Status of the protection, in a group of interfaces 1679 configured in a protection mode."; 1680 reference "ITU-T Rec. G.808.1"; 1681 } 1683 action external-commands { 1684 input { 1685 leaf external-command { 1686 type identityref { 1687 base protection-external-commands; 1688 } 1689 description 1690 "Execution of protection external commands for 1691 trouble shooting purpose."; 1692 } 1693 } 1694 } 1695 } 1696 } 1697 } 1699 1701 6. Security Considerations 1703 The YANG module specified in this document defines a schema for data 1704 that is designed to be accessed via network management protocols such 1705 as NETCONF [RFC6241] or RESTCONF [RFC8040]. The lowest NETCONF layer 1706 is the secure transport layer, and the mandatory-to-implement secure 1707 transport is Secure Shell (SSH) [RFC6242]. The lowest RESTCONF layer 1708 is HTTPS, and the mandatory-to-implement secure transport is TLS 1709 [RFC5246]. 1711 The NETCONF access control model [RFC6536] provides the means to 1712 restrict access for particular NETCONF or RESTCONF users to a 1713 preconfigured subset of all available NETCONF or RESTCONF protocol 1714 operations and content. 1716 There are a number of data nodes defined in this YANG module that are 1717 writable/creatable/deletable (i.e., config true, which is the 1718 default). These data nodes may be considered sensitive or vulnerable 1719 in some network environments. Write operations (e.g., edit-config) 1720 to these data nodes without proper protection can have a negative 1721 effect on network operations. These are the subtrees and data nodes 1722 and their sensitivity/vulnerability: 1724 Interfaces of type radio-link-terminal: 1725 /if:interfaces/if:interface/carrier-terminations, 1726 /if:interfaces/if:interface/rlp-groups, 1727 /if:interfaces/if:interface/xpic-pairs, 1728 /if:interfaces/if:interface/mimo-groups, and 1729 /if:interfaces/if:interface/tdm-connections: 1730 These lists represent the configuration of the radio-link-terminal 1731 and it need to match the configuration of the radio-link-terminal 1732 on the other side of the radio link. Unauthorized access to these 1733 data nodes could interrupt the ability to forward traffic. 1735 Interfaces of type carrier-termination: 1736 /if:interfaces/if:interface/carrier-id, 1737 /if:interfaces/if:interface/tx-enabled, 1738 /if:interfaces/if:interface/tx-frequency, 1739 /if:interfaces/if:interface/rx-frequency, 1740 /if:interfaces/if:interface/duplex-distance, 1741 /if:interfaces/if:interface/channel-separation, 1742 /if:interfaces/if:interface/power-mode, 1743 /if:interfaces/if:interface/maximum-nominal-power, 1744 /if:interfaces/if:interface/atpc-lower-threshold, 1745 /if:interfaces/if:interface/atpc-upper-threshold, 1746 /if:interfaces/if:interface/coding-modulation-mode, 1747 /if:interfaces/if:interface/selected-cm, 1748 /if:interfaces/if:interface/selected-min-acm, 1749 /if:interfaces/if:interface/selected-max-acm, 1750 /if:interfaces/if:interface/if-loop, and 1751 /if:interfaces/if:interface/rf-loop: 1753 These data nodes represent the configuration of the 1754 carrier-termination and it need to match the configuration of the 1755 carrier-termination on the other side of the carrier. Unauthorized 1756 access to these data nodes could interrupt the ability to forward 1757 traffic. 1759 Radio link protection: 1760 /radio-link-protection-groups/protection-group: 1761 This list of protection groups and the constituent data nodes 1762 represents the configuration of the protection of carrier 1763 terminations. Unauthorized access to these data nodes could 1764 interrupt the ability to forward traffic or remove the ability to 1765 perform a necessary protection switch. 1767 XPIC: 1768 /xpic-pairs: 1769 This list represents the XPIC configuration of a pair carriers. 1770 Unauthorized access to these data nodes could interrupt the ability 1771 to forward traffic. 1773 MIMO: 1774 /mimo-groups: 1775 This list represents the MIMO configuration of multiple carriers. 1776 Unauthorized access to these data nodes could interrupt the ability 1777 to forward traffic. 1779 The security considerations of [RFC7223bis] also apply to this 1780 document. 1782 7. IANA Considerations 1784 It is proposed that IANA should assign new URIs from the 1785 "IETF XML Registry" [RFC3688] as follows: 1787 URI: urn:ietf:params:xml:ns:yang:ietf-microwave-radio-link 1788 Registrant Contact: The IESG 1789 XML: N/A; the requested URI is an XML namespace. 1791 URI: urn:ietf:params:xml:ns:yang:ietf-interface-protection 1792 Registrant Contact: The IESG 1793 XML: N/A; the requested URI is an XML namespace. 1795 It is proposed that IANA should record YANG module names in the 1796 "YANG Module Names" registry [RFC6020] as follows: 1798 Name: ietf-microwave-radio-link 1799 Namespace: urn:ietf:params:xml:ns:yang:ietf-microwave-radio-link 1800 Prefix: mrl 1801 Reference: RFC xxxx 1802 Name: ietf-interface-protection 1803 Namespace: urn:ietf:params:xml:ns:yang:ietf-interface-protection 1804 Prefix: ifprot 1805 Reference: RFC xxxx 1807 8. References 1809 8.1. Normative References 1811 [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate 1812 Requirement Levels", BCP 14, RFC 2119, 1813 DOI 10.17487/RFC2119, March 1997, 1814 . 1816 [RFC7223bis] 1817 Bjorklund, M., "A YANG Data Model for Interface 1818 Management", draft-bjorklund-netmod-rfc7223bis-00 1819 (work in progress), September 2017. 1821 [EN302217-2] 1822 ETSI, "Fixed Radio Systems; Characteristics and 1823 requirements for point to-point equipment and antennas; 1824 Part 2: Digital systems operating in frequency bands from 1825 1 GHz to 86 GHz; Harmonised Standard covering the 1826 essential requirements of article 3.2 of Directive 1827 2014/53/EU", EN 302 217-2 V3.1.1, May 2017. 1829 [RFC3688] Mealling, M., "The IETF XML Registry", BCP 81, RFC 3688, 1830 DOI 10.17487/RFC3688, January 2004, . 1833 [RFC5246] Dierks, T. and E. Rescorla, "The Transport Layer Security 1834 (TLS) Protocol Version 1.2", RFC 5246, 1835 DOI 10.17487/RFC5246, August 2008, 1836 . 1838 [RFC6020] Bjorklund, M., Ed., "YANG - A Data Modeling Language for 1839 the Network Configuration Protocol (NETCONF)", RFC 6020, 1840 DOI 10.17487/RFC6020, October 2010, 1841 . 1843 [RFC6241] Enns, R., Bjorklund, M., Schoenwaelder, J., and A. 1844 Bierman, "Network Configuration Protocol (NETCONF)", 1845 RFC 6241, June 2011. 1847 [RFC6242] Wasserman, M., "Using the NETCONF Protocol over Secure 1848 Shell (SSH)", RFC 6242, June 2011. 1850 [RFC6536] Bierman, A. and M. Bjorklund, "Network Configuration 1851 Protocol (NETCONF) Access Control Model", RFC 6536, 1852 March 2012. 1854 [RFC8040] Bierman, A., Bjorklund, M., and K. Watsen, "RESTCONF 1855 Protocol", RFC 8040, DOI 10.17487/RFC8040, January 2017, 1856 . 1858 8.2. Informative References 1860 [NMDA] Bjorklund, M., Schoenwaelder, J., Shafer, P., Watsen, K., 1861 and R. Wilton, "Network Management Datastore 1862 Architecture", draft-ietf-netmod-revised-datastores-10 1863 (work in progress), January 2018. 1865 [I-D.ahlberg-ccamp-microwave-radio-link] 1866 Ahlberg, J., Carlson, J., Lund, H., Olausson, T., Ye, M., 1867 and M. Vaupotic, "Microwave Radio Link YANG Data Models", 1868 draft-ahlberg-ccamp-microwave-radio-link-01 (work in 1869 progress), May 2016. 1871 [I-D.ietf-ccamp-microwave-framework] 1872 Ahlberg, J., Contreras, L., Ye, M., Vaupotic, M., 1873 Tantsura, J., Kawada, K., Li, X., Akiyoshi, I., C. 1874 Bernardos, and D. Spreafico, "A framework for Management 1875 and Control of microwave and millimeter wave interface 1876 parameters", draft-ietf-ccamp-microwave-framework-05 1877 (work in progress), October 2017. 1879 [ONF-model] "Microwave Modeling - ONF Wireless Transport Group", 1880 May 2016. 1882 [RFC6241] Enns, R., Ed., Bjorklund, M., Ed., Schoenwaelder, J., Ed., 1883 and A. Bierman, Ed., "Network Configuration Protocol 1884 (NETCONF)", RFC 6241, DOI 10.17487/RFC6241, June 2011, 1885 . 1887 [RFC6242] Wasserman, M., "Using the NETCONF Protocol over Secure 1888 Shell (SSH)", RFC 6242, DOI 10.17487/RFC6242, June 2011, 1889 . 1891 [RFC6536] Bierman, A. and M. Bjorklund, "Network Configuration 1892 Protocol (NETCONF) Access Control Model", RFC 6536, 1893 DOI 10.17487/RFC6536, March 2012, 1894 . 1896 [YANG-TREE] Bjorklund, M. and L. Berger, "YANG Tree Diagrams", draft- 1897 ietf-netmod-yang-tree-diagrams-06 (work in progress), 1898 February 2018. 1900 Appendix A. Example: 1+0 and 2+0 configuration instances 1902 This section gives simple examples of 1+0 and 2+0 instance using the 1903 YANG module defined in this draft. The examples are not intended as 1904 a complete module for 1+0 and 2+0 configuration. 1906 A.1 1+0 instance 1908 Figure A-1 shows a 1+0 example. 1909 /--------- Radio Link ---------\ 1910 Near End Far End 1912 +---------------+ +---------------+ 1913 | Radio Link | | Radio Link | 1914 | Terminal - A | | Terminal - B | 1915 | | | | 1916 | | | | 1917 | +-----------+ | | +-----------+ | 1918 | | | | Carrier A | | | | 1919 | | Carrier | |<--------->| | Carrier | | 1920 | |Termination| | | |Termination| | 1921 | | -1 | | | | -1 | | 1922 | +-----------+ | | +-----------+ | 1923 | | | | 1924 | | | | 1925 +---------------+ +---------------+ 1927 \--- Microwave Node ---/ \--- Microwave Node ---/ 1928 Figure A-1 1+0 example 1930 The following instance shows the 1+0 configuration of Near End node. 1932 "interface": [ 1933 { 1934 //RLT-A 1935 "name": "RLT-A", 1936 "description": "Radio Link Terminal A", 1937 "type": "mrl:radio-link-terminal", 1938 "id": "RLT-A", 1939 "mode": "one-plus-zero", 1940 "carrier-terminations": [ 1941 "RLT-A:CT-1", 1942 ], 1943 } 1944 { 1945 //CT-1 1946 "name": "RLT-A:CT-1", 1947 "description": "Carrier Termination 1", 1948 "type": "mrl:carrier-termination", 1949 "carrier-id": "A", 1950 "tx-enabled": true, 1951 "tx-oper-status": on 1952 "tx-frequency": 10728000, 1953 "duplex-distance": 644000, 1954 "channel-separation": 28, 1955 "polarization": not-specified, 1956 "power-mode": rtpc, 1957 "coding-modulation-mode": 0, 1958 "selected-cm": "qam-512" 1959 }, 1960 ] 1962 A.2 2+0 instance 1964 Figure A-2 shows a 2+0 example. 1965 /--------- Radio Link ---------\ 1966 Near End Far End 1968 +---------------+ +---------------+ 1969 | Radio Link | | Radio Link | 1970 | Terminal -A | | Terminal -B | 1971 | | | | 1972 | | | | 1973 | +-----------+ | | +-----------+ | 1974 | | | | Carrier A | | | | 1975 | | Carrier | |<--------->| | Carrier | | 1976 | |Termination| | | |Termination| | 1977 | | -1 | | | | -1 | | 1978 | +-----------+ | | +-----------+ | 1979 | | | | 1980 | +-----------+ | | +-----------+ | 1981 | | | | Carrier B | | | | 1982 | | Carrier | |<--------->| | Carrier | | 1983 | |Termination| | | |Termination| | 1984 | | -2 | | | | -2 | | 1985 | +-----------+ | | +-----------+ | 1986 | | | | 1987 +---------------+ +---------------+ 1989 \--- Microwave Node ---/ \--- Microwave Node ---/] 1990 Figure A-2 2+0 example 1992 The following instance shows the 2+0 configuration of Near End node. 1993 "interface": [ 1994 { 1995 //RLT-A 1996 "name": "RLT-A", 1997 "description": "Radio Link Terminal A", 1998 "type": "mrl:radio-link-terminal", 1999 "id": "RLT-A", 2000 "mode": "two-plus-zero", 2001 "carrier-terminations": [ 2002 "RLT-A:CT-1", 2003 "RLT-A:CT-2" 2004 ], 2005 } 2007 { 2008 //CT-1 2009 "name": "RLT-A:CT-1", 2010 "description": "Carrier Termination 1", 2011 "type": "mrl:carrier-termination", 2012 "carrier-id": "A", 2013 "tx-enabled": true, 2014 "tx-oper-status": on 2015 "tx-frequency": 10728000, 2016 "duplex-distance": 644000, 2017 "channel-separation": 28, 2018 "polarization": not-specified, 2019 "power-mode": rtpc, 2020 "coding-modulation-mode": 0, 2021 "selected-cm": "qam-512" 2022 }, 2024 { 2025 //CT-2 2026 "name": "RLT-A:CT-2", 2027 "description": "Carrier Termination 2", 2028 "type": "mrl:carrier-termination", 2029 "carrier-id": "B", 2030 "tx-enabled": true, 2031 "tx-oper-status": on 2032 "tx-frequency": 10618000, 2033 "duplex-distance": 644000, 2034 "channel-separation": 28, 2035 "polarization": not-specified, 2036 "power-mode": rtpc, 2037 "coding-modulation-mode": 0, 2038 "selected-cm": "qam-512" 2039 }, 2040 ] 2042 Appendix B. Contributors 2044 Koji Kawada 2045 NEC Corporation 2046 1753, Shimonumabe Nakahara-ku 2047 Kawasaki, Kanagawa 211-8666 2048 Japan (JPN) 2050 Email: k-kawada@ah.jp.nec.com 2052 Carlos J. Bernardos 2053 Universidad Carlos III de Madrid 2054 Av. Universidad, 30 2055 Leganes, Madrid 28911 2056 Spain (ESP) 2058 Email: cjbc@it.uc3m.es 2060 Authors' Addresses 2062 Jonas Ahlberg 2063 Ericsson AB 2064 Lindholmspiren 11 2065 Goeteborg 417 56 2066 Sweden (SWE) 2068 Email: jonas.ahlberg@ericsson.com 2070 Ye Min 2071 Huawei Technologies 2072 No.1899, Xiyuan Avenue 2073 Chengdu 611731 2074 P.R.China (CHN) 2076 Email: amy.yemin@huawei.com 2078 Xi Li 2079 NEC Laboratories Europe 2080 Kurfursten-Anlage 36 2081 Heidelberg 69115 2082 Germany (DEU) 2084 Email: Xi.Li@neclab.eu 2085 Daniela Spreafico 2086 Nokia - IT 2087 Via Energy Park, 14 2088 Vimercate (MI) 20871 2089 Italy (ITA) 2091 Email: daniela.spreafico@nokia.com 2093 Marko Vaupotic 2094 Aviat Networks 2095 Motnica 9 2096 Trzin-Ljubljana 1236 2097 Slovenia (SVN) 2099 Email: Marko.Vaupotic@Aviatnet.com