Identification of Overlay Operations, Administration, and Maintenance (OAM)
draft-mirsky-rtgwg-oam-identify-01

• Status
• IESG evaluation record
• IESG writeups
• Email expansions
• History

• Versions
• 00
• 01

RTGWG Working Group                                            G. Mirsky
Internet-Draft                                                 ZTE Corp.
Intended status: Informational                         December 29, 2018
Expires: July 2, 2019

 Identification of Overlay Operations, Administration, and Maintenance
                                 (OAM)
                   draft-mirsky-rtgwg-oam-identify-01

Abstract

   This document analyzes how the presence of Operations,
   Administration, and Maintenance (OAM) control command and/or special
   data is identified in some overlay networks and an impact on the
   choice of identification may have on OAM functionality.

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 2, 2019.

Copyright Notice

   Copyright (c) 2018 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.

Mirsky                    Expires July 2, 2019                  [Page 1]
Internet-Draft         Overlay OAM Identification          December 2018

Table of Contents

   1.  Introduction  . . . . . . . . . . . . . . . . . . . . . . . .   2
   2.  Conventions used in this document . . . . . . . . . . . . . .   2
     2.1.  Terminology . . . . . . . . . . . . . . . . . . . . . . .   2
     2.2.  Keywords  . . . . . . . . . . . . . . . . . . . . . . . .   3
   3.  Overlay Network Encapsulations  . . . . . . . . . . . . . . .   3
     3.1.  Encapsulations with Meta-data . . . . . . . . . . . . . .   3
       3.1.1.  Available Solutions . . . . . . . . . . . . . . . . .   5
     3.2.  Fixed-size Encapsulations . . . . . . . . . . . . . . . .   5
     3.3.  Source Information Availability . . . . . . . . . . . . .   6
     3.4.  On-path OAM . . . . . . . . . . . . . . . . . . . . . . .   6
   4.  Conclusions . . . . . . . . . . . . . . . . . . . . . . . . .   7
   5.  IANA Considerations . . . . . . . . . . . . . . . . . . . . .   7
   6.  Security Considerations . . . . . . . . . . . . . . . . . . .   7
   7.  Acknowledgment  . . . . . . . . . . . . . . . . . . . . . . .   7
   8.  References  . . . . . . . . . . . . . . . . . . . . . . . . .   7
     8.1.  Normative References  . . . . . . . . . . . . . . . . . .   7
     8.2.  Informational References  . . . . . . . . . . . . . . . .   8
   Author's Address  . . . . . . . . . . . . . . . . . . . . . . . .  10

1.  Introduction

   Operations, Administration, and Maintenance (OAM) protocols are used
   to detect, localize defects in the network, and monitor network
   performance.  Some OAM functions, e.g., failure detection, work in
   the network proactively, while others, e.g., defect localization,
   usually performed on-demand.  These tasks achieved by a combination
   of active, passive, and hybrid OAM methods, as defined in [RFC7799].

   This document analyzes how the presence of Operations,
   Administration, and Maintenance (OAM) control command and/or special
   data, i.e., OAM packet, is identified in some overlay networks, and
   an impact the choice of identification may have on OAM functionality
   of active and hybrid OAM methods for the respective overlay network
   encapsulation.

2.  Conventions used in this document

2.1.  Terminology

   AMM Alternate Marking method

   BIER Bit Indexed Explicit Replication

   DetNet Deterministic Networks

   GUE Generic UDP Encapsulation

Mirsky                    Expires July 2, 2019                  [Page 2]
Internet-Draft         Overlay OAM Identification          December 2018

   HTS Hybrid Two-step

   NSH Network Service Header

   NVO3 Network Virtualization Overlays

   OAM Operations, Administration and Maintenance

   SFC Service Function Chaining

   TLV Type-Length-Value

   VXLAN-GPE Generic Protocol Extension for VXLAN

   Underlay Network or Underlay Layer: The network that provides