Internet-Draft Microwave Radio Link YANG March 2024
Mansfield, et al. Expires 4 September 2024 [Page]
Workgroup:
CCAMP Working Group
Internet-Draft:
draft-ybam-rfc8561bis-01
Obsoletes:
8561 (if approved)
Published:
Intended Status:
Standards Track
Expires:
Authors:
S. Mansfield
Ericsson
J. Ahlberg
Ericsson AB
M. Ye
Huawei Technologies
D. Spreafico
Nokia - IT
D. Pala
SIAE

A YANG Data Model for Microwave Radio Link

Abstract

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

This note is to be removed before publishing as an RFC.

The latest revision of this draft can be found at https://example.com/LATEST. Status information for this document may be found at https://datatracker.ietf.org/doc/draft-ybam-rfc8561bis/.

Discussion of this document takes place on the CCAMP Working Group mailing list (mailto:WG@example.com), which is archived at https://example.com/WG.

Source for this draft and an issue tracker can be found at https://github.com/USER/REPO.

Status of This Memo

This Internet-Draft is submitted in full conformance with the 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 and may be updated, replaced, or obsoleted by other documents at any time. It is inappropriate to use Internet-Drafts as reference material or to cite them other than as "work in progress."

This Internet-Draft will expire on 4 September 2024.

▲

Table of Contents

1. 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 [EN302217-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 [RFC8342].

The design of the data model follows the framework for management and control of microwave and millimeter wave interface parameters defined in [RFC8432]. 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 [RFC8561], and it augments [RFC8343] 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 [RFC8343] 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 [RFC8561]; and the ONF Microwave Model [ONF-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 [RFC8432].

1.1. 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

1.2. Tree Structure

A simplified graphical representation of the data model is used in Section 1.4 of this document. The meaning of the symbols in these diagrams is defined in [RFC8340].

1.3. 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 Table 1.

Table 1: Prefixes for imported YANG modules
Prefix YANG Module Reference
mrl ietf-microwave-radio-link This document
yang ietf-yang-types [RFC6991]
ianaift iana-if-type [IANA-if-type-module]
if ietf-interfaces [RFC8343]
ifprot ietf-interface-protection This document
mw-types ietf-microwave-types This document

# Microwave Radio Link YANG Data Model

1.4. YANG Tree 

module: ietf-microwave-radio-link
 +--rw radio-link-protection-groups
 | +--rw protection-group* [name]
 |   +--rw name              string
 |   +--rw protection-architecture-type?  identityref
 |   +--rw members*            if:interface-ref
 |   +--rw operation-type?         enumeration
 |   +--rw working-entity*         if:interface-ref
 |   +--rw revertive-wait-to-restore?   uint16
 |   +--rw hold-off-timer?         uint16
 |   +--ro status?             identityref
 |   +---x manual-switch-working
 |   +---x manual-switch-protection
 |   +---x forced-switch
 |   +---x lockout-of-protection
 |   +---x freeze
 |   +---x exercise
 |   +---x clear
 +--rw xpic-pairs {xpic}?
 | +--rw xpic-pair* [name]
 |   +--rw name    string
 |   +--rw enabled?  boolean
 |   +--rw members*  if:interface-ref
 +--rw mimo-groups {mimo}?
   +--rw mimo-group* [name]
    +--rw name    string
    +--rw enabled?  boolean
    +--rw members*  if:interface-ref

 augment /if:interfaces/if:interface:
  +--rw id?           string
  +--rw (mode-option)
  | x--:(mode)
  | | x--rw mode       identityref
  | +--:(rlt-mode)
  |   +--rw rlt-mode
  |    +--rw num-bonded-carriers    uint32
  |    +--rw num-protecting-carriers  uint32
  +--rw carrier-terminations*  if:interface-ref
  +--rw rlp-groups*
  |    -> /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

1.5. 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.

3. 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 [RFC8343], and it references [G.808.1].

<CODE BEGINS> file "ietf-interface-protection@2024-03-03.yang"

module ietf-interface-protection {
  yang-version 1.1;
  namespace "urn:ietf:params:xml:ns:yang:ietf-interface-protection";
  prefix ifprot;

  import ietf-interfaces {
    prefix if;
    reference
      "RFC 8343";
  }

  organization
    "Internet Engineering Task Force (IETF) CCAMP WG";
  contact
    "WG List: <mailto:ccamp@ietf.org>

     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";
      }
    }
  }
}

