Framework of Operations, Administration and Maintenance (OAM) for Deterministic Networking (DetNet)
draft-tpmb-detnet-oam-framework-00

Document Type Active Internet-Draft (individual)
Authors Greg Mirsky  , Fabrice Theoleyre  , Georgios Papadopoulos  , Carlos Bernardos 
Last updated 2021-01-15
Replaces draft-theoleyre-detnet-oam-support
Stream (None)
Intended RFC status (None)
Formats plain text xml pdf htmlized (tools) htmlized bibtex
Stream Stream state (No stream defined)
Consensus Boilerplate Unknown
On Agenda detnet at IETF-110
RFC Editor Note (None)
IESG IESG state I-D Exists
Telechat date
Responsible AD (None)
Send notices to (None)
DetNet                                                         G. Mirsky
Internet-Draft                                                 ZTE Corp.
Intended status: Standards Track                            F. Theoleyre
Expires: July 19, 2021                                              CNRS
                                                         G. Papadopoulos
                                                          IMT Atlantique
                                                           CJ. Bernardos
                                                                    UC3M
                                                        January 15, 2021

   Framework of Operations, Administration and Maintenance (OAM) for
                   Deterministic Networking (DetNet)
                   draft-tpmb-detnet-oam-framework-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, 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 July 19, 2021.

Mirsky, et al.            Expires July 19, 2021                 [Page 1]
Internet-Draft         Framework of OAM for DetNet          January 2021

Copyright Notice

   Copyright (c) 2021 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 . . . . . . . . . . . . . . . . . . . . . . .   3
     1.2.  Acronyms  . . . . . . . . . . . . . . . . . . . . . . . .   4
     1.3.  Requirements Language . . . . . . . . . . . . . . . . . .   4
   2.  Role of OAM in DetNet . . . . . . . . . . . . . . . . . . . .   5
   3.  Operation . . . . . . . . . . . . . . . . . . . . . . . . . .   5
     3.1.  Information Collection  . . . . . . . . . . . . . . . . .   5
     3.2.  Continuity Check  . . . . . . . . . . . . . . . . . . . .   6
     3.3.  Connectivity Verification . . . . . . . . . . . . . . . .   6
     3.4.  Route Tracing . . . . . . . . . . . . . . . . . . . . . .   6
     3.5.  Fault Verification/detection  . . . . . . . . . . . . . .   6
     3.6.  Fault Isolation/identification  . . . . . . . . . . . . .   7
     3.7.  Use of Hybrid OAM in DetNet . . . . . . . . . . . . . . .   7
   4.  Administration  . . . . . . . . . . . . . . . . . . . . . . .   7
     4.1.  Collection of metrics . . . . . . . . . . . . . . . . . .   8
     4.2.  Worst-case metrics  . . . . . . . . . . . . . . . . . . .   8
   5.  Maintenance . . . . . . . . . . . . . . . . . . . . . . . . .   8
     5.1.  Replication / Elimination . . . . . . . . . . . . . . . .   8
     5.2.  Resource Reservation  . . . . . . . . . . . . . . . . . .   9
     5.3.  Soft transition after reconfiguration . . . . . . . . . .   9
   6.  Requirements  . . . . . . . . . . . . . . . . . . . . . . . .   9
   7.  IANA Considerations . . . . . . . . . . . . . . . . . . . . .  10
   8.  Security Considerations . . . . . . . . . . . . . . . . . . .  11
   9.  Acknowledgments . . . . . . . . . . . . . . . . . . . . . . .  11
   10. References  . . . . . . . . . . . . . . . . . . . . . . . . .  11
     10.1.  Normative References . . . . . . . . . . . . . . . . . .  11
Show full document text