RFC 9546: Operations, Administration, and Maintenance (OAM) for Deterministic Networking (DetNet) with the MPLS Data Plane
In plain English — editorial summary, not part of the RFC
This document defines format and usage principles of the Deterministic Networking (DetNet) service Associated Channel over a DetNet network with the MPLS data plane. The DetNet service Associated Channel can be used to carry test packets of active Operations, Administration, and Maintenance (OAM) protocols that are used to detect DetNet failures and measure performance metrics.
Document record
- Document ID
- RFC9546
- Published
- February 2024
- Authors
- G. Mirsky; M. Chen; B. Varga
- Status
- PROPOSED STANDARD
- Stream
- IETF
- Area
- rtg
- Pages
- 12
- Also known as
- —
Topics
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 9634Operations, Administration, and Maintenance (OAM) for Deterministic Networking (DetNet) with the IP Data PlaneCurrent
October 2024
- RFC 9655Egress Validation in Label Switched Path Ping and Traceroute MechanismsCurrent
November 2024
- RFC 9703Label Switched Path (LSP) Ping/Traceroute for Segment Routing (SR) Egress Peer Engineering (EPE) Segment Identifiers (SIDs) with MPLS Data PlaneCurrent
December 2024
- RFC 9716Mechanisms for MPLS Ping and Traceroute Procedures in Inter-Domain Segment Routing NetworksCurrent
February 2025
- RFC 9320Deterministic Networking (DetNet) Bounded LatencyCurrent
November 2022
- RFC 9772Active Operations, Administration, and Maintenance (OAM) for Use in Generic Network Virtualization Encapsulation (Geneve)Current
May 2025
- RFC 9912Reliable and Available Wireless (RAW) ArchitectureCurrent
April 2026
- RFC 9914Root-Initiated Routing State in the Routing Protocol for Low-Power and Lossy Networks (RPL)Current
April 2026
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?