Unaffiliated BFD Echo Function
draft-cw-bfd-unaffiliated-echo-00

Document Type Active Internet-Draft (individual)
Last updated 2020-03-09
Stream (None)
Intended RFC status (None)
Formats plain text pdf 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 Working Group                                               W. Cheng
Internet-Draft                                                   R. Wang
Intended status: Informational                              China Mobile
Expires: September 8, 2020                                        X. Min
                                                                  A. Liu
                                                                     ZTE
                                                           March 7, 2020

                     Unaffiliated BFD Echo Function
                   draft-cw-bfd-unaffiliated-echo-00

Abstract

   Bidirectional Forwarding Detection (BFD) is a fault detection
   protocol that can quickly determine a communication failure between
   devices and notify upper-layer applications [RFC5880].  BFD has
   asynchronous detecting mode and demand detection mode to satisfy
   different scenarios, also supports echo function as an adjunct to
   both modes to reduce the device requirement for BFD.

   Unaffiliated BFD echo function described in this document reuses the
   BFD echo function as described in [RFC5880] and [RFC5881], but
   independent of BFD asynchronous mode or BFD demand mode, that means
   it doesn't need BFD protocol capability of state machine, but only
   BFD echo function to a deployed device supporting BFD detection.
   When using unaffiliated BFD echo function, just the local device
   works on BFD protocol and the BFD peer doesn't, which only loopback
   the received BFD echo packets as usual data packets without enabling
   BFD protocol.

   Section 6.2.2 of [BBF-TR-146] describes one use case of the
   unaffiliated BFD echo function, and at least one more use case is
   known in the field BFD deployment.

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

Cheng, et al.           Expires September 8, 2020               [Page 1]
Internet-Draft       Unaffiliated BFD Echo Function           March 2020

   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 8, 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
   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.  Unaffiliated BFD Echo Behavior  . . . . . . . . . . . . . . .   3
   3.  Discussion  . . . . . . . . . . . . . . . . . . . . . . . . .   4
   4.  Security Considerations . . . . . . . . . . . . . . . . . . .   4
   5.  IANA Considerations . . . . . . . . . . . . . . . . . . . . .   4
   6.  Acknowledgements  . . . . . . . . . . . . . . . . . . . . . .   5
   7.  References  . . . . . . . . . . . . . . . . . . . . . . . . .   5
     7.1.  Normative References  . . . . . . . . . . . . . . . . . .   5
     7.2.  Informative References  . . . . . . . . . . . . . . . . .   5
   Authors' Addresses  . . . . . . . . . . . . . . . . . . . . . . .   5

1.  Introduction

   To minimize the impact of device faults on services and improve
   network availability, a network device must be able to quickly detect
   faults in communication with adjacent devices.  Measures can then be
   taken to promptly rectify the faults to ensure service continuity.

   BFD is a low-overhead, short-duration method to detect faults on the
   path between adjacent forwarding engines.  The faults can be
   interface, data link, and even forwarding engine faults.  It is a
   single, unified mechanism to monitor any media and protocol layers in
   real time.

   BFD has asynchronous detecting mode and demand detection mode to
   satisfy different scenarios, also supports echo function to reduce

Cheng, et al.           Expires September 8, 2020               [Page 2]
Internet-Draft       Unaffiliated BFD Echo Function           March 2020

   the device requirement for BFD.  When the echo function is activated,
Show full document text