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

Document Type Active Internet-Draft (individual)
Last updated 2019-07-02
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                                              Sami Boutros
Intended Status: Standard Track                              Ankur Dubey
                                                                  VMware

                                                           Reshad Rahman
                                                                   Cisco

Expires: January 2, 2020                                    July 1, 2019

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

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 to IETF in full conformance with the
   provisions of BCP 78 and BCP 79.

   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

Copyright and License Notice

   Copyright (c) 2019 IETF Trust and the persons identified as the
 

Dubey-Boutros           Expires January 2, 2020                 [Page 1]
INTERNET DRAFT        Service Redundancy using BFD          July 1, 2019

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

 

Dubey-Boutros           Expires January 2, 2020                 [Page 2]
INTERNET DRAFT        Service Redundancy using BFD          July 1, 2019

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
Show full document text