Network Management Operations (nmop) Internet Drafts

      
 A YANG Data Model for Network Incident Management
 
 draft-ietf-nmop-network-incident-yang-02.txt
 Date: 10/10/2024
 Authors: Tong Hu, Luis Contreras, Qin WU, Nigel Davis, Chong Feng
 Working Group: Network Management Operations (nmop)
 A network incident refers to an unexpected interruption of a network service, degradation of a network service quality, or sub-health of a network service. Different data sources including alarms, metrics, and other anomaly information can be aggregated into a few amount of network incidents through data correlation analysis and the service impact analysis. This document defines a YANG Module for the network incident lifecycle management. This YANG module is meant to provide a standard way to report, diagnose, and help resolve network incidents for the sake of network service health and root cause analysis.
 An Architecture for YANG-Push to Message Broker Integration
 
 draft-ietf-nmop-yang-message-broker-integration-05.txt
 Date: 19/10/2024
 Authors: Thomas Graf, Ahmed Elhassany
 Working Group: Network Management Operations (nmop)
 This document describes the motivation and architecture of a native YANG-Push notifications and YANG Schema integration into a Message Broker and YANG Schema Registry.
 Some Key Terms for Network Fault and Problem Management
 
 draft-ietf-nmop-terminology-09.txt
 Date: 26/11/2024
 Authors: Nigel Davis, Adrian Farrel, Thomas Graf, Qin WU, Chaode Yu
 Working Group: Network Management Operations (nmop)
 This document sets out some terms that are fundamental to a common understanding of network fault and problem management within the IETF. The purpose of this document is to bring clarity to discussions and other work related to network fault and problem management, in particular to YANG models and management protocols that report, make visible, or manage network faults and problems.
 An Architecture for a Network Anomaly Detection Framework
 
 draft-ietf-nmop-network-anomaly-architecture-01.txt
 Date: 20/10/2024
 Authors: Thomas Graf, Wanting Du, Pierre Francois
 Working Group: Network Management Operations (nmop)
 This document describes the motivation and architecture of a Network Anomaly Detection Framework and the relationship to other documents describing network symptom semantics and network incident lifecycle. The described architecture for detecting IP network service interruption is generic applicable and extensible. Different applications are being described and exampled with open-source running code.
 SIMAP: Concept,Requirements,and Use Cases
 
 draft-ietf-nmop-simap-concept-00.txt
 Date: 29/11/2024
 Authors: Olga Havel, Benoit Claise, Oscar de Dios, Thomas Graf
 Working Group: Network Management Operations (nmop)
 This document defines the concept of Service & Infrastructure Maps (SIMAP) and identifies a set of SIMAP requirements and use cases. The SIMAP was previously known as Digital Map in the old draft versions (draft-ietf-nmop-digital-map-concept). The document intends to be used as a reference for the assessment effort of the various topology modules to meet SIMAP requirements.
 Semantic Metadata Annotation for Network Anomaly Detection
 
 draft-ietf-nmop-network-anomaly-semantics-00.txt
 Date: 08/12/2024
 Authors: Thomas Graf, Wanting Du, Alex Feng, Vincenzo Riccobene, Antonio Roberto
 Working Group: Network Management Operations (nmop)
 This document explains why and how semantic metadata annotation helps to test, validate and compare Outlier and Symptom detection, supports supervised and semi-supervised machine learning development, enables data exchange among network operators, vendors and academia and make anomalies for humans apprehensible. The proposed semantics uniforms the network anomaly data exchange between and among operators and vendors to improve their Service Disruption Detection Systems.
 An Experiment: Network Anomaly Lifecycle
 
 draft-ietf-nmop-network-anomaly-lifecycle-00.txt
 Date: 08/12/2024
 Authors: Vincenzo Riccobene, Antonio Roberto, Thomas Graf, Wanting Du, Alex Feng
 Working Group: Network Management Operations (nmop)
 Network Anomaly Detection is the act of detecting problems in the network. Accurately detect problems is very challenging for network operators in production networks. Good results require a lot of expertise and knowledge around both the implied network technologies and the connectivity services provided to customers, apart from a proper monitoring infrastructure. In order to facilitate network anomaly detection, novel techniques are being introduced, including programmatical, rule-based and AI-based, with the promise of improving scalability and the hope to keep a high detection accuracy. To guarantee acceptable results, the process needs to be properly designed, adopting well-defined stages to accurately collect evidence of anomalies, validate their relevancy and improve the detection systems over time, iteratively. This document describes a well-defined approach on managing the lifecycle process of a network anomaly detection system, spanning across the recording of its output and its iterative refinement, in order to facilitate network engineers to interact with the network anomaly detection system, enable the "human-in-the-loop" paradigm and refine the detection abilities over time. The major contributions of this document are: the definition of three key stages of the lifecycle process, the definition of a state machine for each anomaly annotation on the system and the definition of YANG data models describing a comprehensive format for the anomaly labels, allowing a well-structured exchange of those between all the interested actors.

