Supporting BIER in IPv6 Networks (BIERin6)
draft-zhang-bier-bierin6-08

Document Type Active Internet-Draft (individual)
Authors Zheng Zhang  , Zhaohui Zhang  , IJsbrand Wijnands  , Mankamana Mishra  , Hooman Bidgoli  , Gyan Mishra 
Last updated 2020-12-10
Stream (None)
Intended RFC status (None)
Formats plain text xml pdf htmlized (tools) htmlized 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                                                            Z. Zhang
Internet-Draft                                           ZTE Corporation
Intended status: Standards Track                           Z. Zhang, Ed.
Expires: June 13, 2021                                  Juniper Networks
                                                             I. Wijnands
                                                              Individual
                                                               M. Mishra
                                                           Cisco Systems
                                                              H. Bidgoli
                                                                   Nokia
                                                          G. Mishra, Ed.
                                                                 Verizon
                                                       December 10, 2020

               Supporting BIER in IPv6 Networks (BIERin6)
                      draft-zhang-bier-bierin6-08

Abstract

   BIER is a new architecture for the forwarding of multicast data
   packets without requiring per-flow state inside the network.  This
   document describes how the existing BIER encapsulation specified in
   RFC 8296 works in an IPv6 non-MPLS network, referred to as BIERin6.
   Specifically, like in an IPv4 network, BIER can work over L2 links
   directly or over tunnels.  In case of IPv6 tunneling, a new IP "Next
   Header" type is to be assigned for BIER.

Requirements Language

   The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
   "SHOULD", "SHOULD NOT", "RECOMMENDED", "NOT RECOMMENDED", "MAY", and
   "OPTIONAL" in this document are to be interpreted as described in BCP
   14 [RFC2119] [RFC8174] when, and only when, they appear in all
   capitals, as shown here.

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

Zhang, et al.             Expires June 13, 2021                 [Page 1]
Internet-Draft                   BIERin6                   December 2020

   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 June 13, 2021.

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  . . . . . . . . . . . . . . . . . . . . . . . .   2
     1.1.  BIER over L2/Tunnels  . . . . . . . . . . . . . . . . . .   3
     1.2.  Considerations of Requirements for BIER in IPv6 Networks    3
   2.  IPv6 Header . . . . . . . . . . . . . . . . . . . . . . . . .   5
     2.1.  IPv6 Options Considerations . . . . . . . . . . . . . . .   5
   3.  BIER Header . . . . . . . . . . . . . . . . . . . . . . . . .   6
   4.  IPv6 Encapsulation Advertisement  . . . . . . . . . . . . . .   6
     4.1.  Format  . . . . . . . . . . . . . . . . . . . . . . . . .   6
     4.2.  Inter-area prefix redistribution  . . . . . . . . . . . .   7
   5.  IANA Considerations . . . . . . . . . . . . . . . . . . . . .   7
   6.  Security Considerations . . . . . . . . . . . . . . . . . . .   7
   7.  Acknowledgement . . . . . . . . . . . . . . . . . . . . . . .   7
   8.  References  . . . . . . . . . . . . . . . . . . . . . . . . .   7
     8.1.  Normative References  . . . . . . . . . . . . . . . . . .   7
     8.2.  Informative References  . . . . . . . . . . . . . . . . .   8
   Authors' Addresses  . . . . . . . . . . . . . . . . . . . . . . .  10

1.  Introduction

   BIER [RFC8279] is a new architecture for the forwarding of multicast
   data packets.  It provides optimal forwarding through a "multicast
   domain" and it does not precondition construction of a multicast
   distribution tree, nor does it require intermediate nodes to maintain
   any per-flow state.

Zhang, et al.             Expires June 13, 2021                 [Page 2]
Show full document text