RFC 9551: Framework of Operations, Administration, and Maintenance (OAM) for Deterministic Networking (DetNet)
In plain English — editorial summary, not part of the RFC
Deterministic Networking (DetNet), as defined in RFC 8655, aims to provide 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 Operations, Administration, and Maintenance (OAM) recommended to maintain a deterministic network. The document will be used in future work that defines the applicability of and extension of OAM protocols for 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 DetNet flow.
Document record
- Document ID
- RFC9551
- Published
- March 2024
- Authors
- G. Mirsky; F. Theoleyre; G. Papadopoulos; CJ. Bernardos; B. Varga; J. Farkas
- Status
- INFORMATIONAL
- Stream
- IETF
- Area
- rtg
- Pages
- 14
- Also known as
- —
Topics
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 9452Network Service Header (NSH) Encapsulation for In Situ OAM (IOAM) DataCurrent
August 2023
- RFC 7185Link Metrics for the Mobile Ad Hoc Network (MANET) Routing Protocol OLSRv2 - RationaleCurrent
April 2014
- RFC 9378In Situ Operations, Administration, and Maintenance (IOAM) DeploymentCurrent
April 2023
- RFC 9198Advanced Unidirectional Route Assessment (AURA)Current
May 2022
- RFC 9197Data Fields for In Situ Operations, Administration, and Maintenance (IOAM)Current
May 2022
- RFC 6556Testing Eyeball HappinessCurrent
April 2012
- RFC 5093BT's eXtended Network Quality RTP Control Protocol Extended Reports (RTCP XR XNQ)Current
December 2007
- RFC 3897Open Pluggable Edge Services (OPES) Entities and End Points CommunicationCurrent
September 2004
Also filed under
About this page
The document record above — title, authors, date, status, stream, area, relationships, DOI and errata — is imported verbatim from the public RFC Editor index. The “in plain English” section is editorial: written by The metasystema editorial team, not part of the RFC. Where the two differ, the RFC text governs.
Last checked against the RFC Editor index on . RFCs are never revised after publication; changes are issued as new documents.
Data sources · Editorial policy · Report a correction · What is an RFC?