]> Ericsson

scott.mansfield@ericsson.com

Ericsson AB

Lindholmspiren 11 Goteborg 417 56 Sweden jonas.ahlberg@ericsson.com

Huawei Technologies

No.1899, Xiyuan Avenue Chengdu 611731 China amy.yemin@huawei.com

Nokia - IT

Via Energy Park, 14 Vimercate (MI) 20871 Italy daniela.spreafico@nokia.com

SIAE

danilo.pala@saiemic.com

Routing CCAMP Working Group Internet-Draft This document defines a YANG data model for control and management of radio link interfaces and their connectivity to packet (typically Ethernet) interfaces in a microwave/millimeter wave node. The data nodes for management of the interface protection functionality is broken out into a separate and generic YANG data model in order to make it available for other interface types as well. This document obsoletes RFC 8561. About This Document The latest revision of this draft can be found at . Status information for this document may be found at . Discussion of this document takes place on the CCAMP Working Group mailing list (), which is archived at . Source for this draft and an issue tracker can be found at .

Introduction This document defines a YANG data model for management and control of the radio link interface(s) and the relationship to packet (typically Ethernet) and/or Time-Division Multiplexing (TDM) interfaces in a microwave/millimeter wave node. The ETSI EN 302 217 series defines the characteristics and requirements of microwave/millimeter wave equipment and antennas. Specifically, ETSI EN 302 217-2 specifies the essential parameters for systems operating from 1.4 GHz to 86 GHz. The data model includes configuration and state data according to the new Network Management Datastore Architecture . The design of the data model follows the framework for management and control of microwave and millimeter wave interface parameters defined in . This framework identifies the need and the scope of the YANG data model, use cases, and requirements that the model needs to support. Moreover, it provides a detailed gap analysis to identify the missing parameters and functionalities of the existing and established models to support the specified use cases and requirements, and based on that, it recommends how the gaps should be filled with the development of the new model. According to the conclusion of the gap analysis, the structure of the data model is based on the structure defined in , and it augments to align with the same structure for management of the packet interfaces. More specifically, the model will include interface layering to manage the capacity provided by a radio link terminal for the associated Ethernet and TDM interfaces, using the principles for interface layering described in as a basis. The data nodes for management of the interface protection functionality is broken out into a separate and generic YANG data module in order to make it also available for other interface types. The designed YANG data model uses established microwave equipment and radio standards, such as ETSI EN 302 217-2; the IETF Radio Link Model ; and the ONF Microwave Model , as the basis for the definition of the detailed leafs/parameters, and it proposes new ones to cover identified gaps, which are analyzed in .

Terminology and Definitions The following terms are used in this document: Carrier Termination (CT) is an interface for the capacity provided over the air by a single carrier. It is typically defined by its transmitting and receiving frequencies. Radio Link Terminal (RLT) is an interface providing packet capacity and/or TDM capacity to the associated Ethernet and/or TDM interfaces in a node and is used for setting up a transport service over a microwave/millimeter wave link. The following acronyms are used in this document: ACM Adaptive Coding Modulation ATPC Automatic Transmitter Power Control BBE Background Block Error BER Bit Error Ratio BPSK Binary Phase-Shift Keying CM Coding Modulation CT Carrier Termination ES Errored Seconds IF Intermediate Frequency MIMO Multiple Input Multiple Output RF Radio Frequency RLT Radio Link Terminal QAM Quadrature Amplitude Modulation QPSK Quadrature Phase-Shift Keying RTPC Remote Transmit Power Control SES Severely Errored Seconds TDM Time-Division Multiplexing UAS Unavailable Seconds XPIC Cross Polarization Interference Cancellation

Tree Structure A simplified graphical representation of the data model is used in of this document. The meaning of the symbols in these diagrams is defined in .

Prefixes in Data Node Names In this document, names of data nodes and other data model objects are prefixed using the standard prefix associated with the corresponding YANG imported modules, as shown in . Prefixes for imported YANG modules

Prefix	YANG Module	Reference
mrl	ietf-microwave-radio-link	This document
yang	ietf-yang-types
ianaift	iana-if-type
if	ietf-interfaces
ifprot	ietf-interface-protection	This document
mw-types	ietf-microwave-types	This document

# Microwave Radio Link YANG Data Model

YANG Tree /radio-link-protection-groups/protection-group/name +--rw xpic-pairs* -> /xpic-pairs/xpic-pair/name | {xpic}? +--rw mimo-groups* -> /mimo-groups/mimo-group/name | {mimo}? +--rw tdm-connections* [tdm-type] {tdm}? +--rw tdm-type identityref +--rw tdm-connections uint16 augment /if:interfaces/if:interface: +--rw carrier-id? string +--rw tx-enabled? boolean +--ro tx-oper-status? enumeration +--rw tx-frequency uint32 +--rw (freq-or-distance) | +--:(rx-frequency) | | +--rw rx-frequency? uint32 | +--:(duplex-distance) | +--rw duplex-distance? int32 +--ro actual-rx-frequency? uint32 +--ro actual-duplex-distance? uint32 +--rw channel-separation uint32 +--rw polarization? enumeration +--rw (power-mode) | +--:(rtpc) | | +--rw rtpc | | +--rw maximum-nominal-power power | +--:(atpc) | +--rw atpc | +--rw maximum-nominal-power power | +--rw atpc-lower-threshold power | +--rw atpc-upper-threshold power +--ro actual-transmitted-level? power +--ro actual-received-level? power +--rw (coding-modulation-mode) | +--:(single) | | +--rw single | | +--rw selected-cm identityref | +--:(adaptive) | +--rw adaptive | +--rw selected-min-acm identityref | +--rw selected-max-acm identityref +--ro actual-tx-cm? identityref +--ro actual-snir? decimal64 +--ro actual-xpi? decimal64 {xpic}? +--rw ct-performance-thresholds | +--rw received-level-alarm-threshold? power | +--rw transmitted-level-alarm-threshold? power | +--rw ber-alarm-threshold? enumeration +--rw if-loop? enumeration +--rw rf-loop? enumeration +--ro capabilities | +--ro min-tx-frequency? uint32 | +--ro max-tx-frequency? uint32 | +--ro min-rx-frequency? uint32 | +--ro max-rx-frequency? uint32 | +--ro minimum-power? power | +--ro maximum-available-power? power | +--ro available-min-acm? identityref | +--ro available-max-acm? identityref | +--ro acm-profile-list* | [profile-channel-separation-id profile-coding-modulation-id] | +--ro profile-channel-separation-id uint32 | +--ro profile-coding-modulation-id identityref | +--ro modulation-scheme? uint8 | +--ro nominal-tx-capacity? uint32 | +--ro support-as-fixed-modulation? boolean | +--ro max-tx-power? power | +--ro min-tx-power? power | +--ro lower-acm-profile-ptr | | +--ro profile-coding-modulation-id-ref? leafref | | +--ro profile-channel-separation-id-ref? leafref | +--ro upper-acm-profile-ptr | +--ro profile-coding-modulation-id-ref? leafref | +--ro profile-channel-separation-id-ref? leafref +--ro error-performance-statistics | +--ro bbe? yang:counter32 | +--ro es? yang:counter32 | +--ro ses? yang:counter32 | +--ro uas? yang:counter32 +--ro radio-performance-statistics +--ro min-rltm? power +--ro max-rltm? power +--ro min-tltm? power +--ro max-tltm? power ]]>

