BIER Source Protection
draft-zhang-bier-source-protection-01

Document Type Active Internet-Draft (individual)
Last updated 2020-07-13
Stream (None)
Intended RFC status (None)
Formats plain text xml pdf htmlized (tools) 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)
BIER WG                                                         Z. Zhang
Internet-Draft                                                 G. Mirsky
Intended status: Informational                                  Q. Xiong
Expires: January 14, 2021                                ZTE Corporation
                                                                  Y. Liu
                                                            China Mobile
                                                           July 13, 2020

                         BIER Source Protection
                 draft-zhang-bier-source-protection-01

Abstract

   This document describes the multicast source protection functions in
   Bit Index Explicit Replication BIER domain.

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 January 14, 2021.

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.

Zhang, et al.           Expires January 14, 2021                [Page 1]
Internet-Draft           BIER Source Protection                July 2020

Table of Contents

   1.  Introduction  . . . . . . . . . . . . . . . . . . . . . . . .   2
   2.  The Source Protection analysis  . . . . . . . . . . . . . . .   3
     2.1.  Node failure monitoring . . . . . . . . . . . . . . . . .   4
     2.2.  Monitoring of the Working Path for a Failure  . . . . . .   4
   3.  BFD and Ping  . . . . . . . . . . . . . . . . . . . . . . . .   6
     3.1.  BIER Ping . . . . . . . . . . . . . . . . . . . . . . . .   6
     3.2.  BIER BFD  . . . . . . . . . . . . . . . . . . . . . . . .   7
   4.  Security Considerations . . . . . . . . . . . . . . . . . . .   7
   5.  Informative References  . . . . . . . . . . . . . . . . . . .   7
   Authors' Addresses  . . . . . . . . . . . . . . . . . . . . . . .   9

1.  Introduction

   Bit Index Explicit Replication (BIER) [RFC8279] is an architecture
   that provides multicast forwarding through a "BIER domain" without
   requiring intermediate routers to maintain any multicast related per-
   flow state.  BIER also does not require any explicit tree-building
   protocol for its operation.  A multicast data packet enters a BIER
   domain at a "Bit-Forwarding Ingress Router" (BFIR), and leaves the
   BIER domain at one or more "Bit-Forwarding Egress Routers" (BFERs).

   Source Protection is not specific to the BIER environment.  Source
   Protection means that to protect the multicast source node, two or
   more ingress routers, in BIER environment, ingress routers are BFIRs,
   may be used to connect the multicast source node.  Generally, only
   one ingress router (BFIR) is selected to forward flows from multicast
   source node to egress routers, in BIER environment, egress routers
   are BFERs.  The selected BFIR may be chosen based on local policies,
   BFERs that receiving the same multicast flow may elect to use the
   same or different BFIR.  The BFIR and the path in use are referred to
   as working while all alternative available BFIRs and paths that can
   be used to receive the same multicast flow are referred to as
   protection.

   For a BFER, when either the working BFIR or the working path fails,
   the BFER can select one of protecting BFIRs to get the multicast
   flow.  The shorter the detection time is, the faster the flow
   recovers.

   This document discusses the functions that can be used in failure
   detection for multicast source protection.

Zhang, et al.           Expires January 14, 2021                [Page 2]
Internet-Draft           BIER Source Protection                July 2020

2.  The Source Protection analysis

   According to BIER architecture [RFC8279], BIER overlay protocols,
   which include MVPN [RFC8556], MLD [I-D.ietf-bier-mld], PIM
Show full document text