Semantic Metadata Annotation for Network Anomaly Detection

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 24 July 2024.¶

Copyright Notice

Copyright (c) 2024 IETF Trust and the persons identified as the document authors. All rights reserved.¶

This document is subject to BCP 78 and the IETF Trust's Legal Provisions Relating to IETF Documents (https://trustee.ietf.org/license-info) in effect on the date of publication of this document. Please review these documents carefully, as they describe your rights and restrictions with respect to this document. Code Components extracted from this document must include Revised BSD License text as described in Section 4.e of the Trust Legal Provisions and are provided without warranty as described in the Revised BSD License.¶

Table of Contents

1. Introduction

Network Anomaly Detection Architecture [Ahf23] provides an overall introduction into how anomaly detection is being applied into the IP network domain and which operational data is needed. It approaches the problem space by automating what a Network Engineer would normally do when verifying a network connectivity service. Monitor from different network plane perspectives to understand wherever one network plane affects another negatively.¶

In order to fine tune outlier detection, the results provided as analytical data need to be reviewed by a Network Engineer. Keeping the human out of the monitoring but still involving him in the alert verification loop.¶

This document describes what information is needed to understand the output of the outlier detection for a Network Engineer, but also at the same time is semantically structured that it can be used for outlier detection testing by comparing the results systematically and set a baseline for supervised machine learning which requires labeled operational data.¶

2. Outlier Detection

Outlier Detection, also known as anomaly detection, describes a systematic approach to identify rare data points deviating significantly from the majority. Outliers can manifest as single data point or as a sequence of data points. There are multiple ways in general to classify anomalies, but for the context of this draft, the following three classes are taken into account:¶

Global outliers:

An outlier is considered "global" if its behaviour is outside the entirety of the considered data set. For example, if the average dropped packet count is between 0 and 10 per minute and a small time-window gets the value 1000, this is considered a global anomaly.¶

Contextual outliers:

An outlier is considered "contextual" if its behaviour is within a normal (expected) range, but it would not be expected based on some context. Context can be defined as a function of multiple parameters, such as time, location, etc. For example, the forwarded packet volume overnight reaches levels which might be totally normal for the daytime, but anomalous and unexpected for the nighttime.¶

Collective outliers:

An outlier is considered "collective" if the behaviour of each single data point that are part of the anomaly are within expected ranges (so they are not anomalous it either a contextual or a global sense), but the group, taking all the data points together, is. Note that the group can be made within a single time series (a sequence of data points is anomalous) or across multiple metrics (e.g. if looking at two metrics together, the combined behavior turns out to be anomalous). In Network Telemetry time series, one way this can manifest is that the amount of network paths and interface state changes matches the time range when the forwarded packet volume decreases as a group.¶

For each outlier a score between 0 and 1 is being calculated. The higher the value, the higher the probability that the observed data point is an outlier. Anomaly detection: A survey [VAP09] gives additional details on anomaly detection and its types.¶

3. Data Mesh

The Data Mesh [Deh22] Architecture distinguishes between operational and analytical data. Operational data refers to collected data from operational systems. While analytical data refers to insights gained from operational data.¶

In terms of network observability, semantics of operational network metrics are defined by IETF and are categorized as described in the Network Telemetry Framework [RFC9232] in the following three different network planes:¶

Management Plane:

Time series data describing the state changes and statistics of a network node and its components. For example, Interface state and statistics modelled in ietf-interfaces.yang [RFC8343]¶

Control Plane:

Time series data describing the state and state changes of network reachability. For example, BGP VPNv6 unicast updates and withdrawals exported in BGP Monitoring Protocol (BMP) [RFC7854] and modeled in BGP [RFC4364]¶

Forwarding Plane:

Time series data describing the forwarding behavior of packets and its data-plane context. For example, dropped packet count modelled in IPFIX entity forwardingStatus(IE89) [RFC7270] and packetDeltaCount(IE2) [RFC5102] and exportet with IPFIX [RFC7011].¶

In terms of network observability, semantics of analytical data refers to incident notifications or service level indicators. For example the incident notification described in Section 7.2 of [I-D.feng-opsawg-incident-management], the health status and symptoms described in the Service Assurance Intend Based Networking [RFC9418], the precision availability metrics defined in [I-D.ietf-ippm-pam] or network anomalies and its symptoms as described in this document.¶

4. Observed Symptoms

In this section observed network symptoms are specified and categorized according to the following scheme:¶

Action:

Which action the network node performed for a packet in the Forwarding Plane, a path or adjacency in the Control Plane or state or statistical changes in the Management Plane. For Forwarding Plane we distinguish between missing, where the drop occured outside the measured network node, drop and on-path delay, which was measured on the network node. For Control Plane we distinguish between reachability, which refers to a change in the routing or forwarding information base (RIB/FIB) and adjcacency which refers to a change in peering or link-layer resolution. For Management Plane we refer to state or statistical changes on interfaces.¶