Explanation of the Microwave Data Model The leafs in the Interface Management Module augmented by RLT and CT are not always applicable. "/interfaces/interface/enabled" is not applicable for RLT. Enable and disable of an interface is done in the constituent CTs. The packet-related measurements "in-octets", "in-unicast-pkts", "in-broadcast-pkts", "in-multicast-pkts", "in-discards", "in-errors", "in-unknown-protos", "out-octets", "out-unicast-pkts", "out- broadcast-pkts", "out-multicast-pkts", "out-discards", and "out- errors" are not within the scope of the microwave radio link domain and therefore are not applicable for RLT and CT.

Microwave Radio Link YANG Data Model This module imports typedefs and modules from , and , and it references , , , and . 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 "This is a module for the entities in a generic microwave system. Copyright (c) 2024 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 Revised 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 the RFC itself for full legal notices."; // RFC Ed.: replace XXXX with actual RFC number and remove // this note // replace the revision date with the module publication date // the format is (year-month-day) revision 2024-03-03 { description "pretty printing"; reference "RFC XXX: A YANG Data Model for Microwave Radio Link"; } revision 2023-10-06 { description "To add the summary of the changes in this revision: - more updates related to git Issue #13 and #16. - git Issue #13 and #16 and discussion updates for acm-profile - Updated with proposal for BCA."; reference "RFC XXX: A YANG Data Model for Microwave Radio Link"; } revision 2019-06-19 { description "Initial revision."; reference "RFC 8561: A YANG Data Model for Microwave Radio Link"; } /* * Features */ feature xpic { description "Indicates that the device supports XPIC."; reference "ETSI TR 102 311"; } feature mimo { description "Indicates that the device supports MIMO."; reference "ETSI TR 102 311"; } feature tdm { description "Indicates that the device supports TDM."; } /* * Typedefs */ typedef power { type decimal64 { fraction-digits 1; } description "Type used for the power values in the data nodes for configuration or status."; } grouping acm-profile { description "acm-profile"; leaf modulation-scheme { type uint8; description "It is the logarithm base two of the number of points in the transmitted constellation. E.G.: value would be 2 for 4QAM, 10 fo 1024QAM, and 12 for 4096QAM."; } leaf nominal-tx-capacity { type uint32; description "The nominal radio link capacity associated to this acm-profile."; } leaf support-as-fixed-modulation { type boolean; description "True when the profile can be used in single coding-modulation-mode."; } leaf max-tx-power { type power; description "The maximum transmitted power when the carrier termination is operating this acm-profile. Used to configure transmitted power."; } leaf min-tx-power { type power; description "The minimum transmitted power when the carrier termination is operating this acm-profile. Used to configure transmitted power."; } } /* * Radio Link Terminal (RLT) */ augment "/if:interfaces/if:interface" { when "derived-from-or-self(if:type," + "'ianaift:microwaveRadioLinkTerminal')"; description "Addition of data nodes for the radio link terminal to the standard Interface data model, for interfaces of the type 'microwaveRadioLinkTerminal'."; leaf id { type string; description "Descriptive identity of the radio link terminal used by far-end RLT to check that it's connected to the correct near-end RLT. Does not need to be configured if this check is not used."; } choice mode-option { mandatory true; description "A description of the mode in which the radio link terminal is configured in terms of: - number of bonded carrier terminations; - number of protecting carrier terminations."; leaf mode { type identityref { base mw-types:rlt-mode; } mandatory true; status deprecated; description "A description of the mode in which the radio link terminal is configured. The format is X plus Y. X represents the number of bonded carrier terminations. Y represents the number of protecting carrier terminations. This attribute has been deprecated: the rlt-mode container which provide flexible definitions of number of bonded carriers and protecting carriers should be used instead."; } container rlt-mode { description "This grouping provides a flexible definition of number of bonded carriers and protecting carriers of a radio link."; uses mw-types:rlt-mode; } } leaf-list carrier-terminations { type if:interface-ref; must "derived-from-or-self(/if:interfaces/if:interface" + "[if:name = current()]" + "/if:type, 'ianaift:microwaveCarrierTermination')" { description "The type of interface must be 'microwaveCarrierTermination'."; } min-elements 1; description "A list of references to carrier terminations included in the radio link terminal."; } leaf-list rlp-groups { type leafref { path "/mrl:radio-link-protection-groups/" + "mrl:protection-group/mrl:name"; } description "A list of references to the carrier termination groups configured for radio link protection in this radio link terminal."; } leaf-list xpic-pairs { if-feature "xpic"; type leafref { path "/mrl:xpic-pairs/mrl:xpic-pair/mrl:name"; } description "A list of references to the XPIC pairs used in this radio link terminal. One pair can be used by two terminals."; reference "ETSI TR 102 311"; } leaf-list mimo-groups { if-feature "mimo"; type leafref { path "/mrl:mimo-groups/mrl:mimo-group/mrl:name"; } description "A reference to the MIMO group used in this radio link terminal. One group can be used by more than one terminal."; reference "ETSI TR 102 311"; } list tdm-connections { if-feature "tdm"; key "tdm-type"; description "A list stating the number of active TDM connections of a specified tdm-type that is configured to be supported by the RLT."; leaf tdm-type { type identityref { base mw-types:tdm-type; } description "The type of TDM connection, which also indicates the supported capacity."; } leaf tdm-connections { type uint16; mandatory true; description "Number of connections of the specified type."; } } } /* * Carrier Termination */ augment "/if:interfaces/if:interface" { when "derived-from-or-self(if:type," + "'ianaift:microwaveCarrierTermination')"; description "Addition of data nodes for carrier termination to the standard Interface data model, for interfaces of the type 'microwaveCarrierTermination'."; leaf carrier-id { type string; default "A"; description "ID of the carrier (e.g., A, B, C, or D). Used in XPIC and MIMO configurations to check that the carrier termination is connected to the correct far-end carrier termination. Should be the same carrier ID on both sides of the hop. Left as default value when MIMO and XPIC are not in use."; } leaf tx-enabled { type boolean; default "false"; description "Disables (false) or enables (true) the transmitter. Only applicable when the interface is enabled (interface:enabled = true); otherwise, it's always disabled."; } leaf tx-oper-status { type enumeration { enum off { description "Transmitter is off."; } enum on { description "Transmitter is on."; } enum standby { description "Transmitter is in standby."; } } config false; description "Shows the operative status of the transmitter."; } leaf tx-frequency { type uint32; units "kHz"; mandatory true; description "Selected transmitter frequency."; } choice freq-or-distance { mandatory true; description "A choice to configure rx-frequency directly or compute it as duplex-distance subtracted from tx-frequency."; leaf rx-frequency { type uint32; units "kHz"; description "Selected receiver frequency."; } leaf duplex-distance { type int32; units "kHz"; description "Distance between transmitter and receiver frequencies."; } } leaf actual-rx-frequency { type uint32; units "kHz"; config false; description "Computed receiver frequency."; } leaf actual-duplex-distance { type uint32; units "kHz"; config false; description "Computed distance between Tx and Rx frequencies."; } leaf channel-separation { type uint32; units "kHz"; mandatory true; description "The amount of bandwidth allocated to a carrier. The distance between adjacent channels in a radio frequency channels arrangement"; reference "ETSI EN 302 217-1"; } leaf polarization { type enumeration { enum horizontal { description "Horizontal polarization."; } enum vertical { description "Vertical polarization."; } enum not-specified { description "Polarization not specified."; } } default "not-specified"; description "Polarization - a textual description for info only."; } choice power-mode { mandatory true; description "A choice of RTPC or ATPC."; container rtpc { description "Remote Transmit Power Control (RTPC)."; reference "ETSI EN 302 217-1"; leaf maximum-nominal-power { type power { range "-99..99"; } units "dBm"; mandatory true; description "Selected output power."; reference "ETSI EN 302 217-1"; } } container atpc { description "Automatic Transmitter Power Control (ATPC)."; reference "ETSI EN 302 217-1"; leaf maximum-nominal-power { type power { range "-99..99"; } units "dBm"; mandatory true; description "Selected maximum output power. Minimum output power is the same as the system capability, minimum-power."; reference "ETSI EN 302 217-1"; } leaf atpc-lower-threshold { type power { range "-99..-20"; } units "dBm"; must 'current() <= ../atpc-upper-threshold'; mandatory true; description "The lower threshold for the input power at the far end, which is used in the ATPC mode."; reference "ETSI EN 302 217-1"; } leaf atpc-upper-threshold { type power { range "-99..-20"; } units "dBm"; mandatory true; description "The upper threshold for the input power at the far end, which is used in the ATPC mode."; reference "ETSI EN 302 217-1"; } } } leaf actual-transmitted-level { type power { range "-99..99"; } units "dBm"; config false; description "Actual transmitted power level (0.1 dBm resolution)."; reference "ETSI EN 301 129"; } leaf actual-received-level { type power { range "-99..-20"; } units "dBm"; config false; description "Actual received power level (0.1 dBm resolution)."; reference "ETSI EN 301 129"; } choice coding-modulation-mode { mandatory true; description "A selection of single or adaptive coding/modulation mode."; container single { description "A single modulation order only."; reference "ETSI EN 302 217-1"; leaf selected-cm { type identityref { base mw-types:coding-modulation; } mandatory true; description "Selected the single coding/modulation."; } } container adaptive { description "Adaptive coding/modulation."; reference "ETSI EN 302 217-1"; leaf selected-min-acm { type identityref { base mw-types:coding-modulation; } mandatory true; description "Selected minimum coding/modulation. Adaptive coding/modulation shall not go below this value."; } leaf selected-max-acm { type identityref { base mw-types:coding-modulation; } mandatory true; description "Selected maximum coding/modulation. Adaptive coding/modulation shall not go above this value."; } } } leaf actual-tx-cm { type identityref { base mw-types:coding-modulation; } config false; description "Actual coding/modulation in transmitting direction."; } leaf actual-snir { type decimal64 { fraction-digits 1; range "0..99"; } units "dB"; config false; description "Actual signal to noise plus the interference ratio (0.1 dB resolution)."; } leaf actual-xpi { if-feature "xpic"; type decimal64 { fraction-digits 1; range "0..99"; } units "dB"; config false; description "The actual carrier to cross-polar interference. Only valid if XPIC is enabled (0.1 dB resolution)."; reference "ETSI TR 102 311"; } container ct-performance-thresholds { description "Specification of thresholds for when alarms should be sent and cleared for various performance counters."; leaf received-level-alarm-threshold { type power { range "-99..-20"; } units "dBm"; default "-99"; description "An alarm is sent when the received power level is below the specified threshold."; reference "ETSI EN 301 129"; } leaf transmitted-level-alarm-threshold { type power { range "-99..99"; } units "dBm"; default "-99"; description "An alarm is sent when the transmitted power level is below the specified threshold."; reference "ETSI EN 301 129"; } leaf ber-alarm-threshold { type enumeration { enum 1e-9 { description "Threshold at 1e-9 (10^-9)."; } enum 1e-8 { description "Threshold at 1e-8 (10^-8)."; } enum 1e-7 { description "Threshold at 1e-7 (10^-7)."; } enum 1e-6 { description "Threshold at 1e-6 (10^-6)."; } enum 1e-5 { description "Threshold at 1e-5 (10^-5)."; } enum 1e-4 { description "Threshold at 1e-4 (10^-4)."; } enum 1e-3 { description "Threshold at 1e-3 (10^-3)."; } enum 1e-2 { description "Threshold at 1e-2 (10^-2)."; } enum 1e-1 { description "Threshold at 1e-1 (10^-1)."; } } default "1e-6"; description "Specification of at which BER an alarm should be raised."; reference "ETSI EN 302 217-1"; } } leaf if-loop { type enumeration { enum disabled { description "Disables the IF Loop."; } enum client { description "Loops the signal back to the client side."; } enum radio { description "Loops the signal back to the radio side."; } } default "disabled"; description "Enable (client/radio) or disable (disabled) the IF Loop, which loops the signal back to the client side or the radio side."; } leaf rf-loop { type enumeration { enum disabled { description "Disables the RF Loop."; } enum client { description "Loops the signal back to the client side."; } enum radio { description "Loops the signal back to the radio side."; } } default "disabled"; description "Enable (client/radio) or disable (disabled) the RF loop, which loops the signal back to the client side or the radio side."; } container capabilities { config false; description "Capabilities of the installed equipment and some selected configurations."; leaf min-tx-frequency { type uint32; units "kHz"; description "Minimum Tx frequency possible to use."; } leaf max-tx-frequency { type uint32; units "kHz"; description "Maximum Tx frequency possible to use."; } leaf min-rx-frequency { type uint32; units "kHz"; description "Minimum Rx frequency possible to use."; } leaf max-rx-frequency { type uint32; units "kHz"; description "Maximum Tx frequency possible to use."; } leaf minimum-power { type power; units "dBm"; description "The minimum output power supported."; reference "ETSI EN 302 217-1"; } leaf maximum-available-power { type power; units "dBm"; description "The maximum output power supported."; reference "ETSI EN 302 217-1"; } leaf available-min-acm { type identityref { base mw-types:coding-modulation; } description "Minimum coding-modulation possible to use."; } leaf available-max-acm { type identityref { base mw-types:coding-modulation; } description "Maximum coding-modulation possible to use."; } list acm-profile-list { key "profile-channel-separation-id " + "profile-coding-modulation-id"; description "A list of acm-profile. Each acm-profile is identified by a channel-separation and coding-modulation values as supported by the carrier termination and defines the parameter's values of each transmission acm profile. Basically, the list contains all acm profiles supported by the device. Profiles are organized into profile chains for each different channel separation value available. The chains are formed by the lower-acm-profile-ptr and upper-acm-profile-ptr pointers. The sequence in the list reflects the sequence of profiles that are operated by the device according to the fading conditions, from the clear sky down to the persistent rain, and vice versa. The channel-separation and selected-cm configuration parameters (or the selected-min-acm/selected-max-acm pair) must address one of the profiles in the list."; leaf profile-channel-separation-id { type uint32; description "Uniquely identifies the acm profile (together with 'profile-coding-modulation-id'). It could be used to allow the configuration of the channel-separation value."; } leaf profile-coding-modulation-id { type identityref { base mw-types:coding-modulation; } description "Uniquely identifies the acm profile (together with 'profile-channel-separation-id'). It could be used to allow the configuration of the selected-cm (single mode) or selected-min-acm/selected-max-acm (adaptive mode)."; } uses acm-profile; container lower-acm-profile-ptr { description "Together with the upper-acm-profile-ptr parameters it creates a chain of acm profiles related to a specific channel separation value. Specifically it references the next lower acm-profile, while upper-acm-profile-ptr references the next higher profile. The lowest profile in the chain, shall not instantiate this container. The acm-profile-list can contain multiple chains related to different channel separation values supported by the device."; leaf profile-coding-modulation-id-ref { type leafref { path "../../../acm-profile-list" + "/profile-coding-modulation-id"; } description "A reference to an acm-profile to give an order in acm-profile-list. This is the reference to the 'profile-coding-modulation-id' key of the next lower acm-profile in the list respect to the current one."; } leaf profile-channel-separation-id-ref { type leafref { path "../../.." + "/acm-profile-list[profile-coding-modulation-id=" + "current()/../profile-coding-modulation-id-ref]" + "/profile-channel-separation-id"; } description "A reference to an acm-profile to give an order in acm-profile-list. This is the reference to the 'profile-channel-separation-id' key of the next lower acm-profile in the list respect to the current one."; } } container upper-acm-profile-ptr { description "Together with the lower-acm-profile-ptr parameters it creates a chain of acm profiles related to a specific channel separation value. Specifically it references the next higher acm-profile, while lower-acm-profile-ptr references the next lower profile. The highest profile in the chain, shall not instantiate this container. The acm-profile-list can contain multiple chains related to different channel separation values supported by the device."; leaf profile-coding-modulation-id-ref { type leafref { path "../../../acm-profile-list" + "/profile-coding-modulation-id"; } description "A reference to an acm-profile to give an order in acm-profile-list. This is the reference to the 'profile-coding-modulation-id' key of the next higher acm-profile in the list respect to the current one."; } leaf profile-channel-separation-id-ref { type leafref { path "../../.." + "/acm-profile-list[profile-coding-modulation-id=" + "current()/../profile-coding-modulation-id-ref]" + "/profile-channel-separation-id"; } description "A reference to an acm-profile to give an order in acm-profile-list. This is the reference to the 'profile-channel-separation-id' key of the next higher acm-profile in the list respect to the current one."; } } } } container error-performance-statistics { config false; description "ITU-T G.826 error performance statistics relevant for a microwave/millimeter wave carrier."; leaf bbe { type yang:counter32; units "number of block errors"; description "Number of Background Block Errors (BBEs). A BBE is an errored block not occurring as part of Severely Errored Seconds (SES). Discontinuities in the value of this counter can occur at re-initialization of the management system and at other times as indicated by the value of 'discontinuity-time' in ietf-interfaces."; reference "ITU-T G.826"; } leaf es { type yang:counter32; units "seconds"; description "Number of Errored Seconds (ES). An ES is a one-second period with one or more errored blocks or at least one defect. Discontinuities in the value of this counter can occur at re-initialization of the management system and at other times as indicated by the value of 'discontinuity-time' in ietf-interfaces."; reference "ITU-T G.826"; } leaf ses { type yang:counter32; units "seconds"; description "Number of SES. SES is a one-second period that contains equal or more than 30% errored blocks or at least one defect. SES is a subset of ES. Discontinuities in the value of this counter can occur at re-initialization of the management system and at other times as indicated by the value of 'discontinuity-time' in ietf-interfaces."; reference "ITU-T G.826"; } leaf uas { type yang:counter32; units "seconds"; description "Number of Unavailable Seconds (UAS); that is, the total time that the node has been unavailable. Discontinuities in the value of this counter can occur at re-initialization of the management system and at other times as indicated by the value of 'discontinuity-time' in ietf-interfaces."; reference "ITU-T G.826"; } } container radio-performance-statistics { config false; description "ETSI EN 301 129 radio physical interface statistics relevant for a carrier termination."; leaf min-rltm { type power { range "-99..-20"; } units "dBm"; description "Minimum received power level. Discontinuities in the value of this counter can occur at re-initialization of the management system and at other times as indicated by the value of 'discontinuity-time' in ietf-interfaces."; reference "ETSI EN 301 129"; } leaf max-rltm { type power { range "-99..-20"; } units "dBm"; description "Maximum received power level. Discontinuities in the value of this counter can occur at re-initialization of the management system and at other times as indicated by the value of 'discontinuity-time' in ietf-interfaces."; reference "ETSI EN 301 129"; } leaf min-tltm { type power { range "-99..99"; } units "dBm"; description "Minimum transmitted power level. Discontinuities in the value of this counter can occur at re-initialization of the management system and at other times as indicated by the value of 'discontinuity-time' in ietf-interfaces."; reference "ETSI EN 301 129"; } leaf max-tltm { type power { range "-99..99"; } units "dBm"; description "Maximum transmitted power level. Discontinuities in the value of this counter can occur at re-initialization of the management system and at other times as indicated by the value of 'discontinuity-time' in ietf-interfaces."; reference "ETSI EN 301 129"; } } } /* * Radio Link Protection Groups */ container radio-link-protection-groups { description "Configuration of radio link protected groups of carrier terminations in a radio link. More than one protected group per radio link terminal is allowed."; uses ifprot:protection-groups { refine "protection-group/members" { must "derived-from-or-self(/if:interfaces/if:interface" + "[if:name = current()]" + "/if:type, 'ianaift:microwaveCarrierTermination')" { description "The type of a protection member must be 'microwaveCarrierTermination'."; } } refine "protection-group/working-entity" { must "derived-from-or-self(/if:interfaces/if:interface" + "[if:name = current()]" + "/if:type, 'ianaift:microwaveCarrierTermination')" { description "The type of a working-entity must be 'microwaveCarrierTermination'."; } } } } /* * XPIC & MIMO groups - Configuration data nodes */ container xpic-pairs { if-feature "xpic"; description "Configuration of carrier termination pairs for operation in XPIC mode."; reference "ETSI TR 102 311"; list xpic-pair { key "name"; description "List of carrier termination pairs in XPIC mode."; leaf name { type string; description "Name used for identification of the XPIC pair."; } leaf enabled { type boolean; default "false"; description "Enable(true)/disable(false) XPIC"; } leaf-list members { type if:interface-ref; must "derived-from-or-self(/if:interfaces/if:interface" + "[if:name = current()]" + "/if:type, 'ianaift:microwaveCarrierTermination')" { description "The type of a member must be 'microwaveCarrierTermination'."; } min-elements 2; max-elements 2; description "Association to XPIC pairs used in the radio link terminal."; } } } container mimo-groups { if-feature "mimo"; description "Configuration of carrier terminations for operation in MIMO mode."; reference "ETSI TR 102 311"; list mimo-group { key "name"; description "List of carrier terminations in MIMO mode."; leaf name { type string; description "Name used for identification of the MIMO group."; } leaf enabled { type boolean; default "false"; description "Enable(true)/disable(false) MIMO."; } leaf-list members { type if:interface-ref; must "derived-from-or-self(/if:interfaces/if:interface" + "[if:name = current()]" + "/if:type, 'ianaift:microwaveCarrierTermination')" { description "The type of a member must be 'microwaveCarrierTermination'."; } min-elements 2; description "Association to a MIMO group if used in the radio link terminal."; } } } } ]]>

