PCEP Extensions for BIER
draft-chen-pce-bier-05

Document Type Active Internet-Draft (individual)
Last updated 2019-03-24
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)
Networking Working Group                                       Ran. Chen
Internet-Draft                                              Zheng. Zhang
Intended status: Standards Track                         ZTE Corporation
Expires: September 23, 2019                               March 22, 2019

                        PCEP Extensions for BIER
                         draft-chen-pce-bier-05

Abstract

   Bit Index Explicit Replication (BIER)-TE shares architecture and
   packet formats with BIER as described in [RFC8279].  BIER-TE forwards
   and replicates packets based on a BitString in the packet header, but
   every BitPosition of the BitString of a BIER-TE packet indicates one
   or more adjacencies as described in [I-D.ietf-bier-te-arch].BIER-TE
   Path can be derived from a Path Computation Element (PCE).

   This document specifies extensions to the Path Computation Element
   Protocol (PCEP) that allow a PCE to compute and initiate the path for
   the BIER-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 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 September 23, 2019.

Copyright Notice

   Copyright (c) 2019 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

Chen & Zhang           Expires September 23, 2019               [Page 1]
Internet-Draft              PCEP Ext for BIER                 March 2019

   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.  Conventions used in this document . . . . . . . . . . . . . .   3
   3.  Overview of PCEP Operation in BIER Networks . . . . . . . . .   3
   4.  Object Formats  . . . . . . . . . . . . . . . . . . . . . . .   3
     4.1.  The OPEN Object . . . . . . . . . . . . . . . . . . . . .   3
       4.1.1.  The BIER-TE PCE Capability sub-TLV  . . . . . . . . .   3
     4.2.  The SRP Object  . . . . . . . . . . . . . . . . . . . . .   4
     4.3.  END-POINTS object . . . . . . . . . . . . . . . . . . . .   4
       4.3.1.  P2MP END-POINTS object  . . . . . . . . . . . . . . .   4
       4.3.2.  The New BIER END-POINT Object . . . . . . . . . . . .   4
     4.4.  ERO Object  . . . . . . . . . . . . . . . . . . . . . . .   5
       4.4.1.  BIER-ERO Subobject  . . . . . . . . . . . . . . . . .   6
       4.4.2.  BIER-ERO Processing . . . . . . . . . . . . . . . . .   7
   5.  Security Considerations . . . . . . . . . . . . . . . . . . .   7
   6.  IANA Considerations . . . . . . . . . . . . . . . . . . . . .   7
     6.1.  PCEP Objects  . . . . . . . . . . . . . . . . . . . . . .   7
       6.1.1.  BIER-TE-PCE-CAPABILITY Sub-TLV Type Indicators  . . .   7
       6.1.2.  New Path Setup Type . . . . . . . . . . . . . . . . .   8
       6.1.3.  New BIER END-POINT Object . . . . . . . . . . . . . .   8
       6.1.4.  BIER-ERO Subobject  . . . . . . . . . . . . . . . . .   8
       6.1.5.  PCEP-Error Objects and Types  . . . . . . . . . . . .   8
   7.  Normative references  . . . . . . . . . . . . . . . . . . . .   9
   Authors' Addresses  . . . . . . . . . . . . . . . . . . . . . . .  10

1.  Introduction

   Bit Index Explicit Replication (BIER)-TE shares architecture and
   packet formats with BIER as described in [RFC8279].  BIER-TE forwards
   and replicates packets based on a BitString in the packet header, but
   every BitPosition of the BitString of a BIER-TE packet indicates one
   or more adjacencies as described in [I-D.ietf-bier-te-arch].BIER-TE
   Path can be derived from a Path Computation Element (PCE).

   [RFC8231] specifies a set of extensions to PCEP that allow a PCE to
   compute and recommend network paths in compliance with [RFC4657] and
   defines objects and TLVs for MPLS-TE LSPs.

   This document uses a PCE for computing one or more BIER-TE paths
   taking into account various constraints and objective functions.
Show full document text