RFC 9912: Reliable and Available Wireless (RAW) Architecture
In plain English — editorial summary, not part of the RFC
Reliable and Available Wireless (RAW) extends the reliability and availability of Deterministic Networking (DetNet) to networks composed of any combination of wired and wireless segments. The RAW architecture leverages and extends RFC 8655 ("Deterministic Networking Architecture") to adapt to challenges that prominently affect the wireless medium, notably intermittent transmission loss. This document defines a network control loop that optimizes the use of constrained bandwidth and energy while ensuring the expected DetNet services. The loop involves a new Point of Local Repair (PLR) function in the DetNet Service sub-layer that dynamically selects the DetNet path(s) for packets to route around local connectivity degradation.
Document record
- Document ID
- RFC9912
- Published
- April 2026
- Authors
- P. Thubert
- Status
- INFORMATIONAL
- 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 9914Root-Initiated Routing State in the Routing Protocol for Low-Power and Lossy Networks (RPL)Current
April 2026
- RFC 9938A Framework for the Deterministic Networking (DetNet) Controller PlaneCurrent
March 2026
- RFC 9634Operations, Administration, and Maintenance (OAM) for Deterministic Networking (DetNet) with the IP Data PlaneCurrent
October 2024
- RFC 9546Operations, Administration, and Maintenance (OAM) for Deterministic Networking (DetNet) with the MPLS Data PlaneCurrent
February 2024
- RFC 9320Deterministic Networking (DetNet) Bounded LatencyCurrent
November 2022
- RFC 9055Deterministic Networking (DetNet) Security ConsiderationsCurrent
June 2021
- RFC 9016Flow and Service Information Model for Deterministic Networking (DetNet)Current
March 2021
- RFC 8964Deterministic Networking (DetNet) Data Plane: MPLSCurrent
January 2021
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?