Service Redundancy using BFD
draft-adubey-bfd-service-redundancy-03

Document Type Active Internet-Draft (individual)
Last updated 2020-01-24
Stream (None)
Intended RFC status (None)
Formats plain text pdf htmlized (tools) htmlized 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)
BFD Workgroup                                            S. Boutros, Ed.
Internet-Draft                                                     Ciena
Intended status: Standards Track                                A. Dubey
Expires: July 27, 2020                                            VMware
                                                               R. Rahman
                                                                   Cisco
                                                        January 24, 2020

                      Service Redundancy using BFD
                 draft-adubey-bfd-service-redundancy-03

Abstract

   In a data center, when multiple routing/service nodes are providing
   single active redundancy for a set of L2, L3 and/or L4-L7 services.
   Both non-revertive and revertive fail over modes are required for the
   services.  This draft describes a method to achieve the non-revertive
   and revertive fail over modes for services using Bidirectional
   Forwarding Detection (BFD).

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 27, 2020.

Copyright Notice

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

Boutros, et al.           Expires July 27, 2020                 [Page 1]
Internet-Draft        Service Redundancy using BFD          January 2020

   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
     1.1.  Terminology . . . . . . . . . . . . . . . . . . . . . . .   3
   2.  Solution Overview . . . . . . . . . . . . . . . . . . . . . .   3
     2.1.  Node failover . . . . . . . . . . . . . . . . . . . . . .   3
     2.2.  Per service failover for non-revertive services . . . . .   4
   3.  Security Considerations . . . . . . . . . . . . . . . . . . .   5
   4.  IANA Considerations . . . . . . . . . . . . . . . . . . . . .   5
   5.  Acknowledgments . . . . . . . . . . . . . . . . . . . . . . .   5
   6.  References  . . . . . . . . . . . . . . . . . . . . . . . . .   5
     6.1.  Normative References  . . . . . . . . . . . . . . . . . .   5
     6.2.  Informative References  . . . . . . . . . . . . . . . . .   6
   Authors' Addresses  . . . . . . . . . . . . . . . . . . . . . . .   6

1.  Introduction

   This document describes how can a group of service/routing nodes in a
   data center providing single active redundancy for multiple L2/L3
   and/or L4/L7 services, can use BFD protocol to support non-revertive
   as well as revertive fail over mode.

   Typically, BFD is used between the group of service nodes to verify
   the connectivity as well as the aliveness of the service nodes.  The
   assignment of which node in the group is the primary designated
   forwarder for a given service can be determined using a centralized
   or distributed control plane.

   The use of BFD will be to communicate the set of services that are
   being currently active on a given service node to the other service
   nodes.  On a given node failure, for a given service the backup node
   will take over.  If the service was configured to have a non-
   revertive fail over mode, then the backup node should continue to
   perform the service forwarding even after the primary node recovers
   and comes back up.  In order to do that, the backup node MUST inform
   the primary node that it is currently active for the service.  This
   is achieved through the extension we are proposing to the BFD
   protocol as will be described in the following sections.

   It is to be noted that for revertive fail over mode of operation, the
   primary node should be able to take over the active role from the
   backup node when the primary node goes back to an operational state.

Boutros, et al.           Expires July 27, 2020                 [Page 2]
Show full document text