Operations, Administration and Maintenance (OAM) for Overlay Networks: Gap Analysis
draft-ooamdt-rtgwg-oam-gap-analysis-00

Abstract

This document provides an overview of the Operations, Administration, and Maintenance (OAM) for overlay networks. The OAM toolset includes set of fault management and performance monitoring capabilities (operating in the data plane) that comply with the Overlay OAM Requirements. Insufficient functional coverage of existing OAM protocols also noted in this document. The protocol definitions for each of the Overlay OAM tools to be defined in separate documents.

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 http://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 September 22, 2016.

Copyright Notice

Copyright (c) 2016 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 (http://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
• 1.1. Conventions used in this document
• 1.1.1. Terminology
• 1.1.2. Requirements Language
• 2. Overlay OAM Toolset
• 2.1. Overlay OAM Fault Management
• 2.1.1. Proactive Continuity Check and Connectivity Verification
• 2.1.2. On-demand Continuity Check and Connectivity Verification
• 2.1.3. Alarm Indication Signal
• 2.2. Overlay OAM Performance Measurement
• 2.2.1. Overlay OAM PM Active
• 2.2.2. Overlay OAM PM Passive
• 2.3. Telemetry in Overlay OAM
• 2.4. Conclusions
• 3. IANA Considerations
• 4. Security Considerations
• 5. Acknowledgement
• 6. References
• 6.1. Normative References
• 6.2. Informative References
• Authors' Addresses

1. Introduction

Operations, Administration, and Maintenance (OAM) toolset provides methods for fault management and performance monitoring in each layer of the network, in order to improve their ability to support services with guaranteed and strict Service Level Agreements (SLAs) while reducing operational costs.

[RFC7276] provided detailed analysis of OAM protocols. Since its completion several new protocols that define data plane encapsulation were introduced. That presented both need to re-evaluate existing set of OAM tools and opportunity to build it into set of tools that can be used and re-used for different data plane protocols.

Overlay OAM Requirements define the set of requirements for OAM in Overlay networks. The OAM solution for Overlay networks, developed by the design team, has two objectives:

• The Overlay OAM toolset should be developed based on existing IP and IP/MPLS architecture, technology, and toolsets.
• The Overlay OAM operational experience should be similar to that in other, e.g. IP and IP/MPLS, networks.

The Overlay OAM toolset may use some or all of the following OAM protocols designed at IETF:

• proactive continuity check:
  • Bidirectional Forwarding Detection (BFD) for point-to-point as defined in [RFC5880], [RFC5882], [RFC5883], [RFC5884], [RFC5885], [RFC6428] and [RFC7726];
  • BFD for multipoint network as defined in [I-D.ietf-bfd-multipoint] and [I-D.ietf-bfd-multipoint-active-tail];
  • S-BFD as defined in [I-D.ietf-bfd-seamless-base] and [I-D.ietf-bfd-seamless-ip];

• on-demand continuity check and connectivity verification:
  • MPLS Echo Request/Reply, a.k.a. LSP Ping, as defined in [RFC4379] and its numerous extensions;
  • LSP Self-ping, as defined in [RFC7746];
  • [I-D.kumarzheng-bier-ping] is a good example of generic troubleshooting and defect localization tool that can be extended and suited for more specific requirements of the particular type of an overlay network;

• performance measurement:
  • packet loss and delay measurement in MPLS networks, as defined in [RFC6374] with ability to export measurement results for post-processing [I-D.ietf-mpls-rfc6374-udp-return-path];
  • Two-Way Active Measurement Protocol (TWAMP), as defined in [RFC5357], [RFC6038], and [RFC7750];
  • use of the Marking Method [I-D.tempia-ippm-p3m] that, if accordingly supported by the overlay layer, can behave as close as technically possible to a passive method to measure performance, e.g. [I-D.mirsky-bier-pmmm-oam].

1.1. Conventions used in this document

1.1.1. Terminology

Term "Overlay OAM" used in this document interchangeably with longer version "set of OAM protocols, methods and tools for Overlay networks".

BFD Bidirectional Forwarding Detection

FM Fault Management

OAM Operations, Administration, and Maintenance

PM Performance Measurement

SLA Service Level Agreement

TWAMP Two-Way Active Measurement Protocol

1.1.2. Requirements Language

The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", "SHOULD", "SHOULD NOT", "RECOMMENDED", "NOT RECOMMENDED", "MAY", and "OPTIONAL" in this document are to be interpreted as described in [RFC2119].

2. Overlay OAM Toolset

2.1. Overlay OAM Fault Management

Protocols that enable Fault Management functions of OAM toolset are comprised of protocols that perform proactive and on-demand defect detection and failure localization.

2.1.1. Proactive Continuity Check and Connectivity Verification

Bidirectional Forwarding Detection (BFD) [RFC5880] is the protocol of choice for proactive Continuity Check and Connectivity Verification [RFC6428].

2.1.1.1. Proactive CC/CV in BIER

. Bit-Indexed Explicit Replication (BIER) provides the multicast service. For that BFD over multipoint network [I-D.ietf-bfd-multipoint] and [I-D.ietf-bfd-multipoint-active-tail] are the most suitable of BFD family Figure 1 presents IP/UDP format of BFD over BIER in MPLS network.

    
 0                   1                   2                   3
 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|                   Label Stack Element                         |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|                   Label Stack Element                         |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|              BIER-MPLS label          |     |1|               |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|0 1 0 1|  Ver  |  Len  |              Entropy                  |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|                BitString  (first 32 bits)                     ~
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
~                                                               ~
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
~                BitString  (last 32 bits)                      |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|OAM|     Reserved      | Proto |            BFIR-id            |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
~                       IP Header                               ~
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|        Source Port            |   Destination Port (3784)     |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|             Length            |           Checksum            |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
~                  BFD control packet                           ~
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+

    
 0                   1                   2                   3
 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|                   Label Stack Element                         |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|                   Label Stack Element                         |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|              BIER-MPLS label          |     |1|               |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|0 1 0 1|  Ver  |  Len  |              Entropy                  |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|                BitString  (first 32 bits)                     ~
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
~                                                               ~
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
~                BitString  (last 32 bits)                      |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|OAM|     Reserved    | Proto |             BFIR-id             |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Ver | Message Type  | Proto |          Reserved               |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
~                  BFD control packet                           ~
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+