Overlay OAM Requirements
draft-ooamdt-rtgwg-ooam-requirement-02

Document Type Active Internet-Draft (individual)
Last updated 2017-01-08
Stream (None)
Intended RFC status (None)
Formats plain text xml pdf html 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)
rtgwg                                                           N. Kumar
Internet-Draft                                              C. Pignataro
Intended status: Informational                                  D. Kumar
Expires: July 12, 2017                               Cisco Systems, Inc.
                                                               G. Mirsky
                                                                Ericsson
                                                                 M. Chen
                                                     Huawei Technologies
                                                             E. Nordmark
                                                         Arista Networks
                                                           S. Pallagatti
                                                        Juniper Networks
                                                                D. Mozes
                                               Mellanox Technologies Ltd
                                                         January 8, 2017

                        Overlay OAM Requirements
                 draft-ooamdt-rtgwg-ooam-requirement-02

Abstract

   This document describes a list of functional requirements for
   Operations Administration and Maintenance (OAM) in various Overlay
   and Service networks like Service Function Chaining (SFC), Bit Index
   Explicit Replication (BIER), Network Virtualization over Layer 3
   (NVO3).

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 July 12, 2017.

Kumar, et al.             Expires July 12, 2017                 [Page 1]
Internet-Draft          Overlay OAM Requirements            January 2017

Copyright Notice

   Copyright (c) 2017 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  . . . . . . . . . . . . . . . . . . . . . . . .   2
   2.  Requirements notation . . . . . . . . . . . . . . . . . . . .   3
   3.  Terminology . . . . . . . . . . . . . . . . . . . . . . . . .   3
   4.  Detailed Requirement List . . . . . . . . . . . . . . . . . .   4
     4.1.  Fault Management  . . . . . . . . . . . . . . . . . . . .   5
       4.1.1.  Pro-active Fault Management . . . . . . . . . . . . .   5
       4.1.2.  On-demand Fault Management  . . . . . . . . . . . . .   5
     4.2.  Performance Management  . . . . . . . . . . . . . . . . .   6
     4.3.  Alarm Indication Suppression  . . . . . . . . . . . . . .   7
     4.4.  Overlay Network Resiliency  . . . . . . . . . . . . . . .   7
   5.  IANA Considerations . . . . . . . . . . . . . . . . . . . . .   7
   6.  Security Considerations . . . . . . . . . . . . . . . . . . .   7
   7.  Acknowledgement . . . . . . . . . . . . . . . . . . . . . . .   7
   8.  References  . . . . . . . . . . . . . . . . . . . . . . . . .   7
     8.1.  Normative References  . . . . . . . . . . . . . . . . . .   7
     8.2.  Informative References  . . . . . . . . . . . . . . . . .   9
   Authors' Addresses  . . . . . . . . . . . . . . . . . . . . . . .   9

1.  Introduction

   We have witnessed and participated in design of new paradigms in the
   networking that are aimed to address network virtualization, service
   function chaining, and multicast services.  New paradigms require new
   architectural concepts, principles and components.  [RFC7365] defines
   a framework for Data Center Network Virtualization over Layer 3
   (NVO3).  [RFC7665] describes the architecture for creating and
   maintaining Service Function Chains (SFCs) in a network.
Show full document text