Summary

  • RFC 9913 is an IETF Informational RFC published in April 2026. It surveys Wi-Fi 6/7, TSCH, 3GPP 5G and LDACS as possible lower-layer contributors to RAW and deterministic flows.
  • The relevant contract is not a radio label. It is the usable exposure of synchronisation, scheduling, ARQ, modulation and coding variation (MCS), broadcast, MU-MIMO, constructive interference, overhearing, diversity and telemetry.
  • RFC 9913 does not define protocol behaviours or operational practices. It does not establish deployment, equivalent control surfaces, or deterministic guarantees from a feature list.

The practical question is whether a network plane can obtain comparable meanings from unlike media. A Wi-Fi 6/7 deployment may expose coordinated scheduling, spatial transmission and retransmission choices; TSCH brings time-slotted channel hopping and a tightly structured schedule; 3GPP 5G combines managed radio resources, scheduling and configurable coding or retransmission; LDACS operates in an aviation environment where spectrum, regulation and interference assumptions matter. These are useful distinctions, not evidence that the technologies offer the same controls.

RFC 9913's capability survey covers synchronisation, resource allocation and failure handling rather than prescribing a common implementation. ARQ may trade delay for recovery. MCS changes the robustness-throughput balance. Broadcast, MU-MIMO, constructive interference and overhearing can provide different routes to reach receivers or create diversity, but their observability and failure correlations differ. Reliability may be composed across space, time and frequency; it is not automatically created by naming several mechanisms.

Scheduling can allocate time and frequency resources, reduce collisions, support diversity, conserve bandwidth and save energy. It remains bounded by medium access, interference, available bandwidth, device energy, regulation and what the implementation can actually observe and report. A normalization boundary therefore needs explicit units and semantics: clock quality and alignment, resource ownership, retry timing, MCS state, diversity scope, correlation assumptions and measurement confidence.

Evidence and separation

This thesis is deliberately narrower than adjacent coverage. RFC 9912 addresses the RAW recovery graph, local packet-loss-ratio authority and local repair timescale; it is not this article's capability-normalization thesis. RFC 9911 concerns YANG type migration, not wireless capability normalization. RFC 9910 concerns RDAP authoritative-service discovery, not radio control. RFC 9907 concerns YANG review interfaces and groupings, not the exposed behaviour of four radio technologies. Those RFCs are separation evidence, not RAW capability evidence.

The architecture boundary comes from RFC 9912 and RFC 8655; use-case context comes from RFC 9450, and measurement context from RFC 9551. The primary survey is RFC 9913. The adjacent separation references are RFC 9911, RFC 9910, and RFC 9907.

Claim-to-RFC evidence ledger

Claim Evidence
Four technologies and their lower-layer capabilities differ RFC 9913, Sections 1 and 4–7
Synchronisation, scheduling, ARQ, MCS, broadcast, MU-MIMO, constructive interference and overhearing matter RFC 9913, Section 1
Diversity spans space, time and frequency RFC 9913, Section 3.2
Scheduling faces bandwidth, energy, interference and regulatory limits RFC 9913, Section 3.3
Architecture, use cases and OAM bound interpretation RFC 9912, RFC 8655, RFC 9450, RFC 9551
Adjacent work covers migration, discovery and review interfaces RFC 9911, RFC 9910, RFC 9907