draft-ietf-ccamp-microwave-framework-07.txt   rfc8432.txt 
CCAMP Working Group J. Ahlberg, Ed. Internet Engineering Task Force (IETF) J. Ahlberg, Ed.
Internet-Draft Ericsson AB Request for Comments: 8432 Ericsson AB
Intended status: Informational M. Ye, Ed. Category: Informational M. Ye, Ed.
Expires: December 7, 2018 Huawei Technologies ISSN: 2070-1721 Huawei Technologies
X. Li X. Li
NEC Laboratories Europe NEC Laboratories Europe
LM. Contreras LM. Contreras
Telefonica I+D Telefonica I+D
CJ. Bernardos CJ. Bernardos
Universidad Carlos III de Madrid Universidad Carlos III de Madrid
June 5, 2018 October 2018
A framework for Management and Control of microwave and millimeter wave A Framework for Management and Control of
interface parameters Microwave and Millimeter Wave Interface Parameters
draft-ietf-ccamp-microwave-framework-07
Abstract Abstract
The unification of control and management of microwave radio link The unification of control and management of microwave radio link
interfaces is a precondition for seamless multilayer networking and interfaces is a precondition for seamless multi-layer networking and
automated network provisioning and operation. automated network provisioning and operation.
This document describes the required characteristics and use cases This document describes the required characteristics and use cases
for control and management of radio link interface parameters using a for control and management of radio link interface parameters using a
YANG Data Model. YANG data model.
The purpose is to create a framework for identification of the The purpose is to create a framework to identify the necessary
necessary information elements and definition of a YANG Data Model information elements and define a YANG data model for control and
for control and management of the radio link interfaces in a management of the radio link interfaces in a microwave node. Some
microwave node. Some parts of the resulting model may be generic parts of the resulting model may be generic and could also be used by
which could also be used by other technologies, e.g., Ethernet other technologies, e.g., Ethernet technology.
technology.
Status of This Memo Status of This Memo
This Internet-Draft is submitted in full conformance with the This document is not an Internet Standards Track specification; it is
provisions of BCP 78 and BCP 79. published for informational purposes.
Internet-Drafts are working documents of the Internet Engineering This document is a product of the Internet Engineering Task Force
Task Force (IETF). Note that other groups may also distribute (IETF). It represents the consensus of the IETF community. It has
working documents as Internet-Drafts. The list of current Internet- received public review and has been approved for publication by the
Drafts is at https://datatracker.ietf.org/drafts/current/. Internet Engineering Steering Group (IESG). Not all documents
approved by the IESG are candidates for any level of Internet
Standard; see Section 2 of RFC 7841.
Internet-Drafts are draft documents valid for a maximum of six months Information about the current status of this document, any errata,
and may be updated, replaced, or obsoleted by other documents at any and how to provide feedback on it may be obtained at
time. It is inappropriate to use Internet-Drafts as reference https://www.rfc-editor.org/info/rfc8432.
material or to cite them other than as "work in progress."
This Internet-Draft will expire on December 7, 2018.
Copyright Notice Copyright Notice
Copyright (c) 2018 IETF Trust and the persons identified as the Copyright (c) 2018 IETF Trust and the persons identified as the
document authors. All rights reserved. document authors. All rights reserved.
This document is subject to BCP 78 and the IETF Trust's Legal This document is subject to BCP 78 and the IETF Trust's Legal
Provisions Relating to IETF Documents Provisions Relating to IETF Documents
(https://trustee.ietf.org/license-info) in effect on the date of (https://trustee.ietf.org/license-info) in effect on the date of
publication of this document. Please review these documents publication of this document. Please review these documents
carefully, as they describe your rights and restrictions with respect carefully, as they describe your rights and restrictions with respect
to this document. Code Components extracted from this document must to this document. Code Components extracted from this document must
include Simplified BSD License text as described in Section 4.e of include Simplified BSD License text as described in Section 4.e of
the Trust Legal Provisions and are provided without warranty as the Trust Legal Provisions and are provided without warranty as
described in the Simplified BSD License. described in the Simplified BSD License.
Table of Contents Table of Contents
1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 3 1. Introduction ....................................................3
1.1. Conventions used in this document . . . . . . . . . . . . 5 1.1. Conventions Used in This Document ..........................5
2. Terminology and Definitions . . . . . . . . . . . . . . . . . 5 2. Terminology and Definitions .....................................5
3. Approaches to manage and control radio link interfaces . . . 6 3. Approaches to Manage and Control Radio Link Interfaces ..........7
3.1. Network Management Solutions . . . . . . . . . . . . . . 7 3.1. Network Management Solutions ...............................7
3.2. Software Defined Networking . . . . . . . . . . . . . . . 7 3.2. Software-Defined Networking ................................7
4. Use Cases . . . . . . . . . . . . . . . . . . . . . . . . . . 8 4. Use Cases .......................................................8
4.1. Configuration Management . . . . . . . . . . . . . . . . 8 4.1. Configuration Management ...................................9
4.2. Inventory . . . . . . . . . . . . . . . . . . . . . . . . 9 4.2. Inventory .................................................10
4.3. Status and statistics . . . . . . . . . . . . . . . . . . 10 4.3. Status and Statistics .....................................10
4.4. Performance management . . . . . . . . . . . . . . . . . 10 4.4. Performance Management ....................................10
4.5. Fault Management . . . . . . . . . . . . . . . . . . . . 10 4.5. Fault Management ..........................................11
4.6. Troubleshooting and Root Cause Analysis . . . . . . . . . 11 4.6. Troubleshooting and Root Cause Analysis ...................11
5. Requirements . . . . . . . . . . . . . . . . . . . . . . . . 11 5. Requirements ...................................................11
6. Gap Analysis on Models . . . . . . . . . . . . . . . . . . . 12 6. Gap Analysis on Models .........................................12
6.1. Microwave Radio Link Functionality . . . . . . . . . . . 12 6.1. Microwave Radio Link Functionality ........................13
6.2. Generic Functionality . . . . . . . . . . . . . . . . . . 13 6.2. Generic Functionality .....................................14
6.3. Summary . . . . . . . . . . . . . . . . . . . . . . . . . 15 6.3. Summary ...................................................15
7. Security Considerations . . . . . . . . . . . . . . . . . . . 15 7. Security Considerations ........................................16
8. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 16 8. IANA Considerations ............................................16
9. References . . . . . . . . . . . . . . . . . . . . . . . . . 16 9. References .....................................................16
9.1. Normative References . . . . . . . . . . . . . . . . . . 16 9.1. Normative References ......................................16
9.2. Informative References . . . . . . . . . . . . . . . . . 16 9.2. Informative References ....................................17
Appendix A. Contributors . . . . . . . . . . . . . . . . . . . . 18 Contributors ......................................................19
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 19 Authors' Addresses ................................................20
1. Introduction 1. Introduction
Microwave radio is a technology that uses high frequency radio waves Microwave radio is a technology that uses high-frequency radio waves
to provide high speed wireless connections that can send and receive to provide high-speed wireless connections that can send and receive
voice, video, and data information. It is a general term used for voice, video, and data information. It is a general term used for
systems covering a very large range of traffic capacities, channel systems covering a very large range of traffic capacities, channel
separations, modulation formats and applications over a wide range of separations, modulation formats, and applications over a wide range
frequency bands from 1.4 GHz up to and above 100 GHz. of frequency bands from 1.4 GHz up to and above 100 GHz.
The main application for microwave is backhaul for mobile broadband. The main application for microwave is backhaul for mobile broadband.
Those networks will continue to be modernized using a combination of Those networks will continue to be modernized using a combination of
microwave and fiber technologies. The choice of technology is a microwave and fiber technologies. The choice of technology depends
question about fiber presence and cost of ownership, not about on fiber presence and cost of ownership, not capacity limitations in
capacity limitations in microwave. microwave.
Microwave is already today able to fully support the capacity needs Today, microwave is already able to fully support the capacity needs
of a backhaul in a radio access network and will evolve to support of a backhaul in a radio access network and will evolve to support
multiple gigabits in traditional frequency bands and beyond 10 multiple gigabits in traditional frequency bands and more than 10
gigabits in higher frequency bands with more bandwidth. L2 Ethernet gigabits in higher-frequency bands with more bandwidth. Layer 2 (L2)
features are normally an integrated part of microwave nodes and more Ethernet features are normally an integrated part of microwave nodes,
advanced L2 and L3 features will over time be introduced to support and more advanced L2 and Layer 3 (L3) features will be introduced
the evolution of the transport services to be provided by a backhaul/ over time to support the evolution of the transport services that
transport network. Note that the wireless access technologies such will be provided by a backhaul/transport network. Note that wireless
as 3/4/5G and Wi-Fi are not within the scope of this microwave model access technologies such as 3/4/5G and Wi-Fi are not within the scope
work. of this document.
Open and standardized interfaces are a pre-requisite for efficient Open and standardized interfaces are a prerequisite for efficient
management of equipment from multiple vendors, integrated in a single management of equipment from multiple vendors, integrated in a single
system/controller. This framework addresses management and control system/controller. This framework addresses management and control
of the radio link interface(s) and the relationship to other of the radio link interface(s) and their relationship to other
interfaces, typically to Ethernet interfaces, in a microwave node. A interfaces (typically, Ethernet interfaces) in a microwave node. A
radio link provides the transport over the air, using one or several radio link provides the transport over the air, using one or several
carriers in aggregated or protected configurations. Managing and carriers in aggregated or protected configurations. Managing and
controlling a transport service over a microwave node involves both controlling a transport service over a microwave node involves both
radio link and packet transport functionality. radio link and packet transport functionality.
Already today there are numerous IETF data models, RFCs and drafts, Today, there are already numerous IETF data models, RFCs, and
with technology specific extensions that cover a large part of the L2 Internet-Drafts with technology-specific extensions that cover a
and L3 domains. Examples are IP Management [RFC8344], Routing large part of the L2 and L3 domains. Examples include IP Management
Management [RFC8349] and Provider Bridge [PB-YANG]. They are based [RFC8344], Routing Management [RFC8349], and Provider Bridge
on the IETF YANG model for Interface Management [RFC8343], which is [IEEE802.1Qcp]. These are based on the IETF YANG data model for
an evolution of the SNMP IF-MIB [RFC2863]. Interface Management [RFC8343], which is an evolution of the SNMP
IF-MIB [RFC2863].
Since microwave nodes will contain more and more L2 and L3(packet) Since microwave nodes will contain more and more L2 and L3 (packet)
functionality which is expected to be managed using those models, functionality that is expected to be managed using those models,
there are advantages if radio link interfaces can be modeled and there are advantages if radio link interfaces can be modeled and
managed using the same structure and the same approach, specifically managed using the same structure and the same approach. This is
for use cases in which a microwave node is managed as one common especially true for use cases in which a microwave node is managed as
entity including both the radio link and the L2 and L3 functionality, one common entity that includes both the radio link and the L2 and L3
e.g. at basic configuration of node and connections, centralized functionality, e.g., basic configuration of the node and connections,
trouble shooting, upgrade and maintenance. All interfaces in a node, centralized troubleshooting, upgrade, and maintenance. All
irrespective of technology, would then be accessed from the same core interfaces in a node, irrespective of technology, would then be
model, i.e. [RFC8343], and could be extended with technology specific accessed from the same core model, i.e., [RFC8343], and could be
parameters in models augmenting that core model. The relationship/ extended with technology-specific parameters in models augmenting
connectivity between interfaces could be given by the physical that core model. The relationship/connectivity between interfaces
equipment configuration, e.g. the slot in which the Radio Link could be given by the physical equipment configuration. For example,
Terminal (modem) is plugged in could be associated with a specific the slot where the Radio Link Terminal (modem) is plugged in could be
Ethernet port due to the wiring in the backplane of the system, or it associated with a specific Ethernet port due to the wiring in the
could be flexible and therefore configured via a management system or backplane of the system, or it could be flexible and therefore
controller. configured via a management system or controller.
+------------------------------------------------------------------+ +------------------------------------------------------------------+
| Interface [RFC8343] | | Interface [RFC8343] |
| +---------------+ | | +---------------+ |
| | Ethernet Port | | | | Ethernet Port | |
| +---------------+ | | +---------------+ |
| \ | | \ |
| +---------------------+ | | +---------------------+ |
| | Radio Link Terminal | | | | Radio Link Terminal | |
| +---------------------+ | | +---------------------+ |
| / \ | | / \ |
| +---------------------+ +---------------------+ | | +---------------------+ +---------------------+ |
| | Carrier Termination | | Carrier Termination | | | | Carrier Termination | | Carrier Termination | |
| +---------------------+ +---------------------+ | | +---------------------+ +---------------------+ |
+------------------------------------------------------------------+ +------------------------------------------------------------------+
Figure 1: Relationship between interfaces in a node Figure 1: Relationship between Interfaces in a Node
There will always be certain implementations that differ among There will always be certain implementations that differ among
products and it is therefore practically impossible to achieve products, so it is practically impossible to achieve industry
industry consensus on every design detail. It is therefore important consensus on every design detail. It is therefore important to focus
to focus on the parameters that are required to support the use cases on the parameters that are required to support the use cases
applicable for centralized, unified, multi-vendor management and to applicable for centralized, unified, multi-vendor management and to
allow other parameters to be optional or to be covered by extensions allow other parameters to either be optional or be covered by
to the standardized model. Furthermore, a standard that allows for a extensions to the standardized model. Furthermore, a standard that
certain degree of freedom encourages innovation and competition which allows for a certain degree of freedom encourages innovation and
is something that benefits the entire industry. It is therefore competition, which benefits the entire industry. Thus, it is
important that a radio link management model covers all relevant important that a radio link management model covers all relevant
functions but also leaves room for product/feature-specific functions but also leaves room for product- and feature-specific
extensions. extensions.
For microwave radio link functionality work has been initiated (ONF: Models are available for microwave radio link functionality:
Microwave Modeling [ONF-model], IETF: Radio Link Model "Microwave Information Model" by the ONF [ONF-MW] and "Microwave
[I-D.ietf-ccamp-mw-yang]). The purpose of this effort is to reach Radio Link YANG Data Models" submitted to and discussed by the CCAMP
consensus within the industry around one common approach, with Working Group [CCAMP-MW]. The purpose of this document is to reach
respect to the use cases and requirements to be supported, the type consensus within the industry around one common approach with respect
and structure of the model and the resulting attributes to be to the use cases and requirements to be supported, the type and
included. This document describes the use cases and requirements structure of the model, and the resulting attributes to be included.
agreed to be covered, the expected characteristics of the model and This document describes the use cases, requirements, and expected
at the end includes an analysis of how the models in the two on-going characteristics of the model. It also includes an analysis of how
initiatives fulfill these expectations and a recommendation on what the models in the two ongoing initiatives fulfill these expectations
can be reused and what gaps need to be filled by a new and evolved and recommendations for what can be reused and what gaps need to be
radio link model. filled by a new and evolved model ("A YANG Data Model for Microwave
Radio Link" by the IETF [IETF-MW]).
1.1. Conventions used in this document 1.1. Conventions Used in This Document
The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
"SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this "SHOULD", "SHOULD NOT", "RECOMMENDED", "NOT RECOMMENDED", "MAY", and
document are to be interpreted as described in [RFC2119] [RFC8174] "OPTIONAL" in this document are to be interpreted as described in
when, and only when, they appear in all capitals, as shown here. BCP 14 [RFC2119] [RFC8174] when, and only when, they appear in all
capitals, as shown here.
2. Terminology and Definitions 2. Terminology and Definitions
Microwave radio is a term commonly used for technologies that operate Microwave radio: a term commonly used for technologies that operate
in both microwave and millimeter wave lengths and in frequency bands in both microwave and millimeter wavelengths and in frequency
from 1.4 GHz up to and beyond 100 GHz. In traditional bands it bands from 1.4 GHz up to and beyond 100 GHz. In traditional
typically supports capacities of 1-3 Gbps and in 70/80 GHz band up to bands, it typically supports capacities of 1-3 Gbps; in the 70/80
10 Gbps. Using multi-carrier systems operating in frequency bands GHz band, it supports up to 10 Gbps. Using multi-carrier systems
with wider channels, the technology will be capable of providing operating in frequency bands with wider channels, the technology
capacities of up to 100 Gbps. will be capable of providing capacities of up to 100 Gbps.
The microwave radio technology is widely used for point-to-point Microwave radio technology: widely used for point-to-point
telecommunications because of its small wavelength that allows telecommunications because its small wavelength allows
conveniently-sized antennas to direct them in narrow beams, and the conveniently sized antennas to direct radio waves in narrow beams
comparatively higher frequencies that allow broad bandwidth and high and its comparatively higher frequencies allow broad bandwidth and
data transmission rates. It is used for a broad range of fixed and high data-transmission rates. It is used for a broad range of
mobile services including high-speed, point-to-point wireless local fixed and mobile services, including high-speed, point-to-point
area networks (WLANs) and broadband access. wireless local area networks (WLANs) and broadband access.
ETSI EN 302 217 series defines the characteristics and requirements The ETSI EN 302 217 series defines the characteristics and
of microwave equipment and antennas. Especially ETSI EN 302 217-2 requirements of microwave equipment and antennas. In particular,
[EN302217-2] specifies the essential parameters for the systems ETSI EN 302 217-2 [EN302217-2] specifies the essential parameters
operating from 1.4GHz to 86GHz. for the systems operating from 1.4 GHz to 86 GHz.
Carrier Termination and Radio Link Terminal are two concepts defined Carrier Termination and Radio Link Terminal: two concepts defined to
to support modeling of microwave radio link features and parameters support modeling of microwave radio link features and parameters
in a structured and yet simple manner. in a structured yet simple manner.
Carrier Termination is an interface for the capacity provided over * Carrier Termination: an interface for the capacity provided
the air by a single carrier. It is typically defined by its over the air by a single carrier. It is typically defined by
transmitting and receiving frequencies. its transmitting and receiving frequencies.
Radio Link Terminal is an interface providing Ethernet capacity and/ * Radio Link Terminal: an interface providing Ethernet capacity
or Time Division Multiplexing (TDM) capacity to the associated and/or Time Division Multiplexing (TDM) capacity to the
Ethernet and/or TDM interfaces in a node and used for setting up a associated Ethernet and/or TDM interfaces in a node. It is
transport service over a microwave radio link. used for setting up a transport service over a microwave radio
link.
Figure 2 provides a graphical representation of Carrier Termination Figure 2 provides a graphical representation of the Carrier
and Radio Link Terminal concepts. Termination and Radio Link Terminal concepts.
/--------- Radio Link ---------\ /--------- Radio Link ---------\
Near End Far End Near End Far End
+---------------+ +---------------+ +---------------+ +---------------+
| Radio Link | | Radio Link | | Radio Link | | Radio Link |
| Terminal | | Terminal | | Terminal | | Terminal |
| | | | | | | |
| (Protected or Bonded) | | (Protected or Bonded) |
| | | | | | | |
skipping to change at page 6, line 39 skipping to change at page 6, line 43
| |Termination| | | |Termination| | | |Termination| | | |Termination| |
| | | | | | | | | | | | | | | |
| +-----------+ | | +-----------+ | | +-----------+ | | +-----------+ |
| | | | | | | |
+---------------+ +---------------+ +---------------+ +---------------+
\--- Microwave Node ---/ \--- Microwave Node ---/ \--- Microwave Node ---/ \--- Microwave Node ---/
Figure 2: Radio Link Terminal and Carrier Termination Figure 2: Radio Link Terminal and Carrier Termination
Software Defined Networking (SDN) is an architecture that decouples Software-Defined Networking (SDN): an architecture that decouples
the network control and forwarding functions enabling the network the network control and forwarding functions, enabling the network
control to become directly programmable and the underlying control to become directly programmable and the underlying
infrastructure to be abstracted for applications and network infrastructure to be abstracted for applications and network
services. SDN can be used for automation of traditional network services. SDN can be used for automation of traditional network
management functionality using an SDN approach of standardized management functionality using an SDN approach of standardized
programmable interfaces for control and management [RFC7426]. programmable interfaces for control and management [RFC7426].
3. Approaches to manage and control radio link interfaces 3. Approaches to Manage and Control Radio Link Interfaces
This framework addresses the definition of an open and standardized This framework addresses the definition of an open and standardized
interface for the radio link functionality in a microwave node. The interface for radio link functionality in a microwave node. The
application of such an interface used for management and control of application of such an interface used for management and control of
nodes and networks typically vary from one operator to another, in nodes and networks typically varies from one operator to another in
terms of the systems used and how they interact. Possible approaches terms of the systems used and how they interact. Possible approaches
include via the use of a network management system (NMS), via include using a Network Management System (NMS), Software-Defined
software defined networking (SDN) and via some combination of NMS and Networking (SDN), or some combination of the two. As there are still
SDN. As there are still many networks where the NMS is implemented many networks where the NMS is implemented as one component/interface
as one component/interface and the SDN controller is scoped to and the SDN controller is scoped to control-plane functionality as a
control plane functionality as a separate component/interface, this separate component/interface, this document does not preclude either
document does not preclude either model. The aim of this document is model. The aim of this document is to provide a framework for
to provide a framework for development of a common YANG Data Model development of a common YANG data model for both management and
for both management and control of microwave interfaces. control of microwave interfaces.
3.1. Network Management Solutions 3.1. Network Management Solutions
The classic network management solutions, with vendor specific domain The classic network management solutions, with vendor-specific domain
management combined with cross domain functionality for service management combined with cross-domain functionality for service
management and analytics, still dominate the market. These solutions management and analytics, still dominate the market. These solutions
are expected to evolve and benefit from an increased focus on are expected to evolve and benefit from an increased focus on
standardization by simplifying multi-vendor management and remove the standardization by simplifying multi-vendor management and removing
need for vendor/domain specific management. the need for vendor- or domain-specific management.
3.2. Software Defined Networking 3.2. Software-Defined Networking
One of the main drivers for applying SDN from an operator perspective One of the main drivers for applying SDN from an operator perspective
is simplification and automation of network provisioning as well as is simplification and automation of network provisioning as well as
end to end network service management. The vision is to have a end-to-end network service management. The vision is to have a
global view of the network conditions spanning across different global view of the network conditions spanning different vendors'
vendors' equipment and multiple technologies. equipment and multiple technologies.
If nodes from different vendors are be managed by the same SDN If nodes from different vendors are managed by the same SDN
controller via a node management interface (north bound interface, controller via a node management interface without the extra effort
NBI), without the extra effort of introducing intermediate systems, of introducing intermediate systems, all nodes must align their node
all nodes must align their node management interfaces. Hence, an management interfaces. Hence, an open and standardized node
open and standardized node management interface is required in a management interface is required in a multi-vendor environment. Such
multi-vendor environment. Such a standardized interface enables a a standardized interface enables unified management and configuration
unified management and configuration of nodes from different vendors of nodes from different vendors by a common set of applications.
by a common set of applications.
On top of SDN applications to configure, manage and control the nodes In addition to SDN applications for configuring, managing, and
and their associated transport interfaces including the L2 Ethernet controlling the nodes and their associated transport interfaces
and L3 IP interfaces as well as the radio interfaces, there are also (including the L2 Ethernet, L3 IP, and radio interfaces), there are
a large variety of other more advanced SDN applications that can be also a large variety of more advanced SDN applications that can be
utilized and/or developed. utilized and/or developed.
A potentially flexible approach for the operators is to use SDN in a A potentially flexible approach for operators is to use SDN in a
logical control way to manage the radio links by selecting a logically controlled way, managing the radio links by selecting a
predefined operation mode. The operation mode is a set of logical predefined operation mode. The operation mode is a set of logical
metrics or parameters describing a complete radio link configuration, metrics or parameters describing a complete radio link configuration,
such as capacity, availability, priority and power consumption. such as capacity, availability, priority, and power consumption.
An example of an operation mode table is shown in Figure 3. Based on An example of an operation mode table is shown in Figure 3. Based on
its operation policy (e.g., power consumption or traffic priority), its operation policy (e.g., power consumption or traffic priority),
the SDN controller selects one operation mode and translates that the SDN controller selects one operation mode and translates that
into the required configuration of the individual parameters for the into the required configuration of the individual parameters for the
radio link terminals and the associated carrier terminations. Radio Link Terminals and the associated Carrier Terminations.
+----+---------------+------------+-------------+-----------+------+ +----+---------------+------------+-------------+-----------+------+
| ID |Description | Capacity |Availability | Priority |Power | | ID |Description | Capacity |Availability | Priority |Power |
+----+---------------+------------+-------------+-----------+------+ +----+---------------+------------+-------------+-----------+------+
| 1 |High capacity | 400 Mbps | 99.9% | Low |High | | 1 |High capacity | 400 Mbps | 99.9% | Low |High |
+----+---------------+------------+-------------+-----------+------+ +----+---------------+------------+-------------+-----------+------+
| 2 |High avail- | 100 Mbps | 99.999% | High |Low | | 2 |High avail- | 100 Mbps | 99.999% | High |Low |
| | ability | | | | | | | ability | | | | |
+----+---------------+------------+-------------+-----------+------+ +----+---------------+------------+-------------+-----------+------+
Figure 3: Example of an operation mode table Figure 3: Example of an Operation Mode Table
An operation mode bundles together the values of a set of different An operation mode bundles together the values of a set of different
parameters. How each operation mode maps into certain set of parameters. How each operation mode maps a certain set of attributes
attributes is out of scope of this document. is out of the scope of this document.
4. Use Cases 4. Use Cases
The use cases described should be the basis for identification and The use cases described should be the basis for identifying and
definition of the parameters to be supported by a YANG Data model for defining the parameters to be supported by a YANG data model for
management of radio links, applicable for centralized, unified, management of radio links that will be applicable to centralized,
multi-vendor management. The use cases involve configuration unified, multi-vendor management. The use cases involve
management, inventory, status and statistics, performance management, configuration management, inventory, status and statistics,
fault management, troubleshooting and root cause analysis. performance management, fault management, and troubleshooting and
root cause analysis.
Other product specific use cases, addressing e.g. installation, on- Other product-specific use cases, e.g., addressing installation or
site trouble shooting and fault resolution, are outside the scope of on-site troubleshooting and fault resolution, are outside the scope
this framework. If required, these use cases are expected to be of this framework. If required, these use cases are expected to be
supported by product specific extensions to the standardized model. supported by product-specific extensions to the standardized model.
4.1. Configuration Management 4.1. Configuration Management
Configuration of a radio link terminal, the constituent carrier Configuration management involves configuring a Radio Link Terminal,
terminations and when applicable the relationship to IP/Ethernet and the constituent Carrier Terminations, and, when applicable, the
TDM interfaces. relationship to IP/Ethernet and TDM interfaces.
o Understand the capabilities and limitations o Understand the capabilities and limitations
Exchange of information between a manager and a device about the Exchange of information between a manager and a device about the
capabilities supported and specific limitations in the parameter capabilities supported and specific limitations in the parameter
values and enumerations that can be used. values and enumerations that can be used.
Support for the XPIC (Cross Polarization Interference Examples of information that could be exchanged include the
Cancellation) feature or not and the maximum modulation supported maximum modulation supported and support (or lack of support) for
are two examples on information that could be exchanged. the Cross Polarization Interference Cancellation (XPIC) feature.
o Initial Configuration o Initial Configuration
Initial configuration of a radio link terminal, enough to Initial configuration of a Radio Link Terminal, enough to
establish L1 connectivity to an associated radio link terminal on establish Layer 1 (L1) connectivity to an associated Radio Link
a device at far end over the hop. It may also include Terminal on a device at the far end over the hop. It may also
configuration of the relationship between a radio link terminal include configuration of the relationship between a Radio Link
and an associated traffic interface, e.g. an Ethernet interface, Terminal and an associated traffic interface, e.g., an Ethernet
unless that is given by the equipment configuration. interface, unless that is given by the equipment configuration.
Frequency, modulation, coding and output power are examples of Frequency, modulation, coding, and output power are examples of
parameters typically configured for a carrier termination and type parameters typically configured for a Carrier Termination and type
of aggregation/bonding or protection configurations expected for a of aggregation/bonding or protection configurations expected for a
radio link terminal. Radio Link Terminal.
o Radio link re-configuration and optimization o Radio link reconfiguration and optimization
Re-configuration, update or optimization of an existing radio link Reconfiguration, update, or optimization of an existing Radio Link
terminal. Output power and modulation for a carrier termination Terminal. Output power and modulation for a Carrier Termination
and protection schemas and activation/de-activation of carriers in as well as protection schemas and activation/deactivation of
a radio link terminal are examples on parameters that can be re- carriers in a Radio Link Terminal are examples on parameters that
configured and used for optimization of the performance of a can be reconfigured and used for optimization of the performance
network. of a network.
o Radio link logical configuration o Radio link logical configuration
Radio link terminals configured to include a group of carriers are Radio Link Terminals configured to include a group of carriers are
widely used in microwave technology. There are several kinds of widely used in microwave technology. There are several kinds of
groups: aggregation/bonding, 1+1 protection/redundancy, etc. To groups: aggregation/bonding, 1+1 protection/redundancy, etc. To
avoid configuration on each carrier termination directly, a avoid configuration on each Carrier Termination directly, a
logical control provides flexible management by mapping a logical logical control provides flexible management by mapping a logical
configuration to a set of physical attributes. This could also be configuration to a set of physical attributes. This could also be
applied in a hierarchical SDN environment where some domain applied in a hierarchical SDN environment where some domain
controllers are located between the SDN controller and the radio controllers are located between the SDN controller and the Radio
link terminal. Link Terminal.
4.2. Inventory 4.2. Inventory
o Retrieve logical inventory and configuration from device o Retrieve logical inventory and configuration from device
Request from manager and response by device with information about Request from manager and response by device with information about
radio interfaces, their constitution and configuration. radio interfaces, e.g., their constitution and configuration.
o Retrieve physical/equipment inventory from device o Retrieve physical/equipment inventory from device
Request from manager about physical and/or equipment inventory Request from manager about physical and/or equipment inventory
associated with the radio link terminals and carrier terminations. associated with the Radio Link Terminals and Carrier Terminations.
4.3. Status and statistics 4.3. Status and Statistics
o Actual status and performance of a radio link interface o Actual status and performance of a radio link interface
Manager requests and device responds with information about actual Manager requests and device responds with information about actual
status and statistics of configured radio link interfaces and status and statistics of configured radio link interfaces and
their constituent parts. It's important to report the effective their constituent parts. It's important to report the effective
bandwidth of a radio link since it can be configured to bandwidth of a radio link since it can be configured to
dynamically adjust the modulation based on the current signal dynamically adjust the modulation based on the current signal
conditions. conditions.
4.4. Performance management 4.4. Performance Management
o Configuration of historical performance measurements o Configuration of historical performance measurements
Configuration of historical performance measurements for a radio Configuration of historical performance measurements for a radio
link interface and/or its constituent parts. See Section 4.1 link interface and/or its constituent parts. See Section 4.1.
above.
o Collection of historical performance data o Collection of historical performance data
Collection of historical performance data in bulk by the manager Collection of historical performance data in bulk by the manager
is a general use case for a device and not specific to a radio is a general use case for a device and not specific to a radio
link interface. link interface.
Collection of an individual counter for a specific interval is in Collection of an individual counter for a specific interval is in
same cases required as a complement to the retrieval in bulk as some cases required as a complement to the retrieval in bulk as
described above. described above.
4.5. Fault Management 4.5. Fault Management
o Configuration of alarm reporting o Configuration of alarm reporting
Configuration of alarm reporting associated specifically with Configuration of alarm reporting associated specifically with
radio interfaces, e.g. configuration of alarm severity, is a radio interfaces, e.g., configuration of alarm severity, is a
subset of the configuration use case to be supported. See subset of the configuration use case to be supported. See
Section 4.1 above. Section 4.1.
o Alarm management o Alarm management
Alarm synchronization, visualization, handling, notifications and Alarm synchronization, visualization, handling, notifications, and
events are generic use cases for a device and should be supported events are generic use cases for a device and should be supported
on a radio link interface. There are however radio-specific on a radio link interface. There are, however, radio-specific
alarms that are important to report, where signal degradation of alarms that are important to report. Signal degradation of the
the radio link is one example. radio link is one example.
4.6. Troubleshooting and Root Cause Analysis 4.6. Troubleshooting and Root Cause Analysis
Information and actions required by a manager/operator to investigate Provide information and suggest actions required by a manager/
and understand the underlying issue to a problem in the performance operator to investigate and understand the underlying issue to a
and/or functionality of a radio link terminal and the associated problem in the performance and/or functionality of a Radio Link
carrier terminations. Terminal and the associated Carrier Terminations.
5. Requirements 5. Requirements
For managing a microwave node including both the radio link and the For managing a microwave node including both the radio link and the
packet transport functionality, a unified data model is desired to packet transport functionality, a unified data model is desired to
unify the modeling of the radio link interfaces and the L2/L3 unify the modeling of the radio link interfaces and the L2/L3
interfaces using the same structure and the same modelling approach. interfaces using the same structure and the same modeling approach.
If some part of model is generic for other technology usage, it If some part of the model is generic for other technology usage, it
should be clearly stated. should be clearly stated.
The purpose of the YANG Data Model is for management and control of The purpose of the YANG data model is for management and control of
the radio link interface(s) and the relationship/connectivity to the radio link interface(s) and the relationship/connectivity to
other interfaces, typically to Ethernet interfaces, in a microwave other interfaces, typically to Ethernet interfaces, in a microwave
node. node.
The capability of configuring and managing microwave nodes includes The capability of configuring and managing microwave nodes includes
the following requirements for the modelling: the following requirements for the model:
1. It MUST be possible to configure, manage and control a radio link 1. It MUST be possible to configure, manage, and control a Radio
terminal and the constituent carrier terminations. Link Terminal and the constituent Carrier Terminations.
A. Configuration of frequency, channel bandwidth, modulation, A. Configuration of frequency, channel bandwidth, modulation,
coding and transmitter output power MUST be supported for a coding, and transmitter output power MUST be supported for a
carrier termination. Carrier Termination.
B. A radio link terminal MUST configure the associated carrier B. A Radio Link Terminal MUST configure the associated Carrier
terminations and the type of aggregation/bonding or Terminations and the type of aggregation/bonding or
protection configurations expected for the radio link protection configurations expected for the Radio Link
terminal. Terminal.
C. The capability, e.g. the maximum modulation supported, and C. The capability (e.g., the maximum modulation supported) and
the actual status/statistics, e.g. administrative status of the actual status/statistics (e.g., administrative status of
the carriers, SHOULD also be supported by the data model. the carriers) SHOULD also be supported by the data model.
D. The definition of the features and parameters SHOULD be based D. The definition of the features and parameters SHOULD be based
on established microwave equipment and radio standards, such on established microwave equipment and radio standards, such
as ETSI EN 302 217 [EN302217-2] which specifies the essential as ETSI EN 302 217 [EN302217-2], which specifies the
parameters for microwave systems operating from 1.4GHz to essential parameters for microwave systems operating from 1.4
86GHz. GHz to 86 GHz.
2. It MUST be possible to map different traffic types (e.g. TDM, 2. It MUST be possible to map different traffic types (e.g., TDM and
Ethernet) to the transport capacity provided by a specific radio Ethernet) to the transport capacity provided by a specific Radio
link terminal. Link Terminal.
3. It MUST be possible to configure and collect historical 3. It MUST be possible to configure and collect historical
measurements (for the use case described in section 5.4) to be measurements (for the use case described in Section 4.4) to be
performed on a radio link interface, e.g. minimum, maximum and performed on a radio link interface (e.g., minimum, maximum,
average transmit power and receive level in dBm. average transmit power, and received level in dBm).
4. It MUST be possible to configure and retrieve alarms reporting 4. It MUST be possible to configure and retrieve alarms reporting
associated with the radio interfaces, e.g. configuration of alarm associated with the radio interfaces (e.g., configuration fault,
severity, supported alarms like configuration fault, signal lost, signal lost, modem fault, and radio fault).
modem fault, radio fault.
6. Gap Analysis on Models 6. Gap Analysis on Models
The purpose of the gap analysis is to identify and recommend what The purpose of the gap analysis is to identify and recommend what
models to use in a microwave device to support the use cases and models to use in a microwave device to support the use cases and
requirements specified in the previous chapters. This draft shall requirements specified in the previous sections. This document also
also make a recommendation on how the gaps not supported should be makes a recommendation for how the gaps not supported should be
filled, including the need for development of new models and filled, including the need for development of new models and
evolution of existing models and drafts. evolution of existing models and documents.
For microwave radio link functionality work has been initiated (ONF: Models are available for microwave radio link functionality:
Microwave Modeling [ONF-model], IETF: Radio Link Model "Microwave Information Model" by the ONF [ONF-MW] and "Microwave
[I-D.ietf-ccamp-mw-yang]. The analysis is expected to take these Radio Link YANG Data Models" submitted to and discussed by the CCAMP
initiatives into consideration and make a recommendation on how to Working Group [CCAMP-MW]. The analysis in this document takes these
make use of them and how to complement them in order to fill the gaps initiatives into consideration and makes a recommendation on how to
identified. use and complement them in order to fill the gaps identified.
For generic functionality, not specific for radio link, the ambition For generic functionality, not functionality specific to radio link,
is to refer to existing or emerging models that could be applicable the ambition is to refer to existing or emerging models that could be
for all functional areas in a microwave node. applicable for all functional areas in a microwave node.
6.1. Microwave Radio Link Functionality 6.1. Microwave Radio Link Functionality
[ONF-CIM] defines a CoreModel of the ONF Common Information Model. [ONF-CIM] defines a CoreModel of the ONF Common Information Model.
An information model describes the things in a domain in terms of An information model describes the things in a domain in terms of
objects, their properties (represented as attributes), and their objects, their properties (represented as attributes), and their
relationships. The ONF information model is expressed in Unified relationships. The ONF information model is expressed in Unified
Modeling Language (UML). The ONF CoreModel is independent of Modeling Language (UML). The ONF CoreModel is independent of
specific data plane technology. The technology specific content, specific data-plane technology. The technology-specific content,
acquired in a runtime solution via "filled in" cases of acquired in a runtime solution via "filled in" cases of
specification, augment the CoreModel to provide a forwarding specification, augments the CoreModel by providing a forwarding
technology-specific representation. technology-specific representation.
IETF Data Model defines an implementation and protocol-specific IETF data models define implementations and protocol-specific
details. YANG is a data modeling language used to model the details. YANG is a data modeling language used to model the
configuration and state data. [RFC8343] defines a generic YANG data configuration and state data. [RFC8343] defines a generic YANG data
model for interface management which doesn't include technology model for interface management that doesn't include technology-
specific information. To describe the technology specific specific information. To describe the technology-specific
information, several YANG data models have been proposed in IETF by information, several YANG data models have been proposed in the IETF
augmenting [RFC8343], e.g. [RFC8344]. The YANG data model is a to augment [RFC8343], e.g., the data model defined in [RFC8344]. The
popular approach for modeling many packet transport technology YANG data model is a popular approach for modeling interfaces for
interfaces, and it is thereby well positioned to become an industry many packet transport technologies and is thereby well positioned to
standard. In light of this trend, [I-D.ietf-ccamp-mw-yang] provides become an industry standard. In light of this trend, [CCAMP-MW]
a YANG data model proposal for radio interfaces, which is well provides a YANG data model proposal for radio interfaces that is well
aligned with the structure of other technology-specific YANG data aligned with the structure of other technology-specific YANG data
models augmenting [RFC8343]. models augmenting [RFC8343].
[RFC3444] explains the difference between Information Model(IM) and [RFC3444] explains the difference between Information Models (IMs)
Data Models(DM). IM is to model managed objects at a conceptual and Data Models (DMs). An IM models managed objects at a conceptual
level for designers and operators, while DM is defined at a lower level for designers and operators, while a DM is defined at a lower
level and includes many details for implementers. In addition, the level and includes many details for implementers. In addition, the
protocol-specific details are usually included in DM. Since protocol-specific details are usually included in a DM. Since
conceptual models can be implemented in different ways, multiple DMs conceptual models can be implemented in different ways, multiple DMs
can be derived from a single IM. can be derived from a single IM.
It is recommended to use the structure of the IETF: Radio Link Model It is recommended to use the structure of the model described in
[I-D.ietf-ccamp-mw-yang] as the starting point, since [CCAMP-MW] as the starting point, since it is a data model providing
[I-D.ietf-ccamp-mw-yang] is a data model providing the wanted the wanted alignment with [RFC8343]. To cover the identified gaps,
alignment with [RFC8343]. To cover the identified gaps, it is it is recommended to define new leafs/parameters and include those in
recommended to define new leafs/parameters in the new model [IETF-MW] while taking reference from [ONF-CIM]. It is
[I-D.ietf-ccamp-mw-yang] while taking reference from [ONF-CIM]. It also recommended to add the required data nodes to describe the
is also recommended to add the required data nodes to describe the interface layering for the capacity provided by a Radio Link Terminal
interface layering for the capacity provided by a radio link terminal
and the associated Ethernet and TDM interfaces in a microwave node. and the associated Ethernet and TDM interfaces in a microwave node.
The principles and data nodes for interface layering described in The principles and data nodes for interface layering described in
[RFC8343] should be used as a basis. [RFC8343] should be used as a basis.
6.2. Generic Functionality 6.2. Generic Functionality
For generic functionality, not specific for radio link, the For generic functionality, not functionality specific to radio links,
recommendation is to refer to existing RFCs or emerging drafts the recommendation is to refer to existing RFCs or emerging Internet-
according to the table in Figure 4 below. New Radio Link Model is Drafts according to Figure 4. "[IETF-MW]" is used in Figure 4 for
used in the table for the cases where the functionality is the cases where the functionality is recommended to be included in
recommended to be included in the new radio link model as described the new model [IETF-MW] as described in Section 6.1.
in Section 6.1.
+------------------------------------+-----------------------------+ +------------------------------------+-----------------------------+
| Generic Functionality | Recommendation | | Generic Functionality | Recommendation |
| | | | | |
+------------------------------------+-----------------------------+ +------------------------------------+-----------------------------+
|1.Fault Management | | |1. Fault Management | |
| | | | | |
| Alarm Configuration | New Radio Link Model | | Alarm Configuration | [IETF-MW] |
| | | | | |
| Alarm notifications/ | [I-D.ietf-ccamp- | | Alarm Notifications/ | [YANG-ALARM] |
| synchronization | alarm-module] | | Synchronization | |
+------------------------------------+-----------------------------+ +------------------------------------+-----------------------------+
|2.Performance Management | | |2. Performance Management | |
| | | | | |
| Performance Configuration/ | New Radio Link Model | | Performance Configuration/ | [IETF-MW] |
| Activation | | | Activation | |
| | | | | |
| Performance Collection | New Radio Link Model and | | Performance Collection | [IETF-MW] and XML files |
| | XML files |
+------------------------------------+-----------------------------+ +------------------------------------+-----------------------------+
|3.Physical/Equipment Inventory | [RFC8348] | |3. Physical/Equipment Inventory | [RFC8348] |
+------------------------------------+-----------------------------+ +------------------------------------+-----------------------------+
Figure 4: Recommendation on how to support generic functionality Figure 4: Recommendation for How to Support Generic Functionality
Microwave specific alarm configurations are recommended to be Microwave-specific alarm configurations are recommended to be
included in the new radio link model and could be based on what is included in the new model [IETF-MW] and could be based on what is
supported in the IETF and ONF Radio Link Models. Alarm notifications supported in the models described in [ONF-MW] and [CCAMP-MW]. Alarm
and synchronization are general and is recommended to be supported by notifications and synchronization are general and are recommended to
a generic model, such as [I-D.ietf-ccamp-alarm-module]. be supported by a generic model, such as [YANG-ALARM].
Activation of interval counters and thresholds could be a generic Activation of interval counters and thresholds could be a generic
function but it is recommended to be supported by the new radio link function, but it is recommended to be supported by the new model
specific model and can be based on both the ONF and IETF Microwave [IETF-MW]. It can be based on the models described in [ONF-MW] and
Radio Link models. [CCAMP-MW].
Collection of interval/historical counters is a generic function that Collection of interval/historical counters is a generic function that
needs to be supported in a node. File based collection via SSH File needs to be supported in a node. File-based collection via the SSH
Transfer Protocol(SFTP) and collection via a NETCONF/YANG interfaces File Transfer Protocol (SFTP) and collection via NETCONF/YANG
are two possible options and the recommendation is to include support interfaces are two possible options; the recommendation is to include
for the latter in the new radio link specific model. The ONF and support for the latter in the new model [IETF-MW]. The models
IETF Microwave Radio Link models can be used as a basis also in this described in [ONF-MW] and [CCAMP-MW] can also be used as a basis in
area. this area.
Physical and/or equipment inventory associated with the radio link Physical and/or equipment inventory associated with the Radio Link
terminals and carrier terminations is recommended to be covered by a Terminals and Carrier Terminations is recommended to be covered by a
model generic for the complete node, e.g. [RFC8348] and it is generic model for the complete node, e.g., the model defined in
thereby outside the scope of the radio link specific model. [RFC8348]. It is thereby outside the scope of the new model
[IETF-MW].
6.3. Summary 6.3. Summary
The conclusions and recommendations from the analysis can be The conclusions and recommendations from the analysis can be
summarized as follows: summarized as follows:
1. A Microwave Radio Link YANG Data Model should be defined with a 1. A new YANG data model for radio link [IETF-MW] should be defined
scope enough to support the use cases and requirements in with enough scope to support the use cases and requirements in
Sections 4 and 5 of this document. Sections 4 and 5 of this document.
2. Use the structure in the IETF: Radio Link Model 2. Use the structure of the model described in [CCAMP-MW] as the
[I-D.ietf-ccamp-mw-yang] as the starting point. It augments starting point. It augments [RFC8343] and is thereby as required
[RFC8343] and is thereby as required aligned with the structure aligned with the structure of the models for management of the L2
of the models for management of the L2 and L3 domains. and L3 domains.
3. Use established microwave equipment and radio standards, such as 3. Use established microwave equipment and radio standards (such as
[EN302217-2], and the IETF: Radio Link Model [EN302217-2], the model described in [CCAMP-MW], and the model
[I-D.ietf-ccamp-mw-yang] and the ONF: Microwave Modeling described in [ONF-MW]) as the basis for the definition of the
[ONF-model] as the basis for the definition of the detailed detailed leafs/ parameters to support the specified use cases and
leafs/parameters to support the specified use cases and requirements, proposing new ones to cover identified gaps.
requirements, and proposing new ones to cover identified gaps.
4. Add the required data nodes to describe the interface layering 4. Add the required data nodes to describe the interface layering
for the capacity provided by a radio link terminal and the for the capacity provided by a Radio Link Terminal and the
associated Ethernet and TDM interfaces, using the principles and associated Ethernet and TDM interfaces, using the principles and
data nodes for interface layering described in [RFC8343] as a data nodes for interface layering described in [RFC8343] as a
basis. basis.
5. Include support for configuration of microwave specific alarms in 5. Include support for configuration of microwave-specific alarms in
the Microwave Radio Link model and rely on a generic model such the new YANG data model [IETF-MW] and rely on a generic model
as [I-D.ietf-ccamp-alarm-module] for notifications and alarm such as [YANG-ALARM] for notifications and alarm synchronization.
synchronization.
6. Use a generic model such as [RFC8348] for physical/equipment 6. Use a generic model such as [RFC8348] for physical/equipment
inventory. inventory.
7. Security Considerations 7. Security Considerations
The configuration information may be considered sensitive or The configuration information may be considered sensitive or
vulnerable in the network environments. Unauthorized access to vulnerable in network environments. Unauthorized access to
configuration data nodes can have a negative effect on network configuration data nodes can have a negative effect on network
operations, e.g., interrupting the ability to forward traffic, or operations, e.g., interrupting the ability to forward traffic or
increasing the interference level of the network. The status and increasing the interference level of the network. The status and
inventory reveal some network information that could be very helpful inventory reveal some network information that could be very helpful
to an attacker. A malicious attack to that information may result in to an attacker. A malicious attack to that information may result in
a loss of customer data. Security issue concerning the access a loss of customer data. Security issues concerning the access
control to Management interfaces can be generally addressed by control to management interfaces can be generally addressed by
authentication techniques providing origin verification, integrity authentication techniques providing origin verification, integrity,
and confidentiality. In addition, management interfaces can be and confidentiality. In addition, management interfaces can be
physically or logically isolated, by configuring them to be only physically or logically isolated by configuring them to be only
accessible out-of-band, through a system that is physically or accessible out-of-band, through a system that is physically or
logically separated from the rest of the network infrastructure. In logically separated from the rest of the network infrastructure. In
case where management interfaces are accessible in-band at the client cases where management interfaces are accessible in-band at the
device or within the microwave transport network domain, filtering or client device or within the microwave transport network domain,
firewalling techniques can be used to restrict unauthorized in-band filtering or firewalling techniques can be used to restrict
traffic. Authentication techniques may be additionally used in all unauthorized in-band traffic. Additionally, authentication
cases. techniques may be used in all cases.
This framework describes the requirements and characteristics of a This framework describes the requirements and characteristics of a
YANG Data Model for control and management of the radio link YANG data model for control and management of the radio link
interfaces in a microwave node. It is supposed to be accessed via a interfaces in a microwave node. It is supposed to be accessed via a
management protocol with a secure transport layer, such as NETCONF management protocol with a secure transport layer, such as NETCONF
[RFC6241]. [RFC6241].
8. IANA Considerations 8. IANA Considerations
This memo includes no request to IANA. This document has no IANA actions.
9. References 9. References
9.1. Normative References 9.1. Normative References
[RFC2119] Bradner, S., "Key words for use in RFCs to Indicate [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate
Requirement Levels", BCP 14, RFC 2119, Requirement Levels", BCP 14, RFC 2119,
DOI 10.17487/RFC2119, March 1997, DOI 10.17487/RFC2119, March 1997,
<https://www.rfc-editor.org/info/rfc2119>. <https://www.rfc-editor.org/info/rfc2119>.
[RFC8174] Leiba, B., "Ambiguity of Uppercase vs Lowercase in RFC [RFC8174] Leiba, B., "Ambiguity of Uppercase vs Lowercase in RFC
2119 Key Words", BCP 14, RFC 8174, DOI 10.17487/RFC8174, 2119 Key Words", BCP 14, RFC 8174, DOI 10.17487/RFC8174,
May 2017, <https://www.rfc-editor.org/info/rfc8174>. May 2017, <https://www.rfc-editor.org/info/rfc8174>.
9.2. Informative References 9.2. Informative References
[CCAMP-MW] Ahlberg, J., Carlson, J-O., Lund, H-A., Olausson, T.,
Ye, M., and M. Vaupotic, "Microwave Radio Link YANG Data
Models", Work in Progress, draft-ahlberg-ccamp-microwave-
radio-link-01, May 2016.
[EN302217-2] [EN302217-2]
"Fixed Radio Systems; Characteristics and requirements for ETSI, "Fixed Radio Systems; Characteristics and
point to-point equipment and antennas; Part 2: Digital requirements for point-to-point equipment and antennas;
systems operating in frequency bands from 1 GHz to 86 GHz; Part 2: Digital systems operating in frequency bands from
Harmonised Standard covering the essential requirements of 1 GHz to 86 GHz; Harmonised Standard covering the
article 3.2 of Directive 2014/53/EU", EN 302 217-2 essential requirements of article 3.2 of Directive
V3.1.1 , May 2017. 2014/53/EU", ETSI EN 302 217-2, V3.1.1, May 2017.
[I-D.ietf-ccamp-alarm-module] [IEEE802.1Qcp]
Vallin, S. and M. Bjorklund, "YANG Alarm Module", draft- IEEE, "Bridges and Bridged Networks Ammendment: YANG Data
ietf-ccamp-alarm-module-01 (work in progress), February Model", Work in Progress, Draft 2.2, March 2018,
2018. <https://1.ieee802.org/tsn/802-1qcp/>.
[I-D.ietf-ccamp-mw-yang] [IETF-MW] Ahlberg, J., Ye, M., Li, X., Spreafico, D., and
Ahlberg, J., Ye, M., Li, X., Spreafico, D., and M. M. Vaupotic, "A YANG Data Model for Microwave Radio Link",
Vaupotic, "A YANG Data Model for Microwave Radio Link", Work in Progress, draft-ietf-ccamp-mw-yang-10, October
draft-ietf-ccamp-mw-yang-05 (work in progress), March
2018. 2018.
[ONF-CIM] "Core Information Model", version 1.2 , September 2016, [ONF-CIM] ONF, "Core Information Model (CoreModel)", ONF
<https://www.opennetworking.org/wp- TR-512, version 1.2, September 2016,
content/uploads/2014/10/TR-512_CIM_(CoreModel)_1.2.zip>. <https://www.opennetworking.org/images/stories/downloads/
sdn-resources/technical-reports/
TR-512_CIM_(CoreModel)_1.2.zip>.
[ONF-model] [ONF-MW] ONF, "Microwave Information Model", ONF TR-532, version
"Microwave Information Model", version 1.0 , December 1.0, December 2016,
2016,
<https://www.opennetworking.org/images/stories/downloads/ <https://www.opennetworking.org/images/stories/downloads/
sdn-resources/technical-reports/ sdn-resources/technical-reports/
TR-532-Microwave-Information-Model-V1.pdf>. TR-532-Microwave-Information-Model-V1.pdf>.
[PB-YANG] "IEEE 802.1X and 802.1Q Module Specifications", version
0.4 , May 2015,
<http://www.ieee802.org/1/files/public/docs2015/
new-mholness-YANG-8021x-0515-v04.pdf>.
[RFC2863] McCloghrie, K. and F. Kastenholz, "The Interfaces Group [RFC2863] McCloghrie, K. and F. Kastenholz, "The Interfaces Group
MIB", RFC 2863, DOI 10.17487/RFC2863, June 2000, MIB", RFC 2863, DOI 10.17487/RFC2863, June 2000,
<https://www.rfc-editor.org/info/rfc2863>. <https://www.rfc-editor.org/info/rfc2863>.
[RFC3444] Pras, A. and J. Schoenwaelder, "On the Difference between [RFC3444] Pras, A. and J. Schoenwaelder, "On the Difference between
Information Models and Data Models", RFC 3444, Information Models and Data Models", RFC 3444,
DOI 10.17487/RFC3444, January 2003, DOI 10.17487/RFC3444, January 2003,
<https://www.rfc-editor.org/info/rfc3444>. <https://www.rfc-editor.org/info/rfc3444>.
[RFC6241] Enns, R., Ed., Bjorklund, M., Ed., Schoenwaelder, J., Ed., [RFC6241] Enns, R., Ed., Bjorklund, M., Ed., Schoenwaelder, J., Ed.,
skipping to change at page 18, line 19 skipping to change at page 18, line 34
[RFC8348] Bierman, A., Bjorklund, M., Dong, J., and D. Romascanu, "A [RFC8348] Bierman, A., Bjorklund, M., Dong, J., and D. Romascanu, "A
YANG Data Model for Hardware Management", RFC 8348, YANG Data Model for Hardware Management", RFC 8348,
DOI 10.17487/RFC8348, March 2018, DOI 10.17487/RFC8348, March 2018,
<https://www.rfc-editor.org/info/rfc8348>. <https://www.rfc-editor.org/info/rfc8348>.
[RFC8349] Lhotka, L., Lindem, A., and Y. Qu, "A YANG Data Model for [RFC8349] Lhotka, L., Lindem, A., and Y. Qu, "A YANG Data Model for
Routing Management (NMDA Version)", RFC 8349, Routing Management (NMDA Version)", RFC 8349,
DOI 10.17487/RFC8349, March 2018, DOI 10.17487/RFC8349, March 2018,
<https://www.rfc-editor.org/info/rfc8349>. <https://www.rfc-editor.org/info/rfc8349>.
Appendix A. Contributors [YANG-ALARM]
Vallin, S. and M. Bjorklund, "YANG Alarm Module", Work in
Progress, draft-ietf-ccamp-alarm-module-04, October 2018.
Contributors
Marko Vaupotic Marko Vaupotic
Aviat Networks Aviat Networks
Motnica 9 Motnica 9
Trzin-Ljubljana 1236 Trzin-Ljubljana 1236
Slovenia Slovenia
Email: Marko.Vaupotic@aviatnet.com Email: Marko.Vaupotic@aviatnet.com
Jeff Tantsura Jeff Tantsura
skipping to change at page 19, line 22 skipping to change at page 20, line 15
Authors' Addresses Authors' Addresses
Jonas Ahlberg (editor) Jonas Ahlberg (editor)
Ericsson AB Ericsson AB
Lindholmspiren 11 Lindholmspiren 11
Goteborg 417 56 Goteborg 417 56
Sweden Sweden
Email: jonas.ahlberg@ericsson.com Email: jonas.ahlberg@ericsson.com
Ye Min (editor) Min Ye (editor)
Huawei Technologies Huawei Technologies
No.1899, Xiyuan Avenue No.1899, Xiyuan Avenue
Chengdu 611731 Chengdu 611731
P.R.China China
Email: amy.yemin@huawei.com Email: amy.yemin@huawei.com
Xi Li Xi Li
NEC Laboratories Europe NEC Laboratories Europe
Kurfuersten-Anlage 36 Kurfuersten-Anlage 36
Heidelberg 69115 Heidelberg 69115
Germany Germany
Email: Xi.Li@neclab.eu Email: Xi.Li@neclab.eu
Luis Contreras Luis Contreras
Telefonica I+D Telefonica I+D
Ronda de la Comunicacion, S/N Ronda de la Comunicacion, S/N
Madrid 28050 Madrid 28050
Spain Spain
Email: luismiguel.contrerasmurillo@telefonica.com Email: luismiguel.contrerasmurillo@telefonica.com
Carlos Bernardos
Carlos J. Bernardos
Universidad Carlos III de Madrid Universidad Carlos III de Madrid
Av. Universidad, 30 Av. Universidad, 30
Madrid, Leganes 28911 Madrid, Leganes 28911
Spain Spain
Email: cjbc@it.uc3m.es Email: cjbc@it.uc3m.es
 End of changes. 133 change blocks. 
403 lines changed or deleted 405 lines changed or added

This html diff was produced by rfcdiff 1.47. The latest version is available from http://tools.ietf.org/tools/rfcdiff/