Interface Protection YANG Data Model The data nodes for management of the interface protection functionality is broken out from the Microwave Radio Link Module into a separate and generic YANG data model in order to make it also available for other interface types. This module imports modules from , and it references . 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 "This is a module for the entities in a generic interface protection mechanism. Copyright (c) 2024 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 the RFC itself for full legal notices."; // RFC Ed.: replace XXXX with actual RFC number and remove // this note // replace the revision date with the module publication date // the format is (year-month-day) revision 2024-03-03 { description "Updating reference to RFC XXXX. - pretty printing"; reference "RFC XXX: A YANG Data Model for Microwave Radio Link"; } revision 2020-10-06 { description "Updating reference to RFC XXXX."; reference "RFC XXX: A YANG Data Model for Microwave Radio Link"; } revision 2019-06-19 { description "Initial revision."; reference "RFC 8561: A YANG Data Model for Microwave Radio Link"; } /* * Protection architecture type identities */ identity protection-architecture-type { description "protection architecture type"; reference "ITU-T G.808.1"; } identity one-plus-one-type { base protection-architecture-type; description "1+1; one interface protects another one interface."; reference "ITU-T G.808.1"; } identity one-to-n-type { base protection-architecture-type; description "1:N; one interface protects n other interfaces."; reference "ITU-T G.808.1"; } /* * Protection states identities */ identity protection-states { description "Identities describing the status of the protection in a group of interfaces configured in a protection mode."; } identity unprotected { base protection-states; description "Not protected."; } identity protected { base protection-states; description "Protected."; } identity unable-to-protect { base protection-states; description "Unable to protect."; } /* * Protection Groups */ grouping protection-groups { description "Configuration of protected groups of interfaces providing protection for each other. More than one protected group per higher-layer interface is allowed."; list protection-group { key "name"; description "List of protected groups of interfaces in a higher-layer interface."; action manual-switch-working { description "A switch action initiated by an operator command. It switches a normal traffic signal to the working transport entity."; reference "ITU-T G.808.1"; } action manual-switch-protection { description "A switch action initiated by an operator command. It switches a normal traffic signal to the protection transport entity."; reference "ITU-T G.808.1"; } action forced-switch { description "A switch action initiated by an operator command. It switches a normal traffic signal to the protection transport entity and forces it to remain on that entity even when criteria for switching back to the original entity are fulfilled."; reference "ITU-T G.808.1"; } action lockout-of-protection { description "A switch action temporarily disables access to the protection transport entity for all signals."; reference "ITU-T G.808.1"; } action freeze { description "A switch action temporarily prevents any switch action to be taken and, as such, freezes the current state. Until the freeze is cleared, additional near-end external commands are rejected, and fault condition changes and received Automatic Protection-Switching (APS) messages are ignored."; reference "ITU-T G.808.1"; } action exercise { description "A switch action to test if the APS communication is operating correctly. It is lower priority than any 'real' switch request."; reference "ITU-T G.808.1"; } action clear { description "An action clears all switch commands."; reference "ITU-T G.808.1"; } leaf name { type string; description "Name used for identification of the protection group."; } leaf protection-architecture-type { type identityref { base protection-architecture-type; } default "ifprot:one-plus-one-type"; description "The type of protection architecture used, e.g., one interface protecting one or several other interfaces."; reference "ITU-T G.808.1"; } leaf-list members { type if:interface-ref; min-elements 2; description "Association to a group of interfaces configured for protection and used by a higher-layer interface."; } leaf operation-type { type enumeration { enum non-revertive { description "In non-revertive operation, the traffic does not return to the working interface if the switch requests are terminated."; reference "ITU-T G.808.1"; } enum revertive { description "In revertive operation, the traffic always returns to (or remains on) the working interface if the switch requests are terminated."; reference "ITU-T G.808.1"; } } default "non-revertive"; description "The type of protection operation, i.e., revertive or non-revertive operation."; } leaf-list working-entity { when "../operation-type = 'revertive'"; type if:interface-ref; min-elements 1; description "The interfaces that the traffic normally should be transported over when there is no need to use the protecting interface."; } leaf revertive-wait-to-restore { when "../operation-type = 'revertive'"; type uint16; units "seconds"; default "0"; description "The time to wait before switching back to the working interface if operation-type is revertive."; reference "ITU-T G.808.1"; } leaf hold-off-timer { type uint16; units "milliseconds"; default "0"; description "Time interval after the detection of a fault and its confirmation as a condition requiring the protection- switching procedure."; reference "ITU-T G.808.1"; } leaf status { type identityref { base protection-states; } config false; description "Status of the protection in a group of interfaces configured in a protection mode."; reference "ITU-T G.808.1"; } } } } ]]>

