Operations, Administration and Maintenance (OAM) features for RAW
draft-ietf-raw-oam-support-06
Document | Type |
Expired Internet-Draft
(individual)
Expired & archived
|
|
---|---|---|---|
Authors | Fabrice Theoleyre , Georgios Z. Papadopoulos , Greg Mirsky , Carlos J. Bernardos | ||
Last updated | 2023-10-20 (Latest revision 2023-03-05) | ||
Replaces | draft-theoleyre-raw-oam-support | ||
RFC stream | (None) | ||
Intended RFC status | (None) | ||
Formats | |||
Stream | Stream state | (No stream defined) | |
Associated None milestones |
|
||
Consensus boilerplate | Unknown | ||
RFC Editor Note | (None) | ||
IESG | IESG state | Expired | |
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:
Abstract
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).
Authors
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.)