idnits 2.17.1 draft-ietf-ccamp-mw-yang-04.txt: Checking boilerplate required by RFC 5378 and the IETF Trust (see https://trustee.ietf.org/license-info): ---------------------------------------------------------------------------- No issues found here. Checking nits according to https://www.ietf.org/id-info/1id-guidelines.txt: ---------------------------------------------------------------------------- No issues found here. Checking nits according to https://www.ietf.org/id-info/checklist : ---------------------------------------------------------------------------- No issues found here. Miscellaneous warnings: ---------------------------------------------------------------------------- == The copyright year in the IETF Trust and authors Copyright Line does not match the current year == The document doesn't use any RFC 2119 keywords, yet seems to have RFC 2119 boilerplate text. -- The document date (March 3, 2018) is 2245 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. 'EN301129' -- Possible downref: Non-RFC (?) normative reference: ref. 'EN302217-1' -- Possible downref: Non-RFC (?) normative reference: ref. 'EN302217-2' -- Possible downref: Non-RFC (?) normative reference: ref. 'G.808.1' -- Possible downref: Non-RFC (?) normative reference: ref. 'G.826' -- Possible downref: Non-RFC (?) normative reference: ref. 'TR102311' ** Obsolete normative reference: RFC 5246 (Obsoleted by RFC 8446) ** 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 (==), 8 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: September 4, 2018 Huawei Technologies 6 X. Li 7 NEC Laboratories Europe GmbH 8 D. Spreafico 9 Nokia - IT 10 M. Vaupotic 11 Aviat Networks 12 March 3, 2018 14 A YANG Data Model for Microwave Radio Link 15 draft-ietf-ccamp-mw-yang-04 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 September 4, 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 . . . . . . . . . . . . . . . . . . . 37 70 7. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 38 71 8. References . . . . . . . . . . . . . . . . . . . . . . . . . 39 72 8.1. Normative References . . . . . . . . . . . . . . . . . . 39 73 8.2. Informative References . . . . . . . . . . . . . . . . . 40 74 Appendix A. Example: 1+0 and 2+0 configuration instances. . . . . 42 75 Appendix B. Contributors. . . . . . . . . . . . . . . . . . . . . 45 76 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 45 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 This module imports typedefs and modules from [RFC6991], 270 [RFC7223bis] and [RFC7224], and it references [TR102311], 271 [EN302217-1], [EN301129], and [G.826]. 273 file "ietf-microwave-radio-link@2018-03-03.yang" 275 module ietf-microwave-radio-link { 276 yang-version 1.1; 277 namespace "urn:ietf:params:xml:ns:yang:ietf-microwave-radio-link"; 278 prefix mrl; 280 import ietf-yang-types { 281 prefix yang; 282 reference "RFC 6991"; 283 } 285 import ietf-interfaces { 286 prefix if; 287 reference "RFC 7223bis"; 288 // RFC Ed.: replace 7223bis with actual RFC number and remove 289 // this note 290 } 291 import ietf-interface-protection { 292 prefix ifprot; 293 reference "RFC XXXX"; 294 // RFC Ed.: replace XXXX with actual RFC number and remove 295 // this note 296 } 298 import iana-if-type { 299 prefix ianaift; 300 reference "RFC 7224"; 301 } 303 organization 304 "Internet Engineering Task Force (IETF) CCAMP WG"; 306 contact 307 "WG List: 309 ID-draft editors: 310 Jonas Ahlberg (jonas.ahlberg@ericsson.com); 311 Min Ye (amy.yemin@huawei.com); 312 Xi Li (Xi.Li@neclab.eu); 313 Daniela Spreafico (daniela.spreafico@nokia.com) 314 Marko Vaupotic (Marko.Vaupotic@aviatnet.com)"; 316 description 317 "This is a module for the entities in 318 a generic microwave system. 320 Copyright (c) 2018 IETF Trust and the persons identified as 321 authors of the code. All rights reserved. 323 Redistribution and use in source and binary forms, with or 324 without modification, is permitted pursuant to, and subject 325 to the license terms contained in, the Simplified BSD License 326 set forth in Section 4.c of the IETF Trust's Legal Provisions 327 Relating to IETF Documents 328 (http://trustee.ietf.org/license-info). 330 This version of this YANG module is part of RFC XXXX; see 331 the RFC itself for full legal notices. 333 Copyright (c) 2018 IETF Trust and the persons identified as 334 authors of the code. All rights reserved."; 336 revision 2018-03-03 { 337 description "Initial revision."; 338 reference "RFC XXXX: A YANG Data Model for Microwave Radio Link"; 339 // RFC Ed.: replace XXXX with actual RFC number and remove 340 // this note 341 } 342 /* 343 * Features 344 */ 346 feature xpic { 347 description 348 "Indicates that the device supports XPIC."; 349 reference "ETSI TR 102 311"; 350 } 352 feature mimo { 353 description 354 "Indicates that the device supports MIMO."; 355 reference "ETSI TR 102 311"; 356 } 358 feature tdm { 359 description 360 "Indicates that the device supports TDM."; 361 } 363 /* 364 * Interface identities 365 */ 367 identity radio-link-terminal { 368 base ianaift:iana-interface-type; 369 description 370 "Interface identity for a radio link terminal."; 371 } 373 identity carrier-termination { 374 base ianaift:iana-interface-type; 375 description 376 "Interface identity for a carrier termination."; 377 } 379 /* 380 * Radio-link-terminal mode identities 381 */ 383 identity rlt-mode { 384 description 385 "A description of the mode in which the radio link 386 terminal is configured. The format is X plus Y. 387 X represent the number of bonded carrier terminations. 388 Y represent the number of protecting carrier 389 terminations."; 390 } 391 identity one-plus-zero { 392 base rlt-mode; 393 description 394 "1 carrier termination only."; 395 } 397 identity one-plus-one { 398 base rlt-mode; 399 description 400 "1 carrier termination 401 and 1 protecting carrier termination."; 402 } 404 identity two-plus-zero { 405 base rlt-mode; 406 description 407 "2 bonded carrier terminations."; 408 } 410 /* 411 * Coding and modulation identities 412 */ 414 identity coding-modulation { 415 description 416 "The coding and modulation schemes."; 417 } 419 identity half-bpsk-strong { 420 base coding-modulation; 421 description 422 "Half BPSK strong coding and modulation scheme."; 423 } 425 identity half-bpsk { 426 base coding-modulation; 427 description 428 "Half BPSK coding and modulation scheme."; 429 } 431 identity half-bpsk-light { 432 base coding-modulation; 433 description 434 "Half BPSK light coding and modulation scheme."; 435 } 437 identity bpsk-strong { 438 base coding-modulation; 439 description 440 "BPSK strong coding and modulation scheme."; 441 } 442 identity bpsk { 443 base coding-modulation; 444 description 445 "BPSK coding and modulation scheme."; 446 } 448 identity bpsk-light { 449 base coding-modulation; 450 description 451 "BPSK light coding and modulation scheme."; 452 } 454 identity qpsk { 455 base coding-modulation; 456 description 457 "QPSK coding and modulation scheme."; 458 } 460 identity qam-4-strong { 461 base coding-modulation; 462 description 463 "4 QAM strong coding and modulation scheme."; 464 } 466 identity qam-4 { 467 base coding-modulation; 468 description 469 "4 QAM coding and modulation scheme."; 470 } 472 identity qam-4-light { 473 base coding-modulation; 474 description 475 "4 QAM light coding and modulation scheme."; 476 } 478 identity qam-16-strong { 479 base coding-modulation; 480 description 481 "16 QAM strong coding and modulation scheme."; 482 } 484 identity qam-16 { 485 base coding-modulation; 486 description 487 "16 QAM coding and modulation scheme."; 488 } 489 identity qam-16-light { 490 base coding-modulation; 491 description 492 "16 QAM light coding and modulation scheme."; 493 } 495 identity qam-32-strong { 496 base coding-modulation; 497 description 498 "32 QAM strong coding and modulation scheme."; 499 } 501 identity qam-32 { 502 base coding-modulation; 503 description 504 "32 QAM coding and modulation scheme."; 505 } 507 identity qam-32-light { 508 base coding-modulation; 509 description 510 "32 QAM light coding and modulation scheme."; 511 } 513 identity qam-64-strong { 514 base coding-modulation; 515 description 516 "64 QAM strong coding and modulation scheme."; 517 } 519 identity qam-64 { 520 base coding-modulation; 521 description 522 "64 QAM coding and modulation scheme."; 523 } 525 identity qam-64-light { 526 base coding-modulation; 527 description 528 "64 QAM light coding and modulation scheme."; 529 } 531 identity qam-128-strong { 532 base coding-modulation; 533 description 534 "128 QAM strong coding and modulation scheme."; 535 } 536 identity qam-128 { 537 base coding-modulation; 538 description 539 "128 QAM coding and modulation scheme."; 540 } 542 identity qam-128-light { 543 base coding-modulation; 544 description 545 "128 QAM light coding and modulation scheme."; 546 } 548 identity qam-256-strong { 549 base coding-modulation; 550 description 551 "256 QAM strong coding and modulation scheme."; 552 } 554 identity qam-256 { 555 base coding-modulation; 556 description 557 "256 QAM coding and modulation scheme."; 558 } 560 identity qam-256-light { 561 base coding-modulation; 562 description 563 "256 QAM light coding and modulation scheme."; 564 } 566 identity qam-512-strong { 567 base coding-modulation; 568 description 569 "512 QAM strong coding and modulation scheme."; 570 } 572 identity qam-512 { 573 base coding-modulation; 574 description 575 "512 QAM coding and modulation scheme."; 576 } 578 identity qam-512-light { 579 base coding-modulation; 580 description 581 "512 QAM light coding and modulation scheme."; 582 } 583 identity qam-1024-strong { 584 base coding-modulation; 585 description 586 "1024 QAM strong coding and modulation scheme."; 587 } 589 identity qam-1024 { 590 base coding-modulation; 591 description 592 "1024 QAM coding and modulation scheme."; 593 } 595 identity qam-1024-light { 596 base coding-modulation; 597 description 598 "1024 QAM light coding and modulation scheme."; 599 } 601 identity qam-2048-strong { 602 base coding-modulation; 603 description 604 "2048 QAM strong coding and modulation scheme."; 605 } 607 identity qam-2048 { 608 base coding-modulation; 609 description 610 "2048 QAM coding and modulation scheme."; 611 } 613 identity qam-2048-light { 614 base coding-modulation; 615 description 616 "2048 QAM light coding and modulation scheme."; 617 } 619 identity qam-4096-strong { 620 base coding-modulation; 621 description 622 "4096 QAM strong coding and modulation scheme."; 623 } 625 identity qam-4096 { 626 base coding-modulation; 627 description 628 "4096 QAM coding and modulation scheme."; 629 } 630 identity qam-4096-light { 631 base coding-modulation; 632 description 633 "4096 QAM light coding and modulation scheme."; 634 } 636 /* 637 * TDM-type identities 638 */ 640 identity tdm-type { 641 description 642 "A description of the type of TDM connection, 643 also indicating the supported capacity of the 644 connection."; 645 } 647 identity E1 { 648 base tdm-type; 649 description 650 "E1 connection, 2,048 Mbit/s."; 651 } 653 identity STM-1 { 654 base tdm-type; 655 description 656 "STM-1 connection, 155,52 Mbit/s."; 657 } 659 /* 660 * Typedefs 661 */ 663 typedef power { 664 type decimal64 { 665 fraction-digits 1; 666 } 667 description 668 "Type used for power values, selected and measured."; 669 } 671 /* 672 * Radio Link Terminal (RLT) 673 */ 675 augment "/if:interfaces/if:interface" { 676 when "if:type = 'mrl:radio-link-terminal'"; 677 description 678 "Addition of data nodes for radio link terminal to 679 the standard Interface data model, for interfaces of 680 the type 'radio-link-terminal'."; 682 leaf id { 683 type string; 684 default ""; 685 description 686 "ID of the radio link terminal. Used by far-end when 687 checking that it's connected to the correct RLT."; 688 } 690 leaf mode { 691 type identityref { 692 base rlt-mode; 693 } 694 mandatory true; 695 description 696 "A description of the mode in which the radio link 697 terminal is configured. The format is X plus Y. 698 X represent the number of bonded carrier terminations. 699 Y represent the number of protecting carrier 700 terminations."; 701 } 703 leaf-list carrier-terminations { 704 type if:interface-ref; 705 must "/if:interfaces/if:interface[if:name = current()]" 706 + "/if:type = 'mrl:carrier-termination'" { 707 description 708 "The type of interface must be 709 'carrier-termination'."; 710 } 711 min-elements 1; 712 description 713 "A list of references to carrier terminations 714 included in the radio link terminal."; 715 } 717 leaf-list rlp-groups { 718 type leafref { 719 path "/mrl:radio-link-protection-groups/" 720 + "mrl:protection-group/mrl:name"; 721 } 722 description 723 "A list of references to the carrier termination 724 groups configured for radio link protection in this 725 radio link terminal."; 726 } 727 leaf-list xpic-pairs { 728 if-feature xpic; 729 type leafref { 730 path "/mrl:xpic-pairs/mrl:xpic-pair/mrl:name"; 731 } 732 description 733 "A list of references to the XPIC pairs used in this 734 radio link terminal. One pair can be used by two 735 terminals."; 736 reference "ETSI TR 102 311"; 737 } 739 leaf-list mimo-groups { 740 if-feature mimo; 741 type leafref { 742 path "/mrl:mimo-groups/mrl:mimo-group/mrl:name"; 743 } 744 description 745 "A reference to the MIMO group used in this 746 radio link terminal. One group can be used by more 747 than one terminal."; 748 reference "ETSI TR 102 311"; 749 } 751 list tdm-connections { 752 if-feature tdm; 753 key "tdm-type"; 754 description 755 "A list stating the number of active TDM connections 756 of a specified tdm-type that is configured to be 757 supported by the RLT."; 758 leaf tdm-type { 759 type identityref { 760 base tdm-type; 761 } 762 description 763 "The type of TDM connection, which also indicates 764 the supported capacity."; 765 } 766 leaf tdm-connections { 767 type uint16; 768 mandatory true; 769 description 770 "Number of connections of the specified type."; 771 } 772 } 773 } 775 /* 776 * Carrier Termination 777 */ 779 augment "/if:interfaces/if:interface" { 780 when "if:type = 'mrl:carrier-termination'"; 781 description 782 "Addition of data nodes for carrier termination to 783 the standard Interface data model, for interfaces 784 of the type 'carrier-termination'."; 786 leaf carrier-id { 787 type string; 788 default "A"; 789 description 790 "ID of the carrier. (e.g. A, B, C or D) 791 Used in XPIC & MIMO configurations to check that 792 the carrier termination is connected to the correct 793 far-end carrier termination. Should be the same 794 carrier ID on both sides of the hop. 795 Defaulted when not MIMO or XPIC."; 796 } 798 leaf tx-enabled { 799 type boolean; 800 default "false"; 801 description 802 "Disables (false) or enables (true) the transmitter. 803 Only applicable when the interface is enabled 804 (interface:enabled = true) otherwise it's always 805 disabled."; 806 } 808 leaf tx-oper-status { 809 type enumeration { 810 enum "off" { 811 description "Transmitter is off."; 812 } 813 enum "on" { 814 description "Transmitter is on."; 815 } 816 enum "standby" { 817 description "Transmitter is in standby."; 818 } 819 } 820 config false; 821 description 822 "Shows the operative status of the transmitter."; 823 } 824 leaf tx-frequency { 825 type uint32; 826 units "kHz"; 827 mandatory true; 828 description 829 "Selected transmitter frequency."; 830 } 832 leaf rx-frequency { 833 type uint32; 834 units "kHz"; 835 description 836 "Selected receiver frequency. 837 Overrides existing value in duplex-distance. 838 Calculated from tx-frequency and duplex-distance if 839 only duplex-distance is configured. 840 Must match duplex-distance if both leaves are 841 configured in a single operation."; 842 } 844 leaf duplex-distance { 845 type uint32; 846 units "kHz"; 847 description 848 "Distance between Tx & Rx frequencies. 849 Used to calculate rx-frequency when 850 rx-frequency is not specifically configured. 851 Overrides existing value in rx-frequency. 852 Calculated from tx-frequency and rx-frequency if only 853 rx-frequency is configured. 854 Must match rx-frequency if both leaves are configured 855 in a single operation."; 856 } 858 leaf channel-separation { 859 type uint32; 860 units "kHz"; 861 mandatory true; 862 description 863 "The amount of bandwidth allocated to a carrier. The distance 864 between adjacent channels in a radio frequency channels 865 arrangement"; 866 reference "ETSI EN 302 217-1"; 867 } 868 leaf polarization { 869 type enumeration { 870 enum "horizontal" { 871 description "Horizontal polarization."; 872 } 873 enum "vertical" { 874 description "Vertical polarization."; 875 } 876 enum "not-specified" { 877 description "Polarization not specified."; 878 } 879 } 880 default "not-specified"; 881 description 882 "Polarization - A textual description for info only."; 883 } 885 leaf power-mode { 886 type enumeration { 887 enum rtpc { 888 description 889 "Remote Transmit Power Control (RTPC)."; 890 reference "ETSI EN 302 217-1"; 891 } 893 enum atpc { 894 description 895 "Automatic Transmit Power Control (ATPC)."; 896 reference "ETSI EN 302 217-1"; 897 } 898 } 899 mandatory true; 900 description 901 "A choice of Remote Transmit Power Control (RTPC) 902 or Automatic Transmit Power Control (ATPC)."; 903 } 905 leaf maximum-nominal-power { 906 type power { 907 range "-99..40"; 908 } 909 units "dBm"; 910 mandatory true; 911 description 912 "Selected output power in RTPC mode and selected 913 maximum output power in ATPC mode. Minimum output 914 power in ATPC mode is the same as the system 915 capability, available-min-output-power."; 916 reference "ETSI EN 302 217-1"; 917 } 918 leaf atpc-lower-threshold { 919 when "../power-mode = 'atpc'"; 920 type power { 921 range "-99..-30"; 922 } 923 units "dBm"; 924 mandatory true; 925 description 926 "The lower threshold for the input power at far-end 927 used in the ATPC mode."; 928 reference "ETSI EN 302 217-1"; 929 } 931 leaf atpc-upper-threshold { 932 when "../power-mode = 'atpc'"; 933 type power { 934 range "-99..-30"; 935 } 936 units "dBm"; 937 mandatory true; 938 description 939 "The upper threshold for the input power at far-end 940 used in the ATPC mode."; 941 reference "ETSI EN 302 217-1"; 942 } 944 leaf actual-transmitted-level { 945 type power { 946 range "-99..40"; 947 } 948 units "dBm"; 949 config false; 950 description 951 "Actual transmitted power level (0.1 dBm resolution)."; 952 reference "ETSI EN 301 129"; 953 } 955 leaf actual-received-level { 956 type power { 957 range "-99..-20"; 958 } 959 units "dBm"; 960 config false; 961 description 962 "Actual received power level (0.1 dBm resolution)."; 963 reference "ETSI EN 301 129"; 964 } 965 leaf coding-modulation-mode { 966 type enumeration { 967 enum single { 968 description "a single modulation order only."; 969 reference "ETSI EN 302 217-1"; 970 } 971 enum adaptive { 972 description "Adaptive coding/modulation."; 973 reference "ETSI EN 302 217-1"; 974 } 975 } 976 mandatory true; 977 description 978 "A selection of single or 979 adaptive coding/modulation mode."; 980 } 982 leaf selected-cm { 983 when "../coding-modulation-mode = 'single'"; 984 type identityref { 985 base coding-modulation; 986 } 987 mandatory true; 988 description 989 "Selected the single coding/modulation."; 990 } 992 leaf selected-min-acm { 993 when "../coding-modulation-mode = 'adaptive'"; 994 type identityref { 995 base coding-modulation; 996 } 997 mandatory true; 998 description 999 "Selected minimum coding/modulation. 1000 Adaptive coding/modulation shall not go 1001 below this value."; 1002 } 1004 leaf selected-max-acm { 1005 when "../coding-modulation-mode = 'adaptive'"; 1006 type identityref { 1007 base coding-modulation; 1008 } 1009 mandatory true; 1010 description 1011 "Selected maximum coding/modulation. 1012 Adaptive coding/modulation shall not go 1013 above this value."; 1014 } 1015 leaf actual-tx-cm { 1016 type identityref { 1017 base coding-modulation; 1018 } 1019 config false; 1020 description 1021 "Actual coding/modulation in transmitting direction."; 1022 } 1024 leaf actual-snir { 1025 type decimal64 { 1026 fraction-digits 1; 1027 range "0..99"; 1028 } 1029 units "dB"; 1030 config false; 1031 description 1032 "Actual signal to noise plus interference ratio. 1033 (0.1 dB resolution)."; 1034 } 1036 leaf actual-xpi { 1037 if-feature xpic; 1038 type decimal64 { 1039 fraction-digits 1; 1040 range "0..99"; 1041 } 1042 units "dB"; 1043 config false; 1044 description 1045 "The actual carrier to cross-polar interference. 1046 Only valid if XPIC is enabled. (0.1 dB resolution)."; 1047 reference "ETSI TR 102 311"; 1048 } 1050 container ct-performance-thresholds { 1051 description 1052 "Specification of thresholds for when alarms should 1053 be sent and cleared for various performance counters."; 1055 leaf received-level-alarm-threshold { 1056 type power { 1057 range "-99..-30"; 1058 } 1059 units "dBm"; 1060 default "-99"; 1061 description 1062 "An alarm is sent when the received power level is 1063 below the specified threshold."; 1064 reference "ETSI EN 301 129"; 1065 } 1066 leaf transmitted-level-alarm-threshold { 1067 type power { 1068 range "-99..40"; 1069 } 1070 units "dBm"; 1071 default "-99"; 1072 description 1073 "An alarm is sent when the transmitted power level 1074 is below the specified threshold."; 1075 reference "ETSI EN 301 129"; 1076 } 1078 leaf ber-alarm-threshold { 1079 type enumeration { 1080 enum "10e-9" { 1081 description "Threshold at 10e-9."; 1082 } 1083 enum "10e-8" { 1084 description "Threshold at 10e-8."; 1085 } 1086 enum "10e-7" { 1087 description "Threshold at 10e-7."; 1088 } 1089 enum "10e-6" { 1090 description "Threshold at 10e-6."; 1091 } 1092 enum "10e-5" { 1093 description "Threshold at 10e-5."; 1094 } 1095 enum "10e-4" { 1096 description "Threshold at 10e-4."; 1097 } 1098 enum "10e-3" { 1099 description "Threshold at 10e-3."; 1100 } 1101 enum "10e-2" { 1102 description "Threshold at 10e-2."; 1103 } 1104 enum "10e-1" { 1105 description "Threshold at 10e-1."; 1106 } 1107 } 1108 default "10e-6"; 1109 description 1110 "Specification of at which BER an alarm should 1111 be raised."; 1112 reference "ETSI EN 302 217-1"; 1113 } 1114 } 1115 leaf if-loop { 1116 type enumeration { 1117 enum disabled { 1118 description "Disables the IF Loop."; 1119 } 1120 enum client { 1121 description 1122 "Loops the signal back to the client side."; 1123 } 1124 enum radio { 1125 description 1126 "Loops the signal back to the radio side."; 1127 } 1128 } 1129 default "disabled"; 1130 description 1131 "Enable (client/radio) or disable (disabled) 1132 the IF loop, which loops the signal back to 1133 the client side or the radio side."; 1134 } 1136 leaf rf-loop { 1137 type enumeration { 1138 enum disabled { 1139 description "Disables the RF Loop."; 1140 } 1141 enum client { 1142 description 1143 "Loops the signal back to the client side."; 1144 } 1145 enum radio { 1146 description 1147 "Loops the signal back to the radio side."; 1148 } 1149 } 1150 default "disabled"; 1151 description 1152 "Enable (client/radio) or disable (disabled) 1153 the RF loop, which loops the signal back to 1154 the client side or the radio side."; 1155 } 1157 container capabilities { 1158 config false; 1159 description 1160 "Capabilities of the installed equipment and 1161 some selected configurations."; 1163 leaf min-tx-frequency { 1164 type uint32; 1165 units "kHz"; 1166 description 1167 "Minimum Tx frequency possible to use."; 1168 } 1170 leaf max-tx-frequency { 1171 type uint32; 1172 units "kHz"; 1173 description 1174 "Maximum Tx frequency possible to use."; 1175 } 1177 leaf min-rx-frequency { 1178 type uint32; 1179 units "kHz"; 1180 description 1181 "Minimum Rx frequency possible to use."; 1182 } 1184 leaf max-rx-frequency { 1185 type uint32; 1186 units "kHz"; 1187 description 1188 "Maximum Tx frequency possible to use."; 1189 } 1191 leaf minimum-power { 1192 type power; 1193 units "dBm"; 1194 description 1195 "The minimum output power supported."; 1196 reference "ETSI EN 302 217-1"; 1197 } 1199 leaf maximum-available-power { 1200 type power; 1201 units "dBm"; 1202 description 1203 "The maximum output power supported."; 1204 reference "ETSI EN 302 217-1"; 1205 } 1207 leaf available-min-acm { 1208 type identityref { 1209 base coding-modulation; 1210 } 1211 description 1212 "Minimum coding-modulation possible to use."; 1213 } 1214 leaf available-max-acm { 1215 type identityref { 1216 base coding-modulation; 1217 } 1218 description 1219 "Maximum coding-modulation possible to use."; 1220 } 1221 } 1223 container error-performance-statistics { 1224 config false; 1225 description 1226 "ITU-T G.826 error performance statistics relevant for 1227 a microwave/millimeter wave carrier."; 1229 leaf bbe { 1230 type yang:counter32; 1231 units "number of block errors"; 1232 description 1233 "Number of Background Block Errors (BBE) during the 1234 interval. A BBE is an errored block not occurring as 1235 part of an SES."; 1236 reference "ITU-T G.826"; 1237 } 1239 leaf es { 1240 type yang:counter32; 1241 units "seconds"; 1242 description 1243 "Number of Errored Seconds (ES) since last reset. 1244 An ES is a one-second period with one or more errored 1245 blocks or at least one defect."; 1246 reference "ITU-T G.826"; 1247 } 1249 leaf ses { 1250 type yang:counter32; 1251 units "seconds"; 1252 description 1253 "Number of Severely Errored Seconds (SES) during the 1254 interval. SES is a one-second period which contains 1255 equal or more than 30% errored blocks or at least 1256 one defect. SES is a subset of ES."; 1257 reference "ITU-T G.826"; 1258 } 1259 leaf uas { 1260 type yang:counter32; 1261 units "seconds"; 1262 description 1263 "Number of Unavailable Seconds (UAS), that is, the 1264 total time that the node has been unavailable during 1265 a fixed measurement interval."; 1266 reference "ITU-T G.826"; 1267 } 1268 } 1270 container radio-performance-statistics { 1271 config false; 1272 description 1273 "ETSI EN 301 129 radio physical interface statistics relevant 1274 for a carrier termination."; 1276 leaf min-rltm { 1277 type power { 1278 range "-99..-20"; 1279 } 1280 units "dBm"; 1281 description 1282 "Minimum received power level since last reset."; 1283 reference "ETSI EN 301 129"; 1284 } 1286 leaf max-rltm { 1287 type power { 1288 range "-99..-20"; 1289 } 1290 units "dBm"; 1291 description 1292 "Maximum received power level since last reset."; 1293 reference "ETSI EN 301 129"; 1294 } 1296 leaf min-tltm { 1297 type power { 1298 range "-99..40"; 1299 } 1300 units "dBm"; 1301 description 1302 "Minimum transmitted power level since last reset."; 1303 reference "ETSI EN 301 129"; 1304 } 1305 leaf max-tltm { 1306 type power { 1307 range "-99..40"; 1308 } 1309 units "dBm"; 1310 description 1311 "Maximum transmitted power level since last reset."; 1312 reference "ETSI EN 301 129"; 1313 } 1314 } 1315 } 1317 /* 1318 * Radio Link Protection Groups 1319 */ 1321 container radio-link-protection-groups { 1322 description 1323 "Configuration of radio link protected groups (1+1) of 1324 carrier terminations in a radio link. More than one 1325 protected group per radio-link-terminal is allowed."; 1327 uses ifprot:protection-groups { 1329 refine protection-group/members { 1330 must "/if:interfaces/if:interface[if:name = current()]" 1331 + "/if:type = 'mrl:carrier-termination'" { 1332 description 1333 "The type of a protection member must be 1334 'carrier-termination'."; 1335 } 1336 } 1338 refine protection-group/working-entity { 1339 must "/if:interfaces/if:interface[if:name = current()]" 1340 + "/if:type = 'mrl:carrier-termination'" { 1341 description 1342 "The type of a working-entity must be 1343 'carrier-termination'."; 1344 } 1345 } 1346 } 1347 } 1349 /* 1350 * XPIC & MIMO groups - Configuration data nodes 1351 */ 1353 container xpic-pairs { 1354 if-feature xpic; 1355 description 1356 "Configuration of carrier termination pairs 1357 for operation in XPIC mode."; 1358 reference "ETSI TR 102 311"; 1360 list xpic-pair { 1361 key "name"; 1362 description 1363 "List of carrier termination pairs in XPIC mode."; 1365 leaf name { 1366 type string; 1367 description 1368 "Name used for identification of the XPIC pair."; 1369 } 1371 leaf enabled { 1372 type boolean; 1373 default "false"; 1374 description 1375 "Enable(true)/disable(false) XPIC"; 1376 } 1378 leaf-list members { 1379 type if:interface-ref; 1380 must "/if:interfaces/if:interface[if:name = current()]" 1381 + "/if:type = 'mrl:carrier-termination'" { 1382 description 1383 "The type of a member must be 'carrier-termination'."; 1384 } 1385 min-elements 2; 1386 max-elements 2; 1387 description 1388 "Association to XPIC pairs used in the radio link 1389 terminal."; 1390 } 1391 } 1392 } 1394 container mimo-groups { 1395 if-feature mimo; 1396 description 1397 "Configuration of carrier terminations 1398 for operation in MIMO mode."; 1399 reference "ETSI TR 102 311"; 1401 list mimo-group { 1402 key "name"; 1403 description 1404 "List of carrier terminations in MIMO mode."; 1406 leaf name { 1407 type string; 1408 description 1409 "Name used for identification of the MIMO group."; 1410 } 1412 leaf enabled { 1413 type boolean; 1414 default "false"; 1415 description 1416 "Enable(true)/disable(false) MIMO"; 1417 } 1419 leaf-list members { 1420 type if:interface-ref; 1421 must "/if:interfaces/if:interface[if:name = current()]" 1422 + "/if:type = 'mrl:carrier-termination'" { 1423 description 1424 "The type of a member must be 'carrier-termination'."; 1425 } 1426 min-elements 2; 1427 description 1428 "Association to a MIMO group if used in the radio 1429 link terminal."; 1430 } 1431 } 1432 } 1433 } 1435 1437 5. Interface Protection YANG Module 1439 The data nodes for management of the interface protection 1440 functionality is broken out from the Microwave Radio Link Module 1441 into a separate and generic YANG data module in order to make it 1442 available also for other interface types. 1444 This module imports modules from [RFC7223bis], and it references 1445 [G.808.1]. 1447 file "ietf-interface-protection@2018-03-03.yang" 1449 module ietf-interface-protection { 1450 yang-version 1.1; 1451 namespace "urn:ietf:params:xml:ns:yang:ietf-interface-protection"; 1452 prefix ifprot; 1453 import ietf-interfaces { 1454 prefix if; 1455 reference "RFC7223bis"; 1456 // RFC Ed.: replace 7223bis with actual RFC number and remove 1457 // this note 1458 } 1460 organization 1461 "Internet Engineering Task Force (IETF) CCAMP WG"; 1462 contact 1463 "WG List: 1465 ID-draft editors: 1466 Jonas Ahlberg (jonas.ahlberg@ericsson.com); 1467 Min Ye (amy.yemin@huawei.com); 1468 Xi Li (Xi.Li@neclab.eu); 1469 Daniela Spreafico (daniela.spreafico@nokia.com) 1470 Marko Vaupotic (Marko.Vaupotic@aviatnet.com)"; 1472 description 1473 "This is a module for the entities in 1474 a generic interface protection mechanism. 1476 Copyright (c) 2018 IETF Trust and the persons identified as 1477 authors of the code. All rights reserved. 1479 Redistribution and use in source and binary forms, with or 1480 without modification, is permitted pursuant to, and subject 1481 to the license terms contained in, the Simplified BSD License 1482 set forth in Section 4.c of the IETF Trust's Legal Provisions 1483 Relating to IETF Documents 1484 (http://trustee.ietf.org/license-info). 1486 This version of this YANG module is part of RFC XXXX; see 1487 the RFC itself for full legal notices. 1489 Copyright (c) 2018 IETF Trust and the persons identified as 1490 authors of the code. All rights reserved."; 1492 revision 2018-03-03 { 1493 description "Initial revision."; 1494 reference "RFC XXXX: A YANG Data Model for Microwave Radio Link"; 1495 // RFC Ed.: replace XXXX with actual RFC number and remove 1496 // this note 1497 } 1499 /* 1500 * Protection architecture type identities 1501 */ 1503 identity protection-architecture-type { 1504 description 1505 "protection architecture type"; 1506 reference "ITU-T G.808.1"; 1507 } 1509 identity one-plus-one-type { 1510 base protection-architecture-type; 1511 description 1512 "1+1, One interface protects 1513 another one interface."; 1514 reference "ITU-T G.808.1"; 1515 } 1517 identity one-to-n-type { 1518 base protection-architecture-type; 1519 description 1520 "1:N, One interface protects 1521 n other interfaces."; 1522 reference "ITU-T G.808.1"; 1523 } 1525 /* 1526 * Protection states identities 1527 */ 1529 identity protection-states { 1530 description 1531 "Identities describing the status of the protection, 1532 in a group of interfaces configured in 1533 a protection mode."; 1534 } 1536 identity unprotected { 1537 base protection-states; 1538 description "Not protected"; 1539 } 1541 identity protected { 1542 base protection-states; 1543 description "Protected"; 1544 } 1546 identity unable-to-protect { 1547 base protection-states; 1548 description "Unable to protect"; 1549 } 1551 /* 1552 * protection-external-commands identities 1553 */ 1555 identity protection-external-commands{ 1556 description 1557 "Protection external commands for trouble shooting 1558 purpose."; 1559 reference "ITU-T G.808.1"; 1560 } 1562 identity manual-switch-working{ 1563 base protection-external-commands; 1564 description 1565 "A switch action initiated by an operator command. 1566 It switches normal traffic signal to the working 1567 transport entity."; 1568 reference "ITU-T G.808.1"; 1569 } 1571 identity manual-switch-protection{ 1572 base protection-external-commands; 1573 description 1574 "A switch action initiated by an operator command. 1575 It switches normal traffic signal to the protection 1576 transport entity."; 1577 reference "ITU-T G.808.1"; 1578 } 1580 identity forced-switch{ 1581 base protection-external-commands; 1582 description 1583 "A switch action initiated by an operator command. 1584 It switches normal traffic signal to the protection 1585 transport entity and forces it to remain on that 1586 entity even when criteria for switching back to 1587 the original entity are fulfilled."; 1588 reference "ITU-T G.808.1"; 1589 } 1591 identity lockout-of-protection{ 1592 base protection-external-commands; 1593 description 1594 "A switch action temporarily disables access to the 1595 protection transport entity for all signals."; 1596 reference "ITU-T G.808.1"; 1597 } 1598 identity freeze{ 1599 base protection-external-commands; 1600 description 1601 "A switch action temporarily prevents any switch action 1602 to be taken and, as such, freezes the current state. 1603 Until the freeze is cleared, additional near-end external 1604 commands are rejected and fault condition changes and 1605 received APS messages are ignored.."; 1606 reference "ITU-T G.808.1"; 1607 } 1609 identity exercise{ 1610 base protection-external-commands; 1611 description 1612 "A switch action to test if the APS communication is 1613 operating correctly. It is lower priority than any 'real' 1614 switch request.."; 1615 reference "ITU-T G.808.1"; 1616 } 1618 identity clear{ 1619 base protection-external-commands; 1620 description 1621 "An action clears all switch commands."; 1622 reference "ITU-T G.808.1"; 1623 } 1625 /* 1626 * Protection Groups 1627 */ 1629 grouping protection-groups { 1630 description 1631 "Configuration of protected groups (1+1) of interfaces 1632 providing protection for each other. More than one protected 1633 group per higher-layer-interface is allowed."; 1635 list protection-group { 1636 key "name"; 1637 description 1638 "List of protected groups of interfaces 1639 in a higher-layer-interface."; 1641 leaf name { 1642 type string; 1643 description 1644 "Name used for identification of the protection group"; 1645 } 1646 leaf protection-architecture-type { 1647 type identityref{ 1648 base protection-architecture-type; 1649 } 1650 default "ifprot:one-plus-one-type"; 1651 description 1652 "The type of protection architecture used, e.g. one 1653 interface protecting one or several other interfaces."; 1654 reference "ITU-T G.808.1"; 1655 } 1657 leaf-list members { 1658 type if:interface-ref; 1659 min-elements 2; 1660 description 1661 "Association to a group of interfaces configured for 1662 protection and used by a higher-layer-interface."; 1663 } 1665 leaf operation-type { 1666 type enumeration { 1667 enum "non-revertive" { 1668 description 1669 "In non revertive operation, the traffic does not 1670 return to the working interface if the switch requests 1671 are terminated."; 1672 reference "ITU-T G.808.1"; 1673 } 1674 enum "revertive" { 1675 description 1676 "In revertive operation, the traffic always 1677 returns to (or remains on) the working interface 1678 if the switch requests are terminated."; 1679 reference "ITU-T G.808.1"; 1680 } 1681 } 1682 default "non-revertive"; 1683 description 1684 "The type of protection operation, i.e. revertive 1685 or non-revertive operation."; 1686 } 1688 leaf-list working-entity { 1689 when "../operation-type = 'revertive'"; 1690 type if:interface-ref; 1691 min-elements 1; 1692 description 1693 "The interfaces over which the traffic normally should 1694 be transported over when there is no need to use the 1695 protecting interface."; 1696 } 1697 leaf revertive-wait-to-restore { 1698 when "../operation-type = 'revertive'"; 1699 type uint16; 1700 units "seconds"; 1701 default "0"; 1702 description 1703 "The time to wait before switching back to the working 1704 interface if operation-type is revertive."; 1705 reference "ITU-T G.808.1"; 1706 } 1708 leaf hold-off-timer { 1709 type uint16; 1710 units "milliseconds"; 1711 default "0"; 1712 description 1713 "Time interval after the detection of a fault and its 1714 confirmation as a condition requiring the protection 1715 switching procedure."; 1716 reference "ITU-T G.808.1"; 1717 } 1719 leaf status { 1720 type identityref { 1721 base protection-states; 1722 } 1723 description 1724 "Status of the protection, in a group of interfaces 1725 configured in a protection mode."; 1726 reference "ITU-T G.808.1"; 1727 } 1729 action external-commands { 1730 input { 1731 leaf external-command { 1732 type identityref { 1733 base protection-external-commands; 1734 } 1735 description 1736 "Execution of protection external commands for 1737 trouble shooting purpose."; 1738 } 1739 } 1740 } 1741 } 1742 } 1743 } 1745 1747 6. Security Considerations 1749 The YANG module specified in this document defines a schema for data 1750 that is designed to be accessed via network management protocols such 1751 as NETCONF [RFC6241] or RESTCONF [RFC8040]. The lowest NETCONF layer 1752 is the secure transport layer, and the mandatory-to-implement secure 1753 transport is Secure Shell (SSH) [RFC6242]. The lowest RESTCONF layer 1754 is HTTPS, and the mandatory-to-implement secure transport is TLS 1755 [RFC5246]. 1757 The NETCONF access control model [RFC6536] provides the means to 1758 restrict access for particular NETCONF or RESTCONF users to a 1759 preconfigured subset of all available NETCONF or RESTCONF protocol 1760 operations and content. 1762 There are a number of data nodes defined in this YANG module that are 1763 writable/creatable/deletable (i.e., config true, which is the 1764 default). These data nodes may be considered sensitive or vulnerable 1765 in some network environments. Write operations (e.g., edit-config) 1766 to these data nodes without proper protection can have a negative 1767 effect on network operations. These are the subtrees and data nodes 1768 and their sensitivity/vulnerability: 1770 Interfaces of type radio-link-terminal: 1771 /if:interfaces/if:interface/carrier-terminations, 1772 /if:interfaces/if:interface/rlp-groups, 1773 /if:interfaces/if:interface/xpic-pairs, 1774 /if:interfaces/if:interface/mimo-groups, and 1775 /if:interfaces/if:interface/tdm-connections: 1776 These lists represent the configuration of the radio-link-terminal 1777 and it need to match the configuration of the radio-link-terminal 1778 on the other side of the radio link. Unauthorized access to these 1779 data nodes could interrupt the ability to forward traffic. 1781 Interfaces of type carrier-termination: 1782 /if:interfaces/if:interface/carrier-id, 1783 /if:interfaces/if:interface/tx-enabled, 1784 /if:interfaces/if:interface/tx-frequency, 1785 /if:interfaces/if:interface/rx-frequency, 1786 /if:interfaces/if:interface/duplex-distance, 1787 /if:interfaces/if:interface/channel-separation, 1788 /if:interfaces/if:interface/power-mode, 1789 /if:interfaces/if:interface/maximum-nominal-power, 1790 /if:interfaces/if:interface/atpc-lower-threshold, 1791 /if:interfaces/if:interface/atpc-upper-threshold, 1792 /if:interfaces/if:interface/coding-modulation-mode, 1793 /if:interfaces/if:interface/selected-cm, 1794 /if:interfaces/if:interface/selected-min-acm, 1795 /if:interfaces/if:interface/selected-max-acm, 1796 /if:interfaces/if:interface/if-loop, and 1797 /if:interfaces/if:interface/rf-loop: 1799 These data nodes represent the configuration of the 1800 carrier-termination and it need to match the configuration of the 1801 carrier-termination on the other side of the carrier. Unauthorized 1802 access to these data nodes could interrupt the ability to forward 1803 traffic. 1805 Radio link protection: 1806 /radio-link-protection-groups/protection-group: 1807 This list of protection groups and the constituent data nodes 1808 represents the configuration of the protection of carrier 1809 terminations. Unauthorized access to these data nodes could 1810 interrupt the ability to forward traffic or remove the ability to 1811 perform a necessary protection switch. 1813 XPIC: 1814 /xpic-pairs: 1815 This list represents the XPIC configuration of a pair carriers. 1816 Unauthorized access to these data nodes could interrupt the ability 1817 to forward traffic. 1819 MIMO: 1820 /mimo-groups: 1821 This list represents the MIMO configuration of multiple carriers. 1822 Unauthorized access to these data nodes could interrupt the ability 1823 to forward traffic. 1825 The security considerations of [RFC7223bis] also apply to this 1826 document. 1828 7. IANA Considerations 1830 It is proposed that IANA should assign new URIs from the 1831 "IETF XML Registry" [RFC3688] as follows: 1833 URI: urn:ietf:params:xml:ns:yang:ietf-microwave-radio-link 1834 Registrant Contact: The IESG 1835 XML: N/A; the requested URI is an XML namespace. 1837 URI: urn:ietf:params:xml:ns:yang:ietf-interface-protection 1838 Registrant Contact: The IESG 1839 XML: N/A; the requested URI is an XML namespace. 1841 It is proposed that IANA should record YANG module names in the 1842 "YANG Module Names" registry [RFC6020] as follows: 1844 Name: ietf-microwave-radio-link 1845 Namespace: urn:ietf:params:xml:ns:yang:ietf-microwave-radio-link 1846 Prefix: mrl 1847 Reference: RFC XXXX 1848 Name: ietf-interface-protection 1849 Namespace: urn:ietf:params:xml:ns:yang:ietf-interface-protection 1850 Prefix: ifprot 1851 Reference: RFC XXXX 1853 8. References 1855 8.1. Normative References 1857 [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate 1858 Requirement Levels", BCP 14, RFC 2119, 1859 DOI 10.17487/RFC2119, March 1997, 1860 . 1862 [RFC7223bis] 1863 Bjorklund, M., "A YANG Data Model for Interface 1864 Management", draft-bjorklund-netmod-rfc7223bis-00 1865 (work in progress), September 2017. 1867 [EN301129] ETSI, "Transmission and Multiplexing (TM); Digital Radio 1868 Relay Systems (DRRS); Synchronous Digital Hierarchy (SDH); 1869 System performance monitoring parameters of SDH DRRS", 1870 EN 301 129 V1.1.2, May 1995. 1872 [EN302217-1] 1873 ETSI, "Fixed Radio Systems; Characteristics and 1874 requirements for point-to-point equipment and antennas; 1875 Part 1: Overview, common characteristics and system- 1876 dependent requirements", EN 302 217-1 V3.0.5, June 2016. 1878 [EN302217-2] 1879 ETSI, "Fixed Radio Systems; Characteristics and 1880 requirements for point to-point equipment and antennas; 1881 Part 2: Digital systems operating in frequency bands from 1882 1 GHz to 86 GHz; Harmonised Standard covering the 1883 essential requirements of article 3.2 of Directive 1884 2014/53/EU", EN 302 217-2 V3.1.1, May 2017. 1886 [G.808.1] ITU-T, "SERIES G: TRANSMISSION SYSTEMS AND MEDIA, DIGITAL 1887 SYSTEMS AND NETWORKS; Digital networks ; General aspects 1888 Generic protection switching ; Linear trail and subnetwork 1889 protection", ITU-T Rec. G.808.1, May 2014. 1891 [G.826] ITU-T, "SERIES G: TRANSMISSION SYSTEMS AND MEDIA, DIGITAL 1892 SYSTEMS AND NETWORKS; Digital networks ; Quality and 1893 availability targets End-to-end error performance 1894 parameters and objectives for international, constant 1895 bit-rate digital paths and connections", ITU-T Rec. G.826, 1896 December 2002. 1898 [TR102311] ETSI, "Fixed Radio Systems; Point-to-point equipment; 1899 Specific aspects of the spatial frequency reuse method", 1900 ETSI TR 102 311 V1.2.1, November 2015. 1902 [RFC3688] Mealling, M., "The IETF XML Registry", BCP 81, RFC 3688, 1903 DOI 10.17487/RFC3688, January 2004, . 1906 [RFC5246] Dierks, T. and E. Rescorla, "The Transport Layer Security 1907 (TLS) Protocol Version 1.2", RFC 5246, 1908 DOI 10.17487/RFC5246, August 2008, 1909 . 1911 [RFC6020] Bjorklund, M., Ed., "YANG - A Data Modeling Language for 1912 the Network Configuration Protocol (NETCONF)", RFC 6020, 1913 DOI 10.17487/RFC6020, October 2010, 1914 . 1916 [RFC6241] Enns, R., Bjorklund, M., Schoenwaelder, J., and A. 1917 Bierman, "Network Configuration Protocol (NETCONF)", 1918 RFC 6241, June 2011. 1920 [RFC6242] Wasserman, M., "Using the NETCONF Protocol over Secure 1921 Shell (SSH)", RFC 6242, June 2011. 1923 [RFC6536] Bierman, A. and M. Bjorklund, "Network Configuration 1924 Protocol (NETCONF) Access Control Model", RFC 6536, 1925 March 2012. 1927 [RFC6991] Schoenwaelder, J., "Common YANG Data Types", RFC 6991, 1928 July 2013. 1930 [RFC7224] Bjorklund, M., "IANA Interface Type YANG Module", 1931 RFC 7224, May 2014. 1933 [RFC8040] Bierman, A., Bjorklund, M., and K. Watsen, "RESTCONF 1934 Protocol", RFC 8040, DOI 10.17487/RFC8040, January 2017, 1935 . 1937 8.2. Informative References 1939 [NMDA] Bjorklund, M., Schoenwaelder, J., Shafer, P., Watsen, K., 1940 and R. Wilton, "Network Management Datastore 1941 Architecture", draft-ietf-netmod-revised-datastores-10 1942 (work in progress), January 2018. 1944 [I-D.ahlberg-ccamp-microwave-radio-link] 1945 Ahlberg, J., Carlson, J., Lund, H., Olausson, T., Ye, M., 1946 and M. Vaupotic, "Microwave Radio Link YANG Data Models", 1947 draft-ahlberg-ccamp-microwave-radio-link-01 (work in 1948 progress), May 2016. 1950 [I-D.ietf-ccamp-microwave-framework] 1951 Ahlberg, J., Contreras, L., Ye, M., Vaupotic, M., 1952 Tantsura, J., Kawada, K., Li, X., Akiyoshi, I., C. 1953 Bernardos, and D. Spreafico, "A framework for Management 1954 and Control of microwave and millimeter wave interface 1955 parameters", draft-ietf-ccamp-microwave-framework-05 1956 (work in progress), October 2017. 1958 [ONF-model] "Microwave Modeling - ONF Wireless Transport Group", 1959 May 2016. 1961 [RFC6241] Enns, R., Ed., Bjorklund, M., Ed., Schoenwaelder, J., Ed., 1962 and A. Bierman, Ed., "Network Configuration Protocol 1963 (NETCONF)", RFC 6241, DOI 10.17487/RFC6241, June 2011, 1964 . 1966 [RFC6242] Wasserman, M., "Using the NETCONF Protocol over Secure 1967 Shell (SSH)", RFC 6242, DOI 10.17487/RFC6242, June 2011, 1968 . 1970 [RFC6536] Bierman, A. and M. Bjorklund, "Network Configuration 1971 Protocol (NETCONF) Access Control Model", RFC 6536, 1972 DOI 10.17487/RFC6536, March 2012, 1973 . 1975 [YANG-TREE] Bjorklund, M. and L. Berger, "YANG Tree Diagrams", draft- 1976 ietf-netmod-yang-tree-diagrams-06 (work in progress), 1977 February 2018. 1979 Appendix A. Example: 1+0 and 2+0 configuration instances 1981 This section gives simple examples of 1+0 and 2+0 instance using the 1982 YANG module defined in this draft. The examples are not intended as 1983 a complete module for 1+0 and 2+0 configuration. 1985 A.1 1+0 instance 1987 Figure A-1 shows a 1+0 example. 1988 /--------- Radio Link ---------\ 1989 Near End Far End 1991 +---------------+ +---------------+ 1992 | Radio Link | | Radio Link | 1993 | Terminal - A | | Terminal - B | 1994 | | | | 1995 | | | | 1996 | +-----------+ | | +-----------+ | 1997 | | | | Carrier A | | | | 1998 | | Carrier | |<--------->| | Carrier | | 1999 | |Termination| | | |Termination| | 2000 | | -1 | | | | -1 | | 2001 | +-----------+ | | +-----------+ | 2002 | | | | 2003 | | | | 2004 +---------------+ +---------------+ 2006 \--- Microwave Node ---/ \--- Microwave Node ---/ 2007 Figure A-1 1+0 example 2009 The following instance shows the 1+0 configuration of Near End node. 2011 "interface": [ 2012 { 2013 //RLT-A 2014 "name": "RLT-A", 2015 "description": "Radio Link Terminal A", 2016 "type": "mrl:radio-link-terminal", 2017 "id": "RLT-A", 2018 "mode": "one-plus-zero", 2019 "carrier-terminations": [ 2020 "RLT-A:CT-1", 2021 ], 2022 } 2023 { 2024 //CT-1 2025 "name": "RLT-A:CT-1", 2026 "description": "Carrier Termination 1", 2027 "type": "mrl:carrier-termination", 2028 "carrier-id": "A", 2029 "tx-enabled": true, 2030 "tx-oper-status": on 2031 "tx-frequency": 10728000, 2032 "duplex-distance": 644000, 2033 "channel-separation": 28, 2034 "polarization": not-specified, 2035 "power-mode": rtpc, 2036 "coding-modulation-mode": 0, 2037 "selected-cm": "qam-512" 2038 }, 2039 ] 2041 A.2 2+0 instance 2043 Figure A-2 shows a 2+0 example. 2044 /--------- Radio Link ---------\ 2045 Near End Far End 2047 +---------------+ +---------------+ 2048 | Radio Link | | Radio Link | 2049 | Terminal -A | | Terminal -B | 2050 | | | | 2051 | | | | 2052 | +-----------+ | | +-----------+ | 2053 | | | | Carrier A | | | | 2054 | | Carrier | |<--------->| | Carrier | | 2055 | |Termination| | | |Termination| | 2056 | | -1 | | | | -1 | | 2057 | +-----------+ | | +-----------+ | 2058 | | | | 2059 | +-----------+ | | +-----------+ | 2060 | | | | Carrier B | | | | 2061 | | Carrier | |<--------->| | Carrier | | 2062 | |Termination| | | |Termination| | 2063 | | -2 | | | | -2 | | 2064 | +-----------+ | | +-----------+ | 2065 | | | | 2066 +---------------+ +---------------+ 2068 \--- Microwave Node ---/ \--- Microwave Node ---/] 2069 Figure A-2 2+0 example 2071 The following instance shows the 2+0 configuration of Near End node. 2072 "interface": [ 2073 { 2074 //RLT-A 2075 "name": "RLT-A", 2076 "description": "Radio Link Terminal A", 2077 "type": "mrl:radio-link-terminal", 2078 "id": "RLT-A", 2079 "mode": "two-plus-zero", 2080 "carrier-terminations": [ 2081 "RLT-A:CT-1", 2082 "RLT-A:CT-2" 2083 ], 2084 } 2086 { 2087 //CT-1 2088 "name": "RLT-A:CT-1", 2089 "description": "Carrier Termination 1", 2090 "type": "mrl:carrier-termination", 2091 "carrier-id": "A", 2092 "tx-enabled": true, 2093 "tx-oper-status": on 2094 "tx-frequency": 10728000, 2095 "duplex-distance": 644000, 2096 "channel-separation": 28, 2097 "polarization": not-specified, 2098 "power-mode": rtpc, 2099 "coding-modulation-mode": 0, 2100 "selected-cm": "qam-512" 2101 }, 2103 { 2104 //CT-2 2105 "name": "RLT-A:CT-2", 2106 "description": "Carrier Termination 2", 2107 "type": "mrl:carrier-termination", 2108 "carrier-id": "B", 2109 "tx-enabled": true, 2110 "tx-oper-status": on 2111 "tx-frequency": 10618000, 2112 "duplex-distance": 644000, 2113 "channel-separation": 28, 2114 "polarization": not-specified, 2115 "power-mode": rtpc, 2116 "coding-modulation-mode": 0, 2117 "selected-cm": "qam-512" 2118 }, 2119 ] 2121 Appendix B. Contributors 2123 Koji Kawada 2124 NEC Corporation 2125 1753, Shimonumabe Nakahara-ku 2126 Kawasaki, Kanagawa 211-8666 2127 Japan (JPN) 2129 Email: k-kawada@ah.jp.nec.com 2131 Carlos J. Bernardos 2132 Universidad Carlos III de Madrid 2133 Av. Universidad, 30 2134 Leganes, Madrid 28911 2135 Spain (ESP) 2137 Email: cjbc@it.uc3m.es 2139 Authors' Addresses 2141 Jonas Ahlberg 2142 Ericsson AB 2143 Lindholmspiren 11 2144 Goeteborg 417 56 2145 Sweden (SWE) 2147 Email: jonas.ahlberg@ericsson.com 2149 Ye Min 2150 Huawei Technologies 2151 No.1899, Xiyuan Avenue 2152 Chengdu 611731 2153 P.R.China (CHN) 2155 Email: amy.yemin@huawei.com 2157 Xi Li 2158 NEC Laboratories Europe GmbH 2159 Kurfursten-Anlage 36 2160 69115 Heidelberg 2161 Germany (DEU) 2163 Email: Xi.Li@neclab.eu 2164 Daniela Spreafico 2165 Nokia - IT 2166 Via Energy Park, 14 2167 Vimercate (MI) 20871 2168 Italy (ITA) 2170 Email: daniela.spreafico@nokia.com 2172 Marko Vaupotic 2173 Aviat Networks 2174 Motnica 9 2175 Trzin-Ljubljana 1236 2176 Slovenia (SVN) 2178 Email: Marko.Vaupotic@Aviatnet.com