Operations, Administration and Maintenance (OAM) features for DetNet

Document Type Replaced Internet-Draft (individual)
Authors Fabrice Theoleyre  , Georgios Papadopoulos  , Greg Mirsky  , Carlos Bernardos 
Last updated 2020-10-25
Replaced by draft-tpmb-detnet-oam-framework
Stream (None)
Intended RFC status (None)
Expired & archived
plain text xml pdf htmlized bibtex
Stream Stream state (No stream defined)
Consensus Boilerplate Unknown
RFC Editor Note (None)
IESG IESG state Replaced by draft-tpmb-detnet-oam-framework
Telechat date
Responsible AD (None)
Send notices to (None)

This Internet-Draft is no longer active. A copy of the expired Internet-Draft can be found at


Deterministic Networking (DetNet), as defined in RFC 8655, is aimed to provide a bounded end-to-end latency on top of the network infrastructure, comprising both Layer 2 bridged and Layer 3 routed segments. This document's primary purpose is to detail the specific requirements of the Operation, Administration, and Maintenance (OAM) recommended to maintain a deterministic network. With the implementation of the OAM framework in DetNet, an operator will have a real-time view of the network infrastructure regarding the network's ability to respect the Service Level Objective (SLO), such as packet delay, delay variation, and packet loss ratio, assigned to each data flow.


Fabrice Theoleyre (theoleyre@unistra.fr)
Georgios Papadopoulos (georgios.papadopoulos@imt-atlantique.fr)
Greg Mirsky (gregimirsky@gmail.com)
Carlos Bernardos (cjbc@it.uc3m.es)

(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)