PIM Signaling Through BIER Core
draft-ietf-bier-pim-signaling-10

Document Type Active Internet-Draft (bier WG)
Authors Hooman Bidgoli  , Fengman Xu  , Jayant Kotalwar  , IJsbrand Wijnands  , Mankamana Mishra  , Zhaohui Zhang 
Last updated 2020-07-29
Stream IETF
Intended RFC status Proposed Standard
Formats plain text xml pdf htmlized (tools) htmlized bibtex
Stream WG state In WG Last Call
Revised I-D Needed - Issue raised by WGLC
Document shepherd Nabeel Cocker
IESG IESG state I-D Exists
Consensus Boilerplate Yes
Telechat date
Responsible AD (None)
Send notices to Nabeel Cocker <nabeel.cocker@gmail.com>
Network Working Group                                    H. Bidgoli, Ed.
Internet-Draft                                                     Nokia
Intended status: Informational                                     F. Xu
Expires: January 30, 2021                                        Verizon
                                                             J. Kotalwar
                                                                   Nokia
                                                             I. Wijnands
                                                               M. Mishra
                                                            Cisco System
                                                                Z. Zhang
                                                        Juniper Networks
                                                           July 29, 2020

                    PIM Signaling Through BIER Core
                    draft-ietf-bier-pim-signaling-10

Abstract

   Consider large networks deploying traditional PIM multicast service.
   Typically, each portion of these large networks have their own
   mandates and requirements.

   It might be desirable to deploy BIER technology in some part of these
   networks to replace traditional PIM services.  In such cases
   downstream PIM states need to be signaled over BIER Domain toward the
   source.

   This draft explains the procedure to signal PIM joins and prunes
   through a BIER Domain, as such enable provisioning of traditional PIM
   services through a 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 30, 2021.

Bidgoli, et al.         Expires January 30, 2021                [Page 1]
Internet-Draft       PIM Signaling Through BIER Core           July 2020

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  . . . . . . . . . . . . . . . . . . . . . . . .   3
   2.  Conventions used in this document . . . . . . . . . . . . . .   3
     2.1.  Definitions . . . . . . . . . . . . . . . . . . . . . . .   3
   3.  PIM Signaling Through BIER domain . . . . . . . . . . . . . .   5
     3.1.  Ingress BBR procedure . . . . . . . . . . . . . . . . . .   5
       3.1.1.  Determining EBBR on IBBR  . . . . . . . . . . . . . .   6
       3.1.2.  Considering ECMP in EBBR selection  . . . . . . . . .   6
       3.1.3.  PIM Signaling packet construction at IBBR . . . . . .   7
         3.1.3.1.  BIER packet construction at IBBR  . . . . . . . .   8
     3.2.  Signaling PIM through the BIER domain procedure . . . . .   8
     3.3.  EBBR procedure  . . . . . . . . . . . . . . . . . . . . .   9
   4.  Datapath Forwarding . . . . . . . . . . . . . . . . . . . . .   9
     4.1.  BFIR tracking of (S,G)  . . . . . . . . . . . . . . . . .   9
     4.2.  Datapath traffic flow . . . . . . . . . . . . . . . . . .   9
   5.  PIM-SM behavior . . . . . . . . . . . . . . . . . . . . . . .   9
   6.  Applicability to MVPN . . . . . . . . . . . . . . . . . . . .  10
   7.  IANA Considerations . . . . . . . . . . . . . . . . . . . . .  11
   8.  Security Considerations . . . . . . . . . . . . . . . . . . .  11
   9.  Acknowledgments . . . . . . . . . . . . . . . . . . . . . . .  11
   10. References  . . . . . . . . . . . . . . . . . . . . . . . . .  11
     10.1.  Normative References . . . . . . . . . . . . . . . . . .  11
     10.2.  Informative References . . . . . . . . . . . . . . . . .  11
   Appendix A. . . . . . . . . . . . . . . . . . . . . . . . . . . .  12
     A.1.  SPF . . . . . . . . . . . . . . . . . . . . . . . . . . .  12
     A.2.  Indirect next-hop . . . . . . . . . . . . . . . . . . . .  12
       A.2.1.  Static Route  . . . . . . . . . . . . . . . . . . . .  12
Show full document text