Skip to main content

Operations, Administration and Maintenance (OAM) features for RAW

Document Type Replaced Internet-Draft (individual)
Expired & archived
Authors Fabrice Theoleyre , Georgios Z. Papadopoulos , Greg Mirsky
Last updated 2020-10-25
Replaced by draft-ietf-raw-oam-support
RFC stream (None)
Intended RFC status (None)
Stream Stream state (No stream defined)
Consensus boilerplate Unknown
RFC Editor Note (None)
IESG IESG state Replaced by draft-ietf-raw-oam-support
Telechat date (None)
Responsible AD (None)
Send notices to (None)

This Internet-Draft is no longer active. A copy of the expired Internet-Draft is available in these formats:


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, guaranteeing the network infrastructure works properly is particularly challenging, since we need to address some issues specific to wireless networks. This document lists the requirements of the Operation, Administration, and Maintenance (OAM) features recommended to construct a predictable communication infrastructure 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).


Fabrice Theoleyre
Georgios Z. Papadopoulos
Greg Mirsky

(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)