Skip to main content

Operations, Administration and Maintenance (OAM) features for RAW

Document Type Expired Internet-Draft (raw WG)
Expired & archived
Authors Fabrice Theoleyre , Georgios Z. Papadopoulos , Greg Mirsky , Carlos J. Bernardos
Last updated 2023-09-06 (Latest revision 2023-03-05)
Replaces draft-theoleyre-raw-oam-support
RFC stream Internet Engineering Task Force (IETF)
Intended RFC status (None)
Additional resources Mailing list discussion
Stream WG state WG Document
Associated WG milestones
Apr 2021
Working Group Adoption of OAM Document
Mar 2022
OAM Document submitted to IESG
Document shepherd (None)
IESG IESG state Expired
Consensus boilerplate Unknown
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, 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).


Fabrice Theoleyre
Georgios Z. Papadopoulos
Greg Mirsky
Carlos J. Bernardos

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