Operations, Administration and Maintenance (OAM) features for DetNet
draft-theoleyre-detnet-oam-support-00

Document Type Active Internet-Draft (individual)
Authors Fabrice Theoleyre  , Georgios Papadopoulos  , Greg Mirsky  , Carlos Bernardos 
Last updated 2020-10-25
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)
DetNet                                                      F. Theoleyre
Internet-Draft                                                      CNRS
Intended status: Standards Track                         G. Papadopoulos
Expires: April 28, 2021                                   IMT Atlantique
                                                               G. Mirsky
                                                               ZTE Corp.
                                                           CJ. Bernardos
                                                                    UC3M
                                                        October 25, 2020

  Operations, Administration and Maintenance (OAM) features for DetNet
                 draft-theoleyre-detnet-oam-support-00

Abstract

   Deterministic Networking (DetNet), as defined in RFC 8655, is aimed
   to provide a bounded end-to-end latency on top of the network
   infrastructure, comprising both Layer 2 bridged and Layer 3 routed
   segments.  This document's primary purpose is to detail the specific
   requirements of the Operation, Administration, and Maintenance (OAM)
   recommended to maintain a deterministic network.  With the
   implementation of the OAM framework in DetNet, an operator will have
   a real-time view of the network infrastructure regarding the
   network's ability to respect the Service Level Objective (SLO), such
   as packet delay, delay variation, and packet loss ratio, assigned to
   each data flow.

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 April 28, 2021.

Theoleyre, et al.        Expires April 28, 2021                 [Page 1]
Internet-Draft           OAM features for DetNet            October 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.  TEMPORARY EDITORIAL NOTES . . . . . . . . . . . . . . . . . .   2
   2.  Introduction  . . . . . . . . . . . . . . . . . . . . . . . .   3
     2.1.  Terminology . . . . . . . . . . . . . . . . . . . . . . .   3
     2.2.  Acronyms  . . . . . . . . . . . . . . . . . . . . . . . .   4
     2.3.  Requirements Language . . . . . . . . . . . . . . . . . .   4
   3.  Role of OAM in DetNet . . . . . . . . . . . . . . . . . . . .   4
   4.  Operation . . . . . . . . . . . . . . . . . . . . . . . . . .   5
     4.1.  Information Collection  . . . . . . . . . . . . . . . . .   5
     4.2.  Continuity Check  . . . . . . . . . . . . . . . . . . . .   5
     4.3.  Connectivity Verification . . . . . . . . . . . . . . . .   6
     4.4.  Route Tracing . . . . . . . . . . . . . . . . . . . . . .   6
     4.5.  Fault Verification/detection  . . . . . . . . . . . . . .   6
     4.6.  Fault Isolation/identification  . . . . . . . . . . . . .   7
   5.  Administration  . . . . . . . . . . . . . . . . . . . . . . .   7
     5.1.  Collection of metrics . . . . . . . . . . . . . . . . . .   7
     5.2.  Worst-case metrics  . . . . . . . . . . . . . . . . . . .   7
   6.  Maintenance . . . . . . . . . . . . . . . . . . . . . . . . .   8
     6.1.  Replication / Elimination . . . . . . . . . . . . . . . .   8
     6.2.  Resource Reservation  . . . . . . . . . . . . . . . . . .   8
     6.3.  Soft transition after reconfiguration . . . . . . . . . .   9
   7.  IANA Considerations . . . . . . . . . . . . . . . . . . . . .   9
   8.  Security Considerations . . . . . . . . . . . . . . . . . . .   9
   9.  Acknowledgments . . . . . . . . . . . . . . . . . . . . . . .   9
   10. Informative References  . . . . . . . . . . . . . . . . . . .   9
   Authors' Addresses  . . . . . . . . . . . . . . . . . . . . . . .  10

1.  TEMPORARY EDITORIAL NOTES

   This document is an Internet Draft, so it is work-in-progress by
Show full document text