PCEP Procedures and Protocol Extensions for Using PCE as a Central Controller (PCECC) of BIER
draft-chen-pce-pcep-extension-pce-controller-bier-00

Document Type Active Internet-Draft (individual)
Authors Ran Chen  , BenChong Xu 
Last updated 2020-09-27
Stream (None)
Intended RFC status (None)
Formats plain text 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)
PCE WG                                                           R. Chen
Internet-Draft                                                   ch. Zhu
Intended status: Standards Track                                   B. Xu
Expires: March 29, 2021                                  ZTE Corporation
                                                      September 25, 2020

   PCEP Procedures and Protocol Extensions for Using PCE as a Central
                       Controller (PCECC) of BIER
          draft-chen-pce-pcep-extension-pce-controller-bier-00

Abstract

   This draft specify the procedures and PCEP protocol extensions for
   using the PCE as the central controller for BIER.

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 March 29, 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.

Chen, et al.             Expires March 29, 2021                 [Page 1]
Internet-Draft                 PCECC BIER                 September 2020

Table of Contents

   1.  Introduction  . . . . . . . . . . . . . . . . . . . . . . . .   2
   2.  Conventions used in this document . . . . . . . . . . . . . .   3
   3.  PCECC BIER Requirements . . . . . . . . . . . . . . . . . . .   3
   4.  Procedures for Using the PCE as the Central Controller
       (PCECC) in BIER . . . . . . . . . . . . . . . . . . . . . . .   3
     4.1.  Stateful PCE Model  . . . . . . . . . . . . . . . . . . .   3
     4.2.  New Functions . . . . . . . . . . . . . . . . . . . . . .   4
     4.3.  PCECC Capability Advertisement  . . . . . . . . . . . . .   4
     4.4.  BIER Path Operations  . . . . . . . . . . . . . . . . . .   4
       4.4.1.  PCECC Bit Index Explicit Replication (BIER) . . . . .   4
         4.4.1.1.  PCECC BIER information allocation . . . . . . . .   5
         4.4.1.2.  Redundant PCEs  . . . . . . . . . . . . . . . . .   5
         4.4.1.3.  Re Delegation and Cleanup . . . . . . . . . . . .   5
         4.4.1.4.  Synchronization of BIER information Allocations .   5
     4.5.  PCEP messages . . . . . . . . . . . . . . . . . . . . . .   5
       4.5.1.  The OPEN Object . . . . . . . . . . . . . . . . . . .   5
         4.5.1.1.  PCECC Capability sub-TLV  . . . . . . . . . . . .   5
       4.5.2.  PATH-SETUP-TYPE TLV . . . . . . . . . . . . . . . . .   6
       4.5.3.  CCI object  . . . . . . . . . . . . . . . . . . . . .   6
         4.5.3.1.  BIER Encapsulation Sub TLV  . . . . . . . . . . .   7
       4.5.4.  FEC Object  . . . . . . . . . . . . . . . . . . . . .   8
   5.  Security Considerations . . . . . . . . . . . . . . . . . . .   8
   6.  IANA Considerations . . . . . . . . . . . . . . . . . . . . .   8
   7.  Contributors  . . . . . . . . . . . . . . . . . . . . . . . .   8
   8.  Acknowledgements  . . . . . . . . . . . . . . . . . . . . . .   8
   9.  Normative References  . . . . . . . . . . . . . . . . . . . .   8
   Authors' Addresses  . . . . . . . . . . . . . . . . . . . . . . .  10

1.  Introduction

   [RFC8283]introduces the architecture for PCE as a central controller
   as an extension of the architecture described in[RFC4655] and assumes
   the continued use of PCEP as the protocol used between PCE and PCC.
   [RFC8283]further examines the motivations and applicability for PCEP
   as a Southbound Interface (SBI), and introduces the implications for
   the protocol.

   [I-D.ietf-pce-pcep-extension-for-pce-controller]specify the
   procedures and PCEP protocol extensions for using the PCE as the
   central controller for static LSPs, where LSPs can be provisioned as
   explicit label instructions at each hop on the end-to-end path.  Each
   router along the path must be told what label-forwarding instructions
   to program and what resources to reserve.  The PCE-based controller
Show full document text