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

Document Type Active Internet-Draft (individual)
Last updated 2019-07-07
Stream (None)
Intended RFC status (None)
Formats plain text pdf html 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                                                     Zheng. Zhang
Internet-Draft                                              Greg. Mirsky
Intended status: Informational                               Quan. Xiong
Expires: January 8, 2020                                 ZTE Corporation
                                                            July 7, 2019

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

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 8, 2020.

Copyright Notice

   Copyright (c) 2019 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 8, 2020                [Page 1]
Internet-Draft           BIER Source Protection                July 2019

Table of Contents

   1.  Introduction  . . . . . . . . . . . . . . . . . . . . . . . .   2
   2.  Multicast Source Protection . . . . . . . . . . . . . . . . .   2
     2.1.  BIER Ping . . . . . . . . . . . . . . . . . . . . . . . .   3
     2.2.  BIER BFD  . . . . . . . . . . . . . . . . . . . . . . . .   4
   3.  Security Considerations . . . . . . . . . . . . . . . . . . .   4
   4.  Normative References  . . . . . . . . . . . . . . . . . . . .   4
   Authors' Addresses  . . . . . . . . . . . . . . . . . . . . . . .   5

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).

   To protect the source node it may be transmitting to two or more
   BFIRs.  Based on local policies, BFERs may elect to use the same BFIR
   or different BFIRs as the source of the multicast flow.  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 fail, the BFER can select
   one of protection 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.

2.  Multicast Source Protection

   Two BFIRs independently advertise the source of the multicast flow to
   BFERs.  The precise type of advertisement depends on the overlay
   protocol being used, e.g., MLD, MVPN, EVPN.  BFER selects one BFIR as
   the UMH (Upstream Multicast Hop).  Different BFERs may select the
   same BFIR or different BFIRs according to the local policy.

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

                            +--------+S1+-------+
                            |                   |
                         +--v----+          +---v---+
                  +------+ BFIR1 |          | BFIR2 +-------+
                  |      +-------+          +-------+       |
                  |                                         |
                  |                                         |
                  |                                         |
                  | +-------+      +-------+      +-------+ |
Show full document text