Seamless Bidirectional Forwarding Detection (S-BFD) Use Cases
draft-ietf-bfd-seamless-use-case-07

The information below is for an old version of the document
Document Type Active Internet-Draft (bfd WG)
Last updated 2016-05-05 (latest revision 2016-05-04)
Replaces draft-aldrin-bfd-seamless-use-case
Stream IETF
Intended RFC status Informational
Formats plain text pdf html bibtex
Stream WG state Submitted to IESG for Publication (wg milestone: Dec 2014 - Submit the BFD Seaml... )
Document shepherd Jeffrey Haas
Shepherd write-up Show (last changed 2015-07-30)
IESG IESG state Approved-announcement to be sent
Consensus Boilerplate Yes
Telechat date
Responsible AD Alvaro Retana
Send notices to aretana@cisco.com
IANA IANA review state IANA OK - No Actions Needed
IANA action state None
Network Working Group                                          S. Aldrin
Internet-Draft                                               Google, Inc
Intended status: Informational                              C. Pignataro
Expires: November 5, 2016                                          Cisco
                                                               G. Mirsky
                                                                Ericsson
                                                                N. Kumar
                                                                   Cisco
                                                             May 4, 2016

     Seamless Bidirectional Forwarding Detection (S-BFD) Use Cases
                  draft-ietf-bfd-seamless-use-case-07

Abstract

   This document describes various use cases for a Seamless
   Bidirectional Forwarding Detection (S-BFD), and provides requirements
   such that protocol mechanisms allow for a simplified detection of
   forwarding failures.

   These use cases support S-BFD, as a simplified mechanism to use
   Bidirectional Forwarding Detection (BFD) with large portions of
   negotiation aspects eliminated, accelerating the establishment of a
   BFD session.  S-BFD benefits include quick provisioning as well as
   improved control and flexibility to network nodes initiating the path
   monitoring.

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 November 5, 2016.

Aldrin, et al.          Expires November 5, 2016                [Page 1]
Internet-Draft               S-BFD Use Cases                    May 2016

Copyright Notice

   Copyright (c) 2016 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
     1.1.  Terminology . . . . . . . . . . . . . . . . . . . . . . .   3
     1.2.  Requirements Language . . . . . . . . . . . . . . . . . .   3
   2.  Introduction to Seamless BFD  . . . . . . . . . . . . . . . .   4
   3.  Use Cases . . . . . . . . . . . . . . . . . . . . . . . . . .   5
     3.1.  Unidirectional Forwarding Path Validation . . . . . . . .   5
     3.2.  Validation of the Forwarding Path Prior to Switching
           Traffic . . . . . . . . . . . . . . . . . . . . . . . . .   6
     3.3.  Centralized Traffic Engineering . . . . . . . . . . . . .   7
     3.4.  BFD in Centralized Segment Routing  . . . . . . . . . . .   8
     3.5.  Efficient BFD Operation under Resource Constraints  . . .   8
     3.6.  BFD for Anycast Addresses . . . . . . . . . . . . . . . .   8
     3.7.  BFD Fault Isolation . . . . . . . . . . . . . . . . . . .   9
     3.8.  Multiple BFD Sessions to the Same Target Node . . . . . .   9
     3.9.  An MPLS BFD Session Per ECMP Path . . . . . . . . . . . .  10
   4.  Detailed Requirements for a Seamless BFD  . . . . . . . . . .  10
   5.  Security Considerations . . . . . . . . . . . . . . . . . . .  12
   6.  IANA Considerations . . . . . . . . . . . . . . . . . . . . .  12
   7.  Acknowledgements  . . . . . . . . . . . . . . . . . . . . . .  12
   8.  Contributors  . . . . . . . . . . . . . . . . . . . . . . . .  12
   9.  References  . . . . . . . . . . . . . . . . . . . . . . . . .  12
     9.1.  Normative References  . . . . . . . . . . . . . . . . . .  12
     9.2.  Informative References  . . . . . . . . . . . . . . . . .  13
   Authors' Addresses  . . . . . . . . . . . . . . . . . . . . . . .  14

1.  Introduction

   Bidirectional Forwarding Detection (BFD) is a lightweight protocol,
   as defined in [RFC5880], used to detect forwarding failures.  Various
   protocols and applications rely on BFD as its clients for failure
   detection.  Even though the protocol is lightweight and simple, there
Show full document text