Reason:

For each action, one or more reasons describe why this action was used. For Drops in Forwarding Plane we distinguish between Unreachable because network layer reachability information was missing, Administered because an administrator configured a rule preventing the forwarding for this packet and Corrupt where the network node was unable to determine where to forward to due to packet, software or hardware error. For on-path delay we distinguish between Minimum, Average and Maximum Delay for a given flow. For Control Plane wherever a the reachability was updated or withdrawn or the adjcacency was established or teared down. For Management Plane we distinguish between interfaces states up and down, and statistical erros, discards or unknown protocol counters.¶

Cause:

For each reason one or more cause describe the cause why the network node has chosen that action.¶

Table 1 consolidates for the forwarding plane a list of common symptoms with their Actions, Reasons and Causes.¶

Table 2 consolidates for the control plane a list of common symptoms with their actions, reasons and causess.¶

Table 3 consolidates for the management plane a list of common symptoms with their Actions, Reasons and Causes.¶

5. Semantic Metadata

Metadata adds additional context to data. For instance, in networks the software version of a network node where Management Plane metrics are obtained from as described in[I-D.claise-opsawg-collected-data-manifest]. Where in Semantic Metadata the meaning or ontology of the annotated data is being described. In this section a YANG model is defined in order to provide a structure for the metadata related to anomalies happening in the network. The module is intended to describe the metadata used to "annotate" the operational data collected from the network nodes, which can include time series data and logs, as well as other forms of data that is "time-bounded". The aspects discussed so far in this document are grouped under the concept of "incident" which represents a collection of symptoms. The incident overall has a set of parameters that describe the overall behavior of the network in a given time-window including all the spotted symptoms (network anomalies).¶

              module: ietf-symptom-semantic-metadata
                +--rw symptom
                  +--rw id                         yang:uuid
                  +--rw event-id                   yang:uuid
                  +--rw description                string
                  +--rw start-time                 yang:date-and-time
                  +--rw end-time                   yang:date-and-time
                  +--rw confidence-score           float
                  +--rw concern-score?             float
                  +--rw tags* [key]
                  |  +--rw key      string
                  |  +--rw value    string
                  +--rw (pattern)?
                  |  +--:(drop)
                  |  |  +--rw drop                 empty
                  |  +--:(spike)
                  |  |  +--rw spike                empty
                  |  +--:(mean-shift)
                  |  |  +--rw mean-shift           empty
                  |  +--:(seasonality-shift)
                  |  |  +--rw seasonality-shift    empty
                  |  +--:(trend)
                  |  |  +--rw trend                empty
                  |  +--:(other)
                  |     +--rw other                string
                  +--rw source
                      +--rw (source-type)
                      |  +--:(human)
                      |  |  +--rw human        empty
                      |  +--:(algorithm)
                      |     +--rw algorithm    empty
                      +--rw name?              string

                module: ietf-incident-semantic-metadata
                  +--rw incident
                    +--rw id             yang:uuid
                    +--rw description    string
                    +--rw start-time     yang:date-and-time
                    +--rw end-time       yang:date-and-time
                    +--rw symptoms* []
                    |  +--rw symptom
                    |     +--rw id                         yang:uuid
                    |     +--rw event-id                   yang:uuid
                    |     +--rw description                string
                    |     +--rw start-time                 yang:date-and-time
                    |     +--rw end-time                   yang:date-and-time
                    |     +--rw confidence-score           float
                    |     +--rw concern-score?             float
                    |     +--rw tags* [key]
                    |     |  +--rw key      string
                    |     |  +--rw value    string
                    |     +--rw (pattern)?
                    |     |  +--:(drop)
                    |     |  |  +--rw drop                 empty
                    |     |  +--:(spike)
                    |     |  |  +--rw spike                empty
                    |     |  +--:(mean-shift)
                    |     |  |  +--rw mean-shift           empty
                    |     |  +--:(seasonality-shift)
                    |     |  |  +--rw seasonality-shift    empty
                    |     |  +--:(trend)
                    |     |  |  +--rw trend                empty
                    |     |  +--:(other)
                    |     |     +--rw other                string
                    |     +--rw source
                    |        +--rw (source-type)
                    |        |  +--:(human)
                    |        |  |  +--rw human        empty
                    |        |  +--:(algorithm)
                    |        |     +--rw algorithm    empty
                    |        +--rw name?              string
                    +--rw source
                        +--rw (type)
                        |  +--:(human)
                        |  |  +--rw human        empty
                        |  +--:(algorithm)
                        |     +--rw algorithm    empty
                        +--rw name?              string

6. Security Considerations

The security considerations.¶

7. Acknowledgements

The authors would like to thank xxx for their review and valuable comments.¶

Authors' Addresses