<CODE ENDS>

4. 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.

<CODE BEGINS> file "ietf-microwave-types@2024-03-03.yang"

module ietf-microwave-types {
  yang-version 1.1;
  namespace "urn:ietf:params:xml:ns:yang:ietf-microwave-types";
  prefix mw-types;

  organization
    "Internet Engineering Task Force (IETF) CCAMP WG";
  contact
    "WG List: <mailto:ccamp@ietf.org>

     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.";
    }
  }
}

<CODE ENDS>

5. 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 [RFC6241] or RESTCONF [RFC8040]. The lowest NETCONF layer is the secure transport layer, and the mandatory-to-implement secure transport is Secure Shell (SSH) [RFC6242]. The lowest RESTCONF layer is HTTPS, and the mandatory-to-implement secure transport is TLS [RFC8446].

The Network Configuration Access Control Model (NACM) [RFC8341] 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:

      /if:interfaces/if:interface/mode,
      /if:interfaces/if:interface/carrier-terminations,
      /if:interfaces/if:interface/rlp-groups,
      /if:interfaces/if:interface/xpic-pairs,
      /if:interfaces/if:interface/mimo-groups, and
      /if:interfaces/if:interface/tdm-connections:

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:

      /if:interfaces/if:interface/carrier-id,
      /if:interfaces/if:interface/tx-enabled,
      /if:interfaces/if:interface/tx-frequency,
      /if:interfaces/if:interface/rx-frequency,
      /if:interfaces/if:interface/duplex-distance,
      /if:interfaces/if:interface/channel-separation,
      /if:interfaces/if:interface/rtpc/maximum-nominal-power,
      /if:interfaces/if:interface/atpc/maximum-nominal-power,
      /if:interfaces/if:interface/atpc/atpc-lower-threshold,
      /if:interfaces/if:interface/atpc/atpc-upper-threshold,
      /if:interfaces/if:interface/single/selected-cm,
      /if:interfaces/if:interface/adaptive/selected-min-acm,
      /if:interfaces/if:interface/adaptive/selected-max-acm,
      /if:interfaces/if:interface/if-loop, and
      /if:interfaces/if:interface/rf-loop:

These data nodes represent the configuration of the carrier termination, and 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:

      /radio-link-protection-groups/protection-group:

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:

      /xpic-pairs:

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:

      /mimo-groups:

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:

  /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.

6. IANA Considerations

No IANA Considerations in this update.

7. References

7.1. Normative References

[RFC6241]
Enns, R., Ed., Bjorklund, M., Ed., Schoenwaelder, J., Ed., and A. Bierman, Ed., "Network Configuration Protocol (NETCONF)", RFC 6241, DOI 10.17487/RFC6241, , <https://www.rfc-editor.org/rfc/rfc6241>.
[RFC6242]
Wasserman, M., "Using the NETCONF Protocol over Secure Shell (SSH)", RFC 6242, DOI 10.17487/RFC6242, , <https://www.rfc-editor.org/rfc/rfc6242>.
[RFC6991]
Schoenwaelder, J., Ed., "Common YANG Data Types", RFC 6991, DOI 10.17487/RFC6991, , <https://www.rfc-editor.org/rfc/rfc6991>.
[RFC7224]
Bjorklund, M., "IANA Interface Type YANG Module", RFC 7224, DOI 10.17487/RFC7224, , <https://www.rfc-editor.org/rfc/rfc7224>.
[RFC8040]
Bierman, A., Bjorklund, M., and K. Watsen, "RESTCONF Protocol", RFC 8040, DOI 10.17487/RFC8040, , <https://www.rfc-editor.org/rfc/rfc8040>.
[RFC8341]
Bierman, A. and M. Bjorklund, "Network Configuration Access Control Model", STD 91, RFC 8341, DOI 10.17487/RFC8341, , <https://www.rfc-editor.org/rfc/rfc8341>.
[RFC8343]
Bjorklund, M., "A YANG Data Model for Interface Management", RFC 8343, DOI 10.17487/RFC8343, , <https://www.rfc-editor.org/rfc/rfc8343>.
[RFC8446]
Rescorla, E., "The Transport Layer Security (TLS) Protocol Version 1.3", RFC 8446, DOI 10.17487/RFC8446, , <https://www.rfc-editor.org/rfc/rfc8446>.
[RFC8561]
Ahlberg, J., Ye, M., Li, X., Spreafico, D., and M. Vaupotic, "A YANG Data Model for Microwave Radio Link", RFC 8561, DOI 10.17487/RFC8561, , <https://www.rfc-editor.org/rfc/rfc8561>.

