5. Management Plane Overview

This section preserves the RFC text for the DetNet Controller Plane framework, including requirements, control-plane architectures, PREOF, MPLS/IP/Segment Routing considerations, OAM, multi-domain behavior, IANA, and security considerations.

5.  Management Plane Overview

   The management plane includes the ability to statically provision
   network nodes and to use Operations, Administration, and Maintenance
   (OAM) to monitor DetNet performance and to detect outages or other
   issues at the DetNet layer.

5.1.  DetNet Operations, Administration, and Maintenance (OAM)

   This document covers the general considerations for OAM.

5.1.1.  OAM for Performance Monitoring (PM)

5.1.1.1.  Active PM

   Active PM is performed by injecting OAM packets into the network to
   estimate the performance of the network and by then measuring the
   performance of those OAM packets.  Adding extra traffic can affect
   the delay and throughput performance of the network, and for this
   reason, Active PM is not recommended for use in operational DetNet
   domains.  However, it is a useful test tool when commissioning a new
   network or during troubleshooting.

5.1.1.2.  Passive PM

   Passive PM, such as In Situ Operations, Administration, and
   Maintenance (IOAM) [RFC9197], monitors the actual service traffic in
   a network domain in order to measure its performance without having a
   detrimental effect on the network.  As compared to Active PM, Passive
   PM is much preferred for use in DetNet domains.

5.1.2.  OAM for Connectivity and Fault Management (CFM)

   The detailed requirements for CFM in a DetNet IP domain and a DetNet
   MPLS domain are defined in [RFC9551], [RFC9634], and [RFC9546],
   respectively.