BIER in BABEL
draft-zhang-bier-babel-extensions-02

Document Type Active Internet-Draft (individual)
Last updated 2019-11-03
Stream (None)
Intended RFC status (None)
Formats plain text pdf htmlized bibtex
Stream Stream state (No stream defined)
Consensus Boilerplate Unknown
On Agenda babel at IETF-106
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                                           ZTE Corporation
Intended status: Standards Track                           A. Przygienda
Expires: May 6, 2020                                    Juniper Networks
                                                        November 3, 2019

                             BIER in BABEL
                  draft-zhang-bier-babel-extensions-02

Abstract

   BIER introduces a novel multicast architecture.  It does not require
   a signaling protocol to explicitly build multicast distribution
   trees, nor does it require intermediate nodes to maintain any per-
   flow state.

   Babel defines a distance-vector routing protocol that operates in a
   robust and efficient fashion both in wired as well as in wireless
   mesh networks.  This document defines a way to carry necessary BIER
   signaling information in Babel.

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

Zhang & Przygienda         Expires May 6, 2020                  [Page 1]
Internet-Draft            BIER Babel extensions            November 2019

   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
   2.  Terminology . . . . . . . . . . . . . . . . . . . . . . . . .   2
   3.  Advertisement of BIER information . . . . . . . . . . . . . .   2
     3.1.  BIER BFR-prefix and BIER sub-TLV  . . . . . . . . . . . .   3
       3.1.1.  BIER sub-TLV  . . . . . . . . . . . . . . . . . . . .   3
     3.2.  BIER MPLS Encapsulation sub-sub-TLV . . . . . . . . . . .   4
   4.  Tree types and tunneling  . . . . . . . . . . . . . . . . . .   4
   5.  Security Considerations . . . . . . . . . . . . . . . . . . .   5
   6.  IANA Considerations . . . . . . . . . . . . . . . . . . . . .   5
   7.  Normative References  . . . . . . . . . . . . . . . . . . . .   5
   Authors' Addresses  . . . . . . . . . . . . . . . . . . . . . . .   6

1.  Introduction

   [RFC8279] introduces a novel multicast architecture.  It does not
   require a signaling protocol to explicitly build multicast
   distribution trees, nor does it require intermediate nodes to
   maintain any per-flow state.  All procedures necessary to support
   BIER are abbreviated by the "BIER architecture" moniker in this
   document.

   [I-D.ietf-babel-rfc6126bis] define a distance-vector routing protocol
   under the name of "Babel".  Babel operates in a robust and efficient
   fashion both in ordinary wired as well as in wireless mesh networks.

2.  Terminology

   The terminology of this documents follows [RFC8279], [RFC6126],
   [RFC7557] and [I-D.ietf-babel-rfc6126bis].

3.  Advertisement of BIER information

   In case a router is configured with BIER information, and Babel is
   the routing protocol used, such a router MAY use Babel protocol to
   announce the BIER information using the BIER sub-TLV specified below.

Zhang & Przygienda         Expires May 6, 2020                  [Page 2]
Internet-Draft            BIER Babel extensions            November 2019

3.1.  BIER BFR-prefix and BIER sub-TLV

   BFR-prefix and according information is carried in a Babel Update TLV
   per [I-D.ietf-babel-rfc6126bis].  A new sub-TLV is defined to convey
   further BIER information such as BFR-id, sub-domain-id and BSL.  Two
   sub-sub-TLVs are carried as payload of BIER sub-TLV.

   The mandatory bit of BIER sub-TLV should be set to 0.  If a router
   cannot recognize a sub-TLV, the router MUST ignore this unknown sub-
   TLV.

3.1.1.  BIER sub-TLV

   The BIER sub-TLV format aligns exactly with the definition and
Show full document text