Microwave Types YANG Data Model This module defines a collection of common data types using the YANG data modeling language. These common types are designed to be imported by other modules defined in the microwave area. 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 "This module contains a collection of YANG data types considered generally useful for microwave interfaces. Copyright (c) 2024 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 Revised 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."; // RFC Ed.: replace XXXX with actual RFC number and remove // this note // replace the revision date with the module publication date // the format is (year-month-day) revision 2024-03-03 { description "pretty printing"; reference "RFC XXX: A YANG Data Model for Microwave Radio Link"; } revision 2023-10-06 { description "To add the summary of the changes in this revision: - Changed name for 8PSK. - Updated for 8PSK - Updated with proposal for BCA."; reference "RFC XXX: A YANG Data Model for Microwave Radio Link"; } revision 2019-06-19 { description "Initial revision."; reference "RFC 8561: A YANG Data Model for Microwave Radio Link"; } /* * Radio-link-terminal mode identities */ identity rlt-mode { status deprecated; description "A description of the mode in which the radio link terminal is configured. The format is X plus Y. X represents the number of bonded carrier terminations. Y represents the number of protecting carrier terminations."; } identity one-plus-zero { base rlt-mode; status deprecated; description "1 carrier termination only."; } identity one-plus-one { base rlt-mode; status deprecated; description "1 carrier termination and 1 protecting carrier termination."; } identity two-plus-zero { base rlt-mode; status deprecated; description "2 bonded carrier terminations."; } /* * Coding and modulation identities */ identity coding-modulation { description "The coding and modulation schemes."; } identity half-bpsk { base coding-modulation; description "Half BPSK coding and modulation scheme."; } identity half-bpsk-strong { base half-bpsk; description "Half BPSK strong coding and modulation scheme."; } identity half-bpsk-light { base half-bpsk; description "Half BPSK light coding and modulation scheme."; } identity bpsk { base coding-modulation; description "BPSK coding and modulation scheme."; } identity bpsk-strong { base bpsk; description "BPSK strong coding and modulation scheme."; } identity bpsk-light { base bpsk; description "BPSK light coding and modulation scheme."; } identity qpsk { base coding-modulation; description "QPSK coding and modulation scheme."; } identity psk-8 { base coding-modulation; description "8PSK coding and modulation scheme."; } identity qam-4 { base coding-modulation; description "4 QAM coding and modulation scheme."; } identity qam-4-strong { base qam-4; description "4 QAM strong coding and modulation scheme."; } identity qam-4-light { base qam-4; description "4 QAM light coding and modulation scheme."; } identity qam-16 { base coding-modulation; description "16 QAM coding and modulation scheme."; } identity qam-16-strong { base qam-16; description "16 QAM strong coding and modulation scheme."; } identity qam-16-light { base qam-16; description "16 QAM light coding and modulation scheme."; } identity qam-32 { base coding-modulation; description "32 QAM coding and modulation scheme."; } identity qam-32-strong { base qam-32; description "32 QAM strong coding and modulation scheme."; } identity qam-32-light { base qam-32; description "32 QAM light coding and modulation scheme."; } identity qam-64 { base coding-modulation; description "64 QAM coding and modulation scheme."; } identity qam-64-strong { base qam-64; description "64 QAM strong coding and modulation scheme."; } identity qam-64-light { base qam-64; description "64 QAM light coding and modulation scheme."; } identity qam-128 { base coding-modulation; description "128 QAM coding and modulation scheme."; } identity qam-128-strong { base qam-128; description "128 QAM strong coding and modulation scheme."; } identity qam-128-light { base qam-128; description "128 QAM light coding and modulation scheme."; } identity qam-256 { base coding-modulation; description "256 QAM coding and modulation scheme."; } identity qam-256-strong { base qam-256; description "256 QAM strong coding and modulation scheme."; } identity qam-256-light { base qam-256; description "256 QAM light coding and modulation scheme."; } identity qam-512 { base coding-modulation; description "512 QAM coding and modulation scheme."; } identity qam-512-strong { base qam-512; description "512 QAM strong coding and modulation scheme."; } identity qam-512-light { base qam-512; description "512 QAM light coding and modulation scheme."; } identity qam-1024 { base coding-modulation; description "1024 QAM coding and modulation scheme."; } identity qam-1024-strong { base qam-1024; description "1024 QAM strong coding and modulation scheme."; } identity qam-1024-light { base qam-1024; description "1024 QAM light coding and modulation scheme."; } identity qam-2048 { base coding-modulation; description "2048 QAM coding and modulation scheme."; } identity qam-2048-strong { base qam-2048; description "2048 QAM strong coding and modulation scheme."; } identity qam-2048-light { base qam-2048; description "2048 QAM light coding and modulation scheme."; } identity qam-4096 { base coding-modulation; description "4096 QAM coding and modulation scheme."; } identity qam-4096-strong { base qam-4096; description "4096 QAM strong coding and modulation scheme."; } identity qam-4096-light { base qam-4096; description "4096 QAM light coding and modulation scheme."; } /* * TDM-type identities */ identity tdm-type { description "A description of the type of TDM connection, also indicating the supported capacity of the connection."; } identity E1 { base tdm-type; description "E1 connection, 2.048 Mbit/s."; } identity STM-1 { base tdm-type; description "STM-1 connection, 155.52 Mbit/s."; } /* * Radio-link-terminal mode grouping */ grouping rlt-mode { description "This grouping provides a flexible definition of number of bonded carriers and protecting carriers of a radio link."; leaf num-bonded-carriers { type uint32; mandatory true; description "Number of bonded carriers."; } leaf num-protecting-carriers { type uint32; mandatory true; description "Number of protecting carriers."; } } } ]]>

