Multicast Redundant Ingress Router Failover
draft-szcl-mboned-redundant-ingress-failover-00

Document Type Active Internet-Draft (individual)
Authors Greg Shepherd  , Zheng Zhang  , Yisong Liu  , Ying Cheng 
Last updated 2020-10-25
Stream (None)
Intended RFC status (None)
Formats plain text 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)
MBONED WG                                                    G. Shepherd
Internet-Draft                                       Cisco Systems, Inc.
Intended status: Informational                             Z. Zhang, Ed.
Expires: April 28, 2021                                  ZTE Corporation
                                                                  Y. Liu
                                                            China Mobile
                                                                Y. Cheng
                                                            China Unicom
                                                        October 25, 2020

              Multicast Redundant Ingress Router Failover
            draft-szcl-mboned-redundant-ingress-failover-00

Abstract

   This document discusses the redundant ingress router failover in
   multicast 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 April 28, 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

Shepherd, et al.         Expires April 28, 2021                 [Page 1]
Internet-Draft Multicast Redundant Ingress Router Failover  October 2020

   the Trust Legal Provisions and are provided without warranty as
   described in the Simplified BSD License.

Table of Contents

   1.  Introduction  . . . . . . . . . . . . . . . . . . . . . . . .   2
   2.  Terminology . . . . . . . . . . . . . . . . . . . . . . . . .   3
   3.  Multicast Redundant Ingress Router Failover . . . . . . . . .   3
     3.1.  Swichover . . . . . . . . . . . . . . . . . . . . . . . .   4
   4.  Stand-by Modes  . . . . . . . . . . . . . . . . . . . . . . .   6
     4.1.  Cold  . . . . . . . . . . . . . . . . . . . . . . . . . .   6
     4.2.  Warm  . . . . . . . . . . . . . . . . . . . . . . . . . .   7
     4.3.  Hot . . . . . . . . . . . . . . . . . . . . . . . . . . .   7
     4.4.  Summary . . . . . . . . . . . . . . . . . . . . . . . . .   8
   5.  Security Considerations . . . . . . . . . . . . . . . . . . .  10
   6.  References  . . . . . . . . . . . . . . . . . . . . . . . . .  10
     6.1.  Normative References  . . . . . . . . . . . . . . . . . .  10
     6.2.  Informative References  . . . . . . . . . . . . . . . . .  10
   Authors' Addresses  . . . . . . . . . . . . . . . . . . . . . . .  11

1.  Introduction

   The multicast redundant ingress router failover is an important issue
   in multicast deployment.  This document tries to do a research on it
   in the multicast domain.  The Multicast Domain is a domain which is
   used to forward multicast flow according to specific multicast
   technologies, such as PIM ([RFC7761]), BIER ([RFC8279]), P2MP TE
   tunnel ([RFC4875]), MLDP ([RFC6388]), etc.  This domain may or may
   not connect the multicast source and receiver directly.

   The ingress router is close to the multicast source.  The ingress
   router may connect the multicast source directly, or there may be
   multiple hops between the ingress router and the multicast source.
   In the multicast domain, the ingress router is the most adjacent
   router to the multicast source.  It's also called the first-hop
   router in PIM, or BFIR in BIER, or Ingress LSR in P2MP TE tunnel or
   MLDP.

   The failover function between the multicast source and the ingress
   router can be achieved by many ways, and it is not included in this
   document.

   The egress router is close to the multicast receiver.  The egress
   router may connect the multicast receiver directly, or there may be
   multiple hops between the egress router and the multicast receiver.
   In the multicast domain, the egress router is the most adjacent
   router to the multicast receiver.  It's also called the last-hop

Shepherd, et al.         Expires April 28, 2021                 [Page 2]
Internet-Draft Multicast Redundant Ingress Router Failover  October 2020
Show full document text