RFC 8578: Deterministic Networking Use Cases
In plain English — editorial summary, not part of the RFC
This document presents use cases for diverse industries that have in common a need for "deterministic flows". "Deterministic" in this context means that such flows provide guaranteed bandwidth, bounded latency, and other properties germane to the transport of time-sensitive data. These use cases differ notably in their network topologies and specific desired behavior, providing as a group broad industry context for Deterministic Networking (DetNet). For each use case, this document will identify the use case, identify representative solutions used today, and describe potential improvements that DetNet can enable.
Document record
- Document ID
- RFC8578
- Published
- May 2019
- Authors
- E. Grossman
- Status
- INFORMATIONAL
- Stream
- IETF
- Area
- rtg
- Pages
- 97
- Also known as
- —
Topics
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 8655Deterministic Networking ArchitectureCurrent
October 2019
- RFC 8964Deterministic Networking (DetNet) Data Plane: MPLSCurrent
January 2021
- RFC 9016Flow and Service Information Model for Deterministic Networking (DetNet)Current
March 2021
- RFC 9055Deterministic Networking (DetNet) Security ConsiderationsCurrent
June 2021
- RFC 9320Deterministic Networking (DetNet) Bounded LatencyCurrent
November 2022
- RFC 9546Operations, Administration, and Maintenance (OAM) for Deterministic Networking (DetNet) with the MPLS Data PlaneCurrent
February 2024
- RFC 9634Operations, Administration, and Maintenance (OAM) for Deterministic Networking (DetNet) with the IP Data PlaneCurrent
October 2024
- RFC 9912Reliable and Available Wireless (RAW) ArchitectureCurrent
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?