Security Considerations The YANG data models specified in this document define schemas for data that is designed to be accessed via network management protocols such as NETCONF or RESTCONF . The lowest NETCONF layer is the secure transport layer, and the mandatory-to-implement secure transport is Secure Shell (SSH) . The lowest RESTCONF layer is HTTPS, and the mandatory-to-implement secure transport is TLS . The Network Configuration Access Control Model (NACM) provides the means to restrict access for particular NETCONF or RESTCONF users to a preconfigured subset of all available NETCONF or RESTCONF protocol operations and content. There are a number of data nodes defined in these YANG data models that are writable/creatable/deletable (i.e., config true, which is the default). These data nodes may be considered sensitive or vulnerable in some network environments. Write operations (e.g., edit-config) to these data nodes without proper protection can have a negative effect on network operations. These are the subtrees and data nodes and their sensitivity/vulnerability: Interfaces of type microwaveRadioLinkTerminal: These data nodes represent 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 these data nodes could interrupt the ability to forward traffic. Interfaces of type microwaveCarrierTermination: These data nodes represent 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 these data nodes could interrupt the ability to forward traffic. Radio link protection: This data node represents the configuration of the protection of carrier terminations. Unauthorized access to this data node could interrupt the ability to forward traffic or remove the ability to perform a necessary protection switch. XPIC: This data node represents the XPIC configuration of a pair of carriers. Unauthorized access to this data node could interrupt the ability to forward traffic. MIMO: This data node represents the MIMO configuration of multiple carriers. Unauthorized access to this data node could interrupt the 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: 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 also apply to this document.

