Operations, Administration and Maintenance (OAM) features for DetNet
draft-theoleyre-detnet-oam-support-00
| Document | Type |
Replaced Internet-Draft
(individual)
Expired & archived
|
|
|---|---|---|---|
| Authors | Fabrice Theoleyre , Georgios Z. Papadopoulos , Greg Mirsky , Carlos J. Bernardos | ||
| Last updated | 2020-10-25 | ||
| Replaced by | draft-tpmb-detnet-oam-framework | ||
| RFC stream | (None) | ||
| Intended RFC status | (None) | ||
| Formats | |||
| 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 | (None) | ||
| Responsible AD | (None) | ||
| Send notices to | (None) |
This Internet-Draft is no longer active. A copy of the expired Internet-Draft is available in these formats:
Abstract
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.
Authors
Fabrice Theoleyre
Georgios Z. Papadopoulos
Greg Mirsky
Carlos J. Bernardos
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)