draft-ietf-ccamp-microwave-framework-06.txt   draft-ietf-ccamp-microwave-framework-07.txt 
CCAMP Working Group J. Ahlberg, Ed. CCAMP Working Group J. Ahlberg, Ed.
Internet-Draft Ericsson AB Internet-Draft Ericsson AB
Intended status: Informational M. Ye, Ed. Intended status: Informational M. Ye, Ed.
Expires: November 19, 2018 Huawei Technologies Expires: December 7, 2018 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
May 18, 2018 June 5, 2018
A framework for Management and Control of microwave and millimeter wave A framework for Management and Control of microwave and millimeter wave
interface parameters interface parameters
draft-ietf-ccamp-microwave-framework-06 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 multilayer 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 for identification of the
necessary information elements and definition of a YANG Data Model necessary information elements and definition of a YANG Data Model
for control and management of the radio link interfaces in a for control and management of the radio link interfaces in a
microwave node. Some parts of the resulting model may be generic microwave node. Some parts of the resulting model may be generic
which could also be used by other technologies, e.g., ETH technology. which could also be used by other technologies, e.g., Ethernet
technology.
Status of This Memo Status of This Memo
This Internet-Draft is submitted in full conformance with the This Internet-Draft is submitted in full conformance with the
provisions of BCP 78 and BCP 79. provisions of BCP 78 and BCP 79.
Internet-Drafts are working documents of the Internet Engineering Internet-Drafts are working documents of the Internet Engineering
Task Force (IETF). Note that other groups may also distribute Task Force (IETF). Note that other groups may also distribute
working documents as Internet-Drafts. The list of current Internet- working documents as Internet-Drafts. The list of current Internet-
Drafts is at https://datatracker.ietf.org/drafts/current/. Drafts is at https://datatracker.ietf.org/drafts/current/.
Internet-Drafts are draft documents valid for a maximum of six months Internet-Drafts are draft documents valid for a maximum of six months
and may be updated, replaced, or obsoleted by other documents at any and may be updated, replaced, or obsoleted by other documents at any
time. It is inappropriate to use Internet-Drafts as reference time. It is inappropriate to use Internet-Drafts as reference
material or to cite them other than as "work in progress." material or to cite them other than as "work in progress."
This Internet-Draft will expire on November 19, 2018. 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
skipping to change at page 2, line 26 skipping to change at page 2, line 26
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 . . . 7 3. Approaches to manage and control radio link interfaces . . . 6
3.1. Network Management Solutions . . . . . . . . . . . . . . 8 3.1. Network Management Solutions . . . . . . . . . . . . . . 7
3.2. Software Defined Networking . . . . . . . . . . . . . . . 8 3.2. Software Defined Networking . . . . . . . . . . . . . . . 7
4. Use Cases . . . . . . . . . . . . . . . . . . . . . . . . . . 9 4. Use Cases . . . . . . . . . . . . . . . . . . . . . . . . . . 8
4.1. Configuration Management . . . . . . . . . . . . . . . . 9 4.1. Configuration Management . . . . . . . . . . . . . . . . 8
4.1.1. Understand the capabilities and limitations . . . . . 9 4.2. Inventory . . . . . . . . . . . . . . . . . . . . . . . . 9
4.1.2. Initial Configuration . . . . . . . . . . . . . . . . 10 4.3. Status and statistics . . . . . . . . . . . . . . . . . . 10
4.1.3. Radio link re-configuration and optimization . . . . 10 4.4. Performance management . . . . . . . . . . . . . . . . . 10
4.1.4. Radio link logical configuration . . . . . . . . . . 10 4.5. Fault Management . . . . . . . . . . . . . . . . . . . . 10
4.2. Inventory . . . . . . . . . . . . . . . . . . . . . . . . 10 4.6. Troubleshooting and Root Cause Analysis . . . . . . . . . 11
4.2.1. Retrieve logical inventory and configuration from 5. Requirements . . . . . . . . . . . . . . . . . . . . . . . . 11
device . . . . . . . . . . . . . . . . . . . . . . . 10 6. Gap Analysis on Models . . . . . . . . . . . . . . . . . . . 12
4.2.2. Retrieve physical/equipment inventory from device . . 11 6.1. Microwave Radio Link Functionality . . . . . . . . . . . 12
4.3. Status and statistics . . . . . . . . . . . . . . . . . . 11 6.2. Generic Functionality . . . . . . . . . . . . . . . . . . 13
4.3.1. Actual status and performance of a radio link 6.3. Summary . . . . . . . . . . . . . . . . . . . . . . . . . 15
interface . . . . . . . . . . . . . . . . . . . . . . 11 7. Security Considerations . . . . . . . . . . . . . . . . . . . 15
4.4. Performance management . . . . . . . . . . . . . . . . . 11 8. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 16
4.4.1. Configuration of historical measurements to be 9. References . . . . . . . . . . . . . . . . . . . . . . . . . 16
performed . . . . . . . . . . . . . . . . . . . . . . 11 9.1. Normative References . . . . . . . . . . . . . . . . . . 16
4.4.2. Collection of historical performance data . . . . . . 11 9.2. Informative References . . . . . . . . . . . . . . . . . 16
4.5. Fault Management . . . . . . . . . . . . . . . . . . . . 11 Appendix A. Contributors . . . . . . . . . . . . . . . . . . . . 18
4.5.1. Configuration of alarm reporting . . . . . . . . . . 11 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 19
4.5.2. Alarm management . . . . . . . . . . . . . . . . . . 11
4.6. Troubleshooting and Root Cause Analysis . . . . . . . . . 12
5. Requirements . . . . . . . . . . . . . . . . . . . . . . . . 12
6. Gap Analysis on Models . . . . . . . . . . . . . . . . . . . 13
6.1. Microwave Radio Link Functionality . . . . . . . . . . . 13
6.2. Generic Functionality . . . . . . . . . . . . . . . . . . 15
6.3. Summary . . . . . . . . . . . . . . . . . . . . . . . . . 16
7. Security Considerations . . . . . . . . . . . . . . . . . . . 17
8. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 17
9. References . . . . . . . . . . . . . . . . . . . . . . . . . 17
9.1. Normative References . . . . . . . . . . . . . . . . . . 17
9.2. Informative References . . . . . . . . . . . . . . . . . 18
Appendix A. Contributors . . . . . . . . . . . . . . . . . . . . 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 of
frequency bands from 1 GHz up to and above 100 GHz. 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 is a
question about fiber presence and cost of ownership, not about question about fiber presence and cost of ownership, not about
capacity limitations in microwave. capacity limitations in microwave.
Microwave is already today able to fully support the capacity needs Microwave is already today 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 beyond 10
gigabits in higher frequency bands with more band width. L2 Ethernet gigabits in higher frequency bands with more bandwidth. L2 Ethernet
features are normally an integrated part of microwave nodes and more features are normally an integrated part of microwave nodes and more
advanced L2 and L3 features will over time be introduced to support advanced L2 and L3 features will over time be introduced to support
the evolution of the transport services to be provided by a backhaul/ the evolution of the transport services to be provided by a backhaul/
transport network. Note that the wireless access technologies such transport network. Note that the wireless access technologies such
as 3/4/5G and Wi-Fi are not within the scope of this microwave model as 3/4/5G and Wi-Fi are not within the scope of this microwave model
work. work.
Open and standardized interfaces are a pre-requisite for efficient Open and standardized interfaces are a pre-requisite 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
skipping to change at page 4, line 14 skipping to change at page 3, line 50
Already today there are numerous IETF data models, RFCs and drafts, Already today there are numerous IETF data models, RFCs and drafts,
with technology specific extensions that cover a large part of the L2 with technology specific extensions that cover a large part of the L2
and L3 domains. Examples are IP Management [RFC8344], Routing and L3 domains. Examples are IP Management [RFC8344], Routing
Management [RFC8349] and Provider Bridge [PB-YANG]. They are based Management [RFC8349] and Provider Bridge [PB-YANG]. They are based
on the IETF YANG model for Interface Management [RFC8343], which is on the IETF YANG model for Interface Management [RFC8343], which is
an evolution of the SNMP IF-MIB [RFC2863]. 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 which is expected to be managed using those models,
there are advantages if radio link interfaces can be modeled and be 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, specifically
for use cases in which a microwave node is managed as one common for use cases in which a microwave node is managed as one common
entity including both the radio link and the L2 and L3 functionality, entity including both the radio link and the L2 and L3 functionality,
e.g. at basic configuration of node and connections, centralized e.g. at basic configuration of node and connections, centralized
trouble shooting, upgrade and maintenance. All interfaces in a node, trouble shooting, upgrade and maintenance. All interfaces in a node,
irrespective of technology, would then be accessed from the same core irrespective of technology, would then be accessed from the same core
model, i.e. [RFC8343], and could be extended with technology specific model, i.e. [RFC8343], and could be extended with technology specific
parameters in models augmenting that core model. The relationship/ parameters in models augmenting that core model. The relationship/
connectivity between interfaces could be given by the physical connectivity between interfaces could be given by the physical
equipment configuration, e.g. the slot in which the Radio Link equipment configuration, e.g. the slot in which the Radio Link
skipping to change at page 5, line 31 skipping to change at page 5, line 19
can be reused and what gaps need to be filled by a new and evolved can be reused and what gaps need to be filled by a new and evolved
radio link model. radio link model.
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", "MAY", and "OPTIONAL" in this
document are to be interpreted as described in [RFC2119] [RFC8174] document are to be interpreted as described in [RFC2119] [RFC8174]
when, and only when, they appear in all capitals, as shown here. when, and only when, they appear in all capitals, as shown here.
While [RFC2119] [RFC8174] describes interpretations of these key
words in terms of protocol specifications and implementations, they
are used in this document to describe high level requirements to be
met when defining the YANG Data Model for Microwave Radio Link.
This document does not define any protocol extension, hence only
[RFC2119] [RFC8174] can be considered as a normative reference.
However, the list of normative references includes a number of
documents that can be useful for a better understanding of the
context.
2. Terminology and Definitions 2. Terminology and Definitions
Microwave radio is a term commonly used for technologies that operate Microwave radio is a term commonly used for technologies that operate
in both microwave and millimeter wave lengths and in frequency bands in both microwave and millimeter wave lengths and in frequency bands
from 1.4 GHz up to and beyond 100 GHz. In traditional bands it from 1.4 GHz up to and beyond 100 GHz. In traditional bands it
typically supports capacities of 1-3 Gbps and in 70/80 GHz band up to typically supports capacities of 1-3 Gbps and in 70/80 GHz band up to
10 Gbps. Using multi-carrier systems operating in frequency bands 10 Gbps. Using multi-carrier systems operating in frequency bands
with wider channels, the technology will be capable of providing with wider channels, the technology will be capable of providing
capacities up 100 Gbps. capacities of up to 100 Gbps.
The microwave radio technology is widely used for point-to-point The microwave radio technology is widely used for point-to-point
telecommunications because of its small wavelength that allows telecommunications because of its small wavelength that allows
conveniently-sized antennas to direct them in narrow beams, and the conveniently-sized antennas to direct them in narrow beams, and the
comparatively higher frequencies that allow broad bandwidth and high comparatively higher frequencies that allow broad bandwidth and high
data transmission rates. It is used for a broad range of fixed and data transmission rates. It is used for a broad range of fixed and
mobile services including high-speed, point-to-point wireless local mobile services including high-speed, point-to-point wireless local
area networks (WLANs) and broadband access. area networks (WLANs) and broadband access.
ETSI EN 302 217 series defines the characteristics and requirements ETSI EN 302 217 series defines the characteristics and requirements
skipping to change at page 7, line 38 skipping to change at page 6, line 43
+---------------+ +---------------+ +---------------+ +---------------+
\--- 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) is 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 as a term for automation of traditional services. SDN can be used for automation of traditional network
network management, which can be implemented using a similar management functionality using an SDN approach of standardized
approach. The adoption of an SDN framework for management and programmable interfaces for control and management [RFC7426].
control the microwave interface is the key purpose of this work.
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 the 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 vary from one operator to another, in
terms of the systems used and how they interact. A traditional terms of the systems used and how they interact. Possible approaches
solution is network management system(NMS), while an emerging one is include via the use of a network management system (NMS), via
SDN. SDN solutions can be used as part of the network management software defined networking (SDN) and via some combination of NMS and
system, allowing for direct network programmability and automated SDN. As there are still many networks where the NMS is implemented
configurability by means of a centralized SDN control and as one component/interface and the SDN controller is scoped to
standardized interfaces to program the nodes. It's noted that control plane functionality as a separate component/interface, this
there's idea that the NMS and SDN are evolving towards a component, document does not preclude either model. The aim of this document is
and the distinction between them is quite vague. Another fact is to provide a framework for development of a common YANG Data Model
that there is still plenty of networks where NMS is still considered for both management and control of microwave interfaces.
as the implementation of the management plane, while SDN is
considered as the centralization of the control plane. They are
still kept as separate components.
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 dominates the market. These management and analytics, still dominate the market. These solutions
solutions are expected to evolve and benefit from an increased focus are expected to evolve and benefit from an increased focus on
on standardization by simplifying multi-vendor management and remove standardization by simplifying multi-vendor management and remove the
the need for vendor/domain specific management. need for vendor/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 across different
vendors' equipment and multiple technologies. vendors' equipment and multiple technologies.
If nodes from different vendors shall be managed by the same SDN If nodes from different vendors are be managed by the same SDN
controller via a node management interface (north bound interface, controller via a node management interface (north bound interface,
NBI), without the extra effort of introducing intermediate systems, NBI), without the extra effort of introducing intermediate systems,
all nodes must align their node management interfaces. Hence, an all nodes must align their node management interfaces. Hence, an
open and standardized node management interface are required in a open and standardized node management interface is required in a
multi-vendor environment. Such standardized interface enables a multi-vendor environment. Such a standardized interface enables a
unified management and configuration of nodes from different vendors unified management and configuration 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 On top of SDN applications to configure, manage and control the nodes
and their associated transport interfaces including the L2 Ethernet and their associated transport interfaces including the L2 Ethernet
and L3 IP interfaces as well as the radio interfaces, there are also and L3 IP interfaces as well as the radio interfaces, there are also
a large variety of other more advanced SDN applications that can be a large variety of other more advanced SDN applications that can be
exploited and/or developed. utilized and/or developed.
A potential flexible approach for the operators is to use SDN in a A potentially flexible approach for the operators is to use SDN in a
logical control way to manage the radio links by selecting a logical control way to manage 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.
skipping to change at page 9, line 24 skipping to change at page 8, line 24
| 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 into certain set of
attributes is out of scope of this document. Effort on a attributes is out of scope of this document.
standardizing operation mode is required to implement a smoothly
operator environment.
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 identification and
definition of the parameters to be supported by a YANG Data model for definition of the parameters to be supported by a YANG Data model for
management of radio links, applicable for centralized, unified, management of radio links, applicable for centralized, unified,
multi-vendor management. multi-vendor management. The use cases involve configuration
management, inventory, status and statistics, performance management,
fault management, troubleshooting and root cause analysis.
Other product specific use cases, addressing e.g. installation, on- Other product specific use cases, addressing e.g. installation, on-
site trouble shooting and fault resolution, are outside the scope of site trouble shooting and fault resolution, are outside the scope of
this framework. If required, these use cases are expected to be 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 of a radio link terminal, the constituent carrier
terminations and when applicable the relationship to IP/Ethernet and terminations and when applicable the relationship to IP/Ethernet and
TDM interfaces. TDM interfaces.
4.1.1. 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 Cancellation) Support for the XPIC (Cross Polarization Interference
feature or not and the maximum modulation supported are two examples Cancellation) feature or not and the maximum modulation supported
on information that could be exchanged. are two examples on information that could be exchanged.
4.1.2. Initial Configuration o Initial Configuration
Initial configuration of a radio link terminal, enough to establish Initial configuration of a radio link terminal, enough to
L1 connectivity to an associated radio link terminal on a device at establish L1 connectivity to an associated radio link terminal on
far end over the hop. It MAY also include configuration of the a device at far end over the hop. It may also include
relationship between a radio link terminal and an associated traffic configuration of the relationship between a radio link terminal
interface, e.g. an Ethernet interface, unless that is given by the and an associated traffic interface, e.g. an Ethernet interface,
equipment configuration. 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 of parameters typically configured for a carrier termination and type
aggregation/bonding or protection configurations expected for a radio of aggregation/bonding or protection configurations expected for a
link terminal. radio link terminal.
4.1.3. Radio link re-configuration and optimization o Radio link re-configuration and optimization
Re-configuration, update or optimization of an existing radio link Re-configuration, update or optimization of an existing radio link
terminal. Output power and modulation for a carrier termination and terminal. Output power and modulation for a carrier termination
protection schemas and activation/de-activation of carriers in a and protection schemas and activation/de-activation of carriers in
radio link terminal are examples on parameters that can be re- a radio link terminal are examples on parameters that can be re-
configured and used for optimization of the performance of a network. configured and used for optimization of the performance of a
network.
4.1.4. Radio link logical configuration o Radio link logical configuration
Radio link terminals comprising a group of carriers are widely used Radio link terminals configured to include a group of carriers are
in microwave technology. There are several kinds of groups: widely used in microwave technology. There are several kinds of
aggregation/bonding, 1+1 protection/redundancy, etc. To avoid groups: aggregation/bonding, 1+1 protection/redundancy, etc. To
configuration on each carrier termination directly, a logical control avoid configuration on each carrier termination directly, a
provides flexible management by mapping a logical configuration to a logical control provides flexible management by mapping a logical
set of physical attributes. This could also be applied in a configuration to a set of physical attributes. This could also be
hierarchical SDN environment where some domain controllers are applied in a hierarchical SDN environment where some domain
located between the SDN controller and the radio link terminal. controllers are located between the SDN controller and the radio
link terminal.
4.2. Inventory 4.2. Inventory
4.2.1. 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
radio interfaces, their constitution and configuration.
4.2.2. Retrieve physical/equipment inventory from device Request from manager and response by device with information about
radio interfaces, their constitution and configuration.
Request from manager about physical and/or equipment inventory o Retrieve physical/equipment inventory from device
associated with the radio link terminals and carrier terminations. Request from manager about physical and/or equipment inventory
associated with the radio link terminals and carrier terminations.
4.3. Status and statistics 4.3. Status and statistics
4.3.1. 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 their status and statistics of configured radio link interfaces and
constituent parts. It's important to report the effective bandwidth their constituent parts. It's important to report the effective
of a radio link since it can be configured to dynamically adjust the bandwidth of a radio link since it can be configured to
modulation based on the current signal conditions. dynamically adjust the modulation based on the current signal
conditions.
4.4. Performance management 4.4. Performance management
4.4.1. Configuration of historical measurements to be performed o Configuration of historical performance measurements
Configuration of historical measurements to be performed on a radio Configuration of historical performance measurements for a radio
link interface and/or its constituent parts is a subset of the link interface and/or its constituent parts. See Section 4.1
configuration use case to be supported. See Section 4.1 above. above.
4.4.2. Collection of historical performance data o Collection of historical performance data
Collection of historical performance data in bulk by the manager is a Collection of historical performance data in bulk by the manager
general use case for a device and not specific to a radio link is a general use case for a device and not specific to a radio
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 same cases required as a complement to the retrieval in bulk as
described above. described above.
4.5. Fault Management 4.5. Fault Management
4.5.1. Configuration of alarm reporting o Configuration of alarm reporting
Configuration of alarm reporting associated specifically with radio Configuration of alarm reporting associated specifically with
interfaces, e.g. configuration of alarm severity, is a subset of the radio interfaces, e.g. configuration of alarm severity, is a
configuration use case to be supported. See Section 4.1 above. subset of the configuration use case to be supported. See
Section 4.1 above.
4.5.2. 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 not specific to a radio events are generic use cases for a device and should be supported
link interface and should be supported accordingly. It's important on a radio link interface. There are however radio-specific
to report signal degradation of the radio link. alarms that are important to report, where signal degradation of
the 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 Information and actions required by a manager/operator to investigate
and understand the underlying issue to a problem in the performance and understand the underlying issue to a problem in the performance
and/or functionality of a radio link terminal and the associated and/or functionality of a radio link terminal and the associated
carrier terminations. carrier terminations.
5. Requirements 5. Requirements
skipping to change at page 13, line 22 skipping to change at page 12, line 22
average transmit power and receive level in dBm. average transmit power and receive 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 of alarm
severity, supported alarms like configuration fault, signal lost, severity, supported alarms like configuration fault, signal lost,
modem fault, 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
existing and established models as well as draft models under models to use in a microwave device to support the use cases and
definition to support the use cases and requirements specified in the requirements specified in the previous chapters. This draft shall
previous chapters. It shall also make a recommendation on how the also make a recommendation on how the gaps not supported should be
gaps not supported should be filled, including the need for filled, including the need for development of new models and
development of new models and evolution of existing models and evolution of existing models and drafts.
drafts.
For microwave radio link functionality work has been initiated (ONF: For microwave radio link functionality work has been initiated (ONF:
Microwave Modeling [ONF-model], IETF: Radio Link Model Microwave Modeling [ONF-model], IETF: Radio Link Model
[I-D.ietf-ccamp-mw-yang]. The analysis is expected to take these [I-D.ietf-ccamp-mw-yang]. The analysis is expected to take these
initiatives into consideration and make a recommendation on how to initiatives into consideration and make a recommendation on how to
make use of them and how to complement them in order to fill the gaps make use of them and how to complement them in order to fill the gaps
identified. identified.
For generic functionality, not specific for radio link, the ambition For generic functionality, not specific for radio link, the ambition
is to refer to existing or emerging models that could be applicable is to refer to existing or emerging models that could be applicable
for all functional areas in a microwave node. 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. Data plane technology specific specific data plane technology. The technology specific content,
properties are acquired in a runtime solution via "filled in" cases acquired in a runtime solution via "filled in" cases of
of specification (LtpSpec etc.). These can be used to augment the specification, augment the CoreModel to provide a forwarding
CoreModel to provide a data plane technology specific representation. technology-specific representation.
IETF Data Model defines an implementation and NETCONF-specific IETF Data Model defines an implementation 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. It is well aligned with the structure configuration and state data. [RFC8343] defines a generic YANG data
of the YANG data models proposed for the different interfaces which model for interface management which doesn't include technology
are all based on [RFC8343]. Furthermore, several YANG data models specific information. To describe the technology specific
have been proposed in the IETF for other transport technologies such information, several YANG data models have been proposed in IETF by
as optical transport; e.g. [RFC8344], augmenting [RFC8343], e.g. [RFC8344]. The YANG data model is a
[I-D.ietf-ccamp-otn-topo-yang], [I-D.ietf-ospf-yang]. In light of popular approach for modeling many packet transport technology
this trend, the IETF data model is becoming a popular approach for interfaces, and it is thereby well positioned to become an industry
modeling most packet transport technology interfaces and it is standard. In light of this trend, [I-D.ietf-ccamp-mw-yang] provides
thereby well positioned to become an industry standard. a YANG data model proposal for radio interfaces, which is well
aligned with the structure of other technology-specific YANG data
models augmenting [RFC8343].
[RFC3444] explains the difference between Information Model(IM) and [RFC3444] explains the difference between Information Model(IM) and
Data Models(DM). IM is to model managed objects at a conceptual Data Models(DM). IM is to model managed objects at a conceptual
level for designers and operators, DM is defined at a lower level and level for designers and operators, while DM is defined at a lower
includes many details for implementers. In addition, the protocol- level and includes many details for implementers. In addition, the
specific details are usually included in DM. Since conceptual models protocol-specific details are usually included in DM. Since
can be implemented in different ways, multiple DMs can be derived conceptual models can be implemented in different ways, multiple DMs
from a single IM. To ensure better interoperability, it is better to can be derived from a single IM.
focus on DM directly.
[RFC8343] describes an interface management model, however it doesn't
include technology specific information, e.g., for radio interface.
[I-D.ietf-ccamp-mw-yang] provides a model proposal for radio
interfaces, which includes support for basic configuration, status
and performance but lacks full support for alarm management and
interface layering, i.e. the connectivity of the transported capacity
(TDM and Ethernet) with other internal technology specific interfaces
in a microwave node.
The recommendation is to use the structure of the IETF: Radio Link
Model [I-D.ietf-ccamp-mw-yang] as the starting point, since it is a
data model providing the wanted alignment with [RFC8343]. For the
definition of the detailed leafs/parameters, the recommendation is to
use the IETF: Radio Link Model and the ONF: Microwave Modeling
[ONF-model] as the basis and to define new ones to cover identified
gaps. The parameters in those models have been defined by both
operators and vendors within the industry and the implementations of
the ONF Model have been tested in the Proof of Concept events in
multi-vendor environments, showing the validity of the approach
proposed in this framework document.
It is also recommended to add the required data nodes to describe the It is recommended to use the structure of the IETF: Radio Link Model
[I-D.ietf-ccamp-mw-yang] as the starting point, since
[I-D.ietf-ccamp-mw-yang] is a data model providing the wanted
alignment with [RFC8343]. To cover the identified gaps, it is
recommended to define new leafs/parameters in
[I-D.ietf-ccamp-mw-yang] while taking reference from [ONF-CIM]. It
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 specific for radio link, the
recommendation is to refer to existing RFCs or emerging drafts recommendation is to refer to existing RFCs or emerging drafts
according to the table in Figure 4 below. New Radio Link Model is according to the table in Figure 4 below. New Radio Link Model is
skipping to change at page 16, line 48 skipping to change at page 15, line 40
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 Microwave Radio Link model and rely on a generic model such
as [I-D.ietf-ccamp-alarm-module] for notifications and alarm as [I-D.ietf-ccamp-alarm-module] 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.
It is furthermore recommended that the Microwave Radio Link YANG Data
Model should be validated by both operators and vendors as part of
the process to make it stable and mature. During the Hackathon in
IETF 99, a project "SDN Applications for microwave radio link via
IETF YANG Data Model" successfully validated this framework and the
YANG data model[I-D.ietf-ccamp-mw-yang]. The project also received
the BEST OVERALL award from the Hackathon.
7. Security Considerations 7. Security Considerations
Security issue concerning the access control to Management interfaces The configuration information may be considered sensitive or
can be generally addressed by authentication techniques providing vulnerable in the network environments. Unauthorized access to
origin verification, integrity and confidentiality. In addition, configuration data nodes can have a negative effect on network
management interfaces can be physically or logically isolated, by operations, e.g., interrupting the ability to forward traffic, or
configuring them to be only accessible out-of-band, through a system increasing the interference level of the network. The status and
that is physically or logically separated from the rest of the inventory reveal some network information that could be very helpful
network infrastructure. In case where management interfaces are to an attacker. A malicious attack to that information may result in
accessible in-band at the client device or within the microwave a loss of customer data. Security issue concerning the access
transport network domain, filtering or firewalling techniques can be control to Management interfaces can be generally addressed by
used to restrict unauthorized in-band traffic. Authentication authentication techniques providing origin verification, integrity
techniques may be additionally used in all cases. and confidentiality. In addition, management interfaces can be
physically or logically isolated, by configuring them to be only
accessible out-of-band, through a system that is physically or
logically separated from the rest of the network infrastructure. In
case where management interfaces are accessible in-band at the client
device or within the microwave transport network domain, filtering or
firewalling techniques can be used to restrict unauthorized in-band
traffic. Authentication techniques may be additionally 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 memo includes no request to IANA.
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>.
[RFC2863] McCloghrie, K. and F. Kastenholz, "The Interfaces Group
MIB", RFC 2863, DOI 10.17487/RFC2863, June 2000,
<https://www.rfc-editor.org/info/rfc2863>.
[RFC3444] Pras, A. and J. Schoenwaelder, "On the Difference between
Information Models and Data Models", RFC 3444,
DOI 10.17487/RFC3444, January 2003,
<https://www.rfc-editor.org/info/rfc3444>.
[RFC6241] Enns, R., Ed., Bjorklund, M., Ed., Schoenwaelder, J., Ed.,
and A. Bierman, Ed., "Network Configuration Protocol
(NETCONF)", RFC 6241, DOI 10.17487/RFC6241, June 2011,
<https://www.rfc-editor.org/info/rfc6241>.
[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>.
[RFC8343] Bjorklund, M., "A YANG Data Model for Interface
Management", RFC 8343, DOI 10.17487/RFC8343, March 2018,
<https://www.rfc-editor.org/info/rfc8343>.
[RFC8344] Bjorklund, M., "A YANG Data Model for IP Management",
RFC 8344, DOI 10.17487/RFC8344, March 2018,
<https://www.rfc-editor.org/info/rfc8344>.
9.2. Informative References 9.2. Informative References
[EN302217-2] [EN302217-2]
"Fixed Radio Systems; Characteristics and requirements for "Fixed Radio Systems; Characteristics and requirements for
point to-point equipment and antennas; Part 2: Digital point to-point equipment and antennas; Part 2: Digital
systems operating in frequency bands from 1 GHz to 86 GHz; systems operating in frequency bands from 1 GHz to 86 GHz;
Harmonised Standard covering the essential requirements of Harmonised Standard covering the essential requirements of
article 3.2 of Directive 2014/53/EU", EN 302 217-2 article 3.2 of Directive 2014/53/EU", EN 302 217-2
V3.1.1 , May 2017. V3.1.1 , May 2017.
skipping to change at page 18, line 43 skipping to change at page 17, line 11
Vallin, S. and M. Bjorklund, "YANG Alarm Module", draft- Vallin, S. and M. Bjorklund, "YANG Alarm Module", draft-
ietf-ccamp-alarm-module-01 (work in progress), February ietf-ccamp-alarm-module-01 (work in progress), February
2018. 2018.
[I-D.ietf-ccamp-mw-yang] [I-D.ietf-ccamp-mw-yang]
Ahlberg, J., Ye, M., Li, X., Spreafico, D., and M. Ahlberg, J., Ye, M., Li, X., Spreafico, D., and M.
Vaupotic, "A YANG Data Model for Microwave Radio Link", Vaupotic, "A YANG Data Model for Microwave Radio Link",
draft-ietf-ccamp-mw-yang-05 (work in progress), March draft-ietf-ccamp-mw-yang-05 (work in progress), March
2018. 2018.
[I-D.ietf-ccamp-otn-topo-yang]
zhenghaomian@huawei.com, z., Fan, Z., Sharma, A., Liu, X.,
Belotti, S., Xu, Y., Wang, L., and O. Dios, "A YANG Data
Model for Optical Transport Network Topology", draft-ietf-
ccamp-otn-topo-yang-02 (work in progress), October 2017.
[I-D.ietf-ospf-yang]
Yeung, D., Qu, Y., Zhang, Z., Chen, I., and A. Lindem,
"Yang Data Model for OSPF Protocol", draft-ietf-ospf-
yang-11 (work in progress), April 2018.
[ONF-CIM] "Core Information Model", version 1.2 , September 2016, [ONF-CIM] "Core Information Model", version 1.2 , September 2016,
<https://www.opennetworking.org/wp- <https://www.opennetworking.org/wp-
content/uploads/2014/10/TR-512_CIM_(CoreModel)_1.2.zip>. content/uploads/2014/10/TR-512_CIM_(CoreModel)_1.2.zip>.
[ONF-model] [ONF-model]
"Microwave Information Model", version 1.0 , December "Microwave Information Model", version 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 [PB-YANG] "IEEE 802.1X and 802.1Q Module Specifications", version
0.4 , May 2015, 0.4 , May 2015,
<http://www.ieee802.org/1/files/public/docs2015/ <http://www.ieee802.org/1/files/public/docs2015/
new-mholness-YANG-8021x-0515-v04.pdf>. new-mholness-YANG-8021x-0515-v04.pdf>.
[RFC2863] McCloghrie, K. and F. Kastenholz, "The Interfaces Group
MIB", RFC 2863, DOI 10.17487/RFC2863, June 2000,
<https://www.rfc-editor.org/info/rfc2863>.
[RFC3444] Pras, A. and J. Schoenwaelder, "On the Difference between
Information Models and Data Models", RFC 3444,
DOI 10.17487/RFC3444, January 2003,
<https://www.rfc-editor.org/info/rfc3444>.
[RFC6241] Enns, R., Ed., Bjorklund, M., Ed., Schoenwaelder, J., Ed.,
and A. Bierman, Ed., "Network Configuration Protocol
(NETCONF)", RFC 6241, DOI 10.17487/RFC6241, June 2011,
<https://www.rfc-editor.org/info/rfc6241>.
[RFC7426] Haleplidis, E., Ed., Pentikousis, K., Ed., Denazis, S.,
Hadi Salim, J., Meyer, D., and O. Koufopavlou, "Software-
Defined Networking (SDN): Layers and Architecture
Terminology", RFC 7426, DOI 10.17487/RFC7426, January
2015, <https://www.rfc-editor.org/info/rfc7426>.
[RFC8343] Bjorklund, M., "A YANG Data Model for Interface
Management", RFC 8343, DOI 10.17487/RFC8343, March 2018,
<https://www.rfc-editor.org/info/rfc8343>.
[RFC8344] Bjorklund, M., "A YANG Data Model for IP Management",
RFC 8344, DOI 10.17487/RFC8344, March 2018,
<https://www.rfc-editor.org/info/rfc8344>.
[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>.
 End of changes. 56 change blocks. 
251 lines changed or deleted 207 lines changed or added

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