IANA Considerations No IANA Considerations in this update.

References Normative References This document defines a YANG data model for control and management of radio link interfaces and their connectivity to packet (typically Ethernet) interfaces in a microwave/millimeter wave node. The data nodes for management of the interface protection functionality is broken out into a separate and generic YANG data model in order to make it available for other interface types as well. This document defines a YANG data model for the management of network interfaces. It is expected that interface-type-specific data models augment the generic interfaces data model defined in this document. The data model includes definitions for configuration and system state (status information and counters for the collection of statistics). The YANG data model in this document conforms to the Network Management Datastore Architecture (NMDA) defined in RFC 8342. This document obsoletes RFC 7223. This document introduces a collection of common data types to be used with the YANG data modeling language. This document obsoletes RFC 6021. This document defines the initial version of the iana-if-type YANG module. The Network Configuration Protocol (NETCONF) defined in this document provides mechanisms to install, manipulate, and delete the configuration of network devices. It uses an Extensible Markup Language (XML)-based data encoding for the configuration data as well as the protocol messages. The NETCONF protocol operations are realized as remote procedure calls (RPCs). This document obsoletes RFC 4741. [STANDARDS-TRACK] This document describes an HTTP-based protocol that provides a programmatic interface for accessing data defined in YANG, using the datastore concepts defined in the Network Configuration Protocol (NETCONF). This document describes a method for invoking and running the Network Configuration Protocol (NETCONF) within a Secure Shell (SSH) session as an SSH subsystem. This document obsoletes RFC 4742. [STANDARDS-TRACK] This document specifies version 1.3 of the Transport Layer Security (TLS) protocol. TLS allows client/server applications to communicate over the Internet in a way that is designed to prevent eavesdropping, tampering, and message forgery. This document updates RFCs 5705 and 6066, and obsoletes RFCs 5077, 5246, and 6961. This document also specifies new requirements for TLS 1.2 implementations. The standardization of network configuration interfaces for use with the Network Configuration Protocol (NETCONF) or the RESTCONF protocol requires a structured and secure operating environment that promotes human usability and multi-vendor interoperability. There is a need for standard mechanisms to restrict NETCONF or RESTCONF protocol access for particular users to a preconfigured subset of all available NETCONF or RESTCONF protocol operations and content. This document defines such an access control model. This document obsoletes RFC 6536. Informative References IANA ETSI ETSI ETSI ITU-T ITU-T ONF ETSI Datastores are a fundamental concept binding the data models written in the YANG data modeling language to network management protocols such as the Network Configuration Protocol (NETCONF) and RESTCONF. This document defines an architectural framework for datastores based on the experience gained with the initial simpler model, addressing requirements that were not well supported in the initial model. This document updates RFC 7950. The unification of control and management of microwave radio link interfaces is a precondition for seamless multi-layer networking and automated network provisioning and operation. This document describes the required characteristics and use cases for control and management of radio link interface parameters using a YANG data model. The purpose is to create a framework to identify the necessary information elements and define a YANG data model for control and management of the radio link interfaces in a microwave node. Some parts of the resulting model may be generic and could also be used by other technologies, e.g., Ethernet technology. This document captures the current syntax used in YANG module tree diagrams. The purpose of this document is to provide a single location for this definition. This syntax may be updated from time to time based on the evolution of the YANG language.

