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

Document Type Active Internet-Draft (individual)
Last updated 2017-07-16
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)
Networking Working Group                                       Ran. Chen
Internet-Draft                                              Zheng. Zhang
Intended status: Standards Track                         ZTE Corporation
Expires: January 16, 2018                                  July 15, 2017

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

Abstract

   Bit Index Explicit Replication (BIER)-TE shares architecture and
   packet formats with BIER as described in
   [I-D.ietf-bier-architecture].  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.BIER-TE Path can be derived from a Path Computation
   Element (PCE).

   This document specifies extensions to the Path Computation Element
   Protocol (PCEP) to handle requests and responses for the computation
   of paths for 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 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 January 16, 2018.

Copyright Notice

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

Chen & Zhang            Expires January 16, 2018                [Page 1]
Internet-Draft              PCEP Ext for BIER                  July 2017

   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
   2.  Conventions used in this document . . . . . . . . . . . . . .   3
   3.  Overview of PCEP Operation in BIER Networks . . . . . . . . .   3
   4.  BIER PCEP Message Extensions  . . . . . . . . . . . . . . . .   3
     4.1.  BIER Capability Advertisement . . . . . . . . . . . . . .   3
       4.1.1.  The OPEN Object . . . . . . . . . . . . . . . . . . .   3
         4.1.1.1.  The BIER PCE Capability TLV . . . . . . . . . . .   3
     4.2.  Path Computation Request/Reply Message Extensions . . . .   4
       4.2.1.  The RP/SPR Object . . . . . . . . . . . . . . . . . .   4
       4.2.2.  The New BIER END-POINT Object . . . . . . . . . . . .   5
       4.2.3.  ERO Object  . . . . . . . . . . . . . . . . . . . . .   5
         4.2.3.1.  BIER-ERO Subobject  . . . . . . . . . . . . . . .   6
       4.2.4.  RRO Object  . . . . . . . . . . . . . . . . . . . . .   7
         4.2.4.1.  RRO Processing  . . . . . . . . . . . . . . . . .   7
   5.  Security Considerations . . . . . . . . . . . . . . . . . . .   7
   6.  IANA Considerations . . . . . . . . . . . . . . . . . . . . .   7
     6.1.  PCEP Objects  . . . . . . . . . . . . . . . . . . . . . .   7
     6.2.  PCEP-Error Objects and Types  . . . . . . . . . . . . . .   8
     6.3.  PCEP TLV Type Indicators  . . . . . . . . . . . . . . . .   8
     6.4.  New Path Setup Type . . . . . . . . . . . . . . . . . . .   8
   7.  References  . . . . . . . . . . . . . . . . . . . . . . . . .   8
     7.1.  Normative references  . . . . . . . . . . . . . . . . . .   9
     7.2.  Informative references  . . . . . . . . . . . . . . . . .   9
   Authors' Addresses  . . . . . . . . . . . . . . . . . . . . . . .   9

1.  Introduction

   Bit Index Explicit Replication (BIER)-TE shares architecture and
   packet formats with BIER as described in
   [I-D.ietf-bier-architecture].  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.BIER-TE Path can be derived from a Path Computation
   Element (PCE).

   This document specifies extensions to the Path Computation Element
   Protocol (PCEP) to handle requests and responses for the computation
Show full document text