7.2. Informative References

[EN301129]
ETSI, "Transmission and Multiplexing (TM); Digital Radio Relay Systems (DRRS); Synchronous Digital Hierarchy (SDH); System performance monitoring parameters of SDH DRRS", EN 301 129 V1.1.2 , .
[EN302217-1]
ETSI, "Fixed Radio Systems; Characteristics and requirements for point-to-point equipment and antennas; Part 1: Overview, common characteristics and system- dependent requirements", EN 302 217-1 V3.1.0 , .
[EN302217-2]
ETSI, "Fixed Radio Systems; Characteristics and requirements for point to-point equipment and antennas; Part 2: Digital systems operating in frequency bands from 1 GHz to 86 GHz; Harmonised Standard covering the essential requirements of article 3.2 of Directive 2014/53/EU", EN 302 217-2 V3.1.1 , .
[G.808.1]
ITU-T, "SERIES G: TRANSMISSION SYSTEMS AND MEDIA, DIGITAL SYSTEMS AND NETWORKS; Digital networks ; General aspects Generic protection switching ; Linear trail and subnetwork protection", ITU-T Recommendation G.808.1 , .
[G.826]
ITU-T, "SERIES G: TRANSMISSION SYSTEMS AND MEDIA, DIGITAL SYSTEMS AND NETWORKS; Digital networks - Quality and availability targets; End-to-end error performance parameters and objectives for international, constant bit- rate digital paths and connections", ITU-T Recommendation G.826 , .
[IANA-if-type-module]
IANA, "iana-if-type YANG Module", , <http://www.iana.or/assignments/iana-if-type>.
[ONF-model]
ONF, "Microwave Information Model", TR-532, version 1.0 , , <https://www.opennetworking.org/images/stories/downloads/sdn-resources/technical-reports/TR-532-Microwave-Information-Model-V1.pdf>.
[RFC8340]
Bjorklund, M. and L. Berger, Ed., "YANG Tree Diagrams", BCP 215, RFC 8340, DOI 10.17487/RFC8340, , <https://www.rfc-editor.org/rfc/rfc8340>.
[RFC8342]
Bjorklund, M., Schoenwaelder, J., Shafer, P., Watsen, K., and R. Wilton, "Network Management Datastore Architecture (NMDA)", RFC 8342, DOI 10.17487/RFC8342, , <https://www.rfc-editor.org/rfc/rfc8342>.
[RFC8432]
Ahlberg, J., Ed., Ye, M., Ed., Li, X., Contreras, LM., and CJ. Bernardos, "A Framework for Management and Control of Microwave and Millimeter Wave Interface Parameters", RFC 8432, DOI 10.17487/RFC8432, , <https://www.rfc-editor.org/rfc/rfc8432>.
[TR102311]
ETSI, "Fixed Radio Systems; Point-to-point equipment; Specific aspects of the spatial frequency reuse method", ETSI TR 102 311 V1.2.1 , .

Appendix A. Changes from RFC 8561

To be added in a future revision of this draft.

Appendix B. 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.

B.1. 1+0 Instance 

                    /--------- Radio Link ---------\
                     Near End              Far End

              +---------------+           +---------------+
              |  Radio Link   |           | Radio Link    |
              |  Terminal A   |           | Terminal B    |
              |               |           |               |
              |               |           |               |
              | +-----------+ |           | +-----------+ |
              | |           | | Carrier A | |           | |
              | |  Carrier  | |<--------->| |  Carrier  | |
              | |Termination| |           | |Termination| |
              | |     1     | |           | |     1     | |
              | +-----------+ |           | +-----------+ |
              |               |           |               |
              |               |           |               |
              +---------------+           +---------------+

        \--- Microwave Node ---/          \--- Microwave Node ---/
