Seamless Bidirectional Forwarding Detection (BFD) Use Case
draft-ietf-bfd-seamless-use-case-00

The information below is for an old version of the document
Document Type Active Internet-Draft (bfd WG)
Last updated 2014-06-11
Replaces draft-aldrin-bfd-seamless-use-case
Stream IETF
Intended RFC status (None)
Formats plain text pdf html bibtex
Stream WG state WG Document (wg milestone: Dec 2014 - Submit the BFD Seaml... )
Document shepherd No shepherd assigned
IESG IESG state I-D Exists
Consensus Boilerplate Unknown
Telechat date
Responsible AD (None)
Send notices to (None)
INTERNET-DRAFT                                                Sam Aldrin
Intended Status: Informational                                  (Huawei)
Expires: December 13, 2014                                  Manav Bhatia
                                                                 (Ionos)
                                                             Greg Mirsky
                                                              (Ericsson)
                                                          Nagendra Kumar
                                                                 (Cisco)
                                                       Satoru Matsushima
                                                              (Softbank)

                                                           June 11, 2014

      Seamless Bidirectional Forwarding Detection (BFD) Use Case 
                  draft-ietf-bfd-seamless-use-case-00

Abstract

   This document provides various use cases for Bidirectional Forwarding
   Detection (BFD) such that simplified solution and extensions could be
   developed for detecting forwarding failures.

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
 

<Aldrin et al>         Expires December 13, 2014                [Page 1]
INTERNET DRAFT          <Seamless BFD Use Case>            June 11, 2014

   Copyright (c) 2014 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  . . . . . . . . . . . . . . . . . . . . . . . . .  3
     1.1. Terminology . . . . . . . . . . . . . . . . . . . . . . . .  3
   2. Introduction to Seamless BFD  . . . . . . . . . . . . . . . . .  3
   3. Use Cases . . . . . . . . . . . . . . . . . . . . . . . . . . .  4
     3.1. Unidirectional Forwarding Path Validation . . . . . . . . .  4
     3.2. Validation of forwarding path prior to traffic switching  .  5
     3.3. Centralized Traffic Engineering . . . . . . . . . . . . . .  5
     3.4. BFD in Centralized Segment Routing  . . . . . . . . . . . .  6
     3.5. BFD to Efficiently Operate under Resource Constraints . . .  6
     3.6. BFD for Anycast Address . . . . . . . . . . . . . . . . . .  7
     3.7. BFD Fault Isolation . . . . . . . . . . . . . . . . . . . .  7
     3.8. Multiple BFD Sessions to Same Target  . . . . . . . . . . .  7
     3.9. MPLS BFD Session Per ECMP Path  . . . . . . . . . . . . . .  8
   4. Security Considerations . . . . . . . . . . . . . . . . . . . .  9
   5. IANA Considerations . . . . . . . . . . . . . . . . . . . . . .  9
   6. References  . . . . . . . . . . . . . . . . . . . . . . . . . .  9
     6.1. Normative References  . . . . . . . . . . . . . . . . . . .  9
   7. Authors' Addresses  . . . . . . . . . . . . . . . . . . . . . .  9
   8. Contributors  . . . . . . . . . . . . . . . . . . . . . . . . . 10

 

<Aldrin et al>         Expires December 13, 2014                [Page 2]
INTERNET DRAFT          <Seamless BFD Use Case>            June 11, 2014

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 for failure detection. Even
   though the protocol is simple and lightweight, there are certain use
   cases, where a much faster setting up of sessions and continuity
   check of the data forwarding paths is necessary. This document
   identifies those use cases such that necessary enhancements could be
Show full document text