data-group-menu-data-url="/group/groupmenu.json">

Network Management Operations (nmop)

WG Name Network Management Operations
Acronym nmop
Area Operations and Management Area (ops)
State Active
Charter charter-ietf-nmop-01 Approved
Document dependencies
Additional resources GitHub Repository
Experiments & Hackathons
IAB workshop on the Next Era of Network Management Operations (NEMOPS
OLD NETMO Mailing List Archive
Personnel Chairs Benoît Claise, Mohamed Boucadair
Area Director Mahesh Jethanandani
Secretary Thomas Graf
Delegate Thomas Graf
Mailing list Address nmop@ietf.org
To subscribe https://www.ietf.org/mailman/listinfo/nmop
Archive https://mailarchive.ietf.org/arch/browse/nmop/
Chat Room address https://zulip.ietf.org/#narrow/stream/nmop

Charter for Working Group

The increased drive by operators for integration and deployment of
network management protocols and YANG data models may expose issues and
problems with the individual protocols and models, or with the wider
integration of both the protocols and the models. Some of these problems
may only be witnessed when trying to manage large-scale networks, e.g.,
due to the increased complexity and handling large volumes of data
exported in frequent updates. At the same time, simplifying the network
management and operations, with increased automation, is a high priority
for network operators.

The goals of the Network Management Operations working group are to
solicit input from network operators to identify existing and
anticipated operational issues arising from the near-term deployment of
network management technologies, and to consider potential solutions or
workarounds for those issues. Those operational issues may relate to
deployments of existing network management technologies or the
integration of related technologies for network management and
telemetry.

Solving those operational issues requires discussion, investigation, and
potentially some experiments, which may take some time. However, the
working group will focus on pragmatic items achievable in a short
timeframe over long term architectural visions.

Since the focus is on solving network management problems faced by
operators, discussion and experiments are not solely limited to network
management technologies standardized within the IETF but may cover the
wider network management ecosystem as it relates to the management of
IETF protocols, subject to the following two constraints:

  • The working group may discuss network management protocols and data
    models not standardized within the IETF only when they are being used
    to manage IETF protocols or to compare them to equivalent IETF
    solutions.

  • The working group will not work on specific issues or improvements to
    protocols or data models developed and maintained outside the IETF.
    They must be taken to the appropriate organization for discussion and
    resolution.

The Network Management Operations working group is scoped, in rough
order from highest to lowest priority, to:

  • Present and discuss operational issues faced by the deployment of
    existing network management technologies.

  • Discuss ideas for future short-term experiments (i.e., those focused
    on incremental improvements to network management operations that can
    be achieved in 1-2 years) and report on the progress of the relevant
    experimentation being done in the community.

  • Discuss network operator use cases and requirements for solving
    anticipated problems related to the deployment of network management
    technologies.

  • Standardize YANG data models to solve operational issues identified in
    the scope items above. YANG data models potentially within the scope
    of other WGs will only be progressed here with agreement from the
    relevant ADs.

  • Seek involvement with developers of open-source software to help drive
    adoption of IETF network management standards and to improve protocol
    maturity.

  • Document operational experience and best practice for network
    management and telemetry deployment as BCPs or Informational RFCs.

This working group is not chartered to work on new protocols or protocol
enhancements.

Agenda time at NMOP sessions at IETF meetings should allow for
presentations and discussions of operator issues and experience, and
other work within scope for the working group, but with a default
expectation that priority be given to operator presentations.

The current topics of focus for the working group are:

  • NETCONF/YANG Push integration with Apache Kafka & time series databases

  • Anomaly detection and incident management

  • Issues related to deployment/usage of YANG topology modules (e.g., to
    model a Digital Map)

  • Consider/plan an approach for updating RFC 3535-bis (collecting
    updated operator requirements for IETF network management solutions)

Like many of the “ops” working groups, this working group is expected to
be long-lived, and is expected to remain open whilst there is sufficient
interest and drive from the operators to work on topics within the scope
described above.

Milestones

Date Milestone Associated documents
Dec 2025 Submit NMOP Terminology to the IESG
Dec 2025 Submit Network Anomaly Management to the IESG
Dec 2025 Submit Network Incident Management to the IESG
Sep 2025 Submit Architecture for YANG-Push to Message Broker Integration to the IESG
Jun 2025 Submit "Digital Map: Concept, Requirements, and Use Cases" to the IESG

Done milestones

Date Milestone Associated documents
Done Adopt a document on network anomaly management draft-ietf-nmop-network-anomaly-architecture
Done Adopt a terminology document for anomaly and incident management draft-ietf-nmop-terminology
Done Adopt a document on network incident management draft-ietf-nmop-network-incident-yang
Done Adopt a document describing how to integrate YANG Push with Apache Kafka draft-ietf-nmop-yang-message-broker-integration