Figure 1: 1+0 Example

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

{
  "ietf-interfaces:interfaces": {
    "interface": [
      {
        "name": "RLT-A",
        "description": "Radio Link Terminal A",
        "type": "iana-if-type:microwaveRadioLinkTerminal",
        "ietf-microwave-radio-link:mode":
           "ietf-microwave-types:one-plus-zero",
        "ietf-microwave-radio-link:carrier-terminations": [
          "RLT-A:CT-1"
        ]
      },
      {
        "name": "RLT-A:CT-1",
        "description": "Carrier Termination 1",
        "type": "iana-if-type:microwaveCarrierTermination",
        "ietf-microwave-radio-link:carrier-id": "A",
        "ietf-microwave-radio-link:tx-enabled": true,
        "ietf-microwave-radio-link:tx-frequency": 10728000,
        "ietf-microwave-radio-link:duplex-distance": 644000,
        "ietf-microwave-radio-link:channel-separation": 28000,
        "ietf-microwave-radio-link:polarization": "not-specified",
        "ietf-microwave-radio-link:rtpc": {
          "maximum-nominal-power": "20.0"
        },
        "ietf-microwave-radio-link:single": {
          "selected-cm": "ietf-microwave-types:qam-512"
        }
      }
    ]
  }
}

B.2. 2+0 Instance

Figure 2 shows a 2+0 example.

                    /--------- Radio Link ---------\
                     Near End              Far End

              +---------------+           +---------------+
              | Radio Link    |           | Radio Link    |
              | Terminal A    |           | Terminal B    |
              |               |           |               |
              |               |           |               |
              | +-----------+ |           | +-----------+ |
              | |           | | Carrier A | |           | |
              | |  Carrier  | |<--------->| |  Carrier  | |
              | |Termination| |           | |Termination| |
              | |     1     | |           | |     1     | |
              | +-----------+ |           | +-----------+ |
              |               |           |               |
              | +-----------+ |           | +-----------+ |
              | |           | | Carrier B | |           | |
              | |  Carrier  | |<--------->| |  Carrier  | |
              | |Termination| |           | |Termination| |
              | |     2     | |           | |     2     | |
              | +-----------+ |           | +-----------+ |
              |               |           |               |
              +---------------+           +---------------+

        \--- Microwave Node ---/          \--- Microwave Node ---/
Figure 2: 2+0 Example

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

{
  "ietf-interfaces:interfaces": {
    "interface": [
      {
        "name": "RLT-A",
        "description": "Radio Link Terminal A",
        "type": "iana-if-type:microwaveRadioLinkTerminal",
        "ietf-microwave-radio-link:mode":
          "ietf-microwave-types:two-plus-zero",
        "ietf-microwave-radio-link:carrier-terminations": [
          "RLT-A:CT-1",
          "RLT-A:CT-2"
        ]
      },
      {
        "name": "RLT-A:CT-1",
        "description": "Carrier Termination 1",
        "type": "iana-if-type:microwaveCarrierTermination",
        "ietf-microwave-radio-link:carrier-id": "A",
        "ietf-microwave-radio-link:tx-enabled": true,
        "ietf-microwave-radio-link:tx-frequency": 10728000,
        "ietf-microwave-radio-link:duplex-distance": 644000,
        "ietf-microwave-radio-link:channel-separation": 28000,
        "ietf-microwave-radio-link:polarization": "not-specified",
        "ietf-microwave-radio-link:rtpc": {
          "maximum-nominal-power": "20.0"
        },
        "ietf-microwave-radio-link:single": {
          "selected-cm": "ietf-microwave-types:qam-512"
        }
      },
      {
        "name": "RLT-A:CT-2",
        "description": "Carrier Termination 2",
        "type": "iana-if-type:microwaveCarrierTermination",
        "ietf-microwave-radio-link:carrier-id": "B",
        "ietf-microwave-radio-link:tx-enabled": true,
        "ietf-microwave-radio-link:tx-frequency": 10618000,
        "ietf-microwave-radio-link:duplex-distance": 644000,
        "ietf-microwave-radio-link:channel-separation": 28000,
        "ietf-microwave-radio-link:polarization": "not-specified",
        "ietf-microwave-radio-link:rtpc": {
          "maximum-nominal-power": "20.0"
        },
        "ietf-microwave-radio-link:single": {
          "selected-cm": "ietf-microwave-types:qam-512"
        }
      }
    ]
  }
}

