Fault Management for EVPN networks
draft-gmsm-bess-evpn-bfd-01

Document Type Active Internet-Draft (individual)
Last updated 2018-05-27
Stream (None)
Intended RFC status (None)
Formats plain text 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)
INTERNET-DRAFT                                               V. Govindan
Intended status: Proposed Standard                          M. Mudigonda
                                                              A. Sajassi
                                                           Cisco Systems
                                                               G. Mirsky
                                                                     ZTE
                                                             D. Eastlake
                                                                  Huawei
Expires: November 24, 2018                                  May 25, 2018

                   Fault Management for EVPN networks
                      draft-gmsm-bess-evpn-bfd-01

Abstract

   This document specifies a proactive, in-band network OAM mechanism to
   detect loss of continuity and miss-connection faults that affect
   unicast and multi-destination paths, used by Broadcast, unknown
   Unicast and Multicast traffic, in an EVPN network.  The mechanisms
   proposed in the draft use the widely adopted Bidirectional Forwarding
   Detection (BFD) protocol.

Status of this Memo

   This Internet-Draft is submitted to IETF in full conformance with the
   provisions of BCP 78 and BCP 79.

   Distribution of this document is unlimited. Comments should be sent
   to the authors or the BESSq working group mailing list:
   bess@ietf.org.

   Internet-Drafts are working documents of the Internet Engineering
   Task Force (IETF), its areas, and its working groups.  Note that
   other groups may also distribute working documents as Internet-
   Drafts.

   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."

   The list of current Internet-Drafts can be accessed at
   http://www.ietf.org/1id-abstracts.html. The list of Internet-Draft
   Shadow Directories can be accessed at
   http://www.ietf.org/shadow.html.

Govindan, et al                                                 [Page 1]
Internet-Draft                                 Fault Management for EVPN

Table of Contents

      1. Introduction............................................3
      1.1 Terminology............................................3

      2. Scope of this Document..................................4
      3. Motivation for Running BFD at the EVPN Network Layer....4

      4. Fault Detection of Unicast Traffic......................6

      5. Fault Detection for BUM Traffic.........................7
      5.1 Ingress Replication....................................7
      5.2 Label Switched Multicast...............................7

      6. BFD Packet Encapsulation................................8
      6.1 Using GAL/G-ACh Encapsulation Without IP Headers.......8
      6.1.1 Ingress Replication..................................8
      6.1.1.1 Alternative Encapsulation Format...................8
      6.1.2 LSM (Label Switched Multicast).......................9
      6.1.3 Unicast..............................................9
      6.1.3.1 Alternative Encapsulation Format...................9
      6.2 Using IP Headers......................................10

      7. Scalability Considerations.............................11
      8. IANA Considerations....................................12
      9. Security Considerations................................13

      Normative References......................................14
      Informative References....................................15

      Authors' Addresses........................................17

Govindan, et al                                                 [Page 2]
Internet-Draft                                 Fault Management for EVPN

1. Introduction

   [I-D.eastlake-bess-evpn-oam-req-frmwk] and [I-D.ooamdt-rtgwg-ooam-
   requirement] outline the OAM requirements of Ethernet VPN networks
   [RFC7432].  This document proposes mechanisms for proactive fault
   detection at the network (overlay) OAM layer of EVPN.  EVPN fault
   detection mechanisms need to consider unicast traffic separately from
   Broadcast, unknown Unicast, and Multicsst (BUM) traffic since they
   map to different FECs in EVPN, hence this document proposes different
   fault detection mechanisms to suit each type using the principles of
   [RFC5880], [RFC5884] and Point-to-multipoint BFD [I-D.ietf-bfd-
   multipoint] and [I-D.ietf-bfd-multipoint-active-tail]. Packet loss
   and packet delay measurement are out of scope for this document.

1.1 Terminology

   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 BCP
   14 [RFC2119] [RFC8174] when, and only when, they appear in all
Show full document text