RFC 8655: Deterministic Networking Architecture
In plain English — editorial summary, not part of the RFC
This document provides the overall architecture for Deterministic Networking (DetNet), which provides a capability to carry specified unicast or multicast data flows for real-time applications with extremely low data loss rates and bounded latency within a network domain. Techniques used include 1) reserving data-plane resources for individual (or aggregated) DetNet flows in some or all of the intermediate nodes along the path of the flow, 2) providing explicit routes for DetNet flows that do not immediately change with the network topology, and 3) distributing data from DetNet flow packets over time and/or space to ensure delivery of each packet's data in spite of the loss of a path. DetNet operates at the IP layer and delivers service over lower-layer technologies such as MPLS and Time- Sensitive Networking (TSN) as defined by IEEE 802.1.
Document record
- Document ID
- RFC8655
- Published
- October 2019
- Authors
- N. Finn; P. Thubert; B. Varga; J. Farkas
- Status
- PROPOSED STANDARD
- Stream
- IETF
- Area
- rtg
- Pages
- 38
- Also known as
- —
Topics
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 8578Deterministic Networking Use CasesCurrent
May 2019
- RFC 9320Deterministic Networking (DetNet) Bounded LatencyCurrent
November 2022
- RFC 3708Using TCP Duplicate Selective Acknowledgement (DSACKs) and Stream Control Transmission Protocol (SCTP) Duplicate Transmission Sequence Numbers (TSNs) to Detect Spurious RetransmissionsCurrent
February 2004
- RFC 8654Extended Message Support for BGPCurrent
October 2019
- RFC 8652A YANG Data Model for the Internet Group Management Protocol (IGMP) and Multicast Listener Discovery (MLD)Current
November 2019
- RFC 8651Dynamic Link Exchange Protocol (DLEP) Control-Plane-Based Pause ExtensionCurrent
October 2019
- RFC 8660Segment Routing with the MPLS Data PlaneCurrent
December 2019
- RFC 8661Segment Routing MPLS Interworking with LDPCurrent
December 2019
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?