draft-ietf-ccamp-mw-yang-10.txt   draft-ietf-ccamp-mw-yang-11.txt 
CCAMP Working Group J. Ahlberg CCAMP Working Group J. Ahlberg
Internet-Draft Ericsson AB Internet-Draft Ericsson AB
Intended status: Standards Track M. Ye Intended status: Standards Track M. Ye
Expires: April 6, 2019 Huawei Technologies Expires: May 10, 2019 Huawei Technologies
X. Li X. Li
NEC Laboratories Europe NEC Laboratories Europe
D. Spreafico D. Spreafico
Nokia - IT Nokia - IT
M. Vaupotic M. Vaupotic
Aviat Networks Aviat Networks
October 03, 2018 November 06, 2018
A YANG Data Model for Microwave Radio Link A YANG Data Model for Microwave Radio Link
draft-ietf-ccamp-mw-yang-10 draft-ietf-ccamp-mw-yang-11
Abstract Abstract
This document defines a YANG data model for control and management of This document defines a YANG data model for control and management of
the radio link interfaces, and their connectivity to packet the radio link interfaces, and their connectivity to packet
(typically Ethernet) interfaces in a microwave/millimeter wave node. (typically Ethernet) interfaces in a microwave/millimeter wave node.
The data nodes for management of the interface protection The data nodes for management of the interface protection
functionality is broken out into a separate and generic YANG data functionality is broken out into a separate and generic YANG data
model in order to make it available also for other interface types. model in order to make it available also for other interface types.
skipping to change at page 1, line 47 skipping to change at page 1, line 47
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 April 6, 2019. This Internet-Draft will expire on May 10, 2019.
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
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 . . . . . . . . . . . . . . . . . . . . . . . . 2 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 2
1.1. Terminology and Definitions . . . . . . . . . . . . . . . 3 1.1. Terminology and Definitions . . . . . . . . . . . . . . . 3
1.2. Tree Structure . . . . . . . . . . . . . . . . . . . . . 4 1.2. Tree Structure . . . . . . . . . . . . . . . . . . . . . 4
2. Requirements Language . . . . . . . . . . . . . . . . . . . . 4 2. Requirements Language . . . . . . . . . . . . . . . . . . . . 4
3. Microwave Radio Link YANG Data Model . . . . . . . . . . . . 4 3. Microwave Radio Link YANG Data Model . . . . . . . . . . . . 5
3.1. YANG Tree . . . . . . . . . . . . . . . . . . . . . . . . 4 3.1. YANG Tree . . . . . . . . . . . . . . . . . . . . . . . . 5
3.2. Explanation of the Microwave Data Model . . . . . . . . . 7 3.2. Explanation of the Microwave Data Model . . . . . . . . . 7
4. Microwave Radio Link YANG Module . . . . . . . . . . . . . . 7 4. Microwave Radio Link YANG Module . . . . . . . . . . . . . . 7
5. Interface Protection YANG Module . . . . . . . . . . . . . . 26 5. Interface Protection YANG Module . . . . . . . . . . . . . . 27
6. Microwave Types YANG Module . . . . . . . . . . . . . . . . . 32 6. Microwave Types YANG Module . . . . . . . . . . . . . . . . . 33
7. Security Considerations . . . . . . . . . . . . . . . . . . . 39 7. Security Considerations . . . . . . . . . . . . . . . . . . . 40
8. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 41 8. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 42
9. References . . . . . . . . . . . . . . . . . . . . . . . . . 42 9. References . . . . . . . . . . . . . . . . . . . . . . . . . 43
9.1. Normative References . . . . . . . . . . . . . . . . . . 42 9.1. Normative References . . . . . . . . . . . . . . . . . . 43
9.2. Informative References . . . . . . . . . . . . . . . . . 43 9.2. Informative References . . . . . . . . . . . . . . . . . 44
Appendix A. Example: 1+0 and 2+0 configuration instances . . . . 45 Appendix A. Example: 1+0 and 2+0 configuration instances . . . . 46
A.1. 1+0 instance . . . . . . . . . . . . . . . . . . . . . . 45 A.1. 1+0 instance . . . . . . . . . . . . . . . . . . . . . . 46
A.2. 2+0 instance . . . . . . . . . . . . . . . . . . . . . . 46 A.2. 2+0 instance . . . . . . . . . . . . . . . . . . . . . . 47
A.3. 2+0 XPIC instance . . . . . . . . . . . . . . . . . . . . 48 A.3. 2+0 XPIC instance . . . . . . . . . . . . . . . . . . . . 49
Appendix B. Contributors . . . . . . . . . . . . . . . . . . . . 50 Appendix B. Contributors . . . . . . . . . . . . . . . . . . . . 50
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 50 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 51
1. Introduction 1. Introduction
This document defines a YANG data model for management and control of This document defines a YANG data model for management and control of
the radio link interface(s) and the relationship to packet (typically the radio link interface(s) and the relationship to packet (typically
Ethernet) and/or TDM interfaces in a microwave/millimeter wave node. Ethernet) and/or TDM interfaces in a microwave/millimeter wave node.
ETSI EN 302 217 series defines the characteristics and requirements ETSI EN 302 217 series defines the characteristics and requirements
of microwave/millimeter wave equipment and antennas. Especially ETSI of microwave/millimeter wave equipment and antennas. Especially ETSI
EN 302 217-2 [EN302217-2] specifies the essential parameters for the EN 302 217-2 [EN302217-2] specifies the essential parameters for the
systems operating from 1.4GHz to 86GHz. The data model includes systems operating from 1.4GHz to 86GHz. The data model includes
configuration and state data according to the new Network Management configuration and state data according to the new Network Management
Datastore Architecture [RFC8342]. Datastore Architecture [RFC8342].
The design of the data model follows the framework for management and The design of the data model follows the framework for management and
control of microwave and millimeter wave interface parameters defined control of microwave and millimeter wave interface parameters defined
in [I-D.ietf-ccamp-microwave-framework]. This framework identifies in [RFC8432]. This framework identifies the need and the scope of
the need and the scope of the YANG data model, the use cases and the YANG data model, the use cases and requirements that the model
requirements that the model needs to support. Moreover, it provides needs to support. Moreover, it provides a detailed gap analysis to
a detailed gap analysis to identify the missing parameters and identify the missing parameters and functionalities of the existing
functionalities of the existing and established models to support the and established models to support the specified use cases and
specified use cases and requirements, and based on that recommends requirements, and based on that recommends how the gaps should be
how the gaps should be filled with the development of the new model. filled with the development of the new model. According to the
According to the conclusion of the gap analysis, the structure of the conclusion of the gap analysis, the structure of the data model is
data model is based on the structure defined in based on the structure defined in
[I-D.ahlberg-ccamp-microwave-radio-link] and it augments [RFC8343] to [I-D.ahlberg-ccamp-microwave-radio-link] and it augments [RFC8343] to
align with the same structure for management of the packet align with the same structure for management of the packet
interfaces. More specifically, the model will include interface interfaces. More specifically, the model will include interface
layering to manage the capacity provided by a radio link terminal for layering to manage the capacity provided by a radio link terminal for
the associated Ethernet and TDM interfaces, using the principles for the associated Ethernet and TDM interfaces, using the principles for
interface layering described in [RFC8343] as a basis. interface layering described in [RFC8343] as a basis.
The data nodes for management of the interface protection The data nodes for management of the interface protection
functionality is broken out into a separate and generic YANG data functionality is broken out into a separate and generic YANG data
module in order to make it available also for other interface types. module in order to make it available also for other interface types.
The designed YANG data model uses established microwave equipment and The designed YANG data model uses established microwave equipment and
radio standards, such as ETSI EN 302 217-2, and the IETF: Radio Link radio standards, such as ETSI EN 302 217-2, and the IETF: Radio Link
Model [I-D.ahlberg-ccamp-microwave-radio-link] and the ONF: Microwave Model [I-D.ahlberg-ccamp-microwave-radio-link] and the ONF: Microwave
Modeling [ONF-model] as the basis for the definition of the detailed Modeling [ONF-model] as the basis for the definition of the detailed
leafs/parameters, and proposes new ones to cover identified gaps leafs/parameters, and proposes new ones to cover identified gaps
which are analyzed in [I-D.ietf-ccamp-microwave-framework]. which are analyzed in [RFC8432].
1.1. Terminology and Definitions 1.1. Terminology and Definitions
The following terms are used in this document: The following terms are used in this document:
Carrier Termination (CT) is an interface for the capacity provided Carrier Termination (CT) is an interface for the capacity provided
over the air by a single carrier. It is typically defined by its over the air by a single carrier. It is typically defined by its
transmitting and receiving frequencies. transmitting and receiving frequencies.
Radio Link Terminal (RLT) is an interface providing packet capacity Radio Link Terminal (RLT) is an interface providing packet capacity
and/or TDM capacity to the associated Ethernet and/or TDM interfaces and/or TDM capacity to the associated Ethernet and/or TDM interfaces
in a node and used for setting up a transport service over a in a node and used for setting up a transport service over a
microwave/millimeter wave link. microwave/millimeter wave link.
The following acronyms are used in this document: The following acronyms are used in this document:
ACM Adaptive Coding Modulation ACM Adaptive Coding Modulation
ATPC Automatic Transmit Power Control ATPC Automatic Transmit Power Control
BBE Background Block Errors
BER Bit Error Ratio
BPSK Binary Phase-Shift Keying BPSK Binary Phase-Shift Keying
CM Coding Modulation CM Coding Modulation
CT Carrier Termination CT Carrier Termination
RLT Radio Link Terminal ES Errored Seconds
RTPC Remote Transmit Power Control
XPIC Cross Polarization Interference Cancellation IF Intermediate Frequency
MIMO Multiple-Input Multiple-Output MIMO Multiple-Input Multiple-Output
RF Radio Frequency
RLT Radio Link Terminal
QAM Quadrature Amplitude Modulation QAM Quadrature Amplitude Modulation
QPSK Quadrature Phase-Shift Keying QPSK Quadrature Phase-Shift Keying
RTPC Remote Transmit Power Control
SES Severely Errored Seconds
TDM Time-Division Multiplexing
UAS Unavailable Seconds
XPIC Cross Polarization Interference Cancellation
1.2. Tree Structure 1.2. Tree Structure
A simplified graphical representation of the data model is used in A simplified graphical representation of the data model is used in
chapter 3.1 of this this document. The meaning of the symbols in chapter 3.1 of this this document. The meaning of the symbols in
these diagrams is defined in [RFC8340]. these diagrams is defined in [RFC8340].
2. Requirements Language 2. Requirements Language
The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
"SHOULD", "SHOULD NOT", "RECOMMENDED", "NOT RECOMMENDED", "MAY", and "SHOULD", "SHOULD NOT", "RECOMMENDED", "NOT RECOMMENDED", "MAY", and
skipping to change at page 7, line 27 skipping to change at page 7, line 41
broadcast-pkts", "out-multicast-pkts", "out-discards", "out-errors" broadcast-pkts", "out-multicast-pkts", "out-discards", "out-errors"
are not within the scope of the microwave radio link domain and are not within the scope of the microwave radio link domain and
therefore not applicable for RLT and CT. therefore not applicable for RLT and CT.
4. Microwave Radio Link YANG Module 4. Microwave Radio Link YANG Module
This module imports typedefs and modules from [RFC6991], [RFC8343] This module imports typedefs and modules from [RFC6991], [RFC8343]
and [RFC7224], and it references [TR102311], [EN302217-1], and [RFC7224], and it references [TR102311], [EN302217-1],
[EN301129], and [G.826]. [EN301129], and [G.826].
<CODE BEGINS> file "ietf-microwave-radio-link@2018-10-03.yang" <CODE BEGINS> file "ietf-microwave-radio-link@2018-11-06.yang"
module ietf-microwave-radio-link { module ietf-microwave-radio-link {
yang-version 1.1; yang-version 1.1;
namespace "urn:ietf:params:xml:ns:yang:ietf-microwave-radio-link"; namespace "urn:ietf:params:xml:ns:yang:ietf-microwave-radio-link";
prefix mrl; prefix mrl;
import ietf-yang-types { import ietf-yang-types {
prefix yang; prefix yang;
reference "RFC 6991"; reference "RFC 6991";
} }
skipping to change at page 8, line 41 skipping to change at page 9, line 8
set forth in Section 4.c of the IETF Trust's Legal Provisions set forth in Section 4.c of the IETF Trust's Legal Provisions
Relating to IETF Documents Relating to IETF Documents
(http://trustee.ietf.org/license-info). (http://trustee.ietf.org/license-info).
This version of this YANG module is part of RFC XXXX; see This version of this YANG module is part of RFC XXXX; see
the RFC itself for full legal notices. the RFC itself for full legal notices.
Copyright (c) 2018 IETF Trust and the persons identified as Copyright (c) 2018 IETF Trust and the persons identified as
authors of the code. All rights reserved."; authors of the code. All rights reserved.";
revision 2018-10-03 { revision 2018-11-06 {
description "Initial revision."; description "Initial revision.";
reference "RFC XXXX: A YANG Data Model for Microwave Radio Link"; reference "RFC XXXX: A YANG Data Model for Microwave Radio Link";
} }
/* /*
* Features * Features
*/ */
feature xpic { feature xpic {
description description
skipping to change at page 12, line 17 skipping to change at page 12, line 32
leaf carrier-id { leaf carrier-id {
type string; type string;
default "A"; default "A";
description description
"ID of the carrier. (e.g. A, B, C or D) "ID of the carrier. (e.g. A, B, C or D)
Used in XPIC & MIMO configurations to check that Used in XPIC & MIMO configurations to check that
the carrier termination is connected to the correct the carrier termination is connected to the correct
far-end carrier termination. Should be the same far-end carrier termination. Should be the same
carrier ID on both sides of the hop. carrier ID on both sides of the hop.
Defaulted when not MIMO or XPIC."; Left as default value when MIMO and XPIC are not in use.";
} }
leaf tx-enabled { leaf tx-enabled {
type boolean; type boolean;
default "false"; default "false";
description description
"Disables (false) or enables (true) the transmitter. "Disables (false) or enables (true) the transmitter.
Only applicable when the interface is enabled Only applicable when the interface is enabled
(interface:enabled = true) otherwise it's always (interface:enabled = true) otherwise it's always
disabled."; disabled.";
skipping to change at page 13, line 23 skipping to change at page 13, line 39
} }
leaf duplex-distance { leaf duplex-distance {
type int32; type int32;
units "kHz"; units "kHz";
description description
"Distance between transmitter and receiver frequencies."; "Distance between transmitter and receiver frequencies.";
} }
mandatory true; mandatory true;
description description
"A choice to configure rx-frequency directly or by computing "A choice to configure rx-frequency directly or by computing
it as tx-frequency subtracted with the configured it as duplex-distance subtracted from tx-frequency." ;
duplex-distance." ;
} }
leaf actual-rx-frequency { leaf actual-rx-frequency {
type uint32; type uint32;
units "kHz"; units "kHz";
config false; config false;
description description
"Computed receiver frequency."; "Computed receiver frequency.";
} }
skipping to change at page 15, line 12 skipping to change at page 15, line 27
mandatory true; mandatory true;
description description
"Selected maximum output power. Minimum output "Selected maximum output power. Minimum output
power is the same as the system capability, power is the same as the system capability,
available-min-output-power."; available-min-output-power.";
reference "ETSI EN 302 217-1"; reference "ETSI EN 302 217-1";
} }
leaf atpc-lower-threshold { leaf atpc-lower-threshold {
type power { type power {
range "-99..-30"; range "-99..-20";
} }
units "dBm"; units "dBm";
must "current() <= ../atpc-upper-threshold"; must "current() <= ../atpc-upper-threshold";
mandatory true; mandatory true;
description description
"The lower threshold for the input power at far-end "The lower threshold for the input power at far-end
used in the ATPC mode."; used in the ATPC mode.";
reference "ETSI EN 302 217-1"; reference "ETSI EN 302 217-1";
} }
leaf atpc-upper-threshold { leaf atpc-upper-threshold {
type power { type power {
range "-99..-30"; range "-99..-20";
} }
units "dBm"; units "dBm";
mandatory true; mandatory true;
description description
"The upper threshold for the input power at far-end "The upper threshold for the input power at far-end
used in the ATPC mode."; used in the ATPC mode.";
reference "ETSI EN 302 217-1"; reference "ETSI EN 302 217-1";
} }
} }
mandatory true; mandatory true;
skipping to change at page 18, line 8 skipping to change at page 18, line 22
reference "ETSI TR 102 311"; reference "ETSI TR 102 311";
} }
container ct-performance-thresholds { container ct-performance-thresholds {
description description
"Specification of thresholds for when alarms should "Specification of thresholds for when alarms should
be sent and cleared for various performance counters."; be sent and cleared for various performance counters.";
leaf received-level-alarm-threshold { leaf received-level-alarm-threshold {
type power { type power {
range "-99..-30"; range "-99..-20";
} }
units "dBm"; units "dBm";
default "-99"; default "-99";
description description
"An alarm is sent when the received power level is "An alarm is sent when the received power level is
below the specified threshold."; below the specified threshold.";
reference "ETSI EN 301 129"; reference "ETSI EN 301 129";
} }
leaf transmitted-level-alarm-threshold { leaf transmitted-level-alarm-threshold {
skipping to change at page 21, line 43 skipping to change at page 22, line 9
container error-performance-statistics { container error-performance-statistics {
config false; config false;
description description
"ITU-T G.826 error performance statistics relevant for "ITU-T G.826 error performance statistics relevant for
a microwave/millimeter wave carrier."; a microwave/millimeter wave carrier.";
leaf bbe { leaf bbe {
type yang:counter32; type yang:counter32;
units "number of block errors"; units "number of block errors";
description description
"Number of Background Block Errors (BBE) during the "Number of Background Block Errors (BBE). A BBE is an
interval. A BBE is an errored block not occurring as errored block not occurring as part of an SES.
part of an SES."; Discontinuities in the value of this counter can occur
at re-initialization of the management system and at
other times as indicated by the value of
'discontinuity-time' in ietf-interfaces.";
reference "ITU-T G.826"; reference "ITU-T G.826";
} }
leaf es { leaf es {
type yang:counter32; type yang:counter32;
units "seconds"; units "seconds";
description description
"Number of Errored Seconds (ES) since last reset. "Number of Errored Seconds (ES).
An ES is a one-second period with one or more errored An ES is a one-second period with one or more errored
blocks or at least one defect."; blocks or at least one defect.
Discontinuities in the value of this counter can occur
at re-initialization of the management system and at
other times as indicated by the value of
'discontinuity-time' in ietf-interfaces.";
reference "ITU-T G.826"; reference "ITU-T G.826";
} }
leaf ses { leaf ses {
type yang:counter32; type yang:counter32;
units "seconds"; units "seconds";
description description
"Number of Severely Errored Seconds (SES) during the "Number of Severely Errored Seconds (SES).
interval. SES is a one-second period which contains SES is a one-second period which contains
equal or more than 30% errored blocks or at least equal or more than 30% errored blocks or at least
one defect. SES is a subset of ES."; one defect. SES is a subset of ES.
Discontinuities in the value of this counter can occur
at re-initialization of the management system and at
other times as indicated by the value of
'discontinuity-time' in ietf-interfaces.";
reference "ITU-T G.826"; reference "ITU-T G.826";
} }
leaf uas { leaf uas {
type yang:counter32; type yang:counter32;
units "seconds"; units "seconds";
description description
"Number of Unavailable Seconds (UAS), that is, the "Number of Unavailable Seconds (UAS), that is, the
total time that the node has been unavailable during total time that the node has been unavailable.
a fixed measurement interval.";
Discontinuities in the value of this counter can occur
at re-initialization of the management system and at
other times as indicated by the value of
'discontinuity-time' in ietf-interfaces.";
reference "ITU-T G.826"; reference "ITU-T G.826";
} }
} }
container radio-performance-statistics { container radio-performance-statistics {
config false; config false;
description description
"ETSI EN 301 129 radio physical interface statistics relevant "ETSI EN 301 129 radio physical interface statistics relevant
for a carrier termination."; for a carrier termination.";
leaf min-rltm { leaf min-rltm {
type power { type power {
range "-99..-20"; range "-99..-20";
} }
units "dBm"; units "dBm";
description description
"Minimum received power level since last reset."; "Minimum received power level.
Discontinuities in the value of this counter can occur
at re-initialization of the management system and at
other times as indicated by the value of
'discontinuity-time' in ietf-interfaces.";
reference "ETSI EN 301 129"; reference "ETSI EN 301 129";
} }
leaf max-rltm { leaf max-rltm {
type power { type power {
range "-99..-20"; range "-99..-20";
} }
units "dBm"; units "dBm";
description description
"Maximum received power level since last reset."; "Maximum received power level.
Discontinuities in the value of this counter can occur
at re-initialization of the management system and at
other times as indicated by the value of
'discontinuity-time' in ietf-interfaces.";
reference "ETSI EN 301 129"; reference "ETSI EN 301 129";
} }
leaf min-tltm { leaf min-tltm {
type power { type power {
range "-99..99"; range "-99..99";
} }
units "dBm"; units "dBm";
description description
"Minimum transmitted power level since last reset."; "Minimum transmitted power level.
Discontinuities in the value of this counter can occur
at re-initialization of the management system and at
other times as indicated by the value of
'discontinuity-time' in ietf-interfaces.";
reference "ETSI EN 301 129"; reference "ETSI EN 301 129";
} }
leaf max-tltm { leaf max-tltm {
type power { type power {
range "-99..99"; range "-99..99";
} }
units "dBm"; units "dBm";
description description
"Maximum transmitted power level since last reset."; "Maximum transmitted power level.
Discontinuities in the value of this counter can occur
at re-initialization of the management system and at
other times as indicated by the value of
'discontinuity-time' in ietf-interfaces.";
reference "ETSI EN 301 129"; reference "ETSI EN 301 129";
} }
} }
} }
/* /*
* Radio Link Protection Groups * Radio Link Protection Groups
*/ */
container radio-link-protection-groups { container radio-link-protection-groups {
skipping to change at page 26, line 24 skipping to change at page 27, line 20
5. Interface Protection YANG Module 5. Interface Protection YANG Module
The data nodes for management of the interface protection The data nodes for management of the interface protection
functionality is broken out from the Microwave Radio Link Module into functionality is broken out from the Microwave Radio Link Module into
a separate and generic YANG data module in order to make it available a separate and generic YANG data module in order to make it available
also for other interface types. also for other interface types.
This module imports modules from [RFC8343], and it references This module imports modules from [RFC8343], and it references
[G.808.1]. [G.808.1].
<CODE BEGINS> file "ietf-interface-protection@2018-10-03.yang" <CODE BEGINS> file "ietf-interface-protection@2018-11-06.yang"
module ietf-interface-protection { module ietf-interface-protection {
yang-version 1.1; yang-version 1.1;
namespace "urn:ietf:params:xml:ns:yang:ietf-interface-protection"; namespace "urn:ietf:params:xml:ns:yang:ietf-interface-protection";
prefix ifprot; prefix ifprot;
import ietf-interfaces { import ietf-interfaces {
prefix if; prefix if;
reference "RFC8343"; reference "RFC8343";
} }
skipping to change at page 27, line 22 skipping to change at page 28, line 18
set forth in Section 4.c of the IETF Trust's Legal Provisions set forth in Section 4.c of the IETF Trust's Legal Provisions
Relating to IETF Documents Relating to IETF Documents
(http://trustee.ietf.org/license-info). (http://trustee.ietf.org/license-info).
This version of this YANG module is part of RFC XXXX; see This version of this YANG module is part of RFC XXXX; see
the RFC itself for full legal notices. the RFC itself for full legal notices.
Copyright (c) 2018 IETF Trust and the persons identified as Copyright (c) 2018 IETF Trust and the persons identified as
authors of the code. All rights reserved."; authors of the code. All rights reserved.";
revision 2018-10-03 { revision 2018-11-06 {
description "Initial revision."; description "Initial revision.";
reference "RFC XXXX: A YANG Data Model for Microwave Radio Link"; reference "RFC XXXX: A YANG Data Model for Microwave Radio Link";
} }
/* /*
* Protection architecture type identities * Protection architecture type identities
*/ */
identity protection-architecture-type { identity protection-architecture-type {
description description
skipping to change at page 32, line 4 skipping to change at page 32, line 47
} }
action clear { action clear {
description description
"An action clears all switch commands."; "An action clears all switch commands.";
reference "ITU-T G.808.1"; reference "ITU-T G.808.1";
} }
} }
} }
} }
<CODE ENDS> <CODE ENDS>
6. Microwave Types YANG Module 6. Microwave Types YANG Module
This module defines a collection of common data types using the YANG This module defines a collection of common data types using the YANG
data modeling language. These common types are designed to be data modeling language. These common types are designed to be
imported by other modules defined in the microwave area. imported by other modules defined in the microwave area.
<CODE BEGINS> file "ietf-microwave-types@2018-10-03.yang" <CODE BEGINS> file "ietf-microwave-types@2018-11-06.yang"
module ietf-microwave-types { module ietf-microwave-types {
yang-version 1.1; yang-version 1.1;
namespace "urn:ietf:params:xml:ns:yang:ietf-microwave-types"; namespace "urn:ietf:params:xml:ns:yang:ietf-microwave-types";
prefix mw-types; prefix mw-types;
import iana-if-type { import iana-if-type {
prefix ianaift; prefix ianaift;
reference "RFC 7224"; reference "RFC 7224";
} }
skipping to change at page 33, line 4 skipping to change at page 33, line 48
Copyright (c) 2018 IETF Trust and the persons identified as Copyright (c) 2018 IETF Trust and the persons identified as
authors of the code. All rights reserved. authors of the code. All rights reserved.
Redistribution and use in source and binary forms, with or Redistribution and use in source and binary forms, with or
without modification, is permitted pursuant to, and subject without modification, is permitted pursuant to, and subject
to the license terms contained in, the Simplified BSD License to the license terms contained in, the Simplified BSD License
set forth in Section 4.c of the IETF Trust's Legal Provisions set forth in Section 4.c of the IETF Trust's Legal Provisions
Relating to IETF Documents Relating to IETF Documents
(http://trustee.ietf.org/license-info). (http://trustee.ietf.org/license-info).
This version of this YANG module is part of RFC XXXX; see This version of this YANG module is part of RFC XXXX; see
the RFC itself for full legal notices. the RFC itself for full legal notices.
Copyright (c) 2018 IETF Trust and the persons identified as Copyright (c) 2018 IETF Trust and the persons identified as
authors of the code. All rights reserved."; authors of the code. All rights reserved.";
revision 2018-10-03 { revision 2018-11-06 {
description "Initial revision."; description "Initial revision.";
reference "RFC XXXX: A YANG Data Model for Microwave Radio Link"; reference "RFC XXXX: A YANG Data Model for Microwave Radio Link";
} }
/* /*
* Interface identities * Interface identities
*/ */
identity radio-link-terminal { identity radio-link-terminal {
base ianaift:iana-interface-type; base ianaift:iana-interface-type;
skipping to change at page 39, line 35 skipping to change at page 40, line 31
base tdm-type; base tdm-type;
description description
"STM-1 connection, 155.52 Mbit/s."; "STM-1 connection, 155.52 Mbit/s.";
} }
} }
<CODE ENDS> <CODE ENDS>
7. Security Considerations 7. Security Considerations
The YANG module specified in this document defines a schema for data The YANG modules specified in this document define schemas for data
that is designed to be accessed via network management protocols such that is designed to be accessed via network management protocols such
as NETCONF [RFC6241] or RESTCONF [RFC8040]. The lowest NETCONF layer as NETCONF [RFC6241] or RESTCONF [RFC8040]. The lowest NETCONF layer
is the secure transport layer, and the mandatory-to-implement secure is the secure transport layer, and the mandatory-to-implement secure
transport is Secure Shell (SSH) [RFC6242]. The lowest RESTCONF layer transport is Secure Shell (SSH) [RFC6242]. The lowest RESTCONF layer
is HTTPS, and the mandatory-to-implement secure transport is TLS is HTTPS, and the mandatory-to-implement secure transport is TLS
[RFC8446]. [RFC8446].
The NETCONF access control model [RFC8341] provides the means to The NETCONF access control model [RFC8341] provides the means to
restrict access for particular NETCONF or RESTCONF users to a restrict access for particular NETCONF or RESTCONF users to a
preconfigured subset of all available NETCONF or RESTCONF protocol preconfigured subset of all available NETCONF or RESTCONF protocol
operations and content. operations and content.
There are a number of data nodes defined in this YANG module that are There are a number of data nodes defined in these YANG modules that
writable/creatable/deletable (i.e., config true, which is the are writable/creatable/deletable (i.e., config true, which is the
default). These data nodes may be considered sensitive or vulnerable default). These data nodes may be considered sensitive or vulnerable
in some network environments. Write operations (e.g., edit-config) in some network environments. Write operations (e.g., edit-config)
to these data nodes without proper protection can have a negative to these data nodes without proper protection can have a negative
effect on network operations. These are the subtrees and data nodes effect on network operations. These are the subtrees and data nodes
and their sensitivity/vulnerability: and their sensitivity/vulnerability:
Interfaces of type radio-link-terminal: Interfaces of type radio-link-terminal:
/if:interfaces/if:interface/mode,
/if:interfaces/if:interface/carrier-terminations, /if:interfaces/if:interface/carrier-terminations,
/if:interfaces/if:interface/rlp-groups, /if:interfaces/if:interface/rlp-groups,
/if:interfaces/if:interface/xpic-pairs, /if:interfaces/if:interface/xpic-pairs,
/if:interfaces/if:interface/mimo-groups, and /if:interfaces/if:interface/mimo-groups, and
/if:interfaces/if:interface/tdm-connections: /if:interfaces/if:interface/tdm-connections:
These lists represent the configuration of the radio-link-terminal These data nodes represent the configuration of the radio-link-
and it need to match the configuration of the radio-link-terminal on terminal and they need to match the configuration of the radio-link-
the other side of the radio link. Unauthorized access to these data terminal on the other side of the radio link. Unauthorized access to
nodes could interrupt the ability to forward traffic. these data nodes could interrupt the ability to forward traffic.
Interfaces of type carrier-termination: Interfaces of type carrier-termination:
/if:interfaces/if:interface/carrier-id, /if:interfaces/if:interface/carrier-id,
/if:interfaces/if:interface/tx-enabled, /if:interfaces/if:interface/tx-enabled,
/if:interfaces/if:interface/tx-frequency, /if:interfaces/if:interface/tx-frequency,
/if:interfaces/if:interface/rx-frequency, /if:interfaces/if:interface/rx-frequency,
/if:interfaces/if:interface/duplex-distance, /if:interfaces/if:interface/duplex-distance,
/if:interfaces/if:interface/channel-separation, /if:interfaces/if:interface/channel-separation,
/if:interfaces/if:interface/rtpc/maximum-nominal-power, /if:interfaces/if:interface/rtpc/maximum-nominal-power,
/if:interfaces/if:interface/atpc/maximum-nominal-power, /if:interfaces/if:interface/atpc/maximum-nominal-power,
/if:interfaces/if:interface/atpc/atpc-lower-threshold, /if:interfaces/if:interface/atpc/atpc-lower-threshold,
/if:interfaces/if:interface/atpc/atpc-upper-threshold, /if:interfaces/if:interface/atpc/atpc-upper-threshold,
/if:interfaces/if:interface/single/selected-cm, /if:interfaces/if:interface/single/selected-cm,
/if:interfaces/if:interface/adaptive/selected-min-acm, /if:interfaces/if:interface/adaptive/selected-min-acm,
/if:interfaces/if:interface/adaptive/selected-max-acm, /if:interfaces/if:interface/adaptive/selected-max-acm,
/if:interfaces/if:interface/if-loop, and /if:interfaces/if:interface/if-loop, and
/if:interfaces/if:interface/rf-loop: /if:interfaces/if:interface/rf-loop:
These data nodes represent the configuration of the carrier- These data nodes represent the configuration of the carrier-
termination and it need to match the configuration of the carrier- termination and they need to match the configuration of the carrier-
termination on the other side of the carrier. Unauthorized access to termination on the other side of the carrier. Unauthorized access to
these data nodes could interrupt the ability to forward traffic. these data nodes could interrupt the ability to forward traffic.
Radio link protection: Radio link protection:
/radio-link-protection-groups/protection-group: /radio-link-protection-groups/protection-group:
This list of protection groups and the constituent data nodes This data node represents the configuration of the protection of
represents the configuration of the protection of carrier carrier terminations. Unauthorized access to this data node could
terminations. Unauthorized access to these data nodes could
interrupt the ability to forward traffic or remove the ability to interrupt the ability to forward traffic or remove the ability to
perform a necessary protection switch. perform a necessary protection switch.
XPIC: XPIC:
/xpic-pairs: /xpic-pairs:
This list represents the XPIC configuration of a pair carriers. This data node represents the XPIC configuration of a pair carriers.
Unauthorized access to these data nodes could interrupt the ability Unauthorized access to this data node could interrupt the ability to
to forward traffic. forward traffic.
MIMO: MIMO:
/mimo-groups: /mimo-groups:
This list represents the MIMO configuration of multiple carriers. This data node represents the MIMO configuration of multiple
Unauthorized access to these data nodes could interrupt the ability carriers. Unauthorized access to this data node could interrupt the
to forward traffic. ability to forward traffic.
The security considerations of [RFC8343] also apply to this document. The security considerations of [RFC8343] also apply to this document.
8. IANA Considerations 8. IANA Considerations
It is proposed that IANA should assign new URIs from the "IETF XML It is proposed that IANA should assign new URIs from the "IETF XML
Registry" [RFC3688] as follows: Registry" [RFC3688] as follows:
URI: urn:ietf:params:xml:ns:yang:ietf-microwave-radio-link URI: urn:ietf:params:xml:ns:yang:ietf-microwave-radio-link
Registrant Contact: The IESG Registrant Contact: The IESG
skipping to change at page 44, line 42 skipping to change at page 45, line 30
targets End-to-end error performance parameters and targets End-to-end error performance parameters and
objectives for international, constant bit-rate digital objectives for international, constant bit-rate digital
paths and connections", ITU-T Rec. G.826 , December 2002. paths and connections", ITU-T Rec. G.826 , December 2002.
[I-D.ahlberg-ccamp-microwave-radio-link] [I-D.ahlberg-ccamp-microwave-radio-link]
Ahlberg, J., Carlson, J., Lund, H., Olausson, T., Ye, M., Ahlberg, J., Carlson, J., Lund, H., Olausson, T., Ye, M.,
and M. Vaupotic, "Microwave Radio Link YANG Data Models", and M. Vaupotic, "Microwave Radio Link YANG Data Models",
draft-ahlberg-ccamp-microwave-radio-link-01 (work in draft-ahlberg-ccamp-microwave-radio-link-01 (work in
progress), May 2016. progress), May 2016.
[I-D.ietf-ccamp-microwave-framework]
Ahlberg, J., Ye, M., Li, X., Contreras, L., and C.
Bernardos, "A framework for Management and Control of
microwave and millimeter wave interface parameters",
draft-ietf-ccamp-microwave-framework-07 (work in
progress), June 2018.
[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>.
[RFC8340] Bjorklund, M. and L. Berger, Ed., "YANG Tree Diagrams", [RFC8340] Bjorklund, M. and L. Berger, Ed., "YANG Tree Diagrams",
BCP 215, RFC 8340, DOI 10.17487/RFC8340, March 2018, BCP 215, RFC 8340, DOI 10.17487/RFC8340, March 2018,
<https://www.rfc-editor.org/info/rfc8340>. <https://www.rfc-editor.org/info/rfc8340>.
[RFC8342] Bjorklund, M., Schoenwaelder, J., Shafer, P., Watsen, K., [RFC8342] Bjorklund, M., Schoenwaelder, J., Shafer, P., Watsen, K.,
and R. Wilton, "Network Management Datastore Architecture and R. Wilton, "Network Management Datastore Architecture
(NMDA)", RFC 8342, DOI 10.17487/RFC8342, March 2018, (NMDA)", RFC 8342, DOI 10.17487/RFC8342, March 2018,
<https://www.rfc-editor.org/info/rfc8342>. <https://www.rfc-editor.org/info/rfc8342>.
[RFC8432] Ahlberg, J., Ed., Ye, M., Ed., Li, X., Contreras, LM., and
CJ. Bernardos, "A Framework for Management and Control of
Microwave and Millimeter Wave Interface Parameters",
RFC 8432, DOI 10.17487/RFC8432, October 2018,
<https://www.rfc-editor.org/info/rfc8432>.
[TR102311] [TR102311]
"Fixed Radio Systems; Point-to-point equipment; Specific "Fixed Radio Systems; Point-to-point equipment; Specific
aspects of the spatial frequency reuse method", ETSI TR aspects of the spatial frequency reuse method", ETSI TR
102 311 V1.2.1 , November 2015. 102 311 V1.2.1 , November 2015.
Appendix A. Example: 1+0 and 2+0 configuration instances Appendix A. Example: 1+0 and 2+0 configuration instances
This section gives simple examples of 1+0 and 2+0 instance using the This section gives simple examples of 1+0 and 2+0 instance using the
YANG module defined in this draft. The examples are not intended as YANG module defined in this draft. The examples are not intended as
a complete module for 1+0 and 2+0 configuration. a complete module for 1+0 and 2+0 configuration.
A.1. 1+0 instance A.1. 1+0 instance
/--------- Radio Link ---------\ /--------- Radio Link ---------\
Near End Far End Near End Far End
+---------------+ +---------------+ +---------------+ +---------------+
| Radio Link | | Radio Link | | Radio Link | | Radio Link |
| Terminal - A | | Terminal - B | | Terminal A | | Terminal B |
| | | | | | | |
| | | | | | | |
| +-----------+ | | +-----------+ | | +-----------+ | | +-----------+ |
| | | | Carrier A | | | | | | | | Carrier A | | | |
| | Carrier | |<--------->| | Carrier | | | | Carrier | |<--------->| | Carrier | |
| |Termination| | | |Termination| | | |Termination| | | |Termination| |
| | -1 | | | | -1 | | | | 1 | | | | 1 | |
| +-----------+ | | +-----------+ | | +-----------+ | | +-----------+ |
| | | | | | | |
| | | | | | | |
+---------------+ +---------------+ +---------------+ +---------------+
\--- Microwave Node ---/ \--- Microwave Node ---/ \--- Microwave Node ---/ \--- Microwave Node ---/
Figure A-1 1+0 example Figure A-1 1+0 example
Figure A-1 shows a 1+0 example. The following instance Figure A-1 shows a 1+0 example. The following instance
shows the 1+0 configuration of Near End node. shows the 1+0 configuration of Near End node.
skipping to change at page 47, line 8 skipping to change at page 47, line 38
A.2. 2+0 instance A.2. 2+0 instance
Figure A-2 shows a 2+0 example. Figure A-2 shows a 2+0 example.
/--------- Radio Link ---------\ /--------- Radio Link ---------\
Near End Far End Near End Far End
+---------------+ +---------------+ +---------------+ +---------------+
| Radio Link | | Radio Link | | Radio Link | | Radio Link |
| Terminal -A | | Terminal -B | | Terminal A | | Terminal B |
| | | | | | | |
| | | | | | | |
| +-----------+ | | +-----------+ | | +-----------+ | | +-----------+ |
| | | | Carrier A | | | | | | | | Carrier A | | | |
| | Carrier | |<--------->| | Carrier | | | | Carrier | |<--------->| | Carrier | |
| |Termination| | | |Termination| | | |Termination| | | |Termination| |
| | -1 | | | | -1 | | | | 1 | | | | 1 | |
| +-----------+ | | +-----------+ | | +-----------+ | | +-----------+ |
| | | | | | | |
| +-----------+ | | +-----------+ | | +-----------+ | | +-----------+ |
| | | | Carrier B | | | | | | | | Carrier B | | | |
| | Carrier | |<--------->| | Carrier | | | | Carrier | |<--------->| | Carrier | |
| |Termination| | | |Termination| | | |Termination| | | |Termination| |
| | -2 | | | | -2 | | | | 2 | | | | 2 | |
| +-----------+ | | +-----------+ | | +-----------+ | | +-----------+ |
| | | | | | | |
+---------------+ +---------------+ +---------------+ +---------------+
\--- Microwave Node ---/ \--- Microwave Node ---/ \--- Microwave Node ---/ \--- Microwave Node ---/
Figure A-2 2+0 example Figure A-2 2+0 example
The following instance shows the 2+0 configuration of The following instance shows the 2+0 configuration of
Near End node. Near End node.
 End of changes. 53 change blocks. 
88 lines changed or deleted 134 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/