draft-ietf-ccamp-mw-yang-05.txt   draft-ietf-ccamp-mw-yang-06.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: October 1, 2018 Huawei Technologies Expires: December 21, 2018 Huawei Technologies
X. Li X. Li
NEC Laboratories Europe GmbH NEC Laboratories Europe
D. Spreafico D. Spreafico
Nokia - IT Nokia - IT
M. Vaupotic M. Vaupotic
Aviat Networks Aviat Networks
March 30, 2018 June 19, 2018
A YANG Data Model for Microwave Radio Link A YANG Data Model for Microwave Radio Link
draft-ietf-ccamp-mw-yang-05 draft-ietf-ccamp-mw-yang-06
Abstract Abstract
This document defines a YANG data model for control and management This document defines a YANG data model for control and management of
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.
RFC Ed. Note
// RFC Ed.: replace all XXXX throughout the document with actual RFC
numbers and remove this note
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 http://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 October 1, 2018.
// RFC Ed.: replace all XXXX throughout the document with actual This Internet-Draft will expire on December 21, 2018.
// RFC numbers and remove this note
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
(http://trustee.ietf.org/license-info) in effect on the date of (https://trustee.ietf.org/license-info) in effect on the date of
publication of this document. Please review these documents publication of this document. Please review these documents
carefully, as they describe your rights and restrictions with respect carefully, as they describe your rights and restrictions with respect
to this document. Code Components extracted from this document must to this document. Code Components extracted from this document must
include Simplified BSD License text as described in Section 4.e of include Simplified BSD License text as described in Section 4.e of
the Trust Legal Provisions and are provided without warranty as the Trust Legal Provisions and are provided without warranty as
described in the Simplified BSD License. described in the Simplified BSD License.
Table of Contents Table of Contents
1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 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 . . . . . . . . . . . . 4
3.1. YANG Tree . . . . . . . . . . . . . . . . . . . . . . . . 4 3.1. YANG Tree . . . . . . . . . . . . . . . . . . . . . . . . 4
3.2. Explanation of the Microwave Data Model . . . . . . . . . 6 3.2. Explanation of the Microwave Data Model . . . . . . . . . 7
4. Microwave Radio Link YANG Module . . . . . . . . . . . . . . 6 4. Microwave Radio Link YANG Module . . . . . . . . . . . . . . 7
5. Interface Protection YANG Module . . . . . . . . . . . . . . 24 5. Interface Protection YANG Module . . . . . . . . . . . . . . 26
6. Microwave Types YANG Module . . . . . . . . . . . . . . . . . 31 6. Microwave Types YANG Module . . . . . . . . . . . . . . . . . 32
7. Security Considerations . . . . . . . . . . . . . . . . . . . 38 7. Security Considerations . . . . . . . . . . . . . . . . . . . 39
8. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 40 8. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 41
9. References . . . . . . . . . . . . . . . . . . . . . . . . . 40 9. References . . . . . . . . . . . . . . . . . . . . . . . . . 42
9.1. Normative References . . . . . . . . . . . . . . . . . . 40 9.1. Normative References . . . . . . . . . . . . . . . . . . 42
9.2. Informative References . . . . . . . . . . . . . . . . . 42 9.2. Informative References . . . . . . . . . . . . . . . . . 44
Appendix A. Example: 1+0 and 2+0 configuration instances. . . . . 43 Appendix A. Example: 1+0 and 2+0 configuration instances . . . . 44
Appendix B. Contributors. . . . . . . . . . . . . . . . . . . . . 46 Appendix B. Contributors . . . . . . . . . . . . . . . . . . . . 49
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 46 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 50
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 EN 302 217-2 [EN302217-2] specifies the essential parameters for the
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 [I-D.ietf-ccamp-microwave-framework]. This framework identifies
the need and the scope of the YANG data model, the use cases and the need and the scope of the YANG data model, the use cases and
requirements that the model needs to support. Moreover, it provides requirements that the model needs to support. Moreover, it provides
a detailed gap analysis to identify the missing parameters and a detailed gap analysis to identify the missing parameters and
functionalities of the existing and established models to support the functionalities of the existing and established models to support the
specified use cases and requirements, and based on that recommends specified use cases and requirements, and based on that recommends
how the gaps should be filled with the development of the new model. how the gaps should be filled with the development of the new model.
According to the conclusion of the gap analysis, the structure of the According to the conclusion of the gap analysis, the structure of the
data model is based on the structure defined in data model is based on the structure defined in
[I-D.ahlberg-ccamp-microwave-radio-link] and it augments [RFC8343] [I-D.ahlberg-ccamp-microwave-radio-link] and it augments [RFC8343] to
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 The designed YANG data model uses established microwave equipment and
and radio standards, such as ETSI EN 302 217-2, and the IETF: Radio radio standards, such as ETSI EN 302 217-2, and the IETF: Radio Link
Link Model[I-D.ahlberg-ccamp-microwave-radio-link] and the ONF: Model [I-D.ahlberg-ccamp-microwave-radio-link] and the ONF: Microwave
Microwave Modeling[ONF-model] as the basis for the definition of the Modeling [ONF-model] as the basis for the definition of the detailed
detailed leafs/parameters, and proposes new ones to cover identified leafs/parameters, and proposes new ones to cover identified gaps
gaps which are analyzed in[I-D.ietf-ccamp-microwave-framework]. which are analyzed in [I-D.ietf-ccamp-microwave-framework].
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
skipping to change at page 4, line 18 skipping to change at page 4, line 22
RTPC Remote Transmit Power Control RTPC Remote Transmit Power Control
XPIC Cross Polarization Interference Cancellation XPIC Cross Polarization Interference Cancellation
MIMO Multiple-Input Multiple-Output MIMO Multiple-Input Multiple-Output
QAM Quadrature Amplitude Modulation QAM Quadrature Amplitude Modulation
QPSK Quadrature Phase-Shift Keying QPSK Quadrature Phase-Shift Keying
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
"OPTIONAL" in this document are to be interpreted as described in "OPTIONAL" in this document are to be interpreted as described in BCP
BCP 14 [RFC2119] [RFC8174] when, and only when, they appear in all 14 [RFC2119] [RFC8174] when, and only when, they appear in all
capitals, as shown here. capitals, as shown here.
3. Microwave Radio Link YANG Data Model 3. Microwave Radio Link YANG Data Model
3.1. YANG Tree 3.1. YANG Tree
module: ietf-microwave-radio-link module: ietf-microwave-radio-link
+--rw radio-link-protection-groups +--rw radio-link-protection-groups
| +--rw protection-group* [name] | +--rw protection-group* [name]
| +--rw name string | +--rw name string
| +--rw architecture-type? identityref | +--rw protection-architecture-type? identityref
| +--rw members* if:interface-ref | +--rw members* if:interface-ref
| +--rw operation-type? enumeration | +--rw operation-type? enumeration
| +--rw working-entity* if:interface-ref | +--rw working-entity* if:interface-ref
| +--rw revertive-wait-to-restore? uint16 | +--rw revertive-wait-to-restore? uint16
| +--rw hold-off-timer? uint16 | +--rw hold-off-timer? uint16
| +--rw status? identityref | +--ro status? identityref
| +---x external-commands | +---x manual-switch-working
| +---w input | +---x manual-switch-protection
| +---w external-command? identityref | +---x forced-switch
+--rw xpic-pairs {xpic}? | +---x lockout-of-protection
| +--rw xpic-pair* [name] | +---x freeze
| +--rw name string | +---x exercise
| +--rw enabled? boolean | +---x clear
| +--rw members* if:interface-ref +--rw xpic-pairs {xpic}?
+--rw mimo-groups {mimo}? | +--rw xpic-pair* [name]
+--rw mimo-group* [name] | +--rw name string
+--rw name string | +--rw enabled? boolean
+--rw enabled? boolean | +--rw members* if:interface-ref
+--rw members* if:interface-ref +--rw mimo-groups {mimo}?
+--rw mimo-group* [name]
+--rw name string
+--rw enabled? boolean
+--rw members* if:interface-ref
augment /if:interfaces/if:interface: augment /if:interfaces/if:interface:
+--rw id? string +--rw id? string
+--rw mode identityref +--rw mode identityref
+--rw carrier-terminations* if:interface-ref +--rw carrier-terminations* if:interface-ref
+--rw rlp-groups* +--rw rlp-groups*
| -> /radio-link-protection-groups/protection-group/name | -> /radio-link-protection-groups/protection-group/name
+--rw xpic-pairs* -> /xpic-pairs/xpic-pair/name +--rw xpic-pairs* -> /xpic-pairs/xpic-pair/name
| {xpic}? | {xpic}?
+--rw mimo-groups* -> /mimo-groups/mimo-group/name +--rw mimo-groups* -> /mimo-groups/mimo-group/name
| {mimo}? | {mimo}?
+--rw tdm-connections* [tdm-type] {tdm}? +--rw tdm-connections* [tdm-type] {tdm}?
+--rw tdm-type identityref +--rw tdm-type identityref
+--rw tdm-connections uint16 +--rw tdm-connections uint16
augment /if:interfaces/if:interface: augment /if:interfaces/if:interface:
+--rw carrier-id? string +--rw carrier-id? string
+--rw tx-enabled? boolean +--rw tx-enabled? boolean
+--ro tx-oper-status? enumeration +--ro tx-oper-status? enumeration
+--rw tx-frequency uint32 +--rw tx-frequency uint32
+--rw rx-frequency? uint32 +--rw (freq-or-distance)
+--rw duplex-distance? uint32 | +--:(rx-frequency)
| | +--rw rx-frequency? uint32
| +--:(duplex-distance)
| +--rw duplex-distance? int32
+--ro actual-rx-frequency? uint32
+--ro actual-duplex-distance? uint32
+--rw channel-separation uint32 +--rw channel-separation uint32
+--rw polarization? enumeration +--rw polarization? enumeration
+--rw power-mode enumeration +--rw (power-mode)
+--rw maximum-nominal-power power | +--:(rtpc)
+--rw atpc-lower-threshold power | | +--rw rtpc
+--rw atpc-upper-threshold power | | +--rw maximum-nominal-power power
| +--:(atpc)
| +--rw atpc
| +--rw maximum-nominal-power power
| +--rw atpc-lower-threshold power
| +--rw atpc-upper-threshold power
+--ro actual-transmitted-level? power +--ro actual-transmitted-level? power
+--ro actual-received-level? power +--ro actual-received-level? power
+--rw coding-modulation-mode enumeration +--rw (coding-modulation-mode)
+--rw selected-cm identityref | +--:(single)
+--rw selected-min-acm identityref | | +--rw single
+--rw selected-max-acm identityref | | +--rw selected-cm identityref
| +--:(adaptive)
| +--rw adaptive
| +--rw selected-min-acm identityref
| +--rw selected-max-acm identityref
+--ro actual-tx-cm? identityref +--ro actual-tx-cm? identityref
+--ro actual-snir? decimal64 +--ro actual-snir? decimal64
+--ro actual-xpi? decimal64 {xpic}? +--ro actual-xpi? decimal64 {xpic}?
+--rw ct-performance-thresholds +--rw ct-performance-thresholds
| +--rw received-level-alarm-threshold? power | +--rw received-level-alarm-threshold? power
| +--rw transmitted-level-alarm-threshold? power | +--rw transmitted-level-alarm-threshold? power
| +--rw ber-alarm-threshold? enumeration | +--rw ber-alarm-threshold? enumeration
+--rw if-loop? enumeration +--rw if-loop? enumeration
+--rw rf-loop? enumeration +--rw rf-loop? enumeration
+--ro capabilities +--ro capabilities
skipping to change at page 6, line 42 skipping to change at page 7, line 23
The packet related measurements "in-octets", "in-unicast-pkts", "in- The packet related measurements "in-octets", "in-unicast-pkts", "in-
broadcast-pkts", "in-multicast-pkts", "in-discards", "in-errors", broadcast-pkts", "in-multicast-pkts", "in-discards", "in-errors",
"in-unknown-protos", "out-octets", "out-unicast-pkts", "out- "in-unknown-protos", "out-octets", "out-unicast-pkts", "out-
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], This module imports typedefs and modules from [RFC6991], [RFC8343]
[RFC8343] and [RFC7224], and it references [TR102311], and [RFC7224], and it references [TR102311], [EN302217-1],
[EN302217-1], [EN301129], and [G.826]. [EN301129], and [G.826].
<CODE BEGINS> file "ietf-microwave-radio-link@2018-03-30.yang" <CODE BEGINS> file "ietf-microwave-radio-link@2018-06-22.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";
} }
import ietf-interfaces { import ietf-interfaces {
prefix if; prefix if;
reference "RFC 8343"; reference "RFC 8343";
} }
skipping to change at page 7, line 22 skipping to change at page 8, line 4
} }
import ietf-interface-protection { import ietf-interface-protection {
prefix ifprot; prefix ifprot;
reference "RFC XXXX"; reference "RFC XXXX";
} }
import ietf-microwave-types { import ietf-microwave-types {
prefix mw-types; prefix mw-types;
reference "RFC XXXX"; reference "RFC XXXX";
} }
organization organization
"Internet Engineering Task Force (IETF) CCAMP WG"; "Internet Engineering Task Force (IETF) CCAMP WG";
contact contact
"WG List: <mailto:ccamp@ietf.org> "WG List: <mailto:ccamp@ietf.org>
ID-draft editors: ID-draft editors:
// RFC Ed.: replace ID-draft editors with Editors and remove // RFC Ed.: replace ID-draft editors with Editors and remove
// this note // this note
Jonas Ahlberg (jonas.ahlberg@ericsson.com); Jonas Ahlberg (jonas.ahlberg@ericsson.com);
Min Ye (amy.yemin@huawei.com); Min Ye (amy.yemin@huawei.com);
Xi Li (Xi.Li@neclab.eu); Xi Li (Xi.Li@neclab.eu);
Daniela Spreafico (daniela.spreafico@nokia.com) Daniela Spreafico (daniela.spreafico@nokia.com)
Marko Vaupotic (Marko.Vaupotic@aviatnet.com)"; Marko Vaupotic (Marko.Vaupotic@aviatnet.com)";
skipping to change at page 8, line 8 skipping to change at page 8, line 41
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-03-30 { revision 2018-06-22 {
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 8, line 51 skipping to change at page 9, line 36
} }
description description
"Type used for power values, selected and measured."; "Type used for power values, selected and measured.";
} }
/* /*
* Radio Link Terminal (RLT) * Radio Link Terminal (RLT)
*/ */
augment "/if:interfaces/if:interface" { augment "/if:interfaces/if:interface" {
when "if:type = 'mw-types:radio-link-terminal'"; when "derived-from-or-self(if:type,"
+ "'mw-types:radio-link-terminal')";
description description
"Addition of data nodes for radio link terminal to "Addition of data nodes for radio link terminal to
the standard Interface data model, for interfaces of the standard Interface data model, for interfaces of
the type 'radio-link-terminal'."; the type 'radio-link-terminal'.";
leaf id { leaf id {
type string; type string;
default "";
description description
"ID of the radio link terminal. Used by far-end when "Descriptive identity of the radio link terminal used by
checking that it's connected to the correct RLT."; far-end RLT to check that it's connected to the correct
near-end RLT. Does not need to be configured if this check
is not used.";
} }
leaf mode { leaf mode {
type identityref { type identityref {
base mw-types:rlt-mode; base mw-types:rlt-mode;
} }
mandatory true; mandatory true;
description description
"A description of the mode in which the radio link "A description of the mode in which the radio link
terminal is configured. The format is X plus Y. terminal is configured. The format is X plus Y.
X represent the number of bonded carrier terminations. X represent the number of bonded carrier terminations.
Y represent the number of protecting carrier Y represent the number of protecting carrier
terminations."; terminations.";
} }
leaf-list carrier-terminations { leaf-list carrier-terminations {
type if:interface-ref; type if:interface-ref;
must "/if:interfaces/if:interface[if:name = current()]" must "derived-from-or-self(/if:interfaces/if:interface"
+ "/if:type = 'mw-types:carrier-termination'" { + "[if:name = current()]"
+ "/if:type, 'mw-types:carrier-termination')" {
description description
"The type of interface must be "The type of interface must be
'carrier-termination'."; 'carrier-termination'.";
} }
min-elements 1; min-elements 1;
description description
"A list of references to carrier terminations "A list of references to carrier terminations
included in the radio link terminal."; included in the radio link terminal.";
} }
skipping to change at page 10, line 27 skipping to change at page 11, line 24
"A reference to the MIMO group used in this "A reference to the MIMO group used in this
radio link terminal. One group can be used by more radio link terminal. One group can be used by more
than one terminal."; than one terminal.";
reference "ETSI TR 102 311"; reference "ETSI TR 102 311";
} }
list tdm-connections { list tdm-connections {
if-feature tdm; if-feature tdm;
key "tdm-type"; key "tdm-type";
description description
"A list stating the number of active TDM connections "A list stating the number of active TDM connections
of a specified tdm-type that is configured to be of a specified tdm-type that is configured to be
supported by the RLT."; supported by the RLT.";
leaf tdm-type { leaf tdm-type {
type identityref { type identityref {
base mw-types:tdm-type; base mw-types:tdm-type;
} }
description description
"The type of TDM connection, which also indicates "The type of TDM connection, which also indicates
the supported capacity."; the supported capacity.";
} }
leaf tdm-connections { leaf tdm-connections {
type uint16; type uint16;
skipping to change at page 10, line 52 skipping to change at page 11, line 49
"Number of connections of the specified type."; "Number of connections of the specified type.";
} }
} }
} }
/* /*
* Carrier Termination * Carrier Termination
*/ */
augment "/if:interfaces/if:interface" { augment "/if:interfaces/if:interface" {
when "if:type = 'mw-types:carrier-termination'"; when "derived-from-or-self(if:type,"
+ "'mw-types:carrier-termination')";
description description
"Addition of data nodes for carrier termination to "Addition of data nodes for carrier termination to
the standard Interface data model, for interfaces the standard Interface data model, for interfaces
of the type 'carrier-termination'."; of the type 'carrier-termination'.";
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)
skipping to change at page 12, line 4 skipping to change at page 13, line 6
"Shows the operative status of the transmitter."; "Shows the operative status of the transmitter.";
} }
leaf tx-frequency { leaf tx-frequency {
type uint32; type uint32;
units "kHz"; units "kHz";
mandatory true; mandatory true;
description description
"Selected transmitter frequency."; "Selected transmitter frequency.";
} }
leaf rx-frequency {
choice freq-or-distance {
leaf rx-frequency {
type uint32;
units "kHz";
description
"Selected receiver frequency.";
}
leaf duplex-distance {
type int32;
units "kHz";
description
"Distance between transmitter and receiver frequencies.";
}
mandatory true;
description
"A choice to configure rx-frequency directly or by computing
it as tx-frequency subtracted with the configured
duplex-distance." ;
}
leaf actual-rx-frequency {
type uint32; type uint32;
units "kHz"; units "kHz";
config false;
description description
"Selected receiver frequency. "Computed receiver frequency.";
Overrides existing value in duplex-distance.
Calculated from tx-frequency and duplex-distance if
only duplex-distance is configured.
Must match duplex-distance if both leaves are
configured in a single operation.";
} }
leaf duplex-distance { leaf actual-duplex-distance {
type uint32; type uint32;
units "kHz"; units "kHz";
config false;
description description
"Distance between Tx & Rx frequencies. "Computed distance between Tx & Rx frequencies.";
Used to calculate rx-frequency when
rx-frequency is not specifically configured.
Overrides existing value in rx-frequency.
Calculated from tx-frequency and rx-frequency if only
rx-frequency is configured.
Must match rx-frequency if both leaves are configured
in a single operation.";
} }
leaf channel-separation { leaf channel-separation {
type uint32; type uint32;
units "kHz"; units "kHz";
mandatory true; mandatory true;
description description
"The amount of bandwidth allocated to a carrier. The distance "The amount of bandwidth allocated to a carrier. The distance
between adjacent channels in a radio frequency channels between adjacent channels in a radio frequency channels
arrangement"; arrangement";
skipping to change at page 13, line 4 skipping to change at page 14, line 19
enum "horizontal" { enum "horizontal" {
description "Horizontal polarization."; description "Horizontal polarization.";
} }
enum "vertical" { enum "vertical" {
description "Vertical polarization."; description "Vertical polarization.";
} }
enum "not-specified" { enum "not-specified" {
description "Polarization not specified."; description "Polarization not specified.";
} }
} }
default "not-specified"; default "not-specified";
description description
"Polarization - A textual description for info only."; "Polarization - A textual description for info only.";
} }
leaf power-mode { choice power-mode {
type enumeration { container rtpc {
enum rtpc { description
"Remote Transmit Power Control (RTPC).";
reference "ETSI EN 302 217-1";
leaf maximum-nominal-power {
type power {
range "-99..40";
}
units "dBm";
mandatory true;
description description
"Remote Transmit Power Control (RTPC)."; "Selected output power.";
reference "ETSI EN 302 217-1"; reference "ETSI EN 302 217-1";
} }
}
container atpc {
description
"Automatic Transmit Power Control (ATPC).";
reference "ETSI EN 302 217-1";
enum atpc { leaf maximum-nominal-power {
type power {
range "-99..40";
}
units "dBm";
mandatory true;
description description
"Automatic Transmit Power Control (ATPC)."; "Selected maximum output power. Minimum output
power is the same as the system capability,
available-min-output-power.";
reference "ETSI EN 302 217-1"; reference "ETSI EN 302 217-1";
} }
}
mandatory true;
description
"A choice of Remote Transmit Power Control (RTPC)
or Automatic Transmit Power Control (ATPC).";
}
leaf maximum-nominal-power { leaf atpc-lower-threshold {
type power { type power {
range "-99..40"; range "-99..-30";
} }
units "dBm"; units "dBm";
mandatory true; must "current() <= ../atpc-upper-threshold";
description mandatory true;
"Selected output power in RTPC mode and selected description
maximum output power in ATPC mode. Minimum output "The lower threshold for the input power at far-end
power in ATPC mode is the same as the system used in the ATPC mode.";
capability, available-min-output-power."; reference "ETSI EN 302 217-1";
reference "ETSI EN 302 217-1"; }
}
leaf atpc-lower-threshold { leaf atpc-upper-threshold {
when "../power-mode = 'atpc'"; type power {
type power { range "-99..-30";
range "-99..-30"; }
} units "dBm";
units "dBm"; mandatory true;
mandatory true; description
description "The upper 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 {
when "../power-mode = 'atpc'";
type power {
range "-99..-30";
} }
units "dBm";
mandatory true; mandatory true;
description description
"The upper threshold for the input power at far-end "A choice of Remote Transmit Power Control (RTPC)
used in the ATPC mode."; or Automatic Transmit Power Control (ATPC).";
reference "ETSI EN 302 217-1";
} }
leaf actual-transmitted-level { leaf actual-transmitted-level {
type power { type power {
range "-99..40"; range "-99..40";
} }
units "dBm"; units "dBm";
config false; config false;
description description
"Actual transmitted power level (0.1 dBm resolution)."; "Actual transmitted power level (0.1 dBm resolution).";
skipping to change at page 14, line 39 skipping to change at page 16, line 15
type power { type power {
range "-99..-20"; range "-99..-20";
} }
units "dBm"; units "dBm";
config false; config false;
description description
"Actual received power level (0.1 dBm resolution)."; "Actual received power level (0.1 dBm resolution).";
reference "ETSI EN 301 129"; reference "ETSI EN 301 129";
} }
leaf coding-modulation-mode { choice coding-modulation-mode {
type enumeration { container single {
enum single { description "A single modulation order only.";
description "a single modulation order only."; reference "ETSI EN 302 217-1";
reference "ETSI EN 302 217-1";
} leaf selected-cm {
enum adaptive { type identityref {
description "Adaptive coding/modulation."; base mw-types:coding-modulation;
reference "ETSI EN 302 217-1"; }
mandatory true;
description
"Selected the single coding/modulation.";
} }
} }
mandatory true;
description
"A selection of single or
adaptive coding/modulation mode.";
}
leaf selected-cm {
when "../coding-modulation-mode = 'single'";
type identityref {
base mw-types:coding-modulation;
}
mandatory true;
description
"Selected the single coding/modulation.";
}
leaf selected-min-acm { container adaptive {
when "../coding-modulation-mode = 'adaptive'"; description "Adaptive coding/modulation.";
type identityref { reference "ETSI EN 302 217-1";
base mw-types:coding-modulation;
}
mandatory true;
description
"Selected minimum coding/modulation.
Adaptive coding/modulation shall not go
below this value.";
}
leaf selected-max-acm { leaf selected-min-acm {
when "../coding-modulation-mode = 'adaptive'"; type identityref {
type identityref { base mw-types:coding-modulation;
base mw-types:coding-modulation; }
mandatory true;
description
"Selected minimum coding/modulation.
Adaptive coding/modulation shall not go
below this value.";
}
leaf selected-max-acm {
type identityref {
base mw-types:coding-modulation;
}
mandatory true;
description
"Selected maximum coding/modulation.
Adaptive coding/modulation shall not go
above this value.";
}
} }
mandatory true; mandatory true;
description description
"Selected maximum coding/modulation. "A selection of single or
Adaptive coding/modulation shall not go adaptive coding/modulation mode.";
above this value.";
} }
leaf actual-tx-cm { leaf actual-tx-cm {
type identityref { type identityref {
base mw-types:coding-modulation; base mw-types:coding-modulation;
} }
config false; config false;
description description
"Actual coding/modulation in transmitting direction."; "Actual coding/modulation in transmitting direction.";
} }
skipping to change at page 17, line 4 skipping to change at page 18, line 29
type power { type power {
range "-99..40"; range "-99..40";
} }
units "dBm"; units "dBm";
default "-99"; default "-99";
description description
"An alarm is sent when the transmitted power level "An alarm is sent when the transmitted power level
is below the specified threshold."; is below the specified threshold.";
reference "ETSI EN 301 129"; reference "ETSI EN 301 129";
} }
leaf ber-alarm-threshold { leaf ber-alarm-threshold {
type enumeration { type enumeration {
enum "10e-9" { enum "1e-9" {
description "Threshold at 10e-9."; description "Threshold at 1e-9 (10^-9).";
} }
enum "10e-8" { enum "1e-8" {
description "Threshold at 10e-8."; description "Threshold at 1e-8 (10^-8).";
} }
enum "10e-7" { enum "1e-7" {
description "Threshold at 10e-7."; description "Threshold at 1e-7 (10^-7).";
} }
enum "10e-6" { enum "1e-6" {
description "Threshold at 10e-6."; description "Threshold at 1e-6 (10^-6).";
} }
enum "10e-5" { enum "1e-5" {
description "Threshold at 10e-5."; description "Threshold at 1e-5 (10^-5).";
} }
enum "10e-4" { enum "1e-4" {
description "Threshold at 10e-4."; description "Threshold at 1e-4 (10^-4).";
} }
enum "10e-3" { enum "1e-3" {
description "Threshold at 10e-3."; description "Threshold at 1e-3 (10^-3).";
} }
enum "10e-2" { enum "1e-2" {
description "Threshold at 10e-2."; description "Threshold at 1e-2 (10^-2).";
} }
enum "10e-1" { enum "1e-1" {
description "Threshold at 10e-1."; description "Threshold at 1e-1 (10^-1).";
} }
} }
default "10e-6"; default "1e-6";
description description
"Specification of at which BER an alarm should "Specification of at which BER an alarm should
be raised."; be raised.";
reference "ETSI EN 302 217-1"; reference "ETSI EN 302 217-1";
} }
} }
leaf if-loop { leaf if-loop {
type enumeration { type enumeration {
enum disabled { enum disabled {
skipping to change at page 18, line 42 skipping to change at page 20, line 24
container capabilities { container capabilities {
config false; config false;
description description
"Capabilities of the installed equipment and "Capabilities of the installed equipment and
some selected configurations."; some selected configurations.";
leaf min-tx-frequency { leaf min-tx-frequency {
type uint32; type uint32;
units "kHz"; units "kHz";
description description
"Minimum Tx frequency possible to use."; "Minimum Tx frequency possible to use.";
} }
leaf max-tx-frequency { leaf max-tx-frequency {
type uint32; type uint32;
units "kHz"; units "kHz";
description description
"Maximum Tx frequency possible to use."; "Maximum Tx frequency possible to use.";
} }
leaf min-rx-frequency { leaf min-rx-frequency {
type uint32; type uint32;
units "kHz"; units "kHz";
description description
"Minimum Rx frequency possible to use."; "Minimum Rx frequency possible to use.";
} }
leaf max-rx-frequency { leaf max-rx-frequency {
type uint32; type uint32;
units "kHz"; units "kHz";
skipping to change at page 21, line 54 skipping to change at page 23, line 41
} }
} }
/* /*
* Radio Link Protection Groups * Radio Link Protection Groups
*/ */
container radio-link-protection-groups { container radio-link-protection-groups {
description description
"Configuration of radio link protected groups (1+1) of "Configuration of radio link protected groups (1+1) of
carrier terminations in a radio link. More than one carrier terminations in a radio link. More than one
protected group per radio-link-terminal is allowed."; protected group per radio-link-terminal is allowed.";
uses ifprot:protection-groups { uses ifprot:protection-groups {
refine protection-group/members { refine protection-group/members {
must "/if:interfaces/if:interface[if:name = current()]" must "derived-from-or-self(/if:interfaces/if:interface"
+ "/if:type = 'mw-types:carrier-termination'" { + "[if:name = current()]"
+ "/if:type, 'mw-types:carrier-termination')" {
description description
"The type of a protection member must be "The type of a protection member must be
'carrier-termination'."; 'carrier-termination'.";
} }
} }
refine protection-group/working-entity { refine protection-group/working-entity {
must "/if:interfaces/if:interface[if:name = current()]" must "derived-from-or-self(/if:interfaces/if:interface"
+ "/if:type = 'mw-types:carrier-termination'" { + "[if:name = current()]"
+ "/if:type, 'mw-types:carrier-termination')" {
description description
"The type of a working-entity must be "The type of a working-entity must be
'carrier-termination'."; 'carrier-termination'.";
} }
} }
} }
} }
/* /*
* XPIC & MIMO groups - Configuration data nodes * XPIC & MIMO groups - Configuration data nodes
*/ */
container xpic-pairs { container xpic-pairs {
if-feature xpic; if-feature xpic;
description description
"Configuration of carrier termination pairs "Configuration of carrier termination pairs
for operation in XPIC mode."; for operation in XPIC mode.";
reference "ETSI TR 102 311"; reference "ETSI TR 102 311";
list xpic-pair { list xpic-pair {
key "name"; key "name";
description description
"List of carrier termination pairs in XPIC mode."; "List of carrier termination pairs in XPIC mode.";
skipping to change at page 23, line 4 skipping to change at page 24, line 48
description description
"Name used for identification of the XPIC pair."; "Name used for identification of the XPIC pair.";
} }
leaf enabled { leaf enabled {
type boolean; type boolean;
default "false"; default "false";
description description
"Enable(true)/disable(false) XPIC"; "Enable(true)/disable(false) XPIC";
} }
leaf-list members { leaf-list members {
type if:interface-ref; type if:interface-ref;
must "/if:interfaces/if:interface[if:name = current()]" must "derived-from-or-self(/if:interfaces/if:interface"
+ "/if:type = 'mw-types:carrier-termination'" { + "[if:name = current()]"
+ "/if:type, 'mw-types:carrier-termination')" {
description description
"The type of a member must be 'carrier-termination'."; "The type of a member must be 'carrier-termination'.";
} }
min-elements 2; min-elements 2;
max-elements 2; max-elements 2;
description description
"Association to XPIC pairs used in the radio link "Association to XPIC pairs used in the radio link
terminal."; terminal.";
} }
} }
skipping to change at page 23, line 47 skipping to change at page 25, line 44
leaf enabled { leaf enabled {
type boolean; type boolean;
default "false"; default "false";
description description
"Enable(true)/disable(false) MIMO"; "Enable(true)/disable(false) MIMO";
} }
leaf-list members { leaf-list members {
type if:interface-ref; type if:interface-ref;
must "/if:interfaces/if:interface[if:name = current()]" must "derived-from-or-self(/if:interfaces/if:interface"
+ "/if:type = 'mw-types:carrier-termination'" { + "[if:name = current()]"
+ "/if:type, 'mw-types:carrier-termination')" {
description description
"The type of a member must be 'carrier-termination'."; "The type of a member must be 'carrier-termination'.";
} }
min-elements 2; min-elements 2;
description description
"Association to a MIMO group if used in the radio "Association to a MIMO group if used in the radio
link terminal."; link terminal.";
} }
} }
} }
} }
<CODE ENDS> <CODE ENDS>
skipping to change at page 24, line 18 skipping to change at page 26, line 17
} }
} }
} }
} }
<CODE ENDS> <CODE ENDS>
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 functionality is broken out from the Microwave Radio Link Module into
into a separate and generic YANG data module in order to make it a separate and generic YANG data module in order to make it available
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-03-30.yang" <CODE BEGINS> file "ietf-interface-protection@2018-06-22.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 25, line 21 skipping to change at page 27, line 22
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-03-30 { revision 2018-06-22 {
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 26, line 31 skipping to change at page 28, line 31
base protection-states; base protection-states;
description "Protected"; description "Protected";
} }
identity unable-to-protect { identity unable-to-protect {
base protection-states; base protection-states;
description "Unable to protect"; description "Unable to protect";
} }
/* /*
* protection-external-commands identities
*/
identity protection-external-commands{
description
"Protection external commands for trouble shooting
purpose.";
reference "ITU-T G.808.1";
}
identity manual-switch-working{
base protection-external-commands;
description
"A switch action initiated by an operator command.
It switches normal traffic signal to the working
transport entity.";
reference "ITU-T G.808.1";
}
identity manual-switch-protection{
base protection-external-commands;
description
"A switch action initiated by an operator command.
It switches normal traffic signal to the protection
transport entity.";
reference "ITU-T G.808.1";
}
identity forced-switch{
base protection-external-commands;
description
"A switch action initiated by an operator command.
It switches normal traffic signal to the protection
transport entity and forces it to remain on that
entity even when criteria for switching back to
the original entity are fulfilled.";
reference "ITU-T G.808.1";
}
identity lockout-of-protection{
base protection-external-commands;
description
"A switch action temporarily disables access to the
protection transport entity for all signals.";
reference "ITU-T G.808.1";
}
identity freeze{
base protection-external-commands;
description
"A switch action temporarily prevents any switch action
to be taken and, as such, freezes the current state.
Until the freeze is cleared, additional near-end external
commands are rejected and fault condition changes and
received APS messages are ignored..";
reference "ITU-T G.808.1";
}
identity exercise{
base protection-external-commands;
description
"A switch action to test if the APS communication is
operating correctly. It is lower priority than any 'real'
switch request..";
reference "ITU-T G.808.1";
}
identity clear{
base protection-external-commands;
description
"An action clears all switch commands.";
reference "ITU-T G.808.1";
}
/*
* Protection Groups * Protection Groups
*/ */
grouping protection-groups { grouping protection-groups {
description description
"Configuration of protected groups (1+1) of interfaces "Configuration of protected groups (1+1) of interfaces
providing protection for each other. More than one protected providing protection for each other. More than one protected
group per higher-layer-interface is allowed."; group per higher-layer-interface is allowed.";
list protection-group { list protection-group {
skipping to change at page 29, line 4 skipping to change at page 29, line 22
reference "ITU-T G.808.1"; reference "ITU-T G.808.1";
} }
leaf-list members { leaf-list members {
type if:interface-ref; type if:interface-ref;
min-elements 2; min-elements 2;
description description
"Association to a group of interfaces configured for "Association to a group of interfaces configured for
protection and used by a higher-layer-interface."; protection and used by a higher-layer-interface.";
} }
leaf operation-type { leaf operation-type {
type enumeration { type enumeration {
enum "non-revertive" { enum "non-revertive" {
description description
"In non revertive operation, the traffic does not "In non revertive operation, the traffic does not
return to the working interface if the switch requests return to the working interface if the switch requests
are terminated."; are terminated.";
reference "ITU-T G.808.1"; reference "ITU-T G.808.1";
} }
enum "revertive" { enum "revertive" {
description description
"In revertive operation, the traffic always "In revertive operation, the traffic always
returns to (or remains on) the working interface returns to (or remains on) the working interface
if the switch requests are terminated."; if the switch requests are terminated.";
reference "ITU-T G.808.1"; reference "ITU-T G.808.1";
} }
} }
default "non-revertive"; default "non-revertive";
description description
"The type of protection operation, i.e. revertive "The type of protection operation, i.e. revertive
or non-revertive operation."; or non-revertive operation.";
} }
leaf-list working-entity { leaf-list working-entity {
when "../operation-type = 'revertive'"; when "../operation-type = 'revertive'";
type if:interface-ref; type if:interface-ref;
min-elements 1; min-elements 1;
description description
"The interfaces over which the traffic normally should "The interfaces over which the traffic normally should
be transported over when there is no need to use the be transported over when there is no need to use the
protecting interface."; protecting interface.";
skipping to change at page 30, line 19 skipping to change at page 30, line 34
"Time interval after the detection of a fault and its "Time interval after the detection of a fault and its
confirmation as a condition requiring the protection confirmation as a condition requiring the protection
switching procedure."; switching procedure.";
reference "ITU-T G.808.1"; reference "ITU-T G.808.1";
} }
leaf status { leaf status {
type identityref { type identityref {
base protection-states; base protection-states;
} }
config false;
description description
"Status of the protection, in a group of interfaces "Status of the protection, in a group of interfaces
configured in a protection mode."; configured in a protection mode.";
reference "ITU-T G.808.1"; reference "ITU-T G.808.1";
} }
action external-commands { action manual-switch-working{
input { description
leaf external-command { "A switch action initiated by an operator command.
type identityref { It switches normal traffic signal to the working
base protection-external-commands; transport entity.";
} reference "ITU-T G.808.1";
description }
"Execution of protection external commands for
trouble shooting purpose."; action manual-switch-protection{
} description
} "A switch action initiated by an operator command.
It switches normal traffic signal to the protection
transport entity.";
reference "ITU-T G.808.1";
}
action forced-switch{
description
"A switch action initiated by an operator command.
It switches normal traffic signal to the protection
transport entity and forces it to remain on that
entity even when criteria for switching back to
the original entity are fulfilled.";
reference "ITU-T G.808.1";
}
action lockout-of-protection{
description
"A switch action temporarily disables access to the
protection transport entity for all signals.";
reference "ITU-T G.808.1";
}
action freeze{
description
"A switch action temporarily prevents any switch action
to be taken and, as such, freezes the current state.
Until the freeze is cleared, additional near-end external
commands are rejected and fault condition changes and
received APS messages are ignored..";
reference "ITU-T G.808.1";
}
action exercise{
description
"A switch action to test if the APS communication is
operating correctly. It is lower priority than any 'real'
switch request..";
reference "ITU-T G.808.1";
}
action clear{
description
"An action clears all switch commands.";
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 This module defines a collection of common data types using the YANG
YANG data modeling language. These common types are designed data modeling language. These common types are designed to be
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-03-30.yang" <CODE BEGINS> file "ietf-microwave-types@2018-06-22.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 31, line 48 skipping to change at page 33, line 4
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-03-30 { revision 2018-06-22 {
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 33, line 19 skipping to change at page 34, line 24
/* /*
* Coding and modulation identities * Coding and modulation identities
*/ */
identity coding-modulation { identity coding-modulation {
description description
"The coding and modulation schemes."; "The coding and modulation schemes.";
} }
identity half-bpsk-strong { identity half-bpsk {
base coding-modulation; base coding-modulation;
description description
"Half BPSK strong coding and modulation scheme."; "Half BPSK coding and modulation scheme.";
} }
identity half-bpsk { identity half-bpsk-strong {
base coding-modulation; base half-bpsk;
description description
"Half BPSK coding and modulation scheme."; "Half BPSK strong coding and modulation scheme.";
} }
identity half-bpsk-light { identity half-bpsk-light {
base coding-modulation; base half-bpsk;
description description
"Half BPSK light coding and modulation scheme."; "Half BPSK light coding and modulation scheme.";
} }
identity bpsk-strong { identity bpsk {
base coding-modulation; base coding-modulation;
description description
"BPSK strong coding and modulation scheme."; "BPSK coding and modulation scheme.";
} }
identity bpsk { identity bpsk-strong {
base coding-modulation; base bpsk;
description description
"BPSK coding and modulation scheme."; "BPSK strong coding and modulation scheme.";
} }
identity bpsk-light { identity bpsk-light {
base coding-modulation; base bpsk;
description description
"BPSK light coding and modulation scheme."; "BPSK light coding and modulation scheme.";
} }
identity qpsk { identity qpsk {
base coding-modulation; base coding-modulation;
description description
"QPSK coding and modulation scheme."; "QPSK coding and modulation scheme.";
} }
identity qam-4-strong { identity qam-4 {
base coding-modulation; base coding-modulation;
description description
"4 QAM strong coding and modulation scheme."; "4 QAM coding and modulation scheme.";
} }
identity qam-4 { identity qam-4-strong {
base coding-modulation; base qam-4;
description description
"4 QAM coding and modulation scheme."; "4 QAM strong coding and modulation scheme.";
} }
identity qam-4-light { identity qam-4-light {
base coding-modulation; base qam-4;
description description
"4 QAM light coding and modulation scheme."; "4 QAM light coding and modulation scheme.";
} }
identity qam-16-strong { identity qam-16 {
base coding-modulation; base coding-modulation;
description description
"16 QAM strong coding and modulation scheme."; "16 QAM coding and modulation scheme.";
} }
identity qam-16 { identity qam-16-strong {
base coding-modulation; base qam-16;
description description
"16 QAM coding and modulation scheme."; "16 QAM strong coding and modulation scheme.";
} }
identity qam-16-light { identity qam-16-light {
base coding-modulation; base qam-16;
description description
"16 QAM light coding and modulation scheme."; "16 QAM light coding and modulation scheme.";
}
identity qam-32-strong {
base coding-modulation;
description
"32 QAM strong coding and modulation scheme.";
} }
identity qam-32 { identity qam-32 {
base coding-modulation; base coding-modulation;
description description
"32 QAM coding and modulation scheme."; "32 QAM coding and modulation scheme.";
} }
identity qam-32-light { identity qam-32-strong {
base coding-modulation; base qam-32;
description description
"32 QAM light coding and modulation scheme."; "32 QAM strong coding and modulation scheme.";
} }
identity qam-64-strong { identity qam-32-light {
base coding-modulation; base qam-32;
description description
"64 QAM strong coding and modulation scheme."; "32 QAM light coding and modulation scheme.";
} }
identity qam-64 { identity qam-64 {
base coding-modulation; base coding-modulation;
description description
"64 QAM coding and modulation scheme."; "64 QAM coding and modulation scheme.";
} }
identity qam-64-light { identity qam-64-strong {
base coding-modulation; base qam-64;
description description
"64 QAM light coding and modulation scheme."; "64 QAM strong coding and modulation scheme.";
} }
identity qam-128-strong { identity qam-64-light {
base coding-modulation; base qam-64;
description description
"128 QAM strong coding and modulation scheme."; "64 QAM light coding and modulation scheme.";
} }
identity qam-128 { identity qam-128 {
base coding-modulation; base coding-modulation;
description description
"128 QAM coding and modulation scheme."; "128 QAM coding and modulation scheme.";
} }
identity qam-128-light { identity qam-128-strong {
base coding-modulation; base qam-128;
description description
"128 QAM light coding and modulation scheme."; "128 QAM strong coding and modulation scheme.";
} }
identity qam-256-strong {
base coding-modulation; identity qam-128-light {
base qam-128;
description description
"256 QAM strong coding and modulation scheme."; "128 QAM light coding and modulation scheme.";
} }
identity qam-256 { identity qam-256 {
base coding-modulation; base coding-modulation;
description description
"256 QAM coding and modulation scheme."; "256 QAM coding and modulation scheme.";
} }
identity qam-256-light { identity qam-256-strong {
base coding-modulation; base qam-256;
description description
"256 QAM light coding and modulation scheme."; "256 QAM strong coding and modulation scheme.";
} }
identity qam-512-strong { identity qam-256-light {
base coding-modulation; base qam-256;
description description
"512 QAM strong coding and modulation scheme."; "256 QAM light coding and modulation scheme.";
} }
identity qam-512 { identity qam-512 {
base coding-modulation; base coding-modulation;
description description
"512 QAM coding and modulation scheme."; "512 QAM coding and modulation scheme.";
} }
identity qam-512-light { identity qam-512-strong {
base coding-modulation; base qam-512;
description description
"512 QAM light coding and modulation scheme."; "512 QAM strong coding and modulation scheme.";
} }
identity qam-1024-strong { identity qam-512-light {
base coding-modulation; base qam-512;
description description
"1024 QAM strong coding and modulation scheme."; "512 QAM light coding and modulation scheme.";
} }
identity qam-1024 { identity qam-1024 {
base coding-modulation; base coding-modulation;
description description
"1024 QAM coding and modulation scheme."; "1024 QAM coding and modulation scheme.";
} }
identity qam-1024-light {
base coding-modulation; identity qam-1024-strong {
base qam-1024;
description description
"1024 QAM light coding and modulation scheme."; "1024 QAM strong coding and modulation scheme.";
} }
identity qam-2048-strong { identity qam-1024-light {
base coding-modulation; base qam-1024;
description description
"2048 QAM strong coding and modulation scheme."; "1024 QAM light coding and modulation scheme.";
} }
identity qam-2048 { identity qam-2048 {
base coding-modulation; base coding-modulation;
description description
"2048 QAM coding and modulation scheme."; "2048 QAM coding and modulation scheme.";
} }
identity qam-2048-light { identity qam-2048-strong {
base coding-modulation; base qam-2048;
description description
"2048 QAM light coding and modulation scheme."; "2048 QAM strong coding and modulation scheme.";
} }
identity qam-4096-strong { identity qam-2048-light {
base coding-modulation; base qam-2048;
description description
"4096 QAM strong coding and modulation scheme."; "2048 QAM light coding and modulation scheme.";
} }
identity qam-4096 { identity qam-4096 {
base coding-modulation; base coding-modulation;
description description
"4096 QAM coding and modulation scheme."; "4096 QAM coding and modulation scheme.";
} }
identity qam-4096-strong {
base qam-4096;
description
"4096 QAM strong coding and modulation scheme.";
}
identity qam-4096-light { identity qam-4096-light {
base coding-modulation; base qam-4096;
description description
"4096 QAM light coding and modulation scheme."; "4096 QAM light coding and modulation scheme.";
} }
/* /*
* TDM-type identities * TDM-type identities
*/ */
identity tdm-type { identity tdm-type {
description description
"A description of the type of TDM connection, "A description of the type of TDM connection,
also indicating the supported capacity of the also indicating the supported capacity of the
skipping to change at page 38, line 43 skipping to change at page 40, line 9
There are a number of data nodes defined in this YANG module that are There are a number of data nodes defined in this YANG module that are
writable/creatable/deletable (i.e., config true, which is the 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/carrier-terminations,
/if:interfaces/if:interface/rlp-groups, /if:interfaces/if:interface/carrier-terminations,
/if:interfaces/if:interface/xpic-pairs, /if:interfaces/if:interface/rlp-groups,
/if:interfaces/if:interface/mimo-groups, and /if:interfaces/if:interface/xpic-pairs,
/if:interfaces/if:interface/tdm-connections: /if:interfaces/if:interface/mimo-groups, and
/if:interfaces/if:interface/tdm-connections:
These lists represent the configuration of the radio-link-terminal These lists represent the configuration of the radio-link-terminal
and it need to match the configuration of the radio-link-terminal and it need to match the configuration of the radio-link-terminal on
on the other side of the radio link. Unauthorized access to these the other side of the radio link. Unauthorized access to these data
data nodes could interrupt the ability to forward traffic. 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/tx-enabled,
/if:interfaces/if:interface/tx-frequency,
/if:interfaces/if:interface/rx-frequency,
/if:interfaces/if:interface/duplex-distance,
/if:interfaces/if:interface/channel-separation,
/if:interfaces/if:interface/power-mode,
/if:interfaces/if:interface/maximum-nominal-power,
/if:interfaces/if:interface/atpc-lower-threshold,
/if:interfaces/if:interface/atpc-upper-threshold,
/if:interfaces/if:interface/coding-modulation-mode,
/if:interfaces/if:interface/selected-cm,
/if:interfaces/if:interface/selected-min-acm,
/if:interfaces/if:interface/selected-max-acm,
/if:interfaces/if:interface/if-loop, and
/if:interfaces/if:interface/rf-loop:
These data nodes represent the configuration of the /if:interfaces/if:interface/carrier-id,
carrier-termination and it need to match the configuration of the /if:interfaces/if:interface/tx-enabled,
carrier-termination on the other side of the carrier. Unauthorized /if:interfaces/if:interface/tx-frequency,
access to these data nodes could interrupt the ability to forward /if:interfaces/if:interface/rx-frequency,
traffic. /if:interfaces/if:interface/duplex-distance,
/if:interfaces/if:interface/channel-separation,
/if:interfaces/if:interface/rtpc/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-upper-threshold,
/if:interfaces/if:interface/single/selected-cm,
/if:interfaces/if:interface/adaptive/selected-min-acm,
/if:interfaces/if:interface/adaptive/selected-max-acm,
/if:interfaces/if:interface/if-loop, and
/if:interfaces/if:interface/rf-loop:
These data nodes represent the configuration of the carrier-
termination and it need to match the configuration of the carrier-
termination on the other side of the carrier. Unauthorized access to
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 list of protection groups and the constituent data nodes
represents the configuration of the protection of carrier represents the configuration of the protection of carrier
terminations. Unauthorized access to these data nodes 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 list represents the XPIC configuration of a pair carriers.
Unauthorized access to these data nodes could interrupt the ability Unauthorized access to these data nodes could interrupt the ability
to forward traffic. to forward traffic.
MIMO: MIMO:
/mimo-groups:
/mimo-groups:
This list represents the MIMO configuration of multiple carriers. This list represents the MIMO configuration of multiple carriers.
Unauthorized access to these data nodes could interrupt the ability Unauthorized access to these data nodes could interrupt the ability
to forward traffic. to forward traffic.
The security considerations of [RFC8343] also apply to this The security considerations of [RFC8343] also apply to this document.
document.
8. IANA Considerations 8. IANA Considerations
It is proposed that IANA should assign new URIs from the It is proposed that IANA should assign new URIs from the "IETF XML
"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
XML: N/A; the requested URI is an XML namespace. XML: N/A; the requested URI is an XML namespace.
URI: urn:ietf:params:xml:ns:yang:ietf-interface-protection URI: urn:ietf:params:xml:ns:yang:ietf-interface-protection
Registrant Contact: The IESG Registrant Contact: The IESG
XML: N/A; the requested URI is an XML namespace. XML: N/A; the requested URI is an XML namespace.
It is proposed that IANA should record YANG module names in the It is proposed that IANA should record YANG module names in the "YANG
"YANG Module Names" registry [RFC6020] as follows: Module Names" registry [RFC6020] as follows:
Name: ietf-microwave-radio-link Name: ietf-microwave-radio-link
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
Reference: RFC XXXX Reference: RFC XXXX
Name: ietf-interface-protection Name: ietf-interface-protection
Namespace: urn:ietf:params:xml:ns:yang:ietf-interface-protection Namespace: urn:ietf:params:xml:ns:yang:ietf-interface-protection
Prefix: ifprot Prefix: ifprot
Reference: RFC XXXX Reference: RFC XXXX
9. References 9. References
9.1. Normative References 9.1. Normative References
[RFC2119] Bradner, S., "Key words for use in RFCs to Indicate [EN301129]
Requirement Levels", BCP 14, RFC 2119, "Transmission and Multiplexing (TM); Digital Radio Relay
DOI 10.17487/RFC2119, March 1997, Systems (DRRS); Synchronous Digital Hierarchy (SDH);
<http://www.rfc-editor.org/info/rfc2119>. System performance monitoring parameters of SDH DRRS", EN
301 129 V1.1.2 , May 1995.
[RFC8174] Leiba, B., "Ambiguity of Uppercase vs Lowercase in RFC
2119 Key Words", BCP 14, RFC 8174, DOI 10.17487/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>.
[EN301129] ETSI, "Transmission and Multiplexing (TM); Digital Radio
Relay Systems (DRRS); Synchronous Digital Hierarchy (SDH);
System performance monitoring parameters of SDH DRRS",
EN 301 129 V1.1.2, May 1995.
[EN302217-1] [EN302217-1]
ETSI, "Fixed Radio Systems; Characteristics and "Fixed Radio Systems; Characteristics and requirements for
requirements for point-to-point equipment and antennas; point-to-point equipment and antennas; Part 1: Overview,
Part 1: Overview, common characteristics and system- common characteristics and system-dependent requirements",
dependent requirements", EN 302 217-1 V3.0.5, June 2016. EN 302 217-1 V3.0.5 , June 2016.
[EN302217-2] [EN302217-2]
ETSI, "Fixed Radio Systems; Characteristics and "Fixed Radio Systems; Characteristics and requirements for
requirements for point to-point equipment and antennas; point to-point equipment and antennas; Part 2: Digital
Part 2: Digital systems operating in frequency bands from systems operating in frequency bands from 1 GHz to 86 GHz;
1 GHz to 86 GHz; Harmonised Standard covering the Harmonised Standard covering the essential requirements of
essential requirements of article 3.2 of Directive article 3.2 of Directive 2014/53/EU", EN 302 217-2
2014/53/EU", EN 302 217-2 V3.1.1, May 2017. V3.1.1 , May 2017.
[G.808.1] ITU-T, "SERIES G: TRANSMISSION SYSTEMS AND MEDIA, DIGITAL [G.808.1] "SERIES G: TRANSMISSION SYSTEMS AND MEDIA, DIGITAL SYSTEMS
SYSTEMS AND NETWORKS; Digital networks ; General aspects AND NETWORKS; Digital networks ; General aspects Generic
Generic protection switching ; Linear trail and subnetwork protection switching ; Linear trail and subnetwork
protection", ITU-T Rec. G.808.1, May 2014. protection", ITU-T Rec. G.808.1 , May 2014.
[G.826] ITU-T, "SERIES G: TRANSMISSION SYSTEMS AND MEDIA, DIGITAL [G.826] "SERIES G: TRANSMISSION SYSTEMS AND MEDIA, DIGITAL SYSTEMS
SYSTEMS AND NETWORKS; Digital networks ; Quality and AND NETWORKS; Digital networks ; Quality and availability
availability targets End-to-end error performance targets End-to-end error performance parameters and
parameters and objectives for international, constant objectives for international, constant bit-rate digital
bit-rate digital paths and connections", ITU-T Rec. G.826, paths and connections", ITU-T Rec. G.826 , December 2002.
December 2002.
[TR102311] ETSI, "Fixed Radio Systems; Point-to-point equipment; [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate
Specific aspects of the spatial frequency reuse method", Requirement Levels", BCP 14, RFC 2119,
ETSI TR 102 311 V1.2.1, November 2015. DOI 10.17487/RFC2119, March 1997,
<https://www.rfc-editor.org/info/rfc2119>.
[RFC3688] Mealling, M., "The IETF XML Registry", BCP 81, RFC 3688, [RFC3688] Mealling, M., "The IETF XML Registry", BCP 81, RFC 3688,
DOI 10.17487/RFC3688, January 2004, <https://www.rfc- DOI 10.17487/RFC3688, January 2004,
editor.org/info/rfc3688>. <https://www.rfc-editor.org/info/rfc3688>.
[RFC5246] Dierks, T. and E. Rescorla, "The Transport Layer Security [RFC5246] Dierks, T. and E. Rescorla, "The Transport Layer Security
(TLS) Protocol Version 1.2", RFC 5246, (TLS) Protocol Version 1.2", RFC 5246,
DOI 10.17487/RFC5246, August 2008, DOI 10.17487/RFC5246, August 2008,
<https://www.rfc-editor.org/info/rfc5246>. <https://www.rfc-editor.org/info/rfc5246>.
[RFC6020] Bjorklund, M., Ed., "YANG - A Data Modeling Language for [RFC6020] Bjorklund, M., Ed., "YANG - A Data Modeling Language for
the Network Configuration Protocol (NETCONF)", RFC 6020, the Network Configuration Protocol (NETCONF)", RFC 6020,
DOI 10.17487/RFC6020, October 2010, DOI 10.17487/RFC6020, October 2010,
<https://www.rfc-editor.org/info/rfc6020>. <https://www.rfc-editor.org/info/rfc6020>.
[RFC6241] Enns, R., Bjorklund, M., Schoenwaelder, J., and A. [RFC6241] Enns, R., Ed., Bjorklund, M., Ed., Schoenwaelder, J., Ed.,
Bierman, "Network Configuration Protocol (NETCONF)", and A. Bierman, Ed., "Network Configuration Protocol
RFC 6241, June 2011. (NETCONF)", RFC 6241, DOI 10.17487/RFC6241, June 2011,
<https://www.rfc-editor.org/info/rfc6241>.
[RFC6242] Wasserman, M., "Using the NETCONF Protocol over Secure [RFC6242] Wasserman, M., "Using the NETCONF Protocol over Secure
Shell (SSH)", RFC 6242, June 2011. Shell (SSH)", RFC 6242, DOI 10.17487/RFC6242, June 2011,
<https://www.rfc-editor.org/info/rfc6242>.
[RFC6991] Schoenwaelder, J., "Common YANG Data Types", RFC 6991, [RFC6991] Schoenwaelder, J., Ed., "Common YANG Data Types",
July 2013. RFC 6991, DOI 10.17487/RFC6991, July 2013,
<https://www.rfc-editor.org/info/rfc6991>.
[RFC7224] Bjorklund, M., "IANA Interface Type YANG Module", [RFC7224] Bjorklund, M., "IANA Interface Type YANG Module",
RFC 7224, May 2014. RFC 7224, DOI 10.17487/RFC7224, May 2014,
<https://www.rfc-editor.org/info/rfc7224>.
[RFC8040] Bierman, A., Bjorklund, M., and K. Watsen, "RESTCONF [RFC8040] Bierman, A., Bjorklund, M., and K. Watsen, "RESTCONF
Protocol", RFC 8040, DOI 10.17487/RFC8040, January 2017, Protocol", RFC 8040, DOI 10.17487/RFC8040, January 2017,
<http://www.rfc-editor.org/info/rfc8040>. <https://www.rfc-editor.org/info/rfc8040>.
[RFC8174] Leiba, B., "Ambiguity of Uppercase vs Lowercase in RFC
2119 Key Words", BCP 14, RFC 8174, DOI 10.17487/RFC8174,
May 2017, <https://www.rfc-editor.org/info/rfc8174>.
[RFC8341] Bierman, A. and M. Bjorklund, "Network Configuration [RFC8341] Bierman, A. and M. Bjorklund, "Network Configuration
Access Control Model", STD 91, RFC 8341, Access Control Model", STD 91, RFC 8341,
DOI 10.17487/RFC8341, March 2018, <https://www.rfc- DOI 10.17487/RFC8341, March 2018,
editor.org/info/rfc8341>. <https://www.rfc-editor.org/info/rfc8341>.
9.2. Informative References [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>.
[RFC8342] Bjorklund, M., Schoenwaelder, J., Shafer, P., Watsen, K., [TR102311]
and R. Wilton, "Network Management Datastore Architecture "Fixed Radio Systems; Point-to-point equipment; Specific
(NMDA)", RFC 8342, DOI 10.17487/RFC8342, March 2018, aspects of the spatial frequency reuse method", ETSI TR
<https://www.rfc-editor.org/info/rfc8342>. 102 311 V1.2.1 , November 2015.
9.2. Informative References
[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] [I-D.ietf-ccamp-microwave-framework]
Ahlberg, J., Contreras, L., Ye, M., Vaupotic, M., Ahlberg, J., Ye, M., Li, X., Contreras, L., and C.
Tantsura, J., Kawada, K., Li, X., Akiyoshi, I., C. Bernardos, "A framework for Management and Control of
Bernardos, and D. Spreafico, "A framework for Management microwave and millimeter wave interface parameters",
and Control of microwave and millimeter wave interface draft-ietf-ccamp-microwave-framework-07 (work in
parameters", draft-ietf-ccamp-microwave-framework-05 progress), June 2018.
(work in progress), October 2017.
[ONF-model] "Microwave Modeling - ONF Wireless Transport Group",
May 2016.
[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,
<http://www.rfc-editor.org/info/rfc6241>.
[RFC6242] Wasserman, M., "Using the NETCONF Protocol over Secure [ONF-model]
Shell (SSH)", RFC 6242, DOI 10.17487/RFC6242, June 2011, "Microwave Information Model", version 1.0 , December
<http://www.rfc-editor.org/info/rfc6242>. 2016,
<https://www.opennetworking.org/images/stories/downloads/
sdn-resources/technical-reports/
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>.
Appendix A. Example: 1+0 and 2+0 configuration instances [RFC8342] Bjorklund, M., Schoenwaelder, J., Shafer, P., Watsen, K.,
and R. Wilton, "Network Management Datastore Architecture
(NMDA)", RFC 8342, DOI 10.17487/RFC8342, March 2018,
<https://www.rfc-editor.org/info/rfc8342>.
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
Figure A-1 shows a 1+0 example.
Figure A-1 shows a 1+0 example. /--------- Radio Link ---------\
Near End Far End
/--------- Radio Link ---------\
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| |
skipping to change at page 43, line 49 skipping to change at page 45, line 40
{ {
//RLT-A //RLT-A
"name": "RLT-A", "name": "RLT-A",
"description": "Radio Link Terminal A", "description": "Radio Link Terminal A",
"type": "mrl:radio-link-terminal", "type": "mrl:radio-link-terminal",
"id": "RLT-A", "id": "RLT-A",
"mode": "one-plus-zero", "mode": "one-plus-zero",
"carrier-terminations": [ "carrier-terminations": [
"RLT-A:CT-1", "RLT-A:CT-1",
], ],
"tdm-connections": [
"tdm-type": "E1",
"tdm-connections": "4",
]
} }
{ {
//CT-1 //CT-1
"name": "RLT-A:CT-1", "name": "RLT-A:CT-1",
"description": "Carrier Termination 1", "description": "Carrier Termination 1",
"type": "mrl:carrier-termination", "type": "mrl:carrier-termination",
"carrier-id": "A", "carrier-id": "A",
"tx-enabled": true, "tx-enabled": true,
"tx-oper-status": on
"tx-frequency": 10728000, "tx-frequency": 10728000,
"duplex-distance": 644000, "duplex-distance": 644000,
"channel-separation": 28, "channel-separation": 28,
"polarization": not-specified, "polarization": not-specified,
"power-mode": rtpc, "rtpc": {
"coding-modulation-mode": 0, "maximum-nominal-power": 20,
"selected-cm": "qam-512" }
"single":{
"selected-cm": "qam-512",
}
}, },
] ]
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
skipping to change at page 44, line 50 skipping to change at page 46, line 46
| | | | | | | |
| +-----------+ | | +-----------+ | | +-----------+ | | +-----------+ |
| | | | 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 Near End node. The following instance shows the 2+0 configuration of Near End node.
"interface": [ "interface": [
{ {
//RLT-A //RLT-A
"name": "RLT-A", "name": "RLT-A",
"description": "Radio Link Terminal A", "description": "Radio Link Terminal A",
"type": "mrl:radio-link-terminal", "type": "mrl:radio-link-terminal",
"id": "RLT-A", "id": "RLT-A",
"mode": "two-plus-zero", "mode": "two-plus-zero",
"carrier-terminations": [ "carrier-terminations": [
"RLT-A:CT-1", "RLT-A:CT-1",
skipping to change at page 45, line 18 skipping to change at page 47, line 17
//RLT-A //RLT-A
"name": "RLT-A", "name": "RLT-A",
"description": "Radio Link Terminal A", "description": "Radio Link Terminal A",
"type": "mrl:radio-link-terminal", "type": "mrl:radio-link-terminal",
"id": "RLT-A", "id": "RLT-A",
"mode": "two-plus-zero", "mode": "two-plus-zero",
"carrier-terminations": [ "carrier-terminations": [
"RLT-A:CT-1", "RLT-A:CT-1",
"RLT-A:CT-2" "RLT-A:CT-2"
], ],
"tdm-connections": [
"tdm-type": "E1",
"tdm-connections": "4",
]
} }
{ {
//CT-1 //CT-1
"name": "RLT-A:CT-1", "name": "RLT-A:CT-1",
"description": "Carrier Termination 1", "description": "Carrier Termination 1",
"type": "mrl:carrier-termination", "type": "mrl:carrier-termination",
"carrier-id": "A", "carrier-id": "A",
"tx-enabled": true, "tx-enabled": true,
"tx-frequency": 10728000,
"duplex-distance": 644000,
"channel-separation": 28,
"polarization": not-specified,
"rtpc": {
"maximum-nominal-power": 20,
}
"single":{
"selected-cm": "qam-512",
}
},
{
//CT-2
"name": "RLT-A:CT-2",
"description": "Carrier Termination 2",
"type": "mrl:carrier-termination",
"carrier-id": "B",
"tx-enabled": true,
"tx-oper-status": on "tx-oper-status": on
"tx-frequency": 10618000,
"duplex-distance": 644000,
"channel-separation": 28,
"polarization": not-specified,
"rtpc": {
"maximum-nominal-power": 20,
}
"single":{
"selected-cm": "qam-512",
}
},
]
A.3 2+0 XPIC instance
The following instance shows the XPIC configuration of Near End node.
"interface": [
{
//RLT-A
"name": "RLT-A",
"description": "Radio Link Terminal A",
"type": "mrl:radio-link-terminal",
"id": "RLT-A",
"mode": "two-plus-zero",
"carrier-terminations": [
"RLT-A:CT-1",
"RLT-A:CT-2"
],
"xpic-pairs": [
"RLT-A:CT-1",
"RLT-A:CT-2"
]
"tdm-connections": [
"tdm-type": "E1",
"tdm-connections": "4",
]
}
{
//CT-1
"name": "RLT-A:CT-1",
"description": "Carrier Termination 1",
"type": "mrl:carrier-termination",
"carrier-id": "A",
"tx-enabled": true,
"tx-frequency": 10728000, "tx-frequency": 10728000,
"duplex-distance": 644000, "duplex-distance": 644000,
"channel-separation": 28, "channel-separation": 28,
"polarization": not-specified, "polarization": not-specified,
"power-mode": rtpc, "rtpc": {
"coding-modulation-mode": 0, "maximum-nominal-power": 20,
"selected-cm": "qam-512"
}
"single":{
"selected-cm": "qam-512",
}
}, },
{ {
//CT-2 //CT-2
"name": "RLT-A:CT-2", "name": "RLT-A:CT-2",
"description": "Carrier Termination 2", "description": "Carrier Termination 2",
"type": "mrl:carrier-termination", "type": "mrl:carrier-termination",
"carrier-id": "B", "carrier-id": "B",
"tx-enabled": true, "tx-enabled": true,
"tx-oper-status": on "tx-oper-status": on
"tx-frequency": 10618000, "tx-frequency": 10618000,
"duplex-distance": 644000, "duplex-distance": 644000,
"channel-separation": 28, "channel-separation": 28,
"polarization": not-specified, "polarization": not-specified,
"power-mode": rtpc, "rtpc": {
"coding-modulation-mode": 0, "maximum-nominal-power": 20,
"selected-cm": "qam-512" }
"single":{
"selected-cm": "qam-512",
}
}, },
] ]
Appendix B. Contributors Appendix B. Contributors
Koji Kawada Koji Kawada
NEC Corporation NEC Corporation
1753, Shimonumabe Nakahara-ku 1753, Shimonumabe Nakahara-ku
Kawasaki, Kanagawa 211-8666 Kawasaki, Kanagawa 211-8666
Japan (JPN) Japan
Email: k-kawada@ah.jp.nec.com Email: k-kawada@ah.jp.nec.com
Carlos J. Bernardos Carlos J. Bernardos
Universidad Carlos III de Madrid Universidad Carlos III de Madrid
Av. Universidad, 30 Av. Universidad, 30
Leganes, Madrid 28911 Leganes, Madrid 28911
Spain (ESP) Spain (ESP)
Email: cjbc@it.uc3m.es Email: cjbc@it.uc3m.es
Authors' Addresses Authors' Addresses
Jonas Ahlberg Jonas Ahlberg
Ericsson AB Ericsson AB
Lindholmspiren 11 Lindholmspiren 11
Goeteborg 417 56 Goteborg 417 56
Sweden (SWE) Sweden
Email: jonas.ahlberg@ericsson.com Email: jonas.ahlberg@ericsson.com
Ye Min Ye Min
Huawei Technologies Huawei Technologies
No.1899, Xiyuan Avenue No.1899, Xiyuan Avenue
Chengdu 611731 Chengdu 611731
P.R.China (CHN) P.R.China
Email: amy.yemin@huawei.com Email: amy.yemin@huawei.com
Xi Li Xi Li
NEC Laboratories Europe GmbH NEC Laboratories Europe
Kurfursten-Anlage 36 Kurfursten-Anlage 36
69115 Heidelberg Heidelberg 69115
Germany (DEU) Germany
Email: Xi.Li@neclab.eu Email: Xi.Li@neclab.eu
Daniela Spreafico Daniela Spreafico
Nokia - IT Nokia - IT
Via Energy Park, 14 Via Energy Park, 14
Vimercate (MI) 20871 Vimercate (MI) 20871
Italy (ITA) Italy
Email: daniela.spreafico@nokia.com Email: daniela.spreafico@nokia.com
Marko Vaupotic Marko Vaupotic
Aviat Networks Aviat Networks
Motnica 9 Motnica 9
Trzin-Ljubljana 1236 Trzin-Ljubljana 1236
Slovenia (SVN) Slovenia
Email: Marko.Vaupotic@Aviatnet.com Email: Marko.Vaupotic@Aviatnet.com
 End of changes. 203 change blocks. 
553 lines changed or deleted 673 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/