draft-ietf-ccamp-mw-yang-13.txt   rfc8561.txt 
CCAMP Working Group J. Ahlberg Internet Engineering Task Force (IETF) J. Ahlberg
Internet-Draft Ericsson AB Request for Comments: 8561 Ericsson AB
Intended status: Standards Track M. Ye Category: Standards Track M. Ye
Expires: June 1, 2019 Huawei Technologies ISSN: 2070-1721 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
November 28, 2018 June 2019
A YANG Data Model for Microwave Radio Link A YANG Data Model for Microwave Radio Link
draft-ietf-ccamp-mw-yang-13
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 radio link interfaces and their connectivity to packet (typically
(typically Ethernet) interfaces in a microwave/millimeter wave node. Ethernet) interfaces in a microwave/millimeter wave node. The data
The data nodes for management of the interface protection nodes for management of the interface protection functionality is
functionality is broken out into a separate and generic YANG data broken out into a separate and generic YANG data model in order to
model in order to make it available also for other interface types. make it available for other interface types as well.
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 is an Internet Standards Track document.
provisions of BCP 78 and BCP 79.
Internet-Drafts are working documents of the Internet Engineering
Task Force (IETF). Note that other groups may also distribute
working documents as Internet-Drafts. The list of current Internet-
Drafts is at https://datatracker.ietf.org/drafts/current/.
Internet-Drafts are draft documents valid for a maximum of six months This document is a product of the Internet Engineering Task Force
and may be updated, replaced, or obsoleted by other documents at any (IETF). It represents the consensus of the IETF community. It has
time. It is inappropriate to use Internet-Drafts as reference received public review and has been approved for publication by the
material or to cite them other than as "work in progress." Internet Engineering Steering Group (IESG). Further information on
Internet Standards is available in Section 2 of RFC 7841.
This Internet-Draft will expire on June 1, 2019. Information about the current status of this document, any errata,
and how to provide feedback on it may be obtained at
https://www.rfc-editor.org/info/rfc8561.
Copyright Notice Copyright Notice
Copyright (c) 2018 IETF Trust and the persons identified as the Copyright (c) 2019 IETF Trust and the persons identified as the
document authors. All rights reserved. document authors. All rights reserved.
This document is subject to BCP 78 and the IETF Trust's Legal This document is subject to BCP 78 and the IETF Trust's Legal
Provisions Relating to IETF Documents Provisions Relating to IETF Documents
(https://trustee.ietf.org/license-info) in effect on the date of (https://trustee.ietf.org/license-info) in effect on the date of
publication of this document. Please review these documents publication of this document. Please review these documents
carefully, as they describe your rights and restrictions with respect carefully, as they describe your rights and restrictions with respect
to this document. Code Components extracted from this document must to this document. Code Components extracted from this document must
include Simplified BSD License text as described in Section 4.e of include Simplified BSD License text as described in Section 4.e of
the Trust Legal Provisions and are provided without warranty as the Trust Legal Provisions and are provided without warranty as
described in the Simplified BSD License. described in the Simplified BSD License.
Table of Contents Table of Contents
1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 2 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 3
1.1. Terminology and Definitions . . . . . . . . . . . . . . . 3 1.1. Terminology and Definitions . . . . . . . . . . . . . . . 3
1.2. Tree Structure . . . . . . . . . . . . . . . . . . . . . 4 1.2. Tree Structure . . . . . . . . . . . . . . . . . . . . . 5
2. Requirements Language . . . . . . . . . . . . . . . . . . . . 4 2. Microwave Radio Link YANG Data Model . . . . . . . . . . . . 5
3. Microwave Radio Link YANG Data Model . . . . . . . . . . . . 5 2.1. YANG Tree . . . . . . . . . . . . . . . . . . . . . . . . 5
3.1. YANG Tree . . . . . . . . . . . . . . . . . . . . . . . . 5 2.2. Explanation of the Microwave Data Model . . . . . . . . . 7
3.2. Explanation of the Microwave Data Model . . . . . . . . . 7 3. Microwave Radio Link YANG Data Model . . . . . . . . . . . . 7
4. Microwave Radio Link YANG Module . . . . . . . . . . . . . . 7 4. Interface Protection YANG Data Model . . . . . . . . . . . . 27
5. Interface Protection YANG Module . . . . . . . . . . . . . . 27 5. Microwave Types YANG Data Model . . . . . . . . . . . . . . . 33
6. Microwave Types YANG Module . . . . . . . . . . . . . . . . . 33 6. Security Considerations . . . . . . . . . . . . . . . . . . . 40
7. Security Considerations . . . . . . . . . . . . . . . . . . . 40 7. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 42
8. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 42 8. References . . . . . . . . . . . . . . . . . . . . . . . . . 43
9. References . . . . . . . . . . . . . . . . . . . . . . . . . 43 8.1. Normative References . . . . . . . . . . . . . . . . . . 43
9.1. Normative References . . . . . . . . . . . . . . . . . . 43 8.2. Informative References . . . . . . . . . . . . . . . . . 44
9.2. Informative References . . . . . . . . . . . . . . . . . 44 Appendix A. Example: 1+0 and 2+0 Configuration Instances . . . . 47
Appendix A. Example: 1+0 and 2+0 configuration instances . . . . 45 A.1. 1+0 Instance . . . . . . . . . . . . . . . . . . . . . . 47
A.1. 1+0 instance . . . . . . . . . . . . . . . . . . . . . . 46 A.2. 2+0 Instance . . . . . . . . . . . . . . . . . . . . . . 49
A.2. 2+0 instance . . . . . . . . . . . . . . . . . . . . . . 47 A.3. 2+0 XPIC Instance . . . . . . . . . . . . . . . . . . . . 50
A.3. 2+0 XPIC instance . . . . . . . . . . . . . . . . . . . . 49 Contributors . . . . . . . . . . . . . . . . . . . . . . . . . . 52
Appendix B. Contributors . . . . . . . . . . . . . . . . . . . . 50 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 53
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 Time-Division Multiplexing (TDM) interfaces in a
ETSI EN 302 217 series defines the characteristics and requirements microwave/millimeter wave node. The ETSI EN 302 217 series defines
of microwave/millimeter wave equipment and antennas. Especially ETSI the characteristics and requirements of microwave/millimeter wave
EN 302 217-2 [EN302217-2] specifies the essential parameters for the equipment and antennas. Specifically, ETSI EN 302 217-2 [EN302217-2]
systems operating from 1.4GHz to 86GHz. The data model includes specifies the essential parameters for systems operating from 1.4 GHz
configuration and state data according to the new Network Management to 86 GHz. The data model includes configuration and state data
Datastore Architecture [RFC8342]. according to the new Network Management 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 [RFC8432]. This framework identifies the need and the scope of in [RFC8432]. This framework identifies the need and the scope of
the YANG data model, the use cases and requirements that the model the YANG data model, use cases, and requirements that the model needs
needs to support. Moreover, it provides a detailed gap analysis to to support. Moreover, it provides a detailed gap analysis to
identify the missing parameters and functionalities of the existing identify the missing parameters and functionalities of the existing
and established models to support the specified use cases and and established models to support the specified use cases and
requirements, and based on that recommends how the gaps should be requirements, and based on that, it recommends how the gaps should be
filled with the development of the new model. According to the filled with the development of the new model. According to the
conclusion of the gap analysis, the structure of the data model is conclusion of the gap analysis, the structure of the data model is
based on the structure defined in based on the structure defined in [MICROWAVE-RADIO-LINK], and it
[I-D.ahlberg-ccamp-microwave-radio-link] and it augments [RFC8343] to augments [RFC8343] to align with the same structure for management of
align with the same structure for management of the packet the packet interfaces. More specifically, the model will include
interfaces. More specifically, the model will include interface interface layering to manage the capacity provided by a radio link
layering to manage the capacity provided by a radio link terminal for terminal for the associated Ethernet and TDM interfaces, using the
the associated Ethernet and TDM interfaces, using the principles for 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 also available 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; the IETF Radio Link Model
Model [I-D.ahlberg-ccamp-microwave-radio-link] and the ONF: Microwave [MICROWAVE-RADIO-LINK]; and the ONF Microwave Model [ONF-model], as
Modeling [ONF-model] as the basis for the definition of the detailed the basis for the definition of the detailed leafs/parameters, and it
leafs/parameters, and proposes new ones to cover identified gaps proposes new ones to cover identified gaps, which are analyzed in
which are analyzed in [RFC8432]. [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 is 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
BBE Background Block Errors ATPC: Automatic Transmitter Power Control
BER Bit Error Ratio BBE: Background Block Error
BPSK Binary Phase-Shift Keying BER: Bit Error Ratio
CM Coding Modulation BPSK: Binary Phase-Shift Keying
CT Carrier Termination CM: Coding Modulation
ES Errored Seconds CT: Carrier Termination
IF Intermediate Frequency ES: Errored Seconds
MIMO Multiple-Input Multiple-Output IF: Intermediate Frequency
RF Radio Frequency MIMO: Multiple Input Multiple Output
RLT Radio Link Terminal RF: Radio Frequency
QAM Quadrature Amplitude Modulation RLT: Radio Link Terminal
QPSK Quadrature Phase-Shift Keying QAM: Quadrature Amplitude Modulation
RTPC Remote Transmit Power Control QPSK: Quadrature Phase-Shift Keying
SES Severely Errored Seconds RTPC: Remote Transmit Power Control
TDM Time-Division Multiplexing SES: Severely Errored Seconds
UAS Unavailable Seconds TDM: Time-Division Multiplexing
XPIC Cross Polarization Interference Cancellation 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 Section 2.1 of this document. The meaning of the symbols in these
these diagrams is defined in [RFC8340]. diagrams is defined in [RFC8340].
2. Requirements Language
The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
"SHOULD", "SHOULD NOT", "RECOMMENDED", "NOT RECOMMENDED", "MAY", and
"OPTIONAL" in this document are to be interpreted as described in BCP
14 [RFC2119] [RFC8174] when, and only when, they appear in all
capitals, as shown here.
3. Microwave Radio Link YANG Data Model 2. Microwave Radio Link YANG Data Model
3.1. YANG Tree 2.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 protection-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
| +--ro status? identityref | +--ro status? identityref
skipping to change at page 7, line 19 skipping to change at page 7, line 24
| +--ro bbe? yang:counter32 | +--ro bbe? yang:counter32
| +--ro es? yang:counter32 | +--ro es? yang:counter32
| +--ro ses? yang:counter32 | +--ro ses? yang:counter32
| +--ro uas? yang:counter32 | +--ro uas? yang:counter32
+--ro radio-performance-statistics +--ro radio-performance-statistics
+--ro min-rltm? power +--ro min-rltm? power
+--ro max-rltm? power +--ro max-rltm? power
+--ro min-tltm? power +--ro min-tltm? power
+--ro max-tltm? power +--ro max-tltm? power
3.2. Explanation of the Microwave Data Model 2.2. Explanation of the Microwave Data Model
The leafs in the Interface Management Module augmented by Radio Link The leafs in the Interface Management Module augmented by RLT and CT
Terminal (RLT) and Carrier Termination (CT) are not always are not always applicable.
applicable.
"/interfaces/interface/enabled" is not applicable for RLT. Enable "/interfaces/interface/enabled" is not applicable for RLT. Enable
and disable of an interface is done in the constituent CTs. and disable of an interface is done in the constituent CTs.
The packet related measurements "in-octets", "in-unicast-pkts", "in- The packet-related measurements "in-octets", "in-unicast-pkts",
broadcast-pkts", "in-multicast-pkts", "in-discards", "in-errors", "in-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", and "out-
are not within the scope of the microwave radio link domain and errors" are not within the scope of the microwave radio link domain
therefore not applicable for RLT and CT. and therefore are not applicable for RLT and CT.
4. Microwave Radio Link YANG Module 3. Microwave Radio Link YANG Data Model
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-11-28.yang" <CODE BEGINS> file "ietf-microwave-radio-link@2019-06-19.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 iana-if-type { import iana-if-type {
prefix ianaift; prefix ianaift;
} }
import ietf-interfaces { import ietf-interfaces {
prefix if; prefix if;
reference "RFC 8343"; reference
"RFC 8343";
} }
import ietf-interface-protection { import ietf-interface-protection {
prefix ifprot; prefix ifprot;
reference "RFC XXXX"; reference
"RFC 8561";
} }
import ietf-microwave-types { import ietf-microwave-types {
prefix mw-types; prefix mw-types;
reference "RFC XXXX"; reference
"RFC 8561";
} }
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:
// RFC Ed.: replace ID-draft editors with Editors and remove
// this note
Jonas Ahlberg (jonas.ahlberg@ericsson.com);
Min Ye (amy.yemin@huawei.com);
Xi Li (Xi.Li@neclab.eu);
Daniela Spreafico (daniela.spreafico@nokia.com)
Marko Vaupotic (Marko.Vaupotic@aviatnet.com)";
Editors:
Jonas Ahlberg (jonas.ahlberg@ericsson.com)
Min Ye (amy.yemin@huawei.com)
Xi Li (Xi.Li@neclab.eu)
Daniela Spreafico (daniela.spreafico@nokia.com)
Marko Vaupotic (Marko.Vaupotic@aviatnet.com)";
description description
"This is a module for the entities in "This is a module for the entities in
a generic microwave system. a generic microwave system.
Copyright (c) 2018 IETF Trust and the persons identified as
authors of the code. All rights reserved.
Redistribution and use in source and binary forms, with or
without modification, is permitted pursuant to, and subject
to the license terms contained in, the Simplified BSD License
set forth in Section 4.c of the IETF Trust's Legal Provisions
Relating to IETF Documents
(http://trustee.ietf.org/license-info).
This version of this YANG module is part of RFC XXXX; see Copyright (c) 2019 IETF Trust and the persons identified as
the RFC itself for full legal notices. authors of the code. All rights reserved.
Copyright (c) 2018 IETF Trust and the persons identified as Redistribution and use in source and binary forms, with or
authors of the code. All rights reserved."; without modification, is permitted pursuant to, and subject
to the license terms contained in, the Simplified BSD License
set forth in Section 4.c of the IETF Trust's Legal Provisions
Relating to IETF Documents
(http://trustee.ietf.org/license-info).
This version of this YANG module is part of RFC 8561; see
the RFC itself for full legal notices.";
revision 2018-11-28 { revision 2019-06-19 {
description "Initial revision."; description
reference "RFC XXXX: A YANG Data Model for Microwave Radio Link"; "Initial revision.";
reference
"RFC 8561: A YANG Data Model for Microwave Radio Link";
} }
/* /*
* Features * Features
*/ */
feature xpic { feature xpic {
description description
"Indicates that the device supports XPIC."; "Indicates that the device supports XPIC.";
reference "ETSI TR 102 311"; reference
"ETSI TR 102 311";
} }
feature mimo { feature mimo {
description description
"Indicates that the device supports MIMO."; "Indicates that the device supports MIMO.";
reference "ETSI TR 102 311"; reference
"ETSI TR 102 311";
} }
feature tdm { feature tdm {
description description
"Indicates that the device supports TDM."; "Indicates that the device supports TDM.";
} }
/* /*
* Typedefs * Typedefs
*/ */
typedef power { typedef power {
type decimal64 { type decimal64 {
fraction-digits 1; fraction-digits 1;
} }
description description
"Type used for power values, selected and measured."; "Type used for the power values in the data nodes
for configuration or status.";
} }
/* /*
* Radio Link Terminal (RLT) * Radio Link Terminal (RLT)
*/ */
augment "/if:interfaces/if:interface" { augment "/if:interfaces/if:interface" {
when "derived-from-or-self(if:type," when "derived-from-or-self(if:type,"
+ "'ianaift:radio-link-terminal')"; + "'ianaift:microwaveRadioLinkTerminal')";
description description
"Addition of data nodes for radio link terminal to "Addition of data nodes for the 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 'microwaveRadioLinkTerminal'.";
leaf id { leaf id {
type string; type string;
description description
"Descriptive identity of the radio link terminal used by "Descriptive identity of the radio link terminal used by
far-end RLT to check that it's connected to the correct far-end RLT to check that it's connected to the correct
near-end RLT. Does not need to be configured if this check near-end RLT. Does not need to be configured if this
is not used."; 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 represents the number of bonded carrier terminations.
Y represent the number of protecting carrier Y represents the number of protecting carrier
terminations."; terminations.";
} }
leaf-list carrier-terminations { leaf-list carrier-terminations {
type if:interface-ref; type if:interface-ref;
must "derived-from-or-self(/if:interfaces/if:interface" must "derived-from-or-self(/if:interfaces/if:interface"
+ "[if:name = current()]" + "[if:name = current()]"
+ "/if:type, 'ianaift:carrier-termination')" { + "/if:type, 'ianaift:microwaveCarrierTermination')" {
description description
"The type of interface must be "The type of interface must be
'carrier-termination'."; 'microwaveCarrierTermination'.";
} }
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.";
} }
leaf-list rlp-groups { leaf-list rlp-groups {
type leafref { type leafref {
path "/mrl:radio-link-protection-groups/" path "/mrl:radio-link-protection-groups/"
+ "mrl:protection-group/mrl:name"; + "mrl:protection-group/mrl:name";
} }
description description
"A list of references to the carrier termination "A list of references to the carrier termination
groups configured for radio link protection in this groups configured for radio link protection in this
radio link terminal."; radio link terminal.";
} }
skipping to change at page 11, line 13 skipping to change at page 11, line 14
leaf-list rlp-groups { leaf-list rlp-groups {
type leafref { type leafref {
path "/mrl:radio-link-protection-groups/" path "/mrl:radio-link-protection-groups/"
+ "mrl:protection-group/mrl:name"; + "mrl:protection-group/mrl:name";
} }
description description
"A list of references to the carrier termination "A list of references to the carrier termination
groups configured for radio link protection in this groups configured for radio link protection in this
radio link terminal."; radio link terminal.";
} }
leaf-list xpic-pairs { leaf-list xpic-pairs {
if-feature xpic; if-feature "xpic";
type leafref { type leafref {
path "/mrl:xpic-pairs/mrl:xpic-pair/mrl:name"; path "/mrl:xpic-pairs/mrl:xpic-pair/mrl:name";
} }
description description
"A list of references to the XPIC pairs used in this "A list of references to the XPIC pairs used in this
radio link terminal. One pair can be used by two radio link terminal. One pair can be used by two
terminals."; terminals.";
reference "ETSI TR 102 311"; reference
"ETSI TR 102 311";
} }
leaf-list mimo-groups { leaf-list mimo-groups {
if-feature mimo; if-feature "mimo";
type leafref { type leafref {
path "/mrl:mimo-groups/mrl:mimo-group/mrl:name"; path "/mrl:mimo-groups/mrl:mimo-group/mrl:name";
} }
description description
"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;
mandatory true; mandatory true;
description description
"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 "derived-from-or-self(if:type," when "derived-from-or-self(if:type,"
+ "'ianaift:carrier-termination')"; + "'ianaift:microwaveCarrierTermination')";
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 'microwaveCarrierTermination'.";
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 and 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. Left as
Left as default value when MIMO and XPIC are not in use."; 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.";
} }
leaf tx-oper-status { leaf tx-oper-status {
type enumeration { type enumeration {
enum "off" { enum off {
description "Transmitter is off."; description
"Transmitter is off.";
} }
enum "on" { enum on {
description "Transmitter is on."; description
"Transmitter is on.";
} }
enum "standby" { enum standby {
description "Transmitter is in standby."; description
"Transmitter is in standby.";
} }
} }
config false; config false;
description description
"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.";
} }
choice freq-or-distance { choice freq-or-distance {
leaf rx-frequency { leaf rx-frequency {
type uint32; type uint32;
units "kHz"; units "kHz";
description description
"Selected receiver frequency."; "Selected receiver frequency.";
} }
leaf duplex-distance { leaf duplex-distance {
type int32; type int32;
units "kHz"; units "kHz";
skipping to change at page 13, line 42 skipping to change at page 13, line 38
"Selected receiver frequency."; "Selected receiver frequency.";
} }
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 compute
it as duplex-distance subtracted from tx-frequency." ; it as duplex-distance subtracted from tx-frequency.";
} }
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.";
} }
leaf actual-duplex-distance { leaf actual-duplex-distance {
type uint32; type uint32;
units "kHz"; units "kHz";
config false; config false;
description description
"Computed distance between Tx & Rx frequencies."; "Computed distance between Tx and Rx frequencies.";
} }
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
between adjacent channels in a radio frequency channels distance between adjacent channels in a radio
arrangement"; frequency channels arrangement";
reference "ETSI EN 302 217-1"; reference
"ETSI EN 302 217-1";
} }
leaf polarization { leaf polarization {
type enumeration { type enumeration {
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.";
} }
choice power-mode { choice power-mode {
container rtpc { container rtpc {
description description
"Remote Transmit Power Control (RTPC)."; "Remote Transmit Power Control (RTPC).";
reference "ETSI EN 302 217-1"; reference
"ETSI EN 302 217-1";
leaf maximum-nominal-power { leaf maximum-nominal-power {
type power { type power {
range "-99..99"; range "-99..99";
} }
units "dBm"; units "dBm";
mandatory true; mandatory true;
description description
"Selected output power."; "Selected output power.";
reference "ETSI EN 302 217-1";
reference
"ETSI EN 302 217-1";
} }
} }
container atpc { container atpc {
description description
"Automatic Transmit Power Control (ATPC)."; "Automatic Transmitter Power Control (ATPC).";
reference "ETSI EN 302 217-1"; reference
"ETSI EN 302 217-1";
leaf maximum-nominal-power { leaf maximum-nominal-power {
type power { type power {
range "-99..99"; range "-99..99";
} }
units "dBm"; units "dBm";
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."; minimum-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..-20"; 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 the
used in the ATPC mode."; far end, which is 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..-20"; 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 the
used in the ATPC mode."; far end, which is used in the ATPC mode.";
reference "ETSI EN 302 217-1"; reference
"ETSI EN 302 217-1";
} }
} }
mandatory true; mandatory true;
description description
"A choice of Remote Transmit Power Control (RTPC) "A choice of RTPC or ATPC.";
or Automatic Transmit Power Control (ATPC).";
} }
leaf actual-transmitted-level { leaf actual-transmitted-level {
type power { type power {
range "-99..99"; range "-99..99";
} }
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).";
reference "ETSI EN 301 129"; reference
"ETSI EN 301 129";
} }
leaf actual-received-level { leaf actual-received-level {
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";
} }
choice coding-modulation-mode { choice coding-modulation-mode {
container single { container single {
description "A single modulation order only."; description
reference "ETSI EN 302 217-1"; "A single modulation order only.";
reference
"ETSI EN 302 217-1";
leaf selected-cm { leaf selected-cm {
type identityref { type identityref {
base mw-types:coding-modulation; base mw-types:coding-modulation;
} }
mandatory true; mandatory true;
description description
"Selected the single coding/modulation."; "Selected the single coding/modulation.";
} }
} }
container adaptive { container adaptive {
description "Adaptive coding/modulation."; description
reference "ETSI EN 302 217-1"; "Adaptive coding/modulation.";
reference
"ETSI EN 302 217-1";
leaf selected-min-acm { leaf selected-min-acm {
type identityref { type identityref {
base mw-types:coding-modulation; base mw-types:coding-modulation;
} }
mandatory true; mandatory true;
description description
"Selected minimum coding/modulation. "Selected minimum coding/modulation.
Adaptive coding/modulation shall not go Adaptive coding/modulation shall not go
below this value."; below this value.";
} }
skipping to change at page 17, line 31 skipping to change at page 17, line 31
"Selected maximum coding/modulation. "Selected maximum coding/modulation.
Adaptive coding/modulation shall not go Adaptive coding/modulation shall not go
above this value."; above this value.";
} }
} }
mandatory true; mandatory true;
description description
"A selection of single or "A selection of single or
adaptive coding/modulation mode."; adaptive coding/modulation mode.";
} }
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.";
} }
leaf actual-snir { leaf actual-snir {
type decimal64 { type decimal64 {
fraction-digits 1; fraction-digits 1;
range "0..99"; range "0..99";
} }
units "dB"; units "dB";
config false; config false;
description description
"Actual signal to noise plus interference ratio. "Actual signal to noise plus the interference ratio
(0.1 dB resolution)."; (0.1 dB resolution).";
} }
leaf actual-xpi { leaf actual-xpi {
if-feature xpic; if-feature "xpic";
type decimal64 { type decimal64 {
fraction-digits 1; fraction-digits 1;
range "0..99"; range "0..99";
} }
units "dB"; units "dB";
config false; config false;
description description
"The actual carrier to cross-polar interference. "The actual carrier to cross-polar interference.
Only valid if XPIC is enabled. (0.1 dB resolution)."; Only valid if XPIC is enabled (0.1 dB resolution).";
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..-20"; 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 {
type power { type power {
range "-99..99"; range "-99..99";
} }
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 "1e-9" { enum 1e-9 {
description "Threshold at 1e-9 (10^-9)."; description
"Threshold at 1e-9 (10^-9).";
} }
enum "1e-8" { enum 1e-8 {
description "Threshold at 1e-8 (10^-8)."; description
"Threshold at 1e-8 (10^-8).";
} }
enum "1e-7" { enum 1e-7 {
description "Threshold at 1e-7 (10^-7)."; description
"Threshold at 1e-7 (10^-7).";
} }
enum "1e-6" { enum 1e-6 {
description "Threshold at 1e-6 (10^-6)."; description
"Threshold at 1e-6 (10^-6).";
} }
enum "1e-5" { enum 1e-5 {
description "Threshold at 1e-5 (10^-5)."; description
"Threshold at 1e-5 (10^-5).";
} }
enum "1e-4" { enum 1e-4 {
description "Threshold at 1e-4 (10^-4)."; description
"Threshold at 1e-4 (10^-4).";
} }
enum "1e-3" { enum 1e-3 {
description "Threshold at 1e-3 (10^-3)."; description
"Threshold at 1e-3 (10^-3).";
} }
enum "1e-2" { enum 1e-2 {
description "Threshold at 1e-2 (10^-2)."; description
"Threshold at 1e-2 (10^-2).";
} }
enum "1e-1" { enum 1e-1 {
description "Threshold at 1e-1 (10^-1)."; description
"Threshold at 1e-1 (10^-1).";
} }
} }
default "1e-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 {
description "Disables the IF Loop."; description
"Disables the IF Loop.";
} }
enum client { enum client {
description description
"Loops the signal back to the client side."; "Loops the signal back to the client side.";
} }
enum radio { enum radio {
description description
"Loops the signal back to the radio side."; "Loops the signal back to the radio side.";
} }
} }
default "disabled"; default "disabled";
description description
"Enable (client/radio) or disable (disabled) "Enable (client/radio) or disable (disabled)
the IF loop, which loops the signal back to the IF Loop, which loops the signal back to
the client side or the radio side."; the client side or the radio side.";
} }
leaf rf-loop { leaf rf-loop {
type enumeration { type enumeration {
enum disabled { enum disabled {
description "Disables the RF Loop."; description
"Disables the RF Loop.";
} }
enum client { enum client {
description description
"Loops the signal back to the client side."; "Loops the signal back to the client side.";
} }
enum radio { enum radio {
description description
"Loops the signal back to the radio side."; "Loops the signal back to the radio side.";
} }
} }
skipping to change at page 20, line 30 skipping to change at page 20, line 36
description description
"Loops the signal back to the radio side."; "Loops the signal back to the radio side.";
} }
} }
default "disabled"; default "disabled";
description description
"Enable (client/radio) or disable (disabled) "Enable (client/radio) or disable (disabled)
the RF loop, which loops the signal back to the RF loop, which loops the signal back to
the client side or the radio side."; the client side or the radio side.";
} }
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";
description description
"Maximum Tx frequency possible to use."; "Maximum Tx frequency possible to use.";
} }
leaf minimum-power { leaf minimum-power {
type power; type power;
units "dBm"; units "dBm";
description description
"The minimum output power supported."; "The minimum output power supported.";
reference "ETSI EN 302 217-1"; reference
"ETSI EN 302 217-1";
} }
leaf maximum-available-power { leaf maximum-available-power {
type power; type power;
units "dBm"; units "dBm";
description description
"The maximum output power supported."; "The maximum output power supported.";
reference "ETSI EN 302 217-1"; reference
"ETSI EN 302 217-1";
} }
leaf available-min-acm { leaf available-min-acm {
type identityref { type identityref {
base mw-types:coding-modulation; base mw-types:coding-modulation;
} }
description description
"Minimum coding-modulation possible to use."; "Minimum coding-modulation possible to use.";
} }
leaf available-max-acm { leaf available-max-acm {
type identityref { type identityref {
base mw-types:coding-modulation; base mw-types:coding-modulation;
} }
description description
"Maximum coding-modulation possible to use."; "Maximum coding-modulation possible to use.";
} }
} }
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). A BBE is an "Number of Background Block Errors (BBEs). A BBE is an
errored block not occurring as part of an SES. errored block not occurring as part of Severely Errored
Discontinuities in the value of this counter can occur Seconds (SES). Discontinuities in the value of this
at re-initialization of the management system and at counter can occur at re-initialization of the management
other times as indicated by the value of system and at other times as indicated by the value of
'discontinuity-time' in ietf-interfaces."; '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). "Number of Errored Seconds (ES). An ES is a one-second
An ES is a one-second period with one or more errored period with one or more errored blocks or at least one
blocks or at least one defect. defect. Discontinuities in the value of this counter
Discontinuities in the value of this counter can occur can occur at re-initialization of the management system
at re-initialization of the management system and at and at other times as indicated by the value of
other times as indicated by the value of
'discontinuity-time' in ietf-interfaces."; '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). "Number of SES. SES is a one-second period that 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
Discontinuities in the value of this counter can occur the value of this counter can occur at re-initialization
at re-initialization of the management system and at of the management system and at other times as indicated
other times as indicated by the value of by the value of 'discontinuity-time' in ietf-interfaces.";
'discontinuity-time' in ietf-interfaces."; reference
reference "ITU-T G.826"; "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. total time that the node has been unavailable.
Discontinuities in the value of this counter can occur Discontinuities in the value of this counter can occur
at re-initialization of the management system and at at re-initialization of the management system and at
other times as indicated by the value of other times as indicated by the value of
'discontinuity-time' in ietf-interfaces."; '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. "Minimum received power level. Discontinuities in the
Discontinuities in the value of this counter can occur value of this counter can occur at re-initialization
at re-initialization of the management system and at of the management system and at other times as
other times as indicated by the value of indicated by the value of 'discontinuity-time' in
'discontinuity-time' in ietf-interfaces."; 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. "Maximum received power level. Discontinuities in the
Discontinuities in the value of this counter can occur value of this counter can occur at re-initialization
at re-initialization of the management system and at of the management system and at other times as
other times as indicated by the value of indicated by the value of 'discontinuity-time' in
'discontinuity-time' in ietf-interfaces."; 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. "Minimum transmitted power level. Discontinuities
Discontinuities in the value of this counter can occur in the value of this counter can occur at
at re-initialization of the management system and at re-initialization of the management system and
other times as indicated by the value of at other times as indicated by the value of
'discontinuity-time' in ietf-interfaces."; '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. "Maximum transmitted power level. Discontinuities
Discontinuities in the value of this counter can occur in the value of this counter can occur at
at re-initialization of the management system and at re-initialization of the management system and
other times as indicated by the value of at other times as indicated by the value of
'discontinuity-time' in ietf-interfaces."; '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 {
description description
"Configuration of radio link protected groups (1+1) of "Configuration of radio link protected groups 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 "derived-from-or-self(/if:interfaces/if:interface" must "derived-from-or-self(/if:interfaces/if:interface"
+ "[if:name = current()]" + "[if:name = current()]"
+ "/if:type, 'ianaift:carrier-termination')" { + "/if:type, 'ianaift:microwaveCarrierTermination')" {
description description
"The type of a protection member must be "The type of a protection member must be
'carrier-termination'."; 'microwaveCarrierTermination'.";
} }
} }
refine "protection-group/working-entity" {
refine protection-group/working-entity {
must "derived-from-or-self(/if:interfaces/if:interface" must "derived-from-or-self(/if:interfaces/if:interface"
+ "[if:name = current()]" + "[if:name = current()]"
+ "/if:type, 'ianaift:carrier-termination')" { + "/if:type, 'ianaift:microwaveCarrierTermination')" {
description description
"The type of a working-entity must be "The type of a working-entity must be
'carrier-termination'."; 'microwaveCarrierTermination'.";
} }
} }
} }
} }
/* /*
* 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.";
leaf name { leaf name {
type string; type string;
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 "derived-from-or-self(/if:interfaces/if:interface" must "derived-from-or-self(/if:interfaces/if:interface"
+ "[if:name = current()]" + "[if:name = current()]"
+ "/if:type, 'ianaift:carrier-termination')" { + "/if:type, 'ianaift:microwaveCarrierTermination')" {
description description
"The type of a member must be 'carrier-termination'."; "The type of a member must be
'microwaveCarrierTermination'.";
} }
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.";
} }
} }
} }
container mimo-groups { container mimo-groups {
if-feature mimo; if-feature "mimo";
description description
"Configuration of carrier terminations "Configuration of carrier terminations
for operation in MIMO mode."; for operation in MIMO mode.";
reference "ETSI TR 102 311"; reference
"ETSI TR 102 311";
list mimo-group { list mimo-group {
key "name"; key "name";
description description
"List of carrier terminations in MIMO mode."; "List of carrier terminations in MIMO mode.";
leaf name { leaf name {
type string; type string;
description description
"Name used for identification of the MIMO group."; "Name used for identification of the MIMO group.";
} }
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 "derived-from-or-self(/if:interfaces/if:interface" must "derived-from-or-self(/if:interfaces/if:interface"
+ "[if:name = current()]" + "[if:name = current()]"
+ "/if:type, 'ianaift:carrier-termination')" { + "/if:type, 'ianaift:microwaveCarrierTermination')" {
description description
"The type of a member must be 'carrier-termination'."; "The type of a member must be
'microwaveCarrierTermination'.";
} }
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 27, line 13 skipping to change at page 27, line 5
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>
5. Interface Protection YANG Module 4. Interface Protection YANG Data Model
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 model in order to make it also
also for other interface types. available 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-11-28.yang" <CODE BEGINS> file "ietf-interface-protection@2019-06-19.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
"RFC 8343";
} }
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: Editors:
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)";
description description
"This is a module for the entities in "This is a module for the entities in
a generic interface protection mechanism. a generic interface protection mechanism.
Copyright (c) 2018 IETF Trust and the persons identified as
authors of the code. All rights reserved.
Redistribution and use in source and binary forms, with or
without modification, is permitted pursuant to, and subject
to the license terms contained in, the Simplified BSD License
set forth in Section 4.c of the IETF Trust's Legal Provisions
Relating to IETF Documents
(http://trustee.ietf.org/license-info).
This version of this YANG module is part of RFC XXXX; see Copyright (c) 2019 IETF Trust and the persons identified as
the RFC itself for full legal notices. authors of the code. All rights reserved.
Copyright (c) 2018 IETF Trust and the persons identified as Redistribution and use in source and binary forms, with or
authors of the code. All rights reserved."; without modification, is permitted pursuant to, and subject
to the license terms contained in, the Simplified BSD License
set forth in Section 4.c of the IETF Trust's Legal Provisions
Relating to IETF Documents
(http://trustee.ietf.org/license-info).
This version of this YANG module is part of RFC 8561; see
the RFC itself for full legal notices.";
revision 2018-11-28 { revision 2019-06-19 {
description "Initial revision."; description
reference "RFC XXXX: A YANG Data Model for Microwave Radio Link"; "Initial revision.";
reference
"RFC 8561: 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
"protection architecture type"; "protection architecture type";
reference "ITU-T G.808.1"; reference
"ITU-T G.808.1";
} }
identity one-plus-one-type { identity one-plus-one-type {
base protection-architecture-type; base protection-architecture-type;
description description
"1+1, One interface protects "1+1; one interface protects
another one interface."; another one interface.";
reference "ITU-T G.808.1"; reference
"ITU-T G.808.1";
} }
identity one-to-n-type { identity one-to-n-type {
base protection-architecture-type; base protection-architecture-type;
description description
"1:N, One interface protects "1:N; one interface protects
n other interfaces."; n other interfaces.";
reference "ITU-T G.808.1"; reference
"ITU-T G.808.1";
} }
/* /*
* Protection states identities * Protection states identities
*/ */
identity protection-states { identity protection-states {
description description
"Identities describing the status of the protection, "Identities describing the status of the protection
in a group of interfaces configured in in a group of interfaces configured in
a protection mode."; a protection mode.";
} }
identity unprotected { identity unprotected {
base protection-states; base protection-states;
description "Not protected"; description
"Not protected.";
} }
identity protected { identity protected {
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 Groups * Protection Groups
*/ */
grouping protection-groups { grouping protection-groups {
description description
"Configuration of protected groups (1+1) of interfaces "Configuration of protected groups of interfaces
providing protection for each other. More than one protected providing protection for each other. More than one
group per higher-layer-interface is allowed."; protected group per higher-layer interface is allowed.";
list protection-group { list protection-group {
key "name"; key "name";
description description
"List of protected groups of interfaces "List of protected groups of interfaces
in a higher-layer-interface."; in a higher-layer interface.";
leaf name { leaf name {
type string; type string;
description description
"Name used for identification of the protection group"; "Name used for identification of the protection group.";
} }
leaf protection-architecture-type { leaf protection-architecture-type {
type identityref { type identityref {
base protection-architecture-type; base protection-architecture-type;
} }
default "ifprot:one-plus-one-type"; default "ifprot:one-plus-one-type";
description description
"The type of protection architecture used, e.g. one "The type of protection architecture used, e.g., one
interface protecting one or several other interfaces."; interface protecting one or several other interfaces.";
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 that 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.";
} }
leaf revertive-wait-to-restore { leaf revertive-wait-to-restore {
when "../operation-type = 'revertive'"; when "../operation-type = 'revertive'";
type uint16; type uint16;
units "seconds"; units "seconds";
default "0"; default "0";
description description
"The time to wait before switching back to the working "The time to wait before switching back to the working
interface if operation-type is revertive."; interface if operation-type is revertive.";
reference "ITU-T G.808.1"; reference
"ITU-T G.808.1";
} }
leaf hold-off-timer { leaf hold-off-timer {
type uint16; type uint16;
units "milliseconds"; units "milliseconds";
default "0"; default "0";
description description
"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; 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 manual-switch-working { action manual-switch-working {
description description
"A switch action initiated by an operator command. "A switch action initiated by an operator command.
It switches normal traffic signal to the working It switches a normal traffic signal to the working
transport entity."; transport entity.";
reference "ITU-T G.808.1"; reference
"ITU-T G.808.1";
} }
action manual-switch-protection { action manual-switch-protection {
description description
"A switch action initiated by an operator command. "A switch action initiated by an operator command.
It switches normal traffic signal to the protection It switches a normal traffic signal to the protection
transport entity."; transport entity.";
reference "ITU-T G.808.1"; reference
"ITU-T G.808.1";
} }
action forced-switch { action forced-switch {
description description
"A switch action initiated by an operator command. "A switch action initiated by an operator command.
It switches normal traffic signal to the protection It switches a normal traffic signal to the protection
transport entity and forces it to remain on that transport entity and forces it to remain on that
entity even when criteria for switching back to entity even when criteria for switching back to
the original entity are fulfilled."; the original entity are fulfilled.";
reference "ITU-T G.808.1"; reference
"ITU-T G.808.1";
} }
action lockout-of-protection { action lockout-of-protection {
description description
"A switch action temporarily disables access to the "A switch action temporarily disables access to the
protection transport entity for all signals."; protection transport entity for all signals.";
reference "ITU-T G.808.1"; reference
"ITU-T G.808.1";
} }
action freeze { action freeze {
description description
"A switch action temporarily prevents any switch action "A switch action temporarily prevents any switch action
to be taken and, as such, freezes the current state. to be taken and, as such, freezes the current state.
Until the freeze is cleared, additional near-end external Until the freeze is cleared, additional near-end external
commands are rejected and fault condition changes and commands are rejected, and fault condition changes and
received APS messages are ignored.."; received Automatic Protection-Switching (APS) messages
reference "ITU-T G.808.1"; are ignored.";
reference
"ITU-T G.808.1";
} }
action exercise { action exercise {
description description
"A switch action to test if the APS communication is "A switch action to test if the APS communication is
operating correctly. It is lower priority than any 'real' operating correctly. It is lower priority than any 'real'
switch request.."; switch request.";
reference "ITU-T G.808.1"; reference
"ITU-T G.808.1";
} }
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 5. Microwave Types YANG Data Model
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-11-28.yang" <CODE BEGINS> file "ietf-microwave-types@2019-06-19.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;
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: Editors:
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)";
description description
"This module contains a collection of YANG data types "This module contains a collection of YANG data types
considered generally useful for microwave interfaces. considered generally useful for microwave interfaces.
Copyright (c) 2018 IETF Trust and the persons identified as Copyright (c) 2019 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
without modification, is permitted pursuant to, and subject
to the license terms contained in, the Simplified BSD License
set forth in Section 4.c of the IETF Trust's Legal Provisions
Relating to IETF Documents
(http://trustee.ietf.org/license-info).
This version of this YANG module is part of RFC XXXX; see Redistribution and use in source and binary forms, with or
the RFC itself for full legal notices. without modification, is permitted pursuant to, and subject
to the license terms contained in, the Simplified BSD License
set forth in Section 4.c of the IETF Trust's Legal Provisions
Relating to IETF Documents
(http://trustee.ietf.org/license-info).
Copyright (c) 2018 IETF Trust and the persons identified as This version of this YANG module is part of RFC 8561; see
authors of the code. All rights reserved."; the RFC itself for full legal notices.";
revision 2018-11-28 { revision 2019-06-19 {
description "Initial revision."; description
reference "RFC XXXX: A YANG Data Model for Microwave Radio Link"; "Initial revision.";
reference
"RFC 8561: A YANG Data Model for Microwave Radio Link";
} }
/* /*
* Radio-link-terminal mode identities * Radio-link-terminal mode identities
*/ */
identity rlt-mode { identity rlt-mode {
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 represents the number of bonded carrier terminations.
Y represent the number of protecting carrier Y represents the number of protecting carrier
terminations."; terminations.";
} }
identity one-plus-zero { identity one-plus-zero {
base rlt-mode; base rlt-mode;
description description
"1 carrier termination only."; "1 carrier termination only.";
} }
identity one-plus-one { identity one-plus-one {
base rlt-mode; base rlt-mode;
description description
"1 carrier termination "1 carrier termination
and 1 protecting carrier termination."; and 1 protecting carrier termination.";
} }
identity two-plus-zero { identity two-plus-zero {
base rlt-mode; base rlt-mode;
description description
"2 bonded carrier terminations."; "2 bonded carrier terminations.";
} }
/* /*
* Coding and modulation identities * Coding and modulation identities
skipping to change at page 39, line 39 skipping to change at page 39, line 35
"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
connection."; connection.";
} }
identity E1 { identity E1 {
base tdm-type; base tdm-type;
description description
"E1 connection, 2.048 Mbit/s."; "E1 connection, 2.048 Mbit/s.";
} }
identity STM-1 { identity STM-1 {
base tdm-type; base tdm-type;
skipping to change at page 40, line 7 skipping to change at page 40, line 4
description description
"E1 connection, 2.048 Mbit/s."; "E1 connection, 2.048 Mbit/s.";
} }
identity STM-1 { identity STM-1 {
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 6. Security Considerations
The YANG modules specified in this document define schemas for data The YANG data models specified in this document define schemas for
that is designed to be accessed via network management protocols such data that is designed to be accessed via network management protocols
as NETCONF [RFC6241] or RESTCONF [RFC8040]. The lowest NETCONF layer such as NETCONF [RFC6241] or RESTCONF [RFC8040]. The lowest NETCONF
is the secure transport layer, and the mandatory-to-implement secure layer is the secure transport layer, and the mandatory-to-implement
transport is Secure Shell (SSH) [RFC6242]. The lowest RESTCONF layer secure transport is Secure Shell (SSH) [RFC6242]. The lowest
is HTTPS, and the mandatory-to-implement secure transport is TLS RESTCONF layer is HTTPS, and the mandatory-to-implement secure
[RFC8446]. transport is TLS [RFC8446].
The NETCONF access control model [RFC8341] provides the means to The Network Configuration Access Control Model (NACM) [RFC8341]
restrict access for particular NETCONF or RESTCONF users to a provides the means to restrict access for particular NETCONF or
preconfigured subset of all available NETCONF or RESTCONF protocol RESTCONF users to a preconfigured subset of all available NETCONF or
operations and content. RESTCONF protocol operations and content.
There are a number of data nodes defined in these YANG modules that There are a number of data nodes defined in these YANG data models
are writable/creatable/deletable (i.e., config true, which is the that are writable/creatable/deletable (i.e., config true, which is
default). These data nodes may be considered sensitive or vulnerable the default). These data nodes may be considered sensitive or
in some network environments. Write operations (e.g., edit-config) vulnerable in some network environments. Write operations (e.g.,
to these data nodes without proper protection can have a negative edit-config) to these data nodes without proper protection can have a
effect on network operations. These are the subtrees and data nodes negative effect on network operations. These are the subtrees and
and their sensitivity/vulnerability: data nodes and their sensitivity/vulnerability:
Interfaces of type radio-link-terminal: Interfaces of type microwaveRadioLinkTerminal:
/if:interfaces/if:interface/mode, /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 data nodes represent the configuration of the radio-link- These data nodes represent the configuration of the radio link
terminal and they need to match the configuration of the radio-link- terminal, and they need to match the configuration of the radio link
terminal on the other side of the radio link. Unauthorized access to terminal on the other side of the radio link. Unauthorized access to
these data 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 microwaveCarrierTermination:
/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 they 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 data node represents the configuration of the protection of This data node represents the configuration of the protection of
carrier terminations. Unauthorized access to this data node could carrier terminations. Unauthorized access to this data node 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 data node represents the XPIC configuration of a pair carriers. This data node represents the XPIC configuration of a pair of
Unauthorized access to this data node could interrupt the ability to carriers. Unauthorized access to this data node could interrupt the
forward traffic. ability to forward traffic.
MIMO: MIMO:
/mimo-groups: /mimo-groups:
This data node represents the MIMO configuration of multiple This data node represents the MIMO configuration of multiple
carriers. Unauthorized access to this data node could interrupt the carriers. Unauthorized access to this data node could interrupt the
ability to forward traffic. ability to forward traffic.
Some of the RPC operations in this YANG data model may be considered
sensitive or vulnerable in some network environments. It is thus
important to control access to these operations. These are the
operations and their sensitivity/vulnerability:
Radio link protection:
/radio-link-protection-groups/protection-group/manual-switch-working,
/radio-link-protection-groups/protection-group/
manual-switch-protection,
/radio-link-protection-groups/protection-group/forced-switch,
/radio-link-protection-groups/protection-group/lockout-of-protection,
/radio-link-protection-groups/protection-group/freeze,
/radio-link-protection-groups/protection-group/exercise, and
/radio-link-protection-groups/protection-group/clear
These data nodes represent actions that might have an impact on the
configuration of the protection of carrier terminations.
Unauthorized access to these data nodes could interrupt the ability
to forward traffic or remove the ability to perform a necessary
protection switch.
The security considerations of [RFC8343] also apply to this document. The security considerations of [RFC8343] also apply to this document.
8. IANA Considerations 7. IANA Considerations
It is proposed that IANA should assign new URIs from the "IETF XML IANA has assigned new URIs from the "IETF XML Registry" [RFC3688] as
Registry" [RFC3688] as follows: 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.
URI: urn:ietf:params:xml:ns:yang:ietf-microwave-types URI: urn:ietf:params:xml:ns:yang:ietf-microwave-types
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 "YANG IANA has recorded YANG module names in the "YANG Module Names"
Module Names" registry [RFC6020] as follows: registry [RFC6020] as follows:
Name: ietf-microwave-radio-link Name: ietf-microwave-radio-link
Maintained by IANA?: N Maintained by IANA?: N
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 8561
Name: ietf-interface-protection Name: ietf-interface-protection
Maintained by IANA?: N Maintained by IANA?: N
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 8561
Name: ietf-microwave-types Name: ietf-microwave-types
Maintained by IANA?: N Maintained by IANA?: N
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
Reference: RFC XXXX Reference: RFC 8561
It is proposed that IANA should register a new IANAifType TBD1 for IANA has registered the following ifTypes in "ifType definitions"
the interface type radio-link-terminal and a new IANAifType TBD2 for under [IANA-SMI]:
the interface type carrier-termination at [IFTYPE-IANA-REGISTRY].
9. References Decimal Name Description
------- ------------ -------------------------------
295 microwaveCarrierTermination air interface of a single
microwave carrier
9.1. Normative References 296 microwaveRadioLinkTerminal radio link interface for one
or several aggregated microwave
carriers
[IFTYPE-IANA-REGISTRY] 8. References
"Internet Assigned Numbers Authority, "ifType
Definitions"",
<http://www.iana.org/assignments/smi-numbers>.
[RFC2119] Bradner, S., "Key words for use in RFCs to Indicate 8.1. Normative References
Requirement Levels", BCP 14, RFC 2119,
DOI 10.17487/RFC2119, March 1997, [IANA-SMI] IANA, "Structure of Management Information (SMI) Numbers
<https://www.rfc-editor.org/info/rfc2119>. (MIB Module Registrations)",
<https://www.iana.org/assignments/smi-numbers>.
[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, DOI 10.17487/RFC3688, January 2004,
<https://www.rfc-editor.org/info/rfc3688>. <https://www.rfc-editor.org/info/rfc3688>.
[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>.
skipping to change at page 44, line 5 skipping to change at page 44, line 31
<https://www.rfc-editor.org/info/rfc6991>. <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, DOI 10.17487/RFC7224, May 2014, RFC 7224, DOI 10.17487/RFC7224, May 2014,
<https://www.rfc-editor.org/info/rfc7224>. <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,
<https://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, DOI 10.17487/RFC8341, March 2018,
<https://www.rfc-editor.org/info/rfc8341>. <https://www.rfc-editor.org/info/rfc8341>.
[RFC8343] Bjorklund, M., "A YANG Data Model for Interface [RFC8343] Bjorklund, M., "A YANG Data Model for Interface
Management", RFC 8343, DOI 10.17487/RFC8343, March 2018, Management", RFC 8343, DOI 10.17487/RFC8343, March 2018,
<https://www.rfc-editor.org/info/rfc8343>. <https://www.rfc-editor.org/info/rfc8343>.
[RFC8446] Rescorla, E., "The Transport Layer Security (TLS) Protocol [RFC8446] Rescorla, E., "The Transport Layer Security (TLS) Protocol
Version 1.3", RFC 8446, DOI 10.17487/RFC8446, August 2018, Version 1.3", RFC 8446, DOI 10.17487/RFC8446, August 2018,
<https://www.rfc-editor.org/info/rfc8446>. <https://www.rfc-editor.org/info/rfc8446>.
9.2. Informative References 8.2. Informative References
[EN301129] [EN301129] ETSI, "Transmission and Multiplexing (TM); Digital Radio
"Transmission and Multiplexing (TM); Digital Radio Relay Relay Systems (DRRS); Synchronous Digital Hierarchy (SDH);
Systems (DRRS); Synchronous Digital Hierarchy (SDH);
System performance monitoring parameters of SDH DRRS", EN System performance monitoring parameters of SDH DRRS", EN
301 129 V1.1.2 , May 1995. 301 129 V1.1.2, May 1999.
[EN302217-1] [EN302217-1]
"Fixed Radio Systems; Characteristics and requirements for ETSI, "Fixed Radio Systems; Characteristics and
point-to-point equipment and antennas; Part 1: Overview, requirements for point-to-point equipment and antennas;
common characteristics and system-dependent requirements", Part 1: Overview, common characteristics and system-
EN 302 217-1 V3.0.5 , June 2016. dependent requirements", EN 302 217-1 V3.1.0, May 2017.
[EN302217-2] [EN302217-2]
"Fixed Radio Systems; Characteristics and requirements for ETSI, "Fixed Radio Systems; Characteristics and
point to-point equipment and antennas; Part 2: Digital requirements for point to-point equipment and antennas;
systems operating in frequency bands from 1 GHz to 86 GHz; Part 2: Digital systems operating in frequency bands from
Harmonised Standard covering the essential requirements of 1 GHz to 86 GHz; Harmonised Standard covering the
article 3.2 of Directive 2014/53/EU", EN 302 217-2 essential requirements of article 3.2 of Directive
V3.1.1 , May 2017. 2014/53/EU", EN 302 217-2 V3.1.1, May 2017.
[G.808.1] "SERIES G: TRANSMISSION SYSTEMS AND MEDIA, DIGITAL SYSTEMS [G.808.1] ITU-T, "SERIES G: TRANSMISSION SYSTEMS AND MEDIA, DIGITAL
AND NETWORKS; Digital networks ; General aspects Generic SYSTEMS AND NETWORKS; Digital networks ; General aspects
protection switching ; Linear trail and subnetwork Generic protection switching ; Linear trail and subnetwork
protection", ITU-T Rec. G.808.1 , May 2014. protection", ITU-T Recommendation G.808.1, May 2014.
[G.826] "SERIES G: TRANSMISSION SYSTEMS AND MEDIA, DIGITAL SYSTEMS [G.826] ITU-T, "SERIES G: TRANSMISSION SYSTEMS AND MEDIA, DIGITAL
AND NETWORKS; Digital networks ; Quality and availability SYSTEMS AND NETWORKS; Digital networks - Quality and
targets End-to-end error performance parameters and availability targets; End-to-end error performance
objectives for international, constant bit-rate digital parameters and objectives for international, constant bit-
paths and connections", ITU-T Rec. G.826 , December 2002. rate digital paths and connections", ITU-T
Recommendation G.826, December 2002.
[I-D.ahlberg-ccamp-microwave-radio-link] [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 Work in Progress, draft-ahlberg-ccamp-microwave-radio-
progress), May 2016. link-01, May 2016.
[ONF-model] [ONF-model]
"Microwave Information Model", version 1.0 , December ONF, "Microwave Information Model", TR-532, version 1.0,
2016, December 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 [RFC8432] Ahlberg, J., Ed., Ye, M., Ed., Li, X., Contreras, LM., and
CJ. Bernardos, "A Framework for Management and Control of CJ. Bernardos, "A Framework for Management and Control of
Microwave and Millimeter Wave Interface Parameters", Microwave and Millimeter Wave Interface Parameters",
RFC 8432, DOI 10.17487/RFC8432, October 2018, RFC 8432, DOI 10.17487/RFC8432, October 2018,
<https://www.rfc-editor.org/info/rfc8432>. <https://www.rfc-editor.org/info/rfc8432>.
[TR102311] [TR102311] ETSI, "Fixed Radio Systems; Point-to-point equipment;
"Fixed Radio Systems; Point-to-point equipment; Specific Specific aspects of the spatial frequency reuse method",
aspects of the spatial frequency reuse method", ETSI TR 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 instances using the
YANG module defined in this draft. The examples are not intended as YANG data model defined in this document. The examples are not
a complete module for 1+0 and 2+0 configuration. intended as 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 shows a 1+0 example. The following instance Figure 1: 1+0 Example
shows the 1+0 configuration of Near End node.
Figure 1 shows a 1+0 example. The following instance shows the 1+0
configuration of the Near End node.
"interface": [ "interface": [
{ {
"name": "RLT-A", "name": "RLT-A",
"description": "Radio Link Terminal A", "description": "Radio Link Terminal A",
"type": "radio-link-terminal", "type": "microwaveRadioLinkTerminal",
"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-connections": [
"tdm-type": "E1", "tdm-type": "E1",
"tdm-connections": "4" "tdm-connections": "4"
] ]
}, },
{ {
"name": "RLT-A:CT-1", "name": "RLT-A:CT-1",
"description": "Carrier Termination 1", "description": "Carrier Termination 1",
"type": "carrier-termination", "type": "microwaveCarrierTermination",
"carrier-id": "A", "carrier-id": "A",
"tx-enabled": true, "tx-enabled": true,
"tx-frequency": 10728000, "tx-frequency": 10728000,
"duplex-distance": 644000, "duplex-distance": 644000,
"channel-separation": 28, "channel-separation": 28000,
"polarization": not-specified, "polarization": not-specified,
"rtpc": { "rtpc": {
"maximum-nominal-power": 20 "maximum-nominal-power": 20
}, },
"single": { "single": {
"selected-cm": "qam-512" "selected-cm": "qam-512"
} }
} }
] ]
A.2. 2+0 instance A.2. 2+0 Instance
Figure A-2 shows a 2+0 example. Figure 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 |
| | | | | | | |
| | | | | | | |
| +-----------+ | | +-----------+ | | +-----------+ | | +-----------+ |
skipping to change at page 47, line 47 skipping to change at page 49, line 34
| +-----------+ | | +-----------+ | | +-----------+ | | +-----------+ |
| | | | 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
The following instance shows the 2+0 configuration of Figure 2: 2+0 Example
Near End node.
The following instance shows the 2+0 configuration of the Near End
node.
"interface": [ "interface": [
{ {
"name": "RLT-A", "name": "RLT-A",
"description": "Radio Link Terminal A", "description": "Radio Link Terminal A",
"type": "radio-link-terminal", "type": "microwaveRadioLinkTerminal",
"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-connections": [
"tdm-type": "E1", "tdm-type": "E1",
"tdm-connections": "4" "tdm-connections": "4"
] ]
}, },
{ {
"name": "RLT-A:CT-1", "name": "RLT-A:CT-1",
"description": "Carrier Termination 1", "description": "Carrier Termination 1",
"type": "carrier-termination", "type": "microwaveCarrierTermination",
"carrier-id": "A", "carrier-id": "A",
"tx-enabled": true, "tx-enabled": true,
"tx-frequency": 10728000, "tx-frequency": 10728000,
"duplex-distance": 644000, "duplex-distance": 644000,
"channel-separation": 28, "channel-separation": 28000,
"polarization": not-specified, "polarization": not-specified,
"rtpc": { "rtpc": {
"maximum-nominal-power": 20 "maximum-nominal-power": 20
}, },
"single": { "single": {
"selected-cm": "qam-512" "selected-cm": "qam-512"
} }
}, },
{ {
"name": "RLT-A:CT-2", "name": "RLT-A:CT-2",
"description": "Carrier Termination 2", "description": "Carrier Termination 2",
"type": "carrier-termination", "type": "microwaveCarrierTermination",
"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": 28000,
"polarization": not-specified, "polarization": not-specified,
"rtpc": { "rtpc": {
"maximum-nominal-power": 20 "maximum-nominal-power": 20
}, },
"single": { "single": {
"selected-cm": "qam-512" "selected-cm": "qam-512"
} }
} }
] ]
A.3. 2+0 XPIC instance A.3. 2+0 XPIC Instance
The following instance shows the XPIC configuration of The following instance shows the XPIC configuration of the Near End
Near End node. node.
"interface": [ "interface": [
{ {
"name": "RLT-A", "name": "RLT-A",
"description": "Radio Link Terminal A", "description": "Radio Link Terminal A",
"type": "radio-link-terminal", "type": "microwaveRadioLinkTerminal",
"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"
], ],
"xpic-pairs": [ "xpic-pairs": [
"RLT-A:CT-1", "RLT-A:CT-1",
"RLT-A:CT-2" "RLT-A:CT-2"
], ],
"tdm-connections": [ "tdm-connections": [
"tdm-type": "E1", "tdm-type": "E1",
"tdm-connections": "4" "tdm-connections": "4"
] ]
}, },
{ {
"name": "RLT-A:CT-1", "name": "RLT-A:CT-1",
"description": "Carrier Termination 1", "description": "Carrier Termination 1",
"type": "carrier-termination", "type": "microwaveCarrierTermination",
"carrier-id": "A", "carrier-id": "A",
"tx-enabled": true, "tx-enabled": true,
"tx-frequency": 10728000, "tx-frequency": 10728000,
"duplex-distance": 644000, "duplex-distance": 644000,
"channel-separation": 28, "channel-separation": 28000,
"polarization": not-specified, "polarization": not-specified,
"rtpc": { "rtpc": {
"maximum-nominal-power": 20 "maximum-nominal-power": 20
}, },
"single": { "single": {
"selected-cm": "qam-512" "selected-cm": "qam-512"
} }
}, },
{ {
"name": "RLT-A:CT-2", "name": "RLT-A:CT-2",
"description": "Carrier Termination 2", "description": "Carrier Termination 2",
"type": "carrier-termination", "type": "microwaveCarrierTermination",
"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": 28000,
"polarization": not-specified, "polarization": not-specified,
"rtpc": { "rtpc": {
"maximum-nominal-power": 20 "maximum-nominal-power": 20
}, },
"single": { "single": {
"selected-cm": "qam-512" "selected-cm": "qam-512"
} }
} }
] ]
Appendix B. Contributors 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 Japan
Email: k-kawada@ah.jp.nec.com Email: k-kawada@ah.jp.nec.com
Carlos J. Bernardos Carlos J. Bernardos
skipping to change at page 51, line 15 skipping to change at page 53, line 15
Authors' Addresses Authors' Addresses
Jonas Ahlberg Jonas Ahlberg
Ericsson AB Ericsson AB
Lindholmspiren 11 Lindholmspiren 11
Goteborg 417 56 Goteborg 417 56
Sweden Sweden
Email: jonas.ahlberg@ericsson.com Email: jonas.ahlberg@ericsson.com
Ye Min Min Ye
Huawei Technologies Huawei Technologies
No.1899, Xiyuan Avenue No.1899, Xiyuan Avenue
Chengdu 611731 Chengdu 611731
P.R.China China
Email: amy.yemin@huawei.com Email: amy.yemin@huawei.com
Xi Li Xi Li
NEC Laboratories Europe NEC Laboratories Europe
Kurfursten-Anlage 36 Kurfursten-Anlage 36
Heidelberg 69115 Heidelberg 69115
Germany Germany
Email: Xi.Li@neclab.eu Email: Xi.Li@neclab.eu
 End of changes. 355 change blocks. 
645 lines changed or deleted 624 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/