BIER in IPv6
draft-zhang-bier-bierin6-02

Document Type Active Internet-Draft (individual)
Last updated 2018-10-21
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                                                            Z. Zhang
Internet-Draft                                           ZTE Corporation
Intended status: Standards Track                           A. Przygienda
Expires: April 24, 2019                           Juniper Networks, Inc.
                                                        October 21, 2018

                              BIER in IPv6
                      draft-zhang-bier-bierin6-02

Abstract

   BIER is a new architecture for the forwarding of multicast data
   packets.  This document defines native IPv6 encapsulation for BIER
   hop-by-hop forwarding or BIERin6 for short.

Requirements Language

   The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
   "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this
   document are to be interpreted as described in RFC2119.

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 April 24, 2019.

Copyright Notice

   Copyright (c) 2018 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 April 24, 2019                 [Page 1]
Internet-Draft                   BIERv6                     October 2018

   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.  IPv6 Header . . . . . . . . . . . . . . . . . . . . . . . . .   2
   3.  BIER Header . . . . . . . . . . . . . . . . . . . . . . . . .   3
   4.  IANA Considerations . . . . . . . . . . . . . . . . . . . . .   3
   5.  Security Considerations . . . . . . . . . . . . . . . . . . .   3
   6.  References  . . . . . . . . . . . . . . . . . . . . . . . . .   3
     6.1.  Normative References  . . . . . . . . . . . . . . . . . .   4
     6.2.  Informative References  . . . . . . . . . . . . . . . . .   4
   Authors' Addresses  . . . . . . . . . . . . . . . . . . . . . . .   4

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 necessarily precondition construction of a
   multicast distribution tree, nor does it require intermediate nodes
   to maintain any per-flow state.

   [RFC8296] defines the BIER encapsulation format in MPLS and non-MPLS
   environment that rely on MPLS labels or special ethernet type
   support.  In pure IPv6 environments a BIER packet could be forwarded
   by means of simple IPv6 hop-by-hop processing only, without any new
   hardware support.  Ultimate hardware support is obviously possible
   but the encapsulation is especially interesting for environments like
   [RFC7368] where high throughput multicast forwarding performance is
   not decisive and could be initially done in slow-path or end host
   (assuming last-hop being IPv6 encapsulated).

   This document defines native BIER IPv6 [RFC2460] encapsulation we
   call BIERv6.  This encapsulation is aligned with the format defined
   in [RFC8296] for a non-mpls version.

   This document uses terminology defined in [RFC8279].

2.  IPv6 Header

   The BIER packet itself is the payload of an IPv6 frame.  The
   destination address field in IPv6 packet MAY be the neighbor's link-
   local or one of the loopback interface addresses of that neighbor.
   The destination address SHOULD be the BFR-prefix advertised by IGP/

Zhang & Przygienda       Expires April 24, 2019                 [Page 2]
Internet-Draft                   BIERv6                     October 2018

   BGP extensions for BIER.  TTL value of 1 MUST be used on the IPv6
   packet.

   The source address field in IPv6 packet MAY be the loopback interface
   address of the sending BFIR.  The address SHOULD be the BFR-prefix
   advertised in IGP/BGP extension.
Show full document text