< draft-ietf-pce-stateful-pce-auto-bandwidth-11.txt   draft-ietf-pce-stateful-pce-auto-bandwidth-12.txt >
PCE Working Group D. Dhody, Ed. PCE Working Group D. Dhody, Ed.
Internet-Draft Huawei Technologies Internet-Draft Huawei Technologies
Intended status: Standards Track R. Gandhi, Ed. Intended status: Standards Track R. Gandhi, Ed.
Expires: March 01, 2020 Cisco Systems, Inc. Expires: March 28, 2020 Cisco Systems, Inc.
U. Palle U. Palle
R. Singh R. Singh
Individual Contributor Individual Contributor
L. Fang L. Fang
Expedia, Inc. Expedia, Inc.
August 29, 2019 September 25, 2019
PCEP Extensions for MPLS-TE LSP Automatic Bandwidth Adjustment with PCEP Extensions for MPLS-TE LSP Automatic Bandwidth Adjustment with
Stateful PCE Stateful PCE
draft-ietf-pce-stateful-pce-auto-bandwidth-11 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 Clients (PCCs) requests.
The Stateful PCE extensions allow stateful control of Multi-Protocol The Stateful PCE extensions allow stateful control of Multi-Protocol
Label Switching (MPLS) Traffic Engineering Label Switched Paths (TE Label Switching (MPLS) Traffic Engineering Label Switched Paths (TE
LSPs) using PCEP. LSPs) using PCEP.
skipping to change at page 2, line 30 skipping to change at page 2, line 30
Table of Contents Table of Contents
1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 3 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 3
2. Conventions Used in This Document . . . . . . . . . . . . . . 4 2. Conventions Used in This Document . . . . . . . . . . . . . . 4
2.1. Requirements Language . . . . . . . . . . . . . . . . . . 4 2.1. Requirements Language . . . . . . . . . . . . . . . . . . 4
2.2. Abbreviations . . . . . . . . . . . . . . . . . . . . . . 4 2.2. Abbreviations . . . . . . . . . . . . . . . . . . . . . . 4
2.3. Terminology . . . . . . . . . . . . . . . . . . . . . . . 5 2.3. Terminology . . . . . . . . . . . . . . . . . . . . . . . 5
3. Requirements for PCEP Extensions . . . . . . . . . . . . . . . 7 3. Requirements for PCEP Extensions . . . . . . . . . . . . . . . 7
4. Architectural Overview . . . . . . . . . . . . . . . . . . . . 8 4. Architectural Overview . . . . . . . . . . . . . . . . . . . . 8
4.1. Auto-Bandwidth Overview . . . . . . . . . . . . . . . . . 8 4.1. Auto-Bandwidth Overview . . . . . . . . . . . . . . . . . 8
4.2. Auto-bandwidth Theory of Operation . . . . . . . . . . . . 8 4.2. Auto-bandwidth Theory of Operation . . . . . . . . . . . . 9
4.3. Scaling Considerations . . . . . . . . . . . . . . . . . . 10 4.3. Scaling Considerations . . . . . . . . . . . . . . . . . . 10
5. PCEP Extensions . . . . . . . . . . . . . . . . . . . . . . . 10 5. PCEP Extensions . . . . . . . . . . . . . . . . . . . . . . . 10
5.1. Capability Advertisement . . . . . . . . . . . . . . . . . 10 5.1. Capability Advertisement . . . . . . . . . . . . . . . . . 10
5.1.1. AUTO-BANDWIDTH-CAPABILITY TLV . . . . . . . . . . . . 11 5.1.1. AUTO-BANDWIDTH-CAPABILITY TLV . . . . . . . . . . . . 11
5.2. AUTO-BANDWIDTH-ATTRIBUTES TLV . . . . . . . . . . . . . . 11 5.2. AUTO-BANDWIDTH-ATTRIBUTES TLV . . . . . . . . . . . . . . 12
5.2.1. Sample-Interval sub-TLV . . . . . . . . . . . . . . . 13 5.2.1. Sample-Interval sub-TLV . . . . . . . . . . . . . . . 13
5.2.2. Adjustment Intervals . . . . . . . . . . . . . . . . . 13 5.2.2. Adjustment Intervals . . . . . . . . . . . . . . . . . 14
5.2.2.1. Adjustment-Interval sub-TLV . . . . . . . . . . . 13 5.2.2.1. Adjustment-Interval sub-TLV . . . . . . . . . . . 14
5.2.2.2. Down-Adjustment-Interval sub-TLV . . . . . . . . . 14 5.2.2.2. Down-Adjustment-Interval sub-TLV . . . . . . . . . 14
5.2.3. Adjustment Thresholds . . . . . . . . . . . . . . . . 15 5.2.3. Adjustment Thresholds . . . . . . . . . . . . . . . . 15
5.2.3.1. Adjustment-Threshold sub-TLV . . . . . . . . . . . 15 5.2.3.1. Adjustment-Threshold sub-TLV . . . . . . . . . . . 15
5.2.3.2. Adjustment-Threshold-Percentage sub-TLV . . . . . 16 5.2.3.2. Adjustment-Threshold-Percentage sub-TLV . . . . . 16
5.2.3.3. Down-Adjustment-Threshold sub-TLV . . . . . . . . 16 5.2.3.3. Down-Adjustment-Threshold sub-TLV . . . . . . . . 17
5.2.3.4. Down-Adjustment-Threshold-Percentage sub-TLV . . . 17 5.2.3.4. Down-Adjustment-Threshold-Percentage sub-TLV . . . 18
5.2.4. Minimum and Maximum Bandwidth Values . . . . . . . . . 18 5.2.4. Minimum and Maximum Bandwidth Values . . . . . . . . . 19
5.2.4.1. Minimum-Bandwidth sub-TLV . . . . . . . . . . . . 18 5.2.4.1. Minimum-Bandwidth sub-TLV . . . . . . . . . . . . 19
5.2.4.2. Maximum-Bandwidth sub-TLV . . . . . . . . . . . . 18 5.2.4.2. Maximum-Bandwidth sub-TLV . . . . . . . . . . . . 19
5.2.5. Overflow and Underflow Conditions . . . . . . . . . . 19 5.2.5. Overflow and Underflow Conditions . . . . . . . . . . 20
5.2.5.1. Overflow-Threshold sub-TLV . . . . . . . . . . . . 19 5.2.5.1. Overflow-Threshold sub-TLV . . . . . . . . . . . . 20
5.2.5.2. Overflow-Threshold-Percentage sub-TLV . . . . . . 20 5.2.5.2. Overflow-Threshold-Percentage sub-TLV . . . . . . 21
5.2.5.3. Underflow-Threshold sub-TLV . . . . . . . . . . . 21 5.2.5.3. Underflow-Threshold sub-TLV . . . . . . . . . . . 22
5.2.5.4. Underflow-Threshold-Percentage sub-TLV . . . . . . 21 5.2.5.4. Underflow-Threshold-Percentage sub-TLV . . . . . . 23
5.3. BANDWIDTH Object . . . . . . . . . . . . . . . . . . . . . 22 5.3. BANDWIDTH Object . . . . . . . . . . . . . . . . . . . . . 24
5.4. The PCInitiate Message . . . . . . . . . . . . . . . . . . 23 5.4. The PCInitiate Message . . . . . . . . . . . . . . . . . . 24
5.5. The PCUpd Message . . . . . . . . . . . . . . . . . . . . 23 5.5. The PCUpd Message . . . . . . . . . . . . . . . . . . . . 24
5.6. The PCRpt Message . . . . . . . . . . . . . . . . . . . . 23 5.6. The PCRpt Message . . . . . . . . . . . . . . . . . . . . 24
5.7. The PCNtf Message . . . . . . . . . . . . . . . . . . . . 23 5.7. The PCNtf Message . . . . . . . . . . . . . . . . . . . . 25
6. Manageability Considerations . . . . . . . . . . . . . . . . . 24 6. Manageability Considerations . . . . . . . . . . . . . . . . . 26
6.1. Control of Function and Policy . . . . . . . . . . . . . . 24 6.1. Control of Function and Policy . . . . . . . . . . . . . . 26
6.2. Information and Data Models . . . . . . . . . . . . . . . 24 6.2. Information and Data Models . . . . . . . . . . . . . . . 26
6.3. Liveness Detection and Monitoring . . . . . . . . . . . . 25 6.3. Liveness Detection and Monitoring . . . . . . . . . . . . 27
6.4. Verify Correct Operations . . . . . . . . . . . . . . . . 25 6.4. Verify Correct Operations . . . . . . . . . . . . . . . . 27
6.5. Requirements On Other Protocols . . . . . . . . . . . . . 25 6.5. Requirements On Other Protocols . . . . . . . . . . . . . 27
6.6. Impact On Network Operations . . . . . . . . . . . . . . . 25 6.6. Impact On Network Operations . . . . . . . . . . . . . . . 27
7. Security Considerations . . . . . . . . . . . . . . . . . . . 26 7. Security Considerations . . . . . . . . . . . . . . . . . . . 28
8. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 26 8. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 28
8.1. PCEP TLV Type Indicators . . . . . . . . . . . . . . . . . 26 8.1. PCEP TLV Type Indicators . . . . . . . . . . . . . . . . . 28
8.2. AUTO-BANDWIDTH-CAPABILITY TLV Flag Field . . . . . . . . . 26 8.2. AUTO-BANDWIDTH-CAPABILITY TLV Flag Field . . . . . . . . . 28
8.3. AUTO-BANDWIDTH-ATTRIBUTES Sub-TLV . . . . . . . . . . . . 26 8.3. AUTO-BANDWIDTH-ATTRIBUTES Sub-TLV . . . . . . . . . . . . 29
8.4. Error Object . . . . . . . . . . . . . . . . . . . . . . . 27 8.4. Error Object . . . . . . . . . . . . . . . . . . . . . . . 29
8.5. Notification Object . . . . . . . . . . . . . . . . . . . 28 8.5. Notification Object . . . . . . . . . . . . . . . . . . . 30
9. References . . . . . . . . . . . . . . . . . . . . . . . . . . 29 9. References . . . . . . . . . . . . . . . . . . . . . . . . . . 31
9.1. Normative References . . . . . . . . . . . . . . . . . . . 29 9.1. Normative References . . . . . . . . . . . . . . . . . . . 31
9.2. Informative References . . . . . . . . . . . . . . . . . . 29 9.2. Informative References . . . . . . . . . . . . . . . . . . 31
Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . . . 31 Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . . . 33
Contributors' Addresses . . . . . . . . . . . . . . . . . . . . . 31 Contributors' Addresses . . . . . . . . . . . . . . . . . . . . . 33
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . . 32 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . . 34
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 PCE and PCE, that enables
computation of Multi-Protocol Label Switching (MPLS) Traffic computation of Multi-Protocol Label Switching (MPLS) Traffic
Engineering Label Switched Paths (TE 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 mode of operations - 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 Active stateful PCE where
the LSPs are controlled by the PCE. 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 to adjust the bandwidth reserved with a certain bandwidth may require adjustment of the bandwidth
in the network dynamically. The head-end Label Switch Router (LSR) reserved in the network dynamically. The head-end Label Switch
monitors the actual bandwidth demand of the established LSP and Router (LSR) monitors the actual bandwidth demand of the established
periodically computes new bandwidth. The head-end LSR adjusts the LSP and periodically computes new bandwidth. The head-end LSR
bandwidth reservation of the LSP based on the computed bandwidth adjusts the bandwidth reservation of the LSP based on the computed
automatically. This feature is commonly referred to as Auto- bandwidth automatically. This feature, when available in the head-
Bandwidth. The Auto-Bandwidth feature is described in detail in end Label Switching Router (LSR) implementation, is common referred
Section 4 of this document. to as Auto-Bandwidth. The Auto-Bandwidth feature is described in
detail in Section 4 of this 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 the Passive stateful PCE model: while the Passive stateful PCE uses a
path request/reply mechanism, the Active stateful PCE uses path request/reply mechanism, the Active stateful PCE uses a
report/update mechanism. In case of PCE-Initiated LSP, the PCC is report/update mechanism. In case of PCE-Initiated LSP, the PCC is
requested during the LSP initiation to monitor and calculate the new requested during the LSP initiation to monitor and calculate the new
adjusted bandwidth. [RFC8051] describes the use-case for Auto- adjusted bandwidth. [RFC8051] describes the use-case for Auto-
Bandwidth adjustment for Passive and Active stateful PCE. Bandwidth adjustment for Passive and Active stateful PCE.
This document defines the PCEP extensions needed to support Auto- Another approach would be to send the measured values itself to the
Bandwidth feature in a Active stateful PCE model where the LSP PCE, which is considered out of scope for this document.
This document defines the PCEP extensions needed to support an Auto-
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 out
of scope of this document. 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
skipping to change at page 5, line 10 skipping to change at page 5, line 14
PCEP: Path Computation Element Communication Protocol. PCEP: Path Computation Element Communication Protocol.
TE LSP: Traffic Engineering Label Switched Path. TE LSP: Traffic Engineering 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
LSP. Other types of PCC 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 traffic bandwidth demand of the LSP during represents the current 'measured' traffic bandwidth demand of the
a time interval. This is the maximum value of the traffic LSP during a time interval. This is the maximum value of the
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.
skipping to change at page 6, line 11 skipping to change at page 6, line 19
Down-Adjustment-Threshold: This parameter is used to decide when the Down-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 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, the percentage or absolute difference between the
current MaxAvgBw and the current bandwidth reservation of the LSP current MaxAvgBw and the current bandwidth reservation of the LSP
is greater than or equal to the Overflow-Threshold value. needs to be greater than or equal to the Overflow-Threshold 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 set 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. Count. The Overflow-Threshold needs to be greater than or equal 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, the percentage or absolute difference between the
current MaxAvgBw and the current bandwidth reservation of the LSP current MaxAvgBw and the current bandwidth reservation of the LSP
is greater than or equal to the Underflow-Threshold value. needs to be greater than or equal to the Underflow-Threshold 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 set 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 if
the underflow condition is met consecutively for the Underflow- the underflow condition is met consecutively for the Underflow-
Count. Count. The Underflow-Threshold needs to be greater than or equal
to the Down-Adjustment-Threshold.
Minimum-Threshold: The increase or decrease of the LSP bandwidth Minimum-Threshold: When percentage-based thresholds are in use, they
should be at least or above the minimum-threshold represented as are accompanied by this minimum threshold, which is used to
an absolute bandwidth value before the bandwidth adjustment for enforce that the magnitude of deviation of calculated LSP
the LSP is made. This threshold can be seen as a suppression bandwidth to be adjusted from the current bandwidth reservations
threshold that is used along with a percentage threshold to avoid exceeds a specific non-percentage-based criterion (represented as
unnecessary auto-bandwidth adjustments and re-signaling of the LSP an absolute bandwidth value) before any adjustments are made. This
at low bandwidth values. serves to suppress unnecessary auto-bandwidth adjustments and re-
signaling 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 |
+---------------------------------+---------------------------------+ +---------------------------------+---------------------------------+
| | | | | |
skipping to change at page 7, line 50 skipping to change at page 8, line 14
| | REQUESTED BANDWIDTH | | REQUESTED BANDWIDTH
v | v |
---------- ----------
| | | |
| PCC | | PCC |
| | | |
---------- ----------
Figure 1: Overview of Auto-Bandwidth PCEP extensions Figure 1: Overview of Auto-Bandwidth PCEP extensions
The 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 automatic 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 required to identify and inform the PCC, which LSPs are o It is necessary to identify and inform the PCC which LSPs have
enabled with 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 the
real-time bandwidth usage but be constant as set by the operator. real-time bandwidth usage; for some LSPs leaving the bandwidth
constant as set by the operator is preferred.
o In addition, an operator should be able to specify the auto- o 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 being wasted. Conversely,
if the actual traffic flowing through the LSP is higher than the if the actual traffic flowing through the LSP is higher than the
configured or current reserved bandwidth of the LSP, it can 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 operator expected value based on design zero). In practice, it can be set to an expected value based on
and planning. The head-end Label Switch Router (LSR) monitors the design and planning. The head-end Label Switch Router (LSR) monitors
actual traffic flowing through the LSP and uses that information to the actual traffic flowing through the LSP and uses that information
adjust the bandwidth reservation of the LSP in the network. to adjust the 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-before-break signaling method [RFC3209]. make-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 (which can be is periodically sampled at each Sample-Interval by the PCC, when the
configured by an operator and the default value as 5 minutes) by the PCC is the head-end node of the LSP. The sample interval can be
PCC, when the PCC is the head-end node of the LSP. The traffic rate configured by an operator, with a default value of 5 minutes. A very
samples are accumulated over the Adjustment-Interval period (in the low Sample-Interval could have some undesirable interactions with
Up or Down direction) (which can be configured by an operator and the transport protocols (see Section 6.6).
default value as 24 hours). The PCC, in-charge of calculating the
bandwidth to be adjusted, can decide to adjust the bandwidth of the The traffic rate samples are accumulated over the Adjustment-Interval
LSP to the highest traffic rate sample (MaxAvgBw) amongst the set of period (in the Up or Down direction). The period can be configured
bandwidth samples collected over the adjustment-interval period (in by an operator, with a default value of 24 hours. The PCC in-charge
the Up or Down direction) depending on the operator policy. of calculating the bandwidth to be adjusted can decide to adjust the
bandwidth of the LSP to the highest traffic rate sample (MaxAvgBw)
amongst the set of bandwidth samples collected over the
Adjustment-Interval period (in the Up or Down direction) depending on
the 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. Only if the difference between the
current bandwidth demand (MaxAvgBw) and the current bandwidth current bandwidth demand (MaxAvgBw) and the current bandwidth
reservation is greater than or equal to the Adjustment-Threshold reservation is greater than or equal to the Adjustment-Threshold the
(percentage or absolute value) (which can be configured by an LSP bandwidth is adjusted (upsized) to the current bandwidth demand
operator and the default as 5 percentage), the LSP bandwidth is (MaxAvgBw). The Adjustment-Threshold could be an absolute value or a
adjusted (upsized) to the current bandwidth demand (MaxAvgBw). percentage. The threshold can be configured by an operator, with a
Similarly, if the difference between the current bandwidth default value of 5 percentage. Similarly, if the difference between
reservation and the current bandwidth demand (MaxAvgBw) is greater the current bandwidth reservation and the current bandwidth demand
than or equal to the Down-Adjustment-Threshold (percentage or (MaxAvgBw) is greater than or equal to the Down-Adjustment-Threshold
absolute value), the LSP bandwidth is adjusted (downsized) to the (percentage or absolute value), the LSP bandwidth is adjusted
current bandwidth demand (MaxAvgBw). Some LSPs are less eventful (downsized) to the current bandwidth demand (MaxAvgBw). Some LSPs
while other LSPs may encounter a lot of changes in the traffic are less eventful while other LSPs may encounter a lot of changes in
pattern. The thresholds and intervals for bandwidth adjustment are the traffic pattern. The thresholds and intervals for bandwidth
configured based on the traffic pattern of the LSP. adjustment are 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 re-signaling, an operator may set a longer
adjustment-interval value (Up and/or Down). However, 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 an undesirable effect of masking
sudden changes in traffic demands of an LSP. To avoid this, the sudden changes in traffic demands of an LSP. To avoid this, the
Auto-Bandwidth feature may pre-maturely expire the adjustment- Auto-Bandwidth feature may prematurely expire the adjustment interval
interval and adjust the LSP bandwidth to accommodate the sudden and adjust the LSP bandwidth to accommodate the sudden bursts of
bursts of increase in traffic demand as an overflow condition or increase in traffic demand as an overflow condition or decrease in
decrease in traffic demand as an underflow condition. An operator traffic demand as an underflow condition. An operator needs to
needs to configure appropriate values for the Overflow-Threshold configure appropriate values for the Overflow-Threshold and/or
and/or Underflow-Threshold parameters and they do not have default Underflow-Threshold parameters and they do not have default values
values defined in this document. 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 accommodate the cases where the LSP bandwidth reservation may to accommodate the cases where the LSP bandwidth reservation may
become very large or very small over time. For example, an operator become very large or very small over time. For example, an operator
may use the percentage threshold to handle small to large bandwidth may use the percentage threshold to handle small to large bandwidth
values and absolute values to handle very large bandwidth values. values and absolute values to handle very large bandwidth values.
The auto-bandwidth adjustment is made when either one of the two The auto-bandwidth adjustment is made when either one of the two
thresholds, the absolute or percentage, is crossed. thresholds, the absolute or percentage, is crossed.
skipping to change at page 10, line 32 skipping to change at page 11, line 4
Section 5.7 of this document). Similarly, if a PCC gets overwhelmed Section 5.7 of this document). Similarly, if a PCC gets overwhelmed
due to signaling churn, it can notify the PCE to temporarily suspend due to signaling churn, it can notify the PCE to temporarily suspend
new LSP setup requests (see Section 5.7 of this document). new LSP setup requests (see 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 PCEP Initialization Phase, PCEP speakers (PCE or PCC)
advertise their support of Automatic Bandwidth adjustment feature. A advertise their support of Automatic Bandwidth adjustment feature. A
PCEP speaker includes the "Auto-Bandwidth Capability" TLV, in the PCEP speaker includes the AUTO-BANDWIDTH-CAPABILITY TLV, in the OPEN
OPEN Object to advertise its support for PCEP Auto-Bandwidth Object to advertise its support for PCEP Auto-Bandwidth extensions.
extensions. The presence of the "Auto-Bandwidth Capability" TLV in The presence of the AUTO-BANDWIDTH-CAPABILITY TLV in the OPEN Object
the OPEN Object indicates that the Automatic Bandwidth feature is indicates that the Automatic Bandwidth feature is supported as
supported as described in this document. described in this document.
o The PCEP protocol extensions for Auto-Bandwidth adjustments MUST o 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 The PCEP speaker that does not recognize the extensions defined in o A PCEP speaker that does not recognize the extensions defined in
this document sends the PCErr message with error-type 2 this document would simply ignore the TLVs as per [RFC5440].
(capability not supported) as per Section 6.9 in [RFC5440].
o If the PCEP speaker that supports the extensions defined in this o If a PCEP speaker that supports the extensions defined in this
document but did not advertise this capability, then upon receipt document but did not advertise this capability, then upon receipt
of AUTO-BANDWIDTH-ATTRIBUTES TLV in the LSP Attributes (LSPA) of AUTO-BANDWIDTH-ATTRIBUTES TLV in the LSP Attributes (LSPA)
object, it SHOULD generate a PCErr with error-type 19 (Invalid object, it SHOULD generate a PCErr with error-type 19 (Invalid
Operation), error-value TBD4 (Auto-Bandwidth capability was not Operation), error-value TBD4 (Auto-Bandwidth capability was not
advertised) and ignore the AUTO-BANDWIDTH-ATTRIBUTES TLV. advertised) and 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 Automatic Bandwidth Adjustment via PCEP capability
skipping to change at page 11, line 31 skipping to change at page 11, line 48
AUTO-BANDWIDTH-CAPABILITY TLV format AUTO-BANDWIDTH-CAPABILITY TLV format
The Type of the TLV is (TBD2) and it has a fixed Length of 4 octets. The Type of the TLV is (TBD2) 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 - Flags (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 PCE-Initiated LSP [RFC8281], this TLV is included in the LSPA
skipping to change at page 12, line 50 skipping to change at page 13, line 18
5 8 Adjustment-Threshold-Percentage sub-TLV 5 8 Adjustment-Threshold-Percentage sub-TLV
6 4 Down-Adjustment-Threshold sub-TLV 6 4 Down-Adjustment-Threshold sub-TLV
7 8 Down-Adjustment-Threshold-Percentage sub-TLV 7 8 Down-Adjustment-Threshold-Percentage sub-TLV
8 4 Minimum-Bandwidth sub-TLV 8 4 Minimum-Bandwidth sub-TLV
9 4 Maximum-Bandwidth sub-TLV 9 4 Maximum-Bandwidth sub-TLV
10 8 Overflow-Threshold sub-TLV 10 8 Overflow-Threshold sub-TLV
11 8 Overflow-Threshold-Percentage sub-TLV 11 8 Overflow-Threshold-Percentage sub-TLV
12 8 Underflow-Threshold sub-TLV 12 8 Underflow-Threshold sub-TLV
13 8 Underflow-Threshold-Percentage sub-TLV 13 8 Underflow-Threshold-Percentage sub-TLV
Future specification 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. If sub-TLVs are not present, the sampling and adjustment parameters. In case of a missing sub-TLV, as
default values as specified in this document are used or otherwise per the local policy, either the default value (as specified in this
based on the local policy are assumed. 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 sub-sections describe the sub-TLVs which are currently
defined to be carried within the AUTO-BANDWIDTH-ATTRIBUTES TLV. defined to be carried within the AUTO-BANDWIDTH-ATTRIBUTES TLV.
5.2.1. Sample-Interval sub-TLV 5.2.1. Sample-Interval sub-TLV
skipping to change at page 13, line 36 skipping to change at page 13, line 51
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Sample-Interval | | Sample-Interval |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Sample-Interval sub-TLV format Sample-Interval sub-TLV format
The Type is 1, Length is 4 octets, and the value comprises of - The Type is 1, Length is 4 octets, and the value comprises of -
o Sample-Interval: The 4-octet time interval for bandwidth sample o Sample-Interval: The 4-octet time interval for 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. The sample-interval seconds. The default value is 300 seconds. Due care needs to be
parameter MUST NOT be greater than the (down) adjustment-interval, taken in case of a very low Sample-Interval, as it can have some
otherwise the Sub-TLV MUST be ignored and the previous value is undesirable interactions with transport protocols (see Section
maintained. 6.6). The sample-interval parameter MUST NOT be greater than the
(down) adjustment-interval. In case of an invalid value, the Sub-
TLV MUST be ignored and the previous value is 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 the
adjustment interval parameters. An implementation MAY require to set adjustment interval parameters. The Adjustment-Interval sub-TLV
different adjustment interval values for when the bandwidth usage specifies the time interval for both upward (Up-Adjustment-Interval)
trend is moving upwards or downwards. The Adjustment-Interval sub- and downward (Down-Adjustment-Interval) trends. An implementation MAY
TLV specifies the time interval for both upward and downward trend. require to set a different adjustment interval values for when the
If the operator would like to use a different adjustment interval bandwidth usage trend is downwards from when it is moving upwards. In
during the downward trend, the Down-Adjustment-Interval sub-TLV is that case, the operator could use the Down-Adjustment-Interval sub-
included. TLV which overrides the 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 when MaxAvgBw is greater at which bandwidth adjustment should be made in upward or downward
than or less than the current bandwidth reservation of the LSP. direction. This sub-TLV specify the value for Up-Adjustment-Interval
and Down-Adjustment-Interval when they are the same and 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 Adjustment-Interval sub-TLV format
skipping to change at page 14, line 32 skipping to change at page 15, line 6
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-interval, otherwise the Sub-TLV MUST be ignored and the sample-interval, otherwise the Sub-TLV MUST be ignored and the
previous value is maintained. previous value is 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 at which bandwidth adjustment should be made when MaxAvgBw is
less than the current bandwidth reservation of the LSP. This less than the current bandwidth reservation of the LSP. This
parameter overwrites 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
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 Down-Adjustment-Interval sub-TLV format
The Type is 3, Length is 4 octets, and the value comprises of - The Type is 3, Length is 4 octets, and the value comprises of -
o Down-Adjustment-Interval: The 4-octet time interval for downward o Down-Adjustment-Interval: The 4-octet time interval for downward
bandwidth adjustments. The valid range is from 1 to 604800, in bandwidth adjustments. The valid range is from 1 to 604800 (7
seconds. The default value equals the adjustment-interval. The days), in seconds. The default value equals the adjustment-
down-adjustment-interval parameter MUST NOT be less than the interval. The down-adjustment-interval parameter MUST NOT be less
sample-interval, otherwise the Sub-TLV MUST be ignored and the than the sample-interval, otherwise the Sub-TLV MUST be ignored
previous value is maintained. and the previous value is 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 and downward trend. If the specifies the threshold for both upward (Up-Adjustment-Threshold) and
operator would like to use a different adjustment threshold during downward (Down-Adjustment-Threshold) trend. If the operator would
the downward trend, the Down-Adjustment-Threshold sub-TLV is like to use a different adjustment threshold during the downward
included. Similarly, the Adjustment-Threshold-Percentage sub-TLV trend, the Down-Adjustment-Threshold sub-TLV is included. Similarly,
specifies the threshold percentage for both upward and downward the Adjustment-Threshold-Percentage sub-TLV specifies the threshold
trend. If the operator would like to use a different adjustment percentage for both upward and downward trend. If the operator would
threshold percentage during the downward trend, the like to use a different adjustment threshold percentage during the
Down-Adjustment-Threshold-Percentage sub-TLV is included. It is downward trend, the Down-Adjustment-Threshold-Percentage sub-TLV is
worth noting that regardless of how the threshold are set, the included. It is worth noting that regardless of how the threshold
adjustment will not be made until at least one sample-interval simply are set, the adjustment will not be made until at least one sample-
because no sample will be made on which to base a comparison with a interval simply because no sample will be made on which to base a
threshold. 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 when MaxAvgBw is greater than or less bandwidth should be adjusted in upward or downward direction. This
than the current bandwidth reservation. sub-TLV specify the absolute value for Up-Adjustment-Threshold and
Down-Adjustment-Threshold when they are the same and the 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 Adjustment-Threshold sub-TLV format
The Type is 4, Length is 4 octets, and the value comprises of - The Type is 4, Length is 4 octets, and the value comprises of -
o Adjustment-Threshold: The absolute Adjustment-Threshold bandwidth o Adjustment-Threshold: The absolute Adjustment-Threshold bandwidth
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]), 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
previous value is 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 when MaxAvgBw is greater than or the LSP bandwidth should be adjusted in upward or downward direction.
less than the current bandwidth reservation. This sub-TLV specify the percentage value for Up-Adjustment-Threshold
and Down-Adjustment-Threshold when they are the same and 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 Adjustment-Threshold-Percentage sub-TLV format
The Type is 5, Length is 8 octets, and the value comprises of - The Type is 5, Length is 8 octets, and the value comprises of -
o Reserved: SHOULD be set to zero on transmission and MUST be o Reserved: MUST be set to zero on transmission and MUST be ignored
ignored on receipt. on receipt.
o Percentage: The Adjustment-Threshold value (7 bits), encoded in o Percentage: The Adjustment-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. The default value is 5 percent. to be invalid. The default value is 5 percent.
o Minimum-Threshold: The absolute Minimum-Threshold bandwidth value, o 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]),
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 least or above the minimum-threshold
before the bandwidth adjustment is made. The default value is 0. before the bandwidth adjustment is made. The default value is 0.
If the percentage difference between the current MaxAvgBw and the If the percentage absolute difference between the current MaxAvgBw
current bandwidth reservation is greater than or less than or equal and the current bandwidth reservation is greater than or equal to the
to the threshold percentage, the LSP bandwidth is adjusted to the threshold percentage, and the difference in the bandwidth is at least
current bandwidth demand (MaxAvgBw) (as long as the difference in the or above the Minimum-Threshold, the LSP bandwidth is adjusted to the
bandwidth is at least or above the Minimum-Threshold). current bandwidth demand (MaxAvgBw).
In case of an invalid value, the Sub-TLV MUST be ignored and the
previous value is 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 lesser than the current
bandwidth reservation. This parameter overwrites the Adjustment- bandwidth reservation. This parameter overrides the Adjustment-
Threshold for the downward trend. Threshold for the downward trend. This sub-TLV is used only when
there is a need for different threshold 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=6 | Length=4 | | Type=6 | Length=4 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Down-Adjustment-Threshold | | Down-Adjustment-Threshold |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Down-Adjustment-Threshold sub-TLV format Down-Adjustment-Threshold sub-TLV format
The Type is 6, Length is 4 octets, and the value comprises of - The Type is 6, Length is 4 octets, and the value comprises of -
o Down-Adjustment-Threshold: The absolute Down-Adjustment-Threshold o 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]), 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 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).
skipping to change at page 17, line 25 skipping to change at page 18, line 14
o Down-Adjustment-Threshold: The absolute Down-Adjustment-Threshold o 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]), 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 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
previous value is 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 lesser
than the current bandwidth reservation. This parameter overwrites than the current bandwidth reservation. This parameter overrides the
the Adjustment-Threshold-Percentage for the downward trend. Adjustment-Threshold-Percentage for the downward trend. This sub-TLV
is used only when there is a need for different threshold 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 Down-Adjustment-Threshold-Percentage sub-TLV format
The Type is 7, Length is 8 octets, and the value comprises of - The Type is 7, Length is 8 octets, and the value comprises of -
o Reserved: SHOULD be set to zero on transmission and MUST be o Reserved: MUST be set to zero on transmission and MUST be ignored
ignored on receipt. on receipt.
o Percentage: The Down-Adjustment-Threshold value (7 bits), encoded o Percentage: The Down-Adjustment-Threshold value (7 bits), encoded
in percentage (an integer from 1 to 100). The value 0 is in 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, o 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]),
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 least or above the minimum-threshold before the
bandwidth adjustment is made. The default value equals the bandwidth adjustment is made. The default value equals the
minimum-threshold for the adjustment-threshold-percentage. minimum-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, the LSP bandwidth is adjusted to the current threshold percentage, and the difference in the bandwidth is at least
bandwidth demand (MaxAvgBw) (as long as the difference in the or above the Minimum-Threshold, the LSP bandwidth is adjusted to the
bandwidth is at least or above the Minimum-Threshold). current bandwidth demand (MaxAvgBw).
In case of an invalid value, the Sub-TLV MUST be ignored and the
previous value is 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 specify 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
skipping to change at page 18, line 44 skipping to change at page 19, line 42
Minimum-Bandwidth sub-TLV format Minimum-Bandwidth sub-TLV format
The Type is 8, Length is 4 octets, and the value comprises of - The Type is 8, Length is 4 octets, and the value comprises of -
o Minimum-Bandwidth: The 4-octet bandwidth value encoded in IEEE o 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]), 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
previous value is 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 specify 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 |
skipping to change at page 19, line 19 skipping to change at page 20, line 21
Maximum-Bandwidth sub-TLV format Maximum-Bandwidth sub-TLV format
The Type is 9, Length is 4 octets, and the value comprises of - The Type is 9, Length is 4 octets, and the value comprises of -
o Maximum-Bandwidth: The 4-octet bandwidth value encoded in IEEE o 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]), 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
previous value is 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 the
overflow and underflow threshold parameters. An implementation MAY overflow and underflow threshold parameters. An implementation MAY
include sub-TLVs for an absolute value and/or a percentage for the include sub-TLVs for an absolute value and/or a percentage for the
threshold, in which case the bandwidth is immediately adjusted when threshold, in which case the bandwidth is immediately adjusted when
either of the threshold conditions is met consecutively for the given either of the threshold conditions is met consecutively for the given
count (as long as the difference in the bandwidth is at least or count (as long as the difference in the bandwidth is at least 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.
skipping to change at page 19, line 49 skipping to change at page 21, line 7
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Reserved | Count | | Reserved | Count |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Overflow-Threshold | | Overflow-Threshold |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Overflow-Threshold sub-TLV format Overflow-Threshold sub-TLV format
The Type is 10, Length is 8 octets, and the value comprises of - The Type is 10, Length is 8 octets, and the value comprises of -
o Reserved: SHOULD be set to zero on transmission and MUST be o Reserved: MUST be set to zero on transmission and MUST be ignored
ignored on receipt. on receipt.
o Count: The Overflow-Count value (5 bits), encoded in integer. The o Count: The Overflow-Count value (5 bits), encoded in integer. The
value 0 is considered to be invalid. The number of consecutive value 0 is considered to be invalid. The number of consecutive
samples for which the overflow condition MUST be met for the LSP samples for which the overflow condition MUST be met for the LSP
bandwidth to be immediately adjusted to the current bandwidth bandwidth to be immediately adjusted to the current bandwidth
demand, bypassing the (up) adjustment-interval. demand, bypassing the (up) adjustment-interval.
o Overflow-Threshold: The absolute Overflow-Threshold bandwidth o Overflow-Threshold: The absolute Overflow-Threshold bandwidth
value, encoded in IEEE floating point format (see value, encoded in IEEE floating point format (see
[IEEE.754.1985]), expressed in bytes per second. Refer to Section [IEEE.754.1985]), expressed in bytes per second. Refer to Section
3.1.2 of [RFC3471] for a table of commonly used values. If the 3.1.2 of [RFC3471] for a table of commonly used values. If the
increase of the current MaxAvgBw from the current bandwidth difference of the current MaxAvgBw from 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
overflow condition is met. overflow condition is met.
In case of an invalid value, the Sub-TLV MUST be ignored and the
previous value is 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 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
skipping to change at page 20, line 44 skipping to change at page 21, line 52
Overflow-Threshold-Percentage sub-TLV format Overflow-Threshold-Percentage sub-TLV format
The Type is 11, Length is 8 octets, and the value comprises of - The Type is 11, Length is 8 octets, and the value comprises of -
o Percentage: The Overflow-Threshold value (7 bits), encoded in o Percentage: The Overflow-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 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: SHOULD be set to zero on transmission and MUST be o Reserved: MUST be set to zero on transmission and MUST be ignored
ignored on receipt. on receipt.
o Count: The Overflow-Count value (5 bits), encoded in integer. The o Count: The Overflow-Count value (5 bits), encoded in integer. The
value 0 is considered to be invalid. The number of consecutive value 0 is considered to be invalid. The number of consecutive
samples for which the overflow condition MUST be met for the LSP samples for which the overflow condition MUST be met for the LSP
bandwidth to be immediately adjusted to the current bandwidth bandwidth to be immediately adjusted to the current bandwidth
demand, bypassing the (up) adjustment-interval. demand, bypassing the (up) adjustment-interval.
o Minimum-Threshold: The absolute Minimum-Threshold bandwidth value, o 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]),
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 least or above the minimum-threshold before the
bandwidth adjustment is made. bandwidth adjustment is made.
In case of an invalid value, the Sub-TLV MUST be ignored and the
previous value is 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 Underflow-Threshold sub-TLV format
The Type is 12, Length is 8 octets, and the value comprises of - The Type is 12, Length is 8 octets, and the value comprises of -
o Reserved: SHOULD be set to zero on transmission and MUST be o Reserved: MUST be set to zero on transmission and MUST be ignored
ignored on receipt. on receipt.
o Count: The Underflow-Count value (5 bits), encoded in integer. o Count: The Underflow-Count value (5 bits), encoded in 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 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 o 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]), expressed in bytes per second. Refer to Section [IEEE.754.1985]), expressed in bytes per second. Refer to Section
3.1.2 of [RFC3471] for a table of commonly used values. If the 3.1.2 of [RFC3471] for a table of commonly used values. If the
decrease of the current MaxAvgBw from the current bandwidth difference of the current MaxAvgBw from 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
underflow condition is met. underflow condition is met.
In case of an invalid value, the Sub-TLV MUST be ignored and the
previous value is 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 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
skipping to change at page 22, line 23 skipping to change at page 23, line 37
Underflow-Threshold-Percentage sub-TLV format Underflow-Threshold-Percentage sub-TLV format
The Type is 13, Length is 8 octets, and the value comprises of - The Type is 13, Length is 8 octets, and the value comprises of -
o Percentage: The Underflow-Threshold value (7 bits), encoded in o 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: SHOULD be set to zero on transmission and MUST be o Reserved: MUST be set to zero on transmission and MUST be ignored
ignored on receipt. on receipt.
o Count: The Underflow-Count value (5 bits), encoded in integer. o Count: The Underflow-Count value (5 bits), encoded in 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 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, o 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]),
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 least or above the minimum-threshold before the
bandwidth adjustment is made. bandwidth adjustment is made.
In case of an invalid value, the Sub-TLV MUST be ignored and the
previous value is 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 following:
o Requested Bandwidth: BANDWIDTH Object-Type value is 1. o Requested Bandwidth: BANDWIDTH Object-Type value is 1.
o Re-optimization Bandwidth: Bandwidth of an existing TE LSP for o Re-optimization Bandwidth: Bandwidth of an existing TE LSP for
which a re-optimization is requested. BANDWIDTH Object-Type value which a re-optimization is requested. BANDWIDTH Object-Type value
is 2. is 2.
skipping to change at page 24, line 4 skipping to change at page 25, line 21
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 overwhelmed state due to the auto-bandwidth feature.
Upon receipt of such notification, the peer SHOULD NOT send any PCEP An implementation needs to make an attempt to send this notification
messages related to auto-bandwidth adjustment. If a PCEP message (when overwhelmed by auto-bandwidth adjustments) unless sending this
related to auto-bandwidth is received during in overwhelmed state, it notification would only serve to increase the load further. Note that
MUST be ignored. when the notification is not received the PCEP speaker would continue
to request bandwidth adjustments even when they could not be handled
in a timely fashion.
Upon receipt of auto-bandwidth overwhelm notification, the peer
SHOULD NOT send any PCEP messages related to auto-bandwidth
adjustment. If a PCEP message related to auto-bandwidth adjustment
is received during in overwhelmed state, it MUST be ignored.
o When a PCEP speaker is overwhelmed, it SHOULD notify its peer by o 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 = TBD3 (Auto-
bandwidth Overwhelm State) and Notification Value = 1 (Entering bandwidth Overwhelm State) and Notification-Value = 1 (Entering
auto-bandwidth overwhelm state). Optionally, OVERLOADED-DURATION auto-bandwidth overwhelm state). Optionally, OVERLOADED-DURATION
TLV [RFC5440] MAY be included that specifies the time period TLV [RFC5440] MAY be included that specifies the time period
during which no further PCEP messages related to auto-bandwidth during 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 o 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 peer 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 = TBD3 (Auto-bandwidth Overwhelm State) and Notification Value = 2
(Clearing auto-bandwidth overwhelm state). (Clearing auto-bandwidth overwhelm state). A PCEP speaker SHOULD
send such notification to all peers to with a Notification message
(Notification-Type=TBD3, Notification-Value=1) was sent earlier
unless an OVERLOADED-DURATION TLV was included and the PCEP
speakers wishes for the peer to wait for the expiration of that
period of time before receiving further PCEP messages related to
auto-bandwidth adjustment.
When Auto-Bandwidth feature is deployed, a PCE can send this When Auto-Bandwidth feature is deployed, a PCE can send this
notification to PCC when a PCC is reporting frequent auto-bandwidth notification to PCC when a PCC is reporting frequent auto-bandwidth
adjustments. If a PCC is overwhelmed with re-signaling, it can also adjustments. If a PCC is overwhelmed with re-signaling, 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 overwhelm
state. state.
Some dampening notification procedure (as per [RFC5440]) to avoid
oscillations of the overwhelm state is RECOMMENDED. On receipt of an
auto-bandwidth overwhelm notification from the PCE, a PCC should
consider the impact on the entire network. Moving the delegations of
auto-bandwidth enabled LSP to another PCE could cause further
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 per LSP (at PCC
(head-end of the LSP) or PCE) and the values for auto-bandwidth (head-end of the LSP) or PCE) and the values for auto-bandwidth
parameters e.g. sample-interval, adjustment-interval (up/down), parameters e.g. sample-interval, adjustment-interval (up/down),
minimum-bandwidth, maximum-bandwidth, adjustment-threshold (up/down) minimum-bandwidth, maximum-bandwidth, adjustment-threshold (up/down)
SHOULD be configurable by an operator. SHOULD be configurable by an operator.
The Maximum-Bandwidth (and Minimum-Bandwidth) should be set to
acceptable limit to avoid impact on the rest of the MPLS-TE domain.
The operator should make sure that the Overflow-Threshold is greater
than or at least equal to the Up-Adjustment-Threshold. And similarly,
make sure that the Underflow-Threshold is 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 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 [I-D.ietf-pce-pcep-yang] provides for both configuration of PCEP as
well as operational management. These could be enhanced to provide well as operational management. These could be enhanced to provide
controls and indicators for support of auto-bandwidth feature. controls and indicators for support of auto-bandwidth feature.
Support for various configuration knobs as well as counters of Support for various configuration knobs as well as counters of
messages sent/received containing the TLVs defined in this document messages sent/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].
skipping to change at page 25, line 21 skipping to change at page 27, line 18
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. Verify 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
previous value would be maintained. In such case the implementation
SHOULD log the event.
6.5. Requirements On Other Protocols 6.5. Requirements On 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 on 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 auto-bandwidth feature. For each LSP
enabled with auto-bandwidth feature there is an extra load on PCC, as enabled with auto-bandwidth feature there is an extra load on PCC, as
it needs to monitor the traffic and report the calculated bandwidth it needs to monitor the traffic and report the calculated bandwidth
to be adjusted to the PCE. The PCE further re-compute paths based on to be adjusted to the PCE. The PCE further re-compute paths based on
the requested bandwidth and update the path to the PCC, which in the requested bandwidth and update the path to the PCC, which in
turns triggers the re-signalling of the path. All these steps adds turns triggers the re-signaling of the path. All these steps adds
extra load and churn in the network and thus operator needs to take extra load and churn in the network and thus operator needs to take
due care while enabling this features on a number of LSPs. due care while enabling this 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 MAY also allow sending a notification when a peer. An implementation SHOULD also allow sending a notification
PCEP speaker is overwhelmed or the rate of messages reach a when a PCEP speaker is overwhelmed or the rate of messages reach a
threshold. 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 minute) is used, as a 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 out
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 new security BANDWIDTH-ATTRIBUTES sub-TLVs which do not add any substantial new
concerns beyond those already discussed in [RFC8231] and [RFC8281] security concerns beyond those already discussed in [RFC8231] and
for stateful PCE operations. As per [RFC8231], it is RECOMMENDED [RFC8281] for stateful PCE operations. As per [RFC8231], it is
that these PCEP extensions only be activated on authenticated and RECOMMENDED that these PCEP extensions only be activated on
encrypted sessions across PCEs and PCCs belonging to the same authenticated and encrypted sessions across PCEs and PCCs belonging
administrative authority, using Transport Layer Security (TLS) to the same administrative authority, using Transport Layer Security
[RFC8253], as per the recommendations and best current practices in (TLS) [RFC8253], as per the recommendations and best current
[RFC7525] (unless explicitly set aside in [RFC8253]). practices in BCP 195 [RFC7525] (unless explicitly set aside in
[RFC8253]).
Incorrect auto-bandwidth parameters in the AUTO-BANDWIDTH-ATTRIBUTES
sub-TLVs could have an adverse effect on the LSP as well as on the
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 is requested
to make the following allocations from the "PCEP TLV Type Indicators" to make the following allocations from the "PCEP TLV Type Indicators"
sub-registry of the PCEP Numbers registry, as follows: sub-registry of the PCEP Numbers registry, as follows:
Value Name Reference Value Name Reference
----------------------------------------------------------------- -----------------------------------------------------------------
TBD2 AUTO-BANDWIDTH-CAPABILITY [This document] TBD2 AUTO-BANDWIDTH-CAPABILITY [This document]
TBD1 AUTO-BANDWIDTH-ATTRIBUTES [This document] TBD1 AUTO-BANDWIDTH-ATTRIBUTES [This document]
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 is requested to create a sub-registry to manage the Flag field
of the AUTO-BANDWIDTH-CAPABILITY TLV. of the AUTO-BANDWIDTH-CAPABILITY TLV within the "Path Computation
Element 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) o Bit number (counting from bit 0 as the most significant bit)
o Capability description o Capability description
o Defining RFC o Defining RFC
There is no bit defined for the AUTO-BANDWIDTH-CAPABILITY TLV Object The initial contents of the sub-registry are empty, with all bits
flag field in this document. 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" is requested to create an "AUTO-BANDWIDTH-ATTRIBUTES Sub-TLV Types"
sub-registry within the "Path Computation Element Protocol (PCEP) sub-registry within the "Path Computation Element Protocol (PCEP)
Numbers" registry to manage the type indicator space for sub-TLVs of Numbers" registry to manage the type indicator space for sub-TLVs of
the AUTO-BANDWIDTH-ATTRIBUTES TLV. The valid range of values in the the AUTO-BANDWIDTH-ATTRIBUTES TLV. The valid range of values in the
registry is 0-65535. IANA is requested to initialize the registry registry is 0-65535. IANA is requested to initialize the registry
with the following values. All other values in the registry should with the following values. All other values in the registry should
skipping to change at page 29, line 16 skipping to change at page 31, line 16
9.1. Normative References 9.1. Normative References
[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, March 1997.
[RFC5440] Vasseur, JP. and JL. Le Roux, "Path Computation Element [RFC5440] Vasseur, JP. and JL. Le Roux, "Path Computation Element
(PCE) Communication Protocol (PCEP)", RFC 5440, March (PCE) Communication Protocol (PCEP)", RFC 5440, March
2009. 2009.
[RFC7525] Sheffer, Y., Holz, R. and P. Saint-Andre, "Recommendations
for Secure Use of Transport Layer Security (TLS) and
Datagram Transport Layer Security (DTLS)", BCP 195, RFC
7525, DOI 10.17487/RFC7525, May 2015.
[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, "Pah
Computation Element Communication Protocol (PCEP) Computation Element Communication Protocol (PCEP)
Extensions for Stateful PCE", RFC 8231, DOI Extensions for Stateful PCE", RFC 8231, DOI
10.17487/RFC8231, September 2017, 10.17487/RFC8231, September 2017,
<https://www.rfc-editor.org/infor/rfc8231>. <https://www.rfc-editor.org/infor/rfc8231>.
[RFC8253] Lopez, D., Dios, O., Wu, W., and D. Dhody, "PCEPS: Usage
of TLS to Provide a Secure Transport for the Path
Computation Element Communication Protocol (PCEP)", RFC
8253, October 2017,
<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
[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., "Generalized Multi-Protocol Label Switching
(GMPLS) Signaling Functional Description", RFC 3471, (GMPLS) Signaling Functional Description", RFC 3471,
January 2003. January 2003.
[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", RFC
7420, December 2014. 7420, December 2014.
[RFC7525] Sheffer, Y., Holz, R. and P. Saint-Andre, "Recommendations
for Secure Use of Transport Layer Security (TLS) and
Datagram Transport Layer Security (DTLS)", BCP 195, RFC
7525, DOI 10.17487/RFC7525, May 2015.
[RFC8051] Zhang, X. and I. Minei, "Applicability of a Stateful Path [RFC8051] Zhang, X. and I. Minei, "Applicability of a Stateful Path
Computation Element (PCE)", RFC 8051, January 2017. Computation Element (PCE)", RFC 8051, January 2017.
[RFC8253] Lopez, D., Dios, O., Wu, W., and D. Dhody, "PCEPS: Usage
of TLS to Provide a Secure Transport for the Path
Computation Element Communication Protocol (PCEP)", RFC
8253, October 2017,
<https://www.rfc-editor.org/info/rfc8253>.
[I-D.ietf-pce-pcep-yang] Dhody, D., Hardwick, J., Beeram, V., and J. [I-D.ietf-pce-pcep-yang] Dhody, D., Hardwick, J., Beeram, V., and J.
Tantsura, "A YANG Data Model for Path Computation Element Tantsura, "A YANG Data Model for Path Computation Element
Communications Protocol (PCEP)", draft-ietf-pce-pcep-yang Communications Protocol (PCEP)", draft-ietf-pce-pcep-yang
(work in progress). (work in progress).
[IEEE.754.1985] Institute of Electrical and Electronics Engineers,
"Standard for Binary Floating-Point Arithmetic", IEEE
Standard 754, August 1985.
Acknowledgments Acknowledgments
Authors would like to thank Robert Varga, Venugopal Reddy, Reeja 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
Danyliw for the IESG review.
Contributors' Addresses Contributors' Addresses
He Zekun He Zekun
Tencent Holdings Ltd, Tencent Holdings Ltd,
Shenzhen P.R.China Shenzhen P.R.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
Futurewei Technologies SKKU
Futurewei Technologies
5340 Legacy Drive, Building 3
Plano, TX 75023
USA
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, Karnataka 560066
India India
 End of changes. 91 change blocks. 
234 lines changed or deleted 331 lines changed or added

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