BIER Fast ReRoute
draft-chen-bier-frr-00

Document Type Active Internet-Draft (individual)
Authors Huaimo Chen  , Aijun Wang  , Gyan Mishra  , Yanhe Fan  , Lei Liu  , Xufeng Liu 
Last updated 2020-11-02
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)
Network Working Group                                            H. Chen
Internet-Draft                                                 Futurewei
Intended status: Standards Track                                 A. Wang
Expires: May 6, 2021                                       China Telecom
                                                               G. Mishra
                                                            Verizon Inc.
                                                                  Y. Fan
                                                            Casa Systems
                                                                  L. Liu
                                                                 Fujitsu
                                                                  X. Liu
                                                          Volta Networks
                                                        November 2, 2020

                           BIER Fast ReRoute
                         draft-chen-bier-frr-00

Abstract

   This document describes a mechanism for fast re-route (FRR)
   protection against the failure of a node or link in the core of a
   "Bit Index Explicit Replication" (BIER) domain.  It does not have any
   per-flow state in the core.  For a multicast packet to traverse a
   node in the domain, when the node fails, its upstream hop as a PLR
   reroutes the packet around the failed node once it detects the
   failure.

Requirements Language

   The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
   "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this
   document are to be interpreted as described in [RFC2119] [RFC8174]
   when, and only when, they appear in all capitals, as shown here.

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

Chen, et al.               Expires May 6, 2021                  [Page 1]
Internet-Draft                  BIER FRR                   November 2020

   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 May 6, 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.

Table of Contents

   1.  Introduction  . . . . . . . . . . . . . . . . . . . . . . . .   2
     1.1.  Terminology . . . . . . . . . . . . . . . . . . . . . . .   3
   2.  BIER FRR Solution . . . . . . . . . . . . . . . . . . . . . .   4
     2.1.  Overview of BIER forwarding . . . . . . . . . . . . . . .   4
     2.2.  FRR Bit Index Routing Tables  . . . . . . . . . . . . . .   5
     2.3.  FRR Bit Index Forwarding Tables . . . . . . . . . . . . .   6
     2.4.  Updated Forwarding Procedure  . . . . . . . . . . . . . .   7
     2.5.  Switching between FRR and Normal Forwarding . . . . . . .   7
   3.  Example Application of BIER FRR . . . . . . . . . . . . . . .   8
     3.1.  Example BIER Topology . . . . . . . . . . . . . . . . . .   8
     3.2.  BIRT and BIFT on a BFR  . . . . . . . . . . . . . . . . .   8
     3.3.  FRR-BIRTs and FRR-BIFTs on a BFR  . . . . . . . . . . . .  10
     3.4.  Forwarding using FRR-BIFT . . . . . . . . . . . . . . . .  12
   4.  Security Considerations . . . . . . . . . . . . . . . . . . .  13
   5.  IANA Considerations . . . . . . . . . . . . . . . . . . . . .  13
   6.  Acknowledgements  . . . . . . . . . . . . . . . . . . . . . .  13
   7.  References  . . . . . . . . . . . . . . . . . . . . . . . . .  13
     7.1.  Normative References  . . . . . . . . . . . . . . . . . .  13
     7.2.  Informative References  . . . . . . . . . . . . . . . . .  15
   Authors' Addresses  . . . . . . . . . . . . . . . . . . . . . . .  15

1.  Introduction

   [RFC8279] specifies "Bit Index Explicit Replication" (BIER).  It
   provides optimal forwarding of multicast data packets through a
   "multicast/BIER domain".  It does not require the use of a protocol
Show full document text