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

Document Type Active Internet-Draft (individual)
Last updated 2016-10-30
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                                                         Z. Zhang
Internet-Draft                                           ZTE Corporation
Intended status: Standards Track                           A. Przygienda
Expires: May 3, 2017                                    Juniper Networks
                                                        October 30, 2016

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

Abstract

   BIER introduces a novel architecture for multicast packet forwarding.
   It does not require a signalling 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 ordinary wired as well as in
   wireless mesh networks.  This document defines a way to carry BIER
   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 http://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 3, 2017.

Copyright Notice

   Copyright (c) 2016 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
   (http://trustee.ietf.org/license-info) in effect on the date of
   publication of this document.  Please review these documents

Zhang & Przygienda         Expires May 3, 2017                  [Page 1]
Internet-Draft            BIER Babel extensions             October 2016

   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 . . . . . . . . . . . . . .   3
     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 . . . . . . . . . . .   3
     3.3.  Optional BIER sub-domain BSL conversion sub-sub-TLV . . .   4
   4.  Security Considerations . . . . . . . . . . . . . . . . . . .   4
   5.  Acknowledgements  . . . . . . . . . . . . . . . . . . . . . .   4
   6.  Normative References  . . . . . . . . . . . . . . . . . . . .   5
   Authors' Addresses  . . . . . . . . . . . . . . . . . . . . . . .   5

1.  Introduction

   [I-D.ietf-bier-architecture] introduces a novel architecture for
   multicast data packets forwarding.  It does not require a signalling
   protocol to explicitly build multicast distribution trees, nor does
   it require intermediate nodes to maintain any per-flow state.  All
   the necessary extensions to perform this functionality are
   abbreviated by the "BIER architecture" moniker.

   BIER information can be carried in OSPF and ISIS routing protocol as
   defined in [I-D.ietf-bier-isis-extensions] and
   [I-D.ietf-bier-ospf-bier-extensions] respectively.  The according
   tables for BIER forwarding purposes are built when OSPF/ISIS performs
   according calculations on the advertised information.

   [RFC6126] and [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
   [I-D.ietf-bier-architecture], [RFC6126], [RFC7557] and
   [I-D.ietf-babel-rfc6126bis].

Zhang & Przygienda         Expires May 3, 2017                  [Page 2]
Internet-Draft            BIER Babel extensions             October 2016

3.  Advertisement of BIER information

3.1.  BIER BFR-prefix and BIER sub-TLV
Show full document text