| Internet-Draft | OAM features for RAW | November 2026 |
| Theoleyre, et al. | Expires 23 May 2027 | [Page] |
Some critical applications may use a wireless infrastructure. However, wireless networks exhibit a bandwidth of several orders of magnitude lower than wired networks. Besides, wireless transmissions are lossy by nature; the probability that a packet cannot be decoded correctly by the receiver may be quite high. In these conditions, providing high reliability and a low delay is challenging. This document lists the requirements of the Operation, Administration, and Maintenance (OAM) features are recommended to provide availability and reliability on top of a collection of wireless segments. This document describes the benefits, problems, and trade-offs for using OAM in wireless networks to achieve Service Level Objectives (SLO).¶
This Internet-Draft is submitted in full conformance with the provisions of BCP 78 and BCP 79.¶
Internet-Drafts are working documents of the Internet Engineering Task Force (IETF). Note that other groups may also distribute working documents as Internet-Drafts. The list of current Internet-Drafts is at https://datatracker.ietf.org/drafts/current/.¶
Internet-Drafts are draft documents valid for a maximum of six months and may be updated, replaced, or obsoleted by other documents at any time. It is inappropriate to use Internet-Drafts as reference material or to cite them other than as "work in progress."¶
This Internet-Draft will expire on 23 May 2027.¶
Copyright (c) 2026 IETF Trust and the persons identified as the document authors. All rights reserved.¶
This document is subject to BCP 78 and the IETF Trust's Legal Provisions Relating to IETF Documents (https://trustee.ietf.org/license-info) in effect on the date of publication of this document. Please review these documents carefully, as they describe your rights and restrictions with respect to this document. Code Components extracted from this document must include Revised BSD License text as described in Section 4.e of the Trust Legal Provisions and are provided without warranty as described in the Revised BSD License.¶
The Reliable and Available Wireless (RAW) working group aims to extend DetNet to approach end-to-end deterministic performance over a network that includes scheduled wireless segments. In wired networks, many approaches try to enable Quality of Service (QoS) by implementing traffic differentiation so that routers handle each type of packet differently.¶
Deterministic Networking (DetNet) [RFC8655] has proposed to provide a bounded end-to-end latency on top of the network infrastructure, comprising both Layer 2 bridged and Layer 3 routed segments. Their work covers the data plane, OAM, time synchronization, management, control, and security.¶
However, wireless networks create specific challenges. First, radio bandwidth is significantly lower than in wired networks. Under these conditions, the volume of signaling messages must be very limited. Even worse, wireless links are lossy: a Layer 2 transmission may or may not be decoded correctly by the receiver, depending on a broad set of parameters. Thus, providing high reliability through wireless segments is particularly challenging.¶
Wired networks rely on the concept of links. All the devices attached to a link receive any transmission. The concept of a link in wireless networks is somewhat different from what many are used to in wireline networks. A receiver may or may not receive a transmission, depending on the presence of a colliding transmission, the radio channel's quality, and the external interference. Besides, a wireless transmission is broadcast by nature: any neighboring device may be able to decode it. This document includes detailed information on the implications for the OAM features.¶
Last but not least, radio links present volatile characteristics. If the wireless networks use an unlicensed band, packet losses are no longer temporally and spatially independent. Typically, links may exhibit a very bursty characteristic, where several consecutive packets may be dropped because of, e.g., temporary external interference. Thus, providing availability and reliability on top of the wireless infrastructure requires specific Layer 3 mechanisms to counteract these bursty losses. Besides, Layer 3 has to be informed of the physical characteristics to make the right decision, and to avoid exacerbating physical issues (e.g., overloaded link because it became unreliable, overloaded radio channels).¶
Operations, Administration, and Maintenance (OAM) Tools are of primary importance for IP networks [RFC7276]. They define a toolset for fault detection, isolation, and performance measurement.¶
The primary purpose of this document is to detail the specific requirements of the OAM features recommended to provide reliability and availability on top of a collection of wireless segments. This document describes the benefits, problems, and trade-offs for using OAM in wireless networks to provide these properties.¶
In this document, the term OAM will be used according to its definition specified in [RFC6291]. We expect to implement an OAM framework in RAW networks to maintain a real-time view of the network infrastructure, and its ability to respect the Service Level Objectives (SLO), such as delay and reliability, assigned to each data flow.¶
We re-use here the same terminology as [RFC9551]:¶
OAM entity: a data flow to be monitored for defects and/or whose performance metrics are measured. For such an entity, we define the following terms:¶
Active measurement methods (as defined in [RFC7799]) modify a normal data flow by inserting novel fields, injecting specially constructed test packets [RFC2544]). It is critical for the quality of information obtained since generated test packets are in-band with the monitored data flow. In other words, a test packet is required to cross the same network nodes and links and receive the same Quality of Service (QoS) treatment as a data packet. Active methods may implement one of these two strategies:¶
We also adopt the following terminology, which is particularly relevant for RAW-specific (aka wireless) segments.¶
OAM Operations, Administration, and Maintenance¶
DetNet Deterministic Networking¶
PDR Packet Delivery Ratio¶
PREOF Packet Replication, Elimination, and Ordering Functions¶
PSE Path Selection Engine [RFC9912]¶
QoS Quality of Service¶
RAW Reliable and Available Wireless¶
SAP Service Activation Procedures¶
SLO Service Level Objective¶
SNMP Simple Network Management Protocol¶
SDN Software-Defined Network¶
The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", "SHOULD", "SHOULD NOT", "RECOMMENDED", "NOT RECOMMENDED", "MAY", and "OPTIONAL" in this document are to be interpreted as described in BCP 14 [RFC2119] [RFC8174] when, and only when, they appear in all capitals, as shown here.¶
RAW networks expect to provide availability and reliability over a wireless network infrastructure. Most critical applications will define an SLO required for the data flows they generates. RAW expects to use OAM to improve RAW operation at the service and forwarding sub-layers.¶
To respect strict guarantees, RAW relies on the Path Selection Engine (PSE) (as defined in [RFC9912] to monitor and maintain the L3 network. Any L2 scheduling mechanism may be used to allocate transmission opportunities, based on the radio link characteristics, the SLO of the flows, or the number of packets to forward. The PSE exploits the L2 resources reserved by the scheduler and organizes the L3 paths to introduce redundancy, fault tolerance, and create backup paths. OAM represents the core of the pre-provisioning process by supervising the network. It maintains a global view of the network resources to detect defects, faults, over-provisioning, and anomalies.¶
Fault tolerance also assumes that multiple paths must be provisioned so that an end-to-end circuit remains operational regardless of the conditions. The Packet Replication and Elimination Function ([RFC9912]) on a node is typically controlled by the PSE. OAM mechanisms can be used to monitor that PREOF is working correctly on a node and within the domain.¶
To be energy-efficient, out-of-band OAM SHOULD only be used to report aggregated statistics (e.g., counters, histograms) from the nodes using, e.g., SNMP or Netconf/Restconf using YANG-based data models. The out-of-band OAM flow MAY use a dedicated control and management channel for this purpose.¶
RAW supports both proactive and on-demand troubleshooting. Proactively, it is necessary to detect anomalies, report defects, or reduce over-provisioning if it is not required. However, on-demand may also be required to identify the cause of a specific defect. Indeed, some specific faults may only be detected with a global, detailed view of the network, which is too expensive to acquire in the normal operating mode.¶
The specific characteristics of RAW are discussed below.¶
In wireless networks, a link does not exist physically. A device has a set of neighbors corresponding to all devices that have a non-null probability of receiving its packets correctly. We make a distinction between:¶
In scheduled radio networks, p2mp and p2p links are commonly not scheduled simultaneously to save energy and/or to reduce the number of collisions. More precisely, only a fraction of the neighbors may wake up at a given instant.¶
Each wireless link is associated with a link quality, often measured as the Packet Delivery Ratio (PDR), i.e., the probability that the receiver can decode the packet correctly. It is worth noting that this link quality depends on many criteria, such as the level of external interference, the presence of concurrent transmissions, or the radio channel state. This link quality is even time-variant. For p2mp links, consequently, we have a collection of PDRs (one value per receiver). Other more sophisticated, aggregated metrics exist for these p2mp links, such as [anycast-property]¶
In modern switched networks, unicast transmissions are delivered exclusively to the destination. Wireless networks are much closer to the traditional shared access wired networks. Practically, unicast and broadcast frames are handled similarly at the physical layer. The link layer filters frames to discard irrelevant receptions (e.g., different unicast MAC addresses).¶
However, contrary to wired networks, we cannot ensure that a packet is received by all the devices attached to the Layer 2 segment. It depends on the radio channel state between the transmitter(s) and the receiver(s). In particular, concurrent transmissions may be possible or not, depending on the radio conditions (e.g., do the different transmitters use a different radio channel or are they sufficiently spatially separated?)¶
Multiple neighbors may receive a transmission. Thus, anycast Layer 2 forwarding helps to maximize reliability by assigning multiple receivers to a single transmission. That way, the packet is lost only if none of the receivers decode it. Practically, it has been proven that different neighbors may exhibit very different radio conditions, and that reception independence may hold for some of them [anycast-property]. Anycast transmission typically exploits p2mp links.¶
In a wireless network, additional transmission opportunities are provisioned to accommodate packet losses. Thus, the end-to-end delay consists of:¶
OAM features will enable reliability and availability with robust operations both for forwarding and routing purposes.¶
The information-exchange model should match that of a DetNet network to ensure interoperability. YANG may typically fulfill this objective.¶
However, RAW networks imply specific constraints (e.g., low bandwidth, packet losses, cost of medium access) that may require to minimize the volume of information to collect. Thus, we discuss in Section 5.1 different ways to collect information, i.e., transfer the OAM information physically from the emitter to the receiver. This corresponds to passive OAM as defined in [RFC7799].¶
Similarly to DetNet, we need to verify that the source and the destination are connected (at least one valid path exists).¶
As in DetNet, we have to verify the absence of misconnection. Here, we focus on the RAW specifics.¶
Because of radio transmissions' broadcast nature, several receivers may be active at the same time to enable anycast Layer 2 forwarding. Thus, the connectivity verification must test any combination. We also consider priority-based mechanisms for anycast forwarding, i.e., all the receivers have different probabilities of forwarding a packet. To verify a delay SLO for a given flow, we must also consider all the possible combinations, leading to a probability distribution function for end-to-end transmissions. If this verification is implemented naively, the number of combinations to test may be exponential and too costly for wireless networks with low bandwidth.¶
Wireless networks are broadcast by nature: a radio transmission can be decoded by any radio neighbor. In multihop wireless networks, several paths exist between two endpoints. In hub networks, a device may be covered by several Access Points. The network must select the most efficient path or AP, concerning specifically the reliability, and the delay.¶
Thus, multipath routing / multi-attachment can be viewed as making the network more fault-tolerant. Even better, we can exploit the broadcast nature of wireless networks: we may have multiple Maintenance Intermediate Points (MIP) for each of these kinds of hop. While it may be reasonable in the multi-attachment case, the complexity quickly increases with the path length. Indeed, each MIP has several possible next hops in the forwarding plane. Thus, all the possible paths between two MEPs should be retrieved, which may quickly become intractable if we apply a naive approach.¶
Wired networks tend to present stable performances. On the contrary, wireless networks are time-variant. We must consequently make a distinction between expected evolutions and malfunctions.¶
While DetNet already expects to identify malfunctions, some problems are specific to wireless networks. We must consequently collect metrics and implement algorithms tailored for wireless networking.¶
For instance, the decrease in the link quality may be caused by several factors: external interference, obstacles, multipath fading, mobility. It is fundamental to be able to discriminate the different causes to make the right decision.¶
The RAW network has to expose a collection of metrics to support an operator making proper decisions, including:¶
These metrics should be collected per device, virtual circuit, and path, as DetNet already does. However, in RAW, we have to deal with them at a finer granularity:¶
RAW inherits the same requirements as DetNet: we need to know the distribution of a collection of metrics. Besides, wireless networks are known to be highly variable. Changes may be frequent, and may exhibit a periodical pattern. Collecting and analyzing this amount of measurements is challenging. OAM should find an efficient method to encode these time-series in a compact form.¶
We have to minimize the number of statistics / measurements to exchange:¶
In conclusion, we have to take care of power and bandwidth consumption. The following techniques reduce the cost of such maintenance:¶
Several passive techniques can be combined. For instance, the DetNet forwarding sublayer MAY combine In-band Network Telemetry (INT) with P4, iOAM and iPath to compute and report different statistics in the track (e.g., number of link-layer retransmissions, link reliability).¶
The MEP will collect measurements from the OAM probes received in the monitored track. However, the aggregated statistics must then be reported to the other MEP that injected the probes. Unfortunately, the monitored track MAY be unidirectional. In this case, the statistics have to be reported out-of-band (through, e.g., a dedicated control or management channel).¶
It is worth noting that Active OAM and Passive OAM techniques are not mutually exclusive. In particular, Active OAM is useful when a statistic cannot be accurately acquired passively.¶
Besides, Active OAM may also use piggybacking techniques: the OAM packet may be piggybacked in a frame if the MTU is sufficient. Indeed, increasing the number of transmissions in radio networks may very negatively impact the performance of radio networks, particularly for scheduled access, with fixed timeslot durations. Thus, OAM packets may be buffered until another frame has sufficient space, and has to be transmitted to the same neighbor. In conclusion, active OAM packets may be out-of-band or in-band.¶
Maintenance needs to facilitate the maintenance (repairs and upgrades). In wireless networks, repairs are expected to occur much more frequently, since the link quality may be highly time-variant. Thus, maintenance represents a key feature for RAW.¶
Because of the wireless medium, the link quality may fluctuate, and the network needs to reconfigure itself continuously. During this transient state, flows may begin to be gradually re-forwarded, consuming resources in different parts of the network. OAM has to make a distinction between a metric that changed because of an usual network change (e.g., flow redirection) and an unexpected event (e.g., a fault). In a general manner, OAM mechanisms have to provide a consistent view of the OAM domain, even during the reconfiguration.¶
RAW needs to implement self-optimization features. While the network is configured to be fault-tolerant, a reconfiguration may be required to keep on respecting long-term objectives. The network must continuously retrieve the state of the network, to judge about the relevance of a reconfiguration. More precisely, the OAM mechanisms have to provide enough information to predict and quantify:¶
Wireless networks exhibit non linear dependencies among links / radio channels / technologies that complexify significantly such predictions.¶
This section lists requirements for OAM in a RAW domain:¶
This document has no actionable requirements for IANA. This section can be removed before the publication.¶
OAM capabilities described in this document are intended to support the deployment and operation of RAW networks. RAW environments introduce operational challenges that differ from those of traditional wired networks because wireless links may exhibit time-varying quality, bursty loss characteristics, mobility effects, interference, and multi-path forwarding behaviors. These characteristics influence how OAM information is collected, interpreted, and acted upon.¶
Operators continuously monitor service-level and path-level performance metrics associated with RAW forwarding. Relevant metrics include packet loss, PDR, latency, latency variation, retransmission activity, radio link quality indicators, resource utilization, and path availability. Because wireless conditions can fluctuate rapidly, operators continuously evaluate both instantaneous measurements and longer-term trends to distinguish transient impairments from persistent faults.¶
When PREOF is used, the combination of proactive and on-demand monitoring MUST be used to verify that replication and elimination processes operate correctly and continue to satisfy the service objectives associated with the protected flows.¶
RAW OAM mechanisms support proactive fault detection as well as on-demand diagnostics. Operators MUST establish thresholds and policies appropriate to the deployed radio technologies and service objectives. Because wireless environments naturally experience performance variations, detection mechanisms MUST enable operators to distinguish expected variations from conditions that require operational intervention.¶
Route tracing and connectivity verification functions can assist in identifying forwarding anomalies, misconfigurations, path degradation, or failures affecting wireless segments. In deployments that support multiple candidate forwarding paths or anycast forwarding techniques, operators should be aware that observed forwarding behavior may vary over time as radio conditions change.¶
OAM traffic consumes network resources that may otherwise be available to user traffic. This consideration is particularly important in wireless environments where bandwidth and device energy resources can be constrained. Operators MUST configure OAM measurement frequencies, reporting intervals, telemetry export policies, and diagnostic procedures to balance operational visibility against resource consumption.¶
Where possible, passive and hybrid measurements ([RFC7799]), aggregation of collected statistics, can reduce operational overhead. More detailed active measurements can be activated when anomalies or performance degradations are detected.¶
Implementations MUST provide operators with the capability to configure OAM functions, including measurement intervals, reporting policies, telemetry export parameters, continuity-check behavior, and fault-detection thresholds. The management interfaces MAY support automated provisioning and integration with network management and controller-based systems. Guidance from operational manageability best practices recommends that protocol specifications consider how configuration and state information can be exposed to management systems and operational tooling.¶
RAW networks are expected to adapt to changing wireless conditions by modifying forwarding behavior, schedules, or path selection. During such transitions, measured performance may temporarily differ from steady-state conditions. Intelligent correlation of the collected telemetry information enables operators to account for these transient conditions when evaluating OAM reports and diagnosing faults. OAM data collected during reconfiguration events provides valuable information for validating network adaptation procedures and assessing their effectiveness.¶
Before carrying production traffic, operators MAY use Service Activation Procedures (SAP) to verify that OAM functions correctly measure and report performance information across RAW paths. Verification with SAP MUST include continuity checks, connectivity verification, telemetry collection, fault reporting, and route-tracing capabilities, as applicable to the deployment. SAP MUST also enable verification that OAM packets receive forwarding treatment representative of the monitored services whenever in-band measurement techniques are used.¶
Implementations MAY expose operational state and performance information using mechanisms that enable integration with existing operational workflows and telemetry systems. Examples include standardized data models, telemetry export functions, and controller interfaces. The selection of a particular management protocol or data-modeling technology is deployment-specific and outside the scope of this document. Guidance from manageability best practices recommends that protocol specifications identify the operational information required to deploy, monitor, and maintain the technology.¶
This document lists the OAM requirements for an OAM wireless domain and does not raise any security concerns or issues in addition to ones common to networking and those specific to a DetNet discussed in [RFC9055].¶
The authors express their appreciation and gratitude to the colleagues who carefully reviewed the draft and shared their comments (Xavi Vilajosana, Dominique Barthel, Pascal Thubert), and all the RAW and Detnet working group members in general.¶