Changes from RFC 8561 To be added in a future revision of this draft.

Example: 1+0 and 2+0 Configuration Instances This section gives simple examples of 1+0 and 2+0 instances using the YANG data model defined in this document. The examples are not intended as a complete module for 1+0 and 2+0 configuration.

1+0 Instance

1+0 Example | | Carrier | | | |Termination| | | |Termination| | | | 1 | | | | 1 | | | +-----------+ | | +-----------+ | | | | | | | | | +---------------+ +---------------+ \--- Microwave Node ---/ \--- Microwave Node ---/ ]]>

shows a 1+0 example. The following instance shows the 1+0 configuration of the Near End node.

2+0 Instance shows a 2+0 example.

2+0 Example | | Carrier | | | |Termination| | | |Termination| | | | 1 | | | | 1 | | | +-----------+ | | +-----------+ | | | | | | +-----------+ | | +-----------+ | | | | | Carrier B | | | | | | Carrier | |<--------->| | Carrier | | | |Termination| | | |Termination| | | | 2 | | | | 2 | | | +-----------+ | | +-----------+ | | | | | +---------------+ +---------------+ \--- Microwave Node ---/ \--- Microwave Node ---/ ]]>

The following instance shows the 2+0 configuration of the Near End node.

2+0 XPIC Instance The following instance shows the XPIC configuration of the Near End node. ~~~~

Acknowledgments This document was prepared using the kramdown RFC tool written and maintained by Carsten Bormann. Thanks to Martin Thomson for the github integration of the kramdown RFC tool and for the aasvg tool which is used for the ascii to SVG conversion.

Contributors Huawei Technologies

italo.busi@huawei.com

NEC Corporation

1753, Shimonumabe Nakahara-ku Kawasaki, Kanagawa 211-8666 Japan k-kawada@ah.jp.nec.com

Universidad Carlos III de Madrid

Av. Universidad, 30 Leganes, Madrid 28911 Spain cjbc@it.uc3m.es

Aviat Networks

Motnica 9 Trzin-Ljubljana 1236 Slovenia Marko.Vaupotic@Aviatnet.com

NEC Laboratories Europe

Kurfursten-Anlage 36 Heidelberg 69115 Germany Xi.Li@neclab.eu