Path Computation Element Communication Protocol (PCEP) Extensions for MPLS-TE Label Switched Path (LSP) Auto-Bandwidth Adjustment with Stateful PCE
RFC 8733

Document Type RFC - Proposed Standard (February 2020; No errata)
Last updated 2020-02-25
Replaces draft-dhody-pce-stateful-pce-auto-bandwidth
Stream IETF
Formats plain text html xml pdf htmlized bibtex
Reviews
Stream WG state Submitted to IESG for Publication
Document shepherd Adrian Farrel
Shepherd write-up Show (last changed 2019-05-31)
IESG IESG state RFC 8733 (Proposed Standard)
Consensus Boilerplate Yes
Telechat date
Responsible AD Deborah Brungard
Send notices to Adrian Farrel <adrian@olddog.co.uk>
IANA IANA review state Version Changed - Review Needed
IANA action state RFC-Ed-Ack
RFC Editor RFC Editor state AUTH48-DONE


Internet Engineering Task Force (IETF)                     D. Dhody, Ed.
Request for Comments: 8733                           Huawei Technologies
Category: Standards Track                                 R. Gandhi, Ed.
ISSN: 2070-1721                                      Cisco Systems, Inc.
                                                                U. Palle
                                                                R. Singh
                                                  Individual Contributor
                                                                 L. Fang
                                                     Expedia Group, Inc.
                                                           February 2020

 Path Computation Element Communication Protocol (PCEP) Extensions for
    MPLS-TE Label Switched Path (LSP) Auto-Bandwidth Adjustment with
                              Stateful PCE

Abstract

   The Path Computation Element Communication Protocol (PCEP) provides
   mechanisms for Path Computation Elements (PCEs) to perform path
   computations in response to Path Computation Client (PCC) requests.
   Stateful PCE extensions allow stateful control of MPLS-TE Label
   Switched Paths (LSPs) using PCEP.

   The auto-bandwidth feature allows automatic and dynamic adjustment of
   the TE LSP bandwidth reservation based on the volume of traffic
   flowing through the LSP.  This document describes PCEP extensions for
   auto-bandwidth adjustment when employing an active stateful PCE for
   both PCE-initiated and PCC-initiated LSPs.

Status of This Memo

   This is an Internet Standards Track document.

   This document is a product of the Internet Engineering Task Force
   (IETF).  It represents the consensus of the IETF community.  It has
   received public review and has been approved for publication by the
   Internet Engineering Steering Group (IESG).  Further information on
   Internet Standards is available in Section 2 of RFC 7841.

   Information about the current status of this document, any errata,
   and how to provide feedback on it may be obtained at
   https://www.rfc-editor.org/info/rfc8733.

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.  Conventions Used in This Document
     2.1.  Requirements Language
     2.2.  Abbreviations
     2.3.  Terminology
   3.  Requirements for PCEP Extensions
   4.  Architectural Overview
     4.1.  Auto-Bandwidth Overview
     4.2.  Auto-Bandwidth Theory of Operation
     4.3.  Scaling Considerations
   5.  PCEP Extensions
     5.1.  Capability Advertisement
       5.1.1.  AUTO-BANDWIDTH-CAPABILITY TLV
     5.2.  AUTO-BANDWIDTH-ATTRIBUTES TLV
       5.2.1.  Sample-Interval Sub-TLV
       5.2.2.  Adjustment-Intervals
         5.2.2.1.  Adjustment-Interval Sub-TLV
         5.2.2.2.  Down-Adjustment-Interval Sub-TLV
       5.2.3.  Adjustment-Thresholds
         5.2.3.1.  Adjustment-Threshold Sub-TLV
         5.2.3.2.  Adjustment-Threshold-Percentage Sub-TLV
         5.2.3.3.  Down-Adjustment-Threshold Sub-TLV
         5.2.3.4.  Down-Adjustment-Threshold-Percentage Sub-TLV
       5.2.4.  Minimum and Maximum-Bandwidth Values
         5.2.4.1.  Minimum-Bandwidth Sub-TLV
         5.2.4.2.  Maximum-Bandwidth Sub-TLV
       5.2.5.  Overflow and Underflow Conditions
         5.2.5.1.  Overflow-Threshold Sub-TLV
         5.2.5.2.  Overflow-Threshold-Percentage Sub-TLV
         5.2.5.3.  Underflow-Threshold Sub-TLV
         5.2.5.4.  Underflow-Threshold-Percentage Sub-TLV
     5.3.  BANDWIDTH Object
     5.4.  The PCInitiate Message
     5.5.  The PCUpd Message
     5.6.  The PCRpt Message
     5.7.  The PCNtf Message
   6.  Manageability Considerations
     6.1.  Control of Function and Policy
     6.2.  Information and Data Models
     6.3.  Liveness Detection and Monitoring
     6.4.  Verifying Correct Operations
     6.5.  Requirements for Other Protocols
     6.6.  Impact on Network Operations
   7.  Security Considerations
   8.  IANA Considerations
     8.1.  PCEP TLV Type Indicators
     8.2.  AUTO-BANDWIDTH-CAPABILITY TLV Flag Field
     8.3.  AUTO-BANDWIDTH-ATTRIBUTES Sub-TLV
     8.4.  Error Object
     8.5.  Notification Object
   9.  References
     9.1.  Normative References
     9.2.  Informative References
   Acknowledgments
   Contributors
   Authors' Addresses
Show full document text