Bidirectional Forwarding Detection (BFD) for Multi-point Networks and Protocol Independent Multicast - Sparse Mode (PIM-SM) Use Case
draft-ietf-pim-bfd-p2mp-use-case-00

Document Type Active Internet-Draft (pim WG)
Last updated 2018-11-05
Replaces draft-mirsky-pim-bfd-p2mp-use-case
Stream IETF
Intended RFC status (None)
Formats plain text xml pdf html bibtex
Stream WG state WG Document
Document shepherd No shepherd assigned
IESG IESG state I-D Exists
Consensus Boilerplate Unknown
Telechat date
Responsible AD (None)
Send notices to (None)
PIM Working Group                                              G. Mirsky
Internet-Draft                                                 ZTE Corp.
Updates: 7761 (if approved)                                    J. Xiaoli
Intended status: Standards Track                         ZTE Corporation
Expires: April 25, 2019                                 October 22, 2018

 Bidirectional Forwarding Detection (BFD) for Multi-point Networks and
     Protocol Independent Multicast - Sparse Mode (PIM-SM) Use Case
                  draft-ietf-pim-bfd-p2mp-use-case-00

Abstract

   This document discusses the use of Bidirectional Forwarding Detection
   (BFD) for multi-point networks to provide nodes that participate in
   Protocol Independent Multicast - Sparse Mode (PIM-SM) with the sub-
   second convergence.  Optional extension to PIM-SM Hello, as specified
   in RFC 7761, to bootstrap point-to-multipoint BFD session. also
   defined in this document.

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 April 25, 2019.

Copyright Notice

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

Mirsky & Xiaoli          Expires April 25, 2019                 [Page 1]
Internet-Draft           BFD P2MP Use in PIM-SM             October 2018

   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.  Conventions used in this document . . . . . . . . . . . .   3
       1.1.1.  Terminology . . . . . . . . . . . . . . . . . . . . .   3
       1.1.2.  Requirements Language . . . . . . . . . . . . . . . .   3
   2.  Problem Statement . . . . . . . . . . . . . . . . . . . . . .   3
   3.  Applicability of p2mp BFD . . . . . . . . . . . . . . . . . .   3
     3.1.  Multipoint BFD Encapsulation  . . . . . . . . . . . . . .   4
   4.  IANA Considerations . . . . . . . . . . . . . . . . . . . . .   5
   5.  Security Considerations . . . . . . . . . . . . . . . . . . .   5
   6.  Acknowledgments . . . . . . . . . . . . . . . . . . . . . . .   5
   7.  Normative References  . . . . . . . . . . . . . . . . . . . .   5
   Authors' Addresses  . . . . . . . . . . . . . . . . . . . . . . .   6

1.  Introduction

   Faster convergence in the control plane, in general, is beneficial
   and allows minimizing periods of traffic blackholing, transient
   routing loops and other scenarios that may negatively affect service
   data flow.  That equally applies to unicast and multicast routing
   protocols.

   [RFC7761] is the current specification of the Protocol Independent
   Multicast - Sparse Mode (PIM-SM) for IPv4 and IPv6 networks.
   Confirming implementation of PIM-SM elects a Designated Router (DR)
   on each PIM-SM interface.  When a group of PIM-SM nodes is connected
   to shared-media segment, e.g.  Ethernet, the one elected as DR is to
   act on behalf of directly connected hosts in context of the PIM-SM
   protocol.  Failure of the DR impacts the quality of the multicast
   services it provides to directly connected hosts because the default
   failure detection interval for PIM-SM routers is 105 seconds.
   Introduction of Backup DR (BDR), proposed in
   [I-D.ietf-pim-dr-improvement] improves convergence time in the PIM-SM
   over shared-media segment but still depends on long failure detection
   interval.

   Bidirectional Forwarding Detection (BFD) [RFC5880] had been
   originally defined to detect failure of point-to-point (p2p) paths -
   single-hop [RFC5881], multihop [RFC5883].  [I-D.ietf-bfd-multipoint]
   extends the BFD base specification [RFC5880] for multipoint and
   multicast networks, which precisely characterizes deployment
   scenarios for PIM-SM over LAN segment.  This document demonstrates
   how point-to-multipoint (p2mp) BFD can enable faster detection of
Show full document text