idnits 2.17.1 draft-ietf-ccamp-mw-yang-02.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 (October 23, 2017) is 2374 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' == Outdated reference: A later version (-10) exists of draft-ietf-netmod-revised-datastores-05 == Outdated reference: A later version (-07) exists of draft-ietf-ccamp-microwave-framework-02 -- Obsolete informational reference (is this intentional?): RFC 6536 (Obsoleted by RFC 8341) Summary: 0 errors (**), 0 flaws (~~), 4 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: April 26, 2018 Huawei Technologies 6 X. Li 7 NEC Laboratories Europe 8 K. Kawada 9 NEC Corporation 10 CJ. Bernardos 11 Universidad Carlos III de Madrid 12 D. Spreafico 13 Nokia - IT 14 M. Vaupotic 15 Aviat Networks 16 October 23, 2017 18 A YANG Data Model for Microwave Radio Link 19 draft-ietf-ccamp-mw-yang-02 21 Abstract 23 This document defines a YANG data model for control and management 24 of the radio link interfaces, and their connectivity to packet 25 (typically Ethernet) interfaces in a microwave/millimeter wave node. 26 The data nodes for management of the interface protection 27 functionality is broken out into a separate and generic YANG data 28 model in order to make it available also for other interface types. 30 Requirements Language 32 The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", 33 "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this 34 document are to be interpreted as described in [RFC2119]. 36 Status of This Memo 38 This Internet-Draft is submitted in full conformance with the 39 provisions of BCP 78 and BCP 79. 41 Internet-Drafts are working documents of the Internet Engineering 42 Task Force (IETF). Note that other groups may also distribute 43 working documents as Internet-Drafts. The list of current Internet- 44 Drafts is at http://datatracker.ietf.org/drafts/current/. 46 Internet-Drafts are draft documents valid for a maximum of six months 47 and may be updated, replaced, or obsoleted by other documents at any 48 time. It is inappropriate to use Internet-Drafts as reference 49 material or to cite them other than as "work in progress." 51 This Internet-Draft will expire on April 26, 2018. 53 Copyright Notice 55 Copyright (c) 2017 IETF Trust and the persons identified as the 56 document authors. All rights reserved. 58 This document is subject to BCP 78 and the IETF Trust's Legal 59 Provisions Relating to IETF Documents 60 (http://trustee.ietf.org/license-info) in effect on the date of 61 publication of this document. Please review these documents 62 carefully, as they describe your rights and restrictions with respect 63 to this document. Code Components extracted from this document must 64 include Simplified BSD License text as described in Section 4.e of 65 the Trust Legal Provisions and are provided without warranty as 66 described in the Simplified BSD License. 68 Table of Contents 70 1. Terminology and Definitions . . . . . . . . . . . . . . . . . 2 71 2. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 3 72 3. Microwave Radio Link YANG Data Model. . . . . . . . . . . . . 4 73 3.1. YANG Tree . . . . . . . . . . . . . . . . . . . . . . . . 4 74 3.2. Explanation of the Microwave Data Model . . . . . . . . . 5 75 4. Microwave Radio Link YANG Module . . . . . . . . . . . . . . 6 76 5. Interface Protection YANG Module . . . . . . . . . . . . . . 30 77 6. Security Considerations . . . . . . . . . . . . . . . . . . . 36 78 7. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 36 79 8. References . . . . . . . . . . . . . . . . . . . . . . . . . 37 80 8.1. Normative References . . . . . . . . . . . . . . . . . . 37 81 8.2. Informative References . . . . . . . . . . . . . . . . . 37 82 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 38 84 1. Terminology and Definitions 86 The following terms are used in this document: 88 Carrier Termination (CT) is an interface for the capacity provided 89 over the air by a single carrier. It is typically defined by its 90 transmitting and receiving frequencies. 92 Radio Link Terminal (RLT) is an interface providing packet capacity 93 and/or TDM capacity to the associated Ethernet and/or TDM interfaces 94 in a node and used for setting up a transport service over a 95 microwave/millimeter wave link. 97 The following acronyms are used in this document: 99 ACM Adaptive Coding Modulation 101 ATPC Automatic Transmit Power Control 103 CM Coding Modulation 104 CT Carrier Termination 106 RLT Radio Link Terminal 108 RTPC Remote Transmit Power Control 110 XPIC Cross Polarization Interference Cancellation 112 MIMO Multiple-Input Multiple-Output 114 2. Introduction 116 This document defines a YANG data model for management and control of 117 the radio link interface(s) and the relationship to packet (typically 118 Ethernet) and/or TDM interfaces in a microwave/millimeter wave node. 119 ETSI EN 302 217 series defines the characteristics and requirements 120 of microwave/millimeter wave equipment and antennas. Especially ETSI 121 EN 302 217-2 [EN 302 217-2] specifies the essential parameters for 122 the systems operating from 1.4GHz to 86GHz. The data model includes 123 configuration and state data according to the new Network Management 124 Datastore Architecture [NMDA]. 126 The design of the data model follows the framework for management and 127 control of microwave and millimeter wave interface parameters defined 128 in [I-D.ietf-ccamp-microwave-framework]. This framework identifies 129 the need and the scope of the YANG data model, the use cases and 130 requirements that the model needs to support. Moreover, it provides 131 a detailed gap analysis to identify the missing parameters and 132 functionalities of the existing and established models to support the 133 specified use cases and requirements, and based on that recommends 134 how the gaps should be filled with the development of the new model. 136 According to the conclusion of the gap analysis, the structure of the 137 data model is based on the structure defined in 138 [I-D.ahlberg-ccamp-microwave-radio-link] and it augments [RFC7223bis] 139 to align with the same structure for management of the packet 140 interfaces. More specifically, the model will include interface 141 layering to manage the capacity provided by a radio link terminal for 142 the associated Ethernet and TDM interfaces, using the principles for 143 interface layering described in RFC 7223 bis as a basis. 145 The data nodes for management of the interface protection 146 functionality is broken out into a separate and generic YANG data 147 module in order to make it available also for other interface types. 149 The designed YANG data model uses established microwave equipment 150 and radio standards, such as ETSI EN 302 217-2, and the IETF: Radio 151 Link Model[I-D.ahlberg-ccamp-microwave-radio-link] and the ONF: 152 Microwave Modeling[ONF-model] as the basis for the definition of the 153 detailed leafs/parameters, and proposes new ones to cover identified 154 gaps which are analysed in[I-D.ietf-ccamp-microwave-framework]. 156 3. Microwave Radio Link YANG Data Model 158 3.1. YANG Tree 160 module: ietf-microwave-radio-link 161 +--rw radio-link-protection-groups 162 | +--rw protection-group* [name] 163 | +--rw name string 164 | +--rw protection-architecture-type? identityref 165 | +--rw protection-members* if:interface-ref 166 | +--rw protection-operation-type? enumeration 167 | +--rw working-entity* if:interface-ref 168 | +--rw revertive-wait-to-restore? uint16 169 | +--rw hold-off-timer? uint16 170 | +--rw protection-status? identityref 171 | +---x protection-external-commands 172 | +---w input 173 | +---w protection-external-command? identityref 174 +--rw xpic-pairs {xpic}? 175 | +--rw xpic-pair* [name] 176 | +--rw name string 177 | +--rw enabled? boolean 178 | +--rw xpic-members* if:interface-ref 179 +--rw mimo-groups {mimo}? 180 +--rw mimo-group* [name] 181 +--rw name string 182 +--rw enabled? boolean 183 +--rw mimo-members* if:interface-ref 184 augment /if:interfaces/if:interface: 185 +--rw id? string 186 +--rw mode identityref 187 +--rw carrier-terminations* if:interface-ref 188 +--rw rlp-groups* 189 | -> /radio-link-protection-groups/protection-group/name 190 +--rw xpic-pairs* -> /xpic-pairs/xpic-pair/name 191 | {xpic}? 192 +--rw mimo-groups* -> /mimo-groups/mimo-group/name 193 | {mimo}? 194 +--rw tdm-connections* [tdm-type] {tdm}? 195 +--rw tdm-type identityref 196 +--rw tdm-connections uint16 197 augment /if:interfaces/if:interface: 198 +--rw carrier-id? string 199 +--rw tx-enabled? boolean 200 +--ro tx-oper-status? enumeration 201 +--rw tx-frequency uint32 202 +--rw rx-frequency? uint32 203 +--rw duplex-distance? uint32 204 +--rw channel-separation uint32 205 +--rw polarization? enumeration 206 +--rw power-mode enumeration 207 +--rw maximum-nominal-power power 208 +--rw atpc-lower-threshold power 209 +--rw atpc-upper-threshold power 210 +--ro actual-transmitted-level? power 211 +--ro actual-received-level? power 212 +--rw coding-modulation-mode enumeration 213 +--rw selected-cm identityref 214 +--rw selected-min-acm identityref 215 +--rw selected-max-acm identityref 216 +--ro actual-tx-cm? identityref 217 +--ro actual-snir? decimal64 218 +--ro actual-xpi? decimal64 {xpic}? 219 +--rw ct-performance-thresholds 220 | +--rw received-level-alarm-threshold? power 221 | +--rw transmitted-level-alarm-threshold? power 222 | +--rw ber-alarm-threshold? enumeration 223 +--rw if-loop? enumeration 224 +--rw rf-loop? enumeration 225 +--ro capabilities 226 | +--ro min-tx-frequency? uint32 227 | +--ro max-tx-frequency? uint32 228 | +--ro min-rx-frequency? uint32 229 | +--ro max-rx-frequency? uint32 230 | +--ro minimum-power? power 231 | +--ro maximum-available-power? power 232 | +--ro available-min-acm? identityref 233 | +--ro available-max-acm? identityref 234 +--ro error-performance-statistics 235 | +--ro bbe? yang:counter32 236 | +--ro es? yang:counter32 237 | +--ro ses? yang:counter32 238 | +--ro uas? yang:counter32 239 +--ro radio-performance-statistics 240 +--ro min-rltm? power 241 +--ro max-rltm? power 242 +--ro min-tltm? power 243 +--ro max-tltm? power 245 3.2. Explanation of the Microwave Data Model 247 The leafs in the Interface Management Module augmented by Radio Link 248 Terminal (RLT) and Carrier Termination (CT) are not always 249 applicable. 251 "/interfaces/interface/enabled" is not applicable for RLT. Enable and 252 disable of an interface is done in the constituent CTs. 254 The packet related measurements "in-octets", "in-unicast-pkts", "in- 255 broadcast-pkts", "in-multicast-pkts", "in-discards", "in-errors", 256 "in-unknown-protos", "out-octets", "out-unicast-pkts", "out- 257 broadcast-pkts", "out-multicast-pkts", "out-discards", "out-errors" 258 are not within the scope of the microwave radio link domain and 259 therefore not applicable for RLT and CT. 261 4. Microwave Radio Link YANG Module 263 file "ietf-microwave-radio-link.yang" 265 module ietf-microwave-radio-link { 266 yang-version 1.1; 267 namespace "urn:ietf:params:xml:ns:yang:ietf-microwave-radio-link"; 268 prefix mrl; 270 import ietf-yang-types { 271 prefix yang; 272 } 274 import ietf-interfaces { 275 prefix if; 276 } 278 import ietf-interface-protection { 279 prefix ifprot; 280 } 282 import iana-if-type { 283 prefix ianaift; 284 } 286 organization 287 "Internet Engineering Task Force (IETF) CCAMP WG"; 288 contact 289 "WG List: 291 ID-draft authors: 292 Jonas Ahlberg (jonas.ahlberg@ericsson.com); 293 Min Ye (amy.yemin@huawei.com); 294 Xi Li (Xi.Li@neclab.eu); 295 Koji Kawada (k-kawada@ah.jp.nec.com) 296 Carlos J. Bernardos (cjbc@it.uc3m.es) 297 Daniela Spreafico (daniela.spreafico@nokia.com) 298 Marko Vaupotic (Marko.Vaupotic@aviatnet.com)"; 300 description 301 "This is a module for the entities in 302 a generic microwave system."; 304 revision 2017-10-23 { 305 description 306 "Break out protection functionality to a generic module 307 and update to follow the new NMDA style."; 308 reference ""; 309 } 310 revision 2017-06-21 { 311 description 312 "Updated draft revision with updates of some descriptions to 313 increase clarity and some minor adjustments of the model."; 314 reference ""; 315 } 316 revision 2016-12-22 { 317 description 318 "Draft revision covering a complete scope for configuration 319 and state data for radio link interfaces."; 320 reference ""; 321 } 322 revision 2016-10-29 { 323 description 324 "Draft revision."; 325 reference ""; 326 } 328 /* 329 * Features 330 */ 332 feature xpic { 333 description 334 "Indicates that the device supports XPIC."; 335 reference "ETSI TR 102 311"; 336 } 338 feature mimo { 339 description 340 "Indicates that the device supports MIMO."; 341 reference "ETSI TR 102 311"; 342 } 344 feature tdm { 345 description 346 "Indicates that the device supports TDM."; 347 } 349 /* 350 * Interface identities 351 */ 353 identity radio-link-terminal { 354 base ianaift:iana-interface-type; 355 description 356 "Interface identity for a radio link terminal."; 357 } 358 identity carrier-termination { 359 base ianaift:iana-interface-type; 360 description 361 "Interface identity for a carrier termination."; 362 } 364 /* 365 * Radio-link-terminal mode identities 366 */ 368 identity rlt-mode { 369 description 370 "A description of the mode in which the radio link 371 terminal is configured. The format is X plus Y. 372 X represent the number of bonded carrier terminations. 373 Y represent the number of protecting carrier 374 terminations."; 375 } 377 identity one-plus-zero { 378 base rlt-mode; 379 description 380 "1 carrier termination only."; 381 } 383 identity one-plus-one { 384 base rlt-mode; 385 description 386 "1 carrier termination 387 and 1 protecting carrier termination."; 388 } 390 identity two-plus-zero { 391 base rlt-mode; 392 description 393 "2 bonded carrier terminations."; 394 } 396 /* 397 * Coding and modulation identities 398 */ 400 identity coding-modulation { 401 description 402 "The coding and modulation schemes."; 403 } 405 identity half-bpsk-strong { 406 base coding-modulation; 407 description 408 "Half BPSK strong coding and modulation scheme."; 409 } 410 identity half-bpsk { 411 base coding-modulation; 412 description 413 "Half BPSK coding and modulation scheme."; 414 } 416 identity half-bpsk-light { 417 base coding-modulation; 418 description 419 "Half BPSK light coding and modulation scheme."; 420 } 422 identity bpsk-strong { 423 base coding-modulation; 424 description 425 "BPSK strong coding and modulation scheme."; 426 } 428 identity bpsk { 429 base coding-modulation; 430 description 431 "BPSK coding and modulation scheme."; 432 } 434 identity bpsk-light { 435 base coding-modulation; 436 description 437 "BPSK light coding and modulation scheme."; 438 } 440 identity qpsk { 441 base coding-modulation; 442 description 443 "QPSK coding and modulation scheme."; 444 } 446 identity qam-4-strong { 447 base coding-modulation; 448 description 449 "4 QAM strong coding and modulation scheme."; 450 } 452 identity qam-4 { 453 base coding-modulation; 454 description 455 "4 QAM coding and modulation scheme."; 456 } 457 identity qam-4-light { 458 base coding-modulation; 459 description 460 "4 QAM light coding and modulation scheme."; 461 } 463 identity qam-16-strong { 464 base coding-modulation; 465 description 466 "16 QAM strong coding and modulation scheme."; 467 } 469 identity qam-16 { 470 base coding-modulation; 471 description 472 "16 QAM coding and modulation scheme."; 473 } 475 identity qam-16-light { 476 base coding-modulation; 477 description 478 "16 QAM light coding and modulation scheme."; 479 } 481 identity qam-32-strong { 482 base coding-modulation; 483 description 484 "32 QAM strong coding and modulation scheme."; 485 } 487 identity qam-32 { 488 base coding-modulation; 489 description 490 "32 QAM coding and modulation scheme."; 491 } 493 identity qam-32-light { 494 base coding-modulation; 495 description 496 "32 QAM light coding and modulation scheme."; 497 } 499 identity qam-64-strong { 500 base coding-modulation; 501 description 502 "64 QAM strong coding and modulation scheme."; 503 } 504 identity qam-64 { 505 base coding-modulation; 506 description 507 "64 QAM coding and modulation scheme."; 508 } 510 identity qam-64-light { 511 base coding-modulation; 512 description 513 "64 QAM light coding and modulation scheme."; 514 } 516 identity qam-128-strong { 517 base coding-modulation; 518 description 519 "128 QAM strong coding and modulation scheme."; 520 } 522 identity qam-128 { 523 base coding-modulation; 524 description 525 "128 QAM coding and modulation scheme."; 526 } 528 identity qam-128-light { 529 base coding-modulation; 530 description 531 "128 QAM light coding and modulation scheme."; 532 } 534 identity qam-256-strong { 535 base coding-modulation; 536 description 537 "256 QAM strong coding and modulation scheme."; 538 } 540 identity qam-256 { 541 base coding-modulation; 542 description 543 "256 QAM coding and modulation scheme."; 544 } 546 identity qam-256-light { 547 base coding-modulation; 548 description 549 "256 QAM light coding and modulation scheme."; 550 } 551 identity qam-512-strong { 552 base coding-modulation; 553 description 554 "512 QAM strong coding and modulation scheme."; 555 } 557 identity qam-512 { 558 base coding-modulation; 559 description 560 "512 QAM coding and modulation scheme."; 561 } 563 identity qam-512-light { 564 base coding-modulation; 565 description 566 "512 QAM light coding and modulation scheme."; 567 } 569 identity qam-1024-strong { 570 base coding-modulation; 571 description 572 "1024 QAM strong coding and modulation scheme."; 573 } 575 identity qam-1024 { 576 base coding-modulation; 577 description 578 "1024 QAM coding and modulation scheme."; 579 } 581 identity qam-1024-light { 582 base coding-modulation; 583 description 584 "1024 QAM light coding and modulation scheme."; 585 } 587 identity qam-2048-strong { 588 base coding-modulation; 589 description 590 "2048 QAM strong coding and modulation scheme."; 591 } 593 identity qam-2048 { 594 base coding-modulation; 595 description 596 "2048 QAM coding and modulation scheme."; 597 } 598 identity qam-2048-light { 599 base coding-modulation; 600 description 601 "2048 QAM light coding and modulation scheme."; 602 } 604 identity qam-4096-strong { 605 base coding-modulation; 606 description 607 "4096 QAM strong coding and modulation scheme."; 608 } 610 identity qam-4096 { 611 base coding-modulation; 612 description 613 "4096 QAM coding and modulation scheme."; 614 } 616 identity qam-4096-light { 617 base coding-modulation; 618 description 619 "4096 QAM light coding and modulation scheme."; 620 } 622 /* 623 * TDM-type identities 624 */ 626 identity tdm-type { 627 description 628 "A description of the type of TDM connection, 629 also indicating the supported capacity of the 630 connection."; 631 } 633 identity E1 { 634 base tdm-type; 635 description 636 "E1 connection, 2,048 Mbit/s."; 637 } 639 identity STM-1 { 640 base tdm-type; 641 description 642 "STM-1 connection, 155,52 Mbit/s."; 643 } 644 /* 645 * Typedefs 646 */ 648 typedef power { 649 type decimal64 { 650 fraction-digits 1; 651 } 652 description 653 "Type used for power values, selected and measured."; 654 } 656 /* 657 * Radio Link Terminal (RLT) 658 */ 660 augment "/if:interfaces/if:interface" { 661 when "if:type = 'mrl:radio-link-terminal'"; 662 description 663 "Addition of data nodes for radio link terminal to 664 the standard Interface data model, for interfaces of 665 the type 'radio-link-terminal'."; 667 leaf id { 668 type string; 669 default ""; 670 description 671 "ID of the radio link terminal. Used by far-end when 672 checking that it's connected to the correct RLT."; 673 } 675 leaf mode { 676 type identityref { 677 base rlt-mode; 678 } 679 mandatory true; 680 description 681 "A description of the mode in which the radio link 682 terminal is configured. The format is X plus Y. 683 X represent the number of bonded carrier terminations. 684 Y represent the number of protecting carrier 685 terminations."; 686 } 687 leaf-list carrier-terminations { 688 type if:interface-ref; 689 must "/if:interfaces/if:interface[if:name = current()]" 690 + "/if:type = 'mrl:carrier-termination'" { 691 description 692 "The type of interface must be 693 'carrier-termination'."; 694 } 695 min-elements 1; 696 description 697 "A list of references to carrier terminations 698 included in the radio link terminal."; 699 } 701 leaf-list rlp-groups { 702 type leafref { 703 path "/mrl:radio-link-protection-groups/" 704 + "mrl:protection-group/mrl:name"; 705 } 706 description 707 "A list of references to the carrier termination 708 groups configured for radio link protection in this 709 radio link terminal."; 710 } 712 leaf-list xpic-pairs { 713 if-feature xpic; 714 type leafref { 715 path "/mrl:xpic-pairs/mrl:xpic-pair/mrl:name"; 716 } 717 description 718 "A list of references to the XPIC pairs used in this 719 radio link terminal. One pair can be used by two 720 terminals."; 721 reference "ETSI TR 102 311"; 722 } 724 leaf-list mimo-groups { 725 if-feature mimo; 726 type leafref { 727 path "/mrl:mimo-groups/mrl:mimo-group/mrl:name"; 728 } 729 description 730 "A reference to the MIMO group used in this 731 radio link terminal. One group can be used by more 732 than one terminal."; 733 reference "ETSI TR 102 311"; 734 } 735 list tdm-connections { 736 if-feature tdm; 737 key "tdm-type"; 738 description 739 "A list stating the number of active TDM connections 740 of a specified tdm-type that is configured to be 741 supported by the RLT."; 742 leaf tdm-type { 743 type identityref { 744 base tdm-type; 745 } 746 description 747 "The type of TDM connection, which also indicates 748 the supported capacity."; 749 } 750 leaf tdm-connections { 751 type uint16; 752 mandatory true; 753 description 754 "Number of connections of the specified type."; 755 } 756 } 757 } 759 /* 760 * Carrier Termination 761 */ 763 augment "/if:interfaces/if:interface" { 764 when "if:type = 'mrl:carrier-termination'"; 765 description 766 "Addition of data nodes for carrier termination to 767 the standard Interface data model, for interfaces 768 of the type 'carrier-termination'."; 770 leaf carrier-id { 771 type string; 772 default "A"; 773 description 774 "ID of the carrier. (e.g. A, B, C or D) 775 Used in XPIC & MIMO configurations to check that 776 the carrier termination is connected to the correct 777 far-end carrier termination. Should be the same 778 carrier ID on both sides of the hop. 779 Defaulted when not MIMO or XPIC."; 780 } 781 leaf tx-enabled { 782 type boolean; 783 default "false"; 784 description 785 "Disables (false) or enables (true) the transmitter. 786 Only applicable when the interface is enabled 787 (interface:enabled = true) otherwise it's always 788 disabled."; 789 } 791 leaf tx-oper-status { 792 type enumeration { 793 enum "off" { 794 description "Transmitter is off."; 795 } 796 enum "on" { 797 description "Transmitter is on."; 798 } 799 enum "standby" { 800 description "Transmitter is in standby."; 801 } 802 } 803 config false; 804 description 805 "Shows the operative status of the transmitter."; 806 } 808 leaf tx-frequency { 809 type uint32; 810 units "kHz"; 811 mandatory true; 812 description 813 "Selected transmitter frequency."; 814 } 816 leaf rx-frequency { 817 type uint32; 818 units "kHz"; 819 description 820 "Selected receiver frequency. 821 Overrides existing value in duplex-distance. 822 Calculated from tx-frequency and duplex-distance if 823 only duplex-distance is configured. 824 Must match duplex-distance if both leaves are 825 configured in a single operation."; 826 } 827 leaf duplex-distance { 828 type uint32; 829 units "kHz"; 830 description 831 "Distance between Tx & Rx frequencies. 832 Used to calculate rx-frequency when 833 rx-frequency is not specifically configured. 834 Overrides existing value in rx-frequency. 835 Calculated from tx-frequency and rx-frequency if only 836 rx-frequency is configured. 837 Must match rx-frequency if both leaves are configured 838 in a single operation."; 839 } 841 leaf channel-separation { 842 type uint32; 843 units "kHz"; 844 mandatory true; 845 description 846 "The amount of bandwidth allocated to a carrier. The distance 847 between adjacent channels in a radio frequency channels 848 arrangement"; 849 reference "ETSI EN 302 217-1"; 850 } 852 leaf polarization { 853 type enumeration { 854 enum "horizontal" { 855 description "Horizontal polarization."; 856 } 857 enum "vertical" { 858 description "Vertical polarization."; 859 } 860 enum "not-specified" { 861 description "Polarization not specified."; 862 } 863 } 864 default "not-specified"; 865 description 866 "Polarization - A textual description for info only."; 867 } 869 leaf power-mode { 870 type enumeration { 871 enum rtpc { 872 description 873 "Remote Transmit Power Control (RTPC)."; 874 reference "ETSI EN 302 217-1"; 875 } 876 enum atpc { 877 description 878 "Automatic Transmit Power Control (ATPC)."; 879 reference "ETSI EN 302 217-1"; 880 } 881 } 882 mandatory true; 883 description 884 "A choice of Remote Transmit Power Control (RTPC) 885 or Automatic Transmit Power Control (ATPC)."; 886 } 888 leaf maximum-nominal-power { 889 type power { 890 range "-99..40"; 891 } 892 units "dBm"; 893 mandatory true; 894 description 895 "Selected output power in RTPC mode and selected 896 maximum output power in ATPC mode. Minimum ouput 897 power in ATPC mode is the same as the system 898 capability, available-min-output-power."; 899 reference "ETSI EN 302 217-1"; 900 } 902 leaf atpc-lower-threshold { 903 when "../power-mode = 'atpc'"; 904 type power { 905 range "-99..-30"; 906 } 907 units "dBm"; 908 mandatory true; 909 description 910 "The lower threshold for the input power at far-end 911 used in the ATPC mode."; 912 reference "ETSI EN 302 217-1"; 913 } 915 leaf atpc-upper-threshold { 916 when "../power-mode = 'atpc'"; 917 type power { 918 range "-99..-30"; 919 } 920 units "dBm"; 921 mandatory true; 922 description 923 "The upper threshold for the input power at far-end 924 used in the ATPC mode."; 925 reference "ETSI EN 302 217-1"; 926 } 927 leaf actual-transmitted-level { 928 type power { 929 range "-99..40"; 930 } 931 units "dBm"; 932 config false; 933 description 934 "Actual transmitted power level (0.1 dBm resolution)."; 935 reference "ETSI EN 301 129"; 936 } 938 leaf actual-received-level { 939 type power { 940 range "-99..-20"; 941 } 942 units "dBm"; 943 config false; 944 description 945 "Actual received power level (0.1 dBm resolution)."; 946 reference "ETSI EN 301 129"; 947 } 949 leaf coding-modulation-mode { 950 type enumeration { 951 enum single { 952 description "a single modulation order only."; 953 reference "ETSI EN 302 217-1"; 954 } 955 enum adaptive { 956 description "Adaptive coding/modulation."; 957 reference "ETSI EN 302 217-1"; 958 } 959 } 960 mandatory true; 961 description 962 "A selection of single or 963 adaptive coding/modulation mode."; 964 } 966 leaf selected-cm { 967 when "../coding-modulation-mode = 'single'"; 968 type identityref { 969 base coding-modulation; 970 } 971 mandatory true; 972 description 973 "Selected the single coding/modulation."; 974 } 975 leaf selected-min-acm { 976 when "../coding-modulation-mode = 'adaptive'"; 977 type identityref { 978 base coding-modulation; 979 } 980 mandatory true; 981 description 982 "Selected minimum coding/modulation. 983 Adaptive coding/modulation shall not go 984 below this value."; 985 } 987 leaf selected-max-acm { 988 when "../coding-modulation-mode = 'adaptive'"; 989 type identityref { 990 base coding-modulation; 991 } 992 mandatory true; 993 description 994 "Selected maximum coding/modulation. 995 Adaptive coding/modulation shall not go 996 above this value."; 997 } 999 leaf actual-tx-cm { 1000 type identityref { 1001 base coding-modulation; 1002 } 1003 config false; 1004 description 1005 "Actual coding/modulation in transmitting direction."; 1006 } 1008 leaf actual-snir { 1009 type decimal64 { 1010 fraction-digits 1; 1011 range "0..99"; 1012 } 1013 units "dB"; 1014 config false; 1015 description 1016 "Actual signal to noise plus interference ratio. 1017 (0.1 dB resolution)."; 1018 } 1020 leaf actual-xpi { 1021 if-feature xpic; 1022 type decimal64 { 1023 fraction-digits 1; 1024 range "0..99"; 1025 } 1026 units "dB"; 1027 config false; 1028 description 1029 "The actual carrier to cross-polar interference. 1030 Only valid if XPIC is enabled. (0.1 dB resolution)."; 1031 reference "ETSI TR 102 311"; 1032 } 1034 container ct-performance-thresholds { 1035 description 1036 "Specification of thresholds for when alarms should 1037 be sent and cleared for various performance counters."; 1039 leaf received-level-alarm-threshold { 1040 type power { 1041 range "-99..-30"; 1042 } 1043 units "dBm"; 1044 default "-99"; 1045 description 1046 "An alarm is sent when the received power level is 1047 below the specified threshold."; 1048 reference "ETSI EN 301 129"; 1049 } 1051 leaf transmitted-level-alarm-threshold { 1052 type power { 1053 range "-99..40"; 1054 } 1055 units "dBm"; 1056 default "-99"; 1057 description 1058 "An alarm is sent when the transmitted power level 1059 is below the specified threshold."; 1060 reference "ETSI EN 301 129"; 1061 } 1063 leaf ber-alarm-threshold { 1064 type enumeration { 1065 enum "10e-9" { 1066 description "Threshold at 10e-9."; 1067 } 1068 enum "10e-8" { 1069 description "Threshold at 10e-8."; 1070 } 1071 enum "10e-7" { 1072 description "Threshold at 10e-7."; 1073 } 1074 enum "10e-6" { 1075 description "Threshold at 10e-6."; 1076 } 1077 enum "10e-5" { 1078 description "Threshold at 10e-5."; 1079 } 1080 enum "10e-4" { 1081 description "Threshold at 10e-4."; 1082 } 1083 enum "10e-3" { 1084 description "Threshold at 10e-3."; 1085 } 1086 enum "10e-2" { 1087 description "Threshold at 10e-2."; 1088 } 1089 enum "10e-1" { 1090 description "Threshold at 10e-1."; 1091 } 1092 } 1093 default "10e-6"; 1094 description 1095 "Specification of at which BER an alarm should 1096 be raised."; 1097 reference "ETSI EN 302 217-1"; 1098 } 1099 } 1101 leaf if-loop { 1102 type enumeration { 1103 enum disabled { 1104 description "Disables the IF Loop."; 1105 } 1106 enum client { 1107 description 1108 "Loops the signal back to the client side."; 1109 } 1110 enum radio { 1111 description 1112 "Loops the signal back to the radio side."; 1113 } 1114 } 1115 default "disabled"; 1116 description 1117 "Enable (client/radio) or disable (disabled) 1118 the IF loop, which loops the signal back to 1119 the client side or the radio side."; 1120 } 1122 leaf rf-loop { 1123 type enumeration { 1124 enum disabled { 1125 description "Disables the RF Loop."; 1126 } 1127 enum client { 1128 description 1129 "Loops the signal back to the client side."; 1130 } 1131 enum radio { 1132 description 1133 "Loops the signal back to the radio side."; 1134 } 1135 } 1136 default "disabled"; 1137 description 1138 "Enable (client/radio) or disable (disabled) 1139 the RF loop, which loops the signal back to 1140 the client side or the radio side."; 1141 } 1143 container capabilities { 1144 config false; 1145 description 1146 "Capabilities of the the installed equipment and 1147 some selected configurations."; 1149 leaf min-tx-frequency { 1150 type uint32; 1151 units "kHz"; 1152 description 1153 "Minimum Tx frequency possible to use."; 1154 } 1156 leaf max-tx-frequency { 1157 type uint32; 1158 units "kHz"; 1159 description 1160 "Maximum Tx frequency possible to use."; 1161 } 1163 leaf min-rx-frequency { 1164 type uint32; 1165 units "kHz"; 1166 description 1167 "Minimum Rx frequency possible to use."; 1168 } 1170 leaf max-rx-frequency { 1171 type uint32; 1172 units "kHz"; 1173 description 1174 "Maximum Tx frequency possible to use."; 1175 } 1176 leaf minimum-power { 1177 type power; 1178 units "dBm"; 1179 description 1180 "The minimum output power supported."; 1181 reference "ETSI EN 302 217-1"; 1182 } 1184 leaf maximum-available-power { 1185 type power; 1186 units "dBm"; 1187 description 1188 "The maximum output power supported."; 1189 reference "ETSI EN 302 217-1"; 1190 } 1192 leaf available-min-acm { 1193 type identityref { 1194 base coding-modulation; 1195 } 1196 description 1197 "Minimum coding-modulation possible to use."; 1198 } 1200 leaf available-max-acm { 1201 type identityref { 1202 base coding-modulation; 1203 } 1204 description 1205 "Maximum coding-modulation possible to use."; 1206 } 1207 } 1209 container error-performance-statistics { 1210 config false; 1211 description 1212 "ITU-T G.826 error performance statistics relevant for 1213 a microwave/millimeter wave carrier."; 1215 leaf bbe { 1216 type yang:counter32; 1217 units "number of block errors"; 1218 description 1219 "Number of Background Block Errors (BBE) during the 1220 interval. A BBE is an errored block not occurring as 1221 part of an SES."; 1222 reference "ITU-T G.826"; 1223 } 1224 leaf es { 1225 type yang:counter32; 1226 units "seconds"; 1227 description 1228 "Number of Errored Seconds (ES) since last reset. 1229 An ES is a one-second period with one or more errored 1230 blocks or at least one defect."; 1231 reference "ITU-T G.826"; 1232 } 1234 leaf ses { 1235 type yang:counter32; 1236 units "seconds"; 1237 description 1238 "Number of Severely Errored Seconds (SES) during the 1239 interval. SES is a one-second period which contains 1240 equal or more than 30% errored blocks or at least 1241 one defect. SES is a subset of ES."; 1242 reference "ITU-T G.826"; 1243 } 1245 leaf uas { 1246 type yang:counter32; 1247 units "seconds"; 1248 description 1249 "Number of Unavailable Seconds (UAS), that is, the 1250 total time that the node has been unavailable during 1251 a fixed measurement interval."; 1252 reference "ITU-T G.826"; 1253 } 1254 } 1256 container radio-performance-statistics { 1257 config false; 1258 description 1259 "ETSI EN 301 129 radio physical interface statistics relevant 1260 for a carrier termination."; 1262 leaf min-rltm { 1263 type power { 1264 range "-99..-20"; 1265 } 1266 units "dBm"; 1267 description 1268 "Minimum received power level since last reset."; 1269 reference "ETSI EN 301 129"; 1270 } 1271 leaf max-rltm { 1272 type power { 1273 range "-99..-20"; 1274 } 1275 units "dBm"; 1276 description 1277 "Maximum received power level since last reset."; 1278 reference "ETSI EN 301 129"; 1279 } 1281 leaf min-tltm { 1282 type power { 1283 range "-99..40"; 1284 } 1285 units "dBm"; 1286 description 1287 "Minimum transmitted power level since last reset."; 1288 reference "ETSI EN 301 129"; 1289 } 1291 leaf max-tltm { 1292 type power { 1293 range "-99..40"; 1294 } 1295 units "dBm"; 1296 description 1297 "Maximum transmitted power level since last reset."; 1298 reference "ETSI EN 301 129"; 1299 } 1300 } 1301 } 1303 /* 1304 * Radio Link Protection Groups 1305 */ 1307 container radio-link-protection-groups { 1308 description 1309 "Configuration of radio link protected groups (1+1) of 1310 carrier terminations in a radio link. More than one 1311 protected group per radio-link-terminal is allowed."; 1313 uses ifprot:protection-groups { 1315 refine protection-group/protection-members { 1316 must "/if:interfaces/if:interface[if:name = current()]" 1317 + "/if:type = 'mrl:carrier-termination'" { 1318 description 1319 "The type of a protection member must be 1320 'carrier-termination'."; 1321 } 1322 } 1323 refine protection-group/working-entity { 1324 must "/if:interfaces/if:interface[if:name = current()]" 1325 + "/if:type = 'mrl:carrier-termination'" { 1326 description 1327 "The type of a working-entity must be 1328 'carrier-termination'."; 1329 } 1330 } 1331 } 1332 } 1334 /* 1335 * XPIC & MIMO groups - Configuration data nodes 1336 */ 1338 container xpic-pairs { 1339 if-feature xpic; 1340 description 1341 "Configuration of carrier termination pairs 1342 for operation in XPIC mode."; 1343 reference "ETSI TR 102 311"; 1345 list xpic-pair { 1346 key "name"; 1347 description 1348 "List of carrier termination pairs in XPIC mode."; 1350 leaf name { 1351 type string; 1352 description 1353 "Name used for identification of the XPIC pair."; 1354 } 1356 leaf enabled { 1357 type boolean; 1358 default "false"; 1359 description 1360 "Enable(true)/disable(false) XPIC"; 1361 } 1363 leaf-list xpic-members { 1364 type if:interface-ref; 1365 must "/if:interfaces/if:interface[if:name = current()]" 1366 + "/if:type = 'mrl:carrier-termination'" { 1367 description 1368 "The type of a xpic-member must be 1369 'carrier-termination'."; 1370 } 1371 min-elements 2; 1372 max-elements 2; 1373 description 1374 "Association to XPIC pairs used in the radio link 1375 terminal."; 1376 } 1377 } 1378 } 1380 container mimo-groups { 1381 if-feature mimo; 1382 description 1383 "Configuration of carrier terminations 1384 for operation in MIMO mode."; 1385 reference "ETSI TR 102 311"; 1387 list mimo-group { 1388 key "name"; 1389 description 1390 "List of carrier terminations in MIMO mode."; 1392 leaf name { 1393 type string; 1394 description 1395 "Name used for identification of the MIMO group."; 1396 } 1398 leaf enabled { 1399 type boolean; 1400 default "false"; 1401 description 1402 "Enable(true)/disable(false) MIMO"; 1403 } 1405 leaf-list mimo-members { 1406 type if:interface-ref; 1407 must "/if:interfaces/if:interface[if:name = current()]" 1408 + "/if:type = 'mrl:carrier-termination'" { 1409 description 1410 "The type of a mimo-member must be 1411 'carrier-termination'."; 1412 } 1413 min-elements 2; 1414 description 1415 "Association to a MIMO group if used in the radio 1416 link terminal."; 1417 } 1418 } 1419 } 1420 } 1422 1424 5. Interface Protection YANG Module 1426 The data nodes for management of the interface protection 1427 functionality is broken out from the Microwave Radio Link Module 1428 into a separate and generic YANG data module in order to make it 1429 available also for other interface types. 1431 file "ietf-interface-protection.yang" 1433 module ietf-interface-protection { 1434 yang-version 1.1; 1435 namespace "urn:ietf:params:xml:ns:yang:ietf-interface-protection"; 1436 prefix ifprot; 1438 import ietf-interfaces { 1439 prefix if; 1440 } 1442 organization 1443 "Internet Engineering Task Force (IETF) CCAMP WG"; 1444 contact 1445 "WG List: 1447 ID-draft authors: 1448 Jonas Ahlberg (jonas.ahlberg@ericsson.com); 1449 Min Ye (amy.yemin@huawei.com); 1450 Xi Li (Xi.Li@neclab.eu); 1451 Koji Kawada (k-kawada@ah.jp.nec.com) 1452 Carlos J. Bernardos (cjbc@it.uc3m.es) 1453 Daniela Spreafico (daniela.spreafico@nokia.com) 1454 Marko Vaupotic (Marko.Vaupotic@aviatnet.com)"; 1456 description 1457 "This is a module for the entities in 1458 a generic interface protection mechanism."; 1460 revision 2017-10-19 { 1461 description 1462 "Draft revision."; 1463 reference ""; 1464 } 1466 /* 1467 * Protection architecture type identities 1468 */ 1470 identity protection-architecture-type { 1471 description 1472 "protection architecture type"; 1473 reference "ITU-T Rec. G.808.1"; 1474 } 1475 identity one-plus-one-type { 1476 base protection-architecture-type; 1477 description 1478 "1+1, One interface protects 1479 another one interface."; 1480 reference "ITU-T Rec. G.808.1"; 1481 } 1483 identity one-to-n-type { 1484 base protection-architecture-type; 1485 description 1486 "1:N, One interface protects 1487 n other interfaces."; 1488 reference "ITU-T Rec. G.808.1"; 1489 } 1491 /* 1492 * Protection states identities 1493 */ 1495 identity protection-states { 1496 description 1497 "Identities describing the status of the protection, 1498 in a group of interfaces configured in 1499 a protection mode."; 1500 } 1502 identity unprotected { 1503 base protection-states; 1504 description "Not protected"; 1505 } 1507 identity protected { 1508 base protection-states; 1509 description "Protected"; 1510 } 1512 identity unable-to-protect { 1513 base protection-states; 1514 description "Unable to protect"; 1515 } 1517 /* 1518 * protection-external-commands identities 1519 */ 1521 identity protection-external-commands{ 1522 description 1523 "Protection external commands for trouble shooting 1524 purpose."; 1525 reference "ITU-T Rec. G.808.1"; 1526 } 1527 identity manual-switch-working{ 1528 base protection-external-commands; 1529 description 1530 "A switch action initiated by an operator command. 1531 It switches normal traffic signal to the working 1532 transport entity."; 1533 reference "ITU-T Rec. G.808.1"; 1534 } 1536 identity manual-switch-protection{ 1537 base protection-external-commands; 1538 description 1539 "A switch action initiated by an operator command. 1540 It switches normal traffic signal to the protection 1541 transport entity."; 1542 reference "ITU-T Rec. G.808.1"; 1543 } 1545 identity forced-switch{ 1546 base protection-external-commands; 1547 description 1548 "A switch action initiated by an operator command. 1549 It switches normal traffic signal to the protection 1550 transport entity and forces it to remain on that 1551 entity even when criteria for switching back to 1552 the orignal entity are fulfilled."; 1553 reference "ITU-T Rec. G.808.1"; 1554 } 1556 identity lockout-of-protection{ 1557 base protection-external-commands; 1558 description 1559 "A switch action temporarily disables access to the 1560 protection transport entity for all signals."; 1561 reference "ITU-T Rec. G.808.1"; 1562 } 1564 identity freeze{ 1565 base protection-external-commands; 1566 description 1567 "A switch action temporarily prevents any switch action 1568 to be taken and, as such, freezes the current state. 1569 Until the freeze is cleared, additional near-end external 1570 commands are rejected and fault condition changes and 1571 received APS messages are ignored.."; 1572 reference "ITU-T Rec. G.808.1"; 1573 } 1574 identity exercise{ 1575 base protection-external-commands; 1576 description 1577 "A switch action to test if the APS communication is 1578 operating correctly. It is lower priority than any 'real' 1579 switch request.."; 1580 reference "ITU-T Rec. G.808.1"; 1581 } 1583 identity clear{ 1584 base protection-external-commands; 1585 description 1586 "A action clears all switch commands."; 1587 reference "ITU-T Rec. G.808.1"; 1588 } 1590 /* 1591 * Protection Groups 1592 */ 1594 grouping protection-groups { 1595 description 1596 "Configuration of protected groups (1+1) of interfaces 1597 providing protection for each other. More than one protected 1598 group per higher-layer-interface is allowed."; 1600 list protection-group { 1601 key "name"; 1602 description 1603 "List of protected groups of interfaces 1604 in a higher-layer-interface."; 1606 leaf name { 1607 type string; 1608 description 1609 "Name used for identification of the protection group"; 1610 } 1612 leaf protection-architecture-type { 1613 type identityref{ 1614 base protection-architecture-type; 1615 } 1616 default "one-plus-one-type"; 1617 description 1618 "The type of protection architecture used, e.g. one 1619 interface protecting one or several other interfaces."; 1620 reference "ITU-T Rec. G.808.1"; 1621 } 1622 leaf-list protection-members { 1623 type if:interface-ref; 1624 min-elements 2; 1625 description 1626 "Association to a group of interfaces configured for 1627 protection and used by a higher-layer-interface."; 1628 } 1630 leaf protection-operation-type { 1631 type enumeration { 1632 enum "non-revertive" { 1633 description 1634 "In non revertive operation, the traffic does not 1635 return to the working interface if the switch requests 1636 are terminated."; 1637 reference "ITU-T Rec. G.808.1"; 1638 } 1639 enum "revertive" { 1640 description 1641 "In revertive operation, the traffic always 1642 returns to (or remains on) the working interface 1643 if the switch requests are terminated."; 1644 reference "ITU-T Rec. G.808.1"; 1645 } 1646 } 1647 default "non-revertive"; 1648 description 1649 "The type of protection operation, i.e. revertive 1650 or non-revertive operation."; 1651 } 1653 leaf-list working-entity { 1654 when "../protection-operation-type = 'revertive'"; 1655 type if:interface-ref; 1656 min-elements 1; 1657 description 1658 "The interfaces over which the traffic normally should 1659 be transported over when there is no need to use the 1660 protecting interface."; 1661 } 1663 leaf revertive-wait-to-restore { 1664 when "../protection-operation-type = 'revertive'"; 1665 type uint16; 1666 units "seconds"; 1667 default "0"; 1668 description 1669 "The time to wait before switching back to the working 1670 interface if protection-operation-type is revertive."; 1671 reference "ITU-T Rec. G.808.1"; 1672 } 1673 leaf hold-off-timer { 1674 type uint16; 1675 units "milliseconds"; 1676 default "0"; 1677 description 1678 "Time interval after the detection of a fault and its 1679 confirmation as a condition requiring the protection 1680 switching procedure."; 1681 reference "ITU-T Rec. G.808.1"; 1682 } 1684 leaf protection-status { 1685 type identityref { 1686 base protection-states; 1687 } 1688 description 1689 "Status of the protection, in a group of interfaces 1690 configured in a protection mode."; 1691 reference "ITU-T Rec. G.808.1"; 1692 } 1694 action protection-external-commands { 1695 input { 1696 leaf protection-external-command { 1697 type identityref { 1698 base protection-external-commands; 1699 } 1700 description 1701 "Execution of protection external commands for 1702 trouble shooting purpose."; 1703 } 1704 } 1705 } 1706 } 1707 } 1708 } 1710 1712 6. Security Considerations 1714 The YANG module defined in this memo is designed to be accessed via 1715 the NETCONF protocol [RFC6241]. The lowest NETCONF layer is the 1716 secure transport layer and the mandatory-to-implement secure 1717 transport is SSH [RFC6242]. The NETCONF access control model 1718 [RFC6536] provides the means to restrict access for particular 1719 NETCONF users to a pre-configured subset of all available NETCONF 1720 protocol operations and content. 1722 There are a number of data nodes defined in the YANG module which are 1723 writable/creatable/deletable (i.e., config true, which is the 1724 default). These data nodes may be considered sensitive or vulnerable 1725 in some network environments. Write operations (e.g., ) 1726 to these data nodes without proper protection can have a negative 1727 effect on network operations. 1729 The security considerations of [RFC7223bis] also apply to this 1730 document. 1732 7. IANA Considerations 1734 TBD. 1736 8. References 1738 8.1. Normative References 1740 [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate 1741 Requirement Levels", BCP 14, RFC 2119, 1742 DOI 10.17487/RFC2119, March 1997, 1743 . 1745 [RFC7223bis] 1746 Bjorklund, M., "A YANG Data Model for Interface 1747 Management", draft-bjorklund-netmod-rfc7223bis-00 1748 (work in progress), September 2017. 1750 [EN 302 217-2] 1751 ETSI, "Fixed Radio Systems; Characteristics and 1752 requirements for point to-point equipment and antennas; 1753 Part 2: Digital systems operating in frequency bands from 1754 1 GHz to 86 GHz; Harmonised Standard covering the 1755 essential requirements of article 3.2 of Directive 1756 2014/53/EU", EN 302 217-2 V3.1.1, May 2017. 1758 8.2. Informative References 1760 [NMDA] Bjorklund, M., Schoenwaelder, J., Shafer, P., Watsen, K., 1761 Wilton, R. "Network Management Datastore Architecture", 1762 draft-ietf-netmod-revised-datastores-05 (work in 1763 progress), October 2017. 1765 [I-D.ahlberg-ccamp-microwave-radio-link] 1766 Ahlberg, J., Carlson, J., Lund, H., Olausson, T., Ye, M., 1767 and M. Vaupotic, "Microwave Radio Link YANG Data Models", 1768 draft-ahlberg-ccamp-microwave-radio-link-01 (work in 1769 progress), May 2016. 1771 [I-D.ietf-ccamp-microwave-framework] 1772 Ahlberg, J., Contreras, L., Ye, M., Vaupotic, M., 1773 Tantsura, J., Kawada, K., Li, X., Akiyoshi, I., C. 1774 Bernardos, and D. Spreafico, "A framework for Management 1775 and Control of microwave and millimeter wave interface 1776 parameters", draft-ietf-ccamp-microwave-framework-02 1777 (work in progress), October 2017. 1779 [ONF-model] "Microwave Modeling - ONF Wireless Transport Group", 1780 May 2016. 1782 [RFC6241] Enns, R., Ed., Bjorklund, M., Ed., Schoenwaelder, J., Ed., 1783 and A. Bierman, Ed., "Network Configuration Protocol 1784 (NETCONF)", RFC 6241, DOI 10.17487/RFC6241, June 2011, 1785 . 1787 [RFC6242] Wasserman, M., "Using the NETCONF Protocol over Secure 1788 Shell (SSH)", RFC 6242, DOI 10.17487/RFC6242, June 2011, 1789 . 1791 [RFC6536] Bierman, A. and M. Bjorklund, "Network Configuration 1792 Protocol (NETCONF) Access Control Model", RFC 6536, 1793 DOI 10.17487/RFC6536, March 2012, 1794 . 1796 Authors' Addresses 1798 Jonas Ahlberg 1799 Ericsson AB 1800 Lindholmspiren 11 1801 Goeteborg 417 56 1802 Sweden 1804 Email: jonas.ahlberg@ericsson.com 1806 Ye Min 1807 Huawei Technologies 1808 No.1899, Xiyuan Avenue 1809 Chengdu 611731 1810 P.R.China 1812 Email: amy.yemin@huawei.com 1814 Xi Li 1815 NEC Laboratories Europe 1816 Kurfursten-Anlage 36 1817 Heidelberg 69115 1818 Germany 1820 Email: Xi.Li@neclab.eu 1822 Koji Kawada 1823 NEC Corporation 1824 1753, Shimonumabe Nakahara-ku 1825 Kawasaki, Kanagawa 211-8666 1826 Japan 1828 Email: k-kawada@ah.jp.nec.com 1829 Carlos J. Bernardos 1830 Universidad Carlos III de Madrid 1831 Av. Universidad, 30 1832 Leganes, Madrid 28911 1833 Spain 1835 Email: cjbc@it.uc3m.es 1837 Daniela Spreafico 1838 Nokia - IT 1839 Via Energy Park, 14 1840 Vimercate (MI) 20871 1841 Italy 1843 Email: daniela.spreafico@nokia.com 1845 Marko Vaupotic 1846 Aviat Networks 1847 Motnica 9 1848 Trzin-Ljubljana 1236 1849 Slovenia 1851 Email: Marko.Vaupotic@Aviatnet.com