BIER IPv6 Requirements
draft-mcbride-bier-ipv6-requirements-00

Document Type Active Internet-Draft (individual)
Last updated 2019-04-01
Replaces draft-mcbride-bier-ipv6-problem-statement
Stream (None)
Intended RFC status (None)
Formats plain text xml 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                                                          M. McBride
Internet-Draft                                                    J. Xie
Intended status: Standards Track                             S. Dhanaraj
Expires: October 3, 2019                                          Huawei
                                                                R. Asati
                                                                   Cisco
                                                           April 1, 2019

                         BIER IPv6 Requirements
                draft-mcbride-bier-ipv6-requirements-00

Abstract

   The BIER WG has a charter item to work on mechanisms which use BIER
   natively in IPv6.  This document is intended to help the WG with this
   effort by describing the problem space of transporting packets, with
   Bit Index Explicit Replication (BIER) headers, in an IPv6
   environment.  There will be a need to send IPv6 payloads, to multiple
   IPv6 destinations, using BIER.  There have been several proposed
   solutions in this area.  But there hasn't been a document which
   describes the problem and why this may be necessary.  The goal of
   this document is to describe the BIER IPv6 problem space, basic use
   cases, why new solutions may be needed and briefly summarize some of
   the proposed solutions.

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 October 3, 2019.

Copyright Notice

   Copyright (c) 2019 IETF Trust and the persons identified as the
   document authors.  All rights reserved.

McBride, et al.          Expires October 3, 2019                [Page 1]
Internet-Draft           BIER IPv6 Requirements               April 2019

   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  . . . . . . . . . . . . . . . . . . . . . . . .   2
     1.1.  Requirements Language . . . . . . . . . . . . . . . . . .   3
     1.2.  Terminology . . . . . . . . . . . . . . . . . . . . . . .   3
   2.  Problem Statement . . . . . . . . . . . . . . . . . . . . . .   3
   3.  BIER IPv6 encapsulation Scenario's  . . . . . . . . . . . . .   3
     3.1.  BIERv6 for Access Network . . . . . . . . . . . . . . . .   4
     3.2.  BIERv6 for Data Center  . . . . . . . . . . . . . . . . .   4
     3.3.  BIERv6 for Core Networks  . . . . . . . . . . . . . . . .   4
     3.4.  Implications for BIER in SRv6 . . . . . . . . . . . . . .   5
   4.  Example Proposed Solutions  . . . . . . . . . . . . . . . . .   5
     4.1.  BIER-ETH encapsulation in IPv6 networks . . . . . . . . .   5
     4.2.  Encode Bitstring in IPv6 destination address  . . . . . .   6
     4.3.  Add BIER header into IPv6 Extension Header  . . . . . . .   7
     4.4.  Transport BIER as IPv6 payload  . . . . . . . . . . . . .   8
     4.5.  Tunneling BIER in a IPv6 tunnel . . . . . . . . . . . . .   8
   5.  Suggested Requirements  . . . . . . . . . . . . . . . . . . .   9
   6.  IANA Considerations . . . . . . . . . . . . . . . . . . . . .  10
   7.  Security Considerations . . . . . . . . . . . . . . . . . . .  10
   8.  Acknowledgement . . . . . . . . . . . . . . . . . . . . . . .  10
   9.  Normative References  . . . . . . . . . . . . . . . . . . . .  10
   Authors' Addresses  . . . . . . . . . . . . . . . . . . . . . . .  11

1.  Introduction

   Bit Index Explicit Replication (BIER) [RFC8279] is an architecture
   that provides optimal multicast forwarding, without requiring
   intermediate routers to maintain per-flow state, through the use of a
   multicast-specific BIER header.  [RFC8296] defines two types of BIER
   encapsulation to run on physical links: one is BIER MPLS
   encapsulation to run on various physical links that support MPLS, the
   other is BIER Ethernet encapsulation to run on ethernet links, with
   an ethertype 0xAB37.  This document describes using BIER in non-MPLS
Show full document text