Traffic Enginering for Bit Index Explicit Replication BIER-TE
draft-eckert-bier-te-arch-02

The information below is for an old version of the document
Document Type Active Internet-Draft (individual)
Last updated 2015-10-18
Replaced by draft-ietf-bier-te-arch
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)
Network Working Group                                          T. Eckert
Internet-Draft                                       Cisco Systems, Inc.
Intended status: Standards Track                              G. Cauchie
Expires: April 20, 2016                                 Bouygues Telecom
                                                        October 18, 2015

     Traffic Enginering for Bit Index Explicit Replication BIER-TE
                      draft-eckert-bier-te-arch-02

Abstract

   This document proposes an architecture for BIER-TE: Traffic
   Engineering for Bit Index Explicit Replication (BIER).

   BIER-TE shares part of its architecture with BIER as described in
   [I-D.ietf-bier-architecture].  It also proposes to share the packet
   format with BIER.

   BIER-TE forwards and replicates packets like BIER based on a
   BitString in the packet header but it does not require an IGP.  It
   does support traffic engineering by explicit hop-by-hop forwarding
   and loose hop forwarding of packets.  It does support Fast ReRoute
   (FRR) for link and node protection and incremental deployment.
   Because BIER-TE like BIER operates without explicit in-network tree-
   building but also supports traffic engineering, it is more similar to
   SR than RSVP-TE.

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 April 20, 2016.

Eckert & Cauchie         Expires April 20, 2016                 [Page 1]
Internet-Draft                BIER-TE ARCH                  October 2015

Copyright Notice

   Copyright (c) 2015 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
   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
     1.1.  Overview  . . . . . . . . . . . . . . . . . . . . . . . .   3
     1.2.  Requirements Language . . . . . . . . . . . . . . . . . .   4
   2.  Layering  . . . . . . . . . . . . . . . . . . . . . . . . . .   4
     2.1.  The Multicast Flow Overlay  . . . . . . . . . . . . . . .   5
     2.2.  The BIER-TE Controller Host . . . . . . . . . . . . . . .   5
       2.2.1.  Assignment of BitPositions to adjacencies of the
               network topology  . . . . . . . . . . . . . . . . . .   6
       2.2.2.  Changes in the network topology . . . . . . . . . . .   6
       2.2.3.  Set up per-multicast flow BIER-TE state . . . . . . .   6
       2.2.4.  Link/Node Failures and Recovery . . . . . . . . . . .   6
     2.3.  The BIER-TE Forwarding Layer  . . . . . . . . . . . . . .   7
     2.4.  The Routing Underlay  . . . . . . . . . . . . . . . . . .   7
   3.  BIER-TE Forwarding  . . . . . . . . . . . . . . . . . . . . .   7
     3.1.  The Bit Index Forwarding Table (BIFT) . . . . . . . . . .   7
     3.2.  Adjacency Types . . . . . . . . . . . . . . . . . . . . .   8
       3.2.1.  Forward Connected . . . . . . . . . . . . . . . . . .   8
       3.2.2.  Forward Routed  . . . . . . . . . . . . . . . . . . .   9
       3.2.3.  ECMP  . . . . . . . . . . . . . . . . . . . . . . . .   9
       3.2.4.  Local Decap . . . . . . . . . . . . . . . . . . . . .   9
     3.3.  Encapsulation considerations  . . . . . . . . . . . . . .  10
     3.4.  Basic BIER-TE Forwarding Example  . . . . . . . . . . . .  10
   4.  BIER-TE Controller Host BitPosition Assignments . . . . . . .  12
     4.1.  P2P Links . . . . . . . . . . . . . . . . . . . . . . . .  12
     4.2.  BFER  . . . . . . . . . . . . . . . . . . . . . . . . . .  13
     4.3.  Leaf BFERs  . . . . . . . . . . . . . . . . . . . . . . .  13
     4.4.  LANs  . . . . . . . . . . . . . . . . . . . . . . . . . .  13
     4.5.  Hub and Spoke . . . . . . . . . . . . . . . . . . . . . .  14
     4.6.  Rings . . . . . . . . . . . . . . . . . . . . . . . . . .  14
     4.7.  Equal Cost MultiPath (ECMP) . . . . . . . . . . . . . . .  15
Show full document text