Operations, Administration and Maintenance (OAM) features for RAW
draft-theoleyre-raw-oam-support-02

Document Type Active Internet-Draft (individual)
Last updated 2020-04-11
Stream (None)
Intended RFC status (None)
Formats plain text xml pdf htmlized (tools) htmlized bibtex
Stream Stream state (No stream defined)
Consensus Boilerplate Unknown
RFC Editor Note (None)
IESG IESG state I-D Exists
Telechat date
Responsible AD (None)
Send notices to (None)
RAW                                                         F. Theoleyre
Internet-Draft                                                      CNRS
Intended status: Standards Track                         G. Papadopoulos
Expires: October 13, 2020                                 IMT Atlantique
                                                               G. Mirsky
                                                               ZTE Corp.
                                                          April 11, 2020

   Operations, Administration and Maintenance (OAM) features for RAW
                   draft-theoleyre-raw-oam-support-02

Abstract

   Some critical applications may use a wireless infrastructure.
   However, wireless networks exhibit a bandiwidth 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).

Status of This Memo

   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 October 13, 2020.

Theoleyre, et al.       Expires October 13, 2020                [Page 1]
Internet-Draft            OAM features for RAW                April 2020

Copyright Notice

   Copyright (c) 2020 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 Simplified BSD License text as described in Section 4.e of
   the Trust Legal Provisions and are provided without warranty as
   described in the Simplified BSD License.

Table of Contents

   1.  Introduction  . . . . . . . . . . . . . . . . . . . . . . . .   3
     1.1.  Terminology . . . . . . . . . . . . . . . . . . . . . . .   4
     1.2.  Acronyms  . . . . . . . . . . . . . . . . . . . . . . . .   4
     1.3.  Requirements Language . . . . . . . . . . . . . . . . . .   4
   2.  Role of OAM in RAW  . . . . . . . . . . . . . . . . . . . . .   5
   3.  Operation . . . . . . . . . . . . . . . . . . . . . . . . . .   5
     3.1.  Information Collection  . . . . . . . . . . . . . . . . .   5
     3.2.  Continuity Check  . . . . . . . . . . . . . . . . . . . .   5
     3.3.  Connectivity Verification . . . . . . . . . . . . . . . .   6
     3.4.  Route Tracing . . . . . . . . . . . . . . . . . . . . . .   6
     3.5.  Fault Verification/detection  . . . . . . . . . . . . . .   6
     3.6.  Fault Isolation/identification  . . . . . . . . . . . . .   7
   4.  Administration  . . . . . . . . . . . . . . . . . . . . . . .   7
     4.1.  Collection of metrics . . . . . . . . . . . . . . . . . .   8
     4.2.  Worst-case metrics  . . . . . . . . . . . . . . . . . . .   8
     4.3.  Energy efficiency constraint  . . . . . . . . . . . . . .   8
   5.  Maintenance . . . . . . . . . . . . . . . . . . . . . . . . .   9
     5.1.  Multipath Routing . . . . . . . . . . . . . . . . . . . .   9
     5.2.  Replication / Elimination . . . . . . . . . . . . . . . .   9
     5.3.  Resource Reservation  . . . . . . . . . . . . . . . . . .  10
     5.4.  Soft transition after reconfiguration . . . . . . . . . .  10
   6.  IANA Considerations . . . . . . . . . . . . . . . . . . . . .  10
   7.  Security Considerations . . . . . . . . . . . . . . . . . . .  10
   8.  Acknowledgments . . . . . . . . . . . . . . . . . . . . . . .  10
   9.  Informative References  . . . . . . . . . . . . . . . . . . .  10
   Authors' Addresses  . . . . . . . . . . . . . . . . . . . . . . .  11
Show full document text