B.3. 2+0 XPIC Instance

The following instance shows the XPIC configuration of the Near End node.

{
  "ietf-interfaces:interfaces": {
    "interface": [
      {
        "name": "RLT-A",
        "description": "Radio Link Terminal A",
        "type": "iana-if-type:microwaveRadioLinkTerminal",
        "ietf-microwave-radio-link:mode":
           "ietf-microwave-types:two-plus-zero",
        "ietf-microwave-radio-link:carrier-terminations": [
          "RLT-A:CT-1",
          "RLT-A:CT-2"
        ],
        "ietf-microwave-radio-link:xpic-pairs": [
          "xpic-pair1"
        ]
      },
      {
        "name": "RLT-A:CT-1",
        "description": "Carrier Termination 1",
        "type": "iana-if-type:microwaveCarrierTermination",
        "ietf-microwave-radio-link:carrier-id": "A",
        "ietf-microwave-radio-link:tx-enabled": true,
        "ietf-microwave-radio-link:tx-frequency": 10728000,
        "ietf-microwave-radio-link:duplex-distance": 644000,
        "ietf-microwave-radio-link:channel-separation": 28000,
        "ietf-microwave-radio-link:polarization": "not-specified",
        "ietf-microwave-radio-link:rtpc": {
          "maximum-nominal-power": "20.0"
        },
        "ietf-microwave-radio-link:single": {
          "selected-cm": "ietf-microwave-types:qam-512"
        }
      },
      {
        "name": "RLT-A:CT-2",
        "description": "Carrier Termination 2",
        "type": "iana-if-type:microwaveCarrierTermination",
        "ietf-microwave-radio-link:carrier-id": "B",
        "ietf-microwave-radio-link:tx-enabled": true,
        "ietf-microwave-radio-link:tx-frequency": 10618000,
        "ietf-microwave-radio-link:duplex-distance": 644000,
        "ietf-microwave-radio-link:channel-separation": 28000,
        "ietf-microwave-radio-link:polarization": "not-specified",
        "ietf-microwave-radio-link:rtpc": {
          "maximum-nominal-power": "20.0"
        },
        "ietf-microwave-radio-link:single": {
          "selected-cm": "ietf-microwave-types:qam-512"
        }
      }
    ]
  },
  "ietf-microwave-radio-link:xpic-pairs": {
    "xpic-pair": [
      {
        "name": "xpic-pair1",
        "members": [
          "RLT-A:CT-1",
          "RLT-A:CT-2"
        ]
      }
    ]
  }
}

~~~~

Appendix C. 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

Italo Busi
Huawei Technologies
Koji Kawada
NEC Corporation
1753, Shimonumabe Nakahara-ku, Kawasaki, Kanagawa
211-8666
Japan
Carlos J. Bernardos
Universidad Carlos III de Madrid
Av. Universidad, 30
28911 Leganes, Madrid
Spain
Marko Vaupotic
Aviat Networks
Motnica 9
SI-1236 Trzin-Ljubljana
Slovenia
Xi Li
NEC Laboratories Europe
Kurfursten-Anlage 36
69115 Heidelberg
Germany

Authors' Addresses

Scott Mansfield
Ericsson
Jonas Ahlberg
Ericsson AB
Lindholmspiren 11
SE-417 56 Goteborg
Sweden
Min Ye
Huawei Technologies
No.1899, Xiyuan Avenue
Chengdu
611731
China
Daniela Spreafico
Nokia - IT
Via Energy Park, 14
20871 Vimercate (MI)
Italy
Danilo Pala
SIAE