draft-ietf-pce-stateful-pce-auto-bandwidth-03.txt   draft-ietf-pce-stateful-pce-auto-bandwidth-04.txt 
PCE Working Group D. Dhody PCE Working Group D. Dhody
Internet-Draft U. Palle Internet-Draft U. Palle
Intended status: Standards Track Huawei Technologies Intended status: Standards Track Huawei Technologies
Expires: September 14, 2017 R. Singh Expires: October 19, 2017 R. Singh
Juniper Networks Juniper Networks
R. Gandhi R. Gandhi
Cisco Systems, Inc. Cisco Systems, Inc.
L. Fang L. Fang
eBay eBay
March 13, 2017 April 17, 2017
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-03 draft-ietf-pce-stateful-pce-auto-bandwidth-04
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 22 skipping to change at page 2, line 25
to this document. Code Components extracted from this document must to this document. Code Components extracted from this document must
include Simplified BSD License text as described in Section 4.e of include Simplified BSD License text as described in Section 4.e of
the Trust Legal Provisions and are provided without warranty as the Trust Legal Provisions and are provided without warranty as
described in the Simplified BSD License. described in the Simplified BSD License.
Table of Contents Table of Contents
1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 3 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 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. Terminology . . . . . . . . . . . . . . . . . . . . . . . 4 2.2. Abbreviations . . . . . . . . . . . . . . . . . . . . . . 5
3. Requirements for PCEP Extensions . . . . . . . . . . . . . . . 5 2.3. Terminology . . . . . . . . . . . . . . . . . . . . . . . 5
4. Architectural Overview . . . . . . . . . . . . . . . . . . . . 6 3. Requirements for PCEP Extensions . . . . . . . . . . . . . . . 7
4.1. Auto-Bandwidth Overview . . . . . . . . . . . . . . . . . 6 4. Architectural Overview . . . . . . . . . . . . . . . . . . . . 7
4.1. Auto-Bandwidth Overview . . . . . . . . . . . . . . . . . 7
4.2. Auto-bandwidth Theory of Operation . . . . . . . . . . . . 8 4.2. Auto-bandwidth Theory of Operation . . . . . . . . . . . . 8
4.3. Scaling Considerations . . . . . . . . . . . . . . . . . . 9 4.3. Scaling Considerations . . . . . . . . . . . . . . . . . . 9
5. Extensions to the PCEP . . . . . . . . . . . . . . . . . . . . 9 5. Extensions to the PCEP . . . . . . . . . . . . . . . . . . . . 9
5.1. Capability Advertisement . . . . . . . . . . . . . . . . . 9 5.1. Capability Advertisement . . . . . . . . . . . . . . . . . 9
5.1.1 AUTO-BANDWIDTH-CAPABILITY TLV . . . . . . . . . . . . . 10 5.1.1. AUTO-BANDWIDTH-CAPABILITY TLV . . . . . . . . . . . . 10
5.2. AUTO-BANDWIDTH-ATTRIBUTE TLV . . . . . . . . . . . . . . . 10 5.2. AUTO-BANDWIDTH-ATTRIBUTES TLV . . . . . . . . . . . . . . 10
5.2.1. Sample-Interval sub-TLV . . . . . . . . . . . . . . . 12 5.2.1. Sample-Interval sub-TLV . . . . . . . . . . . . . . . 12
5.2.2. Adjustment Interval . . . . . . . . . . . . . . . . . 12 5.2.2. Adjustment Intervals . . . . . . . . . . . . . . . . . 12
5.2.2.1. Adjustment-Interval sub-TLV . . . . . . . . . . . 12 5.2.2.1. Adjustment-Interval sub-TLV . . . . . . . . . . . 12
5.2.2.2. Down-Adjustment-Interval sub-TLV . . . . . . . . . 13 5.2.2.2. Down-Adjustment-Interval sub-TLV . . . . . . . . . 13
5.2.3. Adjustment Threshold . . . . . . . . . . . . . . . . . 13 5.2.3. Adjustment Thresholds . . . . . . . . . . . . . . . . 13
5.2.3.1. Adjustment-Threshold sub-TLV . . . . . . . . . . . 13 5.2.3.1. Adjustment-Threshold sub-TLV . . . . . . . . . . . 14
5.2.3.2. Adjustment-Threshold-Percentage sub-TLV . . . . . 14 5.2.3.2. Adjustment-Threshold-Percentage sub-TLV . . . . . 14
5.2.3.3. Down-Adjustment-Threshold sub-TLV . . . . . . . . 15 5.2.3.3. Down-Adjustment-Threshold sub-TLV . . . . . . . . 15
5.2.3.4. Down-Adjustment-Threshold-Percentage sub-TLV . . . 15 5.2.3.4. Down-Adjustment-Threshold-Percentage sub-TLV . . . 15
5.2.4. Minimum and Maximum Bandwidth Values . . . . . . . . . 16 5.2.4. Minimum and Maximum Bandwidth Values . . . . . . . . . 16
5.2.4.1. Minimum-Bandwidth sub-TLV . . . . . . . . . . . . 16 5.2.4.1. Minimum-Bandwidth sub-TLV . . . . . . . . . . . . 16
5.2.4.2. Maximum-Bandwidth sub-TLV . . . . . . . . . . . . 16 5.2.4.2. Maximum-Bandwidth sub-TLV . . . . . . . . . . . . 17
5.2.5. Overflow and Underflow Conditions . . . . . . . . . . 17 5.2.5. Overflow and Underflow Conditions . . . . . . . . . . 17
5.2.5.1. Overflow-Threshold sub-TLV . . . . . . . . . . . . 17 5.2.5.1. Overflow-Threshold sub-TLV . . . . . . . . . . . . 17
5.2.5.2. Overflow-Threshold-Percentage sub-TLV . . . . . . 18 5.2.5.2. Overflow-Threshold-Percentage sub-TLV . . . . . . 18
5.2.5.3. Underflow-Threshold sub-TLV . . . . . . . . . . . 18 5.2.5.3. Underflow-Threshold sub-TLV . . . . . . . . . . . 19
5.2.5.4. Underflow-Threshold-Percentage sub-TLV . . . . . . 19 5.2.5.4. Underflow-Threshold-Percentage sub-TLV . . . . . . 19
5.3. BANDWIDTH Object . . . . . . . . . . . . . . . . . . . . . 20 5.3. BANDWIDTH Object . . . . . . . . . . . . . . . . . . . . . 20
5.4. The PCInitiate Message . . . . . . . . . . . . . . . . . . 20 5.4. The PCInitiate Message . . . . . . . . . . . . . . . . . . 20
5.5. The PCUpd Message . . . . . . . . . . . . . . . . . . . . 20 5.5. The PCUpd Message . . . . . . . . . . . . . . . . . . . . 21
5.6. The PCRpt Message . . . . . . . . . . . . . . . . . . . . 21 5.6. The PCRpt Message . . . . . . . . . . . . . . . . . . . . 21
5.7. The PCNtf Message . . . . . . . . . . . . . . . . . . . . 21 5.7. The PCNtf Message . . . . . . . . . . . . . . . . . . . . 21
6. Security Considerations . . . . . . . . . . . . . . . . . . . 22 6. Security Considerations . . . . . . . . . . . . . . . . . . . 22
7. Manageability Considerations . . . . . . . . . . . . . . . . . 22 7. Manageability Considerations . . . . . . . . . . . . . . . . . 22
7.1. Control of Function and Policy . . . . . . . . . . . . . . 22 7.1. Control of Function and Policy . . . . . . . . . . . . . . 22
7.2. Information and Data Models . . . . . . . . . . . . . . . 22 7.2. Information and Data Models . . . . . . . . . . . . . . . 23
7.3. Liveness Detection and Monitoring . . . . . . . . . . . . 23 7.3. Liveness Detection and Monitoring . . . . . . . . . . . . 23
7.4. Verify Correct Operations . . . . . . . . . . . . . . . . 23 7.4. Verify Correct Operations . . . . . . . . . . . . . . . . 23
7.5. Requirements On Other Protocols . . . . . . . . . . . . . 23 7.5. Requirements On Other Protocols . . . . . . . . . . . . . 23
7.6. Impact On Network Operations . . . . . . . . . . . . . . . 23 7.6. Impact On Network Operations . . . . . . . . . . . . . . . 23
8. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 24 8. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 24
8.1. PCEP TLV Type Indicators . . . . . . . . . . . . . . . . . 24 8.1. PCEP TLV Type Indicators . . . . . . . . . . . . . . . . . 24
8.2. AUTO-BANDWIDTH-CAPABILITY TLV Flag Field . . . . . . . . . 24 8.2. AUTO-BANDWIDTH-CAPABILITY TLV Flag Field . . . . . . . . . 24
8.3. AUTO-BANDWIDTH-ATTRIBUTE Sub-TLV . . . . . . . . . . . . . 24 8.3. AUTO-BANDWIDTH-ATTRIBUTES Sub-TLV . . . . . . . . . . . . 24
8.4. Error Object . . . . . . . . . . . . . . . . . . . . . . . 25 8.4. Error Object . . . . . . . . . . . . . . . . . . . . . . . 25
8.5. Notification Object . . . . . . . . . . . . . . . . . . . 25 8.5. Notification Object . . . . . . . . . . . . . . . . . . . 25
9. References . . . . . . . . . . . . . . . . . . . . . . . . . . 26 9. References . . . . . . . . . . . . . . . . . . . . . . . . . . 26
9.1. Normative References . . . . . . . . . . . . . . . . . . . 26 9.1. Normative References . . . . . . . . . . . . . . . . . . . 26
9.2. Informative References . . . . . . . . . . . . . . . . . . 26 9.2. Informative References . . . . . . . . . . . . . . . . . . 26
Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . . . 28 Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . . . 28
Contributors' Addresses . . . . . . . . . . . . . . . . . . . . . 28 Contributors' Addresses . . . . . . . . . . . . . . . . . . . . . 28
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . . 29 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . . 29
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 Control Element (PCE), or between PCE and PCE, that enables Path Control 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).
[I-D.ietf-pce-stateful-pce] specifies extensions to PCEP to enable [I-D.ietf-pce-stateful-pce] specifies extensions to PCEP to enable
stateful control of MPLS TE LSPs. It describes two mode of stateful control of MPLS TE LSPs. It describes two mode of
operations - Passive stateful PCE and Active stateful PCE. Further operations - Passive stateful PCE and Active stateful PCE. Further,
[I-D.ietf-pce-pce-initiated-lsp] describes the setup, maintenance and [I-D.ietf-pce-pce-initiated-lsp] describes the setup, maintenance and
teardown of PCE-Initiated LSPs for the stateful PCE model. In this teardown of PCE-Initiated LSPs for the stateful PCE model. In this
document, the focus is on Active stateful PCE where the LSPs are document, the focus is on Active stateful PCE where the LSPs are
controlled by the PCE. 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 certain bandwidth may require to adjust the bandwidth reserved with certain bandwidth may require to adjust the bandwidth reserved
in the network automatically. The head-end Label Switch Router (LSR) in the network automatically. The head-end Label Switch Router (LSR)
needs to monitor the actual bandwidth demand of the LSP and adjust needs to monitor the actual bandwidth demand of the LSP and adjust
the LSP bandwidth reservation periodically. This feature is commonly the LSP bandwidth reservation periodically. This feature is commonly
referred to as Auto-Bandwidth. referred to as Auto-Bandwidth. Enabling Auto-Bandwidth feature on an
LSP results in the head-end LSR automatically adjusting the LSP
Enabling Auto-Bandwidth feature on an LSP results in the head-end LSR bandwidth reservation based on the traffic flowing through the LSP.
automatically adjusting the LSP bandwidth reservation based on the The initial LSP bandwidth can be set to an arbitrary value (including
traffic flowing through the LSP. The initial LSP bandwidth can be zero), in practice, it can be operator expected value based on design
set to an arbitrary value (including zero), in practice, it can be and planning. Once the LSP is set-up, the head-end monitors the
operator expected value based on design and planning. Once the LSP traffic flow on the LSP and adjusts the bandwidth reservation
is set-up, the head-end monitors the traffic flow on the LSP and periodically. The Auto-Bandwidth feature is described in detail in
adjusts the bandwidth every adjustment-interval. The bandwidth Section 4 of this document.
adjustment uses the make-before-break signaling method so that there
is no disruption to the traffic flow. The Auto-Bandwidth feature is
described in detail in Section 4.1 of this document.
The PCC (head-end of the LSP) collects the traffic rate samples The PCC (head-end of the LSP) collects the traffic rate samples
flowing through the LSP and calculates the new adjusted bandwidth. flowing through the LSP and calculates the new adjusted bandwidth.
The PCC reports the calculated bandwidth to be adjusted to the PCE. The PCC reports the calculated bandwidth to be adjusted to the PCE.
This is similar to a passive stateful PCE model, while the passive This is similar to a passive stateful PCE model, while the passive
stateful PCE uses path request/reply mechanism, the active stateful stateful PCE uses path request/reply mechanism, the active stateful
PCE uses report/update mechanism to adjust the LSP bandwidth. In PCE uses report/update mechanism to adjust the LSP bandwidth. In
case of PCE-Initiated LSP, the PCC is requested during the LSP case of PCE-Initiated LSP, the PCC is requested during the LSP
initiation to monitor and calculate the new adjusted bandwidth. initiation to monitor and calculate the new adjusted bandwidth.
[RFC8051] describes the use-case for Auto-Bandwidth adjustment for [RFC8051] describes the use-case for Auto-Bandwidth adjustment for
passive and active stateful PCE. passive and active stateful PCE.
The document [I-D.gandhi-pce-pm] describes the PCEP extensions for The document [I-D.gandhi-pce-pm] describes the PCEP extensions for
reporting the performance measurements to the PCE, and includes the reporting the performance measurements to the PCE, and includes the
real-time bandwidth usage information of a TE LSP. Those extensions real-time bandwidth utilization information of a TE LSP. Those
can be used to implement the auto-bandwidth feature on a stateful extensions can be used to implement the auto-bandwidth feature on a
PCE, i.e. can be used to calculate the new bandwidth to be adjusted stateful PCE, i.e. can be used to calculate the new bandwidth to be
on the stateful PCE. adjusted on the stateful PCE.
This document defines the extensions needed to support Auto-Bandwidth This document defines the extensions needed to support Auto-Bandwidth
features on the LSPs in a active stateful PCE model using PCEP where features on the LSPs in a active stateful PCE model using PCEP where
the bandwidth to be adjusted is calculated on the PCC (the head-end the bandwidth to be adjusted is calculated on the PCC (head-end of
of the LSP). the LSP).
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", "MAY", and "OPTIONAL" in this "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this
document are to be interpreted as described in [RFC2119]. document are to be interpreted as described in [RFC2119].
2.2. Terminology 2.2. Abbreviations
The following terminology is used in this document.
Active Stateful PCE: PCE that uses tunnel state information learned
from PCCs to optimize path computations. Additionally, it
actively updates tunnel parameters in those PCCs that delegated
control over their tunnels to the PCE.
Delegation: An operation to grant a PCE temporary rights to modify a PCC: Path Computation Client.
subset of tunnel parameters on one or more PCC's tunnels. Tunnels
are delegated from a PCC to a PCE.
PCC: Path Computation Client. Any client application requesting a PCE: Path Computation Element.
path computation to be performed by a Path Computation Element.
PCE: Path Computation Element. An entity (component, application, PCEP: Path Computation Element Communication Protocol.
or network node) that is capable of computing a network path or
route based on a network graph and applying computational
constraints.
TE LSP: Traffic Engineering Label Switched Path. TE LSP: Traffic Engineering Label Switched Path.
Note the Auto-Bandwidth feature specific terms are defined in Section 2.3. Terminology
4.1.
3. Requirements for PCEP Extensions
The PCEP speaker supporting this document MUST have a mechanism to
advertise the automatic bandwidth adjustment capability.
Additional auto-bandwidth PCEP extensions required are summarized in
the following table.
+---------------------------------+---------------------------------+
| PCC Initiated | PCE Initiated |
+---------------------------------+---------------------------------+
| | |
| PCC monitors the traffic | At the time of initiation, |
| and reports the calculated | PCE request PCC to monitor |
| bandwidth to be adjusted | the traffic and report the |
| to the PCE. | calculated bandwidth to be |
| | adjusted to the PCE. |
| | |
| Extension is needed for PCC | Extension is needed for PCE |
| to pass on the adjustment | to pass on the adjustment |
| parameters at the time of | parameters at the time of |
| Delegation. | Initiation. |
| | |
+---------------------------------+---------------------------------+
Table 1: Auto-Bandwidth PCEP extensions
Further Auto-Bandwidth deployment considerations are summarized
below:
o It is required to identify and inform the PCEP peer, the LSP that
are enabled with Auto-Bandwidth feature. Not all LSPs in some
deployments would like their bandwidth to be dependent on the
real-time bandwidth usage but be constant as set by the operator.
o Further for the LSP with Auto-Bandwidth feature enabled, an
operator should be able to specify the adjustment parameters (i.e.
configuration knobs) to control this feature (e.g. minimum/
maximum bandwidth range) and PCEP peer should be informed.
4. Architectural Overview
4.1. Auto-Bandwidth Overview
Auto-Bandwidth feature allows automatic and dynamic adjustment of the The reader is assumed to be familiar with the terminology defined in
reserved bandwidth of an LSP over time, i.e. without network operator [RFC5440], [I-D.ietf-pce-pce-initiated-lsp], and [I-D.ietf-pce-
intervention. The new bandwidth reservation is determined by stateful-pce].
sampling the actual traffic flowing through the LSP. If the traffic
flowing through the LSP is lower than the configured or current
bandwidth of the LSP, the extra bandwidth is being reserved
needlessly and being wasted. Conversely, if the actual traffic
flowing through the LSP is higher than the configured or current
bandwidth of the LSP, it can potentially cause congestion or packet
loss in the network. With Auto-Bandwidth feature, the LSP bandwidth
can be set to some arbitrary value (including zero) during initial
setup time, and it will be periodically adjusted over time based on
the actual bandwidth demand.
Note the following definitions of the Auto-Bandwidth terms: 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 during a time represents the current traffic bandwidth demand during a time
interval. This is the maximum value of the averaged traffic interval. This is the maximum value of the traffic bandwidth rate
bandwidth rate in a given adjustment-interval. samples (Bandwidth-Samples) in a given Adjustment-Interval.
Adjusted Bandwidth: This is the Auto-Bandwidth computed bandwidth Adjusted Bandwidth: This is the Auto-Bandwidth computed bandwidth
that needs to be adjusted for the LSP. that is used to adjust the bandwidth reservation of the LSP.
Sample-Interval: The periodic time interval at which the traffic Sample-Interval: The periodic time interval at which the measured
rate is collected as a sample. traffic rate is collected as a Bandwidth-Sample.
Bandwidth-Sample: The bandwidth sample collected at every sample Bandwidth-Sample: The bandwidth sample of the measured traffic rate
interval to measure the traffic rate. collected at every Sample-Interval.
Maximum-Bandwidth: The maximum bandwidth that can be reserved for
the LSP.
Minimum-Bandwidth: The minimum bandwidth that can be reserved for
the LSP.
Up-Adjustment-Interval: The periodic time interval at which the Up-Adjustment-Interval: The periodic time interval at which the
bandwidth adjustment should be made using the MaxAvgBw, when bandwidth adjustment should be made using the MaxAvgBw, when
MaxAvgBw is greater than the current bandwidth reservation. MaxAvgBw is greater than the current bandwidth reservation.
Down-Adjustment-Interval: The periodic time interval at which the Down-Adjustment-Interval: The periodic time interval at which the
bandwidth adjustment should be made using the MaxAvgBw, when bandwidth adjustment should be made using the MaxAvgBw, when
MaxAvgBw is lesser than the current bandwidth reservation. MaxAvgBw is lesser than the current bandwidth reservation.
Maximum-Bandwidth: The maximum bandwidth that can be reserved for Up-Adjustment-Threshold: This parameter is used to decide when the
the LSP.
Minimum-Bandwidth: The minimum bandwidth that can be reserved for
the LSP.
Up-Adjustment-Threshold: This value is used to decide when the
bandwidth should be adjusted. If the percentage or absolute bandwidth should be adjusted. If the percentage or absolute
difference between the current MaxAvgBw and the current bandwidth difference between the current MaxAvgBw and the current bandwidth
reservation is greater than or equal to the threshold value, the reservation is greater than or equal to the threshold value, the
LSP bandwidth is adjusted (upsized) to the current bandwidth LSP bandwidth is adjusted (upsized) to the current bandwidth
demand (Adjusted Bandwidth) at the up-adjustment-interval expiry. demand (Adjusted Bandwidth) at the Up-Adjustment-Interval expiry.
Down-Adjustment-Threshold: This value is used to decide when the Down-Adjustment-Threshold: This parameter is used to decide when the
bandwidth should be adjusted. If the percentage or absolute 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 value is used to decide when the bandwidth Overflow-Count: This parameter is used to decide when the bandwidth
should be adjusted when there is a sudden increase in traffic should be adjusted when there is a sudden increase in traffic
demand. This value indicates how many times consecutively, the demand. This value indicates how many times consecutively, the
percentage or absolute difference between the current MaxAvgBw and percentage or absolute difference between the current MaxAvgBw and
the current bandwidth reservation is greater than or equal to the the current bandwidth reservation is greater than or equal to the
Overflow-Threshold value. Overflow-Threshold value.
Overflow-Threshold: This value is used to decide when the bandwidth Overflow-Threshold: This parameter is used to decide when the
should be adjusted when there is a sudden increase in traffic bandwidth should be adjusted when there is a sudden increase in
demand. If the percentage or absolute difference between the traffic demand. If the percentage or absolute difference between
current MaxAvgBw and the current bandwidth reservation is greater the current MaxAvgBw and the current bandwidth reservation is
than or equal to the threshold value, the overflow-condition is greater than or equal to the threshold value, the overflow
set to be met. The LSP bandwidth is adjusted to the current condition is set to be met. The LSP bandwidth is adjusted to the
bandwidth demand bypassing the adjustment-interval if the current bandwidth demand bypassing the Up-Adjustment-Interval if
overflow-condition is met consecutively for the Overflow-Count. the overflow condition is met consecutively for the Overflow-
Count.
Underflow-Count: This value is used to decide when the bandwidth Underflow-Count: This parameter is used to decide when the bandwidth
should be adjusted when there is a sudden decrease in traffic should be adjusted when there is a sudden decrease in traffic
demand. This value indicates how many times consecutively, the demand. This value indicates how many times consecutively, the
percentage or absolute difference between the current MaxAvgBw and percentage or absolute difference between the current MaxAvgBw and
the current bandwidth reservation is greater than or equal to the the current bandwidth reservation is greater than or equal to the
Underflow-Threshold value. Underflow-Threshold value.
Underflow-Threshold: This value is used to decide when the bandwidth Underflow-Threshold: This parameter is used to decide when the
should be adjusted when there is a sudden decrease in traffic bandwidth should be adjusted when there is a sudden decrease in
demand. If the percentage or absolute difference between the traffic demand. If the percentage or absolute difference between
current MaxAvgBw and the current bandwidth reservation is greater the current MaxAvgBw and the current bandwidth reservation is
than or equal to the threshold value, the underflow-condition is greater than or equal to the threshold value, the underflow
set to be met. The LSP bandwidth is adjusted to the current condition is set to be met. The LSP bandwidth is adjusted to the
bandwidth demand bypassing the adjustment-interval if the current bandwidth demand bypassing the Down-Adjustment-Interval if
underflow-condition is met consecutively for the Underflow-Count. the underflow condition is met consecutively for the Underflow-
Count.
3. Requirements for PCEP Extensions
The PCEP extensions required for auto-bandwidth are summarized in the
following table.
+---------------------------------+---------------------------------+
| PCC Initiated | PCE Initiated |
+---------------------------------+---------------------------------+
| | |
| PCC monitors the traffic | At the time of initiation, |
| and reports the calculated | PCE request PCC to monitor |
| bandwidth to be adjusted | the traffic and report the |
| to the PCE. | calculated bandwidth to be |
| | adjusted to the PCE. |
| | |
| Extension is needed for PCC | Extension is needed for PCE |
| to pass on the adjustment | to pass on the adjustment |
| parameters at the time of | parameters at the time of |
| Delegation. | Initiation. |
| | |
+---------------------------------+---------------------------------+
Table 1: Auto-Bandwidth PCEP extensions
The PCEP speaker supporting this document must have a mechanism to
advertise the automatic bandwidth adjustment capability for both PCC-
Initiated and PCE-Initiated LSPs.
Auto-bandwidth deployment considerations for PCEP extensions are
summarized below:
o It is required to identify and inform the PCC, the LSP that are
enabled with Auto-Bandwidth feature. Not all LSPs in some
deployments would like their bandwidth to be dependent on the
real-time bandwidth usage but be constant as set by the operator.
o In addition, an operator should be able to specify the auto-
bandwidth adjustment parameters (i.e. configuration knobs) to
control this feature (e.g. minimum/ maximum bandwidth range). The
PCC should be informed about these adjustment parameters.
4. Architectural Overview
4.1. Auto-Bandwidth Overview
Auto-Bandwidth feature allows automatic and dynamic adjustment of the
reserved bandwidth of an LSP over time, i.e. without network operator
intervention. The new bandwidth reservation is determined by
measuring the actual traffic flowing through the LSP. If the traffic
flowing through the LSP is lower than the configured or current
bandwidth of the LSP, the extra bandwidth is being reserved
needlessly and being wasted. Conversely, if the actual traffic
flowing through the LSP is higher than the configured or current
bandwidth of the LSP, it can potentially cause congestion or packet
loss in the network. With Auto-Bandwidth feature, the LSP bandwidth
is set to some arbitrary value (including zero) during initial setup
time, which will be periodically adjusted based on the actual
bandwidth demand. The bandwidth adjustment uses the make-before-
break (MBB) signaling method so that there is no disruption to the
traffic flow.
4.2. Auto-bandwidth Theory of Operation 4.2. Auto-bandwidth Theory of Operation
The traffic rate is periodically sampled at each sample-interval The measured traffic rate is periodically sampled at each Sample-
(which can be configured by the user and the default value as 5 Interval (which can be configured by an operator and the default
minutes) by the PCC which is the head-end node of the LSP. The value as 5 minutes) by the PCC which is the head-end node of the LSP.
sampled traffic rates are accumulated over the adjustment-interval The traffic rate samples are accumulated over the Adjustment-
period (which can be configured by the user and the default value as Interval period (which can be configured by an operator and the
24 hours). The PCC (the head-end of the LSP) is in-charge of default value as 24 hours). The PCC, in-charge of calculating the
calculating the bandwidth to be adjusted, will adjust the bandwidth bandwidth to be adjusted, will adjust the bandwidth of the LSP to the
of the LSP to the highest sampled traffic rate (MaxAvgBw) amongst the highest traffic rate sample (MaxAvgBw) amongst the set of bandwidth
set of bandwidth samples collected over the adjustment-interval samples collected over the adjustment-interval period (in the Up or
period (Up or Down). Down direction).
Note that the highest sampled traffic rate 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 Up-Adjustment-Threshold reservation is greater than or equal to the Adjustment-Threshold
(percentage or absolute value), the LSP bandwidth is adjusted (percentage or absolute value) (which can be configured by an
(upsized) to the current bandwidth demand (MaxAvgBw). Similarly if operator and the default as 5 percentage), the LSP bandwidth is
the difference between the current bandwidth reservation and the adjusted (upsized) to the current bandwidth demand (MaxAvgBw).
current bandwidth demand (MaxAvgBw) is greater than or equal to the Similarly if the difference between the current bandwidth reservation
Down-Adjustment-Threshold (percentage or absolute value), the LSP and the current bandwidth demand (MaxAvgBw) is greater than or equal
bandwidth is adjusted (downsized) to the current bandwidth demand to the Down-Adjustment-Threshold (percentage or absolute value), the
LSP bandwidth is adjusted (downsized) to the current bandwidth demand
(MaxAvgBw). Some LSPs are less eventful while other LSPs may (MaxAvgBw). Some LSPs are less eventful while other LSPs may
encounter a lot of changes in the traffic pattern. The intervals for encounter a lot of changes in the traffic pattern. The thresholds
adjustment is configured based on the traffic pattern of the LSP. and intervals for bandwidth 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, 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 pre-maturely expire the adjustment-
interval and adjust the LSP bandwidth to accommodate the sudden interval and adjust the LSP bandwidth to accommodate the sudden
bursts of increase in traffic demand as an overflow condition or bursts of increase in traffic demand as an overflow condition or
decrease in traffic demand as an underflow condition. decrease in traffic demand as an underflow condition. An operator
needs to configure appropriate values for the Overflow-Threshold
and/or Underflow-Threshold parameters and they do not have default
values.
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 done to value and percentage, and could be used together. This is provided
accommodate case where the LSP bandwidth reservation may become very to accommodate the cases where the LSP bandwidth reservation may
large or very small over time, the two representations help the become very large or very small over time, the two representations
operator to provide conditions when the bandwidth usage is too large help an operator to handle conditions when the bandwidth usage
or too small. becomes too large or too small. In any case, the auto-bandwidth
adjusted bandwidth is only reported to a PCE when MaxAvgBw crosses a
threshold.
4.3. Scaling Considerations 4.3. Scaling Considerations
It should be noted that any bandwidth change requires re-signaling of It should be noted that any bandwidth change requires re-signaling of
an LSP in a make-before-break fashion, which can further trigger an LSP in a make-before-break fashion, which can further trigger
preemption of lower priority LSPs in the network. When deployed preemption of lower priority LSPs in the network. When deployed
under scale, this can lead to a signaling churn in the network. The under scale, this can lead to a signaling churn in the network. The
Auto-bandwidth application algorithm is thus advised to take this Auto-bandwidth application algorithm is thus advised to take this
into consideration before adjusting the LSP bandwidth. Operators are into consideration before adjusting the LSP bandwidth. Operators are
advised to set the values of various auto-bandwidth adjustment advised to set the values of various auto-bandwidth adjustment
parameters appropriate for the deployed LSP scale. parameters appropriate for the deployed LSP scale.
If a PCE gets overwhelmed, it can notify the PCC to temporarily If a PCE gets overwhelmed, it can notify the PCC to temporarily
suspend the reporting of the new LSP bandwidth to be adjusted (see suspend the reporting of the new LSP bandwidth to be adjusted (see
Section 5.7). Similarly if a PCC gets overwhelmed due to signaling Section 5.7 of this document). Similarly, if a PCC gets overwhelmed
churn, it can notify the PCE to temporarily suspend the new LSP setup due to signaling churn, it can notify the PCE to temporarily suspend
requests. new LSP setup requests.
5. Extensions to the PCEP 5. Extensions to the PCEP
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 Object to advertise its support for PCEP Auto-Bandwidth OPEN Object to advertise its support for PCEP Auto-Bandwidth
extensions. The presence of the "Auto-Bandwidth Capability" TLV in extensions. The presence of the "Auto-Bandwidth Capability" TLV in
the OPEN Object indicates that the Automatic Bandwidth Adjustment is the OPEN Object indicates that the Automatic Bandwidth feature is
supported as described in this document. supported as described in this document.
The PCEP protocol extensions for Auto-Bandwidth adjustments MUST NOT The PCEP protocol extensions for Auto-Bandwidth adjustments MUST NOT
be used if one or both PCEP Speakers have not included the "Auto- be used if one or both PCEP Speakers have not included the "Auto-
Bandwidth Capability" TLV in their respective OPEN message. If the Bandwidth Capability" TLV in their respective OPEN message. If the
PCEP speaker that supports the extensions of this draft but did not PCEP speaker that supports the extensions of this document but did
advertise this capability, then upon receipt of AUTO-BANDWIDTH- not advertise this capability, then upon receipt of AUTO-BANDWIDTH-
ATTRIBUTE TLV in LSPA object, it SHOULD generate a PCErr with error- ATTRIBUTES TLV in LSPA object, it SHOULD generate a PCErr with error-
type 19 (Invalid Operation), error-value TBD4 (Auto-Bandwidth type 19 (Invalid Operation), error-value TBD4 (Auto-Bandwidth
capability was not advertised) and it will terminate the PCEP capability was not advertised) and terminate the PCEP session.
session.
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
advertisement. Its format is shown in the following figure: advertisement. Its format is shown in the following figure:
0 1 2 3 0 1 2 3
0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Type=TBD2 | Length=4 | | Type=TBD2 | Length=4 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Flags | | Flags |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
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). Currently no The value comprises a single field - Flags (32 bits). No flags are
flags are defined for this TLV. 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-ATTRIBUTE TLV 5.2. AUTO-BANDWIDTH-ATTRIBUTES TLV
The AUTO-BANDWIDTH-ATTRIBUTE TLV provides the 'configurable knobs' of The AUTO-BANDWIDTH-ATTRIBUTES TLV provides the 'configurable knobs'
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 ([I-D.ietf-pce-pce-initiated-lsp]), this TLV is For PCE-Initiated LSP [I-D.ietf-pce-pce-initiated-lsp], this TLV is
included in the LSPA Object with the PCInitiate message. For the included in the LSPA Object with the PCInitiate message. For the
PCC-Initiated delegated LSPs, this TLV is carried in the PCRpt PCC-Initiated delegated LSPs, this TLV is carried in the PCRpt
message in LSPA Object. This TLV is also included in the LSPA object message in LSPA Object. This TLV is also carried in the LSPA object
with the PCUpd message to direct the PCC (the LSP head-end) to use with the PCUpd message to direct the PCC (LSP head-end) to make
different parameters with the LSP. updates to auto-bandwidth attributes such as Adjustment-Interval.
The TLV is encoded in all PCEP messages for the LSP while the auto The TLV is encoded in all PCEP messages for the LSP while the auto-
bandwidth adjustment feature is enabled, the absence of the TLV bandwidth adjustment feature is enabled, the absence of the TLV
indicate the PCEP speaker wish to disable the feature. indicate the PCEP speaker wish to disable the feature.
The format of the AUTO-BANDWIDTH-ATTRIBUTE TLV is shown in the The format of the AUTO-BANDWIDTH-ATTRIBUTES TLV is shown in the
following figure: following figure:
0 1 2 3 0 1 2 3
0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Type=TBD1 | Length | | Type=TBD1 | Length |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| | | |
// sub-TLVs // // sub-TLVs //
| | | |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
AUTO-BANDWIDTH-ATTRIBUTE TLV format AUTO-BANDWIDTH-ATTRIBUTES TLV format
Type: TBD1 Type: TBD1
Length: The Length field defines the length of the value portion Length: The Length field defines the length of the value portion
in bytes as per [RFC5440]. in octets as per [RFC5440].
Value: This comprises one or more sub-TLVs. Value: This comprises one or more sub-TLVs.
Following sub-TLVs are defined in this document: Following sub-TLVs are defined in this document:
Type Len Name Type Len Name
------------------------------------------------------------------- -------------------------------------------------------------------
1 4 Sample-Interval sub-TLV 1 4 Sample-Interval sub-TLV
2 4 Adjustment-Interval sub-TLV 2 4 Adjustment-Interval sub-TLV
3 4 Down-Adjustment-Interval sub-TLV 3 4 Down-Adjustment-Interval sub-TLV
skipping to change at page 11, line 51 skipping to change at page 11, line 51
7 4 Down-Adjustment-Threshold-Percentage sub-TLV 7 4 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 4 Overflow-Threshold-Percentage sub-TLV 11 4 Overflow-Threshold-Percentage sub-TLV
12 8 Underflow-Threshold sub-TLV 12 8 Underflow-Threshold sub-TLV
13 4 Underflow-Threshold-Percentage sub-TLV 13 4 Underflow-Threshold-Percentage sub-TLV
Future specification can define additional sub-TLVs. Future specification can define additional sub-TLVs.
The presence of AUTO-BANDWIDTH-ATTRIBUTE TLV in LSPA Object means
that the automatic bandwidth adjustment feature is enabled. All
sub-TLVs are optional and any unrecognized sub-TLV MUST be silently
ignored. If a sub-TLV of same type appears more than once, only the
first occurrence is processed and all others MUST be ignored.
The AUTO-BANDWIDTH-ATTRIBUTE TLV can also be carried in PCUpd message
in LSPA Object in order to make updates to auto-bandwidth attributes
such as Adjustment-Interval.
If sub-TLVs are not present, the default values based on the local
policy are assumed.
The sub-TLVs are encoded to inform the PCEP peer the various sampling The sub-TLVs are encoded to inform the PCEP peer the various sampling
and adjustment parameters. and adjustment parameters. If sub-TLVs are not present, the default
values as specified in this document are used or otherwise based on
the local policy are assumed.
All sub-TLVs are optional and any unrecognized sub-TLV MUST be
silently ignored. If a sub-TLV of same type appears more than once,
only 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-ATTRIBUTE 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
The Sample-Interval sub-TLV specifies a time interval in seconds at The Sample-Interval sub-TLV specifies a time interval in seconds at
which traffic samples are collected at the PCC. which traffic samples are collected at the PCC.
The Type is 1, Length is 4, and the value comprises of 4-octet time
interval, the valid range is from 1 to 604800, in seconds. The
default value is 300 seconds.
0 1 2 3 0 1 2 3
0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Type=1 | Length=4 | | Type=1 | Length=4 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Sample-Interval | | Sample-Interval |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Sample-Interval sub-TLV format Sample-Interval sub-TLV format
5.2.2. Adjustment Interval The Type is 1, Length is 4, and the value comprises of 4-octet time
interval, the valid range is from 1 to 604800, in seconds. The
default value is 300 seconds. The sample-interval parameter MUST NOT
be greater than the (down) adjustment-interval.
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 want to set adjustment interval parameters. An implementation MAY require to set
different adjustment interval, as the bandwidth usage trend is moving different adjustment interval values for when the bandwidth usage
upwards or downwards. When the TLV is not included default value are trend is moving upwards or downwards. The Adjustment-Interval sub-
used. TLV specify the time interval for both upward and downward trend (Up-
Adjustment-Interval and Down-Adjustment-Interval). If the operator
would like to use a different adjustment interval during the downward
trend, the Down-Adjustment-Interval sub-TLV is included.
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 when MaxAvgBw is greater
than or less than the current bandwidth reservation. than or less than the current bandwidth reservation of the LSP.
The Type is 2, Length is 4, and the value comprises of 4-octet time
interval, the valid range is from 1 to 604800, in seconds. The
default value is 300 seconds.
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
The Type is 2, Length is 4, and the value comprises of 4-octet time
interval, the valid range is from 1 to 604800, in seconds. The
default value is 86400 seconds. The adjustment-interval parameter
MUST NOT be less than the sample-interval.
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. This parameter less than the current bandwidth reservation of the LSP. This
overwrites the Adjustment-Interval. parameter overwrites the Adjustment-Interval for the downward trend.
The Type is 3, Length is 4, and the value comprises of 4-octet time
interval, the valid range is from 1 to 604800, in seconds. The
default value is 300 seconds.
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
5.2.3. Adjustment Threshold The Type is 3, Length is 4, and the value comprises of 4-octet time
interval, the valid range is from 1 to 604800, in seconds. The
default value equals the adjustment-interval. The down-adjustment-
interval parameter MUST NOT be less than the sample-interval.
5.2.3. Adjustment Thresholds
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 threshold parameters. An implementation MAY include both adjustment threshold parameters. An implementation MAY include both
sub-TLVs for the absolute value and the percentage, in which case the sub-TLVs for the absolute value and the percentage, in which case the
bandwidth is adjusted when either of the adjustment threshold bandwidth is adjusted when either of the adjustment threshold
conditions are met. conditions are met. The Adjustment-Threshold sub-TLV specify the
threshold for both upward and downward trend. If the operator would
like to use a different adjustment threshold during the downward
trend, the Down-Adjustment-Threshold sub-TLV is included. Similarly,
the Adjustment-Threshold-Percentage sub-TLV specify the threshold
percentage for both upward and downward trend. If the operator would
like to use a different adjustment threshold percentage during the
downward trend, the Down-Adjustment-Threshold-Percentage sub-TLV is
included.
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 when MaxAvgBw is greater than or less
than the current bandwidth reservation. than the current bandwidth reservation.
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
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
skipping to change at page 14, line 27 skipping to change at page 14, line 35
The Type is 4, Length is 4, and the value comprises of - The Type is 4, Length is 4, 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 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. 3.1.2 of [RFC3471] for a table of commonly used values.
If the difference between the current MaxAvgBw and the current If the difference between the current MaxAvgBw and the current
bandwidth reservation is greater than or less than or equal to the bandwidth reservation is greater than or less 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). The default adjustment-threshold value
is not set.
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 when MaxAvgBw is greater than or
less than the current bandwidth reservation. less than the current bandwidth reservation.
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=4 | | Type=5 | Length=4 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Reserved | Percentage | | Reserved | Percentage |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Adjustment-Threshold-Percentage sub-TLV format
Adjustment-Threshold-Percentage sub-TLV format
The Type is 5, Length is 4, and the value comprises of - The Type is 5, Length is 4, and the value comprises of -
o Reserved: SHOULD be set to zero on transmission and MUST be o Reserved: SHOULD be set to zero on transmission and MUST be
ignored on receipt. ignored on receipt.
o Percentage: The Adjustment-Threshold value, encoded in percentage o Percentage: The Adjustment-Threshold value, encoded in percentage
(an integer from 0 to 100). If the percentage difference between (an integer from 0 to 100). If the percentage difference between
the current MaxAvgBw and the current bandwidth reservation is the current MaxAvgBw and the current bandwidth reservation is
greater than or less than or equal to the threshold percentage, greater than or less than or equal to the threshold percentage,
the LSP bandwidth is adjusted to the current bandwidth demand the LSP bandwidth is adjusted to the current bandwidth demand
(MaxAvgBw). (MaxAvgBw). The default value is 5 percent.
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 The Down-Adjustment-Threshold sub-TLV is used to decide when the LSP
LSP bandwidth should be adjusted when MaxAvgBw is lesser than the bandwidth should be adjusted when MaxAvgBw is lesser than the current
current bandwidth reservation. This parameter overwrites the bandwidth reservation. This parameter overwrites the Adjustment-
Adjustment-Threshold. Threshold for the downward trend.
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, and the value comprises of - The Type is 6, Length is 4, 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. 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. 3.1.2 of [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).
The default value equals the adjustment-threshold.
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 overwrites
the Adjustment-Threshold-Percentage. the Adjustment-Threshold-Percentage for the downward trend.
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=4 | | Type=7 | Length=4 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Reserved | Percentage | | Reserved | Percentage |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Down-Adjustment-Threshold-Percentage sub-TLV format
Down-Adjustment-Threshold-Percentage sub-TLV format
The Type is 7, Length is 4, and the value comprises of - The Type is 7, Length is 4, and the value comprises of -
o Reserved: SHOULD be set to zero on transmission and MUST be o Reserved: SHOULD be set to zero on transmission and MUST be
ignored on receipt. ignored on receipt.
o Percentage: The Down-Adjustment-Threshold value, encoded in o Percentage: The Down-Adjustment-Threshold value, encoded in
percentage (an integer from 0 to 100). If the percentage percentage (an integer from 0 to 100). If the percentage
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 current MaxAvgBw is greater than or equal to the threshold
percentage, the LSP bandwidth is adjusted to the current bandwidth percentage, the LSP bandwidth is adjusted to the current bandwidth
demand (MaxAvgBw). demand (MaxAvgBw). The default value equals the adjustment-
threshold-percentage.
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.
The Type is 8, Length is 4, and the value comprises of 4-octet
bandwidth value encoded in IEEE floating point format (see
[IEEE.754.1985]), expressed in bytes per second. Refer to Section
3.1.2 of [RFC3471] for a table of commonly used values.
0 1 2 3 0 1 2 3
0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Type=8 | Length=4 | | Type=8 | Length=4 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Minimum-Bandwidth | | Minimum-Bandwidth |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Minimum-Bandwidth sub-TLV format Minimum-Bandwidth sub-TLV format
The Type is 8, Length is 4, and the value comprises of 4-octet
bandwidth value encoded in IEEE floating point format (see
[IEEE.754.1985]), expressed in bytes 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 values.
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.
The Type is 9, Length is 4, and the value comprises of 4-octet
bandwidth value encoded in IEEE floating point format (see
[IEEE.754.1985]), expressed in bytes per second. Refer to Section
3.1.2 of [RFC3471] for a table of commonly used values.
0 1 2 3 0 1 2 3
0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Type=9 | Length=4 | | Type=9 | Length=4 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Maximum-Bandwidth | | Maximum-Bandwidth |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Maximum-Bandwidth sub-TLV format Maximum-Bandwidth sub-TLV format
The Type is 9, Length is 4, and the value comprises of 4-octet
bandwidth value encoded in IEEE floating point format (see
[IEEE.754.1985]), expressed in bytes per second. The default
maximum-bandwidth value is not set. Refer to Section 3.1.2 of
[RFC3471] for a table of commonly used values.
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 the absolute value and the 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 adjustment threshold conditions are met consecutively either of the threshold conditions is met consecutively for the given
for the given count. count. The default threshold values for overflow and underflow
conditions are not set.
5.2.5.1. Overflow-Threshold sub-TLV 5.2.5.1. Overflow-Threshold sub-TLV
The Overflow-Threshold sub-TLV is used to decide if the bandwidth The Overflow-Threshold sub-TLV is used to decide if the bandwidth
should be adjusted immediately. should be adjusted immediately.
0 1 2 3 0 1 2 3
0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Type=10 | Length=8 | | Type=10 | Length=8 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Reserved | Count | | Reserved | Count |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Overflow-Threshold | | Overflow-Threshold |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Overflow-Threshold sub-TLV format Overflow-Threshold sub-TLV format
The Type is 10, Length is 8, and the value comprises of - The Type is 10, Length is 8, and the value comprises of -
o Reserved: SHOULD be set to zero on transmission and MUST be o Reserved: SHOULD be set to zero on transmission and MUST be
ignored on receipt. ignored on receipt.
o Count: The Overflow-Count value, encoded in integer. The value 0 o Count: The Overflow-Count value, encoded in integer. The value 0
is considered to be invalid. The number of consecutive samples is considered to be invalid. The number of consecutive samples
for which the overflow condition MUST be met for the LSP bandwidth for which the overflow condition MUST be met for the LSP bandwidth
to be immediately adjusted to the current bandwidth demand, to be immediately adjusted to the current bandwidth demand,
bypassing the adjustment-interval. 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 increase 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.
5.2.5.2. Overflow-Threshold-Percentage sub-TLV 5.2.5.2. Overflow-Threshold-Percentage sub-TLV
skipping to change at page 18, line 41 skipping to change at page 19, line 5
than or equal to the threshold percentage, the overflow condition than or equal to the threshold percentage, the overflow condition
is met. is met.
o Reserved: SHOULD be set to zero on transmission and MUST be o Reserved: SHOULD be set to zero on transmission and MUST be
ignored on receipt. ignored on receipt.
o Count: The Overflow-Count value, encoded in integer. The value 0 o Count: The Overflow-Count value, encoded in integer. The value 0
is considered to be invalid. The number of consecutive samples is considered to be invalid. The number of consecutive samples
for which the overflow condition MUST be met for the LSP bandwidth for which the overflow condition MUST be met for the LSP bandwidth
to be immediately adjusted to the current bandwidth demand, to be immediately adjusted to the current bandwidth demand,
bypassing the adjustment-interval. bypassing the (up) adjustment-interval.
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 bandwidth The Underflow-Threshold sub-TLV is used to decide if the bandwidth
should be adjusted immediately. should be adjusted immediately.
0 1 2 3 0 1 2 3
0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Type=12 | Length=8 | | Type=12 | Length=8 |
skipping to change at page 19, line 21 skipping to change at page 19, line 33
The Type is 12, Length is 8, and the value comprises of - The Type is 12, Length is 8, and the value comprises of -
o Reserved: SHOULD be set to zero on transmission and MUST be o Reserved: SHOULD be set to zero on transmission and MUST be
ignored on receipt. ignored on receipt.
o Count: The Underflow-Count value, encoded in integer. The value 0 o Count: The Underflow-Count value, encoded in integer. The value 0
is considered to be invalid. The number of consecutive samples is considered to be invalid. The number of consecutive samples
for which the underflow condition MUST be met for the LSP for which the underflow 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 adjustment-interval. 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 decrease 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.
5.2.5.4. Underflow-Threshold-Percentage sub-TLV 5.2.5.4. Underflow-Threshold-Percentage sub-TLV
skipping to change at page 20, line 13 skipping to change at page 20, line 25
than or equal to the threshold percentage, the underflow condition than or equal to the threshold percentage, the underflow condition
is met. is met.
o Reserved: SHOULD be set to zero on transmission and MUST be o Reserved: SHOULD be set to zero on transmission and MUST be
ignored on receipt. ignored on receipt.
o Count: The Underflow-Count value, encoded in integer. The value 0 o Count: The Underflow-Count value, encoded in integer. The value 0
is considered to be invalid. The number of consecutive samples is considered to be invalid. The number of consecutive samples
for which the underflow condition MUST be met for the LSP for which the underflow 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 adjustment-interval. demand, bypassing the down-adjustment-interval.
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.
PCC reports the calculated bandwidth to be adjusted (MaxAvgBw) to the The PCC reports the calculated bandwidth to be adjusted (MaxAvgBw) to
PCE using the existing 'Requested Bandwidth' with BANDWIDTH Object- the Stateful PCE using the existing 'Requested Bandwidth' with
Type as 1. BANDWIDTH Object-Type as 1. The reporting of the 're-optimization
bandwidth' with BANDWIDTH Object-Type as 2 is not required as the
Stateful PCE is aware of the existing LSP bandwidth.
5.4. The PCInitiate Message 5.4. The PCInitiate Message
A PCInitiate message is a PCEP message sent by a PCE to a PCC to A PCInitiate message is a PCEP message sent by a PCE to a PCC to
trigger LSP instantiation or deletion [I.D.ietf-pce-pce-initiated- trigger LSP instantiation or deletion
lsp]. [I.D.ietf-pce-pce-initiated-lsp].
For the PCE-Initiated LSP with Auto-Bandwidth feature enabled, AUTO- For the PCE-Initiated LSP with Auto-Bandwidth feature enabled, AUTO-
BANDWIDTH-ATTRIBUTE TLV MUST be included in the LSPA object with the BANDWIDTH-ATTRIBUTES TLV MUST be included in the LSPA object with the
PCInitiate message. PCInitiate message.
The definition of the PCInitiate message (see The definition (RBNF) of the PCInitiate message
[I-D.ietf-pce-stateful-pce]) is unchanged by this document. [I.D.ietf-pce-pce-initiated-lsp] is unchanged by this document.
5.5. The PCUpd Message 5.5. The PCUpd Message
A PCUpd message is a PCEP message sent by a PCE to a PCC to update A PCUpd message is a PCEP message sent by a PCE to a PCC to update
the LSP parameters [I-D.ietf-pce-stateful-pce]. the LSP parameters [I-D.ietf-pce-stateful-pce].
For PCE-Initiated LSPs with Auto-Bandwidth feature enabled, AUTO- For PCE-Initiated LSPs with Auto-Bandwidth feature enabled, AUTO-
BANDWIDTH-ATTRIBUTE TLV MUST be included in the LSPA object with the BANDWIDTH-ATTRIBUTES TLV MUST be included in the LSPA object with the
PCUpd message. The PCE can send this TLV to direct the PCC to change PCUpd message. The PCE can send this TLV to direct the PCC to change
the auto bandwidth parameters. the auto-bandwidth parameters.
The definition of the PCUpd message (see [I-D.ietf-pce-stateful-pce]) The definition (RBNF) of the PCUpd message
is unchanged by this document. [I-D.ietf-pce-stateful-pce] is unchanged by this document.
5.6. The PCRpt Message 5.6. The PCRpt Message
The PCRpt message ([I-D.ietf-pce-stateful-pce]) is a PCEP message The PCRpt message [I-D.ietf-pce-stateful-pce] is a PCEP message sent
sent by a PCC to a PCE to report the status of one or more LSPs. by a PCC to a PCE to report the status of one or more LSPs.
For PCE-Initiated LSPs [I.D.ietf-pce-pce-initiated-lsp], the PCC For PCE-Initiated LSPs [I.D.ietf-pce-pce-initiated-lsp], the PCC
creates the LSP using the attributes communicated by the PCE, and creates the LSP using the attributes communicated by the PCE, and
using the local values for the unspecified parameters. After the using the local values for the unspecified parameters. After the
successful instantiation of the LSP, PCC automatically delegates the successful instantiation of the LSP, PCC automatically delegates the
LSP to the PCE and generates a PCRpt message to provide the status LSP to the PCE and generates a PCRpt message to provide the status
report for the LSP. report for the LSP.
For both PCE-Initiated and PCC-Initiated LSPs, when the LSP is For both PCE-Initiated and PCC-Initiated LSPs, when the LSP is
delegated to a PCE for the very first time, the BANDWIDTH object of delegated to a PCE for the very first time as well as after the
type 1 is used to specify the requested bandwidth in the PCRpt successful delegation, the BANDWIDTH object of type 1 is used to
message. After the successful delegation, to specify the LSP specify the requested bandwidth in the PCRpt message.
bandwidth to be adjusted, the BANDWIDTH object of type 1 is included
in the PCRpt message.
For PCC-Initiated LSPs with Auto-Bandwidth feature enabled, AUTO- For all LSPs with Auto-Bandwidth feature enabled, AUTO-BANDWIDTH-
BANDWIDTH-ATTRIBUTE TLV MUST be included in the LSPA object of the ATTRIBUTES TLV MUST be included in the LSPA object of the PCRpt
PCRpt message. message.
The definition of the PCRpt message (see [I-D.ietf-pce-stateful-pce]) The definition (RBNF) of the PCRpt message
is unchanged by this document. [I-D.ietf-pce-stateful-pce] is unchanged by 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.
As described in Section 4.3 of this document, a PCEP speaker (PCE or A PCEP speaker (PCE or PCC) SHOULD notify its PCEP peer (PCC or PCE)
PCC) SHOULD notify its PCEP peer (PCC or PCE) when it is in when it is in overwhelmed state due to the auto-bandwidth feature.
overwhelmed state for the auto-bandwidth feature. Upon receipt of Upon receipt of such notification, the peer SHOULD NOT send any PCEP
such notification, the peer SHOULD NOT send any PCEP messages related messages related to auto-bandwidth adjustment. If a PCEP message
to auto-bandwidth adjustment. If a PCEP message related to auto- related to auto-bandwidth is received during in overwhelmed state, it
bandwidth is received during in overwhelmed state, it MUST be MUST be silently ignored.
silently ignored.
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-bandwidth sending a PCNtf message with Notification Type = TBD3 (Auto-
Overwhelm State) and Notification Value = 1 (Entering auto-bandwidth bandwidth Overwhelm State) and Notification Value = 1 (Entering
overwhelm state). Optionally, OVERLOADED-DURATION TLV [RFC5440] MAY auto-bandwidth overwhelm state). Optionally, OVERLOADED-DURATION
be included that specifies the time period during which no further TLV [RFC5440] MAY be included that specifies the time period
PCEP messages related to auto-bandwidth adjustment should be sent. during which no further PCEP messages related to auto-bandwidth
When the PCEP speaker is no longer in the overwhelm state and is adjustment should be sent.
available to process the auto-bandwidth adjustment, it SHOULD notify
its peer by sending a PCNtf message with Notification Type = TBD3 o When the PCEP speaker is no longer in the overwhelm state and is
(Auto-bandwidth Overwhelm State) and Notification Value = 2 (Clearing available to process the auto-bandwidth adjustments, it SHOULD
auto-bandwidth overwhelm state). notify its peer by sending a PCNtf message with Notification Type
= TBD3 (Auto-bandwidth Overwhelm State) and Notification Value = 2
(Clearing auto-bandwidth overwhelm state).
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.
6. Security Considerations 6. Security Considerations
This document defines AUTO-BANDWIDTH-CAPABILITY TLV and This document defines AUTO-BANDWIDTH-CAPABILITY TLV and
AUTO-BANDWIDTH-ATTRIBUTE TLV which do not add any new security AUTO-BANDWIDTH-ATTRIBUTES TLV which do not add any new security
concerns beyond those discussed in [RFC5440] and concerns beyond those discussed in [RFC5440] and
[I-D.ietf-pce-stateful-pce] in itself. Some deployments may find the [I-D.ietf-pce-stateful-pce] in itself. Some deployments may find the
auto-bandwidth information as extra sensitive as it could be used to auto-bandwidth information as extra sensitive as it could be used to
influence LSP path computation and LSP setup with adverse effect. influence LSP path computation and LSP setup with adverse effect.
Additionally, snooping of PCEP messages with such data or using PCEP Additionally, snooping of PCEP messages with such data or using PCEP
messages for network reconnaissance, may give an attacker sensitive messages for network reconnaissance, may give an attacker sensitive
information about the operations of the network. Thus, such information about the operations of the network. Thus, such
deployment should employ suitable PCEP security mechanisms like TCP deployment should employ suitable PCEP security mechanisms like TCP
Authentication Option (TCP-AO) [RFC5925] or [I-D.ietf-pce-pceps]. Authentication Option (TCP-AO) [RFC5925] or [I-D.ietf-pce-pceps].
7. Manageability Considerations 7. Manageability Considerations
7.1. Control of Function and Policy 7.1. Control of Function and Policy
The Auto-Bandwidth feature SHOULD be controlled per tunnel (at The Auto-Bandwidth feature SHOULD be controlled per LSP (at PCC
ingress (PCC) or PCE) and the values for auto-bandwidth parameters (head-end of the LSP) or PCE) and the values for auto-bandwidth
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.
7.2. Information and Data Models 7.2. Information and Data Models
A Management Information Base (MIB) module for modeling PCEP is A Management Information Base (MIB) module for modeling PCEP is
described in [RFC7420]. However, one may prefer the mechanism for described in [RFC7420]. However, one may prefer the mechanism for
configuration using YANG data model [I-D.ietf-pce-pcep-yang]. These configuration using YANG data model [I-D.ietf-pce-pcep-yang]. These
SHOULD be enhanced to provide controls and indicators for support of SHOULD be enhanced to provide controls and indicators for support of
auto-bandwidth feature. Support for various configuration knobs as auto-bandwidth feature. Support for various configuration knobs as
well as counters of messages sent/received containing the TLVs well as counters of messages sent/received containing the TLVs
(defined in this document) SHOULD be added. defined in this document SHOULD be added.
7.3. Liveness Detection and Monitoring 7.3. Liveness Detection and Monitoring
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].
7.4. Verify Correct Operations 7.4. Verify Correct Operations
Mechanisms defined in this document do not imply any new operation The mechanisms defined in this document do not imply any new
verification requirements in addition to those already listed in operation verification requirements in addition to those already
[RFC5440]. listed in [RFC5440].
7.5. Requirements On Other Protocols 7.5. Requirements On Other Protocols
Mechanisms defined in this document do not add any new requirements The mechanisms defined in this document do not add any new
on other protocols. requirements on other protocols.
7.6. Impact On Network Operations 7.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. An LSPs that can be enabled with auto-bandwidth feature. An
implementation MAY allow a limit to be placed on the rate of auto- implementation MAY allow a limit to be placed on the rate of auto-
bandwidth messages sent by a PCEP speaker and received by a peer. An bandwidth related messages sent by a PCEP speaker and received by a
implementation MAY also allow sending a notification when a PCEP peer. An implementation MAY also allow sending a notification when a
speaker is overwhelmed or the rate of messages reach a threshold. PCEP speaker is overwhelmed or the rate of messages reach a
threshold.
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 this registry. to make the following allocations from the "PCEP TLV Type Indicators"
<http://www.iana.org/assignments/pcep/pcep.xhtml#pcep-tlv-type- sub-registry of the PCEP Numbers registry, as follows:
indicators>.
Value Name Reference Value Name Reference
-------------------------------------------------------------- -----------------------------------------------------------------
TBD2 AUTO-BANDWIDTH-CAPABILITY [This I.D.] TBD2 AUTO-BANDWIDTH-CAPABILITY [This document]
TBD1 AUTO-BANDWIDTH-ATTRIBUTE [This I.D.] 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 registry to manage the Flag field of IANA is requested to create a sub-registry to manage the Flag field
the AUTO-BANDWIDTH-CAPABILITY TLV. of the AUTO-BANDWIDTH-CAPABILITY TLV.
New bit numbers are allocated only by an IETF Review action New bit numbers are allocated only by an IETF Review action
[RFC5226]. Each bit should be tracked with the following qualities: [RFC5226]. 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
No bit is defined for the AUTO-BANDWIDTH-CAPABILITY TLV Object flag There is no bit defined for the AUTO-BANDWIDTH-CAPABILITY TLV Object
field in this document. flag field in this document.
8.3. AUTO-BANDWIDTH-ATTRIBUTE Sub-TLV 8.3. AUTO-BANDWIDTH-ATTRIBUTES Sub-TLV
This document specifies the AUTO-BANDWIDTH-ATTRIBUTE Sub-TLVs. IANA This document specifies the AUTO-BANDWIDTH-ATTRIBUTES Sub-TLVs. IANA
is requested to create an "AUTO-BANDWIDTH-ATTRIBUTE Sub-TLV Types" is requested to create an "AUTO-BANDWIDTH-ATTRIBUTES Sub-TLV Types"
sub-registry in the "PCEP TLV Type Indicators" for the sub-TLVs sub-registry in the "PCEP TLV Type Indicators" for the sub-TLVs
carried in the AUTO-BANDWIDTH-ATTRIBUTE TLV. New sub-TLV are carried in the AUTO-BANDWIDTH-ATTRIBUTES TLV. New sub-TLV are
allocated only by an IETF Review action [RFC5226]. allocated only by an IETF Review action [RFC5226].
This document defines the following types: This document defines the following types:
Type Name Reference Type Name Reference
-------------------------------------------------------------- -----------------------------------------------------------------
0 Reserved [This I.D.] 0 Reserved [This document]
1 Sample-Interval sub-TLV [This I.D.] 1 Sample-Interval sub-TLV [This document]
2 Adjustment-Interval sub-TLV [This I.D.] 2 Adjustment-Interval sub-TLV [This document]
3 Down-Adjustment-Interval sub-TLV [This I.D.] 3 Down-Adjustment-Interval sub-TLV [This document]
4 Adjustment-Threshold sub-TLV [This I.D.] 4 Adjustment-Threshold sub-TLV [This document]
5 Adjustment-Threshold-Percentage sub-TLV [This I.D.] 5 Adjustment-Threshold-Percentage sub-TLV [This document]
6 Down-Adjustment-Threshold sub-TLV [This I.D.] 6 Down-Adjustment-Threshold sub-TLV [This document]
7 Down-Adjustment-Threshold-Percentage sub-TLV [This I.D.] 7 Down-Adjustment-Threshold-Percentage sub-TLV [This document]
8 Minimum-Bandwidth sub-TLV [This I.D.] 8 Minimum-Bandwidth sub-TLV [This document]
9 Maximum-Bandwidth sub-TLV [This I.D.] 9 Maximum-Bandwidth sub-TLV [This document]
10 Overflow-Threshold sub-TLV [This I.D.] 10 Overflow-Threshold sub-TLV [This document]
11 Overflow-Threshold-Percentage sub-TLV [This I.D.] 11 Overflow-Threshold-Percentage sub-TLV [This document]
12 Underflow-Threshold sub-TLV [This I.D.] 12 Underflow-Threshold sub-TLV [This document]
13 Underflow-Threshold-Percentage sub-TLV [This I.D.] 13 Underflow-Threshold-Percentage sub-TLV [This document]
14- Unassigned [This I.D.] 14- Unassigned [This document]
65535 65535
8.4. Error Object 8.4. Error Object
This document defines a new Error-Value for PCErr message of type 19 This document defines a new Error-Value for PCErr message of Error-
(Invalid Operation) [I-D.ietf-pce-stateful-pce]); IANA is requested Type 19 (Invalid Operation) [I-D.ietf-pce-stateful-pce]; IANA is
to make the following allocation from this registry. requested to allocate new error-value within the "PCEP-ERROR Object
<http://www.iana.org/assignments/pcep/pcep.xhtml#pcep-error-object> Error Types and Values" subregistry of the PCEP Numbers registry, as
follows:
Error-Value Meaning Reference Error-Type Meaning & error values Reference
-------------------------------------------------------------- -----------------------------------------------------------------
TBD4 Auto-Bandwidth Capability [This I.D.] 19 Invalid Operations
was not Advertised
Error-Value = TBD4: [This document]
Auto-Bandwidth Capability
was not Advertised
8.5. Notification Object 8.5. Notification Object
IANA is requested to allocate new Notification Types and Notification IANA is requested to allocate new Notification Types and Notification
Values within the "Notification Object" sub-registry of the PCEP Values within the "Notification Object" sub-registry of the PCEP
Numbers registry, as follows: Numbers registry, as follows:
Type Meaning Reference Type Meaning Reference
--------------------------------------------------------------- -----------------------------------------------------------------
TBD3 Auto-Bandwidth Overwhelm State [This I.D.] TBD3 Auto-Bandwidth Overwhelm State [This document]
Notification-value=1: Entering Auto-Bandwidth Notification-value=1: Entering Auto-Bandwidth
overwhelm state overwhelm state
Notification-value=2: Clearing Auto-Bandwidth Notification-value=2: Clearing Auto-Bandwidth
overwhelm state overwhelm state
9. References 9. References
9.1. Normative References 9.1. Normative References
skipping to change at page 27, line 6 skipping to change at page 27, line 6
[I-D.ietf-pce-pceps] Lopez, D., Dios, O., Wu, W., and D. Dhody, [I-D.ietf-pce-pceps] Lopez, D., Dios, O., Wu, W., and D. Dhody,
"Secure Transport for PCEP", draft-ietf-pce-pceps (work in "Secure Transport for PCEP", draft-ietf-pce-pceps (work in
progress). progress).
[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).
[I-D.gandhi-pce-pm] Gandhi, R., Wen, B., Barth, C., and D. Dhody [I-D.gandhi-pce-pm] Gandhi, R., Wen, B., Barth, C., and D. Dhody,
"PCEP Extensions for Reporting MPLS-TE LSP Performance "PCEP Extensions for Reporting MPLS-TE LSP Performance
Measurements", draft-gandhi-pce-pm (work in progress). Measurements", draft-gandhi-pce-pm (work in progress).
[IEEE.754.1985] Institute of Electrical and Electronics Engineers, [IEEE.754.1985] Institute of Electrical and Electronics Engineers,
"Standard for Binary Floating-Point Arithmetic", IEEE "Standard for Binary Floating-Point Arithmetic", IEEE
Standard 754, August 1985. 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 and Adrian Paul, Sandeep Boina, Avantika, JP Vasseur, Himanshu Shah and Adrian
Farrel for their useful comments and suggestions. Farrel for their useful comments and suggestions.
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
Huawei Technologies Huawei Technologies
1700 Alma Drive, Suite 100 1700 Alma Drive, Suite 100
Plano, TX 75075 Plano, TX 75075
USA USA
Phone: +1 972 509 5599 x2240 Phone: +1 972 509 5599 x2240
Fax: +1 469 229 5397 Fax: +1 469 229 5397
EMail: leeyoung@huawei.com Email: leeyoung@huawei.com
Authors' Addresses Authors' Addresses
Dhruv Dhody Dhruv Dhody
Huawei Technologies Huawei Technologies
Divyashree Techno Park, Whitefield Divyashree Techno Park, Whitefield
Bangalore, Karnataka 560066 Bangalore, Karnataka 560066
India India
EMail: dhruv.ietf@gmail.com Email: dhruv.ietf@gmail.com
Udayasree Palle Udayasree Palle
Huawei Technologies Huawei Technologies
Divyashree Techno Park, Whitefield Divyashree Techno Park, Whitefield
Bangalore, Karnataka 560037 Bangalore, Karnataka 560037
India India
EMail: udayasree.palle@huawei.com Email: udayasreereddy@gmail.com
Ravi Singh Ravi Singh
Juniper Networks Juniper Networks
1194 N. Mathilda Ave. 1194 N. Mathilda Ave.
Sunnyvale, CA 94089 Sunnyvale, CA 94089
USA USA
EMail: ravis@juniper.net Email: ravis@juniper.net
Rakesh Gandhi Rakesh Gandhi
Cisco Systems, Inc. Cisco Systems, Inc.
EMail: rgandhi@cisco.com Email: rgandhi@cisco.com
Luyuan Fang Luyuan Fang
eBay eBay
USA USA
EMail: lufang@ebay.com Email: lufang@ebay.com
 End of changes. 133 change blocks. 
385 lines changed or deleted 403 lines changed or added

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