draft-ietf-pce-stateful-pce-auto-bandwidth-08.txt   draft-ietf-pce-stateful-pce-auto-bandwidth-09.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: May 23, 2019 R. Singh Expires: October 25, 2019 R. Singh
Juniper Networks Juniper Networks
R. Gandhi R. Gandhi
Cisco Systems, Inc. Cisco Systems, Inc.
L. Fang L. Fang
Expedia, Inc. Expedia, Inc.
November 19, 2018 April 23, 2019
PCEP Extensions for MPLS-TE LSP Automatic Bandwidth Adjustment with PCEP Extensions for MPLS-TE LSP Automatic Bandwidth Adjustment with
Stateful PCE Stateful PCE
draft-ietf-pce-stateful-pce-auto-bandwidth-08 draft-ietf-pce-stateful-pce-auto-bandwidth-09
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.
Automatic bandwidth allows automatic and dynamic adjustment of the TE The automatic bandwidth feature allows automatic and dynamic
LSP bandwidth reservation based on the volume of traffic flowing adjustment of the TE LSP bandwidth reservation based on the volume of
through the LSP. This document describes PCEP extensions for traffic flowing through the LSP. This document describes PCEP
automatic bandwidth adjustment when employing an Active Stateful PCE extensions for automatic bandwidth adjustment when employing an
for both PCE-Initiated and PCC-Initiated LSPs. Active Stateful PCE for both PCE-Initiated and PCC-Initiated LSPs.
Status of This Memo Status of This Memo
This Internet-Draft is submitted in full conformance with the This Internet-Draft is submitted in full conformance with the
provisions of BCP 78 and BCP 79. provisions of BCP 78 and BCP 79.
Internet-Drafts are working documents of the Internet Engineering Internet-Drafts are working documents of the Internet Engineering
Task Force (IETF). Note that other groups may also distribute Task Force (IETF). Note that other groups may also distribute
working documents as Internet-Drafts. The list of current Internet- working documents as Internet-Drafts. The list of current Internet-
Drafts is at http://datatracker.ietf.org/drafts/current/. Drafts is at http://datatracker.ietf.org/drafts/current/.
Internet-Drafts are draft documents valid for a maximum of six months Internet-Drafts are draft documents valid for a maximum of six months
and may be updated, replaced, or obsoleted by other documents at any and may be updated, replaced, or obsoleted by other documents at any
time. It is inappropriate to use Internet-Drafts as reference time. It is inappropriate to use Internet-Drafts as reference
material or to cite them other than as "work in progress." material or to cite them other than as "work in progress."
Copyright Notice Copyright Notice
Copyright (c) 2018 IETF Trust and the persons identified as the Copyright (c) 2019 IETF Trust and the persons identified as the
document authors. All rights reserved. document authors. All rights reserved.
This document is subject to BCP 78 and the IETF Trust's Legal This document is subject to BCP 78 and the IETF Trust's Legal
Provisions Relating to IETF Documents Provisions Relating to IETF Documents
(http://trustee.ietf.org/license-info) in effect on the date of (http://trustee.ietf.org/license-info) in effect on the date of
publication of this document. Please review these documents publication of this document. Please review these documents
carefully, as they describe your rights and restrictions with respect carefully, as they describe your rights and restrictions with respect
to this document. Code Components extracted from this document must to this document. Code Components extracted from this document must
include Simplified BSD License text as described in Section 4.e of include Simplified BSD License text as described in Section 4.e of
the Trust Legal Provisions and are provided without warranty as the Trust Legal Provisions and are provided without warranty as
skipping to change at page 2, line 34 skipping to change at page 2, line 34
2.1. Requirements Language . . . . . . . . . . . . . . . . . . 4 2.1. Requirements Language . . . . . . . . . . . . . . . . . . 4
2.2. Abbreviations . . . . . . . . . . . . . . . . . . . . . . 4 2.2. Abbreviations . . . . . . . . . . . . . . . . . . . . . . 4
2.3. Terminology . . . . . . . . . . . . . . . . . . . . . . . 5 2.3. Terminology . . . . . . . . . . . . . . . . . . . . . . . 5
3. Requirements for PCEP Extensions . . . . . . . . . . . . . . . 7 3. Requirements for PCEP Extensions . . . . . . . . . . . . . . . 7
4. Architectural Overview . . . . . . . . . . . . . . . . . . . . 8 4. Architectural Overview . . . . . . . . . . . . . . . . . . . . 8
4.1. Auto-Bandwidth Overview . . . . . . . . . . . . . . . . . 8 4.1. Auto-Bandwidth Overview . . . . . . . . . . . . . . . . . 8
4.2. Auto-bandwidth Theory of Operation . . . . . . . . . . . . 8 4.2. Auto-bandwidth Theory of Operation . . . . . . . . . . . . 8
4.3. Scaling Considerations . . . . . . . . . . . . . . . . . . 10 4.3. Scaling Considerations . . . . . . . . . . . . . . . . . . 10
5. Extensions to the PCEP . . . . . . . . . . . . . . . . . . . . 10 5. Extensions to the PCEP . . . . . . . . . . . . . . . . . . . . 10
5.1. Capability Advertisement . . . . . . . . . . . . . . . . . 10 5.1. Capability Advertisement . . . . . . . . . . . . . . . . . 10
5.1.1. AUTO-BANDWIDTH-CAPABILITY TLV . . . . . . . . . . . . 10 5.1.1. AUTO-BANDWIDTH-CAPABILITY TLV . . . . . . . . . . . . 11
5.2. AUTO-BANDWIDTH-ATTRIBUTES TLV . . . . . . . . . . . . . . 11 5.2. AUTO-BANDWIDTH-ATTRIBUTES TLV . . . . . . . . . . . . . . 11
5.2.1. Sample-Interval sub-TLV . . . . . . . . . . . . . . . 13 5.2.1. Sample-Interval sub-TLV . . . . . . . . . . . . . . . 13
5.2.2. Adjustment Intervals . . . . . . . . . . . . . . . . . 13 5.2.2. Adjustment Intervals . . . . . . . . . . . . . . . . . 13
5.2.2.1. Adjustment-Interval sub-TLV . . . . . . . . . . . 13 5.2.2.1. Adjustment-Interval sub-TLV . . . . . . . . . . . 13
5.2.2.2. Down-Adjustment-Interval sub-TLV . . . . . . . . . 14 5.2.2.2. Down-Adjustment-Interval sub-TLV . . . . . . . . . 14
5.2.3. Adjustment Thresholds . . . . . . . . . . . . . . . . 14 5.2.3. Adjustment Thresholds . . . . . . . . . . . . . . . . 15
5.2.3.1. Adjustment-Threshold sub-TLV . . . . . . . . . . . 15 5.2.3.1. Adjustment-Threshold sub-TLV . . . . . . . . . . . 15
5.2.3.2. Adjustment-Threshold-Percentage sub-TLV . . . . . 15 5.2.3.2. Adjustment-Threshold-Percentage sub-TLV . . . . . 16
5.2.3.3. Down-Adjustment-Threshold sub-TLV . . . . . . . . 16 5.2.3.3. Down-Adjustment-Threshold sub-TLV . . . . . . . . 16
5.2.3.4. Down-Adjustment-Threshold-Percentage sub-TLV . . . 17 5.2.3.4. Down-Adjustment-Threshold-Percentage sub-TLV . . . 17
5.2.4. Minimum and Maximum Bandwidth Values . . . . . . . . . 17 5.2.4. Minimum and Maximum Bandwidth Values . . . . . . . . . 18
5.2.4.1. Minimum-Bandwidth sub-TLV . . . . . . . . . . . . 17 5.2.4.1. Minimum-Bandwidth sub-TLV . . . . . . . . . . . . 18
5.2.4.2. Maximum-Bandwidth sub-TLV . . . . . . . . . . . . 18 5.2.4.2. Maximum-Bandwidth sub-TLV . . . . . . . . . . . . 18
5.2.5. Overflow and Underflow Conditions . . . . . . . . . . 18 5.2.5. Overflow and Underflow Conditions . . . . . . . . . . 19
5.2.5.1. Overflow-Threshold sub-TLV . . . . . . . . . . . . 19 5.2.5.1. Overflow-Threshold sub-TLV . . . . . . . . . . . . 19
5.2.5.2. Overflow-Threshold-Percentage sub-TLV . . . . . . 19 5.2.5.2. Overflow-Threshold-Percentage sub-TLV . . . . . . 20
5.2.5.3. Underflow-Threshold sub-TLV . . . . . . . . . . . 20 5.2.5.3. Underflow-Threshold sub-TLV . . . . . . . . . . . 21
5.2.5.4. Underflow-Threshold-Percentage sub-TLV . . . . . . 21 5.2.5.4. Underflow-Threshold-Percentage sub-TLV . . . . . . 21
5.3. BANDWIDTH Object . . . . . . . . . . . . . . . . . . . . . 22 5.3. BANDWIDTH Object . . . . . . . . . . . . . . . . . . . . . 22
5.4. The PCInitiate Message . . . . . . . . . . . . . . . . . . 22 5.4. The PCInitiate Message . . . . . . . . . . . . . . . . . . 23
5.5. The PCUpd Message . . . . . . . . . . . . . . . . . . . . 22 5.5. The PCUpd Message . . . . . . . . . . . . . . . . . . . . 23
5.6. The PCRpt Message . . . . . . . . . . . . . . . . . . . . 23 5.6. The PCRpt Message . . . . . . . . . . . . . . . . . . . . 23
5.7. The PCNtf Message . . . . . . . . . . . . . . . . . . . . 23 5.7. The PCNtf Message . . . . . . . . . . . . . . . . . . . . 24
6. Security Considerations . . . . . . . . . . . . . . . . . . . 24 6. Security Considerations . . . . . . . . . . . . . . . . . . . 24
7. Manageability Considerations . . . . . . . . . . . . . . . . . 24 7. Manageability Considerations . . . . . . . . . . . . . . . . . 25
7.1. Control of Function and Policy . . . . . . . . . . . . . . 24 7.1. Control of Function and Policy . . . . . . . . . . . . . . 25
7.2. Information and Data Models . . . . . . . . . . . . . . . 24 7.2. Information and Data Models . . . . . . . . . . . . . . . 25
7.3. Liveness Detection and Monitoring . . . . . . . . . . . . 25 7.3. Liveness Detection and Monitoring . . . . . . . . . . . . 25
7.4. Verify Correct Operations . . . . . . . . . . . . . . . . 25 7.4. Verify Correct Operations . . . . . . . . . . . . . . . . 25
7.5. Requirements On Other Protocols . . . . . . . . . . . . . 25 7.5. Requirements On Other Protocols . . . . . . . . . . . . . 25
7.6. Impact On Network Operations . . . . . . . . . . . . . . . 25 7.6. Impact On Network Operations . . . . . . . . . . . . . . . 25
8. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 26 8. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 26
8.1. PCEP TLV Type Indicators . . . . . . . . . . . . . . . . . 26 8.1. PCEP TLV Type Indicators . . . . . . . . . . . . . . . . . 26
8.2. AUTO-BANDWIDTH-CAPABILITY TLV Flag Field . . . . . . . . . 26 8.2. AUTO-BANDWIDTH-CAPABILITY TLV Flag Field . . . . . . . . . 26
8.3. AUTO-BANDWIDTH-ATTRIBUTES Sub-TLV . . . . . . . . . . . . 26 8.3. AUTO-BANDWIDTH-ATTRIBUTES Sub-TLV . . . . . . . . . . . . 26
8.4. Error Object . . . . . . . . . . . . . . . . . . . . . . . 27 8.4. Error Object . . . . . . . . . . . . . . . . . . . . . . . 27
8.5. Notification Object . . . . . . . . . . . . . . . . . . . 27 8.5. Notification Object . . . . . . . . . . . . . . . . . . . 27
skipping to change at page 5, line 15 skipping to change at page 5, line 15
2.3. Terminology 2.3. Terminology
The reader is assumed to be familiar with the terminology defined in The reader is assumed to be familiar with the terminology defined in
[RFC5440], [RFC8231], and [RFC8281]. [RFC5440], [RFC8231], and [RFC8281].
The following auto-bandwidth terminology is defined in this document. The following auto-bandwidth terminology is defined in this document.
Maximum Average Bandwidth (MaxAvgBw): The maximum average bandwidth Maximum Average Bandwidth (MaxAvgBw): The maximum average bandwidth
represents the current traffic bandwidth demand of the LSP during represents the current traffic bandwidth demand of the LSP during
a time interval. This is the maximum value of the traffic a time interval. This is the maximum value of the traffic
bandwidth rate samples (Bandwidth-Samples) in a given bandwidth rate samples (Bandwidth-Samples) in a given time
Adjustment-Interval. interval.
Adjusted Bandwidth: This is the Auto-Bandwidth computed bandwidth Adjusted Bandwidth: This is the Auto-Bandwidth computed bandwidth
that is used to adjust the bandwidth reservation of the LSP. that is used to adjust the bandwidth reservation of the LSP.
Sample-Interval: The periodic time interval at which the measured Sample-Interval: The periodic time interval at which the measured
traffic rate of the LSP is collected as a Bandwidth-Sample. traffic rate of the LSP is collected as a Bandwidth-Sample.
Bandwidth-Sample: The bandwidth sample of the measured traffic rate Bandwidth-Sample: The bandwidth sample of the measured traffic rate
of the LSP collected at every Sample-Interval. of the LSP collected at every Sample-Interval.
skipping to change at page 5, line 40 skipping to change at page 5, line 40
Minimum-Bandwidth: The minimum bandwidth that can be reserved for Minimum-Bandwidth: The minimum bandwidth that can be reserved for
the LSP. the LSP.
Up-Adjustment-Interval: The periodic time interval at which the Up-Adjustment-Interval: The periodic time interval at which the
bandwidth adjustment should be made using the MaxAvgBw, when bandwidth adjustment should be made using the MaxAvgBw, when
MaxAvgBw is greater than the current bandwidth reservation of the MaxAvgBw is greater than the current bandwidth reservation of the
LSP. LSP.
Down-Adjustment-Interval: The periodic time interval at which the Down-Adjustment-Interval: The periodic time interval at which the
bandwidth adjustment should be made using the MaxAvgBw, when bandwidth adjustment should be made using the MaxAvgBw, when
MaxAvgBw is lesser than the current bandwidth reservation of the MaxAvgBw is less than the current bandwidth reservation of the
LSP. LSP.
Up-Adjustment-Threshold: This parameter is used to decide when the Up-Adjustment-Threshold: This parameter is used to decide when the
LSP bandwidth should be adjusted. If the percentage or absolute LSP bandwidth should be adjusted. If the percentage or absolute
difference between the current MaxAvgBw and the current bandwidth difference between the current MaxAvgBw and the current bandwidth
reservation is greater than or equal to the threshold value, the reservation is greater than or equal to the threshold value, the
LSP bandwidth is adjusted (upsized) to the current bandwidth LSP bandwidth is adjusted (upsized) to the current bandwidth
demand (Adjusted Bandwidth) at the Up-Adjustment-Interval expiry. demand (Adjusted Bandwidth) at the Up-Adjustment-Interval expiry.
Down-Adjustment-Threshold: This parameter is used to decide when the Down-Adjustment-Threshold: This parameter is used to decide when the
skipping to change at page 8, line 9 skipping to change at page 8, line 9
Figure 1: Overview of Auto-Bandwidth PCEP extensions Figure 1: Overview of Auto-Bandwidth PCEP extensions
The PCEP speaker supporting this document must have a mechanism to The PCEP speaker supporting this document must have a mechanism to
advertise the automatic bandwidth adjustment capability for both PCC- advertise the automatic bandwidth adjustment capability for both PCC-
Initiated and PCE-Initiated LSPs. Initiated and PCE-Initiated LSPs.
Auto-bandwidth deployment considerations for PCEP extensions are Auto-bandwidth deployment considerations for PCEP extensions are
summarized below: summarized below:
o It is required to identify and inform the PCC, the LSP that are o It is required to identify and inform the PCC, which LSPs are
enabled with Auto-Bandwidth feature. Not all LSPs in some enabled with Auto-Bandwidth feature. Not all LSPs in some
deployments would like their bandwidth to be dependent on the deployments would like their bandwidth to be dependent on the
real-time bandwidth usage but be constant as set by the operator. real-time bandwidth usage but be constant as set by the operator.
o In addition, an operator should be able to specify the auto- o In addition, an operator should be able to specify the auto-
bandwidth adjustment parameters (i.e. configuration knobs) to bandwidth adjustment parameters (i.e. configuration knobs) to
control this feature (e.g. minimum/ maximum bandwidth range). The control this feature (e.g. minimum/ maximum bandwidth range). The
PCC should be informed about these adjustment parameters. PCC should be informed about these adjustment parameters.
4. Architectural Overview 4. Architectural Overview
4.1. Auto-Bandwidth Overview 4.1. Auto-Bandwidth Overview
Auto-Bandwidth feature allows automatic and dynamic adjustment of the The Auto-Bandwidth feature allows automatic and dynamic adjustment of
reserved bandwidth of an LSP over time, i.e. without network operator the reserved bandwidth of an LSP over time (i.e., without network
intervention to accommodate the varying traffic demand of the LSP. operator intervention) to accommodate the varying traffic demand of
If the traffic flowing through the LSP is lower than the configured the LSP. If the traffic flowing through the LSP is lower than the
or current reserved bandwidth of the LSP, the extra bandwidth is configured or current reserved bandwidth of the LSP, the extra
being reserved needlessly and being wasted. Conversely, if the bandwidth is being reserved needlessly and being wasted. Conversely,
actual traffic flowing through the LSP is higher than the configured if the actual traffic flowing through the LSP is higher than the
or current reserved bandwidth of the LSP, it can potentially cause configured or current reserved bandwidth of the LSP, it can
congestion or packet loss in the network. The initial LSP bandwidth potentially cause congestion or packet loss in the network. The
can be set to an arbitrary value (including zero), in practice, it initial LSP bandwidth can be set to an arbitrary value (including
can be operator expected value based on design and planning. The zero), in practice, it can be operator expected value based on design
head-end Label Switch Router (LSR) monitors the actual traffic and planning. The head-end Label Switch Router (LSR) monitors the
flowing through the LSP and uses that information to adjust the actual traffic flowing through the LSP and uses that information to
bandwidth reservation of the LSP in the network. The bandwidth adjust the bandwidth reservation of the LSP in the network.
adjustment uses the make-before-break (MBB) signaling method so that Bandwidth adjustment must not cause disruption to the traffic flow
there is no disruption to the traffic flow carried by the LSP. carried by the LSP. One way to achieve this is to use the
make-before-break (MBB) signaling method.
4.2. Auto-bandwidth Theory of Operation 4.2. Auto-bandwidth Theory of Operation
This section describes the Auto-Bandwidth feature in a general way.
When the Auto-Bandwidth feature is enabled, the measured traffic rate When the Auto-Bandwidth feature is enabled, the measured traffic rate
is periodically sampled at each Sample-Interval (which can be is periodically sampled at each Sample-Interval (which can be
configured by an operator and the default value as 5 minutes) by the configured by an operator and the default value as 5 minutes) by the
PCC which is the head-end node of the LSP. The traffic rate samples PCC, when the PCC is the head-end node of the LSP. The traffic rate
are accumulated over the Adjustment-Interval period (which can be samples are accumulated over the Adjustment-Interval period (in the
configured by an operator and the default value as 24 hours). The Up or Down direction) (which can be configured by an operator and the
PCC, in-charge of calculating the bandwidth to be adjusted, will default value as 24 hours). The PCC, in-charge of calculating the
adjust the bandwidth of the LSP to the highest traffic rate sample bandwidth to be adjusted, can decide to adjust the bandwidth of the
(MaxAvgBw) amongst the set of bandwidth samples collected over the LSP to the highest traffic rate sample (MaxAvgBw) amongst the set of
adjustment-interval period (in the Up or Down direction). bandwidth samples collected over the adjustment-interval period (in
the Up or Down direction) depending on the operator policy.
Note that the highest traffic rate sample could be higher or lower Note that the highest traffic rate sample could be higher or lower
than the current LSP bandwidth. Only if the difference between the than the current LSP bandwidth. Only if the difference between the
current bandwidth demand (MaxAvgBw) and the current bandwidth current bandwidth demand (MaxAvgBw) and the current bandwidth
reservation is greater than or equal to the Adjustment-Threshold reservation is greater than or equal to the Adjustment-Threshold
(percentage or absolute value) (which can be configured by an (percentage or absolute value) (which can be configured by an
operator and the default as 5 percentage), the LSP bandwidth is operator and the default as 5 percentage), the LSP bandwidth is
adjusted (upsized) to the current bandwidth demand (MaxAvgBw). adjusted (upsized) to the current bandwidth demand (MaxAvgBw).
Similarly, if the difference between the current bandwidth Similarly, if the difference between the current bandwidth
reservation and the current bandwidth demand (MaxAvgBw) is greater reservation and the current bandwidth demand (MaxAvgBw) is greater
skipping to change at page 10, line 8 skipping to change at page 10, line 12
the percentage thresholds. This can lead to unnecessary re-signaling the percentage thresholds. This can lead to unnecessary re-signaling
of the LSPs in the network. This is suppressed by setting the of the LSPs in the network. This is suppressed by setting the
minimum-threshold parameters along with the percentage thresholds. minimum-threshold parameters along with the percentage thresholds.
The auto-bandwidth adjustment is only made if the LSP bandwidth The auto-bandwidth adjustment is only made if the LSP bandwidth
crosses both the percentage threshold and the minimum-threshold crosses both the percentage threshold and the minimum-threshold
parameters. parameters.
4.3. Scaling Considerations 4.3. Scaling Considerations
It should be noted that any bandwidth change requires re-signaling of It should be noted that any bandwidth change requires re-signaling of
an LSP in a make-before-break fashion, which can further trigger an LSP, which can further trigger preemption of lower priority LSPs
preemption of lower priority LSPs in the network. When deployed in the network. When deployed under scale, this can lead to a
under scale, this can lead to a signaling churn in the network. The signaling churn in the network. The Auto-bandwidth application
Auto-bandwidth application algorithm is thus advised to take this algorithm is thus advised to take this into consideration before
into consideration before adjusting the LSP bandwidth. Operators are adjusting the LSP bandwidth. Operators are advised to set the values
advised to set the values of various auto-bandwidth adjustment of various auto-bandwidth adjustment parameters appropriate for the
parameters appropriate for the deployed LSP scale. deployed LSP scale.
If a PCE gets overwhelmed, it can notify the PCC to temporarily If a PCE gets overwhelmed, it can notify the PCC to temporarily
suspend the reporting of the new LSP bandwidth to be adjusted (see suspend the reporting of the new LSP bandwidth to be adjusted (see
Section 5.7 of this document). Similarly, if a PCC gets overwhelmed Section 5.7 of this document). Similarly, if a PCC gets overwhelmed
due to signaling churn, it can notify the PCE to temporarily suspend due to signaling churn, it can notify the PCE to temporarily suspend
new LSP setup requests. new LSP setup requests.
5. Extensions to the PCEP 5. Extensions to the PCEP
5.1. Capability Advertisement 5.1. Capability Advertisement
skipping to change at page 10, line 44 skipping to change at page 10, line 48
o The PCEP protocol extensions for Auto-Bandwidth adjustments MUST o The PCEP protocol extensions for Auto-Bandwidth adjustments MUST
NOT be used if one or both PCEP speakers have not included the NOT be used if one or both PCEP speakers have not included the
"Auto-Bandwidth Capability" TLV in their respective OPEN message. "Auto-Bandwidth Capability" TLV in their respective OPEN message.
o The PCEP speaker that does not recognize the extensions defined in o The PCEP speaker that does not recognize the extensions defined in
this document sends the PCErr message with error-type 2 this document sends the PCErr message with error-type 2
(capability not supported) as per Section 6.9 in [RFC5440]. (capability not supported) as per Section 6.9 in [RFC5440].
o If the PCEP speaker that supports the extensions defined in this o If the PCEP speaker that supports the extensions defined in this
document but did not advertise this capability, then upon receipt document but did not advertise this capability, then upon receipt
of AUTO-BANDWIDTH-ATTRIBUTES TLV in the LSPA object, it SHOULD of AUTO-BANDWIDTH-ATTRIBUTES TLV in the LSP Attributes (LSPA)
generate a PCErr with error-type 19 (Invalid Operation), error- object, it SHOULD generate a PCErr with error-type 19 (Invalid
value TBD4 (Auto-Bandwidth capability was not advertised) and Operation), error-value TBD4 (Auto-Bandwidth capability was not
ignore the AUTO-BANDWIDTH-ATTRIBUTES TLV. advertised) and ignore the AUTO-BANDWIDTH-ATTRIBUTES TLV.
5.1.1. AUTO-BANDWIDTH-CAPABILITY TLV 5.1.1. AUTO-BANDWIDTH-CAPABILITY TLV
The AUTO-BANDWIDTH-CAPABILITY TLV is an optional TLV for use in the The AUTO-BANDWIDTH-CAPABILITY TLV is an optional TLV for use in the
OPEN Object for Automatic Bandwidth Adjustment via PCEP capability OPEN Object for Automatic Bandwidth Adjustment via PCEP capability
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
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
skipping to change at page 11, line 44 skipping to change at page 11, line 50
For PCE-Initiated LSP [RFC8281], this TLV is included in the LSPA For PCE-Initiated LSP [RFC8281], this TLV is included in the LSPA
Object with the PCInitiate message. For the PCC-Initiated delegated Object with the PCInitiate message. For the PCC-Initiated delegated
LSPs, this TLV is carried in the PCRpt message in LSPA Object. This LSPs, this TLV is carried in the PCRpt message in LSPA Object. This
TLV is also carried in the LSPA object with the PCUpd message to TLV is also carried in the LSPA object with the PCUpd message to
direct the PCC (LSP head-end) to make updates to auto-bandwidth direct the PCC (LSP head-end) to make updates to auto-bandwidth
attributes such as Adjustment-Interval. attributes such as Adjustment-Interval.
The TLV is encoded in all PCEP messages for the LSP while the auto- The TLV is encoded in all PCEP messages for the LSP while the auto-
bandwidth adjustment feature is enabled, the absence of the TLV bandwidth adjustment feature is enabled, the absence of the TLV
indicates the PCEP speaker wish to disable the feature. indicates the PCEP speaker wish to disable the feature. This TLV
includes multiple AUTO-BANDWIDTH-ATTRIBUTES sub-TLVs. The
AUTO-BANDWIDTH-ATTRIBUTES sub-TLVs are included if there is a change
since the last information sent in the PCEP message. The default
values for missing sub-TLVs apply for the first PCEP message for the
LSP.
The format of the AUTO-BANDWIDTH-ATTRIBUTES TLV is shown in the The format of the AUTO-BANDWIDTH-ATTRIBUTES TLV is shown in the
following figure: following figure:
0 1 2 3 0 1 2 3
0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Type=TBD1 | Length | | Type=TBD1 | Length |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| | | |
// sub-TLVs // // sub-TLVs //
| | | |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
AUTO-BANDWIDTH-ATTRIBUTES TLV format AUTO-BANDWIDTH-ATTRIBUTES TLV format
skipping to change at page 12, line 42 skipping to change at page 13, line 5
7 8 Down-Adjustment-Threshold-Percentage sub-TLV 7 8 Down-Adjustment-Threshold-Percentage sub-TLV
8 4 Minimum-Bandwidth sub-TLV 8 4 Minimum-Bandwidth sub-TLV
9 4 Maximum-Bandwidth sub-TLV 9 4 Maximum-Bandwidth sub-TLV
10 8 Overflow-Threshold sub-TLV 10 8 Overflow-Threshold sub-TLV
11 8 Overflow-Threshold-Percentage sub-TLV 11 8 Overflow-Threshold-Percentage sub-TLV
12 8 Underflow-Threshold sub-TLV 12 8 Underflow-Threshold sub-TLV
13 8 Underflow-Threshold-Percentage sub-TLV 13 8 Underflow-Threshold-Percentage sub-TLV
Future specification can define additional sub-TLVs. Future specification can define additional sub-TLVs.
The sub-TLVs are encoded to inform the PCEP peer the various sampling The sub-TLVs are encoded to inform the PCEP peer of the various
and adjustment parameters. If sub-TLVs are not present, the default sampling and adjustment parameters. If sub-TLVs are not present, the
values as specified in this document are used or otherwise based on default values as specified in this document are used or otherwise
the local policy are assumed. based on the local policy are assumed.
All sub-TLVs are optional and any unrecognized sub-TLV MUST be 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, ignored. If a sub-TLV of same type appears more than once, only the
only the first occurrence is processed and all others MUST be first occurrence is processed and all others MUST be ignored.
ignored.
The following sub-sections describe the sub-TLVs which are currently The following sub-sections describe the sub-TLVs which are currently
defined to be carried within the AUTO-BANDWIDTH-ATTRIBUTES TLV. defined to be carried within the AUTO-BANDWIDTH-ATTRIBUTES TLV.
5.2.1. Sample-Interval sub-TLV 5.2.1. Sample-Interval sub-TLV
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.
0 1 2 3 0 1 2 3
skipping to change at page 13, line 24 skipping to change at page 13, line 35
| Type=1 | Length=4 | | Type=1 | Length=4 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Sample-Interval | | Sample-Interval |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Sample-Interval sub-TLV format Sample-Interval sub-TLV format
The Type is 1, Length is 4 octets, and the value comprises of - The Type is 1, Length is 4 octets, and the value comprises of -
o Sample-Interval: The 4-octet time interval for bandwidth sample o Sample-Interval: The 4-octet time interval for bandwidth sample
collection. The valid range is from 1 to 604800, in seconds. The collection. The valid range is from 1 to 604800 (7 days), in
default value is 300 seconds. The sample-interval parameter MUST seconds. The default value is 300 seconds. The sample-interval
NOT be greater than the (down) adjustment-interval. parameter MUST NOT be greater than the (down) adjustment-interval,
otherwise the Sub-TLV MUST be ignored and the previous value is
maintained.
5.2.2. Adjustment Intervals 5.2.2. Adjustment Intervals
The sub-TLVs in this section are encoded to inform the PCEP peer the The sub-TLVs in this section are encoded to inform the PCEP peer the
adjustment interval parameters. An implementation MAY require to set adjustment interval parameters. An implementation MAY require to set
different adjustment interval values for when the bandwidth usage different adjustment interval values for when the bandwidth usage
trend is moving upwards or downwards. The Adjustment-Interval sub- trend is moving upwards or downwards. The Adjustment-Interval sub-
TLV specifies the time interval for both upward and downward trend. TLV specifies the time interval for both upward and downward trend.
If the operator would like to use a different adjustment interval If the operator would like to use a different adjustment interval
during the downward trend, the Down-Adjustment-Interval sub-TLV is during the downward trend, the Down-Adjustment-Interval sub-TLV is
skipping to change at page 14, line 4 skipping to change at page 14, line 15
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 of the LSP. than or less than the current bandwidth reservation of the LSP.
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 octets, and the value comprises of - The Type is 2, Length is 4 octets, and the value comprises of -
o Adjustment-Interval: The 4-octet time interval for bandwidth o Adjustment-Interval: The 4-octet time interval for bandwidth
adjustments. The valid range is from 1 to 604800, in seconds. adjustments. The valid range is from 1 to 604800 (7 days), in
The default value is 86400 seconds. The adjustment-interval seconds. The default value is 86400 seconds (1 day). The
parameter MUST NOT be less than the sample-interval. adjustment-interval parameter MUST NOT be less than the
sample-interval, otherwise the Sub-TLV MUST be ignored and the
previous value is maintained.
5.2.2.2. Down-Adjustment-Interval sub-TLV 5.2.2.2. Down-Adjustment-Interval sub-TLV
The Down-Adjustment-Interval sub-TLV specifies a time interval in The Down-Adjustment-Interval sub-TLV specifies a time interval in
seconds at which bandwidth adjustment should be made when MaxAvgBw is seconds at which bandwidth adjustment should be made when MaxAvgBw is
less than the current bandwidth reservation of the LSP. This less than the current bandwidth reservation of the LSP. This
parameter overwrites the Adjustment-Interval for the downward trend. parameter overwrites the Adjustment-Interval 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
skipping to change at page 14, line 36 skipping to change at page 14, line 50
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Down-Adjustment-Interval sub-TLV format Down-Adjustment-Interval sub-TLV format
The Type is 3, Length is 4 octets, and the value comprises of - The Type is 3, Length is 4 octets, and the value comprises of -
o Down-Adjustment-Interval: The 4-octet time interval for downward o Down-Adjustment-Interval: The 4-octet time interval for downward
bandwidth adjustments. The valid range is from 1 to 604800, in bandwidth adjustments. The valid range is from 1 to 604800, in
seconds. The default value equals the adjustment-interval. The seconds. The default value equals the adjustment-interval. The
down-adjustment-interval parameter MUST NOT be less than the down-adjustment-interval parameter MUST NOT be less than the
sample-interval. sample-interval, otherwise the Sub-TLV MUST be ignored and the
previous value is maintained.
5.2.3. Adjustment Thresholds 5.2.3. Adjustment Thresholds
The sub-TLVs in this section are encoded to inform the PCEP peer the The sub-TLVs in this section are encoded to inform the PCEP peer of
adjustment threshold parameters. An implementation MAY include both the adjustment threshold parameters. An implementation MAY include
sub-TLVs for the absolute value and the percentage, in which case the both sub-TLVs for the absolute value and the percentage, in which
bandwidth is adjusted when either of the adjustment threshold case the bandwidth is adjusted when either of the adjustment
conditions are met. The Adjustment-Threshold sub-TLV specifies the threshold conditions are met. The Adjustment-Threshold sub-TLV
threshold for both upward and downward trend. If the operator would specifies the threshold for both upward and downward trend. If the
like to use a different adjustment threshold during the downward operator would like to use a different adjustment threshold during
trend, the Down-Adjustment-Threshold sub-TLV is included. Similarly, the downward trend, the Down-Adjustment-Threshold sub-TLV is
the Adjustment-Threshold-Percentage sub-TLV specifies the threshold included. Similarly, the Adjustment-Threshold-Percentage sub-TLV
percentage for both upward and downward trend. If the operator would specifies the threshold percentage for both upward and downward
like to use a different adjustment threshold percentage during the trend. If the operator would like to use a different adjustment
downward trend, the Down-Adjustment-Threshold-Percentage sub-TLV is threshold percentage during the downward trend, the
included. Down-Adjustment-Threshold-Percentage sub-TLV is included. It is
worth noting that regardless of how the threshold are set, the
adjustment will not be made until at least one sample-interval simply
because no sample will be made on which to base a comparison with a
threshold.
5.2.3.1. Adjustment-Threshold sub-TLV 5.2.3.1. Adjustment-Threshold sub-TLV
The Adjustment-Threshold sub-TLV is used to decide when the LSP The Adjustment-Threshold sub-TLV is used to decide when the LSP
bandwidth should be adjusted 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 15, line 30 skipping to change at page 15, line 49
Adjustment-Threshold sub-TLV format Adjustment-Threshold sub-TLV format
The Type is 4, Length is 4 octets, and the value comprises of - The Type is 4, Length is 4 octets, and the value comprises of -
o Adjustment-Threshold: The absolute Adjustment-Threshold bandwidth o Adjustment-Threshold: The absolute Adjustment-Threshold bandwidth
value, encoded in IEEE floating point format (see value, encoded in IEEE floating point format (see
[IEEE.754.1985]), expressed in bytes per second. The default [IEEE.754.1985]), expressed in bytes per second. The default
adjustment-threshold value is not set. Refer to Section 3.1.2 of adjustment-threshold value is not set. Refer to Section 3.1.2 of
[RFC3471] for a table of commonly used values. [RFC3471] for a table of commonly used values.
If the difference between the current MaxAvgBw and the current If the modulus of difference between the current MaxAvgBw and the
bandwidth reservation is greater than or less than or equal to the current bandwidth reservation is greater than or equal to the
threshold value, the LSP bandwidth is adjusted to the current threshold value, the LSP bandwidth is adjusted to the current
bandwidth demand (MaxAvgBw). bandwidth demand (MaxAvgBw).
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
skipping to change at page 22, line 47 skipping to change at page 23, line 16
5.4. The PCInitiate Message 5.4. The PCInitiate Message
A PCInitiate message is a PCEP message sent by a PCE to a PCC to A PCInitiate message is a PCEP message sent by a PCE to a PCC to
trigger LSP instantiation or deletion [RFC8281]. trigger LSP instantiation or deletion [RFC8281].
For the PCE-Initiated LSP with Auto-Bandwidth feature enabled, AUTO- For the PCE-Initiated LSP with Auto-Bandwidth feature enabled, AUTO-
BANDWIDTH-ATTRIBUTES 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 (RBNF) of the PCInitiate message [RFC8281] is The Routing Backus-Naur Format (RBNF) definition of the PCInitiate
unchanged by this document. message [RFC8281] is unchanged by this document.
5.5. The PCUpd Message 5.5. The PCUpd Message
A PCUpd message is a PCEP message sent by a PCE to a PCC to update A PCUpd message is a PCEP message sent by a PCE to a PCC to update
the LSP parameters [RFC8231]. the LSP parameters [RFC8231].
For PCE-Initiated LSPs with Auto-Bandwidth feature enabled, AUTO- For PCE-Initiated LSPs with Auto-Bandwidth feature enabled, AUTO-
BANDWIDTH-ATTRIBUTES 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 (RBNF) of the PCUpd message [RFC8231] is unchanged by The RBNF definition of the PCUpd message [RFC8231] is unchanged by
this document. this document.
5.6. The PCRpt Message 5.6. The PCRpt Message
The PCRpt message [RFC8231] is a PCEP message sent by a PCC to a PCE The PCRpt message [RFC8231] is a PCEP message sent by a PCC to a PCE
to report the status of one or more LSPs. to report the status of one or more LSPs.
For PCE-Initiated LSPs [RFC8281], the PCC creates the LSP using the For PCE-Initiated LSPs [RFC8281], the PCC creates the LSP using the
attributes communicated by the PCE, and using the local values for attributes communicated by the PCE, and using the local values for
the unspecified parameters. After the successful instantiation of the unspecified parameters. After the successful instantiation of
skipping to change at page 23, line 35 skipping to change at page 24, line 5
For both PCE-Initiated and PCC-Initiated LSPs, when the LSP is For both PCE-Initiated and PCC-Initiated LSPs, when the LSP is
delegated to a PCE for the very first time as well as after the delegated to a PCE for the very first time as well as after the
successful delegation, the BANDWIDTH object of type 1 is used to successful delegation, the BANDWIDTH object of type 1 is used to
specify the requested bandwidth in the PCRpt message. specify the requested bandwidth in the PCRpt message.
For all LSPs with Auto-Bandwidth feature enabled, AUTO-BANDWIDTH- For all LSPs with Auto-Bandwidth feature enabled, AUTO-BANDWIDTH-
ATTRIBUTES TLV MUST be included in the LSPA object of the PCRpt ATTRIBUTES TLV MUST be included in the LSPA object of the PCRpt
message. message.
The definition (RBNF) of the PCRpt message [RFC8231] is unchanged by The RBNF definition of the PCRpt message [RFC8231] is unchanged by
this document. this document.
5.7. The PCNtf Message 5.7. The PCNtf Message
As per [RFC5440], the PCEP Notification message (PCNtf) can be sent As per [RFC5440], the PCEP Notification message (PCNtf) can be sent
by a PCEP speaker to notify its peer of a specific event. by a PCEP speaker to notify its peer of a specific event.
A PCEP speaker (PCE or PCC) SHOULD notify its PCEP peer (PCC or PCE) A PCEP speaker (PCE or PCC) SHOULD notify its PCEP peer (PCC or PCE)
when it is in overwhelmed state due to the auto-bandwidth feature. when it is in overwhelmed state due to the auto-bandwidth feature.
Upon receipt of such notification, the peer SHOULD NOT send any PCEP Upon receipt of such notification, the peer SHOULD NOT send any PCEP
messages related to auto-bandwidth adjustment. If a PCEP message messages related to auto-bandwidth adjustment. If a PCEP message
related to auto-bandwidth is received during in overwhelmed state, it related to auto-bandwidth is received during in overwhelmed state, it
MUST be silently ignored. MUST be ignored.
o When a PCEP speaker is overwhelmed, it SHOULD notify its peer by o When a PCEP speaker is overwhelmed, it SHOULD notify its peer by
sending a PCNtf message with Notification Type = TBD3 (Auto- sending a PCNtf message with Notification Type = TBD3 (Auto-
bandwidth Overwhelm State) and Notification Value = 1 (Entering bandwidth Overwhelm State) and Notification Value = 1 (Entering
auto-bandwidth overwhelm state). Optionally, OVERLOADED-DURATION auto-bandwidth overwhelm state). Optionally, OVERLOADED-DURATION
TLV [RFC5440] MAY be included that specifies the time period TLV [RFC5440] MAY be included that specifies the time period
during which no further PCEP messages related to auto-bandwidth during which no further PCEP messages related to auto-bandwidth
adjustment should be sent. adjustment should be sent.
o When the PCEP speaker is no longer in the overwhelm state and is o When the PCEP speaker is no longer in the overwhelm state and is
skipping to change at page 24, line 24 skipping to change at page 24, line 42
(Clearing auto-bandwidth overwhelm state). (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-
AUTO-BANDWIDTH-ATTRIBUTES TLV which do not add any new security BANDWIDTH-ATTRIBUTES sub-TLVs which do not add any new security
concerns beyond those discussed in [RFC5440] and [RFC8231] in itself. concerns beyond those already discussed in [RFC8231] and [RFC8281]
Some deployments may find the auto-bandwidth information as extra for stateful PCE operations. As per [RFC8231], it is RECOMMENDED
sensitive as it could be used to influence LSP path computation and that these PCEP extensions only be activated on authenticated and
LSP setup with adverse effect. Additionally, snooping of PCEP encrypted sessions across PCEs and PCCs belonging to the same
messages with such data or using PCEP messages for network administrative authority, using Transport Layer Security (TLS)
reconnaissance, may give an attacker sensitive information about the [RFC8253], as per the recommendations and best current practices in
operations of the network. Thus, such deployment should employ [RFC7525] (unless explicitly set aside in [RFC8253]).
suitable PCEP security mechanisms like TCP Authentication Option
(TCP-AO) [RFC5925] or [RFC8253].
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 LSP (at PCC The Auto-Bandwidth feature SHOULD be controlled per LSP (at PCC
(head-end of the LSP) or PCE) and the values for auto-bandwidth (head-end of the LSP) or PCE) and the values for auto-bandwidth
parameters e.g. sample-interval, adjustment-interval (up/down), parameters e.g. sample-interval, adjustment-interval (up/down),
minimum-bandwidth, maximum-bandwidth, adjustment-threshold (up/down) minimum-bandwidth, maximum-bandwidth, adjustment-threshold (up/down)
SHOULD be configurable by an operator. SHOULD be configurable by an operator.
skipping to change at page 26, line 39 skipping to change at page 26, line 39
o Defining RFC o Defining RFC
There is no bit defined for the AUTO-BANDWIDTH-CAPABILITY TLV Object There is no bit defined for the AUTO-BANDWIDTH-CAPABILITY TLV Object
flag field in this document. flag field in this document.
8.3. AUTO-BANDWIDTH-ATTRIBUTES Sub-TLV 8.3. AUTO-BANDWIDTH-ATTRIBUTES Sub-TLV
This document specifies the AUTO-BANDWIDTH-ATTRIBUTES Sub-TLVs. IANA This document specifies the AUTO-BANDWIDTH-ATTRIBUTES Sub-TLVs. IANA
is requested to create an "AUTO-BANDWIDTH-ATTRIBUTES Sub-TLV Types" is requested to create an "AUTO-BANDWIDTH-ATTRIBUTES Sub-TLV Types"
sub-registry in the "PCEP TLV Type Indicators" for the sub-TLVs sub-registry within the "Path Computation Element Protocol (PCEP)
carried in the AUTO-BANDWIDTH-ATTRIBUTES TLV. New sub-TLV are Numbers" registry to manage the type indicator space for sub-TLVs of
assigned by Standards Action [RFC8126]. the AUTO-BANDWIDTH-ATTRIBUTES TLV. The valid range of values in the
registry is 0-65535. IANA is requested to initialize the registry
with the following values. All other values in the registry should
be marked as "Unassigned".
IANA is requested to set the registration procedure for this registry
to read as follows:
0-65503 IETF Review
65504-65535 Experimental Use
This document defines the following types: This document defines the following types:
Type Name Reference Type Name Reference
----------------------------------------------------------------- -----------------------------------------------------------------
0 Reserved [This document] 0 Reserved [This document]
1 Sample-Interval sub-TLV [This document] 1 Sample-Interval sub-TLV [This document]
2 Adjustment-Interval sub-TLV [This document] 2 Adjustment-Interval sub-TLV [This document]
3 Down-Adjustment-Interval sub-TLV [This document] 3 Down-Adjustment-Interval sub-TLV [This document]
4 Adjustment-Threshold sub-TLV [This document] 4 Adjustment-Threshold sub-TLV [This document]
5 Adjustment-Threshold-Percentage sub-TLV [This document] 5 Adjustment-Threshold-Percentage sub-TLV [This document]
6 Down-Adjustment-Threshold sub-TLV [This document] 6 Down-Adjustment-Threshold sub-TLV [This document]
7 Down-Adjustment-Threshold-Percentage sub-TLV [This document] 7 Down-Adjustment-Threshold-Percentage sub-TLV [This document]
8 Minimum-Bandwidth sub-TLV [This document] 8 Minimum-Bandwidth sub-TLV [This document]
9 Maximum-Bandwidth sub-TLV [This document] 9 Maximum-Bandwidth sub-TLV [This document]
10 Overflow-Threshold sub-TLV [This document] 10 Overflow-Threshold sub-TLV [This document]
11 Overflow-Threshold-Percentage sub-TLV [This document] 11 Overflow-Threshold-Percentage sub-TLV [This document]
12 Underflow-Threshold sub-TLV [This document] 12 Underflow-Threshold sub-TLV [This document]
13 Underflow-Threshold-Percentage sub-TLV [This document] 13 Underflow-Threshold-Percentage sub-TLV [This document]
14- Unassigned [This document] 14- Unassigned [This document]
65535 65503
8.4. Error Object 8.4. Error Object
This document defines a new Error-Value for PCErr message of Error- This document defines a new Error-Value for PCErr message of Error-
Type 19 (Invalid Operation) [RFC8231]. IANA is requested to allocate Type 19 (Invalid Operation) [RFC8231]. IANA is requested to allocate
new error-value within the "PCEP-ERROR Object Error Types and Values" new error-value within the "PCEP-ERROR Object Error Types and Values"
subregistry of the PCEP Numbers registry, as follows: subregistry of the PCEP Numbers registry, as follows:
Error-Type Meaning & error values Reference Error-Type Meaning & error values Reference
----------------------------------------------------------------- -----------------------------------------------------------------
19 Invalid Operations 19 Invalid Operations
Error-Value = TBD4: [This document] Error-Value = TBD4: [This document]
Auto-Bandwidth Capability Auto-Bandwidth Capability
was not Advertised was not Advertised
8.5. Notification Object 8.5. Notification Object
IANA is requested to allocate new Notification Type and Notification IANA is requested to allocate new Notification Type 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 document] TBD3 Auto-Bandwidth Overwhelm State [This document]
skipping to change at page 28, line 43 skipping to change at page 28, line 43
Extensions for PCE-Initiated LSP Setup in a Stateful PCE, Extensions for PCE-Initiated LSP Setup in a Stateful PCE,
Model", RFC 8281, DOI 10.17487/RFC8281, December 2017, Model", RFC 8281, DOI 10.17487/RFC8281, December 2017,
<https://www.rfc-editor.org/info/rfc8281>. <https://www.rfc-editor.org/info/rfc8281>.
9.2. Informative References 9.2. Informative References
[RFC3471] Berger, L., "Generalized Multi-Protocol Label Switching [RFC3471] Berger, L., "Generalized Multi-Protocol Label Switching
(GMPLS) Signaling Functional Description", RFC 3471, (GMPLS) Signaling Functional Description", RFC 3471,
January 2003. January 2003.
[RFC5925] Touch, J., Mankin, A., and R. Bonica, "The TCP
Authentication Option", RFC 5925, June 2010.
[RFC7420] Koushik, A., Stephan, E., Zhao, Q., King, D., and J. [RFC7420] Koushik, A., Stephan, E., Zhao, Q., King, D., and J.
Hardwick, "Path Computation Element Communication Protocol Hardwick, "Path Computation Element Communication Protocol
(PCEP) Management Information Base (MIB) Module", RFC (PCEP) Management Information Base (MIB) Module", RFC
7420, December 2014. 7420, December 2014.
[RFC7525] Sheffer, Y., Holz, R. and P. Saint-Andre, "Recommendations
for Secure Use of Transport Layer Security (TLS) and
Datagram Transport Layer Security (DTLS)", BCP 195, RFC
7525, DOI 10.17487/RFC7525, May 2015.
[RFC8051] Zhang, X. and I. Minei, "Applicability of a Stateful Path [RFC8051] Zhang, X. and I. Minei, "Applicability of a Stateful Path
Computation Element (PCE)", RFC 8051, January 2017. Computation Element (PCE)", RFC 8051, January 2017.
[RFC8253] Lopez, D., Dios, O., Wu, W., and D. Dhody, "PCEPS: Usage [RFC8253] Lopez, D., Dios, O., Wu, W., and D. Dhody, "PCEPS: Usage
of TLS to Provide a Secure Transport for the Path of TLS to Provide a Secure Transport for the Path
Computation Element Communication Protocol (PCEP)", RFC Computation Element Communication Protocol (PCEP)", RFC
8253, October 2017, 8253, October 2017,
<https://www.rfc-editor.org/info/rfc8253>. <https://www.rfc-editor.org/info/rfc8253>.
[I-D.ietf-pce-pcep-yang] Dhody, D., Hardwick, J., Beeram, V., and J. [I-D.ietf-pce-pcep-yang] Dhody, D., Hardwick, J., Beeram, V., and J.
 End of changes. 46 change blocks. 
121 lines changed or deleted 147 lines changed or added

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