draft-ietf-pce-stateful-pce-auto-bandwidth-12.txt   rfc8733.txt 
PCE Working Group D. Dhody, Ed. Internet Engineering Task Force (IETF) D. Dhody, Ed.
Internet-Draft Huawei Technologies Request for Comments: 8733 Huawei Technologies
Intended status: Standards Track R. Gandhi, Ed. Category: Standards Track R. Gandhi, Ed.
Expires: March 29, 2020 Cisco Systems, Inc. ISSN: 2070-1721 Cisco Systems, Inc.
U. Palle U. Palle
R. Singh R. Singh
Individual Contributor Individual Contributor
L. Fang L. Fang
Expedia, Inc. Expedia Group, Inc.
September 26, 2019 February 2020
PCEP Extensions for MPLS-TE LSP Automatic Bandwidth Adjustment with Path Computation Element Communication Protocol (PCEP) Extensions for
MPLS-TE Label Switched Path (LSP) Auto-Bandwidth Adjustment with
Stateful PCE Stateful PCE
draft-ietf-pce-stateful-pce-auto-bandwidth-12
Abstract Abstract
The Path Computation Element Communication Protocol (PCEP) provides The Path Computation Element Communication Protocol (PCEP) provides
mechanisms for Path Computation Elements (PCEs) to perform path mechanisms for Path Computation Elements (PCEs) to perform path
computations in response to Path Computation Clients (PCCs) requests. computations in response to Path Computation Client (PCC) requests.
The Stateful PCE extensions allow stateful control of Multi-Protocol Stateful PCE extensions allow stateful control of MPLS-TE Label
Label Switching (MPLS) Traffic Engineering Label Switched Paths (TE Switched Paths (LSPs) using PCEP.
LSPs) using PCEP.
The automatic bandwidth feature allows automatic and dynamic The auto-bandwidth feature allows automatic and dynamic adjustment of
adjustment of the TE LSP bandwidth reservation based on the volume of the TE LSP bandwidth reservation based on the volume of traffic
traffic flowing through the LSP. This document describes PCEP flowing through the LSP. This document describes PCEP extensions for
extensions for automatic bandwidth adjustment when employing an auto-bandwidth adjustment when employing an active stateful PCE for
Active Stateful PCE for both PCE-Initiated and PCC-Initiated LSPs. both PCE-initiated and PCC-initiated LSPs.
Status of This Memo Status of This Memo
This Internet-Draft is submitted in full conformance with the This is an Internet Standards Track document.
provisions of BCP 78 and BCP 79.
Internet-Drafts are working documents of the Internet Engineering This document is a product of the Internet Engineering Task Force
Task Force (IETF). Note that other groups may also distribute (IETF). It represents the consensus of the IETF community. It has
working documents as Internet-Drafts. The list of current Internet- received public review and has been approved for publication by the
Drafts is at https://datatracker.ietf.org/drafts/current/. Internet Engineering Steering Group (IESG). Further information on
Internet Standards is available in Section 2 of RFC 7841.
Internet-Drafts are draft documents valid for a maximum of six months Information about the current status of this document, any errata,
and may be updated, replaced, or obsoleted by other documents at any and how to provide feedback on it may be obtained at
time. It is inappropriate to use Internet-Drafts as reference https://www.rfc-editor.org/info/rfc8733.
material or to cite them other than as "work in progress."
Copyright Notice Copyright Notice
Copyright (c) 2019 IETF Trust and the persons identified as the Copyright (c) 2020 IETF Trust and the persons identified as the
document authors. All rights reserved. document authors. All rights reserved.
This document is subject to BCP 78 and the IETF Trust's Legal This document is subject to BCP 78 and the IETF Trust's Legal
Provisions Relating to IETF Documents Provisions Relating to IETF Documents
(https://trustee.ietf.org/license-info) in effect on the date of (https://trustee.ietf.org/license-info) in effect on the date of
publication of this document. Please review these documents publication of this document. Please review these documents
carefully, as they describe your rights and restrictions with respect carefully, as they describe your rights and restrictions with respect
to this document. Code Components extracted from this document must to this document. Code Components extracted from this document must
include Simplified BSD License text as described in Section 4.e of include Simplified BSD License text as described in Section 4.e of
the Trust Legal Provisions and are provided without warranty as the Trust Legal Provisions and are provided without warranty as
described in the Simplified BSD License. described in the Simplified BSD License.
Table of Contents Table of Contents
1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 3 1. Introduction
2. Conventions Used in This Document . . . . . . . . . . . . . . 4 2. Conventions Used in This Document
2.1. Requirements Language . . . . . . . . . . . . . . . . . . 4 2.1. Requirements Language
2.2. Abbreviations . . . . . . . . . . . . . . . . . . . . . . 4 2.2. Abbreviations
2.3. Terminology . . . . . . . . . . . . . . . . . . . . . . . 5 2.3. Terminology
3. Requirements for PCEP Extensions . . . . . . . . . . . . . . . 7 3. Requirements for PCEP Extensions
4. Architectural Overview . . . . . . . . . . . . . . . . . . . . 8 4. Architectural Overview
4.1. Auto-Bandwidth Overview . . . . . . . . . . . . . . . . . 8 4.1. Auto-Bandwidth Overview
4.2. Auto-bandwidth Theory of Operation . . . . . . . . . . . . 9 4.2. Auto-Bandwidth Theory of Operation
4.3. Scaling Considerations . . . . . . . . . . . . . . . . . . 10 4.3. Scaling Considerations
5. PCEP Extensions . . . . . . . . . . . . . . . . . . . . . . . 10 5. PCEP Extensions
5.1. Capability Advertisement . . . . . . . . . . . . . . . . . 10 5.1. Capability Advertisement
5.1.1. AUTO-BANDWIDTH-CAPABILITY TLV . . . . . . . . . . . . 11 5.1.1. AUTO-BANDWIDTH-CAPABILITY TLV
5.2. AUTO-BANDWIDTH-ATTRIBUTES TLV . . . . . . . . . . . . . . 12 5.2. AUTO-BANDWIDTH-ATTRIBUTES TLV
5.2.1. Sample-Interval sub-TLV . . . . . . . . . . . . . . . 13 5.2.1. Sample-Interval Sub-TLV
5.2.2. Adjustment Intervals . . . . . . . . . . . . . . . . . 14 5.2.2. Adjustment-Intervals
5.2.2.1. Adjustment-Interval sub-TLV . . . . . . . . . . . 14 5.2.2.1. Adjustment-Interval Sub-TLV
5.2.2.2. Down-Adjustment-Interval sub-TLV . . . . . . . . . 14 5.2.2.2. Down-Adjustment-Interval Sub-TLV
5.2.3. Adjustment Thresholds . . . . . . . . . . . . . . . . 15 5.2.3. Adjustment-Thresholds
5.2.3.1. Adjustment-Threshold sub-TLV . . . . . . . . . . . 15 5.2.3.1. Adjustment-Threshold Sub-TLV
5.2.3.2. Adjustment-Threshold-Percentage sub-TLV . . . . . 16 5.2.3.2. Adjustment-Threshold-Percentage Sub-TLV
5.2.3.3. Down-Adjustment-Threshold sub-TLV . . . . . . . . 17 5.2.3.3. Down-Adjustment-Threshold Sub-TLV
5.2.3.4. Down-Adjustment-Threshold-Percentage sub-TLV . . . 18 5.2.3.4. Down-Adjustment-Threshold-Percentage Sub-TLV
5.2.4. Minimum and Maximum Bandwidth Values . . . . . . . . . 19 5.2.4. Minimum and Maximum-Bandwidth Values
5.2.4.1. Minimum-Bandwidth sub-TLV . . . . . . . . . . . . 19 5.2.4.1. Minimum-Bandwidth Sub-TLV
5.2.4.2. Maximum-Bandwidth sub-TLV . . . . . . . . . . . . 19 5.2.4.2. Maximum-Bandwidth Sub-TLV
5.2.5. Overflow and Underflow Conditions . . . . . . . . . . 20 5.2.5. Overflow and Underflow Conditions
5.2.5.1. Overflow-Threshold sub-TLV . . . . . . . . . . . . 20 5.2.5.1. Overflow-Threshold Sub-TLV
5.2.5.2. Overflow-Threshold-Percentage sub-TLV . . . . . . 21 5.2.5.2. Overflow-Threshold-Percentage Sub-TLV
5.2.5.3. Underflow-Threshold sub-TLV . . . . . . . . . . . 22 5.2.5.3. Underflow-Threshold Sub-TLV
5.2.5.4. Underflow-Threshold-Percentage sub-TLV . . . . . . 23 5.2.5.4. Underflow-Threshold-Percentage Sub-TLV
5.3. BANDWIDTH Object . . . . . . . . . . . . . . . . . . . . . 24 5.3. BANDWIDTH Object
5.4. The PCInitiate Message . . . . . . . . . . . . . . . . . . 24 5.4. The PCInitiate Message
5.5. The PCUpd Message . . . . . . . . . . . . . . . . . . . . 24 5.5. The PCUpd Message
5.6. The PCRpt Message . . . . . . . . . . . . . . . . . . . . 24 5.6. The PCRpt Message
5.7. The PCNtf Message . . . . . . . . . . . . . . . . . . . . 25 5.7. The PCNtf Message
6. Manageability Considerations . . . . . . . . . . . . . . . . . 26 6. Manageability Considerations
6.1. Control of Function and Policy . . . . . . . . . . . . . . 26 6.1. Control of Function and Policy
6.2. Information and Data Models . . . . . . . . . . . . . . . 26 6.2. Information and Data Models
6.3. Liveness Detection and Monitoring . . . . . . . . . . . . 27 6.3. Liveness Detection and Monitoring
6.4. Verify Correct Operations . . . . . . . . . . . . . . . . 27 6.4. Verifying Correct Operations
6.5. Requirements On Other Protocols . . . . . . . . . . . . . 27 6.5. Requirements for Other Protocols
6.6. Impact On Network Operations . . . . . . . . . . . . . . . 27 6.6. Impact on Network Operations
7. Security Considerations . . . . . . . . . . . . . . . . . . . 28 7. Security Considerations
8. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 28 8. IANA Considerations
8.1. PCEP TLV Type Indicators . . . . . . . . . . . . . . . . . 28 8.1. PCEP TLV Type Indicators
8.2. AUTO-BANDWIDTH-CAPABILITY TLV Flag Field . . . . . . . . . 28 8.2. AUTO-BANDWIDTH-CAPABILITY TLV Flag Field
8.3. AUTO-BANDWIDTH-ATTRIBUTES Sub-TLV . . . . . . . . . . . . 29 8.3. AUTO-BANDWIDTH-ATTRIBUTES Sub-TLV
8.4. Error Object . . . . . . . . . . . . . . . . . . . . . . . 29 8.4. Error Object
8.5. Notification Object . . . . . . . . . . . . . . . . . . . 30 8.5. Notification Object
9. References . . . . . . . . . . . . . . . . . . . . . . . . . . 31 9. References
9.1. Normative References . . . . . . . . . . . . . . . . . . . 31 9.1. Normative References
9.2. Informative References . . . . . . . . . . . . . . . . . . 31 9.2. Informative References
Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . . . 33 Acknowledgments
Contributors' Addresses . . . . . . . . . . . . . . . . . . . . . 33 Contributors
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . . 34 Authors' Addresses
1. Introduction 1. Introduction
[RFC5440] describes the Path Computation Element Protocol (PCEP) as a [RFC5440] describes the Path Computation Element Protocol (PCEP) as a
communication mechanism between a Path Computation Client (PCC) and a communication mechanism between a Path Computation Client (PCC) and a
Path Computation Element (PCE), or between PCE and PCE, that enables Path Computation Element (PCE), or between a PCE and a PCE, that
computation of Multi-Protocol Label Switching (MPLS) Traffic enables computation of MPLS-TE Label Switched Paths (LSPs).
Engineering Label Switched Paths (TE LSPs).
[RFC8231] specifies extensions to PCEP to enable stateful control of [RFC8231] specifies extensions to PCEP to enable stateful control of
MPLS TE LSPs. It describes two mode of operations - Passive stateful MPLS-TE LSPs. It describes two modes of operation: passive stateful
PCE and Active stateful PCE. Further, [RFC8281] describes the setup, PCE and active stateful PCE. Further, [RFC8281] describes the setup,
maintenance and teardown of PCE-Initiated LSPs for the stateful PCE maintenance, and teardown of PCE-initiated LSPs for the stateful PCE
model. In this document, the focus is on Active stateful PCE where model. In this document, the focus is on the active stateful PCE,
the LSPs are controlled by the PCE. where the LSPs are controlled by the PCE.
Over time, based on the varying traffic pattern, an LSP established Over time, based on the varying traffic pattern, an LSP established
with a certain bandwidth may require adjustment of the bandwidth with a certain bandwidth may require adjustment of the bandwidth
reserved in the network dynamically. The head-end Label Switch reserved in the network dynamically. The head-end Label Switching
Router (LSR) monitors the actual bandwidth demand of the established Router (LSR) monitors the actual bandwidth demand of the established
LSP and periodically computes new bandwidth. The head-end LSR LSP and periodically computes new bandwidth. The head-end LSR
adjusts the bandwidth reservation of the LSP based on the computed automatically adjusts the bandwidth reservation of the LSP based on
bandwidth automatically. This feature, when available in the head- the computed bandwidth. This feature, when available in the head-end
end Label Switching Router (LSR) implementation, is common referred LSR implementation, is commonly referred to as auto-bandwidth. The
to as Auto-Bandwidth. The Auto-Bandwidth feature is described in auto-bandwidth feature is described in detail in Section 4 of this
detail in Section 4 of this document. document.
In the model considered in this document, the PCC (head-end of the In the model considered in this document, the PCC (head-end of the
LSP) collects the traffic rate samples flowing through the LSP and LSP) collects the traffic rate samples flowing through the LSP and
calculates the new adjusted bandwidth. The PCC reports the calculates the new Adjusted Bandwidth. The PCC reports the
calculated bandwidth to be adjusted to the PCE. This is similar to calculated bandwidth to be adjusted to the PCE. This is similar to
the Passive stateful PCE model: while the Passive stateful PCE uses a the passive stateful PCE model: while the passive stateful PCE uses a
path request/reply mechanism, the Active stateful PCE uses a path request/reply mechanism, the active stateful PCE uses a report/
report/update mechanism. In case of PCE-Initiated LSP, the PCC is update mechanism. With a PCE-initiated LSP, the PCC is requested
requested during the LSP initiation to monitor and calculate the new during the LSP initiation to monitor and calculate the new Adjusted
adjusted bandwidth. [RFC8051] describes the use-case for Auto- Bandwidth. [RFC8051] describes the use case for auto-bandwidth
Bandwidth adjustment for Passive and Active stateful PCE. adjustment for passive and active stateful PCEs.
Another approach would be to send the measured values itself to the Another approach would be to send the measured values themselves to
PCE, which is considered out of scope for this document. the PCE, which is considered out of scope for this document.
This document defines the PCEP extensions needed to support an Auto- This document defines the PCEP extensions needed to support an auto-
Bandwidth feature in an Active stateful PCE model where the LSP bandwidth feature in an active stateful PCE model where the LSP
bandwidth to be adjusted is calculated on the PCC (head-end of the bandwidth to be adjusted is calculated on the PCC (head-end of the
LSP). The use of PCE to calculate the bandwidth to be adjusted is out LSP). The use of PCE to calculate the bandwidth to be adjusted is
of scope of this document. out of scope of this document.
2. Conventions Used in This Document 2. Conventions Used in This Document
2.1. Requirements Language 2.1. Requirements Language
The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
"SHOULD", "SHOULD NOT", "RECOMMENDED", "NOT RECOMMENDED", "MAY", and "SHOULD", "SHOULD NOT", "RECOMMENDED", "NOT RECOMMENDED", "MAY", and
"OPTIONAL" in this document are to be interpreted as described in BCP "OPTIONAL" in this document are to be interpreted as described in
14 [RFC2119] [RFC8174] when, and only when, they appear in all BCP 14 [RFC2119] [RFC8174] when, and only when, they appear in all
capitals, as shown here. capitals, as shown here.
2.2. Abbreviations 2.2. Abbreviations
PCC: Path Computation Client. PCC: Path Computation Client
PCE: Path Computation Element. PCE: Path Computation Element
PCEP: Path Computation Element Communication Protocol. PCEP: Path Computation Element Communication Protocol
TE LSP: Traffic Engineering Label Switched Path. TE: Traffic Engineering
LSP: Label Switched Path
2.3. Terminology 2.3. Terminology
The reader is assumed to be familiar with the terminology defined in The reader is assumed to be familiar with the terminology defined in
[RFC5440], [RFC8231], and [RFC8281]. [RFC5440], [RFC8231], and [RFC8281].
In this document, the PCC is considered to be the head end LSR of the In this document, the PCC is considered to be the head-end LSR of the
LSP. Other types of PCC are not in scope. LSP. Other types of PCCs are not in scope.
The following auto-bandwidth terminology is defined in this document. The following auto-bandwidth terminology is defined in this document.
Maximum Average Bandwidth (MaxAvgBw): The maximum average bandwidth Maximum Average Bandwidth (MaxAvgBw): The maximum average bandwidth
represents the current 'measured' traffic bandwidth demand of the represents the current 'measured' traffic bandwidth demand of the
LSP during a time interval. This is the maximum value of the LSP during a time interval. This is the maximum value of the
traffic bandwidth rate samples (Bandwidth-Samples) in a given time traffic bandwidth rate samples (Bandwidth-Samples) in a given time
interval. interval.
Adjusted Bandwidth: This is the Auto-Bandwidth 'computed' bandwidth Adjusted Bandwidth: This is the auto-bandwidth 'computed' bandwidth
that is used to adjust the bandwidth reservation of the LSP. that is used to adjust the bandwidth reservation of the LSP.
Sample-Interval: The periodic time interval at which the measured Sample-Interval: The periodic time interval at which the measured
traffic rate of the LSP is collected as a Bandwidth-Sample. traffic rate of the LSP is collected as a Bandwidth-Sample.
Bandwidth-Sample: The bandwidth sample of the measured traffic rate Bandwidth-Sample: The Bandwidth-Sample of the measured traffic rate
of the LSP collected at every Sample-Interval. of the LSP collected at every Sample-Interval.
Maximum-Bandwidth: The maximum bandwidth that can be reserved for Maximum-Bandwidth: The Maximum-Bandwidth that can be reserved for
the LSP. the LSP.
Minimum-Bandwidth: The minimum bandwidth that can be reserved for Minimum-Bandwidth: The Minimum-Bandwidth that can be reserved for
the LSP. the LSP.
Up-Adjustment-Interval: The periodic time interval at which the Up-Adjustment-Interval: The periodic time interval at which the
bandwidth adjustment should be made using the MaxAvgBw, when bandwidth adjustment should be made using the MaxAvgBw when
MaxAvgBw is greater than the current bandwidth reservation of the MaxAvgBw is greater than the current bandwidth reservation of the
LSP. LSP.
Down-Adjustment-Interval: The periodic time interval at which the Down-Adjustment-Interval: The periodic time interval at which the
bandwidth adjustment should be made using the MaxAvgBw, when bandwidth adjustment should be made using the MaxAvgBw when
MaxAvgBw is less than the current bandwidth reservation of the MaxAvgBw is less than the current bandwidth reservation of the
LSP. LSP.
Up-Adjustment-Threshold: This parameter is used to decide when the Up-Adjustment-Threshold: This parameter is used to decide when the
LSP bandwidth should be adjusted. If the percentage or absolute LSP bandwidth should be adjusted. If the percentage or absolute
difference between the current MaxAvgBw and the current bandwidth difference between the current MaxAvgBw and the current bandwidth
reservation is greater than or equal to the threshold value, the reservation is greater than or equal to the threshold value, the
LSP bandwidth is adjusted (upsized) to the current bandwidth LSP bandwidth is adjusted (upsized) to the current bandwidth
demand (Adjusted Bandwidth) at the Up-Adjustment-Interval expiry. demand (Adjusted Bandwidth) at the Up-Adjustment-Interval expiry.
skipping to change at page 6, line 20 skipping to change at line 245
LSP bandwidth should be adjusted. If the percentage or absolute LSP bandwidth should be adjusted. If the percentage or absolute
difference between the current bandwidth reservation and the difference between the current bandwidth reservation and the
current MaxAvgBw is greater than or equal to the threshold value, current MaxAvgBw is greater than or equal to the threshold value,
the LSP bandwidth is adjusted (downsized) to the current bandwidth the LSP bandwidth is adjusted (downsized) to the current bandwidth
demand (Adjusted Bandwidth) at the Down-Adjustment-Interval demand (Adjusted Bandwidth) at the Down-Adjustment-Interval
expiry. expiry.
Overflow-Count: This parameter is used to decide when the LSP Overflow-Count: This parameter is used to decide when the LSP
bandwidth should be adjusted when there is a sudden increase in bandwidth should be adjusted when there is a sudden increase in
traffic demand. This value indicates how many times, traffic demand. This value indicates how many times,
consecutively, the percentage or absolute difference between the consecutively, that the percentage or absolute difference between
current MaxAvgBw and the current bandwidth reservation of the LSP the current MaxAvgBw and the current bandwidth reservation of the
needs to be greater than or equal to the Overflow-Threshold value LSP needs to be greater than or equal to the Overflow-Threshold
in order to meet the overflow condition. value in order to meet the overflow condition.
Overflow-Threshold: This parameter is used to decide when the LSP Overflow-Threshold: This parameter is used to decide when the LSP
bandwidth should be adjusted when there is a sudden increase in bandwidth should be adjusted when there is a sudden increase in
traffic demand. If the percentage or absolute difference between traffic demand. If the percentage or absolute difference between
the current MaxAvgBw and the current bandwidth reservation of the the current MaxAvgBw and the current bandwidth reservation of the
LSP is greater than or equal to the threshold value, the overflow LSP is greater than or equal to the threshold value, the overflow
condition is said to be met. The LSP bandwidth is adjusted to the condition is said to be met. The LSP bandwidth is adjusted to the
current bandwidth demand bypassing the Up-Adjustment-Interval if current bandwidth demand, bypassing the Up-Adjustment-Interval if
the overflow condition is met consecutively for the Overflow- the overflow condition is met consecutively for the Overflow-
Count. The Overflow-Threshold needs to be greater than or equal to Count. The Overflow-Threshold needs to be greater than or equal
the Up-Adjustment-Threshold. to the Up-Adjustment-Threshold.
Underflow-Count: This parameter is used to decide when the LSP Underflow-Count: This parameter is used to decide when the LSP
bandwidth should be adjusted when there is a sudden decrease in bandwidth should be adjusted when there is a sudden decrease in
traffic demand. This value indicates how many times traffic demand. This value indicates how many times,
consecutively, the percentage or absolute difference between the consecutively, that the percentage or absolute difference between
current MaxAvgBw and the current bandwidth reservation of the LSP the current MaxAvgBw and the current bandwidth reservation of the
needs to be greater than or equal to the Underflow-Threshold value LSP needs to be greater than or equal to the Underflow-Threshold
in order to meet the underflow condition. value in order to meet the underflow condition.
Underflow-Threshold: This parameter is used to decide when the LSP Underflow-Threshold: This parameter is used to decide when the LSP
bandwidth should be adjusted when there is a sudden decrease in bandwidth should be adjusted when there is a sudden decrease in
traffic demand. If the percentage or absolute difference between traffic demand. If the percentage or absolute difference between
the current MaxAvgBw and the current bandwidth reservation of the the current MaxAvgBw and the current bandwidth reservation of the
LSP is greater than or equal to the threshold value, the underflow LSP is greater than or equal to the threshold value, the underflow
condition is said to be met. The LSP bandwidth is adjusted to the condition is said to be met. The LSP bandwidth is adjusted to the
current bandwidth demand bypassing the Down-Adjustment-Interval if current bandwidth demand, bypassing the Down-Adjustment-Interval
the underflow condition is met consecutively for the Underflow- if the underflow condition is met consecutively for the Underflow-
Count. The Underflow-Threshold needs to be greater than or equal Count. The Underflow-Threshold needs to be greater than or equal
to the Down-Adjustment-Threshold. to the Down-Adjustment-Threshold.
Minimum-Threshold: When percentage-based thresholds are in use, they Minimum-Threshold: When percentage-based thresholds are in use, they
are accompanied by this minimum threshold, which is used to are accompanied by this Minimum-Threshold, which is used to ensure
enforce that the magnitude of deviation of calculated LSP that the magnitude of deviation of the calculated LSP bandwidth to
bandwidth to be adjusted from the current bandwidth reservations be adjusted from the current bandwidth reservations exceeds a
exceeds a specific non-percentage-based criterion (represented as specific non-percentage-based criterion (represented as an
an absolute bandwidth value) before any adjustments are made. This absolute bandwidth value) before any adjustments are made. This
serves to suppress unnecessary auto-bandwidth adjustments and re- serves to suppress unnecessary auto-bandwidth adjustments and
signaling of the LSP at low bandwidth values. resignaling of the LSP at low bandwidth values.
3. Requirements for PCEP Extensions 3. Requirements for PCEP Extensions
The PCEP extensions required for auto-bandwidth are summarized in the The PCEP extensions required for auto-bandwidth are summarized in the
following table as well as in Figure 1. following table as well as in Figure 1.
+---------------------------------+---------------------------------+ +-------------------------+--------------------------------------+
| PCC Initiated | PCE Initiated | | PCC Initiated | PCE Initiated |
+---------------------------------+---------------------------------+ +=========================+======================================+
| | | | PCC monitors the | At the time of initiation, the PCE |
| PCC monitors the traffic | At the time of initiation, | | traffic and reports the | requests that the PCC monitor the |
| and reports the calculated | PCE request PCC to monitor | | calculated bandwidth to | traffic and report the calculated |
| bandwidth to be adjusted | the traffic and report the | | be adjusted to the PCE. | bandwidth to be adjusted to the PCE. |
| to the PCE. | calculated bandwidth to be | +-------------------------+--------------------------------------+
| | adjusted to the PCE. | | Extension is needed for | Extension is needed for the PCE to |
| | | | the PCC to pass on the | pass on the adjustment parameters at |
| Extension is needed for PCC | Extension is needed for PCE | | adjustment parameters | the time of LSP initiation. |
| to pass on the adjustment | to pass on the adjustment | | at the time of LSP | |
| parameters at the time of | parameters at the time of | | delegation. | |
| LSP Delegation. | LSP Initiation. | +-------------------------+--------------------------------------+
| | |
+---------------------------------+---------------------------------+
Table 1: Requirements for Auto-Bandwidth PCEP extensions Table 1: Requirements for Auto-Bandwidth PCEP Extensions
---------- ----------
| | | |
| PCE | | PCE |
| | | |
---------- ----------
| ^ | ^
AUTO-BANDWIDTH CAPABILITY | | AUTO-BANDWIDTH CAPABILITY AUTO-BANDWIDTH CAPABILITY | | AUTO-BANDWIDTH CAPABILITY
| | | |
AUTO-BANDWIDTH ATTRIBUTES | | AUTO-BANDWIDTH ATTRIBUTES AUTO-BANDWIDTH ATTRIBUTES | | AUTO-BANDWIDTH ATTRIBUTES
| | (For Delegated LSPs) | | (For Delegated LSPs)
| | | |
| | REQUESTED BANDWIDTH | | REQUESTED BANDWIDTH
v | v |
---------- ----------
| | | |
| PCC | | PCC |
| | | |
---------- ----------
Figure 1: Overview of Auto-Bandwidth PCEP extensions Figure 1: Overview of Auto-Bandwidth PCEP Extensions
A PCEP speaker supporting this document must have a mechanism to A PCEP speaker supporting this document must have a mechanism to
advertise the automatic bandwidth adjustment capability for both PCC- advertise the auto-bandwidth adjustment capability for both PCC-
Initiated and PCE-Initiated LSPs. initiated and PCE-initiated LSPs.
Auto-bandwidth deployment considerations for PCEP extensions are Auto-bandwidth deployment considerations for PCEP extensions are
summarized below: summarized below:
o It is necessary to identify and inform the PCC which LSPs have * It is necessary to identify and inform the PCC which LSPs have
enabled the Auto-Bandwidth feature. Not all LSPs in some enabled the auto-bandwidth feature. Not all LSPs in some
deployments would like their bandwidth to be dependent on the deployments would like their bandwidth to be dependent on real-
real-time bandwidth usage; for some LSPs leaving the bandwidth time bandwidth usage; for some LSPs, leaving the bandwidth
constant as set by the operator is preferred. constant as set by the operator is preferred.
o In addition, an operator should be able to specify the auto- * In addition, an operator should be able to specify the auto-
bandwidth adjustment parameters (i.e. configuration knobs) to bandwidth adjustment parameters (i.e., configuration knobs) to
control this feature (e.g. minimum/ maximum bandwidth range). The control this feature (e.g., Minimum/Maximum-Bandwidth range). The
PCC should be informed about these adjustment parameters. PCC should be informed about these adjustment parameters.
4. Architectural Overview 4. Architectural Overview
4.1. Auto-Bandwidth Overview 4.1. Auto-Bandwidth Overview
The Auto-Bandwidth feature allows automatic and dynamic adjustment of The auto-bandwidth feature allows automatic and dynamic adjustment of
the reserved bandwidth of an LSP over time (i.e., without network the reserved bandwidth of an LSP over time (i.e., without network
operator intervention) to accommodate the varying traffic demand of operator intervention) to accommodate the varying traffic demand of
the LSP. If the traffic flowing through the LSP is lower than the the LSP. If the traffic flowing through the LSP is lower than the
configured or current reserved bandwidth of the LSP, the extra configured or current reserved bandwidth of the LSP, the extra
bandwidth is being reserved needlessly and being wasted. Conversely, bandwidth is being reserved needlessly and is being wasted.
if the actual traffic flowing through the LSP is higher than the Conversely, if the actual traffic flowing through the LSP is higher
configured or current reserved bandwidth of the LSP, it can than the configured or current reserved bandwidth of the LSP, it can
potentially cause congestion or packet loss in the network. The potentially cause congestion or packet loss in the network. The
initial LSP bandwidth can be set to an arbitrary value (including initial LSP bandwidth can be set to an arbitrary value (including
zero). In practice, it can be set to an expected value based on zero). In practice, it can be set to an expected value based on
design and planning. The head-end Label Switch Router (LSR) monitors design and planning. The head-end LSR monitors the actual traffic
the actual traffic flowing through the LSP and uses that information flowing through the LSP and uses that information to adjust the
to adjust the bandwidth reservation of the LSP in the network. bandwidth reservation of the LSP in the network.
Bandwidth adjustment must not cause disruption to the traffic flow Bandwidth adjustment must not cause disruption to the traffic flow
carried by the LSP. One way to achieve this is to use the carried by the LSP. One way to achieve this is to use the make-
make-before-break signaling method [RFC3209]. before-break signaling method [RFC3209].
4.2. Auto-bandwidth Theory of Operation 4.2. Auto-Bandwidth Theory of Operation
This section describes the Auto-Bandwidth feature in a general way. This section describes the auto-bandwidth feature in a general way.
When the Auto-Bandwidth feature is enabled, the measured traffic rate When the auto-bandwidth feature is enabled, the measured traffic rate
is periodically sampled at each Sample-Interval by the PCC, when the is periodically sampled at each Sample-Interval by the PCC when the
PCC is the head-end node of the LSP. The sample interval can be PCC is the head-end node of the LSP. The Sample-Interval can be
configured by an operator, with a default value of 5 minutes. A very configured by an operator, with a default value of 5 minutes. A very
low Sample-Interval could have some undesirable interactions with low Sample-Interval could have some undesirable interactions with
transport protocols (see Section 6.6). transport protocols (see Section 6.6).
The traffic rate samples are accumulated over the Adjustment-Interval The traffic rate samples are accumulated over the Adjustment-Interval
period (in the Up or Down direction). The period can be configured period (in the Up or Down direction). The period can be configured
by an operator, with a default value of 24 hours. The PCC in-charge by an operator, with a default value of 24 hours. The PCC in charge
of calculating the bandwidth to be adjusted can decide to adjust the of calculating the bandwidth to be adjusted can decide to adjust the
bandwidth of the LSP to the highest traffic rate sample (MaxAvgBw) bandwidth of the LSP to the highest traffic rate sample (MaxAvgBw)
amongst the set of bandwidth samples collected over the amongst the set of Bandwidth-Samples collected over the Adjustment-
Adjustment-Interval period (in the Up or Down direction) depending on Interval period (in the Up or Down direction) depending on the
the operator policy. operator policy.
Note that the highest traffic rate sample could be higher or lower Note that the highest traffic rate sample could be higher or lower
than the current LSP bandwidth. Only if the difference between the than the current LSP bandwidth. The LSP is adjusted (upsized) to the
current bandwidth demand (MaxAvgBw) and the current bandwidth current bandwidth demand (MaxAvgBW) only if the difference between
reservation is greater than or equal to the Adjustment-Threshold the the current bandwidth demand (MaxAvgBw) and the current bandwidth
LSP bandwidth is adjusted (upsized) to the current bandwidth demand reservation is greater than or equal to the Adjustment-Threshold.
(MaxAvgBw). The Adjustment-Threshold could be an absolute value or a The Adjustment-Threshold could be an absolute value or a percentage.
percentage. The threshold can be configured by an operator, with a The threshold can be configured by an operator, with a default value
default value of 5 percentage. Similarly, if the difference between of 5 percent. Similarly, if the difference between the current
the current bandwidth reservation and the current bandwidth demand bandwidth reservation and the current bandwidth demand (MaxAvgBw) is
(MaxAvgBw) is greater than or equal to the Down-Adjustment-Threshold greater than or equal to the Down-Adjustment-Threshold (percentage or
(percentage or absolute value), the LSP bandwidth is adjusted absolute value), the LSP bandwidth is adjusted (downsized) to the
(downsized) to the current bandwidth demand (MaxAvgBw). Some LSPs current bandwidth demand (MaxAvgBw). Some LSPs are less eventful,
are less eventful while other LSPs may encounter a lot of changes in while other LSPs may encounter a lot of changes in the traffic
the traffic pattern. The thresholds and intervals for bandwidth pattern. The thresholds and intervals for bandwidth adjustment are
adjustment are configured based on the traffic pattern of the LSP. configured based on the traffic pattern of the LSP.
In order to avoid frequent re-signaling, an operator may set a longer In order to avoid frequent resignaling, an operator may set a longer
adjustment-interval value (Up and/or Down). However, a longer Adjustment-Interval value (Up and/or Down). However, a longer
Adjustment-Interval can result in an undesirable effect of masking Adjustment-Interval can result in the undesirable effect of masking
sudden changes in traffic demands of an LSP. To avoid this, the sudden changes in the traffic demands of an LSP. To avoid this, the
Auto-Bandwidth feature may prematurely expire the adjustment interval auto-bandwidth feature may force the Adjustment-Interval to
and adjust the LSP bandwidth to accommodate the sudden bursts of prematurely expire and adjust the LSP bandwidth to accommodate the
increase in traffic demand as an overflow condition or decrease in sudden bursts of increase in traffic demand as an overflow condition
traffic demand as an underflow condition. An operator needs to or decrease in traffic demand as an underflow condition. An operator
configure appropriate values for the Overflow-Threshold and/or needs to configure appropriate values for the Overflow-Threshold and/
Underflow-Threshold parameters and they do not have default values or Underflow-Threshold parameters, and they do not have default
defined in this document. values defined in this document.
All thresholds in this document could be represented in both absolute All thresholds in this document could be represented in both absolute
value and percentage, and could be used together. This is provided value and percentage and could be used together. This is provided to
to accommodate the cases where the LSP bandwidth reservation may accommodate cases where the LSP bandwidth reservation may become very
become very large or very small over time. For example, an operator large or very small over time. For example, an operator may use the
may use the percentage threshold to handle small to large bandwidth percentage threshold to handle small to large bandwidth values and
values and absolute values to handle very large bandwidth values. absolute values to handle very large bandwidth values. The auto-
The auto-bandwidth adjustment is made when either one of the two bandwidth adjustment is made when either one of the two thresholds,
thresholds, the absolute or percentage, is crossed. the absolute or percentage, is crossed.
When using the (adjustment/overflow/underflow) percentage thresholds, When using the (adjustment/overflow/underflow) percentage thresholds,
if the LSP bandwidth changes rapidly at very low values, it may if the LSP bandwidth changes rapidly at very low values, it may
trigger frequent auto-bandwidth adjustments due to the crossing of trigger frequent auto-bandwidth adjustments due to the crossing of
the percentage thresholds. This can lead to unnecessary re-signaling the percentage thresholds. This can lead to unnecessary resignaling
of the LSPs in the network. This is suppressed by setting the of the LSPs in the network. This is suppressed by setting the
minimum-threshold parameters along with the percentage thresholds. Minimum-Threshold parameters along with the percentage thresholds.
The auto-bandwidth adjustment is only made if the LSP bandwidth The auto-bandwidth adjustment is only made if the LSP bandwidth
crosses both the percentage threshold and the minimum-threshold crosses both the percentage threshold and the Minimum-Threshold
parameters. parameters.
4.3. Scaling Considerations 4.3. Scaling Considerations
It should be noted that any bandwidth change requires re-signaling of It should be noted that any bandwidth change requires resignaling of
an LSP, which can further trigger preemption of lower priority LSPs an LSP, which can further trigger preemption of lower-priority LSPs
in the network. When deployed under scale, this can lead to a in the network. When deployed under scale, this can lead to a
signaling churn in the network. The Auto-bandwidth application signaling churn in the network. The auto-bandwidth application
algorithm is thus advised to take this into consideration before algorithm is thus advised to take this into consideration before
adjusting the LSP bandwidth. Operators are advised to set the values adjusting the LSP bandwidth. Operators are advised to set the values
of various auto-bandwidth adjustment parameters appropriate for the of various auto-bandwidth adjustment parameters appropriate for the
deployed LSP scale. deployed LSP scale.
If a PCE gets overwhelmed, it can notify the PCC to temporarily If a PCE gets overwhelmed, it can notify the PCC to temporarily
suspend the reporting of the new LSP bandwidth to be adjusted (see suspend the reporting of the new LSP bandwidth to be adjusted.
Section 5.7 of this document). Similarly, if a PCC gets overwhelmed Similarly, if a PCC gets overwhelmed due to signaling churn, it can
due to signaling churn, it can notify the PCE to temporarily suspend notify the PCE to temporarily suspend new LSP setup requests. See
new LSP setup requests (see Section 5.7 of this document). Section 5.7 of this document.
5. PCEP Extensions 5. PCEP Extensions
5.1. Capability Advertisement 5.1. Capability Advertisement
During PCEP Initialization Phase, PCEP speakers (PCE or PCC) During the PCEP initialization phase, PCEP speakers (PCE or PCC)
advertise their support of Automatic Bandwidth adjustment feature. A advertise their support of the auto-bandwidth adjustment feature. A
PCEP speaker includes the AUTO-BANDWIDTH-CAPABILITY TLV, in the OPEN PCEP speaker includes the AUTO-BANDWIDTH-CAPABILITY TLV in the OPEN
Object to advertise its support for PCEP Auto-Bandwidth extensions. object to advertise its support for PCEP auto-bandwidth extensions.
The presence of the AUTO-BANDWIDTH-CAPABILITY TLV in the OPEN Object The presence of the AUTO-BANDWIDTH-CAPABILITY TLV in the OPEN object
indicates that the Automatic Bandwidth feature is supported as indicates that the auto-bandwidth feature is supported as described
described in this document. in this document.
o The PCEP protocol extensions for Auto-Bandwidth adjustments MUST * The PCEP protocol extensions for auto-bandwidth adjustments MUST
NOT be used if one or both PCEP speakers have not included the NOT be used if one or both PCEP speakers have not included the
AUTO-BANDWIDTH-CAPABILITY TLV in their respective OPEN message. AUTO-BANDWIDTH-CAPABILITY TLV in their respective OPEN message.
o A PCEP speaker that does not recognize the extensions defined in * A PCEP speaker that does not recognize the extensions defined in
this document would simply ignore the TLVs as per [RFC5440]. this document would simply ignore the TLVs as per [RFC5440].
o If a PCEP speaker that supports the extensions defined in this * If a PCEP speaker supports the extensions defined in this document
document but did not advertise this capability, then upon receipt but did not advertise this capability, then upon receipt of AUTO-
of AUTO-BANDWIDTH-ATTRIBUTES TLV in the LSP Attributes (LSPA) BANDWIDTH-ATTRIBUTES TLV in the LSP Attributes (LSPA) object, it
object, it SHOULD generate a PCErr with error-type 19 (Invalid SHOULD generate a PCErr with Error-Type 19 (Invalid Operation) and
Operation), error-value TBD4 (Auto-Bandwidth capability was not Error-value 14 (Auto-Bandwidth capability was not advertised) and
advertised) and ignore the AUTO-BANDWIDTH-ATTRIBUTES TLV. ignore the AUTO-BANDWIDTH-ATTRIBUTES TLV.
5.1.1. AUTO-BANDWIDTH-CAPABILITY TLV 5.1.1. AUTO-BANDWIDTH-CAPABILITY TLV
The AUTO-BANDWIDTH-CAPABILITY TLV is an optional TLV for use in the The AUTO-BANDWIDTH-CAPABILITY TLV is an optional TLV for use in the
OPEN Object for Automatic Bandwidth Adjustment via PCEP capability OPEN Object for auto-bandwidth adjustment via PCEP capability
advertisement. Its format is shown in the following figure: advertisement. Its format is shown in the following figure:
0 1 2 3 0 1 2 3
0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Type=TBD2 | Length=4 | | Type=36 | Length=4 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Flags | | Flag |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
AUTO-BANDWIDTH-CAPABILITY TLV format Figure 2: AUTO-BANDWIDTH-CAPABILITY TLV Format
The Type of the TLV is (TBD2) and it has a fixed Length of 4 octets. The TLV Type is 36, and it has a fixed Length of 4 octets.
The value comprises a single field - Flags (32 bits). No flags are The value comprises a single field: Flag (32 bits). No flags are
defined for this TLV in this document. defined for this TLV in this document.
Unassigned bits are considered reserved. They MUST be set to 0 on Unassigned bits are considered reserved. They MUST be set to 0 on
transmission and MUST be ignored on receipt. transmission and MUST be ignored on receipt.
Advertisement of the AUTO-BANDWIDTH-CAPABILITY TLV implies support of Advertisement of the AUTO-BANDWIDTH-CAPABILITY TLV implies support of
auto-bandwidth adjustment, as well as the objects, TLVs and auto-bandwidth adjustment, as well as the objects, TLVs, and
procedures defined in this document. procedures defined in this document.
5.2. AUTO-BANDWIDTH-ATTRIBUTES TLV 5.2. AUTO-BANDWIDTH-ATTRIBUTES TLV
The AUTO-BANDWIDTH-ATTRIBUTES TLV provides the 'configurable knobs' The AUTO-BANDWIDTH-ATTRIBUTES TLV provides the 'configurable knobs'
of the feature and it can be included as an optional TLV in the LSPA of the feature, and it can be included as an optional TLV in the LSPA
Object (as described in [RFC5440]). object (as described in [RFC5440]).
For PCE-Initiated LSP [RFC8281], this TLV is included in the LSPA For a PCE-initiated LSP [RFC8281], this TLV is included in the LSPA
Object with the PCInitiate message. For the PCC-Initiated delegated object with the PCInitiate message. For the PCC-initiated delegated
LSPs, this TLV is carried in the PCRpt message in LSPA Object. This LSPs, this TLV is carried in the Path Computation State Report
TLV is also carried in the LSPA object with the PCUpd message to (PCRpt) message in the LSPA object. This TLV is also carried in the
direct the PCC (LSP head-end) to make updates to auto-bandwidth LSPA object with the Path Computation Update Request (PCUpd) message
to direct the PCC (LSP head-end) to make updates to auto-bandwidth
attributes such as Adjustment-Interval. attributes such as Adjustment-Interval.
The TLV is encoded in all PCEP messages for the LSP while the auto- The TLV is encoded in all PCEP messages for the LSP while the auto-
bandwidth adjustment feature is enabled, the absence of the TLV bandwidth adjustment feature is enabled. The absence of the TLV
indicates the PCEP speaker wishes to disable the feature. This TLV indicates the PCEP speaker wishes to disable the feature. This TLV
includes multiple AUTO-BANDWIDTH-ATTRIBUTES sub-TLVs. The includes multiple AUTO-BANDWIDTH-ATTRIBUTES sub-TLVs. The AUTO-
AUTO-BANDWIDTH-ATTRIBUTES sub-TLVs are included if there is a change BANDWIDTH-ATTRIBUTES sub-TLVs are included if there is a change since
since the last information sent in the PCEP message. The default the last information sent in the PCEP message. The default values
values for missing sub-TLVs apply for the first PCEP message for the for missing sub-TLVs apply for the first PCEP message for the LSP.
LSP.
The format of the AUTO-BANDWIDTH-ATTRIBUTES TLV is shown in the The format of the AUTO-BANDWIDTH-ATTRIBUTES TLV is shown in the
following figure: following figure:
0 1 2 3 0 1 2 3
0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Type=TBD1 | Length | | Type=37 | Length |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| | | |
// sub-TLVs // // sub-TLVs //
| | | |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
AUTO-BANDWIDTH-ATTRIBUTES TLV format Figure 3: AUTO-BANDWIDTH-ATTRIBUTES TLV Format
Type: TBD1 Type: 37
Length: The Length field defines the length of the value portion Length: The Length field defines the length of the value portion in
in octets as per [RFC5440]. bytes as per [RFC5440].
Value: This comprises one or more sub-TLVs. Value: This comprises one or more sub-TLVs.
Following sub-TLVs are defined in this document: The following sub-TLVs are defined in this document:
Type Len Name +------+-----+--------------------------------------+
------------------------------------------------------------------- | Type | Len | Name |
1 4 Sample-Interval sub-TLV +======+=====+======================================+
2 4 Adjustment-Interval sub-TLV | 1 | 4 | Sample-Interval |
3 4 Down-Adjustment-Interval sub-TLV +------+-----+--------------------------------------+
4 4 Adjustment-Threshold sub-TLV | 2 | 4 | Adjustment-Interval |
5 8 Adjustment-Threshold-Percentage sub-TLV +------+-----+--------------------------------------+
6 4 Down-Adjustment-Threshold sub-TLV | 3 | 4 | Down-Adjustment-Interval |
7 8 Down-Adjustment-Threshold-Percentage sub-TLV +------+-----+--------------------------------------+
8 4 Minimum-Bandwidth sub-TLV | 4 | 4 | Adjustment-Threshold |
9 4 Maximum-Bandwidth sub-TLV +------+-----+--------------------------------------+
10 8 Overflow-Threshold sub-TLV | 5 | 8 | Adjustment-Threshold-Percentage |
11 8 Overflow-Threshold-Percentage sub-TLV +------+-----+--------------------------------------+
12 8 Underflow-Threshold sub-TLV | 6 | 4 | Down-Adjustment-Threshold |
13 8 Underflow-Threshold-Percentage sub-TLV +------+-----+--------------------------------------+
| 7 | 8 | Down-Adjustment-Threshold-Percentage |
+------+-----+--------------------------------------+
| 8 | 4 | Minimum-Bandwidth |
+------+-----+--------------------------------------+
| 9 | 4 | Maximum-Bandwidth |
+------+-----+--------------------------------------+
| 10 | 8 | Overflow-Threshold |
+------+-----+--------------------------------------+
| 11 | 8 | Overflow-Threshold-Percentage |
+------+-----+--------------------------------------+
| 12 | 8 | Underflow-Threshold |
+------+-----+--------------------------------------+
| 13 | 8 | Underflow-Threshold-Percentage |
+------+-----+--------------------------------------+
Table 2: Sub-TLV Types of the AUTO-BANDWIDTH-
ATTRIBUTES TLV
Future specifications can define additional sub-TLVs. Future specifications can define additional sub-TLVs.
The sub-TLVs are encoded to inform the PCEP peer of the various The sub-TLVs are encoded to inform the PCEP peer of the various
sampling and adjustment parameters. In case of a missing sub-TLV, as sampling and adjustment parameters. In the case of a missing sub-
per the local policy, either the default value (as specified in this TLV, as per the local policy, either the default value (as specified
document) or some other operator configured value is used. in this document) or some other operator-configured value is used.
All sub-TLVs are optional and any unrecognized sub-TLV MUST be All sub-TLVs are optional, and any unrecognized sub-TLV MUST be
ignored. If a sub-TLV of the same type appears more than once, only ignored. If a sub-TLV of the same type appears more than once, only
the first occurrence is processed and all others MUST be ignored. the first occurrence is processed, and all others MUST be ignored.
The following sub-sections describe the sub-TLVs which are currently The following subsections describe the sub-TLVs that are currently
defined to be carried within the AUTO-BANDWIDTH-ATTRIBUTES TLV. defined as being carried within the AUTO-BANDWIDTH-ATTRIBUTES TLV.
5.2.1. Sample-Interval sub-TLV 5.2.1. Sample-Interval Sub-TLV
The Sample-Interval sub-TLV specifies a time interval in seconds at The Sample-Interval sub-TLV specifies a time interval in seconds in
which traffic samples are collected at the PCC. which traffic samples are collected at the PCC.
0 1 2 3 0 1 2 3
0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Type=1 | Length=4 | | Type=1 | Length=4 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Sample-Interval | | Sample-Interval |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Sample-Interval sub-TLV format Figure 4: Sample-Interval Sub-TLV Format
The Type is 1, Length is 4 octets, and the value comprises of - The Type is 1, the Length is 4 octets, and the value comprises the
following:
o Sample-Interval: The 4-octet time interval for bandwidth sample Sample-Interval: The 4-octet time interval for the Bandwidth-Sample
collection. The valid range is from 1 to 604800 (7 days), in collection. The valid range is from 1 to 604800 (7 days), in
seconds. The default value is 300 seconds. Due care needs to be seconds. The default value is 300 seconds. Due care needs to be
taken in case of a very low Sample-Interval, as it can have some taken in a case with a very low Sample-Interval, as it can have
undesirable interactions with transport protocols (see Section some undesirable interactions with transport protocols (see
6.6). The sample-interval parameter MUST NOT be greater than the Section 6.6). The Sample-Interval parameter MUST NOT be greater
(down) adjustment-interval. In case of an invalid value, the Sub- than the (down) Adjustment-Interval. In the case in which an
TLV MUST be ignored and the previous value is maintained. invalid value is present, the sub-TLV MUST be ignored and the
previous value will be maintained.
5.2.2. Adjustment Intervals 5.2.2. Adjustment-Intervals
The sub-TLVs in this section are encoded to inform the PCEP peer the The sub-TLVs in this section are encoded to inform the PCEP peer of
adjustment interval parameters. The Adjustment-Interval sub-TLV the Adjustment-Interval parameters. The Adjustment-Interval sub-TLV
specifies the time interval for both upward (Up-Adjustment-Interval) specifies the time interval for both upward (Up-Adjustment-Interval)
and downward (Down-Adjustment-Interval) trends. An implementation MAY and downward (Down-Adjustment-Interval) trends. An implementation
require to set a different adjustment interval values for when the MAY require that a different Adjustment-Interval value be set when
bandwidth usage trend is downwards from when it is moving upwards. In the bandwidth usage trend is moving downwards from the one used when
that case, the operator could use the Down-Adjustment-Interval sub- it is moving upwards. In that case, the operator could use the Down-
TLV which overrides the Adjustment-Interval value for Down- Adjustment-Interval sub-TLV, which overrides the Adjustment-Interval
Adjustment-Interval. value for Down-Adjustment-Interval.
5.2.2.1. Adjustment-Interval sub-TLV 5.2.2.1. Adjustment-Interval Sub-TLV
The Adjustment-Interval sub-TLV specifies a time interval in seconds The Adjustment-Interval sub-TLV specifies a time interval in seconds
at which bandwidth adjustment should be made in upward or downward in which a bandwidth adjustment should be made in an upward or
direction. This sub-TLV specify the value for Up-Adjustment-Interval downward direction. This sub-TLV specifies the value for Up-
and Down-Adjustment-Interval when they are the same and the Down- Adjustment-Interval and Down-Adjustment-Interval when they are the
Adjustment-Interval sub-TLV is not included. same and when the Down-Adjustment-Interval sub-TLV is not included.
0 1 2 3 0 1 2 3
0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Type=2 | Length=4 | | Type=2 | Length=4 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Adjustment-Interval | | Adjustment-Interval |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Adjustment-Interval sub-TLV format Figure 5: Adjustment-Interval Sub-TLV Format
The Type is 2, Length is 4 octets, and the value comprises of - The Type is 2, the Length is 4 octets, and the value comprises the
following:
o Adjustment-Interval: The 4-octet time interval for bandwidth Adjustment-Interval: The 4-octet time interval for bandwidth
adjustments. The valid range is from 1 to 604800 (7 days), in adjustments. The valid range is from 1 to 604800 (7 days), in
seconds. The default value is 86400 seconds (1 day). The seconds. The default value is 86400 seconds (1 day). The
adjustment-interval parameter MUST NOT be less than the Adjustment-Interval parameter MUST NOT be less than the Sample-
sample-interval, otherwise the Sub-TLV MUST be ignored and the Interval; otherwise, the sub-TLV MUST be ignored, and the previous
previous value is maintained. value will be maintained.
5.2.2.2. Down-Adjustment-Interval sub-TLV 5.2.2.2. Down-Adjustment-Interval Sub-TLV
The Down-Adjustment-Interval sub-TLV specifies a time interval in The Down-Adjustment-Interval sub-TLV specifies a time interval in
seconds at which bandwidth adjustment should be made when MaxAvgBw is seconds in which a bandwidth adjustment should be made when MaxAvgBw
less than the current bandwidth reservation of the LSP. This is less than the current bandwidth reservation of the LSP. This
parameter overrides the Adjustment-Interval for the downward trend. parameter overrides the Adjustment-Interval for the downward trend.
This sub-TLV is used only when there is a need for different This sub-TLV is used only when there is a need for different
adjustment intervals in the upward and downward directions. Adjustment-Intervals in the upward and downward directions.
0 1 2 3 0 1 2 3
0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Type=3 | Length=4 | | Type=3 | Length=4 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Down-Adjustment-Interval | | Down-Adjustment-Interval |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Down-Adjustment-Interval sub-TLV format Figure 6: Down-Adjustment-Interval Sub-TLV Format
The Type is 3, Length is 4 octets, and the value comprises of - The Type is 3, the Length is 4 octets, and the value comprises the
following:
o Down-Adjustment-Interval: The 4-octet time interval for downward Down-Adjustment-Interval: The 4-octet time interval for downward
bandwidth adjustments. The valid range is from 1 to 604800 (7 bandwidth adjustments. The valid range is from 1 to 604800 (7
days), in seconds. The default value equals the adjustment- days), in seconds. The default value equals the Adjustment-
interval. The down-adjustment-interval parameter MUST NOT be less Interval. The Down-Adjustment-Interval parameter MUST NOT be less
than the sample-interval, otherwise the Sub-TLV MUST be ignored than the Sample-Interval; otherwise, the sub-TLV MUST be ignored
and the previous value is maintained. and the previous value will be maintained.
5.2.3. Adjustment Thresholds 5.2.3. Adjustment-Thresholds
The sub-TLVs in this section are encoded to inform the PCEP peer of The sub-TLVs in this section are encoded to inform the PCEP peer of
the adjustment threshold parameters. An implementation MAY include the Adjustment-Threshold parameters. An implementation MAY include
both sub-TLVs for the absolute value and the percentage, in which both sub-TLVs for the absolute value and the percentage, in which
case the bandwidth is adjusted when either of the adjustment case the bandwidth is adjusted when either of the Adjustment-
threshold conditions are met. The Adjustment-Threshold sub-TLV Threshold conditions are met. The Adjustment-Threshold sub-TLV
specifies the threshold for both upward (Up-Adjustment-Threshold) and specifies the threshold for both upward (Up-Adjustment-Threshold) and
downward (Down-Adjustment-Threshold) trend. If the operator would downward (Down-Adjustment-Threshold) trends. If the operator would
like to use a different adjustment threshold during the downward like to use a different Adjustment-Threshold during the downward
trend, the Down-Adjustment-Threshold sub-TLV is included. Similarly, trend, the Down-Adjustment-Threshold sub-TLV is included. Similarly,
the Adjustment-Threshold-Percentage sub-TLV specifies the threshold the Adjustment-Threshold-Percentage sub-TLV specifies the threshold
percentage for both upward and downward trend. If the operator would percentage for both upward and downward trends. If the operator
like to use a different adjustment threshold percentage during the would like to use a different Adjustment-Threshold percentage during
downward trend, the Down-Adjustment-Threshold-Percentage sub-TLV is the downward trend, the Down-Adjustment-Threshold-Percentage sub-TLV
included. It is worth noting that regardless of how the threshold is included. It is worth noting that regardless of how the
are set, the adjustment will not be made until at least one sample- thresholds are set, the adjustment will not be made until at least
interval simply because no sample will be made on which to base a one Sample-Interval has passed simply because no sample will be made
comparison with a threshold. on which to base a comparison with a threshold.
5.2.3.1. Adjustment-Threshold Sub-TLV
5.2.3.1. Adjustment-Threshold sub-TLV
The Adjustment-Threshold sub-TLV is used to decide when the LSP The Adjustment-Threshold sub-TLV is used to decide when the LSP
bandwidth should be adjusted in upward or downward direction. This bandwidth should be adjusted in an upward or downward direction.
sub-TLV specify the absolute value for Up-Adjustment-Threshold and This sub-TLV specifies the absolute value for Up-Adjustment-Threshold
Down-Adjustment-Threshold when they are the same and the Down- and Down-Adjustment-Threshold when they are the same and when the
Adjustment-Threshold sub-TLV is not included. Down-Adjustment-Threshold sub-TLV is not included.
0 1 2 3 0 1 2 3
0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Type=4 | Length=4 | | Type=4 | Length=4 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Adjustment-Threshold | | Adjustment-Threshold |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Adjustment-Threshold sub-TLV format Figure 7: Adjustment-Threshold Sub-TLV Format
The Type is 4, Length is 4 octets, and the value comprises of - The Type is 4, the Length is 4 octets, and the value comprises the
following:
o Adjustment-Threshold: The absolute Adjustment-Threshold bandwidth Adjustment-Threshold: The absolute Adjustment-Threshold bandwidth
difference value, encoded in IEEE floating point format (see difference value, encoded in IEEE floating point format (see
[IEEE.754.1985]), expressed in bytes per second. The default [IEEE.754.1985]) and expressed in bytes per second. The default
adjustment-threshold value is not set. Refer to Section 3.1.2 of Adjustment-Threshold value is not set. Refer to Section 3.1.2 of
[RFC3471] for a table of commonly used values. [RFC3471] for a table of commonly used values.
If the modulus of difference between the current MaxAvgBw and the If the modulus of difference between the current MaxAvgBw and the
current bandwidth reservation is greater than or equal to the current bandwidth reservation is greater than or equal to the
threshold value, the LSP bandwidth is adjusted to the current threshold value, the LSP bandwidth is adjusted to the current
bandwidth demand (MaxAvgBw). bandwidth demand (MaxAvgBw).
In case of an invalid value, the Sub-TLV MUST be ignored and the In the case in which an invalid value is present, the sub-TLV MUST be
previous value is maintained. ignored and the previous value will be maintained.
5.2.3.2. Adjustment-Threshold-Percentage sub-TLV 5.2.3.2. Adjustment-Threshold-Percentage Sub-TLV
The Adjustment-Threshold-Percentage sub-TLV is used to decide when The Adjustment-Threshold-Percentage sub-TLV is used to decide when
the LSP bandwidth should be adjusted in upward or downward direction. the LSP bandwidth should be adjusted in an upward or downward
This sub-TLV specify the percentage value for Up-Adjustment-Threshold direction. This sub-TLV specifies the percentage value for Up-
and Down-Adjustment-Threshold when they are the same and the Down- Adjustment-Threshold and Down-Adjustment-Threshold when they are the
Adjustment-Threshold-Percentage sub-TLV is not included. same and when the Down-Adjustment-Threshold-Percentage sub-TLV is not
included.
0 1 2 3 0 1 2 3
0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Type=5 | Length=8 | | Type=5 | Length=8 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Reserved | Percentage | | Reserved | Percentage |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Minimum-Threshold | | Minimum-Threshold |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Adjustment-Threshold-Percentage sub-TLV format Figure 8: Adjustment-Threshold-Percentage Sub-TLV Format
The Type is 5, Length is 8 octets, and the value comprises of - The Type is 5, the Length is 8 octets, and the value comprises the
following:
o Reserved: MUST be set to zero on transmission and MUST be ignored Reserved: MUST be set to zero on transmission and MUST be ignored on
on receipt. receipt.
o Percentage: The Adjustment-Threshold value (7 bits), encoded in Percentage: The Adjustment-Threshold value (7 bits), encoded in a
percentage (an integer from 1 to 100). The value 0 is considered percentage (an integer from 1 to 100). The value 0 is considered
to be invalid. The default value is 5 percent. to be invalid. The default value is 5 percent.
o Minimum-Threshold: The absolute Minimum-Threshold bandwidth value, Minimum-Threshold: The absolute Minimum-Threshold bandwidth value,
encoded in IEEE floating point format (see [IEEE.754.1985]), encoded in IEEE floating point format (see [IEEE.754.1985]) and
expressed in bytes per second. The increase or decrease of the expressed in bytes per second. The increase or decrease of the
LSP bandwidth MUST be at least or above the minimum-threshold LSP bandwidth MUST be at or above the Minimum-Threshold before the
before the bandwidth adjustment is made. The default value is 0. bandwidth adjustment is made. The default value is 0.
If the percentage absolute difference between the current MaxAvgBw If the percentage absolute difference between the current MaxAvgBw
and the current bandwidth reservation is greater than or equal to the and the current bandwidth reservation is greater than or equal to the
threshold percentage, and the difference in the bandwidth is at least threshold percentage and the difference in the bandwidth is at or
or above the Minimum-Threshold, the LSP bandwidth is adjusted to the above the Minimum-Threshold, the LSP bandwidth is adjusted to the
current bandwidth demand (MaxAvgBw). current bandwidth demand (MaxAvgBw).
In case of an invalid value, the Sub-TLV MUST be ignored and the In the case in which an invalid value is present, the sub-TLV MUST be
previous value is maintained. ignored and the previous value will be maintained.
5.2.3.3. Down-Adjustment-Threshold sub-TLV 5.2.3.3. Down-Adjustment-Threshold Sub-TLV
The Down-Adjustment-Threshold sub-TLV is used to decide when the LSP The Down-Adjustment-Threshold sub-TLV is used to decide when the LSP
bandwidth should be adjusted when MaxAvgBw is lesser than the current bandwidth should be adjusted when MaxAvgBw is less than the current
bandwidth reservation. This parameter overrides the Adjustment- bandwidth reservation. This parameter overrides the Adjustment-
Threshold for the downward trend. This sub-TLV is used only when Threshold for the downward trend. This sub-TLV is used only when
there is a need for different threshold in the upward and downward there is a need for a different threshold in the upward and downward
directions. directions.
0 1 2 3 0 1 2 3
0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Type=6 | Length=4 | | Type=6 | Length=4 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Down-Adjustment-Threshold | | Down-Adjustment-Threshold |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Down-Adjustment-Threshold sub-TLV format Figure 9: Down-Adjustment-Threshold Sub-TLV Format
The Type is 6, Length is 4 octets, and the value comprises of - The Type is 6, the Length is 4 octets, and the value comprises the
o Down-Adjustment-Threshold: The absolute Down-Adjustment-Threshold following:
Down-Adjustment-Threshold: The absolute Down-Adjustment-Threshold
bandwidth value, encoded in IEEE floating point format (see bandwidth value, encoded in IEEE floating point format (see
[IEEE.754.1985]), expressed in bytes per second. The default [IEEE.754.1985]) and expressed in bytes per second. The default
value equals the adjustment-threshold. Refer to Section 3.1.2 of value equals the Adjustment-Threshold. Refer to Section 3.1.2 of
[RFC3471] for a table of commonly used values. [RFC3471] for a table of commonly used values.
If the difference between current bandwidth reservation and the If the difference between the current bandwidth reservation and the
current MaxAvgBw is greater than or equal to the threshold value, the current MaxAvgBw is greater than or equal to the threshold value, the
LSP bandwidth is adjusted to the current bandwidth demand (MaxAvgBw). LSP bandwidth is adjusted to the current bandwidth demand (MaxAvgBw).
In case of an invalid value, the Sub-TLV MUST be ignored and the In the case in which an invalid value is present, the sub-TLV MUST be
previous value is maintained. ignored and the previous value will be maintained.
5.2.3.4. Down-Adjustment-Threshold-Percentage sub-TLV 5.2.3.4. Down-Adjustment-Threshold-Percentage Sub-TLV
The Down-Adjustment-Threshold-Percentage sub-TLV is used to decide The Down-Adjustment-Threshold-Percentage sub-TLV is used to decide
when the LSP bandwidth should be adjusted when MaxAvgBw is lesser when the LSP bandwidth should be adjusted when MaxAvgBw is less than
than the current bandwidth reservation. This parameter overrides the the current bandwidth reservation. This parameter overrides the
Adjustment-Threshold-Percentage for the downward trend. This sub-TLV Adjustment-Threshold-Percentage for the downward trend. This sub-TLV
is used only when there is a need for different threshold percentage is used only when there is a need for a different threshold
in the upward and downward directions. percentage in the upward and downward directions.
0 1 2 3 0 1 2 3
0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Type=7 | Length=8 | | Type=7 | Length=8 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Reserved | Percentage | | Reserved | Percentage |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Minimum-Threshold | | Minimum-Threshold |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Down-Adjustment-Threshold-Percentage sub-TLV format Figure 10: Down-Adjustment-Threshold-Percentage Sub-TLV Format
The Type is 7, Length is 8 octets, and the value comprises of - The Type is 7, the Length is 8 octets, and the value comprises the
following:
o Reserved: MUST be set to zero on transmission and MUST be ignored Reserved: MUST be set to zero on transmission and MUST be ignored on
on receipt. receipt.
o Percentage: The Down-Adjustment-Threshold value (7 bits), encoded Percentage: The Down-Adjustment-Threshold value (7 bits), encoded in
in percentage (an integer from 1 to 100). The value 0 is a percentage (an integer from 1 to 100). The value 0 is
considered to be invalid. The default value equals the considered to be invalid. The default value equals the
adjustment-threshold-percentage. Adjustment-Threshold-Percentage.
o Minimum-Threshold: The absolute Minimum-Threshold bandwidth value, Minimum-Threshold: The absolute Minimum-Threshold bandwidth value,
encoded in IEEE floating point format (see [IEEE.754.1985]), encoded in IEEE floating point format (see [IEEE.754.1985]) and
expressed in bytes per second. The decrease of the LSP bandwidth expressed in bytes per second. The decrease of the LSP bandwidth
MUST be at least or above the minimum-threshold before the MUST be at or above the Minimum-Threshold before the bandwidth
bandwidth adjustment is made. The default value equals the adjustment is made. The default value equals the Minimum-
minimum-threshold for the adjustment-threshold-percentage. Threshold for the Adjustment-Threshold-Percentage.
If the percentage difference between the current bandwidth If the percentage difference between the current bandwidth
reservation and the current MaxAvgBw is greater than or equal to the reservation and the current MaxAvgBw is greater than or equal to the
threshold percentage, and the difference in the bandwidth is at least threshold percentage and the difference in the bandwidth is at or
or above the Minimum-Threshold, the LSP bandwidth is adjusted to the above the Minimum-Threshold, the LSP bandwidth is adjusted to the
current bandwidth demand (MaxAvgBw). current bandwidth demand (MaxAvgBw).
In case of an invalid value, the Sub-TLV MUST be ignored and the In the case in which an invalid value is present, the sub-TLV MUST be
previous value is maintained. ignored and the previous value will be maintained.
5.2.4. Minimum and Maximum Bandwidth Values 5.2.4. Minimum and Maximum-Bandwidth Values
5.2.4.1. Minimum-Bandwidth sub-TLV 5.2.4.1. Minimum-Bandwidth Sub-TLV
The Minimum-Bandwidth sub-TLV specify the minimum bandwidth allowed The Minimum-Bandwidth sub-TLV specifies the Minimum-Bandwidth allowed
for the LSP, and is expressed in bytes per second. The LSP bandwidth for the LSP and is expressed in bytes per second. The LSP bandwidth
cannot be adjusted below the minimum bandwidth value. cannot be adjusted below the Minimum-Bandwidth value.
0 1 2 3 0 1 2 3
0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Type=8 | Length=4 | | Type=8 | Length=4 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Minimum-Bandwidth | | Minimum-Bandwidth |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Minimum-Bandwidth sub-TLV format Figure 11: Minimum-Bandwidth Sub-TLV Format
The Type is 8, Length is 4 octets, and the value comprises of - The Type is 8, the Length is 4 octets, and the value comprises the
following:
o Minimum-Bandwidth: The 4-octet bandwidth value encoded in IEEE Minimum-Bandwidth: The 4-octet bandwidth value encoded in IEEE
floating point format (see [IEEE.754.1985]), expressed in bytes floating point format (see [IEEE.754.1985]) and expressed in bytes
per second. The default minimum-bandwidth value is set to 0. per second. The default Minimum-Bandwidth value is set to 0.
Refer to Section 3.1.2 of [RFC3471] for a table of commonly used Refer to Section 3.1.2 of [RFC3471] for a table of commonly used
values. values.
In case of an invalid value, the Sub-TLV MUST be ignored and the In the case in which an invalid value is present, the sub-TLV MUST be
previous value is maintained. ignored and the previous value will be maintained.
5.2.4.2. Maximum-Bandwidth sub-TLV 5.2.4.2. Maximum-Bandwidth Sub-TLV
The Maximum-Bandwidth sub-TLV specify the maximum bandwidth allowed The Maximum-Bandwidth sub-TLV specifies the Maximum-Bandwidth allowed
for the LSP, and is expressed in bytes per second. The LSP bandwidth for the LSP and is expressed in bytes per second. The LSP bandwidth
cannot be adjusted above the maximum bandwidth value. cannot be adjusted above the Maximum-Bandwidth value.
0 1 2 3 0 1 2 3
0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Type=9 | Length=4 | | Type=9 | Length=4 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Maximum-Bandwidth | | Maximum-Bandwidth |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Maximum-Bandwidth sub-TLV format Figure 12: Maximum-Bandwidth Sub-TLV Format
The Type is 9, Length is 4 octets, and the value comprises of - The Type is 9, the Length is 4 octets, and the value comprises the
following:
o Maximum-Bandwidth: The 4-octet bandwidth value encoded in IEEE Maximum-Bandwidth: The 4-octet bandwidth value encoded in IEEE
floating point format (see [IEEE.754.1985]), expressed in bytes floating point format (see [IEEE.754.1985]) and expressed in bytes
per second. The default maximum-bandwidth value is not set. per second. The default Maximum-Bandwidth value is not set.
Refer to Section 3.1.2 of [RFC3471] for a table of commonly used Refer to Section 3.1.2 of [RFC3471] for a table of commonly used
values. values.
In case of an invalid value, the Sub-TLV MUST be ignored and the In the case in which an invalid value is present, the sub-TLV MUST be
previous value is maintained. ignored and the previous value will be maintained.
5.2.5. Overflow and Underflow Conditions 5.2.5. Overflow and Underflow Conditions
The sub-TLVs in this section are encoded to inform the PCEP peer the The sub-TLVs in this section are encoded to inform the PCEP peer of
overflow and underflow threshold parameters. An implementation MAY the overflow and underflow threshold parameters. An implementation
include sub-TLVs for an absolute value and/or a percentage for the MAY include sub-TLVs for an absolute value and/or a percentage for
threshold, in which case the bandwidth is immediately adjusted when the threshold, in which case the bandwidth is immediately adjusted
either of the threshold conditions is met consecutively for the given when either of the threshold conditions is met consecutively for the
count (as long as the difference in the bandwidth is at least or given count (as long as the difference in the bandwidth is at or
above the Minimum-Threshold). By default, the threshold values for above the Minimum-Threshold). By default, the threshold values for
overflow and underflow conditions are not set. overflow and underflow conditions are not set.
5.2.5.1. Overflow-Threshold sub-TLV 5.2.5.1. Overflow-Threshold Sub-TLV
The Overflow-Threshold sub-TLV is used to decide if the LSP bandwidth The Overflow-Threshold sub-TLV is used to decide if the LSP bandwidth
should be adjusted immediately. should be adjusted immediately.
0 1 2 3 0 1 2 3
0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Type=10 | Length=8 | | Type=10 | Length=8 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Reserved | Count | | Reserved | Count |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Overflow-Threshold | | Overflow-Threshold |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Overflow-Threshold sub-TLV format Figure 13: Overflow-Threshold Sub-TLV Format
The Type is 10, Length is 8 octets, and the value comprises of - The Type is 10, the Length is 8 octets, and the value comprises the
following:
o Reserved: MUST be set to zero on transmission and MUST be ignored Reserved: MUST be set to zero on transmission and MUST be ignored on
on receipt. receipt.
o Count: The Overflow-Count value (5 bits), encoded in integer. The Count: The Overflow-Count value (5 bits), encoded in an integer.
value 0 is considered to be invalid. The number of consecutive The value 0 is considered to be invalid. The number of
samples for which the overflow condition MUST be met for the LSP consecutive samples for which the overflow condition MUST be met
bandwidth to be immediately adjusted to the current bandwidth for the LSP bandwidth is to be immediately adjusted to the current
demand, bypassing the (up) adjustment-interval. bandwidth demand, bypassing the (up) Adjustment-Interval.
o Overflow-Threshold: The absolute Overflow-Threshold bandwidth Overflow-Threshold: The absolute Overflow-Threshold bandwidth value,
value, encoded in IEEE floating point format (see encoded in IEEE floating point format (see [IEEE.754.1985]) and
[IEEE.754.1985]), expressed in bytes per second. Refer to Section expressed in bytes per second. Refer to Section 3.1.2 of
3.1.2 of [RFC3471] for a table of commonly used values. If the [RFC3471] for a table of commonly used values. If the difference
difference of the current MaxAvgBw from the current bandwidth between the current MaxAvgBw and the current bandwidth reservation
reservation is greater than or equal to the threshold value, the is greater than or equal to the threshold value, the overflow
overflow condition is met. condition is met.
In case of an invalid value, the Sub-TLV MUST be ignored and the In the case in which an invalid value is present, the sub-TLV MUST be
previous value is maintained. ignored and the previous value will be maintained.
5.2.5.2. Overflow-Threshold-Percentage sub-TLV 5.2.5.2. Overflow-Threshold-Percentage Sub-TLV
The Overflow-Threshold-Percentage sub-TLV is used to decide if the The Overflow-Threshold-Percentage sub-TLV is used to decide if the
LSP bandwidth should be adjusted immediately. LSP bandwidth should be adjusted immediately.
0 1 2 3 0 1 2 3
0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Type=11 | Length=8 | | Type=11 | Length=8 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Percentage | Reserved | Count | | Percentage | Reserved | Count |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Minimum-Threshold | | Minimum-Threshold |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Overflow-Threshold-Percentage sub-TLV format Figure 14: Overflow-Threshold-Percentage Sub-TLV Format
The Type is 11, Length is 8 octets, and the value comprises of - The Type is 11, the Length is 8 octets, and the value comprises the
following:
o Percentage: The Overflow-Threshold value (7 bits), encoded in Percentage: The Overflow-Threshold value (7 bits), encoded in a
percentage (an integer from 1 to 100). The value 0 is considered percentage (an integer from 1 to 100). The value 0 is considered
to be invalid. If the percentage increase of the current MaxAvgBw to be invalid. If the percentage increase of the current MaxAvgBw
from the current bandwidth reservation is greater than or equal to from the current bandwidth reservation is greater than or equal to
the threshold percentage, the overflow condition is met. the threshold percentage, the overflow condition is met.
o Reserved: MUST be set to zero on transmission and MUST be ignored Reserved: MUST be set to zero on transmission and MUST be ignored on
on receipt. receipt.
o Count: The Overflow-Count value (5 bits), encoded in integer. The Count: The Overflow-Count value (5 bits), encoded in an integer.
value 0 is considered to be invalid. The number of consecutive The value 0 is considered to be invalid. The number of
samples for which the overflow condition MUST be met for the LSP consecutive samples for which the overflow condition MUST be met
bandwidth to be immediately adjusted to the current bandwidth for the LSP bandwidth is to be immediately adjusted to the current
demand, bypassing the (up) adjustment-interval. bandwidth demand, bypassing the (up) Adjustment-Interval.
o Minimum-Threshold: The absolute Minimum-Threshold bandwidth value, Minimum-Threshold: The absolute Minimum-Threshold bandwidth value,
encoded in IEEE floating point format (see [IEEE.754.1985]), encoded in IEEE floating point format (see [IEEE.754.1985]) and
expressed in bytes per second. The increase of the LSP bandwidth expressed in bytes per second. The increase of the LSP bandwidth
MUST be at least or above the minimum-threshold before the MUST be at or above the Minimum-Threshold before the bandwidth
bandwidth adjustment is made. adjustment is made.
In case of an invalid value, the Sub-TLV MUST be ignored and the In the case in which an invalid value is present, the sub-TLV MUST be
previous value is maintained. ignored and the previous value will be maintained.
5.2.5.3. Underflow-Threshold sub-TLV 5.2.5.3. Underflow-Threshold Sub-TLV
The Underflow-Threshold sub-TLV is used to decide if the LSP The Underflow-Threshold sub-TLV is used to decide if the LSP
bandwidth should be adjusted immediately. bandwidth should be adjusted immediately.
0 1 2 3 0 1 2 3
0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Type=12 | Length=8 | | Type=12 | Length=8 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Reserved | Count | | Reserved | Count |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Underflow-Threshold | | Underflow-Threshold |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Underflow-Threshold sub-TLV format Figure 15: Underflow-Threshold Sub-TLV Format
The Type is 12, Length is 8 octets, and the value comprises of - The Type is 12, the Length is 8 octets, and the value comprises the
following:
o Reserved: MUST be set to zero on transmission and MUST be ignored Reserved: MUST be set to zero on transmission and MUST be ignored on
on receipt. receipt.
o Count: The Underflow-Count value (5 bits), encoded in integer. Count: The Underflow-Count value (5 bits), encoded in an integer.
The value 0 is considered to be invalid. The number of The value 0 is considered to be invalid. The number of
consecutive samples for which the underflow condition MUST be met consecutive samples for which the underflow condition MUST be met
for the LSP bandwidth to be immediately adjusted to the current for the LSP bandwidth is to be immediately adjusted to the current
bandwidth demand, bypassing the down-adjustment-interval. bandwidth demand, bypassing the Down-Adjustment-Interval.
o Underflow-Threshold: The absolute Underflow-Threshold bandwidth Underflow-Threshold: The absolute Underflow-Threshold bandwidth
value, encoded in IEEE floating point format (see value, encoded in IEEE floating point format (see [IEEE.754.1985])
[IEEE.754.1985]), expressed in bytes per second. Refer to Section and expressed in bytes per second. Refer to Section 3.1.2 of
3.1.2 of [RFC3471] for a table of commonly used values. If the [RFC3471] for a table of commonly used values. If the difference
difference of the current MaxAvgBw from the current bandwidth between the current MaxAvgBw and the current bandwidth reservation
reservation is greater than or equal to the threshold value, the is greater than or equal to the threshold value, the underflow
underflow condition is met. condition is met.
In case of an invalid value, the Sub-TLV MUST be ignored and the In the case in which an invalid value is present, the sub-TLV MUST be
previous value is maintained. ignored and the previous value will be maintained.
5.2.5.4. Underflow-Threshold-Percentage sub-TLV 5.2.5.4. Underflow-Threshold-Percentage Sub-TLV
The Underflow-Threshold-Percentage sub-TLV is used to decide if the The Underflow-Threshold-Percentage sub-TLV is used to decide if the
LSP bandwidth should be adjusted immediately. LSP bandwidth should be adjusted immediately.
0 1 2 3 0 1 2 3
0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Type=13 | Length=8 | | Type=13 | Length=8 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Percentage | Reserved | Count | | Percentage | Reserved | Count |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Minimum-Threshold | | Minimum-Threshold |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Underflow-Threshold-Percentage sub-TLV format Figure 16: Underflow-Threshold-Percentage Sub-TLV Format
The Type is 13, Length is 8 octets, and the value comprises of - The Type is 13, the Length is 8 octets, and the value comprises the
following:
o Percentage: The Underflow-Threshold value (7 bits), encoded in Percentage: The Underflow-Threshold value (7 bits), encoded in
percentage (an integer from 1 to 100). The value 0 is considered percentage (an integer from 1 to 100). The value 0 is considered
to be invalid. If the percentage decrease of the current MaxAvgBw to be invalid. If the percentage decrease of the current MaxAvgBw
from the current bandwidth reservation is greater than or equal to from the current bandwidth reservation is greater than or equal to
the threshold percentage, the underflow condition is met. the threshold percentage, the underflow condition is met.
o Reserved: MUST be set to zero on transmission and MUST be ignored Reserved: MUST be set to zero on transmission and MUST be ignored on
on receipt. receipt.
o Count: The Underflow-Count value (5 bits), encoded in integer. Count: The Underflow-Count value (5 bits), encoded in an integer.
The value 0 is considered to be invalid. The number of The value 0 is considered to be invalid. The number of
consecutive samples for which the underflow condition MUST be met consecutive samples for which the underflow condition MUST be met
for the LSP bandwidth to be immediately adjusted to the current for the LSP bandwidth is to be immediately adjusted to the current
bandwidth demand, bypassing the down-adjustment-interval. bandwidth demand, bypassing the Down-Adjustment-Interval.
o Minimum-Threshold: The absolute Minimum-Threshold bandwidth value, Minimum-Threshold: The absolute Minimum-Threshold bandwidth value,
encoded in IEEE floating point format (see [IEEE.754.1985]), encoded in IEEE floating point format (see [IEEE.754.1985]) and
expressed in bytes per second. The decrease of the LSP bandwidth expressed in bytes per second. The decrease of the LSP bandwidth
MUST be at least or above the minimum-threshold before the MUST be at or above the Minimum-Threshold before the bandwidth
bandwidth adjustment is made. adjustment is made.
In case of an invalid value, the Sub-TLV MUST be ignored and the In the case in which an invalid value is present, the sub-TLV MUST be
previous value is maintained. ignored and the previous value will be maintained.
5.3. BANDWIDTH Object 5.3. BANDWIDTH Object
As per [RFC5440], the BANDWIDTH object (Object-Class value 5) is As per [RFC5440], the BANDWIDTH object (Object-Class value 5) is
defined with two Object-Type values as following: defined with two Object-Type values as follows:
o Requested Bandwidth: BANDWIDTH Object-Type value is 1. Requested Bandwidth: The BANDWIDTH Object-Type value is 1.
o Re-optimization Bandwidth: Bandwidth of an existing TE LSP for Reoptimization Bandwidth: The bandwidth of an existing TE LSP for
which a re-optimization is requested. BANDWIDTH Object-Type value which a reoptimization is requested. The BANDWIDTH Object-Type
is 2. value is 2.
The PCC reports the calculated bandwidth to be adjusted (MaxAvgBw) to The PCC reports the calculated bandwidth to be adjusted (MaxAvgBw) to
the Stateful PCE using the existing 'Requested Bandwidth' with the stateful PCE using the existing 'Requested Bandwidth' with the
BANDWIDTH Object-Type as 1. The reporting of the 're-optimization BANDWIDTH Object-Type as 1. The reporting of the 'reoptimization
bandwidth' with BANDWIDTH Object-Type as 2 is not required as the bandwidth' with BANDWIDTH Object-Type as 2 is not required as the
Stateful PCE is aware of the existing LSP bandwidth. stateful PCE is aware of the existing LSP bandwidth.
5.4. The PCInitiate Message 5.4. The PCInitiate Message
A PCInitiate message is a PCEP message sent by a PCE to a PCC to A PCInitiate message is a PCEP message sent by a PCE to a PCC to
trigger LSP instantiation or deletion [RFC8281]. trigger LSP instantiation or deletion [RFC8281].
For the PCE-Initiated LSP with Auto-Bandwidth feature enabled, AUTO- For the PCE-initiated LSP with the auto-bandwidth feature enabled,
BANDWIDTH-ATTRIBUTES TLV MUST be included in the LSPA object with the AUTO-BANDWIDTH-ATTRIBUTES TLV MUST be included in the LSPA object
PCInitiate message. with the PCInitiate message.
The Routing Backus-Naur Format (RBNF) definition of the PCInitiate The Routing Backus-Naur Form (RBNF) definition of the PCInitiate
message [RFC8281] is unchanged by this document. message [RFC8281] is unchanged by this document.
5.5. The PCUpd Message 5.5. The PCUpd Message
A PCUpd message is a PCEP message sent by a PCE to a PCC to update A PCUpd message is a PCEP message sent by a PCE to a PCC to update
the LSP parameters [RFC8231]. the LSP parameters [RFC8231].
For PCE-Initiated LSPs with Auto-Bandwidth feature enabled, AUTO- For PCE-initiated LSPs with the auto-bandwidth feature enabled, the
BANDWIDTH-ATTRIBUTES TLV MUST be included in the LSPA object with the AUTO-BANDWIDTH-ATTRIBUTES TLV MUST be included in the LSPA object
PCUpd message. The PCE can send this TLV to direct the PCC to change with the PCUpd message. The PCE can send this TLV to direct the PCC
the auto-bandwidth parameters. to change the auto-bandwidth parameters.
The RBNF definition of the PCUpd message [RFC8231] is unchanged by The RBNF definition of the PCUpd message [RFC8231] is unchanged by
this document. this document.
5.6. The PCRpt Message 5.6. The PCRpt Message
The PCRpt message [RFC8231] is a PCEP message sent by a PCC to a PCE The PCRpt message [RFC8231] is a PCEP message sent by a PCC to a PCE
to report the status of one or more LSPs. to report the status of one or more LSPs.
For PCE-Initiated LSPs [RFC8281], the PCC creates the LSP using the For PCE-initiated LSPs [RFC8281], the PCC creates the LSP using the
attributes communicated by the PCE, and using the local values for attributes communicated by the PCE and the local values for the
the unspecified parameters. After the successful instantiation of unspecified parameters. After the successful instantiation of the
the LSP, PCC automatically delegates the LSP to the PCE and generates LSP, the PCC automatically delegates the LSP to the PCE and generates
a PCRpt message to provide the status report for the LSP. a PCRpt message to provide the status report for the LSP.
For both PCE-Initiated and PCC-Initiated LSPs, when the LSP is For both PCE-initiated and PCC-initiated LSPs, when the LSP is
delegated to a PCE for the very first time as well as after the delegated to a PCE for the very first time as well as after the
successful delegation, the BANDWIDTH object of type 1 is used to successful delegation, the BANDWIDTH object of type 1 is used to
specify the requested bandwidth in the PCRpt message. specify the requested bandwidth in the PCRpt message.
The RBNF definition of the PCRpt message [RFC8231] is unchanged by The RBNF definition of the PCRpt message [RFC8231] is unchanged by
this document. this document.
5.7. The PCNtf Message 5.7. The PCNtf Message
As per [RFC5440], the PCEP Notification message (PCNtf) can be sent As per [RFC5440], the PCEP Notification message (PCNtf) can be sent
by a PCEP speaker to notify its peer of a specific event. by a PCEP speaker to notify its peer of a specific event.
A PCEP speaker (PCE or PCC) SHOULD notify its PCEP peer (PCC or PCE) A PCEP speaker (PCE or PCC) SHOULD notify its PCEP peer (PCC or PCE)
when it is in overwhelmed state due to the auto-bandwidth feature. when it is in an overwhelmed state due to the auto-bandwidth feature.
An implementation needs to make an attempt to send this notification An implementation needs to make an attempt to send this notification
(when overwhelmed by auto-bandwidth adjustments) unless sending this (when overwhelmed by auto-bandwidth adjustments) unless sending this
notification would only serve to increase the load further. Note that notification would only serve to increase the load further. Note
when the notification is not received the PCEP speaker would continue that when the notification is not received, the PCEP speaker would
to request bandwidth adjustments even when they could not be handled continue to request bandwidth adjustments even when they cannot be
in a timely fashion. handled in a timely fashion.
Upon receipt of auto-bandwidth overwhelm notification, the peer Upon receipt of an auto-bandwidth overwhelm notification, the peer
SHOULD NOT send any PCEP messages related to auto-bandwidth SHOULD NOT send any PCEP messages related to auto-bandwidth
adjustment. If a PCEP message related to auto-bandwidth adjustment adjustment. If a PCEP message related to auto-bandwidth adjustment
is received during in overwhelmed state, it MUST be ignored. is received while in an overwhelmed state, it MUST be ignored.
o When a PCEP speaker is overwhelmed, it SHOULD notify its peer by * When a PCEP speaker is overwhelmed, it SHOULD notify its peer by
sending a PCNtf message with Notification-Type = TBD3 (Auto- sending a PCNtf message with Notification-type = 5 (Auto-Bandwidth
bandwidth Overwhelm State) and Notification-Value = 1 (Entering Overwhelm State) and Notification-value = 1 (Entering Auto-
auto-bandwidth overwhelm state). Optionally, OVERLOADED-DURATION Bandwidth Overwhelm State). Optionally, an OVERLOADED-DURATION
TLV [RFC5440] MAY be included that specifies the time period TLV [RFC5440] MAY be included to specify the time period during
during which no further PCEP messages related to auto-bandwidth which no further PCEP messages related to auto-bandwidth
adjustment should be sent. adjustment should be sent.
o When the PCEP speaker is no longer in the overwhelm state and is * When the PCEP speaker is no longer in the overwhelm state and is
available to process the auto-bandwidth adjustments, it SHOULD available to process the auto-bandwidth adjustments, it SHOULD
notify its peers by sending a PCNtf message with Notification Type notify its peers by sending a PCNtf message with Notification-type
= TBD3 (Auto-bandwidth Overwhelm State) and Notification Value = 2 = 5 (Auto-Bandwidth Overwhelm State) and Notification-value = 2
(Clearing auto-bandwidth overwhelm state). A PCEP speaker SHOULD (Clearing Auto-Bandwidth Overwhelm State). A PCEP speaker SHOULD
send such notification to all peers to with a Notification message send such notification to all peers if a Notification message
(Notification-Type=TBD3, Notification-Value=1) was sent earlier (Notification-type = 5, Notification-value = 1) was sent earlier.
unless an OVERLOADED-DURATION TLV was included and the PCEP This message is not sent if an OVERLOADED-DURATION TLV was
speakers wishes for the peer to wait for the expiration of that included and the PCEP speakers wishes for the peer to wait for the
period of time before receiving further PCEP messages related to expiration of that period of time before receiving further PCEP
auto-bandwidth adjustment. messages related to auto-bandwidth adjustment.
When Auto-Bandwidth feature is deployed, a PCE can send this When the auto-bandwidth feature is deployed, a PCE can send this
notification to PCC when a PCC is reporting frequent auto-bandwidth notification to a PCC when it reports frequent auto-bandwidth
adjustments. If a PCC is overwhelmed with re-signaling, it can also adjustments. If a PCC is overwhelmed with resignaling, it can also
notify the PCE to not adjust the LSP bandwidth while in overwhelm notify the PCE to not adjust the LSP bandwidth while in the overwhelm
state. state.
Some dampening notification procedure (as per [RFC5440]) to avoid Some dampening notification procedure (as per [RFC5440]) to avoid
oscillations of the overwhelm state is RECOMMENDED. On receipt of an oscillations of the overwhelm state is RECOMMENDED. On receipt of an
auto-bandwidth overwhelm notification from the PCE, a PCC should auto-bandwidth overwhelm notification from the PCE, a PCC should
consider the impact on the entire network. Moving the delegations of consider the impact on the entire network. Moving the delegations of
auto-bandwidth enabled LSP to another PCE could cause further auto-bandwidth-enabled LSPs to another PCE could cause further
overloading. overloading.
6. Manageability Considerations 6. Manageability Considerations
6.1. Control of Function and Policy 6.1. Control of Function and Policy
The Auto-Bandwidth feature SHOULD be controlled per LSP (at PCC The auto-bandwidth feature SHOULD be controlled on a per-LSP basis
(head-end of the LSP) or PCE) and the values for auto-bandwidth (at the PCC (head-end of the LSP) or PCE), and the values for auto-
parameters e.g. sample-interval, adjustment-interval (up/down), bandwidth parameters, e.g., Sample-Interval, Adjustment-Interval (up/
minimum-bandwidth, maximum-bandwidth, adjustment-threshold (up/down) down), Minimum-Bandwidth, Maximum-Bandwidth, and Adjustment-Threshold
SHOULD be configurable by an operator. (up/down), SHOULD be configurable by an operator.
The Maximum-Bandwidth (and Minimum-Bandwidth) should be set to The Maximum-Bandwidth (and Minimum-Bandwidth) should be set to an
acceptable limit to avoid impact on the rest of the MPLS-TE domain. acceptable limit to avoid having an impact on the rest of the MPLS-TE
domain.
The operator should make sure that the Overflow-Threshold is greater The operator should make sure that the Overflow-Threshold is greater
than or at least equal to the Up-Adjustment-Threshold. And similarly, than or at least equal to the Up-Adjustment-Threshold. And
make sure that the Underflow-Threshold is greater than or at least similarly, it is important to ensure that the Underflow-Threshold is
equal to the Down-Adjustment-Threshold. greater than or at least equal to the Down-Adjustment-Threshold.
6.2. Information and Data Models 6.2. Information and Data Models
A MIB module for gathering operational information about PCEP is A MIB module for gathering operational information about the PCEP is
defined in [RFC7420]. Additionally, the YANG module defined in defined in [RFC7420]. Additionally, the YANG module defined in
[I-D.ietf-pce-pcep-yang] provides for both configuration of PCEP as [PCE-PCEP-YANG] provides both configuration of PCEP as well as
well as operational management. These could be enhanced to provide operational management. These could be enhanced to provide controls
controls and indicators for support of auto-bandwidth feature. and indicators for support of the auto-bandwidth feature. Support
Support for various configuration knobs as well as counters of for various configuration knobs as well as counters of messages sent/
messages sent/received containing the TLVs defined in this document received containing the TLVs defined in this document could be added.
could be added.
6.3. Liveness Detection and Monitoring 6.3. Liveness Detection and Monitoring
The mechanisms defined in this document do not imply any new liveness The mechanisms defined in this document do not imply any new liveness
detection and monitoring requirements in addition to those already detection and monitoring requirements in addition to those already
listed in [RFC5440]. listed in [RFC5440].
6.4. Verify Correct Operations 6.4. Verifying Correct Operations
The mechanisms defined in this document do not imply any new The mechanisms defined in this document do not imply any new
operation verification requirements in addition to those already operation verification requirements in addition to those already
listed in [RFC5440]. listed in [RFC5440].
In case of an invalid value, the Sub-TLV would get ignored and the In the case in which an invalid value is present, the sub-TLV would
previous value would be maintained. In such case the implementation get ignored and the previous value will be maintained. In such a
SHOULD log the event. case, the implementation SHOULD log the event.
6.5. Requirements On Other Protocols 6.5. Requirements for Other Protocols
The mechanisms defined in this document do not add any new The mechanisms defined in this document do not add any new
requirements on other protocols. requirements for other protocols.
6.6. Impact On Network Operations 6.6. Impact on Network Operations
In order to avoid any unacceptable impact on network operations, an In order to avoid any unacceptable impact on network operations, an
implementation SHOULD allow a limit to be placed on the number of implementation SHOULD allow a limit to be placed on the number of
LSPs that can be enabled with auto-bandwidth feature. For each LSP LSPs that can be enabled with the auto-bandwidth feature. For each
enabled with auto-bandwidth feature there is an extra load on PCC, as LSP enabled with the auto-bandwidth feature, there is an extra load
it needs to monitor the traffic and report the calculated bandwidth on the PCC, as it needs to monitor the traffic and report the
to be adjusted to the PCE. The PCE further re-compute paths based on calculated bandwidth to be adjusted to the PCE. The PCE further
the requested bandwidth and update the path to the PCC, which in recomputes paths based on the requested bandwidth and updates the
turns triggers the re-signaling of the path. All these steps adds path to the PCC, which, in turn, triggers the resignaling of the
extra load and churn in the network and thus operator needs to take path. All these steps add extra load and churn in the network; thus,
due care while enabling this features on a number of LSPs. the operator needs to take due care while enabling these features on
a number of LSPs.
An implementation MAY allow a limit to be placed on the rate of auto- An implementation MAY allow a limit to be placed on the rate of auto-
bandwidth related messages sent by a PCEP speaker and received by a bandwidth-related messages sent by a PCEP speaker and received by a
peer. An implementation SHOULD also allow sending a notification peer. An implementation SHOULD also allow notifications to be sent
when a PCEP speaker is overwhelmed or the rate of messages reach a when a PCEP speaker is overwhelmed or when the rate of messages
threshold. reaches a threshold.
Due care is required by the operator if a Sample-Interval value Due care is required by the operator if a Sample-Interval value
significantly smaller than the default (5 minute) is used, as a small significantly smaller than the default (5 minutes) is used, as small
Sample-Interval values, e.g., 1 minute or less, could cause Sample-Interval values, e.g., 1 minute or less, could cause
undesirable interactions with transport protocols. These undesirable undesirable interactions with transport protocols. These undesirable
interactions result from providing insufficient time for transport interactions result from providing insufficient time for transport
protocol reactions to a prior bandwidth adjustment to settle out protocol reactions to a prior bandwidth adjustment to settle down
before bandwidth samples are taken for the next bandwidth adjustment. before Bandwidth-Samples are taken for the next bandwidth adjustment.
7. Security Considerations 7. Security Considerations
This document defines AUTO-BANDWIDTH-CAPABILITY TLV and AUTO- This document defines AUTO-BANDWIDTH-CAPABILITY TLV and AUTO-
BANDWIDTH-ATTRIBUTES sub-TLVs which do not add any substantial new BANDWIDTH-ATTRIBUTES sub-TLVs, which do not add any substantial new
security concerns beyond those already discussed in [RFC8231] and security concerns beyond those already discussed in [RFC8231] and
[RFC8281] for stateful PCE operations. As per [RFC8231], it is [RFC8281] for stateful PCE operations. As per [RFC8231], it is
RECOMMENDED that these PCEP extensions only be activated on RECOMMENDED that these PCEP extensions only be activated on
authenticated and encrypted sessions across PCEs and PCCs belonging authenticated and encrypted sessions across PCEs and PCCs belonging
to the same administrative authority, using Transport Layer Security to the same administrative authority, using Transport Layer Security
(TLS) [RFC8253], as per the recommendations and best current (TLS) [RFC8253], as per the recommendations and best current
practices in BCP 195 [RFC7525] (unless explicitly set aside in practices in BCP 195 [RFC7525] (unless explicitly set aside in
[RFC8253]). [RFC8253]).
Incorrect auto-bandwidth parameters in the AUTO-BANDWIDTH-ATTRIBUTES Incorrect auto-bandwidth parameters in the AUTO-BANDWIDTH-ATTRIBUTES
sub-TLVs could have an adverse effect on the LSP as well as on the sub-TLVs could have an adverse effect on the LSP as well as on the
network. network.
8. IANA Considerations 8. IANA Considerations
8.1. PCEP TLV Type Indicators 8.1. PCEP TLV Type Indicators
This document defines the following new PCEP TLVs; IANA is requested This document defines the following new PCEP TLVs; IANA has made the
to make the following allocations from the "PCEP TLV Type Indicators" following allocations from the "PCEP TLV Type Indicators" subregistry
sub-registry of the PCEP Numbers registry, as follows: of the "Path Computation Element Protocol (PCEP) Numbers" registry as
follows:
Value Name Reference +-------+---------------------------+-----------+
----------------------------------------------------------------- | Value | Description | Reference |
TBD2 AUTO-BANDWIDTH-CAPABILITY [This document] +=======+===========================+===========+
TBD1 AUTO-BANDWIDTH-ATTRIBUTES [This document] | 36 | AUTO-BANDWIDTH-CAPABILITY | [RFC8733] |
+-------+---------------------------+-----------+
| 37 | AUTO-BANDWIDTH-ATTRIBUTES | [RFC8733] |
+-------+---------------------------+-----------+
Table 3: PCEP TLV Type Indicators
8.2. AUTO-BANDWIDTH-CAPABILITY TLV Flag Field 8.2. AUTO-BANDWIDTH-CAPABILITY TLV Flag Field
IANA is requested to create a sub-registry to manage the Flag field IANA has created a subregistry to manage the Flag field of the AUTO-
of the AUTO-BANDWIDTH-CAPABILITY TLV within the "Path Computation BANDWIDTH-CAPABILITY TLV within the "Path Computation Element
Element Protocol (PCEP) Numbers" registry. Protocol (PCEP) Numbers" registry.
New bit numbers are to be assigned by Standards Action [RFC8126]. New bit numbers are to be assigned by Standards Action [RFC8126].
Each bit should be tracked with the following qualities: Each bit should be tracked with the following qualities:
o Bit number (counting from bit 0 as the most significant bit) * Bit number (counting from bit 0 as the most significant bit)
o Capability description * Capability description
o Defining RFC * Defining RFC
The initial contents of the sub-registry are empty, with all bits The initial contents of the subregistry are empty, with all bits
marked unassigned marked unassigned.
8.3. AUTO-BANDWIDTH-ATTRIBUTES Sub-TLV 8.3. AUTO-BANDWIDTH-ATTRIBUTES Sub-TLV
This document specifies the AUTO-BANDWIDTH-ATTRIBUTES Sub-TLVs. IANA This document specifies the AUTO-BANDWIDTH-ATTRIBUTES sub-TLVs. IANA
is requested to create an "AUTO-BANDWIDTH-ATTRIBUTES Sub-TLV Types" has created an "AUTO-BANDWIDTH-ATTRIBUTES Sub-TLV Types" subregistry
sub-registry within the "Path Computation Element Protocol (PCEP) within the "Path Computation Element Protocol (PCEP) Numbers"
Numbers" registry to manage the type indicator space for sub-TLVs of registry to manage the type indicator space for sub-TLVs of the AUTO-
the AUTO-BANDWIDTH-ATTRIBUTES TLV. The valid range of values in the BANDWIDTH-ATTRIBUTES TLV. The valid range of values in the registry
registry is 0-65535. IANA is requested to initialize the registry is 0-65535. IANA has initialized the registry with the following
with the following values. All other values in the registry should values. All other values in the registry should be marked as
be marked as "Unassigned". "Unassigned".
IANA is requested to set the registration procedure for this registry IANA has set the Registration Procedure for this registry to read as
to read as follows: follows:
0-65503 IETF Review +-------------+------------------------+
65504-65535 Experimental Use | Range | Registration Procedure |
+=============+========================+
| 0-65503 | IETF Review |
+-------------+------------------------+
| 65504-65535 | Experimental Use |
+-------------+------------------------+
Table 4: Registration Procedure for
the "AUTO-BANDWIDTH-ATTRIBUTES Sub-
TLV" Registry
This document defines the following types: This document defines the following types:
Type Name Reference +----------+--------------------------------------+-----------+
----------------------------------------------------------------- | Type | Name | Reference |
0 Reserved [This document] +==========+======================================+===========+
1 Sample-Interval sub-TLV [This document] | 0 | Reserved | [RFC8733] |
2 Adjustment-Interval sub-TLV [This document] +----------+--------------------------------------+-----------+
3 Down-Adjustment-Interval sub-TLV [This document] | 1 | Sample-Interval | [RFC8733] |
4 Adjustment-Threshold sub-TLV [This document] +----------+--------------------------------------+-----------+
5 Adjustment-Threshold-Percentage sub-TLV [This document] | 2 | Adjustment-Interval | [RFC8733] |
6 Down-Adjustment-Threshold sub-TLV [This document] +----------+--------------------------------------+-----------+
7 Down-Adjustment-Threshold-Percentage sub-TLV [This document] | 3 | Down-Adjustment-Interval | [RFC8733] |
8 Minimum-Bandwidth sub-TLV [This document] +----------+--------------------------------------+-----------+
9 Maximum-Bandwidth sub-TLV [This document] | 4 | Adjustment-Threshold | [RFC8733] |
10 Overflow-Threshold sub-TLV [This document] +----------+--------------------------------------+-----------+
11 Overflow-Threshold-Percentage sub-TLV [This document] | 5 | Adjustment-Threshold-Percentage | [RFC8733] |
12 Underflow-Threshold sub-TLV [This document] +----------+--------------------------------------+-----------+
13 Underflow-Threshold-Percentage sub-TLV [This document] | 6 | Down-Adjustment-Threshold | [RFC8733] |
14- Unassigned [This document] +----------+--------------------------------------+-----------+
65503 | 7 | Down-Adjustment-Threshold-Percentage | [RFC8733] |
+----------+--------------------------------------+-----------+
| 8 | Minimum-Bandwidth | [RFC8733] |
+----------+--------------------------------------+-----------+
| 9 | Maximum-Bandwidth | [RFC8733] |
+----------+--------------------------------------+-----------+
| 10 | Overflow-Threshold | [RFC8733] |
+----------+--------------------------------------+-----------+
| 11 | Overflow-Threshold-Percentage | [RFC8733] |
+----------+--------------------------------------+-----------+
| 12 | Underflow-Threshold | [RFC8733] |
+----------+--------------------------------------+-----------+
| 13 | Underflow-Threshold-Percentage | [RFC8733] |
+----------+--------------------------------------+-----------+
| 14-65503 | Unassigned | [RFC8733] |
+----------+--------------------------------------+-----------+
Table 5: Initial Contents of the "AUTO-BANDWIDTH-ATTRIBUTES
Sub-TLV" Registry
8.4. Error Object 8.4. Error Object
This document defines a new Error-Value for PCErr message of Error- This document defines a new Error-value for PCErr message of Error-
Type 19 (Invalid Operation) [RFC8231]. IANA is requested to allocate Type 19 (Invalid Operation) [RFC8231]. IANA has allocated a new
new error-value within the "PCEP-ERROR Object Error Types and Values" Error-value within the "PCEP-ERROR Object Error Types and Values"
subregistry of the PCEP Numbers registry, as follows: subregistry of the "Path Computation Element Protocol (PCEP) Numbers"
registry as follows:
Error-Type Meaning & error values Reference +------------+-----------+--------------------+-----------+
----------------------------------------------------------------- | Error-Type | Meaning | Error-value | Reference |
19 Invalid Operations +============+===========+====================+===========+
| 19 | Invalid | 14: Auto-Bandwidth | [RFC8733] |
| | Operation | capability was not | |
| | | advertised | |
+------------+-----------+--------------------+-----------+
Error-Value = TBD4: [This document] Table 6: Addition to the "PCEP-ERROR Object Error Types
Auto-Bandwidth Capability and Values" Registry
was not Advertised
8.5. Notification Object 8.5. Notification Object
IANA is requested to allocate new Notification Type and Notification IANA has allocated a new Notification-type and Notification-values
Values within the "Notification Object" sub-registry of the PCEP within the "Notification Object" subregistry of the "Path Computation
Numbers registry, as follows: Element Protocol (PCEP) Numbers" registry as follows:
Type Meaning Reference +-------------------+----------------+--------------------+---------+
----------------------------------------------------------------- | Notification-type | Name | Notification-value |Reference|
TBD3 Auto-Bandwidth Overwhelm State [This document] +===================+================+====================+=========+
| 5 | Auto-Bandwidth | 0: Unassigned |[RFC8733]|
| |Overwhelm State | | |
+-------------------+----------------+--------------------+---------+
| | | 1: Entering Auto- |[RFC8733]|
| | |Bandwidth Overwhelm | |
| | | State | |
+-------------------+----------------+--------------------+---------+
| | | 2: Clearing Auto- |[RFC8733]|
| | |Bandwidth Overwhelm | |
| | | State | |
+-------------------+----------------+--------------------+---------+
Notification-value=1: Entering Auto-Bandwidth Table 7: Additions to the "Notification Object" Registry
overwhelm state
Notification-value=2: Clearing Auto-Bandwidth
overwhelm state
9. References 9. References
9.1. Normative References 9.1. Normative References
[IEEE.754.1985]
IEEE, "Standard for Binary Floating-Point Arithmetic",
DOI 10.1109/IEEESTD.1985.82928, IEEE Standard 754, October
1985, <https://doi.org/10.1109/IEEESTD.1985.82928>.
[RFC2119] Bradner, S., "Key words for use in RFCs to Indicate [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate
Requirement Levels", BCP 14, RFC 2119, March 1997. Requirement Levels", BCP 14, RFC 2119,
DOI 10.17487/RFC2119, March 1997,
<https://www.rfc-editor.org/info/rfc2119>.
[RFC5440] Vasseur, JP. and JL. Le Roux, "Path Computation Element [RFC5440] Vasseur, JP., Ed. and JL. Le Roux, Ed., "Path Computation
(PCE) Communication Protocol (PCEP)", RFC 5440, March Element (PCE) Communication Protocol (PCEP)", RFC 5440,
2009. DOI 10.17487/RFC5440, March 2009,
<https://www.rfc-editor.org/info/rfc5440>.
[RFC7525] Sheffer, Y., Holz, R. and P. Saint-Andre, "Recommendations [RFC7525] Sheffer, Y., Holz, R., and P. Saint-Andre,
for Secure Use of Transport Layer Security (TLS) and "Recommendations for Secure Use of Transport Layer
Datagram Transport Layer Security (DTLS)", BCP 195, RFC Security (TLS) and Datagram Transport Layer Security
7525, DOI 10.17487/RFC7525, May 2015. (DTLS)", BCP 195, RFC 7525, DOI 10.17487/RFC7525, May
2015, <https://www.rfc-editor.org/info/rfc7525>.
[RFC8126] Cotton, M., Leiba, B., and T. Narten, "Guidelines for [RFC8126] Cotton, M., Leiba, B., and T. Narten, "Guidelines for
Writing an IANA Considerations Section in RFCs", BCP 26, Writing an IANA Considerations Section in RFCs", BCP 26,
RFC 8126, DOI 10.17487/RFC8126, June 2017, RFC 8126, DOI 10.17487/RFC8126, June 2017,
<https://www.rfc-editor.org/info/rfc8126>. <https://www.rfc-editor.org/info/rfc8126>.
[RFC8174] Leiba, B., "Ambiguity of Uppercase vs Lowercase in RFC [RFC8174] Leiba, B., "Ambiguity of Uppercase vs Lowercase in RFC
2119 Key Words", BCP 14, RFC 8174, DOI 10.17487/RFC8174, 2119 Key Words", BCP 14, RFC 8174, DOI 10.17487/RFC8174,
May 2017, <https://www.rfc-editor.org/info/rfc8174>. May 2017, <https://www.rfc-editor.org/info/rfc8174>.
[RFC8231] Crabbe, E., Minei, I., Medved, J., and R. Varga, "Pah [RFC8231] Crabbe, E., Minei, I., Medved, J., and R. Varga, "Path
Computation Element Communication Protocol (PCEP) Computation Element Communication Protocol (PCEP)
Extensions for Stateful PCE", RFC 8231, DOI Extensions for Stateful PCE", RFC 8231,
10.17487/RFC8231, September 2017, DOI 10.17487/RFC8231, September 2017,
<https://www.rfc-editor.org/infor/rfc8231>. <https://www.rfc-editor.org/info/rfc8231>.
[RFC8253] Lopez, D., Dios, O., Wu, W., and D. Dhody, "PCEPS: Usage [RFC8253] Lopez, D., Gonzalez de Dios, O., Wu, Q., and D. Dhody,
of TLS to Provide a Secure Transport for the Path "PCEPS: Usage of TLS to Provide a Secure Transport for the
Computation Element Communication Protocol (PCEP)", RFC Path Computation Element Communication Protocol (PCEP)",
8253, October 2017, RFC 8253, DOI 10.17487/RFC8253, October 2017,
<https://www.rfc-editor.org/info/rfc8253>. <https://www.rfc-editor.org/info/rfc8253>.
[RFC8281] Crabbe, E., Minei, I., Sivabalan, S., and R. Varga, "Path [RFC8281] Crabbe, E., Minei, I., Sivabalan, S., and R. Varga, "Path
Computation Element Communication Protocol (PCEP) Computation Element Communication Protocol (PCEP)
Extensions for PCE-Initiated LSP Setup in a Stateful PCE, Extensions for PCE-Initiated LSP Setup in a Stateful PCE
Model", RFC 8281, DOI 10.17487/RFC8281, December 2017, Model", RFC 8281, DOI 10.17487/RFC8281, December 2017,
<https://www.rfc-editor.org/info/rfc8281>. <https://www.rfc-editor.org/info/rfc8281>.
[IEEE.754.1985] Institute of Electrical and Electronics Engineers,
"Standard for Binary Floating-Point Arithmetic", IEEE
Standard 754, August 1985.
9.2. Informative References 9.2. Informative References
[PCE-PCEP-YANG]
Dhody, D., Hardwick, J., Beeram, V., and J. Tantsura, "A
YANG Data Model for Path Computation Element
Communications Protocol (PCEP)", Work in Progress,
Internet-Draft, draft-ietf-pce-pcep-yang-13, 31 October
2019,
<https://tools.ietf.org/html/draft-ietf-pce-pcep-yang-13>.
[RFC3209] Awduche, D., Berger, L., Gan, D., Li, T., Srinivasan, V., [RFC3209] Awduche, D., Berger, L., Gan, D., Li, T., Srinivasan, V.,
and G. Swallow, "RSVP-TE: Extensions to RSVP for LSP and G. Swallow, "RSVP-TE: Extensions to RSVP for LSP
Tunnels", RFC 3209, DOI 10.17487/RFC3209, December 2001, Tunnels", RFC 3209, DOI 10.17487/RFC3209, December 2001,
<https://www.rfc-editor.org/info/rfc3209>. <https://www.rfc-editor.org/info/rfc3209>.
[RFC3471] Berger, L., "Generalized Multi-Protocol Label Switching [RFC3471] Berger, L., Ed., "Generalized Multi-Protocol Label
(GMPLS) Signaling Functional Description", RFC 3471, Switching (GMPLS) Signaling Functional Description",
January 2003. RFC 3471, DOI 10.17487/RFC3471, January 2003,
<https://www.rfc-editor.org/info/rfc3471>.
[RFC7420] Koushik, A., Stephan, E., Zhao, Q., King, D., and J. [RFC7420] Koushik, A., Stephan, E., Zhao, Q., King, D., and J.
Hardwick, "Path Computation Element Communication Protocol Hardwick, "Path Computation Element Communication Protocol
(PCEP) Management Information Base (MIB) Module", RFC (PCEP) Management Information Base (MIB) Module",
7420, December 2014. RFC 7420, DOI 10.17487/RFC7420, December 2014,
<https://www.rfc-editor.org/info/rfc7420>.
[RFC8051] Zhang, X. and I. Minei, "Applicability of a Stateful Path
Computation Element (PCE)", RFC 8051, January 2017.
[I-D.ietf-pce-pcep-yang] Dhody, D., Hardwick, J., Beeram, V., and J. [RFC8051] Zhang, X., Ed. and I. Minei, Ed., "Applicability of a
Tantsura, "A YANG Data Model for Path Computation Element Stateful Path Computation Element (PCE)", RFC 8051,
Communications Protocol (PCEP)", draft-ietf-pce-pcep-yang DOI 10.17487/RFC8051, January 2017,
(work in progress). <https://www.rfc-editor.org/info/rfc8051>.
Acknowledgments Acknowledgments
Authors would like to thank Robert Varga, Venugopal Reddy, Reeja The authors would like to thank Robert Varga, Venugopal Reddy, Reeja
Paul, Sandeep Boina, Avantika, JP Vasseur, Himanshu Shah, Jonathan Paul, Sandeep Boina, Avantika, JP Vasseur, Himanshu Shah, Jonathan
Hardwick and Adrian Farrel for their useful comments and suggestions. Hardwick, and Adrian Farrel for their useful comments and
suggestions.
Thanks to Daniel Franke, Joe Clarke, David Black, and Erik Kline for Thanks to Daniel Franke, Joe Clarke, David Black, and Erik Kline for
the directorate reviews. the directorate reviews.
Thanks to Mirja Kuhlewind, Barry Leiba, Benjamin Kaduk, and Roman Thanks to Mirja KΓΌhlewind, Barry Leiba, Benjamin Kaduk, and Roman
Danyliw for the IESG review. Danyliw for the IESG review.
Contributors' Addresses Contributors
He Zekun He Zekun
Tencent Holdings Ltd, Tencent Holdings Ltd.
Shenzhen P.R.China Shenzhen
China
Email: kinghe@tencent.com Email: kinghe@tencent.com
Xian Zhang Xian Zhang
Huawei Technologies Huawei Technologies
Research Area F3-1B, Research Area F3-1B
Huawei Industrial Base, Huawei Industrial Base,
Shenzhen, 518129 Shenzhen
518129
China China
Phone: +86-755-28972645 Phone: +86-755-28972645
Email: zhang.xian@huawei.com Email: zhang.xian@huawei.com
Young Lee Young Lee
SKKU Samsung
Email: younglee.tx@gmail.com Email: younglee.tx@gmail.com
Authors' Addresses Authors' Addresses
Dhruv Dhody (editor) Dhruv Dhody (editor)
Huawei Technologies Huawei Technologies
Divyashree Techno Park, Whitefield Divyashree Techno Park, Whitefield
Bangalore, Karnataka 560066 Bangalore 560066
Karnataka
India India
Email: dhruv.ietf@gmail.com Email: dhruv.ietf@gmail.com
Rakesh Gandhi (editor) Rakesh Gandhi (editor)
Cisco Systems, Inc. Cisco Systems, Inc.
Canada Canada
Email: rgandhi@cisco.com Email: rgandhi@cisco.com
skipping to change at page 34, line 32 skipping to change at line 1622
Individual Contributor Individual Contributor
Email: udayasreereddy@gmail.com Email: udayasreereddy@gmail.com
Ravi Singh Ravi Singh
Individual Contributor Individual Contributor
Email: ravi.singh.ietf@gmail.com Email: ravi.singh.ietf@gmail.com
Luyuan Fang Luyuan Fang
Expedia, Inc. Expedia Group, Inc.
USA United States of America
Email: luyuanf@gmail.com Email: luyuanf@gmail.com
 End of changes. 274 change blocks. 
717 lines changed or deleted 810 lines changed or added

This html diff was produced by rfcdiff 1.47. The latest version is available from http://tools.ietf.org/tools/rfcdiff/