idnits 2.17.00 (12 Aug 2021) /tmp/idnits50817/draft-ietf-ccamp-microwave-framework-07.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 date (June 5, 2018) is 1439 days in the past. Is this intentional? Checking references for intended status: Informational ---------------------------------------------------------------------------- == Outdated reference: draft-ietf-ccamp-alarm-module has been published as RFC 8632 == Outdated reference: draft-ietf-ccamp-mw-yang has been published as RFC 8561 Summary: 0 errors (**), 0 flaws (~~), 3 warnings (==), 1 comment (--). Run idnits with the --verbose option for more detailed information about the items above. -------------------------------------------------------------------------------- 2 CCAMP Working Group J. Ahlberg, Ed. 3 Internet-Draft Ericsson AB 4 Intended status: Informational M. Ye, Ed. 5 Expires: December 7, 2018 Huawei Technologies 6 X. Li 7 NEC Laboratories Europe 8 LM. Contreras 9 Telefonica I+D 10 CJ. Bernardos 11 Universidad Carlos III de Madrid 12 June 5, 2018 14 A framework for Management and Control of microwave and millimeter wave 15 interface parameters 16 draft-ietf-ccamp-microwave-framework-07 18 Abstract 20 The unification of control and management of microwave radio link 21 interfaces is a precondition for seamless multilayer networking and 22 automated network provisioning and operation. 24 This document describes the required characteristics and use cases 25 for control and management of radio link interface parameters using a 26 YANG Data Model. 28 The purpose is to create a framework for identification of the 29 necessary information elements and definition of a YANG Data Model 30 for control and management of the radio link interfaces in a 31 microwave node. Some parts of the resulting model may be generic 32 which could also be used by other technologies, e.g., Ethernet 33 technology. 35 Status of This Memo 37 This Internet-Draft is submitted in full conformance with the 38 provisions of BCP 78 and BCP 79. 40 Internet-Drafts are working documents of the Internet Engineering 41 Task Force (IETF). Note that other groups may also distribute 42 working documents as Internet-Drafts. The list of current Internet- 43 Drafts is at https://datatracker.ietf.org/drafts/current/. 45 Internet-Drafts are draft documents valid for a maximum of six months 46 and may be updated, replaced, or obsoleted by other documents at any 47 time. It is inappropriate to use Internet-Drafts as reference 48 material or to cite them other than as "work in progress." 49 This Internet-Draft will expire on December 7, 2018. 51 Copyright Notice 53 Copyright (c) 2018 IETF Trust and the persons identified as the 54 document authors. All rights reserved. 56 This document is subject to BCP 78 and the IETF Trust's Legal 57 Provisions Relating to IETF Documents 58 (https://trustee.ietf.org/license-info) in effect on the date of 59 publication of this document. Please review these documents 60 carefully, as they describe your rights and restrictions with respect 61 to this document. Code Components extracted from this document must 62 include Simplified BSD License text as described in Section 4.e of 63 the Trust Legal Provisions and are provided without warranty as 64 described in the Simplified BSD License. 66 Table of Contents 68 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 3 69 1.1. Conventions used in this document . . . . . . . . . . . . 5 70 2. Terminology and Definitions . . . . . . . . . . . . . . . . . 5 71 3. Approaches to manage and control radio link interfaces . . . 6 72 3.1. Network Management Solutions . . . . . . . . . . . . . . 7 73 3.2. Software Defined Networking . . . . . . . . . . . . . . . 7 74 4. Use Cases . . . . . . . . . . . . . . . . . . . . . . . . . . 8 75 4.1. Configuration Management . . . . . . . . . . . . . . . . 8 76 4.2. Inventory . . . . . . . . . . . . . . . . . . . . . . . . 9 77 4.3. Status and statistics . . . . . . . . . . . . . . . . . . 10 78 4.4. Performance management . . . . . . . . . . . . . . . . . 10 79 4.5. Fault Management . . . . . . . . . . . . . . . . . . . . 10 80 4.6. Troubleshooting and Root Cause Analysis . . . . . . . . . 11 81 5. Requirements . . . . . . . . . . . . . . . . . . . . . . . . 11 82 6. Gap Analysis on Models . . . . . . . . . . . . . . . . . . . 12 83 6.1. Microwave Radio Link Functionality . . . . . . . . . . . 12 84 6.2. Generic Functionality . . . . . . . . . . . . . . . . . . 13 85 6.3. Summary . . . . . . . . . . . . . . . . . . . . . . . . . 15 86 7. Security Considerations . . . . . . . . . . . . . . . . . . . 15 87 8. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 16 88 9. References . . . . . . . . . . . . . . . . . . . . . . . . . 16 89 9.1. Normative References . . . . . . . . . . . . . . . . . . 16 90 9.2. Informative References . . . . . . . . . . . . . . . . . 16 91 Appendix A. Contributors . . . . . . . . . . . . . . . . . . . . 18 92 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 19 94 1. Introduction 96 Microwave radio is a technology that uses high frequency radio waves 97 to provide high speed wireless connections that can send and receive 98 voice, video, and data information. It is a general term used for 99 systems covering a very large range of traffic capacities, channel 100 separations, modulation formats and applications over a wide range of 101 frequency bands from 1.4 GHz up to and above 100 GHz. 103 The main application for microwave is backhaul for mobile broadband. 104 Those networks will continue to be modernized using a combination of 105 microwave and fiber technologies. The choice of technology is a 106 question about fiber presence and cost of ownership, not about 107 capacity limitations in microwave. 109 Microwave is already today able to fully support the capacity needs 110 of a backhaul in a radio access network and will evolve to support 111 multiple gigabits in traditional frequency bands and beyond 10 112 gigabits in higher frequency bands with more bandwidth. L2 Ethernet 113 features are normally an integrated part of microwave nodes and more 114 advanced L2 and L3 features will over time be introduced to support 115 the evolution of the transport services to be provided by a backhaul/ 116 transport network. Note that the wireless access technologies such 117 as 3/4/5G and Wi-Fi are not within the scope of this microwave model 118 work. 120 Open and standardized interfaces are a pre-requisite for efficient 121 management of equipment from multiple vendors, integrated in a single 122 system/controller. This framework addresses management and control 123 of the radio link interface(s) and the relationship to other 124 interfaces, typically to Ethernet interfaces, in a microwave node. A 125 radio link provides the transport over the air, using one or several 126 carriers in aggregated or protected configurations. Managing and 127 controlling a transport service over a microwave node involves both 128 radio link and packet transport functionality. 130 Already today there are numerous IETF data models, RFCs and drafts, 131 with technology specific extensions that cover a large part of the L2 132 and L3 domains. Examples are IP Management [RFC8344], Routing 133 Management [RFC8349] and Provider Bridge [PB-YANG]. They are based 134 on the IETF YANG model for Interface Management [RFC8343], which is 135 an evolution of the SNMP IF-MIB [RFC2863]. 137 Since microwave nodes will contain more and more L2 and L3(packet) 138 functionality which is expected to be managed using those models, 139 there are advantages if radio link interfaces can be modeled and 140 managed using the same structure and the same approach, specifically 141 for use cases in which a microwave node is managed as one common 142 entity including both the radio link and the L2 and L3 functionality, 143 e.g. at basic configuration of node and connections, centralized 144 trouble shooting, upgrade and maintenance. All interfaces in a node, 145 irrespective of technology, would then be accessed from the same core 146 model, i.e. [RFC8343], and could be extended with technology specific 147 parameters in models augmenting that core model. The relationship/ 148 connectivity between interfaces could be given by the physical 149 equipment configuration, e.g. the slot in which the Radio Link 150 Terminal (modem) is plugged in could be associated with a specific 151 Ethernet port due to the wiring in the backplane of the system, or it 152 could be flexible and therefore configured via a management system or 153 controller. 155 +------------------------------------------------------------------+ 156 | Interface [RFC8343] | 157 | +---------------+ | 158 | | Ethernet Port | | 159 | +---------------+ | 160 | \ | 161 | +---------------------+ | 162 | | Radio Link Terminal | | 163 | +---------------------+ | 164 | / \ | 165 | +---------------------+ +---------------------+ | 166 | | Carrier Termination | | Carrier Termination | | 167 | +---------------------+ +---------------------+ | 168 +------------------------------------------------------------------+ 170 Figure 1: Relationship between interfaces in a node 172 There will always be certain implementations that differ among 173 products and it is therefore practically impossible to achieve 174 industry consensus on every design detail. It is therefore important 175 to focus on the parameters that are required to support the use cases 176 applicable for centralized, unified, multi-vendor management and to 177 allow other parameters to be optional or to be covered by extensions 178 to the standardized model. Furthermore, a standard that allows for a 179 certain degree of freedom encourages innovation and competition which 180 is something that benefits the entire industry. It is therefore 181 important that a radio link management model covers all relevant 182 functions but also leaves room for product/feature-specific 183 extensions. 185 For microwave radio link functionality work has been initiated (ONF: 186 Microwave Modeling [ONF-model], IETF: Radio Link Model 187 [I-D.ietf-ccamp-mw-yang]). The purpose of this effort is to reach 188 consensus within the industry around one common approach, with 189 respect to the use cases and requirements to be supported, the type 190 and structure of the model and the resulting attributes to be 191 included. This document describes the use cases and requirements 192 agreed to be covered, the expected characteristics of the model and 193 at the end includes an analysis of how the models in the two on-going 194 initiatives fulfill these expectations and a recommendation on what 195 can be reused and what gaps need to be filled by a new and evolved 196 radio link model. 198 1.1. Conventions used in this document 200 The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", 201 "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this 202 document are to be interpreted as described in [RFC2119] [RFC8174] 203 when, and only when, they appear in all capitals, as shown here. 205 2. Terminology and Definitions 207 Microwave radio is a term commonly used for technologies that operate 208 in both microwave and millimeter wave lengths and in frequency bands 209 from 1.4 GHz up to and beyond 100 GHz. In traditional bands it 210 typically supports capacities of 1-3 Gbps and in 70/80 GHz band up to 211 10 Gbps. Using multi-carrier systems operating in frequency bands 212 with wider channels, the technology will be capable of providing 213 capacities of up to 100 Gbps. 215 The microwave radio technology is widely used for point-to-point 216 telecommunications because of its small wavelength that allows 217 conveniently-sized antennas to direct them in narrow beams, and the 218 comparatively higher frequencies that allow broad bandwidth and high 219 data transmission rates. It is used for a broad range of fixed and 220 mobile services including high-speed, point-to-point wireless local 221 area networks (WLANs) and broadband access. 223 ETSI EN 302 217 series defines the characteristics and requirements 224 of microwave equipment and antennas. Especially ETSI EN 302 217-2 225 [EN302217-2] specifies the essential parameters for the systems 226 operating from 1.4GHz to 86GHz. 228 Carrier Termination and Radio Link Terminal are two concepts defined 229 to support modeling of microwave radio link features and parameters 230 in a structured and yet simple manner. 232 Carrier Termination is an interface for the capacity provided over 233 the air by a single carrier. It is typically defined by its 234 transmitting and receiving frequencies. 236 Radio Link Terminal is an interface providing Ethernet capacity and/ 237 or Time Division Multiplexing (TDM) capacity to the associated 238 Ethernet and/or TDM interfaces in a node and used for setting up a 239 transport service over a microwave radio link. 241 Figure 2 provides a graphical representation of Carrier Termination 242 and Radio Link Terminal concepts. 244 /--------- Radio Link ---------\ 245 Near End Far End 247 +---------------+ +---------------+ 248 | Radio Link | | Radio Link | 249 | Terminal | | Terminal | 250 | | | | 251 | (Protected or Bonded) | 252 | | | | 253 | +-----------+ | | +-----------+ | 254 | | | | Carrier A | | | | 255 | | Carrier | |<--------->| | Carrier | | 256 | |Termination| | | |Termination| | 257 ETH----| | | | | | | |----ETH 258 | +-----------+ | | +-----------+ | 259 TDM----| | | |----TDM 260 | +-----------+ | | +-----------+ | 261 | | | | Carrier B | | | | 262 | | Carrier | |<--------->| | Carrier | | 263 | |Termination| | | |Termination| | 264 | | | | | | | | 265 | +-----------+ | | +-----------+ | 266 | | | | 267 +---------------+ +---------------+ 269 \--- Microwave Node ---/ \--- Microwave Node ---/ 271 Figure 2: Radio Link Terminal and Carrier Termination 273 Software Defined Networking (SDN) is an architecture that decouples 274 the network control and forwarding functions enabling the network 275 control to become directly programmable and the underlying 276 infrastructure to be abstracted for applications and network 277 services. SDN can be used for automation of traditional network 278 management functionality using an SDN approach of standardized 279 programmable interfaces for control and management [RFC7426]. 281 3. Approaches to manage and control radio link interfaces 283 This framework addresses the definition of an open and standardized 284 interface for the radio link functionality in a microwave node. The 285 application of such an interface used for management and control of 286 nodes and networks typically vary from one operator to another, in 287 terms of the systems used and how they interact. Possible approaches 288 include via the use of a network management system (NMS), via 289 software defined networking (SDN) and via some combination of NMS and 290 SDN. As there are still many networks where the NMS is implemented 291 as one component/interface and the SDN controller is scoped to 292 control plane functionality as a separate component/interface, this 293 document does not preclude either model. The aim of this document is 294 to provide a framework for development of a common YANG Data Model 295 for both management and control of microwave interfaces. 297 3.1. Network Management Solutions 299 The classic network management solutions, with vendor specific domain 300 management combined with cross domain functionality for service 301 management and analytics, still dominate the market. These solutions 302 are expected to evolve and benefit from an increased focus on 303 standardization by simplifying multi-vendor management and remove the 304 need for vendor/domain specific management. 306 3.2. Software Defined Networking 308 One of the main drivers for applying SDN from an operator perspective 309 is simplification and automation of network provisioning as well as 310 end to end network service management. The vision is to have a 311 global view of the network conditions spanning across different 312 vendors' equipment and multiple technologies. 314 If nodes from different vendors are be managed by the same SDN 315 controller via a node management interface (north bound interface, 316 NBI), without the extra effort of introducing intermediate systems, 317 all nodes must align their node management interfaces. Hence, an 318 open and standardized node management interface is required in a 319 multi-vendor environment. Such a standardized interface enables a 320 unified management and configuration of nodes from different vendors 321 by a common set of applications. 323 On top of SDN applications to configure, manage and control the nodes 324 and their associated transport interfaces including the L2 Ethernet 325 and L3 IP interfaces as well as the radio interfaces, there are also 326 a large variety of other more advanced SDN applications that can be 327 utilized and/or developed. 329 A potentially flexible approach for the operators is to use SDN in a 330 logical control way to manage the radio links by selecting a 331 predefined operation mode. The operation mode is a set of logical 332 metrics or parameters describing a complete radio link configuration, 333 such as capacity, availability, priority and power consumption. 335 An example of an operation mode table is shown in Figure 3. Based on 336 its operation policy (e.g., power consumption or traffic priority), 337 the SDN controller selects one operation mode and translates that 338 into the required configuration of the individual parameters for the 339 radio link terminals and the associated carrier terminations. 341 +----+---------------+------------+-------------+-----------+------+ 342 | ID |Description | Capacity |Availability | Priority |Power | 343 +----+---------------+------------+-------------+-----------+------+ 344 | 1 |High capacity | 400 Mbps | 99.9% | Low |High | 345 +----+---------------+------------+-------------+-----------+------+ 346 | 2 |High avail- | 100 Mbps | 99.999% | High |Low | 347 | | ability | | | | | 348 +----+---------------+------------+-------------+-----------+------+ 350 Figure 3: Example of an operation mode table 352 An operation mode bundles together the values of a set of different 353 parameters. How each operation mode maps into certain set of 354 attributes is out of scope of this document. 356 4. Use Cases 358 The use cases described should be the basis for identification and 359 definition of the parameters to be supported by a YANG Data model for 360 management of radio links, applicable for centralized, unified, 361 multi-vendor management. The use cases involve configuration 362 management, inventory, status and statistics, performance management, 363 fault management, troubleshooting and root cause analysis. 365 Other product specific use cases, addressing e.g. installation, on- 366 site trouble shooting and fault resolution, are outside the scope of 367 this framework. If required, these use cases are expected to be 368 supported by product specific extensions to the standardized model. 370 4.1. Configuration Management 372 Configuration of a radio link terminal, the constituent carrier 373 terminations and when applicable the relationship to IP/Ethernet and 374 TDM interfaces. 376 o Understand the capabilities and limitations 378 Exchange of information between a manager and a device about the 379 capabilities supported and specific limitations in the parameter 380 values and enumerations that can be used. 382 Support for the XPIC (Cross Polarization Interference 383 Cancellation) feature or not and the maximum modulation supported 384 are two examples on information that could be exchanged. 386 o Initial Configuration 388 Initial configuration of a radio link terminal, enough to 389 establish L1 connectivity to an associated radio link terminal on 390 a device at far end over the hop. It may also include 391 configuration of the relationship between a radio link terminal 392 and an associated traffic interface, e.g. an Ethernet interface, 393 unless that is given by the equipment configuration. 395 Frequency, modulation, coding and output power are examples of 396 parameters typically configured for a carrier termination and type 397 of aggregation/bonding or protection configurations expected for a 398 radio link terminal. 400 o Radio link re-configuration and optimization 402 Re-configuration, update or optimization of an existing radio link 403 terminal. Output power and modulation for a carrier termination 404 and protection schemas and activation/de-activation of carriers in 405 a radio link terminal are examples on parameters that can be re- 406 configured and used for optimization of the performance of a 407 network. 409 o Radio link logical configuration 411 Radio link terminals configured to include a group of carriers are 412 widely used in microwave technology. There are several kinds of 413 groups: aggregation/bonding, 1+1 protection/redundancy, etc. To 414 avoid configuration on each carrier termination directly, a 415 logical control provides flexible management by mapping a logical 416 configuration to a set of physical attributes. This could also be 417 applied in a hierarchical SDN environment where some domain 418 controllers are located between the SDN controller and the radio 419 link terminal. 421 4.2. Inventory 423 o Retrieve logical inventory and configuration from device 425 Request from manager and response by device with information about 426 radio interfaces, their constitution and configuration. 428 o Retrieve physical/equipment inventory from device 429 Request from manager about physical and/or equipment inventory 430 associated with the radio link terminals and carrier terminations. 432 4.3. Status and statistics 434 o Actual status and performance of a radio link interface 436 Manager requests and device responds with information about actual 437 status and statistics of configured radio link interfaces and 438 their constituent parts. It's important to report the effective 439 bandwidth of a radio link since it can be configured to 440 dynamically adjust the modulation based on the current signal 441 conditions. 443 4.4. Performance management 445 o Configuration of historical performance measurements 447 Configuration of historical performance measurements for a radio 448 link interface and/or its constituent parts. See Section 4.1 449 above. 451 o Collection of historical performance data 453 Collection of historical performance data in bulk by the manager 454 is a general use case for a device and not specific to a radio 455 link interface. 457 Collection of an individual counter for a specific interval is in 458 same cases required as a complement to the retrieval in bulk as 459 described above. 461 4.5. Fault Management 463 o Configuration of alarm reporting 465 Configuration of alarm reporting associated specifically with 466 radio interfaces, e.g. configuration of alarm severity, is a 467 subset of the configuration use case to be supported. See 468 Section 4.1 above. 470 o Alarm management 472 Alarm synchronization, visualization, handling, notifications and 473 events are generic use cases for a device and should be supported 474 on a radio link interface. There are however radio-specific 475 alarms that are important to report, where signal degradation of 476 the radio link is one example. 478 4.6. Troubleshooting and Root Cause Analysis 480 Information and actions required by a manager/operator to investigate 481 and understand the underlying issue to a problem in the performance 482 and/or functionality of a radio link terminal and the associated 483 carrier terminations. 485 5. Requirements 487 For managing a microwave node including both the radio link and the 488 packet transport functionality, a unified data model is desired to 489 unify the modeling of the radio link interfaces and the L2/L3 490 interfaces using the same structure and the same modelling approach. 491 If some part of model is generic for other technology usage, it 492 should be clearly stated. 494 The purpose of the YANG Data Model is for management and control of 495 the radio link interface(s) and the relationship/connectivity to 496 other interfaces, typically to Ethernet interfaces, in a microwave 497 node. 499 The capability of configuring and managing microwave nodes includes 500 the following requirements for the modelling: 502 1. It MUST be possible to configure, manage and control a radio link 503 terminal and the constituent carrier terminations. 505 A. Configuration of frequency, channel bandwidth, modulation, 506 coding and transmitter output power MUST be supported for a 507 carrier termination. 509 B. A radio link terminal MUST configure the associated carrier 510 terminations and the type of aggregation/bonding or 511 protection configurations expected for the radio link 512 terminal. 514 C. The capability, e.g. the maximum modulation supported, and 515 the actual status/statistics, e.g. administrative status of 516 the carriers, SHOULD also be supported by the data model. 518 D. The definition of the features and parameters SHOULD be based 519 on established microwave equipment and radio standards, such 520 as ETSI EN 302 217 [EN302217-2] which specifies the essential 521 parameters for microwave systems operating from 1.4GHz to 522 86GHz. 524 2. It MUST be possible to map different traffic types (e.g. TDM, 525 Ethernet) to the transport capacity provided by a specific radio 526 link terminal. 528 3. It MUST be possible to configure and collect historical 529 measurements (for the use case described in section 5.4) to be 530 performed on a radio link interface, e.g. minimum, maximum and 531 average transmit power and receive level in dBm. 533 4. It MUST be possible to configure and retrieve alarms reporting 534 associated with the radio interfaces, e.g. configuration of alarm 535 severity, supported alarms like configuration fault, signal lost, 536 modem fault, radio fault. 538 6. Gap Analysis on Models 540 The purpose of the gap analysis is to identify and recommend what 541 models to use in a microwave device to support the use cases and 542 requirements specified in the previous chapters. This draft shall 543 also make a recommendation on how the gaps not supported should be 544 filled, including the need for development of new models and 545 evolution of existing models and drafts. 547 For microwave radio link functionality work has been initiated (ONF: 548 Microwave Modeling [ONF-model], IETF: Radio Link Model 549 [I-D.ietf-ccamp-mw-yang]. The analysis is expected to take these 550 initiatives into consideration and make a recommendation on how to 551 make use of them and how to complement them in order to fill the gaps 552 identified. 554 For generic functionality, not specific for radio link, the ambition 555 is to refer to existing or emerging models that could be applicable 556 for all functional areas in a microwave node. 558 6.1. Microwave Radio Link Functionality 560 [ONF-CIM] defines a CoreModel of the ONF Common Information Model. 561 An information model describes the things in a domain in terms of 562 objects, their properties (represented as attributes), and their 563 relationships. The ONF information model is expressed in Unified 564 Modeling Language (UML). The ONF CoreModel is independent of 565 specific data plane technology. The technology specific content, 566 acquired in a runtime solution via "filled in" cases of 567 specification, augment the CoreModel to provide a forwarding 568 technology-specific representation. 570 IETF Data Model defines an implementation and protocol-specific 571 details. YANG is a data modeling language used to model the 572 configuration and state data. [RFC8343] defines a generic YANG data 573 model for interface management which doesn't include technology 574 specific information. To describe the technology specific 575 information, several YANG data models have been proposed in IETF by 576 augmenting [RFC8343], e.g. [RFC8344]. The YANG data model is a 577 popular approach for modeling many packet transport technology 578 interfaces, and it is thereby well positioned to become an industry 579 standard. In light of this trend, [I-D.ietf-ccamp-mw-yang] provides 580 a YANG data model proposal for radio interfaces, which is well 581 aligned with the structure of other technology-specific YANG data 582 models augmenting [RFC8343]. 584 [RFC3444] explains the difference between Information Model(IM) and 585 Data Models(DM). IM is to model managed objects at a conceptual 586 level for designers and operators, while DM is defined at a lower 587 level and includes many details for implementers. In addition, the 588 protocol-specific details are usually included in DM. Since 589 conceptual models can be implemented in different ways, multiple DMs 590 can be derived from a single IM. 592 It is recommended to use the structure of the IETF: Radio Link Model 593 [I-D.ietf-ccamp-mw-yang] as the starting point, since 594 [I-D.ietf-ccamp-mw-yang] is a data model providing the wanted 595 alignment with [RFC8343]. To cover the identified gaps, it is 596 recommended to define new leafs/parameters in 597 [I-D.ietf-ccamp-mw-yang] while taking reference from [ONF-CIM]. It 598 is also recommended to add the required data nodes to describe the 599 interface layering for the capacity provided by a radio link terminal 600 and the associated Ethernet and TDM interfaces in a microwave node. 601 The principles and data nodes for interface layering described in 602 [RFC8343] should be used as a basis. 604 6.2. Generic Functionality 606 For generic functionality, not specific for radio link, the 607 recommendation is to refer to existing RFCs or emerging drafts 608 according to the table in Figure 4 below. New Radio Link Model is 609 used in the table for the cases where the functionality is 610 recommended to be included in the new radio link model as described 611 in Section 6.1. 613 +------------------------------------+-----------------------------+ 614 | Generic Functionality | Recommendation | 615 | | | 616 +------------------------------------+-----------------------------+ 617 |1.Fault Management | | 618 | | | 619 | Alarm Configuration | New Radio Link Model | 620 | | | 621 | Alarm notifications/ | [I-D.ietf-ccamp- | 622 | synchronization | alarm-module] | 623 +------------------------------------+-----------------------------+ 624 |2.Performance Management | | 625 | | | 626 | Performance Configuration/ | New Radio Link Model | 627 | Activation | | 628 | | | 629 | Performance Collection | New Radio Link Model and | 630 | | XML files | 631 +------------------------------------+-----------------------------+ 632 |3.Physical/Equipment Inventory | [RFC8348] | 633 +------------------------------------+-----------------------------+ 635 Figure 4: Recommendation on how to support generic functionality 637 Microwave specific alarm configurations are recommended to be 638 included in the new radio link model and could be based on what is 639 supported in the IETF and ONF Radio Link Models. Alarm notifications 640 and synchronization are general and is recommended to be supported by 641 a generic model, such as [I-D.ietf-ccamp-alarm-module]. 643 Activation of interval counters and thresholds could be a generic 644 function but it is recommended to be supported by the new radio link 645 specific model and can be based on both the ONF and IETF Microwave 646 Radio Link models. 648 Collection of interval/historical counters is a generic function that 649 needs to be supported in a node. File based collection via SSH File 650 Transfer Protocol(SFTP) and collection via a NETCONF/YANG interfaces 651 are two possible options and the recommendation is to include support 652 for the latter in the new radio link specific model. The ONF and 653 IETF Microwave Radio Link models can be used as a basis also in this 654 area. 656 Physical and/or equipment inventory associated with the radio link 657 terminals and carrier terminations is recommended to be covered by a 658 model generic for the complete node, e.g. [RFC8348] and it is 659 thereby outside the scope of the radio link specific model. 661 6.3. Summary 663 The conclusions and recommendations from the analysis can be 664 summarized as follows: 666 1. A Microwave Radio Link YANG Data Model should be defined with a 667 scope enough to support the use cases and requirements in 668 Sections 4 and 5 of this document. 670 2. Use the structure in the IETF: Radio Link Model 671 [I-D.ietf-ccamp-mw-yang] as the starting point. It augments 672 [RFC8343] and is thereby as required aligned with the structure 673 of the models for management of the L2 and L3 domains. 675 3. Use established microwave equipment and radio standards, such as 676 [EN302217-2], and the IETF: Radio Link Model 677 [I-D.ietf-ccamp-mw-yang] and the ONF: Microwave Modeling 678 [ONF-model] as the basis for the definition of the detailed 679 leafs/parameters to support the specified use cases and 680 requirements, and proposing new ones to cover identified gaps. 682 4. Add the required data nodes to describe the interface layering 683 for the capacity provided by a radio link terminal and the 684 associated Ethernet and TDM interfaces, using the principles and 685 data nodes for interface layering described in [RFC8343] as a 686 basis. 688 5. Include support for configuration of microwave specific alarms in 689 the Microwave Radio Link model and rely on a generic model such 690 as [I-D.ietf-ccamp-alarm-module] for notifications and alarm 691 synchronization. 693 6. Use a generic model such as [RFC8348] for physical/equipment 694 inventory. 696 7. Security Considerations 698 The configuration information may be considered sensitive or 699 vulnerable in the network environments. Unauthorized access to 700 configuration data nodes can have a negative effect on network 701 operations, e.g., interrupting the ability to forward traffic, or 702 increasing the interference level of the network. The status and 703 inventory reveal some network information that could be very helpful 704 to an attacker. A malicious attack to that information may result in 705 a loss of customer data. Security issue concerning the access 706 control to Management interfaces can be generally addressed by 707 authentication techniques providing origin verification, integrity 708 and confidentiality. In addition, management interfaces can be 709 physically or logically isolated, by configuring them to be only 710 accessible out-of-band, through a system that is physically or 711 logically separated from the rest of the network infrastructure. In 712 case where management interfaces are accessible in-band at the client 713 device or within the microwave transport network domain, filtering or 714 firewalling techniques can be used to restrict unauthorized in-band 715 traffic. Authentication techniques may be additionally used in all 716 cases. 718 This framework describes the requirements and characteristics of a 719 YANG Data Model for control and management of the radio link 720 interfaces in a microwave node. It is supposed to be accessed via a 721 management protocol with a secure transport layer, such as NETCONF 722 [RFC6241]. 724 8. IANA Considerations 726 This memo includes no request to IANA. 728 9. References 730 9.1. Normative References 732 [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate 733 Requirement Levels", BCP 14, RFC 2119, 734 DOI 10.17487/RFC2119, March 1997, 735 . 737 [RFC8174] Leiba, B., "Ambiguity of Uppercase vs Lowercase in RFC 738 2119 Key Words", BCP 14, RFC 8174, DOI 10.17487/RFC8174, 739 May 2017, . 741 9.2. Informative References 743 [EN302217-2] 744 "Fixed Radio Systems; Characteristics and requirements for 745 point to-point equipment and antennas; Part 2: Digital 746 systems operating in frequency bands from 1 GHz to 86 GHz; 747 Harmonised Standard covering the essential requirements of 748 article 3.2 of Directive 2014/53/EU", EN 302 217-2 749 V3.1.1 , May 2017. 751 [I-D.ietf-ccamp-alarm-module] 752 Vallin, S. and M. Bjorklund, "YANG Alarm Module", draft- 753 ietf-ccamp-alarm-module-01 (work in progress), February 754 2018. 756 [I-D.ietf-ccamp-mw-yang] 757 Ahlberg, J., Ye, M., Li, X., Spreafico, D., and M. 758 Vaupotic, "A YANG Data Model for Microwave Radio Link", 759 draft-ietf-ccamp-mw-yang-05 (work in progress), March 760 2018. 762 [ONF-CIM] "Core Information Model", version 1.2 , September 2016, 763 . 766 [ONF-model] 767 "Microwave Information Model", version 1.0 , December 768 2016, 769 . 773 [PB-YANG] "IEEE 802.1X and 802.1Q Module Specifications", version 774 0.4 , May 2015, 775 . 778 [RFC2863] McCloghrie, K. and F. Kastenholz, "The Interfaces Group 779 MIB", RFC 2863, DOI 10.17487/RFC2863, June 2000, 780 . 782 [RFC3444] Pras, A. and J. Schoenwaelder, "On the Difference between 783 Information Models and Data Models", RFC 3444, 784 DOI 10.17487/RFC3444, January 2003, 785 . 787 [RFC6241] Enns, R., Ed., Bjorklund, M., Ed., Schoenwaelder, J., Ed., 788 and A. Bierman, Ed., "Network Configuration Protocol 789 (NETCONF)", RFC 6241, DOI 10.17487/RFC6241, June 2011, 790 . 792 [RFC7426] Haleplidis, E., Ed., Pentikousis, K., Ed., Denazis, S., 793 Hadi Salim, J., Meyer, D., and O. Koufopavlou, "Software- 794 Defined Networking (SDN): Layers and Architecture 795 Terminology", RFC 7426, DOI 10.17487/RFC7426, January 796 2015, . 798 [RFC8343] Bjorklund, M., "A YANG Data Model for Interface 799 Management", RFC 8343, DOI 10.17487/RFC8343, March 2018, 800 . 802 [RFC8344] Bjorklund, M., "A YANG Data Model for IP Management", 803 RFC 8344, DOI 10.17487/RFC8344, March 2018, 804 . 806 [RFC8348] Bierman, A., Bjorklund, M., Dong, J., and D. Romascanu, "A 807 YANG Data Model for Hardware Management", RFC 8348, 808 DOI 10.17487/RFC8348, March 2018, 809 . 811 [RFC8349] Lhotka, L., Lindem, A., and Y. Qu, "A YANG Data Model for 812 Routing Management (NMDA Version)", RFC 8349, 813 DOI 10.17487/RFC8349, March 2018, 814 . 816 Appendix A. Contributors 818 Marko Vaupotic 819 Aviat Networks 820 Motnica 9 821 Trzin-Ljubljana 1236 822 Slovenia 824 Email: Marko.Vaupotic@aviatnet.com 826 Jeff Tantsura 828 Email: jefftant.ietf@gmail.com 830 Koji Kawada 831 NEC Corporation 832 1753, Shimonumabe Nakahara-ku 833 Kawasaki, Kanagawa 211-8666 834 Japan 836 Email: k-kawada@ah.jp.nec.com 838 Ippei Akiyoshi 839 NEC 840 1753, Shimonumabe Nakahara-ku 841 Kawasaki, Kanagawa 211-8666 842 Japan 844 Email: i-akiyoshi@ah.jp.nec.com 845 Daniela Spreafico 846 Nokia - IT 847 Via Energy Park, 14 848 Vimercate (MI) 20871 849 Italy 851 Email: daniela.spreafico@nokia.com 853 Authors' Addresses 855 Jonas Ahlberg (editor) 856 Ericsson AB 857 Lindholmspiren 11 858 Goteborg 417 56 859 Sweden 861 Email: jonas.ahlberg@ericsson.com 863 Ye Min (editor) 864 Huawei Technologies 865 No.1899, Xiyuan Avenue 866 Chengdu 611731 867 P.R.China 869 Email: amy.yemin@huawei.com 871 Xi Li 872 NEC Laboratories Europe 873 Kurfuersten-Anlage 36 874 Heidelberg 69115 875 Germany 877 Email: Xi.Li@neclab.eu 879 Luis Contreras 880 Telefonica I+D 881 Ronda de la Comunicacion, S/N 882 Madrid 28050 883 Spain 885 Email: luismiguel.contrerasmurillo@telefonica.com 886 Carlos Bernardos 887 Universidad Carlos III de Madrid 888 Av. Universidad, 30 889 Madrid, Leganes 28911 890 Spain 892 Email: cjbc@it.uc3m.es