rfc8733xml2.original.xml		rfc8733.xml
	<?xml version='1.0' encoding='utf-8'?>		<?xml version='1.0' encoding='utf-8'?>
	<!DOCTYPE rfc SYSTEM "rfc2629.dtd" [		<rfc xmlns:xi="http://www.w3.org/2001/XInclude" version="3" category="std" conse
	<!ENTITY RFC2119 SYSTEM "https://xml2rfc.ietf.org/public/rfc/bibxml/reference.RF		nsus="true" docName="draft-ietf-pce-stateful-pce-auto-bandwidth-12" indexInclude
	C.2119.xml">		="true" ipr="trust200902" number="8733" prepTime="2020-02-25T16:36:04" scripts="
	<!ENTITY RFC5440 SYSTEM "https://xml2rfc.ietf.org/public/rfc/bibxml/reference.RF		Common,Latin" sortRefs="true" submissionType="IETF" symRefs="true" tocDepth="4"
	C.5440.xml">		tocInclude="true" xml:lang="en">
	<!ENTITY RFC7525 SYSTEM "https://xml2rfc.ietf.org/public/rfc/bibxml/reference.RF		<link href="https://datatracker.ietf.org/doc/draft-ietf-pce-stateful-pce-auto-
	C.7525.xml">		bandwidth-12" rel="prev"/>
	<!ENTITY RFC8126 SYSTEM "https://xml2rfc.ietf.org/public/rfc/bibxml/reference.RF		<link href="https://dx.doi.org/10.17487/rfc8733" rel="alternate"/>
	C.8126.xml">		<link href="urn:issn:2070-1721" rel="alternate"/>
	<!ENTITY RFC8174 SYSTEM "https://xml2rfc.ietf.org/public/rfc/bibxml/reference.RF		<front>
	C.8174.xml">		<title abbrev="Auto-Bandwidth with Stateful PCE">Path Computation Element Co
	<!ENTITY RFC8231 SYSTEM "https://xml2rfc.ietf.org/public/rfc/bibxml/reference.RF		mmunication Protocol (PCEP) Extensions for MPLS-TE Label Switched Path (LSP) Aut
	C.8231.xml">		o-Bandwidth Adjustment with Stateful PCE</title>
	<!ENTITY RFC8253 SYSTEM "https://xml2rfc.ietf.org/public/rfc/bibxml/reference.RF		<seriesInfo name="RFC" value="8733" stream="IETF"/>
	C.8253.xml">		<author fullname="Dhruv Dhody" initials="D." role="editor" surname="Dhody">
	<!ENTITY RFC8281 SYSTEM "https://xml2rfc.ietf.org/public/rfc/bibxml/reference.RF		<organization showOnFrontPage="true">Huawei Technologies</organization>
	C.8281.xml">		<address>
	<!ENTITY RFC3209 SYSTEM "https://xml2rfc.ietf.org/public/rfc/bibxml/reference.RF		<postal>
	C.3209.xml">		<street>Divyashree Techno Park, Whitefield</street>
	<!ENTITY RFC3471 SYSTEM "https://xml2rfc.ietf.org/public/rfc/bibxml/reference.RF		<city>Bangalore</city>
	C.3471.xml">		<region>Karnataka</region>
	<!ENTITY RFC7420 SYSTEM "https://xml2rfc.ietf.org/public/rfc/bibxml/reference.RF		<code>560066</code>
	C.7420.xml">		<country>India</country>
	<!ENTITY RFC8051 SYSTEM "https://xml2rfc.ietf.org/public/rfc/bibxml/reference.RF		</postal>
	C.8051.xml">		<email>dhruv.ietf@gmail.com</email>
	<!ENTITY I-D.ietf-pce-pcep-yang SYSTEM "https://xml2rfc.ietf.org/public/rfc/bibx		</address>
	ml3/reference.I-D.ietf-pce-pcep-yang.xml">		</author>
	]>		<author fullname="Rakesh Gandhi" initials="R." role="editor" surname="Gandhi
	<rfc submissionType="IETF" docName="draft-ietf-pce-stateful-pce-auto-bandwidth-1		">
	2" category="std" ipr="trust200902">		<organization showOnFrontPage="true">Cisco Systems, Inc.</organization>
	<!-- Generated by id2xml 1.5.0 on 2019-10-29T21:33:17Z -->		<address>
	<?rfc compact="yes"?>		<postal>
	<?rfc text-list-symbols="ooo*+-"?>		<country>Canada</country>
	<?rfc subcompact="no"?>		</postal>
	<?rfc sortrefs="yes"?>		<email>rgandhi@cisco.com</email>
	<?rfc symrefs="yes"?>		</address>
	<?rfc strict="yes"?>		</author>
	<?rfc toc="yes"?>		<author fullname="Udayasree Palle" initials="U." surname="Palle">
	<?rfc tocdepth="4"?>		<organization showOnFrontPage="true">Individual Contributor</organization>
	<front>		<address>
	<title abbrev="PCEP Extensions for MPLS-TE LSP Automati">PCEP Extensions		<email>udayasreereddy@gmail.com</email>
	for MPLS-TE LSP Automatic Bandwidth Adjustment with Stateful PCE</title>		</address>
	<author fullname="Dhruv Dhody" initials="D." role="editor" surname="Dhody		</author>
	">		<author fullname="Ravi Singh" initials="R." surname="Singh">
	<organization>Huawei Technologies</organization>		<organization showOnFrontPage="true">Individual Contributor</organization>
	<address><postal><street>Divyashree Techno Park, Whitefield</street>		<address>
	<street>Bangalore, Karnataka 560066</street>		<email>ravi.singh.ietf@gmail.com</email>
	<street>India</street>		</address>
	</postal>		</author>
	<email>dhruv.ietf@gmail.com</email>		<author fullname="Luyuan Fang" initials="L." surname="Fang">
	</address>		<organization showOnFrontPage="true">Expedia Group, Inc.</organization>
	</author>		<address>
			<postal>
	<author fullname="Rakesh Gandhi" initials="R." role="editor" surname="Gan		<country>United States of America</country>
	dhi">		</postal>
	<organization>Cisco Systems, Inc.</organization>		<email>luyuanf@gmail.com</email>
	<address><postal><street>Canada</street>		</address>
	</postal>		</author>
	<email>rgandhi@cisco.com</email>		<date month="02" year="2020"/>
	</address>		<workgroup>PCE Working Group</workgroup>
	</author>		<keyword>Bandwidth optimization</keyword>
			<keyword>PCEP Overwhelm</keyword>
	<author fullname="Udayasree Palle" initials="U." surname="Palle">		<keyword>LSP re-optimization</keyword>
	<organization>Individual Contributor</organization>		<abstract pn="section-abstract">
	<address><email>udayasreereddy@gmail.com</email>		<t pn="section-abstract-1">
	</address>
	</author>
	<author fullname="Ravi Singh" initials="R." surname="Singh">
	<organization>Individual Contributor</organization>
	<address><email>ravi.singh.ietf@gmail.com</email>
	</address>
	</author>
	<author fullname="Luyuan Fang" initials="L." surname="Fang">
	<organization>Expedia, Inc.</organization>
	<address><postal><street>USA</street>
	</postal>
	<email>luyuanf@gmail.com</email>
	</address>
	</author>
	<date month="October" year="2019"/>
	<workgroup>PCE Working Group</workgroup>
	<abstract><t>
	The Path Computation Element Communication Protocol (PCEP) provides		The Path Computation Element Communication Protocol (PCEP) provides
	mechanisms for Path Computation Elements (PCEs) to perform path		mechanisms for Path Computation Elements (PCEs) to perform path
	computations in response to Path Computation Clients (PCCs) requests.		computations in response to Path Computation Client (PCC) requests.
	The Stateful PCE extensions allow stateful control of Multi-Protocol		Stateful PCE extensions allow stateful control of MPLS-TE Label Switched Path
	Label Switching (MPLS) Traffic Engineering Label Switched Paths (TE		s (LSPs) using PCEP.</t>
	LSPs) using PCEP.</t>		<t pn="section-abstract-2">
			The auto-bandwidth feature allows automatic and dynamic
	<t>
	The automatic bandwidth feature allows automatic and dynamic
	adjustment of the TE LSP bandwidth reservation based on the volume of		adjustment of the TE LSP bandwidth reservation based on the volume of
	traffic flowing through the LSP. This document describes PCEP		traffic flowing through the LSP. This document describes PCEP
	extensions for automatic bandwidth adjustment when employing an		extensions for auto-bandwidth adjustment when employing an
	Active Stateful PCE for both PCE-Initiated and PCC-Initiated LSPs.</t>		active stateful PCE for both PCE-initiated and PCC-initiated LSPs.</t>
			</abstract>
	</abstract>		<boilerplate>
	</front>		<section anchor="status-of-memo" numbered="false" removeInRFC="false" toc=
			"exclude" pn="section-boilerplate.1">
	<middle>		<name slugifiedName="name-status-of-this-memo">Status of This Memo</name
	<section title="Introduction" anchor="sect-1"><t>		>
	<xref target="RFC5440"/> describes the Path Computation Element Protocol (PCE		<t pn="section-boilerplate.1-1">
	P) as a		This is an Internet Standards Track document.
			</t>
			<t pn="section-boilerplate.1-2">
			This document is a product of the Internet Engineering Task Force
			(IETF). It represents the consensus of the IETF community. It has
			received public review and has been approved for publication by
			the Internet Engineering Steering Group (IESG). Further
			information on Internet Standards is available in Section 2 of
			RFC 7841.
			</t>
			<t pn="section-boilerplate.1-3">
			Information about the current status of this document, any
			errata, and how to provide feedback on it may be obtained at
			<eref target="https://www.rfc-editor.org/info/rfc8733" brackets="non
			e"/>.
			</t>
			</section>
			<section anchor="copyright" numbered="false" removeInRFC="false" toc="excl
			ude" pn="section-boilerplate.2">
			<name slugifiedName="name-copyright-notice">Copyright Notice</name>
			<t pn="section-boilerplate.2-1">
			Copyright (c) 2020 IETF Trust and the persons identified as the
			document authors. All rights reserved.
			</t>
			<t pn="section-boilerplate.2-2">
			This document is subject to BCP 78 and the IETF Trust's Legal
			Provisions Relating to IETF Documents
			(<eref target="https://trustee.ietf.org/license-info" brackets="none
			"/>) in effect on the date of
			publication of this document. Please review these documents
			carefully, as they describe your rights and restrictions with
			respect to this document. Code Components extracted from this
			document must include Simplified BSD License text as described in
			Section 4.e of the Trust Legal Provisions and are provided without
			warranty as described in the Simplified BSD License.
			</t>
			</section>
			</boilerplate>
			<toc>
			<section anchor="toc" numbered="false" removeInRFC="false" toc="exclude" p
			n="section-toc.1">
			<name slugifiedName="name-table-of-contents">Table of Contents</name>
			<ul bare="true" empty="true" indent="2" spacing="compact" pn="section-to
			c.1-1">
			<li pn="section-toc.1-1.1">
			<t keepWithNext="true" pn="section-toc.1-1.1.1"><xref derivedContent
			="1" format="counter" sectionFormat="of" target="section-1"/>.  <xref derivedCon
			tent="" format="title" sectionFormat="of" target="name-introduction">Introductio
			n</xref></t>
			</li>
			<li pn="section-toc.1-1.2">
			<t keepWithNext="true" pn="section-toc.1-1.2.1"><xref derivedContent
			="2" format="counter" sectionFormat="of" target="section-2"/>.  <xref derivedCon
			tent="" format="title" sectionFormat="of" target="name-conventions-used-in-this-
			do">Conventions Used in This Document</xref></t>
			<ul bare="true" empty="true" indent="2" spacing="compact" pn="sectio
			n-toc.1-1.2.2">
			<li pn="section-toc.1-1.2.2.1">
			<t keepWithNext="true" pn="section-toc.1-1.2.2.1.1"><xref derive
			dContent="2.1" format="counter" sectionFormat="of" target="section-2.1"/>.  <xre
			f derivedContent="" format="title" sectionFormat="of" target="name-requirements-
			language">Requirements Language</xref></t>
			</li>
			<li pn="section-toc.1-1.2.2.2">
			<t keepWithNext="true" pn="section-toc.1-1.2.2.2.1"><xref derive
			dContent="2.2" format="counter" sectionFormat="of" target="section-2.2"/>.  <xre
			f derivedContent="" format="title" sectionFormat="of" target="name-abbreviations
			">Abbreviations</xref></t>
			</li>
			<li pn="section-toc.1-1.2.2.3">
			<t keepWithNext="true" pn="section-toc.1-1.2.2.3.1"><xref derive
			dContent="2.3" format="counter" sectionFormat="of" target="section-2.3"/>.  <xre
			f derivedContent="" format="title" sectionFormat="of" target="name-terminology">
			Terminology</xref></t>
			</li>
			</ul>
			</li>
			<li pn="section-toc.1-1.3">
			<t keepWithNext="true" pn="section-toc.1-1.3.1"><xref derivedContent
			="3" format="counter" sectionFormat="of" target="section-3"/>.  <xref derivedCon
			tent="" format="title" sectionFormat="of" target="name-requirements-for-pcep-ext
			en">Requirements for PCEP Extensions</xref></t>
			</li>
			<li pn="section-toc.1-1.4">
			<t keepWithNext="true" pn="section-toc.1-1.4.1"><xref derivedContent
			="4" format="counter" sectionFormat="of" target="section-4"/>.  <xref derivedCon
			tent="" format="title" sectionFormat="of" target="name-architectural-overview">A
			rchitectural Overview</xref></t>
			<ul bare="true" empty="true" indent="2" spacing="compact" pn="sectio
			n-toc.1-1.4.2">
			<li pn="section-toc.1-1.4.2.1">
			<t keepWithNext="true" pn="section-toc.1-1.4.2.1.1"><xref derive
			dContent="4.1" format="counter" sectionFormat="of" target="section-4.1"/>.  <xre
			f derivedContent="" format="title" sectionFormat="of" target="name-auto-bandwidt
			h-overview">Auto-Bandwidth Overview</xref></t>
			</li>
			<li pn="section-toc.1-1.4.2.2">
			<t keepWithNext="true" pn="section-toc.1-1.4.2.2.1"><xref derive
			dContent="4.2" format="counter" sectionFormat="of" target="section-4.2"/>.  <xre
			f derivedContent="" format="title" sectionFormat="of" target="name-auto-bandwidt
			h-theory-of-op">Auto-Bandwidth Theory of Operation</xref></t>
			</li>
			<li pn="section-toc.1-1.4.2.3">
			<t keepWithNext="true" pn="section-toc.1-1.4.2.3.1"><xref derive
			dContent="4.3" format="counter" sectionFormat="of" target="section-4.3"/>.  <xre
			f derivedContent="" format="title" sectionFormat="of" target="name-scaling-consi
			derations">Scaling Considerations</xref></t>
			</li>
			</ul>
			</li>
			<li pn="section-toc.1-1.5">
			<t keepWithNext="true" pn="section-toc.1-1.5.1"><xref derivedContent
			="5" format="counter" sectionFormat="of" target="section-5"/>.  <xref derivedCon
			tent="" format="title" sectionFormat="of" target="name-pcep-extensions">PCEP Ext
			ensions</xref></t>
			<ul bare="true" empty="true" indent="2" spacing="compact" pn="sectio
			n-toc.1-1.5.2">
			<li pn="section-toc.1-1.5.2.1">
			<t keepWithNext="true" pn="section-toc.1-1.5.2.1.1"><xref derive
			dContent="5.1" format="counter" sectionFormat="of" target="section-5.1"/>.  <xre
			f derivedContent="" format="title" sectionFormat="of" target="name-capability-ad
			vertisement">Capability Advertisement</xref></t>
			<ul bare="true" empty="true" indent="2" spacing="compact" pn="se
			ction-toc.1-1.5.2.1.2">
			<li pn="section-toc.1-1.5.2.1.2.1">
			<t keepWithNext="true" pn="section-toc.1-1.5.2.1.2.1.1"><xre
			f derivedContent="5.1.1" format="counter" sectionFormat="of" target="section-5.1
			.1"/>.  <xref derivedContent="" format="title" sectionFormat="of" target="name-a
			uto-bandwidth-capability-t">AUTO-BANDWIDTH-CAPABILITY TLV</xref></t>
			</li>
			</ul>
			</li>
			<li pn="section-toc.1-1.5.2.2">
			<t keepWithNext="true" pn="section-toc.1-1.5.2.2.1"><xref derive
			dContent="5.2" format="counter" sectionFormat="of" target="section-5.2"/>.  <xre
			f derivedContent="" format="title" sectionFormat="of" target="name-auto-bandwidt
			h-attributes-t">AUTO-BANDWIDTH-ATTRIBUTES TLV</xref></t>
			<ul bare="true" empty="true" indent="2" spacing="compact" pn="se
			ction-toc.1-1.5.2.2.2">
			<li pn="section-toc.1-1.5.2.2.2.1">
			<t keepWithNext="true" pn="section-toc.1-1.5.2.2.2.1.1"><xre
			f derivedContent="5.2.1" format="counter" sectionFormat="of" target="section-5.2
			.1"/>.  <xref derivedContent="" format="title" sectionFormat="of" target="name-s
			ample-interval-sub-tlv">Sample-Interval Sub-TLV</xref></t>
			</li>
			<li pn="section-toc.1-1.5.2.2.2.2">
			<t keepWithNext="true" pn="section-toc.1-1.5.2.2.2.2.1"><xre
			f derivedContent="5.2.2" format="counter" sectionFormat="of" target="section-5.2
			.2"/>.  <xref derivedContent="" format="title" sectionFormat="of" target="name-a
			djustment-intervals">Adjustment-Intervals</xref></t>
			<ul bare="true" empty="true" indent="2" spacing="compact" pn
			="section-toc.1-1.5.2.2.2.2.2">
			<li pn="section-toc.1-1.5.2.2.2.2.2.1">
			<t keepWithNext="true" pn="section-toc.1-1.5.2.2.2.2.2.1
			.1"><xref derivedContent="5.2.2.1" format="counter" sectionFormat="of" target="s
			ection-5.2.2.1"/>.  <xref derivedContent="" format="title" sectionFormat="of" ta
			rget="name-adjustment-interval-sub-tlv">Adjustment-Interval Sub-TLV</xref></t>
			</li>
			<li pn="section-toc.1-1.5.2.2.2.2.2.2">
			<t keepWithNext="true" pn="section-toc.1-1.5.2.2.2.2.2.2
			.1"><xref derivedContent="5.2.2.2" format="counter" sectionFormat="of" target="s
			ection-5.2.2.2"/>.  <xref derivedContent="" format="title" sectionFormat="of" ta
			rget="name-down-adjustment-interval-su">Down-Adjustment-Interval Sub-TLV</xref><
			/t>
			</li>
			</ul>
			</li>
			<li pn="section-toc.1-1.5.2.2.2.3">
			<t keepWithNext="true" pn="section-toc.1-1.5.2.2.2.3.1"><xre
			f derivedContent="5.2.3" format="counter" sectionFormat="of" target="section-5.2
			.3"/>.  <xref derivedContent="" format="title" sectionFormat="of" target="name-a
			djustment-thresholds">Adjustment-Thresholds</xref></t>
			<ul bare="true" empty="true" indent="2" spacing="compact" pn
			="section-toc.1-1.5.2.2.2.3.2">
			<li pn="section-toc.1-1.5.2.2.2.3.2.1">
			<t keepWithNext="true" pn="section-toc.1-1.5.2.2.2.3.2.1
			.1"><xref derivedContent="5.2.3.1" format="counter" sectionFormat="of" target="s
			ection-5.2.3.1"/>.  <xref derivedContent="" format="title" sectionFormat="of" ta
			rget="name-adjustment-threshold-sub-tl">Adjustment-Threshold Sub-TLV</xref></t>
			</li>
			<li pn="section-toc.1-1.5.2.2.2.3.2.2">
			<t keepWithNext="true" pn="section-toc.1-1.5.2.2.2.3.2.2
			.1"><xref derivedContent="5.2.3.2" format="counter" sectionFormat="of" target="s
			ection-5.2.3.2"/>.  <xref derivedContent="" format="title" sectionFormat="of" ta
			rget="name-adjustment-threshold-percen">Adjustment-Threshold-Percentage Sub-TLV<
			/xref></t>
			</li>
			<li pn="section-toc.1-1.5.2.2.2.3.2.3">
			<t keepWithNext="true" pn="section-toc.1-1.5.2.2.2.3.2.3
			.1"><xref derivedContent="5.2.3.3" format="counter" sectionFormat="of" target="s
			ection-5.2.3.3"/>.  <xref derivedContent="" format="title" sectionFormat="of" ta
			rget="name-down-adjustment-threshold-s">Down-Adjustment-Threshold Sub-TLV</xref>
			</t>
			</li>
			<li pn="section-toc.1-1.5.2.2.2.3.2.4">
			<t keepWithNext="true" pn="section-toc.1-1.5.2.2.2.3.2.4
			.1"><xref derivedContent="5.2.3.4" format="counter" sectionFormat="of" target="s
			ection-5.2.3.4"/>.  <xref derivedContent="" format="title" sectionFormat="of" ta
			rget="name-down-adjustment-threshold-p">Down-Adjustment-Threshold-Percentage Sub
			-TLV</xref></t>
			</li>
			</ul>
			</li>
			<li pn="section-toc.1-1.5.2.2.2.4">
			<t keepWithNext="true" pn="section-toc.1-1.5.2.2.2.4.1"><xre
			f derivedContent="5.2.4" format="counter" sectionFormat="of" target="section-5.2
			.4"/>.  <xref derivedContent="" format="title" sectionFormat="of" target="name-m
			inimum-and-maximum-bandwid">Minimum and Maximum-Bandwidth Values</xref></t>
			<ul bare="true" empty="true" indent="2" spacing="compact" pn
			="section-toc.1-1.5.2.2.2.4.2">
			<li pn="section-toc.1-1.5.2.2.2.4.2.1">
			<t keepWithNext="true" pn="section-toc.1-1.5.2.2.2.4.2.1
			.1"><xref derivedContent="5.2.4.1" format="counter" sectionFormat="of" target="s
			ection-5.2.4.1"/>.  <xref derivedContent="" format="title" sectionFormat="of" ta
			rget="name-minimum-bandwidth-sub-tlv">Minimum-Bandwidth Sub-TLV</xref></t>
			</li>
			<li pn="section-toc.1-1.5.2.2.2.4.2.2">
			<t keepWithNext="true" pn="section-toc.1-1.5.2.2.2.4.2.2
			.1"><xref derivedContent="5.2.4.2" format="counter" sectionFormat="of" target="s
			ection-5.2.4.2"/>.  <xref derivedContent="" format="title" sectionFormat="of" ta
			rget="name-maximum-bandwidth-sub-tlv">Maximum-Bandwidth Sub-TLV</xref></t>
			</li>
			</ul>
			</li>
			<li pn="section-toc.1-1.5.2.2.2.5">
			<t keepWithNext="true" pn="section-toc.1-1.5.2.2.2.5.1"><xre
			f derivedContent="5.2.5" format="counter" sectionFormat="of" target="section-5.2
			.5"/>.  <xref derivedContent="" format="title" sectionFormat="of" target="name-o
			verflow-and-underflow-cond">Overflow and Underflow Conditions</xref></t>
			<ul bare="true" empty="true" indent="2" spacing="compact" pn
			="section-toc.1-1.5.2.2.2.5.2">
			<li pn="section-toc.1-1.5.2.2.2.5.2.1">
			<t keepWithNext="true" pn="section-toc.1-1.5.2.2.2.5.2.1
			.1"><xref derivedContent="5.2.5.1" format="counter" sectionFormat="of" target="s
			ection-5.2.5.1"/>.  <xref derivedContent="" format="title" sectionFormat="of" ta
			rget="name-overflow-threshold-sub-tlv">Overflow-Threshold Sub-TLV</xref></t>
			</li>
			<li pn="section-toc.1-1.5.2.2.2.5.2.2">
			<t keepWithNext="true" pn="section-toc.1-1.5.2.2.2.5.2.2
			.1"><xref derivedContent="5.2.5.2" format="counter" sectionFormat="of" target="s
			ection-5.2.5.2"/>.  <xref derivedContent="" format="title" sectionFormat="of" ta
			rget="name-overflow-threshold-percenta">Overflow-Threshold-Percentage Sub-TLV</x
			ref></t>
			</li>
			<li pn="section-toc.1-1.5.2.2.2.5.2.3">
			<t keepWithNext="true" pn="section-toc.1-1.5.2.2.2.5.2.3
			.1"><xref derivedContent="5.2.5.3" format="counter" sectionFormat="of" target="s
			ection-5.2.5.3"/>.  <xref derivedContent="" format="title" sectionFormat="of" ta
			rget="name-underflow-threshold-sub-tlv">Underflow-Threshold Sub-TLV</xref></t>
			</li>
			<li pn="section-toc.1-1.5.2.2.2.5.2.4">
			<t keepWithNext="true" pn="section-toc.1-1.5.2.2.2.5.2.4
			.1"><xref derivedContent="5.2.5.4" format="counter" sectionFormat="of" target="s
			ection-5.2.5.4"/>.  <xref derivedContent="" format="title" sectionFormat="of" ta
			rget="name-underflow-threshold-percent">Underflow-Threshold-Percentage Sub-TLV</
			xref></t>
			</li>
			</ul>
			</li>
			</ul>
			</li>
			<li pn="section-toc.1-1.5.2.3">
			<t keepWithNext="true" pn="section-toc.1-1.5.2.3.1"><xref derive
			dContent="5.3" format="counter" sectionFormat="of" target="section-5.3"/>.  <xre
			f derivedContent="" format="title" sectionFormat="of" target="name-bandwidth-obj
			ect">BANDWIDTH Object</xref></t>
			</li>
			<li pn="section-toc.1-1.5.2.4">
			<t keepWithNext="true" pn="section-toc.1-1.5.2.4.1"><xref derive
			dContent="5.4" format="counter" sectionFormat="of" target="section-5.4"/>.  <xre
			f derivedContent="" format="title" sectionFormat="of" target="name-the-pcinitiat
			e-message">The PCInitiate Message</xref></t>
			</li>
			<li pn="section-toc.1-1.5.2.5">
			<t keepWithNext="true" pn="section-toc.1-1.5.2.5.1"><xref derive
			dContent="5.5" format="counter" sectionFormat="of" target="section-5.5"/>.  <xre
			f derivedContent="" format="title" sectionFormat="of" target="name-the-pcupd-mes
			sage">The PCUpd Message</xref></t>
			</li>
			<li pn="section-toc.1-1.5.2.6">
			<t keepWithNext="true" pn="section-toc.1-1.5.2.6.1"><xref derive
			dContent="5.6" format="counter" sectionFormat="of" target="section-5.6"/>.  <xre
			f derivedContent="" format="title" sectionFormat="of" target="name-the-pcrpt-mes
			sage">The PCRpt Message</xref></t>
			</li>
			<li pn="section-toc.1-1.5.2.7">
			<t keepWithNext="true" pn="section-toc.1-1.5.2.7.1"><xref derive
			dContent="5.7" format="counter" sectionFormat="of" target="section-5.7"/>.  <xre
			f derivedContent="" format="title" sectionFormat="of" target="name-the-pcntf-mes
			sage">The PCNtf Message</xref></t>
			</li>
			</ul>
			</li>
			<li pn="section-toc.1-1.6">
			<t keepWithNext="true" pn="section-toc.1-1.6.1"><xref derivedContent
			="6" format="counter" sectionFormat="of" target="section-6"/>.  <xref derivedCon
			tent="" format="title" sectionFormat="of" target="name-manageability-considerati
			on">Manageability Considerations</xref></t>
			<ul bare="true" empty="true" indent="2" spacing="compact" pn="sectio
			n-toc.1-1.6.2">
			<li pn="section-toc.1-1.6.2.1">
			<t keepWithNext="true" pn="section-toc.1-1.6.2.1.1"><xref derive
			dContent="6.1" format="counter" sectionFormat="of" target="section-6.1"/>.  <xre
			f derivedContent="" format="title" sectionFormat="of" target="name-control-of-fu
			nction-and-pol">Control of Function and Policy</xref></t>
			</li>
			<li pn="section-toc.1-1.6.2.2">
			<t keepWithNext="true" pn="section-toc.1-1.6.2.2.1"><xref derive
			dContent="6.2" format="counter" sectionFormat="of" target="section-6.2"/>.  <xre
			f derivedContent="" format="title" sectionFormat="of" target="name-information-a
			nd-data-models">Information and Data Models</xref></t>
			</li>
			<li pn="section-toc.1-1.6.2.3">
			<t keepWithNext="true" pn="section-toc.1-1.6.2.3.1"><xref derive
			dContent="6.3" format="counter" sectionFormat="of" target="section-6.3"/>.  <xre
			f derivedContent="" format="title" sectionFormat="of" target="name-liveness-dete
			ction-and-moni">Liveness Detection and Monitoring</xref></t>
			</li>
			<li pn="section-toc.1-1.6.2.4">
			<t keepWithNext="true" pn="section-toc.1-1.6.2.4.1"><xref derive
			dContent="6.4" format="counter" sectionFormat="of" target="section-6.4"/>.  <xre
			f derivedContent="" format="title" sectionFormat="of" target="name-verifying-cor
			rect-operation">Verifying Correct Operations</xref></t>
			</li>
			<li pn="section-toc.1-1.6.2.5">
			<t keepWithNext="true" pn="section-toc.1-1.6.2.5.1"><xref derive
			dContent="6.5" format="counter" sectionFormat="of" target="section-6.5"/>.  <xre
			f derivedContent="" format="title" sectionFormat="of" target="name-requirements-
			for-other-prot">Requirements for Other Protocols</xref></t>
			</li>
			<li pn="section-toc.1-1.6.2.6">
			<t keepWithNext="true" pn="section-toc.1-1.6.2.6.1"><xref derive
			dContent="6.6" format="counter" sectionFormat="of" target="section-6.6"/>.  <xre
			f derivedContent="" format="title" sectionFormat="of" target="name-impact-on-net
			work-operation">Impact on Network Operations</xref></t>
			</li>
			</ul>
			</li>
			<li pn="section-toc.1-1.7">
			<t keepWithNext="true" pn="section-toc.1-1.7.1"><xref derivedContent
			="7" format="counter" sectionFormat="of" target="section-7"/>.  <xref derivedCon
			tent="" format="title" sectionFormat="of" target="name-security-considerations">
			Security Considerations</xref></t>
			</li>
			<li pn="section-toc.1-1.8">
			<t keepWithNext="true" pn="section-toc.1-1.8.1"><xref derivedContent
			="8" format="counter" sectionFormat="of" target="section-8"/>.  <xref derivedCon
			tent="" format="title" sectionFormat="of" target="name-iana-considerations">IANA
			Considerations</xref></t>
			<ul bare="true" empty="true" indent="2" spacing="compact" pn="sectio
			n-toc.1-1.8.2">
			<li pn="section-toc.1-1.8.2.1">
			<t keepWithNext="true" pn="section-toc.1-1.8.2.1.1"><xref derive
			dContent="8.1" format="counter" sectionFormat="of" target="section-8.1"/>.  <xre
			f derivedContent="" format="title" sectionFormat="of" target="name-pcep-tlv-type
			-indicators">PCEP TLV Type Indicators</xref></t>
			</li>
			<li pn="section-toc.1-1.8.2.2">
			<t keepWithNext="true" pn="section-toc.1-1.8.2.2.1"><xref derive
			dContent="8.2" format="counter" sectionFormat="of" target="section-8.2"/>.  <xre
			f derivedContent="" format="title" sectionFormat="of" target="name-auto-bandwidt
			h-capability-tlv">AUTO-BANDWIDTH-CAPABILITY TLV Flag Field</xref></t>
			</li>
			<li pn="section-toc.1-1.8.2.3">
			<t keepWithNext="true" pn="section-toc.1-1.8.2.3.1"><xref derive
			dContent="8.3" format="counter" sectionFormat="of" target="section-8.3"/>.  <xre
			f derivedContent="" format="title" sectionFormat="of" target="name-auto-bandwidt
			h-attributes-s">AUTO-BANDWIDTH-ATTRIBUTES Sub-TLV</xref></t>
			</li>
			<li pn="section-toc.1-1.8.2.4">
			<t keepWithNext="true" pn="section-toc.1-1.8.2.4.1"><xref derive
			dContent="8.4" format="counter" sectionFormat="of" target="section-8.4"/>.  <xre
			f derivedContent="" format="title" sectionFormat="of" target="name-error-object"
			>Error Object</xref></t>
			</li>
			<li pn="section-toc.1-1.8.2.5">
			<t keepWithNext="true" pn="section-toc.1-1.8.2.5.1"><xref derive
			dContent="8.5" format="counter" sectionFormat="of" target="section-8.5"/>.  <xre
			f derivedContent="" format="title" sectionFormat="of" target="name-notification-
			object">Notification Object</xref></t>
			</li>
			</ul>
			</li>
			<li pn="section-toc.1-1.9">
			<t keepWithNext="true" pn="section-toc.1-1.9.1"><xref derivedContent
			="9" format="counter" sectionFormat="of" target="section-9"/>.  <xref derivedCon
			tent="" format="title" sectionFormat="of" target="name-references">References</x
			ref></t>
			<ul bare="true" empty="true" indent="2" spacing="compact" pn="sectio
			n-toc.1-1.9.2">
			<li pn="section-toc.1-1.9.2.1">
			<t keepWithNext="true" pn="section-toc.1-1.9.2.1.1"><xref derive
			dContent="9.1" format="counter" sectionFormat="of" target="section-9.1"/>.  <xre
			f derivedContent="" format="title" sectionFormat="of" target="name-normative-ref
			erences">Normative References</xref></t>
			</li>
			<li pn="section-toc.1-1.9.2.2">
			<t keepWithNext="true" pn="section-toc.1-1.9.2.2.1"><xref derive
			dContent="9.2" format="counter" sectionFormat="of" target="section-9.2"/>.  <xre
			f derivedContent="" format="title" sectionFormat="of" target="name-informative-r
			eferences">Informative References</xref></t>
			</li>
			</ul>
			</li>
			<li pn="section-toc.1-1.10">
			<t keepWithNext="true" pn="section-toc.1-1.10.1"><xref derivedConten
			t="" format="none" sectionFormat="of" target="section-appendix.a"/><xref derived
			Content="" format="title" sectionFormat="of" target="name-acknowledgments">Ackno
			wledgments</xref></t>
			</li>
			<li pn="section-toc.1-1.11">
			<t keepWithNext="true" pn="section-toc.1-1.11.1"><xref derivedConten
			t="" format="none" sectionFormat="of" target="section-appendix.b"/><xref derived
			Content="" format="title" sectionFormat="of" target="name-contributors">Contribu
			tors</xref></t>
			</li>
			<li pn="section-toc.1-1.12">
			<t keepWithNext="true" pn="section-toc.1-1.12.1"><xref derivedConten
			t="" format="none" sectionFormat="of" target="section-appendix.c"/><xref derived
			Content="" format="title" sectionFormat="of" target="name-authors-addresses">Aut
			hors' Addresses</xref></t>
			</li>
			</ul>
			</section>
			</toc>
			</front>
			<middle>
			<section anchor="sect-1" numbered="true" toc="include" removeInRFC="false" p
			n="section-1">
			<name slugifiedName="name-introduction">Introduction</name>
			<t pn="section-1-1">
			<xref target="RFC5440" format="default" sectionFormat="of" derivedContent="RF
			C5440"/> describes the Path Computation Element Protocol (PCEP) as a
	communication mechanism between a Path Computation Client (PCC) and a		communication mechanism between a Path Computation Client (PCC) and a
	Path Computation Element (PCE), or between PCE and PCE, that enables		Path Computation Element (PCE), or between a PCE and a PCE, that enables
	computation of Multi-Protocol Label Switching (MPLS) Traffic		computation of MPLS-TE Label Switched Paths (LSPs).</t>
	Engineering Label Switched Paths (TE LSPs).</t>		<t pn="section-1-2">
			<xref target="RFC8231" format="default" sectionFormat="of" derivedContent="RF
	<t>		C8231"/> specifies extensions to PCEP to enable stateful control of
	<xref target="RFC8231"/> specifies extensions to PCEP to enable stateful cont		MPLS-TE LSPs. It describes two modes of operation: passive stateful
	rol of		PCE and active stateful PCE. Further, <xref target="RFC8281" format="default
	MPLS TE LSPs. It describes two mode of operations - Passive stateful		" sectionFormat="of" derivedContent="RFC8281"/> describes the setup,
	PCE and Active stateful PCE. Further, <xref target="RFC8281"/> describes the		maintenance, and teardown of PCE-initiated LSPs for the stateful PCE
	setup,		model. In this document, the focus is on the active stateful PCE, where
	maintenance and teardown of PCE-Initiated LSPs for the stateful PCE
	model. In this document, the focus is on Active stateful PCE where
	the LSPs are controlled by the PCE.</t>		the LSPs are controlled by the PCE.</t>
			<t pn="section-1-3">
	<t>
	Over time, based on the varying traffic pattern, an LSP established with a		Over time, based on the varying traffic pattern, an LSP established with a
	certain bandwidth may require adjustment of the bandwidth reserved in the		certain bandwidth may require adjustment of the bandwidth reserved in the
	network dynamically. The head-end Label Switch Router (LSR) monitors the		network dynamically. The head-end Label Switching Router (LSR) monitors the
	actual bandwidth demand of the established LSP and periodically computes		actual bandwidth demand of the established LSP and periodically computes
	new bandwidth. The head-end LSR adjusts the bandwidth reservation of the		new bandwidth. The head-end LSR automatically adjusts the bandwidth reservat
	LSP based on the computed bandwidth automatically. This feature, when		ion of the
	available in the head-end Label Switching Router (LSR) implementation, is		LSP based on the computed bandwidth. This feature, when
	common referred to as Auto-Bandwidth. The Auto-Bandwidth feature is		available in the head-end LSR implementation, is
	described in detail in Section 4 of this document.</t>		commonly referred to as auto-bandwidth. The auto-bandwidth feature is
			described in detail in <xref target="sect-4" format="default" sectionFormat="
	<t>		of" derivedContent="Section 4"/> of this
			document.</t>
			<t pn="section-1-4">
	In the model considered in this document, the PCC (head-end of the LSP)		In the model considered in this document, the PCC (head-end of the LSP)
	collects the traffic rate samples flowing through the LSP and calculates		collects the traffic rate samples flowing through the LSP and calculates
	the new adjusted bandwidth. The PCC reports the calculated bandwidth to be		the new Adjusted Bandwidth. The PCC reports the calculated bandwidth to be
	adjusted to the PCE. This is similar to the Passive stateful PCE model:		adjusted to the PCE. This is similar to the passive stateful PCE model:
	while the Passive stateful PCE uses a path request/reply mechanism, the		while the passive stateful PCE uses a path request/reply mechanism, the
	Active stateful PCE uses a report/update mechanism. In case of		active stateful PCE uses a report/update mechanism. With a PCE-initiated LSP
	PCE-Initiated LSP, the PCC is requested during the LSP initiation to		, the PCC is requested during the LSP initiation to
	monitor and calculate the new adjusted bandwidth. <xref target="RFC8051"/>		monitor and calculate the new Adjusted Bandwidth. <xref target="RFC8051" for
	describes the use-case for Auto-Bandwidth adjustment for Passive and Active		mat="default" sectionFormat="of" derivedContent="RFC8051"/>
	stateful PCE.</t>		describes the use case for auto-bandwidth adjustment for passive and active
			stateful PCEs.</t>
	<t>		<t pn="section-1-5">
	Another approach would be to send the measured values itself to the		Another approach would be to send the measured values themselves to the
	PCE, which is considered out of scope for this document.</t>		PCE, which is considered out of scope for this document.</t>
			<t pn="section-1-6">
	<t>
	This document defines the PCEP extensions needed to support an		This document defines the PCEP extensions needed to support an
	Auto-Bandwidth feature in an Active stateful PCE model where the LSP		auto-bandwidth feature in an active stateful PCE model where the LSP
	bandwidth to be adjusted is calculated on the PCC (head-end of the		bandwidth to be adjusted is calculated on the PCC (head-end of the
	LSP). The use of PCE to calculate the bandwidth to be adjusted is out of		LSP). The use of PCE to calculate the bandwidth to be adjusted is out of
	scope of this document.</t>		scope of this document.</t>
			</section>
	</section>		<section anchor="sect-2" numbered="true" toc="include" removeInRFC="false" p
			n="section-2">
	<section title="Conventions Used in This Document" anchor="sect-2"><secti		<name slugifiedName="name-conventions-used-in-this-do">Conventions Used in
	on title="Requirements Language" anchor="sect-2.1"><t>		This Document</name>
	The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",		<section anchor="sect-2.1" numbered="true" toc="include" removeInRFC="fals
	"SHOULD", "SHOULD NOT", "RECOMMENDED", "NOT RECOMMENDED", "MAY", and		e" pn="section-2.1">
	"OPTIONAL" in this document are to be interpreted as described in BCP		<name slugifiedName="name-requirements-language">Requirements Language</
	14 <xref target="RFC2119"/> <xref target="RFC8174"/> when, and only when, the		name>
	y appear in all		<t pn="section-2.1-1">
	capitals, as shown here.</t>		The key words "<bcp14>MUST</bcp14>", "<bcp14>MUST NOT</bcp14>", "<bcp14>REQU
			IRED</bcp14>", "<bcp14>SHALL</bcp14>", "<bcp14>SHALL NOT</bcp14>", "<bcp14>SHOUL
	</section>		D</bcp14>", "<bcp14>SHOULD NOT</bcp14>", "<bcp14>RECOMMENDED</bcp14>", "<bcp14>N
			OT RECOMMENDED</bcp14>",
	<section title="Abbreviations" anchor="sect-2.2">		"<bcp14>MAY</bcp14>", and "<bcp14>OPTIONAL</bcp14>" in this document are to
			be interpreted as
	<t><list style="hanging" hangIndent="3">		described in BCP 14 <xref target="RFC2119" format="default" sectionFormat="o
			f" derivedContent="RFC2119"/> <xref target="RFC8174" format="default" sectionFor
	<t hangText="PCC:"> Path Computation Client.</t>		mat="of" derivedContent="RFC8174"/>
			when, and only when, they appear in all capitals, as shown here.
	<t hangText="PCE:"> Path Computation Element.</t>
	<t hangText="PCEP:"> Path Computation Element Communication Protocol.</t>
	<t hangText="TE LSP:"> Traffic Engineering Label Switched Path.</t>
	</list>
	</t>		</t>
			</section>
	</section>		<section anchor="sect-2.2" numbered="true" toc="include" removeInRFC="fals
			e" pn="section-2.2">
	<section title="Terminology" anchor="sect-2.3"><t>		<name slugifiedName="name-abbreviations">Abbreviations</name>
			<dl newline="false" spacing="normal" indent="9" pn="section-2.2-1">
			<dt pn="section-2.2-1.1">PCC:</dt>
			<dd pn="section-2.2-1.2"> Path Computation Client</dd>
			<dt pn="section-2.2-1.3">PCE:</dt>
			<dd pn="section-2.2-1.4"> Path Computation Element</dd>
			<dt pn="section-2.2-1.5">PCEP:</dt>
			<dd pn="section-2.2-1.6"> Path Computation Element Communication Proto
			col</dd>
			<dt pn="section-2.2-1.7">TE:</dt>
			<dd pn="section-2.2-1.8"> Traffic Engineering</dd>
			<dt pn="section-2.2-1.9">LSP:</dt>
			<dd pn="section-2.2-1.10">Label Switched Path</dd>
			</dl>
			</section>
			<section anchor="sect-2.3" numbered="true" toc="include" removeInRFC="fals
			e" pn="section-2.3">
			<name slugifiedName="name-terminology">Terminology</name>
			<t pn="section-2.3-1">
	The reader is assumed to be familiar with the terminology defined in		The reader is assumed to be familiar with the terminology defined in
	<xref target="RFC5440"/>, <xref target="RFC8231"/>, and <xref target="RFC8281		<xref target="RFC5440" format="default" sectionFormat="of" derivedContent="RF
	"/>.</t>		C5440"/>, <xref target="RFC8231" format="default" sectionFormat="of" derivedCont
			ent="RFC8231"/>, and <xref target="RFC8281" format="default" sectionFormat="of"
	<t>		derivedContent="RFC8281"/>.</t>
	In this document, the PCC is considered to be the head end LSR of the		<t pn="section-2.3-2">
	LSP. Other types of PCC are not in scope.</t>		In this document, the PCC is considered to be the head-end LSR of the
			LSP. Other types of PCCs are not in scope.</t>
	<t>		<t pn="section-2.3-3">
	The following auto-bandwidth terminology is defined in this document.</t>		The following auto-bandwidth terminology is defined in this document.</t>
			<dl newline="false" spacing="normal" indent="3" pn="section-2.3-4">
	<t><list style="hanging" hangIndent="3">		<dt pn="section-2.3-4.1">Maximum Average Bandwidth (MaxAvgBw):</dt>
			<dd pn="section-2.3-4.2">The maximum
	<t hangText="Maximum Average Bandwidth (MaxAvgBw):">The maximum		average bandwidth represents the current 'measured' traffic bandwidth
	average bandwidthrepresents the current 'measured' traffic bandwidth
	demand of the LSP during a time interval. This is the maximum value		demand of the LSP during a time interval. This is the maximum value
	of the traffic bandwidth rate samples (Bandwidth-Samples) in a given		of the traffic bandwidth rate samples (Bandwidth-Samples) in a given
	time interval.		time interval.
	</t>		</dd>
			<dt pn="section-2.3-4.3">Adjusted Bandwidth:</dt>
	<t hangText="Adjusted Bandwidth:">This is the Auto-Bandwidth		<dd pn="section-2.3-4.4">This is the auto-bandwidth
	'computed' bandwidth that is used to adjust the bandwidth reservation		'computed' bandwidth that is used to adjust the bandwidth reservation
	of the LSP.		of the LSP.
	</t>		</dd>
			<dt pn="section-2.3-4.5">Sample-Interval:</dt>
	<t hangText="Sample-Interval:">The periodic time interval at which the		<dd pn="section-2.3-4.6">The periodic time interval at which the
	measured traffic rate of the LSP is collected as a Bandwidth-Sample.		measured traffic rate of the LSP is collected as a Bandwidth-Sample.
	</t>		</dd>
			<dt pn="section-2.3-4.7">Bandwidth-Sample:</dt>
	<t hangText="Bandwidth-Sample:">The bandwidth sample of the measured		<dd pn="section-2.3-4.8">The Bandwidth-Sample of the measured
	traffic rate of the LSP collected at every Sample-Interval.		traffic rate of the LSP collected at every Sample-Interval.
	</t>		</dd>
			<dt pn="section-2.3-4.9">Maximum-Bandwidth:</dt>
	<t hangText="Maximum-Bandwidth:">The maximum bandwidth that can be		<dd pn="section-2.3-4.10">The Maximum-Bandwidth that can be
	reserved for the LSP.		reserved for the LSP.
	</t>		</dd>
			<dt pn="section-2.3-4.11">Minimum-Bandwidth:</dt>
	<t hangText="Minimum-Bandwidth:">The minimum bandwidth that can be		<dd pn="section-2.3-4.12">The Minimum-Bandwidth that can be
	reserved for the LSP.		reserved for the LSP.
	</t>		</dd>
			<dt pn="section-2.3-4.13">Up-Adjustment-Interval:</dt>
	<t hangText="Up-Adjustment-Interval:">The periodic time interval at		<dd pn="section-2.3-4.14">The periodic time interval at
	which the bandwidth adjustment should be made using the MaxAvgBw, when		which the bandwidth adjustment should be made using the MaxAvgBw when
	MaxAvgBw is greater than the current bandwidth reservation of the LSP.		MaxAvgBw is greater than the current bandwidth reservation of the LSP.
	</t>		</dd>
			<dt pn="section-2.3-4.15">Down-Adjustment-Interval:</dt>
	<t hangText="Down-Adjustment-Interval:">The periodic time interval at		<dd pn="section-2.3-4.16">The periodic time interval at
	which the bandwidth adjustment should be made using the MaxAvgBw, when		which the bandwidth adjustment should be made using the MaxAvgBw when
	MaxAvgBw is less than the current bandwidth reservation of the LSP.		MaxAvgBw is less than the current bandwidth reservation of the LSP.
	</t>		</dd>
			<dt pn="section-2.3-4.17">Up-Adjustment-Threshold:</dt>
	<t hangText="Up-Adjustment-Threshold:">This parameter is used to		<dd pn="section-2.3-4.18">This parameter is used to
	decide when the LSP bandwidth should be adjusted. If the percentage		decide when the LSP bandwidth should be adjusted. If the percentage
	or absolute difference between the current MaxAvgBw and the current		or absolute difference between the current MaxAvgBw and the current
	bandwidth reservation is greater than or equal to the threshold value,		bandwidth reservation is greater than or equal to the threshold value,
	the LSP bandwidth is adjusted (upsized) to the current bandwidth		the 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.
	</t>		</dd>
			<dt pn="section-2.3-4.19">Down-Adjustment-Threshold:</dt>
	<t hangText="Down-Adjustment-Threshold:">This parameter is used to		<dd pn="section-2.3-4.20">This parameter is used to
	decide when the LSP bandwidth should be adjusted. If the percentage		decide when the LSP bandwidth should be adjusted. If the percentage
	or absolute difference between the current bandwidth reservation and		or absolute difference between the current bandwidth reservation and
	the current MaxAvgBw is greater than or equal to the threshold value,		the current MaxAvgBw is greater than or equal to the threshold value,
	the LSP bandwidth is adjusted (downsized) to the current bandwidth		the LSP bandwidth is adjusted (downsized) to the current bandwidth
	demand (Adjusted Bandwidth) at the Down-Adjustment-Interval expiry.		demand (Adjusted Bandwidth) at the Down-Adjustment-Interval expiry.
	</t>		</dd>
			<dt pn="section-2.3-4.21">Overflow-Count:</dt>
	<t hangText="Overflow-Count:">This parameter is used to decide when		<dd pn="section-2.3-4.22">This parameter is used to decide when
	the LSP bandwidth should be adjusted when there is a sudden increase		the LSP bandwidth should be adjusted when there is a sudden increase
	in traffic demand. This value indicates how many times,		in traffic demand. This value indicates how many times,
	consecutively, the percentage or absolute difference between the		consecutively, that the percentage or absolute difference between the
	current MaxAvgBw and the current bandwidth reservation of the LSP		current MaxAvgBw and the current bandwidth reservation of the LSP
	needs to be greater than or equal to the Overflow-Threshold value in		needs to be greater than or equal to the Overflow-Threshold value in
	order to meet the overflow condition.		order to meet the overflow condition.
	</t>		</dd>
			<dt pn="section-2.3-4.23">Overflow-Threshold:</dt>
	<t hangText="Overflow-Threshold:">This parameter is used to decide		<dd pn="section-2.3-4.24">This parameter is used to decide
	when the LSP bandwidth should be adjusted when there is a sudden		when the LSP bandwidth should be adjusted when there is a sudden
	increase in traffic demand. If the percentage or absolute difference		increase in traffic demand. If the percentage or absolute difference
	between the current MaxAvgBw and the current bandwidth reservation of		between the current MaxAvgBw and the current bandwidth reservation of
	the LSP is greater than or equal to the threshold value, the overflow		the LSP is greater than or equal to the threshold value, the overflow
	condition is said to be met. The LSP bandwidth is adjusted to the		condition is said to be met. The LSP bandwidth is adjusted to the
	current bandwidth demand bypassing the Up-Adjustment-Interval if the		current bandwidth demand, bypassing the Up-Adjustment-Interval if the
	overflow condition is met consecutively for the Overflow-Count. The		overflow condition is met consecutively for the Overflow-Count. The
	Overflow-Threshold needs to be greater than or equal to the		Overflow-Threshold needs to be greater than or equal to the
	Up-Adjustment-Threshold.		Up-Adjustment-Threshold.
	</t>		</dd>
			<dt pn="section-2.3-4.25">Underflow-Count:</dt>
	<t hangText="Underflow-Count:">This parameter is used to decide when		<dd pn="section-2.3-4.26">This parameter is used to decide when
	the LSP bandwidth should be adjusted when there is a sudden decrease		the LSP bandwidth should be adjusted when there is a sudden decrease
	in traffic demand. This value indicates how many times consecutively,		in traffic demand. This value indicates how many times, consecutively,
	the percentage or absolute difference between the current MaxAvgBw and		that the percentage or absolute difference between the current MaxAvgBw a
			nd
	the current bandwidth reservation of the LSP needs to be greater than		the current bandwidth reservation of the LSP needs to be greater than
	or equal to the Underflow-Threshold value in order to meet the		or equal to the Underflow-Threshold value in order to meet the
	underflow condition.		underflow condition.
	</t>		</dd>
			<dt pn="section-2.3-4.27">Underflow-Threshold:</dt>
	<t hangText="Underflow-Threshold:">This parameter is used to decide		<dd pn="section-2.3-4.28">This parameter is used to decide
	when the LSP bandwidth should be adjusted when there is a sudden		when the LSP bandwidth should be adjusted when there is a sudden
	decrease in traffic demand. If the percentage or absolute difference		decrease in traffic demand. If the percentage or absolute difference
	between the current MaxAvgBw and the current bandwidth reservation of		between the current MaxAvgBw and the current bandwidth reservation of
	the LSP is greater than or equal to the threshold value, the underflow		the LSP is greater than or equal to the threshold value, the underflow
	condition is said to be met. The LSP bandwidth is adjusted to the		condition is said to be met. The LSP bandwidth is adjusted to the
	current bandwidth demand bypassing the Down-Adjustment-Interval if the		current bandwidth demand, bypassing the Down-Adjustment-Interval if the
	underflow condition is met consecutively for the Underflow-Count. The		underflow condition is met consecutively for the Underflow-Count. The
	Underflow-Threshold needs to be greater than or equal to the		Underflow-Threshold needs to be greater than or equal to the
	Down-Adjustment-Threshold.		Down-Adjustment-Threshold.
	</t>		</dd>
			<dt pn="section-2.3-4.29">Minimum-Threshold:</dt>
	<t hangText="Minimum-Threshold:">When percentage-based thresholds are		<dd pn="section-2.3-4.30">When percentage-based thresholds are
	in use, they are accompanied by this minimum threshold, which is used		in use, they are accompanied by this Minimum-Threshold, which is used
	to enforce that the magnitude of deviation of calculated LSP bandwidth		to ensure that the magnitude of deviation of the calculated LSP bandwidth
	to be adjusted from the current bandwidth reservations exceeds a		to be adjusted from the current bandwidth reservations exceeds a
	specific non-percentage-based criterion (represented as an absolute		specific non-percentage-based criterion (represented as an absolute
	bandwidth value) before any adjustments are made. This serves to		bandwidth value) before any adjustments are made. This serves to
	suppress unnecessary auto-bandwidth adjustments and re-signaling of		suppress unnecessary auto-bandwidth adjustments and resignaling of
	the LSP at low bandwidth values.		the LSP at low bandwidth values.
	</t>		</dd>
			</dl>
	</list>		</section>
	</t>		</section>
			<section anchor="sect-3" numbered="true" toc="include" removeInRFC="false" p
	</section>		n="section-3">
			<name slugifiedName="name-requirements-for-pcep-exten">Requirements for PC
	</section>		EP Extensions</name>
			<t pn="section-3-1">
	<section title="Requirements for PCEP Extensions" anchor="sect-3"><t>
	The PCEP extensions required for auto-bandwidth are summarized in the		The PCEP extensions required for auto-bandwidth are summarized in the
	following table as well as in Figure 1.</t>		following table as well as in <xref target="ure-overview-of-auto-bandwidth-pc
			ep-extensions" format="default" sectionFormat="of" derivedContent="Figure 1"/>.<
	<texttable title="Requirements for Auto-Bandwidth PCEP extensions" anchor		/t>
	="tab-requirements-for-auto-bandwidth-pcep-extensions" style="full"><ttcol> PCC		<table anchor="tab-requirements-for-auto-bandwidth-pcep-extensions" align=
	Initiated</ttcol>		"center" pn="table-1">
	<ttcol> PCE Initiated</ttcol>		<name slugifiedName="name-requirements-for-auto-bandw">Requirements for
	<c>PCC monitors the traffic</c>		Auto-Bandwidth PCEP Extensions</name>
	<c>At the time of initiation,</c>		<thead>
	<c>and reports the calculated</c>		<tr>
	<c>PCE request PCC to monitor</c>		<th align="left" colspan="1" rowspan="1">PCC Initiated</th>
	<c>bandwidth to be adjusted</c>		<th align="left" colspan="1" rowspan="1">PCE Initiated</th>
	<c>the traffic and report the</c>		</tr>
	<c>to the PCE.</c>		</thead>
	<c>calculated bandwidth to be</c>		<tbody>
	<c></c>		<tr>
	<c>adjusted to the PCE.</c>		<td align="left" colspan="1" rowspan="1">PCC monitors the traffic an
	<c>Extension is needed for PCC</c>		d reports the
	<c>Extension is needed for PCE</c>		calculated bandwidth to be adjusted to the PCE.</td>
	<c>to pass on the adjustment</c>		<td align="left" colspan="1" rowspan="1">At the time of initiation,
	<c>to pass on the adjustment</c>		the PCE requests that the PCC monitor the traffic and report the calculated band
	<c>parameters at the time of</c>		width to be
	<c>parameters at the time of</c>		adjusted to the PCE.</td>
	<c>LSP Delegation.</c>		</tr>
	<c>LSP Initiation.</c>		<tr>
	</texttable>		<td align="left" colspan="1" rowspan="1">
	<figure title="Overview of Auto-Bandwidth PCEP extensions" anchor="ure-ov		Extension is needed for the PCC to pass on the adjustment
	erview-of-auto-bandwidth-pcep-extensions"><artwork><![CDATA[		parameters at the time of LSP delegation.</td>
			<td align="left" colspan="1" rowspan="1">
			Extension is needed for the PCE to pass on the adjustment
			parameters at the time of LSP initiation.</td>
			</tr>
			</tbody>
			</table>
			<figure anchor="ure-overview-of-auto-bandwidth-pcep-extensions" align="lef
			t" suppress-title="false" pn="figure-1">
			<name slugifiedName="name-overview-of-auto-bandwidth-">Overview of Auto-
			Bandwidth PCEP Extensions</name>
			<artwork name="" type="" align="left" alt="" pn="section-3-3.1">
	----------		----------
	| |		| |
	| PCE |		| PCE |
	| |		| |
	----------		----------
	| ^		| ^
	AUTO-BANDWIDTH CAPABILITY | | AUTO-BANDWIDTH CAPABILITY		AUTO-BANDWIDTH CAPABILITY | | AUTO-BANDWIDTH CAPABILITY
	| |		| |
	AUTO-BANDWIDTH ATTRIBUTES | | AUTO-BANDWIDTH ATTRIBUTES		AUTO-BANDWIDTH ATTRIBUTES | | AUTO-BANDWIDTH ATTRIBUTES
	| | (For Delegated LSPs)		| | (For Delegated LSPs)
	| |		| |
	| | REQUESTED BANDWIDTH		| | REQUESTED BANDWIDTH
	v |		v |
	----------		----------
	| |		| |
	| PCC |		| PCC |
	| |		| |
	----------		----------</artwork>
	]]></artwork>		</figure>
	</figure>		<t pn="section-3-4">
	<t>
	A PCEP speaker supporting this document must have a mechanism to advertise		A PCEP speaker supporting this document must have a mechanism to advertise
	the automatic bandwidth adjustment capability for both PCC-Initiated and		the auto-bandwidth adjustment capability for both PCC-initiated and
	PCE-Initiated LSPs.</t>		PCE-initiated LSPs.</t>
			<t pn="section-3-5">
	<t>
	Auto-bandwidth deployment considerations for PCEP extensions are		Auto-bandwidth deployment considerations for PCEP extensions are
	summarized below:</t>		summarized below:</t>
			<ul spacing="normal" bare="false" empty="false" pn="section-3-6">
	<t><list style="symbols"><t>It is necessary to identify and inform the		<li pn="section-3-6.1">It is necessary to identify and inform the
	PCC which LSPs have enabled the Auto-Bandwidth feature. Not all LSPs		PCC which LSPs have enabled the auto-bandwidth feature. Not all LSPs
	in some deployments would like their bandwidth to be dependent on the		in some deployments would like their bandwidth to be dependent on real-ti
	real-time bandwidth usage; for some LSPs leaving the bandwidth		me bandwidth usage; for some LSPs, leaving the bandwidth
	constant as set by the operator is preferred.</t>		constant as set by the operator is preferred.</li>
			<li pn="section-3-6.2">In addition, an operator should be able to specif
	<t>In addition, an operator should be able to specify the		y the
	auto-bandwidth adjustment parameters (i.e. configuration knobs) to		auto-bandwidth adjustment parameters (i.e., configuration knobs) to
	control this feature (e.g. minimum/ maximum bandwidth range). The PCC		control this feature (e.g., Minimum/Maximum-Bandwidth range). The PCC
	should be informed about these adjustment parameters.</t>		should be informed about these adjustment parameters.</li>
			</ul>
	</list>		</section>
	</t>		<section anchor="sect-4" numbered="true" toc="include" removeInRFC="false" p
			n="section-4">
	</section>		<name slugifiedName="name-architectural-overview">Architectural Overview</
			name>
	<section title="Architectural Overview" anchor="sect-4"><section title="A		<section anchor="sect-4.1" numbered="true" toc="include" removeInRFC="fals
	uto-Bandwidth Overview" anchor="sect-4.1"><t>		e" pn="section-4.1">
	The Auto-Bandwidth feature allows automatic and dynamic adjustment of		<name slugifiedName="name-auto-bandwidth-overview">Auto-Bandwidth Overvi
			ew</name>
			<t pn="section-4.1-1">
			The auto-bandwidth feature allows automatic and dynamic adjustment of
	the reserved bandwidth of an LSP over time (i.e., without network		the reserved bandwidth of an LSP over time (i.e., without network
	operator intervention) to accommodate the varying traffic demand of		operator intervention) to accommodate the varying traffic demand of
	the LSP. If the traffic flowing through the LSP is lower than the		the LSP. If the traffic flowing through the LSP is lower than the
	configured or current reserved bandwidth of the LSP, the extra		configured or current reserved bandwidth of the LSP, the extra
	bandwidth is being reserved needlessly and being wasted. Conversely,		bandwidth is being reserved needlessly and is being wasted. Conversely,
	if the actual traffic flowing through the LSP is higher than the		if the actual traffic flowing through the LSP is higher than the
	configured or current reserved bandwidth of the LSP, it can		configured or current reserved bandwidth of the LSP, it can
	potentially cause congestion or packet loss in the network. The		potentially cause congestion or packet loss in the network. The
	initial LSP bandwidth can be set to an arbitrary value (including		initial LSP bandwidth can be set to an arbitrary value (including
	zero). In practice, it can be set to an expected value based on		zero). In practice, it can be set to an expected value based on
	design and planning. The head-end Label Switch Router (LSR) monitors		design and planning. The head-end LSR monitors
	the actual traffic flowing through the LSP and uses that information		the actual traffic flowing through the LSP and uses that information
	to adjust the bandwidth reservation of the LSP in the network.</t>		to adjust the bandwidth reservation of the LSP in the network.</t>
			<t pn="section-4.1-2">
	<t>
	Bandwidth adjustment must not cause disruption to the traffic flow		Bandwidth adjustment must not cause disruption to the traffic flow
	carried by the LSP. One way to achieve this is to use the		carried by the LSP. One way to achieve this is to use the
	make-before-break signaling method <xref target="RFC3209"/>.</t>		make-before-break signaling method <xref target="RFC3209" format="default" se
			ctionFormat="of" derivedContent="RFC3209"/>.</t>
	</section>		</section>
			<section anchor="sect-4.2" numbered="true" toc="include" removeInRFC="fals
	<section title="Auto-bandwidth Theory of Operation" anchor="sect-4.2"><t>		e" pn="section-4.2">
	This section describes the Auto-Bandwidth feature in a general way.		<name slugifiedName="name-auto-bandwidth-theory-of-op">Auto-Bandwidth Th
	When the Auto-Bandwidth feature is enabled, the measured traffic rate		eory of Operation</name>
	is periodically sampled at each Sample-Interval by the PCC, when the		<t pn="section-4.2-1">
	PCC is the head-end node of the LSP. The sample interval can be		This section describes the auto-bandwidth feature in a general way.
			When the auto-bandwidth feature is enabled, the measured traffic rate
			is periodically sampled at each Sample-Interval by the PCC when the
			PCC is the head-end node of the LSP. The Sample-Interval can be
	configured by an operator, with a default value of 5 minutes. A very		configured by an operator, with a default value of 5 minutes. A very
	low Sample-Interval could have some undesirable interactions with		low Sample-Interval could have some undesirable interactions with
	transport protocols (see <xref target="sect-6.6"/>).</t>		transport protocols (see <xref target="sect-6.6" format="default" sectionForm
			at="of" derivedContent="Section 6.6"/>).</t>
	<t>		<t pn="section-4.2-2">
	The traffic rate samples are accumulated over the Adjustment-Interval		The traffic rate samples are accumulated over the Adjustment-Interval
	period (in the Up or Down direction). The period can be configured		period (in the Up or Down direction). The period can be configured
	by an operator, with a default value of 24 hours. The PCC in-charge		by an operator, with a default value of 24 hours. The PCC in charge
	of calculating the bandwidth to be adjusted can decide to adjust the		of calculating the bandwidth to be adjusted can decide to adjust the
	bandwidth of the LSP to the highest traffic rate sample (MaxAvgBw)		bandwidth of the LSP to the highest traffic rate sample (MaxAvgBw)
	amongst the set of bandwidth samples collected over the		amongst the set of Bandwidth-Samples collected over the
	Adjustment-Interval period (in the Up or Down direction) depending on		Adjustment-Interval period (in the Up or Down direction) depending on
	the operator policy.</t>		the operator policy.</t>
			<t pn="section-4.2-3">
	<t>
	Note that the highest traffic rate sample could be higher or lower		Note that the highest traffic rate sample could be higher or lower
	than the current LSP bandwidth. Only if the difference between the		than the current LSP bandwidth. The LSP is adjusted (upsized) to the
			current bandwidth demand (MaxAvgBW) 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 the		reservation is greater than or equal to the Adjustment-Threshold. The Adjustm
	LSP bandwidth is adjusted (upsized) to the current bandwidth demand		ent-Threshold could be an absolute value or a
	(MaxAvgBw). The Adjustment-Threshold could be an absolute value or a
	percentage. The threshold can be configured by an operator, with a		percentage. The threshold can be configured by an operator, with a
	default value of 5 percentage. Similarly, if the difference between		default value of 5 percent. Similarly, if the difference between
	the current bandwidth reservation and the current bandwidth demand		the current bandwidth reservation and the current bandwidth demand
	(MaxAvgBw) is greater than or equal to the Down-Adjustment-Threshold		(MaxAvgBw) is greater than or equal to the Down-Adjustment-Threshold
	(percentage or absolute value), the LSP bandwidth is adjusted		(percentage or absolute value), the LSP bandwidth is adjusted
	(downsized) to the current bandwidth demand (MaxAvgBw). Some LSPs		(downsized) to the current bandwidth demand (MaxAvgBw). Some LSPs
	are less eventful while other LSPs may encounter a lot of changes in		are less eventful, while other LSPs may encounter a lot of changes in
	the traffic pattern. The thresholds and intervals for bandwidth		the traffic pattern. The thresholds and intervals for bandwidth
	adjustment are configured based on the traffic pattern of the LSP.</t>		adjustment are configured based on the traffic pattern of the LSP.</t>
			<t pn="section-4.2-4">
	<t>		In order to avoid frequent resignaling, 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, a longer
	adjustment-interval value (Up and/or Down). However, a longer		Adjustment-Interval can result in the undesirable effect of masking
	Adjustment-Interval can result in an undesirable effect of masking		sudden changes in the 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 force the Adjustment-Interval to prematurely
	Auto-Bandwidth feature may prematurely expire the adjustment interval		expire and adjust the LSP bandwidth to accommodate the sudden bursts of
	and adjust the LSP bandwidth to accommodate the sudden bursts of
	increase in traffic demand as an overflow condition or decrease in		increase in traffic demand as an overflow condition or decrease in
	traffic demand as an underflow condition. An operator needs to		traffic demand as an underflow condition. An operator needs to
	configure appropriate values for the Overflow-Threshold and/or		configure appropriate values for the Overflow-Threshold and/or
	Underflow-Threshold parameters and they do not have default values		Underflow-Threshold parameters, and they do not have default values
	defined in this document.</t>		defined in this document.</t>
			<t pn="section-4.2-5">
	<t>
	All thresholds in this document could be represented in both absolute		All thresholds in this document could be represented in both absolute
	value and percentage, and could be used together. This is provided		value and percentage and could be used together. This is provided
	to accommodate the cases where the LSP bandwidth reservation may		to accommodate cases where the LSP bandwidth reservation may
	become very large or very small over time. For example, an operator		become very large or very small over time. For example, an operator
	may use the percentage threshold to handle small to large bandwidth		may use the percentage threshold to handle small to large bandwidth
	values and absolute values to handle very large bandwidth values.		values and absolute values to handle very large bandwidth values.
	The auto-bandwidth adjustment is made when either one of the two		The auto-bandwidth adjustment is made when either one of the two
	thresholds, the absolute or percentage, is crossed.</t>		thresholds, the absolute or percentage, is crossed.</t>
			<t pn="section-4.2-6">
	<t>
	When using the (adjustment/overflow/underflow) percentage thresholds,		When using the (adjustment/overflow/underflow) percentage thresholds,
	if the LSP bandwidth changes rapidly at very low values, it may		if the LSP bandwidth changes rapidly at very low values, it may
	trigger frequent auto-bandwidth adjustments due to the crossing of		trigger frequent auto-bandwidth adjustments due to the crossing of
	the percentage thresholds. This can lead to unnecessary re-signaling		the percentage thresholds. This can lead to unnecessary resignaling
	of the LSPs in the network. This is suppressed by setting the		of the LSPs in the network. This is suppressed by setting the
	minimum-threshold parameters along with the percentage thresholds.		Minimum-Threshold parameters along with the percentage thresholds.
	The auto-bandwidth adjustment is only made if the LSP bandwidth		The auto-bandwidth adjustment is only made if the LSP bandwidth
	crosses both the percentage threshold and the minimum-threshold		crosses both the percentage threshold and the Minimum-Threshold
	parameters.</t>		parameters.</t>
			</section>
	</section>		<section anchor="sect-4.3" numbered="true" toc="include" removeInRFC="fals
			e" pn="section-4.3">
	<section title="Scaling Considerations" anchor="sect-4.3"><t>		<name slugifiedName="name-scaling-considerations">Scaling Considerations
	It should be noted that any bandwidth change requires re-signaling of		</name>
	an LSP, which can further trigger preemption of lower priority LSPs		<t pn="section-4.3-1">
			It should be noted that any bandwidth change requires resignaling of
			an LSP, which can further trigger preemption of lower-priority LSPs
	in the network. When deployed under scale, this can lead to a		in the network. When deployed under scale, this can lead to a
	signaling churn in the network. The Auto-bandwidth application		signaling churn in the network. The auto-bandwidth application
	algorithm is thus advised to take this into consideration before		algorithm is thus advised to take this into consideration before
	adjusting the LSP bandwidth. Operators are advised to set the values		adjusting the LSP bandwidth. Operators are advised to set the values
	of various auto-bandwidth adjustment parameters appropriate for the		of various auto-bandwidth adjustment parameters appropriate for the
	deployed LSP scale.</t>		deployed LSP scale.</t>
			<t pn="section-4.3-2">
	<t>
	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. Similarly,
	Section 5.7 of this document). Similarly, if a PCC gets overwhelmed		if a PCC gets overwhelmed due to signaling churn, it can notify the PCE to te
	due to signaling churn, it can notify the PCE to temporarily suspend		mporarily suspend
	new LSP setup requests (see Section 5.7 of this document).</t>		new LSP setup requests. See <xref target="sect-5.7" format="default" sectionF
			ormat="of" derivedContent="Section 5.7"/> of this document.</t>
	</section>		</section>
			</section>
	</section>		<section anchor="sect-5" numbered="true" toc="include" removeInRFC="false" p
			n="section-5">
	<section title="PCEP Extensions" anchor="sect-5"><section title="Capabili		<name slugifiedName="name-pcep-extensions">PCEP Extensions</name>
	ty Advertisement" anchor="sect-5.1"><t>		<section anchor="sect-5.1" numbered="true" toc="include" removeInRFC="fals
	During PCEP Initialization Phase, PCEP speakers (PCE or PCC)		e" pn="section-5.1">
	advertise their support of Automatic Bandwidth adjustment feature. A		<name slugifiedName="name-capability-advertisement">Capability Advertise
	PCEP speaker includes the AUTO-BANDWIDTH-CAPABILITY TLV, in the OPEN		ment</name>
	Object to advertise its support for PCEP Auto-Bandwidth extensions.		<t pn="section-5.1-1">
	The presence of the AUTO-BANDWIDTH-CAPABILITY TLV in the OPEN Object		During the PCEP initialization phase, PCEP speakers (PCE or PCC)
	indicates that the Automatic Bandwidth feature is supported as		advertise their support of the auto-bandwidth adjustment feature. A
			PCEP speaker includes the AUTO-BANDWIDTH-CAPABILITY TLV in the OPEN
			object to advertise its support for PCEP auto-bandwidth extensions.
			The presence of the AUTO-BANDWIDTH-CAPABILITY TLV in the OPEN object
			indicates that the auto-bandwidth feature is supported as
	described in this document.</t>		described in this document.</t>
			<ul spacing="normal" bare="false" empty="false" pn="section-5.1-2">
	<t><list style="symbols"><t>The PCEP protocol extensions for Auto-Bandwid		<li pn="section-5.1-2.1">The PCEP protocol extensions for auto-bandwid
	th adjustments MUST		th adjustments <bcp14>MUST NOT</bcp14> be used if one or both PCEP speakers have
	NOT be used if one or both PCEP speakers have not included the		not included the
	AUTO-BANDWIDTH-CAPABILITY TLV in their respective OPEN message.</t>		AUTO-BANDWIDTH-CAPABILITY TLV in their respective OPEN message.</li>
			<li pn="section-5.1-2.2">A PCEP speaker that does not recognize the ex
	<t>A PCEP speaker that does not recognize the extensions defined in		tensions defined in
	this document would simply ignore the TLVs as per <xref target="RFC5440"/>		this document would simply ignore the TLVs as per <xref target="RFC5440" f
	.</t>		ormat="default" sectionFormat="of" derivedContent="RFC5440"/>.</li>
			<li pn="section-5.1-2.3">If a PCEP speaker supports the extensions def
	<t>If a PCEP speaker that supports the extensions defined in this		ined in this
	document but did not advertise this capability, then upon receipt		document but did not advertise this capability, then upon receipt
	of AUTO-BANDWIDTH-ATTRIBUTES TLV in the LSP Attributes (LSPA)		of AUTO-BANDWIDTH-ATTRIBUTES TLV in the LSP Attributes (LSPA)
	object, it SHOULD generate a PCErr with error-type 19 (Invalid		object, it <bcp14>SHOULD</bcp14> generate a PCErr with Error-Type 19 (Inva
	Operation), error-value TBD4 (Auto-Bandwidth capability was not		lid
	advertised) and ignore the AUTO-BANDWIDTH-ATTRIBUTES TLV.</t>		Operation) and Error-value 14 (Auto-Bandwidth capability was not
			advertised) and ignore the AUTO-BANDWIDTH-ATTRIBUTES TLV.</li>
	</list>		</ul>
	</t>		<section anchor="sect-5.1.1" numbered="true" toc="include" removeInRFC="
			false" pn="section-5.1.1">
	<section title="AUTO-BANDWIDTH-CAPABILITY TLV" anchor="sect-5.1.1"><t>		<name slugifiedName="name-auto-bandwidth-capability-t">AUTO-BANDWIDTH-
			CAPABILITY TLV</name>
			<t pn="section-5.1.1-1">
	The AUTO-BANDWIDTH-CAPABILITY TLV is an optional TLV for use in the		The AUTO-BANDWIDTH-CAPABILITY TLV is an optional TLV for use in the
	OPEN Object for Automatic Bandwidth Adjustment via PCEP capability		OPEN Object for auto-bandwidth adjustment via PCEP capability
	advertisement. Its format is shown in the following figure:</t>		advertisement. Its format is shown in the following figure:</t>
			<figure anchor="auto-bandwidth-capability-tlv" align="left" suppress-t
	<figure><artwork><![CDATA[		itle="false" pn="figure-2">
			<name slugifiedName="name-auto-bandwidth-capability-tl">AUTO-BANDWID
			TH-CAPABILITY TLV Format</name>
			<artwork name="" type="" align="left" alt="" pn="section-5.1.1-2.1">
	0 1 2 3		0 1 2 3
	0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1		0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
	+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+		+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
	| Type=TBD2 | Length=4 |		| Type=36 | Length=4 |
	+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
	| Flags |
	+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+		+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
			| Flag |
	AUTO-BANDWIDTH-CAPABILITY TLV format		+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+</artwork>
	]]></artwork>		</figure>
	</figure>		<t pn="section-5.1.1-3">
			The TLV Type is 36, and it has a fixed Length of 4 octets.</t>
	<t>		<t pn="section-5.1.1-4">
	The Type of the TLV is (TBD2) and it has a fixed Length of 4 octets.</t>		The value comprises a single field: Flag (32 bits). No flags are
	<t>
	The value comprises a single field - Flags (32 bits). No flags are
	defined for this TLV in this document.</t>		defined for this TLV in this document.</t>
			<t pn="section-5.1.1-5">
	<t>		Unassigned bits are considered reserved. They <bcp14>MUST</bcp14> be set to
	Unassigned bits are considered reserved. They MUST be set to 0 on		0 on
	transmission and MUST be ignored on receipt.</t>		transmission and <bcp14>MUST</bcp14> be ignored on receipt.</t>
			<t pn="section-5.1.1-6">
	<t>
	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.</t>		procedures defined in this document.</t>
			</section>
	</section>		</section>
			<section anchor="sect-5.2" numbered="true" toc="include" removeInRFC="fals
	</section>		e" pn="section-5.2">
			<name slugifiedName="name-auto-bandwidth-attributes-t">AUTO-BANDWIDTH-AT
	<section title="AUTO-BANDWIDTH-ATTRIBUTES TLV" anchor="sect-5.2"><t>		TRIBUTES TLV</name>
			<t pn="section-5.2-1">
	The AUTO-BANDWIDTH-ATTRIBUTES TLV provides the 'configurable knobs'		The AUTO-BANDWIDTH-ATTRIBUTES TLV provides the 'configurable knobs'
	of the feature and it can be included as an optional TLV in the LSPA		of the feature, and it can be included as an optional TLV in the LSPA
	Object (as described in <xref target="RFC5440"/>).</t>		object (as described in <xref target="RFC5440" format="default" sectionFormat
			="of" derivedContent="RFC5440"/>).</t>
	<t>		<t pn="section-5.2-2">
	For PCE-Initiated LSP <xref target="RFC8281"/>, this TLV is included in the L		For a PCE-initiated LSP <xref target="RFC8281" format="default" sectionFormat
	SPA		="of" derivedContent="RFC8281"/>, this TLV is included in the LSPA
	Object with the PCInitiate message. For the PCC-Initiated delegated		object with the PCInitiate message. For the PCC-initiated delegated
	LSPs, this TLV is carried in the PCRpt message in LSPA Object. This		LSPs, this TLV is carried in the Path Computation State Report (PCRpt) messag
	TLV is also carried in the LSPA object with the PCUpd message to		e in the LSPA object. This
			TLV is also carried in the LSPA object with the Path Computation Update
			Request (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.</t>		attributes such as Adjustment-Interval.</t>
			<t pn="section-5.2-3">
	<t>
	The TLV is encoded in all PCEP messages for the LSP while the		The TLV is encoded in all PCEP messages for the LSP while the
	auto-bandwidth adjustment feature is enabled, the absence of the TLV		auto-bandwidth adjustment feature is enabled. The absence of the TLV
	indicates the PCEP speaker wishes to disable the feature. This TLV		indicates the PCEP speaker wishes to disable the feature. This TLV
	includes multiple AUTO-BANDWIDTH-ATTRIBUTES sub-TLVs. The		includes multiple AUTO-BANDWIDTH-ATTRIBUTES sub-TLVs. The
	AUTO-BANDWIDTH-ATTRIBUTES sub-TLVs are included if there is a change since		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		the last information sent in the PCEP message. The default values for
	missing sub-TLVs apply for the first PCEP message for the LSP.</t>		missing sub-TLVs apply for the first PCEP message for the LSP.</t>
			<t pn="section-5.2-4">
	<t>
	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:</t>		following figure:</t>
			<figure anchor="AUTO-BANDWIDTH-ATTRIBUTES-TLV" align="left" suppress-tit
	<figure><artwork><![CDATA[		le="false" pn="figure-3">
			<name slugifiedName="name-auto-bandwidth-attributes-tl">AUTO-BANDWIDTH
			-ATTRIBUTES TLV Format</name>
			<artwork name="" type="" align="left" alt="" pn="section-5.2-5.1">
	0 1 2 3		0 1 2 3
	0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1		0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
	+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+		+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
	| Type=TBD1 | Length |		| Type=37 | Length |
	+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+		+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
	| |		| |
	// sub-TLVs //		// sub-TLVs //
	| |		| |
	+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+		+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+</artwork>
			</figure>
	AUTO-BANDWIDTH-ATTRIBUTES TLV format		<dl newline="false" spacing="normal" indent="3" pn="section-5.2-6">
	]]></artwork>		<dt pn="section-5.2-6.1">Type:</dt>
	</figure>		<dd pn="section-5.2-6.2">37</dd>
			<dt pn="section-5.2-6.3">Length:</dt>
	<t><list style="hanging" hangIndent="3">		<dd pn="section-5.2-6.4">The Length field defines the length of the va
			lue
	<t hangText="Type:">TBD1</t>		portion in bytes as per <xref target="RFC5440" format="default" sectionFormat
			="of" derivedContent="RFC5440"/>.</dd>
	<t hangText="Length:"> The Length field defines the length of the value		<dt pn="section-5.2-6.5">Value:</dt>
	portion in octets as per <xref target="RFC5440"/>.</t>		<dd pn="section-5.2-6.6">This comprises one or more sub-TLVs.</dd>
			</dl>
	<t hangText="Value:"> This comprises one or more sub-TLVs.</t>		<t pn="section-5.2-7">
			The following sub-TLVs are defined in this document:</t>
	</list>		<table anchor="subTLV" align="left" pn="table-2">
	</t>		<name slugifiedName="name-sub-tlv-types-of-the-auto-b">Sub-TLV Types o
			f the AUTO-BANDWIDTH-ATTRIBUTES TLV</name>
	<t>		<thead>
	Following sub-TLVs are defined in this document:</t>		<tr>
			<th align="left" colspan="1" rowspan="1">Type</th>
	<figure><artwork><![CDATA[		<th align="left" colspan="1" rowspan="1">Len</th>
	Type Len Name		<th align="left" colspan="1" rowspan="1">Name</th>
	1 4 Sample-Interval sub-TLV		</tr>
	2 4 Adjustment-Interval sub-TLV		</thead>
	3 4 Down-Adjustment-Interval sub-TLV		<tbody>
	4 4 Adjustment-Threshold sub-TLV		<tr>
	5 8 Adjustment-Threshold-Percentage sub-TLV		<td align="left" colspan="1" rowspan="1">1</td>
	6 4 Down-Adjustment-Threshold sub-TLV		<td align="left" colspan="1" rowspan="1">4</td>
	7 8 Down-Adjustment-Threshold-Percentage sub-TLV		<td align="left" colspan="1" rowspan="1">Sample-Interval </td>
	8 4 Minimum-Bandwidth sub-TLV		</tr>
	9 4 Maximum-Bandwidth sub-TLV		<tr>
	10 8 Overflow-Threshold sub-TLV		<td align="left" colspan="1" rowspan="1">2</td>
	11 8 Overflow-Threshold-Percentage sub-TLV		<td align="left" colspan="1" rowspan="1">4</td>
	12 8 Underflow-Threshold sub-TLV		<td align="left" colspan="1" rowspan="1">Adjustment-Interval </td>
	13 8 Underflow-Threshold-Percentage sub-TLV		</tr>
	]]></artwork>		<tr>
	</figure>		<td align="left" colspan="1" rowspan="1">3</td>
			<td align="left" colspan="1" rowspan="1">4</td>
	<t>		<td align="left" colspan="1" rowspan="1">Down-Adjustment-Interval
			</td>
			</tr>
			<tr>
			<td align="left" colspan="1" rowspan="1">4</td>
			<td align="left" colspan="1" rowspan="1">4</td>
			<td align="left" colspan="1" rowspan="1">Adjustment-Threshold </td
			>
			</tr>
			<tr>
			<td align="left" colspan="1" rowspan="1">5</td>
			<td align="left" colspan="1" rowspan="1">8</td>
			<td align="left" colspan="1" rowspan="1">Adjustment-Threshold-Perc
			entage </td>
			</tr>
			<tr>
			<td align="left" colspan="1" rowspan="1">6</td>
			<td align="left" colspan="1" rowspan="1">4</td>
			<td align="left" colspan="1" rowspan="1">Down-Adjustment-Threshold
			</td>
			</tr>
			<tr>
			<td align="left" colspan="1" rowspan="1">7</td>
			<td align="left" colspan="1" rowspan="1">8</td>
			<td align="left" colspan="1" rowspan="1">Down-Adjustment-Threshold
			-Percentage </td>
			</tr>
			<tr>
			<td align="left" colspan="1" rowspan="1">8</td>
			<td align="left" colspan="1" rowspan="1">4</td>
			<td align="left" colspan="1" rowspan="1">Minimum-Bandwidth </td>
			</tr>
			<tr>
			<td align="left" colspan="1" rowspan="1">9</td>
			<td align="left" colspan="1" rowspan="1">4</td>
			<td align="left" colspan="1" rowspan="1">Maximum-Bandwidth </td>
			</tr>
			<tr>
			<td align="left" colspan="1" rowspan="1">10</td>
			<td align="left" colspan="1" rowspan="1">8</td>
			<td align="left" colspan="1" rowspan="1">Overflow-Threshold </td>
			</tr>
			<tr>
			<td align="left" colspan="1" rowspan="1">11</td>
			<td align="left" colspan="1" rowspan="1">8</td>
			<td align="left" colspan="1" rowspan="1">Overflow-Threshold-Percen
			tage </td>
			</tr>
			<tr>
			<td align="left" colspan="1" rowspan="1">12</td>
			<td align="left" colspan="1" rowspan="1">8</td>
			<td align="left" colspan="1" rowspan="1">Underflow-Threshold </td>
			</tr>
			<tr>
			<td align="left" colspan="1" rowspan="1">13</td>
			<td align="left" colspan="1" rowspan="1">8</td>
			<td align="left" colspan="1" rowspan="1">Underflow-Threshold-Perce
			ntage </td>
			</tr>
			</tbody>
			</table>
			<t pn="section-5.2-9">
	Future specifications can define additional sub-TLVs.</t>		Future specifications can define additional sub-TLVs.</t>
			<t pn="section-5.2-10">
	<t>
	The sub-TLVs are encoded to inform the PCEP peer of the various		The sub-TLVs are encoded to inform the PCEP peer of the various
	sampling and adjustment parameters. In case of a missing sub-TLV, as		sampling and adjustment parameters. In the case of a missing sub-TLV, as
	per the local policy, either the default value (as specified in this		per the local policy, either the default value (as specified in this
	document) or some other operator configured value is used.</t>		document) or some other operator-configured value is used.</t>
			<t pn="section-5.2-11">
	<t>		All sub-TLVs are optional, and any unrecognized sub-TLV <bcp14>MUST</bcp14> b
	All sub-TLVs are optional and any unrecognized sub-TLV MUST be		e
	ignored. If a sub-TLV of the same type appears more than once, only		ignored. If a sub-TLV of the same type appears more than once, only
	the first occurrence is processed and all others MUST be ignored.</t>		the first occurrence is processed, and all others <bcp14>MUST</bcp14> be igno
			red.</t>
	<t>		<t pn="section-5.2-12">
	The following sub-sections describe the sub-TLVs which are currently		The following subsections describe the sub-TLVs that are currently
	defined to be carried within the AUTO-BANDWIDTH-ATTRIBUTES TLV.</t>		defined as being carried within the AUTO-BANDWIDTH-ATTRIBUTES TLV.</t>
			<section anchor="sect-5.2.1" numbered="true" toc="include" removeInRFC="
	<section title="Sample-Interval sub-TLV" anchor="sect-5.2.1"><t>		false" pn="section-5.2.1">
	The Sample-Interval sub-TLV specifies a time interval in seconds at		<name slugifiedName="name-sample-interval-sub-tlv">Sample-Interval Sub
			-TLV</name>
			<t pn="section-5.2.1-1">
			The Sample-Interval sub-TLV specifies a time interval in seconds in
	which traffic samples are collected at the PCC.</t>		which traffic samples are collected at the PCC.</t>
			<figure anchor="Sample-Interval-sub-TLV" align="left" suppress-title="
	<figure><artwork><![CDATA[		false" pn="figure-4">
			<name slugifiedName="name-sample-interval-sub-tlv-for">Sample-Interv
			al Sub-TLV Format</name>
			<artwork name="" type="" align="left" alt="" pn="section-5.2.1-2.1">
	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 |
	+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+		+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+</artwork>
			</figure>
	Sample-Interval sub-TLV format		<t pn="section-5.2.1-3">
	]]></artwork>		The Type is 1, the Length is 4 octets, and the value comprises the followi
	</figure>		ng:</t>
			<dl newline="false" spacing="normal" indent="3" pn="section-5.2.1-4">
	<t>		<dt pn="section-5.2.1-4.1">Sample-Interval:</dt>
	The Type is 1, Length is 4 octets, and the value comprises of - </t>		<dd pn="section-5.2.1-4.2">The 4-octet time interval for the Bandwid
			th-Sample collection. The valid range is from 1 to 604800 (7
	<t><list style="hanging" hangIndent="3">
	<t hangText="Sample-Interval:"> The 4-octet time interval for
	bandwidth sample collection. The valid range is from 1 to 604800 (7
	days), in seconds. The default value is 300 seconds. Due care needs		days), in seconds. The default value is 300 seconds. Due care needs
	to be taken in case of a very low Sample-Interval, as it can have some		to be taken in a case with a very low Sample-Interval, as it can have som
	undesirable interactions with transport protocols (see <xref		e
	target="sect-6.6"/>). The sample-interval parameter MUST NOT be		undesirable interactions with transport protocols (see <xref target="sect
	greater than the (down) adjustment-interval. In case of an invalid		-6.6" format="default" sectionFormat="of" derivedContent="Section 6.6"/>). The S
	value, the Sub-TLV MUST be ignored and the previous value is		ample-Interval parameter <bcp14>MUST NOT</bcp14> be
	maintained.</t>		greater than the (down) Adjustment-Interval. In the case in which an inva
			lid
	</list>		value is present, the sub-TLV <bcp14>MUST</bcp14> be ignored and the
	</t>		previous value will be maintained.</dd>
			</dl>
	</section>		</section>
			<section anchor="sect-5.2.2" numbered="true" toc="include" removeInRFC="
	<section title="Adjustment Intervals" anchor="sect-5.2.2"><t> The		false" pn="section-5.2.2">
	sub-TLVs in this section are encoded to inform the PCEP peer the		<name slugifiedName="name-adjustment-intervals">Adjustment-Intervals</
	adjustment interval parameters. The Adjustment-Interval sub-TLV		name>
			<t pn="section-5.2.2-1"> The
			sub-TLVs in this section are encoded to inform the PCEP peer of the
			Adjustment-Interval parameters. The Adjustment-Interval sub-TLV
	specifies the time interval for both upward (Up-Adjustment-Interval)		specifies the time interval for both upward (Up-Adjustment-Interval)
	and downward (Down-Adjustment-Interval) trends. An implementation MAY		and downward (Down-Adjustment-Interval) trends. An implementation <bcp14>
	require to set a different adjustment interval values for when the		MAY</bcp14>
	bandwidth usage trend is downwards from when it is moving upwards. In		require that a different Adjustment-Interval value be set when the
	that case, the operator could use the Down-Adjustment-Interval sub-TLV		bandwidth usage trend is moving downwards from the one used when it is mo
			ving upwards. In
			that case, the operator could use the Down-Adjustment-Interval sub-TLV,
	which overrides the Adjustment-Interval value for		which overrides the Adjustment-Interval value for
	Down-Adjustment-Interval.</t>		Down-Adjustment-Interval.</t>
			<section anchor="sect-5.2.2.1" numbered="true" toc="include" removeInR
	<section title="Adjustment-Interval sub-TLV" anchor="sect-5.2.2.1"><t>		FC="false" pn="section-5.2.2.1">
			<name slugifiedName="name-adjustment-interval-sub-tlv">Adjustment-In
			terval Sub-TLV</name>
			<t pn="section-5.2.2.1-1">
	The Adjustment-Interval sub-TLV specifies a time interval in seconds		The Adjustment-Interval sub-TLV specifies a time interval in seconds
	at which bandwidth adjustment should be made in upward or downward		in which a bandwidth adjustment should be made in an upward or downward
	direction. This sub-TLV specify the value for Up-Adjustment-Interval		direction. This sub-TLV specifies the value for Up-Adjustment-Interval
	and Down-Adjustment-Interval when they are the same and the		and Down-Adjustment-Interval when they are the same and when the
	Down-Adjustment-Interval sub-TLV is not included.</t>		Down-Adjustment-Interval sub-TLV is not included.</t>
			<figure anchor="Adjustment-Interval-sub-TLV" align="left" suppress-t
	<figure><artwork><![CDATA[		itle="false" pn="figure-5">
			<name slugifiedName="name-adjustment-interval-sub-tlv-">Adjustment
			-Interval Sub-TLV Format</name>
			<artwork name="" type="" align="left" alt="" pn="section-5.2.2.1-2
			.1">
	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 |
	+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+		+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+</artwork>
			</figure>
	Adjustment-Interval sub-TLV format		<t pn="section-5.2.2.1-3">The Type is 2, the Length is 4 octets, and
	]]></artwork>		the value comprises the following:</t>
	</figure>		<dl newline="false" spacing="normal" indent="3" pn="section-5.2.2.1-
			4">
	<t>The Type is 2, Length is 4 octets, and the value comprises of - </t>		<dt pn="section-5.2.2.1-4.1">Adjustment-Interval:</dt>
			<dd pn="section-5.2.2.1-4.2">The 4-octet time interval for
	<t><list style="hanging" hangIndent="3">
	<t hangText="Adjustment-Interval:"> The 4-octet time interval for
	bandwidth adjustments. The valid range is from 1 to 604800 (7 days), in		bandwidth adjustments. The valid range is from 1 to 604800 (7 days), in
	seconds. The default value is 86400 seconds (1 day). The		seconds. The default value is 86400 seconds (1 day). The
	adjustment-interval parameter MUST NOT be less than the sample-interval,		Adjustment-Interval parameter <bcp14>MUST NOT</bcp14> be less than the Sam
	otherwise the Sub-TLV MUST be ignored and the previous value is		ple-Interval;
	maintained.</t>		otherwise, the sub-TLV <bcp14>MUST</bcp14> be ignored, and the previous
			value will be
	</list>		maintained.</dd>
	</t>		</dl>
			</section>
	</section>		<section anchor="sect-5.2.2.2" numbered="true" toc="include" removeInR
			FC="false" pn="section-5.2.2.2">
	<section title="Down-Adjustment-Interval sub-TLV" anchor="sect-5.2.2.2"><		<name slugifiedName="name-down-adjustment-interval-su">Down-Adjustme
	t>		nt-Interval Sub-TLV</name>
			<t pn="section-5.2.2.2-1">
	The Down-Adjustment-Interval sub-TLV specifies a time interval in		The Down-Adjustment-Interval sub-TLV specifies a time interval in
	seconds at which bandwidth adjustment should be made when MaxAvgBw is		seconds in which a bandwidth adjustment should be made when MaxAvgBw is
	less than the current bandwidth reservation of the LSP. This		less than the current bandwidth reservation of the LSP. This
	parameter overrides the Adjustment-Interval for the downward trend.		parameter overrides the Adjustment-Interval for the downward trend.
	This sub-TLV is used only when there is a need for different		This sub-TLV is used only when there is a need for different
	adjustment intervals in the upward and downward directions.</t>		Adjustment-Intervals in the upward and downward directions.</t>
			<figure anchor="Down-Adjustment-Interval-sub-TLV" align="left" suppr
	<figure><artwork><![CDATA[		ess-title="false" pn="figure-6">
			<name slugifiedName="name-down-adjustment-interval-sub">Down-Adjus
			tment-Interval Sub-TLV Format</name>
			<artwork name="" type="" align="left" alt="" pn="section-5.2.2.2-2
			.1">
	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 |
	+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+		+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+</artwork>
			</figure>
	Down-Adjustment-Interval sub-TLV format		<t pn="section-5.2.2.2-3">The Type is 3, the Length is 4 octets, and
	]]></artwork>		the value comprises the following: </t>
	</figure>		<dl newline="false" spacing="normal" indent="3" pn="section-5.2.2.2-
			4">
	<t>The Type is 3, Length is 4 octets, and the value comprises of - </t>		<dt pn="section-5.2.2.2-4.1">Down-Adjustment-Interval:</dt>
			<dd pn="section-5.2.2.2-4.2">The 4-octet time
	<t><list style="hanging" hangIndent="3">
	<t hangText="Down-Adjustment-Interval:"> The 4-octet time
	interval for downward bandwidth adjustments. The valid range is from		interval for downward bandwidth adjustments. The valid range is from
	1 to 604800 (7 days), in seconds. The default value equals the		1 to 604800 (7 days), in seconds. The default value equals the
	adjustment-interval. The down-adjustment-interval parameter MUST NOT		Adjustment-Interval. The Down-Adjustment-Interval parameter <bcp14>MUST
	be less than the sample-interval, otherwise the Sub-TLV MUST be		NOT</bcp14>
	ignored and the previous value is maintained.</t>		be less than the Sample-Interval; otherwise, the sub-TLV <bcp14>MUST</bcp
			14> be
	</list>		ignored and the previous value will be maintained.</dd>
	</t>		</dl>
			</section>
	</section>		</section>
			<section anchor="sect-5.2.3" numbered="true" toc="include" removeInRFC="
	</section>		false" pn="section-5.2.3">
			<name slugifiedName="name-adjustment-thresholds">Adjustment-Thresholds
	<section title="Adjustment Thresholds" anchor="sect-5.2.3"><t> The		</name>
			<t pn="section-5.2.3-1"> The
	sub-TLVs in this section are encoded to inform the PCEP peer of the		sub-TLVs in this section are encoded to inform the PCEP peer of the
	adjustment threshold parameters. An implementation MAY include both		Adjustment-Threshold parameters. An implementation <bcp14>MAY</bcp14> in clude 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. The Adjustment-Threshold sub-TLV specifies the		conditions are met. The Adjustment-Threshold sub-TLV specifies the
	threshold for both upward (Up-Adjustment-Threshold) and downward		threshold for both upward (Up-Adjustment-Threshold) and downward
	(Down-Adjustment-Threshold) trend. If the operator would like to use		(Down-Adjustment-Threshold) trends. If the operator would like to use
	a different adjustment threshold during the downward trend, the		a different Adjustment-Threshold during the downward trend, the
	Down-Adjustment-Threshold sub-TLV is included. Similarly, the		Down-Adjustment-Threshold sub-TLV is included. Similarly, the
	Adjustment-Threshold-Percentage sub-TLV specifies the threshold		Adjustment-Threshold-Percentage sub-TLV specifies the threshold
	percentage for both upward and downward trend. If the operator would		percentage for both upward and downward trends. If the operator would
	like to use a different adjustment threshold percentage during the		like to use a different Adjustment-Threshold percentage during the
	downward trend, the Down-Adjustment-Threshold-Percentage sub-TLV is		downward trend, the Down-Adjustment-Threshold-Percentage sub-TLV is
	included. It is worth noting that regardless of how the threshold are		included. It is worth noting that regardless of how the thresholds are
	set, the adjustment will not be made until at least one		set, the adjustment will not be made until at least one
	sample-interval simply because no sample will be made on which to base		Sample-Interval has passed simply because no sample will be made on which to base
	a comparison with a threshold.</t>		a comparison with a threshold.</t>
			<section anchor="sect-5.2.3.1" numbered="true" toc="include" removeInR
	<section title="Adjustment-Threshold sub-TLV"		FC="false" pn="section-5.2.3.1">
	anchor="sect-5.2.3.1"><t> The Adjustment-Threshold sub-TLV is used to		<name slugifiedName="name-adjustment-threshold-sub-tl">Adjustment-Th
	decide when the LSP bandwidth should be adjusted in upward or downward		reshold Sub-TLV</name>
	direction. This sub-TLV specify the absolute value for		<t pn="section-5.2.3.1-1">The Adjustment-Threshold sub-TLV is used t
			o
			decide when the LSP bandwidth should be adjusted in an upward or downward
			direction. This sub-TLV specifies the absolute value for
	Up-Adjustment-Threshold and Down-Adjustment-Threshold when they are		Up-Adjustment-Threshold and Down-Adjustment-Threshold when they are
	the same and the Down-Adjustment-Threshold sub-TLV is not		the same and when the Down-Adjustment-Threshold sub-TLV is not
	included.</t>		included.</t>
			<figure anchor="Adjustment-Threshold-sub-TLV" align="left" suppress-
	<figure><artwork><![CDATA[		title="false" pn="figure-7">
			<name slugifiedName="name-adjustment-threshold-sub-tlv">Adjustment
			-Threshold Sub-TLV Format</name>
			<artwork name="" type="" align="left" alt="" pn="section-5.2.3.1-2
			.1">
	0 1 2 3		0 1 2 3
	0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1		0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
	+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+		+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
	| Type=4 | Length=4 |		| Type=4 | Length=4 |
	+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+		+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
	| Adjustment-Threshold |		| Adjustment-Threshold |
	+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+		+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+</artwork>
			</figure>
	Adjustment-Threshold sub-TLV format		<t pn="section-5.2.3.1-3"> The Type is 4, the Length is 4 octets, an
	]]></artwork>		d the value comprises the following: </t>
	</figure>		<dl newline="false" spacing="normal" indent="3" pn="section-5.2.3.1-
			4">
	<t> The Type is 4, Length is 4 octets, and the value comprises of - </t>		<dt pn="section-5.2.3.1-4.1">Adjustment-Threshold:</dt>
			<dd pn="section-5.2.3.1-4.2">The absolute Adjustment-Threshold
	<t><list style="hanging" hangIndent="3">
	<t hangText="Adjustment-Threshold:"> The absolute Adjustment-Threshold
	bandwidth difference value, encoded in IEEE floating point format (see		bandwidth difference value, encoded in IEEE floating point format (see
	[<xref target="IEEE.754.1985"/>]), expressed in bytes per second. The		<xref target="IEEE.754.1985" format="default" sectionFormat="of" derivedCo
	default adjustment-threshold value is not set. Refer to Section 3.1.2		ntent="IEEE.754.1985"/>) and expressed in bytes per second. The
	of <xref target="RFC3471"/> for a table of commonly used values.</t>		default Adjustment-Threshold value is not set. Refer to <xref target="RFC
			3471" sectionFormat="of" section="3.1.2" format="default" derivedLink="https://r
	</list>		fc-editor.org/rfc/rfc3471#section-3.1.2" derivedContent="RFC3471"/> for a table
	</t>		of commonly used values.</dd>
			</dl>
	<t>		<t pn="section-5.2.3.1-5">
	If the modulus of difference between the current MaxAvgBw and the		If the modulus of difference between the current MaxAvgBw and the
	current bandwidth reservation is greater than or equal to the		current bandwidth reservation is greater than or equal to the
	threshold value, the LSP bandwidth is adjusted to the current		threshold value, the LSP bandwidth is adjusted to the current
	bandwidth demand (MaxAvgBw).</t>		bandwidth demand (MaxAvgBw).</t>
			<t pn="section-5.2.3.1-6">
	<t>		In the case in which an invalid value is present, the sub-TLV
	In case of an invalid value, the Sub-TLV MUST be ignored and the		<bcp14>MUST</bcp14> be ignored and the
	previous value is maintained.</t>		previous value will be maintained.</t>
			</section>
	</section>		<section anchor="sect-5.2.3.2" numbered="true" toc="include" removeInR
			FC="false" pn="section-5.2.3.2">
	<section title="Adjustment-Threshold-Percentage sub-TLV"		<name slugifiedName="name-adjustment-threshold-percen">Adjustment-Th
	anchor="sect-5.2.3.2"><t> The Adjustment-Threshold-Percentage sub-TLV		reshold-Percentage Sub-TLV</name>
	is used to decide when the LSP bandwidth should be adjusted in upward		<t pn="section-5.2.3.2-1">The Adjustment-Threshold-Percentage sub-TL
	or downward direction. This sub-TLV specify the percentage value for		V
			is used to decide when the LSP bandwidth should be adjusted in an upward
			or downward direction. This sub-TLV specifies the percentage value for
	Up-Adjustment-Threshold and Down-Adjustment-Threshold when they are		Up-Adjustment-Threshold and Down-Adjustment-Threshold when they are
	the same and the Down-Adjustment-Threshold-Percentage sub-TLV is not		the same and when the Down-Adjustment-Threshold-Percentage sub-TLV is not
	included.</t>		included.</t>
			<figure anchor="Adjustment-Threshold-Percentage-sub-TLV" align="left
	<figure><artwork><![CDATA[		" suppress-title="false" pn="figure-8">
			<name slugifiedName="name-adjustment-threshold-percent">Adjustment
			-Threshold-Percentage Sub-TLV Format</name>
			<artwork name="" type="" align="left" alt="" pn="section-5.2.3.2-2
			.1">
	0 1 2 3		0 1 2 3
	0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1		0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
	+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+		+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
	| Type=5 | Length=8 |		| Type=5 | Length=8 |
	+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+		+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
	| Reserved | Percentage |		| Reserved | Percentage |
	+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+		+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
	| Minimum-Threshold |		| Minimum-Threshold |
	+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+		+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+</artwork>
			</figure>
	Adjustment-Threshold-Percentage sub-TLV format		<t pn="section-5.2.3.2-3">The Type is 5, the Length is 8 octets, and
	]]></artwork>		the value comprises the following: </t>
	</figure>		<dl newline="false" spacing="normal" indent="3" pn="section-5.2.3.2-
			4">
	<t>The Type is 5, Length is 8 octets, and the value comprises of - </t>		<dt pn="section-5.2.3.2-4.1">Reserved:</dt>
			<dd pn="section-5.2.3.2-4.2">
	<t><list style="hanging" hangIndent="3">		<bcp14>MUST</bcp14> be set to zero on transmission and <bcp14>MU
			ST</bcp14> be
	<t hangText="Reserved:"> MUST be set to zero on transmission and MUST be		ignored on receipt.</dd>
	ignored on receipt.</t>		<dt pn="section-5.2.3.2-4.3">Percentage:</dt>
			<dd pn="section-5.2.3.2-4.4">The Adjustment-Threshold value (7 bit
	<t hangText="Percentage:"> The Adjustment-Threshold value (7 bits),		s),
	encoded in percentage (an integer from 1 to 100). The value 0 is		encoded in a percentage (an integer from 1 to 100). The value 0 is
	considered to be invalid. The default value is 5 percent.</t>		considered to be invalid. The default value is 5 percent.</dd>
			<dt pn="section-5.2.3.2-4.5">Minimum-Threshold:</dt>
	<t hangText="Minimum-Threshold:"> The absolute Minimum-Threshold		<dd pn="section-5.2.3.2-4.6">The absolute Minimum-Threshold
	bandwidth value, encoded in IEEE floating point format (see [<xref		bandwidth value, encoded in IEEE floating point format (see <xref target="
	target="IEEE.754.1985"/>]), expressed in bytes per second. The increase		IEEE.754.1985" format="default" sectionFormat="of" derivedContent="IEEE.754.1985
	or decrease of the LSP bandwidth MUST be at least or above the		"/>) and expressed in bytes per second. The increase
	minimum-threshold before the bandwidth adjustment is made. The default		or decrease of the LSP bandwidth <bcp14>MUST</bcp14> be at or above the
	value is 0.</t>		Minimum-Threshold before the bandwidth adjustment is made. The default
			value is 0.</dd>
	</list>		</dl>
	</t>		<t pn="section-5.2.3.2-5">
	<t>
	If the percentage absolute difference between the current MaxAvgBw		If the percentage absolute difference between the current MaxAvgBw
	and the current bandwidth reservation is greater than or equal to the		and the current bandwidth reservation is greater than or equal to the
	threshold percentage, and the difference in the bandwidth is at least		threshold percentage and the difference in the bandwidth is at or above the M
	or above the Minimum-Threshold, the LSP bandwidth is adjusted to the		inimum-Threshold, the LSP bandwidth is adjusted to the
	current bandwidth demand (MaxAvgBw).</t>		current bandwidth demand (MaxAvgBw).</t>
			<t pn="section-5.2.3.2-6">
	<t>		In the case in which an invalid value is present, the sub-TLV <bcp14>MUST</bc
	In case of an invalid value, the Sub-TLV MUST be ignored and the		p14> be ignored and the
	previous value is maintained.</t>		previous value will be maintained.</t>
			</section>
	</section>		<section anchor="sect-5.2.3.3" numbered="true" toc="include" removeInR
			FC="false" pn="section-5.2.3.3">
	<section title="Down-Adjustment-Threshold sub-TLV"		<name slugifiedName="name-down-adjustment-threshold-s">Down-Adjustme
	anchor="sect-5.2.3.3"><t> The Down-Adjustment-Threshold sub-TLV is		nt-Threshold Sub-TLV</name>
			<t pn="section-5.2.3.3-1">The Down-Adjustment-Threshold sub-TLV is
	used to decide when the LSP bandwidth should be adjusted when MaxAvgBw		used to decide when the LSP bandwidth should be adjusted when MaxAvgBw
	is lesser than the current bandwidth reservation. This parameter		is less than the current bandwidth reservation. This parameter
	overrides the Adjustment-Threshold for the downward trend. This		overrides the Adjustment-Threshold for the downward trend. This
	sub-TLV is used only when there is a need for different threshold in		sub-TLV is used only when there is a need for a different threshold in
	the upward and downward directions.</t>		the upward and downward directions.</t>
			<figure anchor="Down-Adjustment-Threshold-sub-TLV" align="left" supp
	<figure><artwork><![CDATA[		ress-title="false" pn="figure-9">
			<name slugifiedName="name-down-adjustment-threshold-su">Down-Adjus
			tment-Threshold Sub-TLV Format</name>
			<artwork name="" type="" align="left" alt="" pn="section-5.2.3.3-2
			.1">
	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 |
	+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+		+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+</artwork>
			</figure>
	Down-Adjustment-Threshold sub-TLV format		<t pn="section-5.2.3.3-3">The Type is 6, the Length is 4 octets, and
	]]></artwork>		the value comprises the following: </t>
	</figure>		<dl newline="false" spacing="normal" indent="3" pn="section-5.2.3.3-
			4">
	<t>The Type is 6, Length is 4 octets, and the value comprises of - </t>		<dt pn="section-5.2.3.3-4.1">Down-Adjustment-Threshold:</dt>
			<dd pn="section-5.2.3.3-4.2">The absolute
	<t><list style="hanging" hangIndent="3">
	<t hangText="Down-Adjustment-Threshold:"> The absolute
	Down-Adjustment-Threshold bandwidth value, encoded in IEEE floating		Down-Adjustment-Threshold bandwidth value, encoded in IEEE floating
	point format (see [<xref target="IEEE.754.1985"/>]), expressed in bytes		point format (see <xref target="IEEE.754.1985" format="default" sectionFor
	per second. The default value equals the adjustment-threshold. Refer		mat="of" derivedContent="IEEE.754.1985"/>) and expressed in bytes
	to Section 3.1.2 of <xref target="RFC3471"/> for a table of commonly		per second. The default value equals the Adjustment-Threshold. Refer
			to <xref target="RFC3471" sectionFormat="of" section="3.1.2" format="defau
			lt" derivedLink="https://rfc-editor.org/rfc/rfc3471#section-3.1.2" derivedConten
			t="RFC3471"/> for a table of commonly
	used values.		used values.
	</t>		</dd>
			</dl>
	</list>		<t pn="section-5.2.3.3-5">
	</t>		If the difference between the current bandwidth reservation and the
	<t>
	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).</t>		LSP bandwidth is adjusted to the current bandwidth demand (MaxAvgBw).</t>
			<t pn="section-5.2.3.3-6">
	<t>		In the case in which an invalid value is present, the sub-TLV <bcp14>MUST</bc
	In case of an invalid value, the Sub-TLV MUST be ignored and the		p14> be ignored and the
	previous value is maintained.</t>		previous value will be maintained.</t>
			</section>
	</section>		<section anchor="sect-5.2.3.4" numbered="true" toc="include" removeInR
			FC="false" pn="section-5.2.3.4">
	<section title="Down-Adjustment-Threshold-Percentage sub-TLV" anchor="sec		<name slugifiedName="name-down-adjustment-threshold-p">Down-Adjustme
	t-5.2.3.4"><t>		nt-Threshold-Percentage Sub-TLV</name>
			<t pn="section-5.2.3.4-1">
	The Down-Adjustment-Threshold-Percentage sub-TLV is used to decide		The Down-Adjustment-Threshold-Percentage sub-TLV is used to decide
	when the LSP bandwidth should be adjusted when MaxAvgBw is lesser		when the LSP bandwidth should be adjusted when MaxAvgBw is less than the curr
	than the current bandwidth reservation. This parameter overrides the		ent bandwidth reservation. This parameter overrides the
	Adjustment-Threshold-Percentage for the downward trend. This sub-TLV		Adjustment-Threshold-Percentage for the downward trend. This sub-TLV
	is used only when there is a need for different threshold percentage		is used only when there is a need for a different threshold percentage
	in the upward and downward directions.</t>		in the upward and downward directions.</t>
			<figure anchor="Down-Adjustment-Threshold-Percentage-sub-TLV" align=
	<figure><artwork><![CDATA[		"left" suppress-title="false" pn="figure-10">
			<name slugifiedName="name-down-adjustment-threshold-pe">Down-Adjus
			tment-Threshold-Percentage Sub-TLV Format</name>
			<artwork name="" type="" align="left" alt="" pn="section-5.2.3.4-2
			.1">
	0 1 2 3		0 1 2 3
	0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1		0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
	+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+		+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
	| Type=7 | Length=8 |		| Type=7 | Length=8 |
	+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+		+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
	| Reserved | Percentage |		| Reserved | Percentage |
	+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+		+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
	| Minimum-Threshold |		| Minimum-Threshold |
	+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+		+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+</artwork>
			</figure>
	Down-Adjustment-Threshold-Percentage sub-TLV format		<t pn="section-5.2.3.4-3">The Type is 7, the Length is 8 octets, and
	]]></artwork>		the value comprises the following:</t>
	</figure>		<dl newline="false" spacing="normal" indent="3" pn="section-5.2.3.4-
			4">
	<t>The Type is 7, Length is 8 octets, and the value comprises of -</t>		<dt pn="section-5.2.3.4-4.1">Reserved:</dt>
			<dd pn="section-5.2.3.4-4.2">
	<t><list style="hanging" hangIndent="3">		<bcp14>MUST</bcp14> be set to zero on transmission and <bcp14>MU
			ST</bcp14>
	<t hangText="Reserved:"> MUST be set to zero on transmission and MUST		be ignored on receipt.</dd>
	be ignored on receipt.</t>		<dt pn="section-5.2.3.4-4.3">Percentage:</dt>
			<dd pn="section-5.2.3.4-4.4">The Down-Adjustment-Threshold value (
	<t hangText="Percentage:"> The Down-Adjustment-Threshold value (7 bits),		7 bits),
	encoded in percentage (an integer from 1 to 100). The value 0 is		encoded in a percentage (an integer from 1 to 100). The value 0 is
	considered to be invalid. The default value equals the		considered to be invalid. The default value equals the
	adjustment-threshold-percentage.</t>		Adjustment-Threshold-Percentage.</dd>
			<dt pn="section-5.2.3.4-4.5">Minimum-Threshold:</dt>
	<t hangText="Minimum-Threshold:"> The absolute Minimum-Threshold		<dd pn="section-5.2.3.4-4.6">The absolute Minimum-Threshold
	bandwidth value, encoded in IEEE floating point format (see [<xref		bandwidth value, encoded in IEEE floating point format (see <xref target="
	target="IEEE.754.1985"/>]), expressed in bytes per second. The decrease		IEEE.754.1985" format="default" sectionFormat="of" derivedContent="IEEE.754.1985
	of the LSP bandwidth MUST be at least or above the minimum-threshold		"/>) and expressed in bytes per second. The decrease
			of the LSP bandwidth <bcp14>MUST</bcp14> be at or above the Minimum-Thresh
			old
	before the bandwidth adjustment is made. The default value equals the		before the bandwidth adjustment is made. The default value equals the
	minimum-threshold for the adjustment-threshold-percentage.</t>		Minimum-Threshold for the Adjustment-Threshold-Percentage.</dd>
			</dl>
	</list>		<t pn="section-5.2.3.4-5">
	</t>
	<t>
	If the percentage difference between the current bandwidth		If the percentage difference between the current bandwidth
	reservation and the current MaxAvgBw is greater than or equal to the		reservation and the current MaxAvgBw is greater than or equal to the
	threshold percentage, and the difference in the bandwidth is at least		threshold percentage and the difference in the bandwidth is at or above the M
	or above the Minimum-Threshold, the LSP bandwidth is adjusted to the		inimum-Threshold, the LSP bandwidth is adjusted to the
	current bandwidth demand (MaxAvgBw).</t>		current bandwidth demand (MaxAvgBw).</t>
			<t pn="section-5.2.3.4-6">
	<t>		In the case in which an invalid value is present, the sub-TLV <bcp14>MUST</bc
	In case of an invalid value, the Sub-TLV MUST be ignored and the		p14> be ignored and the
	previous value is maintained.</t>		previous value will be maintained.</t>
			</section>
	</section>		</section>
			<section anchor="sect-5.2.4" numbered="true" toc="include" removeInRFC="
	</section>		false" pn="section-5.2.4">
			<name slugifiedName="name-minimum-and-maximum-bandwid">Minimum and Max
	<section title="Minimum and Maximum Bandwidth Values" anchor="sect-5.2.4"		imum-Bandwidth Values</name>
	><section title="Minimum-Bandwidth sub-TLV" anchor="sect-5.2.4.1"><t>		<section anchor="sect-5.2.4.1" numbered="true" toc="include" removeInR
	The Minimum-Bandwidth sub-TLV specify the minimum bandwidth allowed		FC="false" pn="section-5.2.4.1">
	for the LSP, and is expressed in bytes per second. The LSP bandwidth		<name slugifiedName="name-minimum-bandwidth-sub-tlv">Minimum-Bandwid
	cannot be adjusted below the minimum bandwidth value.</t>		th Sub-TLV</name>
			<t pn="section-5.2.4.1-1">
	<figure><artwork><![CDATA[		The Minimum-Bandwidth sub-TLV specifies the Minimum-Bandwidth allowed
			for the LSP and is expressed in bytes per second. The LSP bandwidth
			cannot be adjusted below the Minimum-Bandwidth value.</t>
			<figure anchor="Minimum-Bandwidth-sub-TLV" align="left" suppress-tit
			le="false" pn="figure-11">
			<name slugifiedName="name-minimum-bandwidth-sub-tlv-f">Minimum-Ban
			dwidth Sub-TLV Format</name>
			<artwork name="" type="" align="left" alt="" pn="section-5.2.4.1-2
			.1">
	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 |
	+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+		+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+</artwork>
			</figure>
	Minimum-Bandwidth sub-TLV format		<t pn="section-5.2.4.1-3">The Type is 8, the Length is 4 octets, and
	]]></artwork>		the value comprises the following: </t>
	</figure>		<dl newline="false" spacing="normal" indent="3" pn="section-5.2.4.1-
			4">
	<t>The Type is 8, Length is 4 octets, and the value comprises of - </t>		<dt pn="section-5.2.4.1-4.1">Minimum-Bandwidth:</dt>
			<dd pn="section-5.2.4.1-4.2">The 4-octet bandwidth value encoded i
	<t><list style="hanging" hangIndent="3">		n
			IEEE floating point format (see <xref target="IEEE.754.1985" format="default
	<t hangText="Minimum-Bandwidth:"> The 4-octet bandwidth value encoded in		" sectionFormat="of" derivedContent="IEEE.754.1985"/>) and
	IEEE floating point format (see [<xref target="IEEE.754.1985"/>]),		expressed in bytes per second. The default Minimum-Bandwidth value is set
	expressed in bytes per second. The default minimum-bandwidth value is set		to 0. Refer to <xref target="RFC3471" sectionFormat="of" section="3.1.2" fo
	to 0. Refer to Section 3.1.2 of <xref target="RFC3471"/> for a table of		rmat="default" derivedLink="https://rfc-editor.org/rfc/rfc3471#section-3.1.2" de
	commonly used values.</t>		rivedContent="RFC3471"/> for a table of
			commonly used values.</dd>
	</list>		</dl>
	</t>		<t pn="section-5.2.4.1-5">
			In the case in which an invalid value is present, the sub-TLV <bcp14>MUST</bc
	<t>		p14> be ignored and the
	In case of an invalid value, the Sub-TLV MUST be ignored and the		previous value will be maintained.</t>
	previous value is maintained.</t>		</section>
			<section anchor="sect-5.2.4.2" numbered="true" toc="include" removeInR
	</section>		FC="false" pn="section-5.2.4.2">
			<name slugifiedName="name-maximum-bandwidth-sub-tlv">Maximum-Bandwid
	<section title="Maximum-Bandwidth sub-TLV" anchor="sect-5.2.4.2"><t>		th Sub-TLV</name>
	The Maximum-Bandwidth sub-TLV specify the maximum bandwidth allowed		<t pn="section-5.2.4.2-1">
	for the LSP, and is expressed in bytes per second. The LSP bandwidth		The Maximum-Bandwidth sub-TLV specifies the Maximum-Bandwidth allowed
	cannot be adjusted above the maximum bandwidth value.</t>		for the LSP and is expressed in bytes per second. The LSP bandwidth
			cannot be adjusted above the Maximum-Bandwidth value.</t>
	<figure><artwork><![CDATA[		<figure anchor="Maximum-Bandwidth-sub-TLV" align="left" suppress-tit
			le="false" pn="figure-12">
			<name slugifiedName="name-maximum-bandwidth-sub-tlv-f">Maximum-Ban
			dwidth Sub-TLV Format</name>
			<artwork name="" type="" align="left" alt="" pn="section-5.2.4.2-2
			.1">
	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 |
	+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+		+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+</artwork>
			</figure>
	Maximum-Bandwidth sub-TLV format		<t pn="section-5.2.4.2-3">The Type is 9, the Length is 4 octets, and
	]]></artwork>		the value comprises the following: </t>
	</figure>		<dl newline="false" spacing="normal" indent="3" pn="section-5.2.4.2-
			4">
	<t>The Type is 9, Length is 4 octets, and the value comprises of - </t>		<dt pn="section-5.2.4.2-4.1">Maximum-Bandwidth:</dt>
			<dd pn="section-5.2.4.2-4.2">The 4-octet bandwidth value encoded i
	<t><list style="hanging" hangIndent="3">		n
			IEEE floating point format (see <xref target="IEEE.754.1985" format="defau
	<t hangText="Maximum-Bandwidth:"> The 4-octet bandwidth value encoded in		lt" sectionFormat="of" derivedContent="IEEE.754.1985"/>) and expressed in bytes
	IEEE floating point format (see [<xref target="IEEE.754.1985"/>]),		per second. The default Maximum-Bandwidth value is
	expressed in bytes per second. The default maximum-bandwidth value is		not set. Refer to <xref target="RFC3471" sectionFormat="of" section="3.1.
	not set. Refer to Section 3.1.2 of <xref target="RFC3471"/> for a table		2" format="default" derivedLink="https://rfc-editor.org/rfc/rfc3471#section-3.1.
	of commonly used values.</t>		2" derivedContent="RFC3471"/> for a table
			of commonly used values.</dd>
	</list>		</dl>
	</t>		<t pn="section-5.2.4.2-5">
			In the case in which an invalid value is present, the sub-TLV <bcp14>MUST</bc
	<t>		p14> be ignored and the
	In case of an invalid value, the Sub-TLV MUST be ignored and the		previous value will be maintained.</t>
	previous value is maintained.</t>		</section>
			</section>
	</section>		<section anchor="sect-5.2.5" numbered="true" toc="include" removeInRFC="
			false" pn="section-5.2.5">
	</section>		<name slugifiedName="name-overflow-and-underflow-cond">Overflow and Un
			derflow Conditions</name>
	<section title="Overflow and Underflow Conditions" anchor="sect-5.2.5"><t		<t pn="section-5.2.5-1">
	>		The sub-TLVs in this section are encoded to inform the PCEP peer of the
	The sub-TLVs in this section are encoded to inform the PCEP peer the		overflow and underflow threshold parameters. An implementation <bcp14>MAY</b
	overflow and underflow threshold parameters. An implementation MAY		cp14>
	include sub-TLVs for an absolute value and/or a percentage for the		include sub-TLVs for an absolute value and/or a percentage for the
	threshold, in which case the bandwidth is immediately adjusted when		threshold, in which case the bandwidth is immediately adjusted when
	either of the threshold conditions is met consecutively for the given		either of the threshold conditions is met consecutively for the given
	count (as long as the difference in the bandwidth is at least or		count (as long as the difference in the bandwidth is at or
	above the Minimum-Threshold). By default, the threshold values for		above the Minimum-Threshold). By default, the threshold values for
	overflow and underflow conditions are not set.</t>		overflow and underflow conditions are not set.</t>
			<section anchor="sect-5.2.5.1" numbered="true" toc="include" removeInR
	<section title="Overflow-Threshold sub-TLV" anchor="sect-5.2.5.1"><t>		FC="false" pn="section-5.2.5.1">
			<name slugifiedName="name-overflow-threshold-sub-tlv">Overflow-Thres
			hold Sub-TLV</name>
			<t pn="section-5.2.5.1-1">
	The Overflow-Threshold sub-TLV is used to decide if the LSP bandwidth		The Overflow-Threshold sub-TLV is used to decide if the LSP bandwidth
	should be adjusted immediately.</t>		should be adjusted immediately.</t>
			<figure anchor="Overflow-Threshold-sub-TLV" align="left" suppress-ti
	<figure><artwork><![CDATA[		tle="false" pn="figure-13">
			<name slugifiedName="name-overflow-threshold-sub-tlv-">Overflow-Th
			reshold Sub-TLV Format</name>
			<artwork name="" type="" align="left" alt="" pn="section-5.2.5.1-2
			.1">
	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 |
	+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+		+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+</artwork>
			</figure>
	Overflow-Threshold sub-TLV format		<t pn="section-5.2.5.1-3">The Type is 10, the Length is 8 octets, an
	]]></artwork>		d the value comprises the following: </t>
	</figure>		<dl newline="false" spacing="normal" indent="3" pn="section-5.2.5.1-
			4">
	<t>The Type is 10, Length is 8 octets, and the value comprises of - </t>		<dt pn="section-5.2.5.1-4.1">Reserved:</dt>
			<dd pn="section-5.2.5.1-4.2">
	<t><list style="hanging" hangIndent="3">		<bcp14>MUST</bcp14> be set to zero on transmission and <bcp14>MU
			ST</bcp14>
	<t hangText="Reserved:"> MUST be set to zero on transmission and MUST		be ignored on receipt.</dd>
	be ignored on receipt.</t>		<dt pn="section-5.2.5.1-4.3">Count:</dt>
			<dd pn="section-5.2.5.1-4.4">The Overflow-Count value (5 bits), en
	<t hangText="Count:"> The Overflow-Count value (5 bits), encoded in		coded in
	integer. The value 0 is considered to be invalid. The number of		an integer. The value 0 is considered to be invalid. The number of
	consecutive samples for which the overflow condition MUST be met for		consecutive samples for which the overflow condition <bcp14>MUST</bcp14>
	the LSP bandwidth to be immediately adjusted to the current bandwidth		be met for
	demand, bypassing the (up) adjustment-interval.</t>		the LSP bandwidth is to be immediately adjusted to the current bandwidth
			demand, bypassing the (up) Adjustment-Interval.</dd>
	<t hangText="Overflow-Threshold:"> The absolute Overflow-Threshold		<dt pn="section-5.2.5.1-4.5">Overflow-Threshold:</dt>
	bandwidth value, encoded in IEEE floating point format (see [<xref		<dd pn="section-5.2.5.1-4.6"> The absolute Overflow-Threshold
	target="IEEE.754.1985"/>]), expressed in bytes per second. Refer to		bandwidth value, encoded in IEEE floating point format (see <xref target=
	Section 3.1.2 of <xref target="RFC3471"/> for a table of commonly used		"IEEE.754.1985" format="default" sectionFormat="of" derivedContent="IEEE.754.198
	values. If the difference of the current MaxAvgBw from the current		5"/>) and expressed in bytes per
			second. Refer to <xref target="RFC3471" sectionFormat="of" section="3.1.
			2" format="default" derivedLink="https://rfc-editor.org/rfc/rfc3471#section-3.1.
			2" derivedContent="RFC3471"/> for a table of commonly used
			values. If the difference between the current MaxAvgBw and the current
	bandwidth reservation is greater than or equal to the threshold value,		bandwidth reservation is greater than or equal to the threshold value,
	the overflow condition is met.</t>		the overflow condition is met.</dd>
			</dl>
	</list>		<t pn="section-5.2.5.1-5">
	</t>		In the case in which an invalid value is present, the sub-TLV <bcp14>MUST</bc
			p14> be ignored and the
	<t>		previous value will be maintained.</t>
	In case of an invalid value, the Sub-TLV MUST be ignored and the		</section>
	previous value is maintained.</t>		<section anchor="sect-5.2.5.2" numbered="true" toc="include" removeInR
			FC="false" pn="section-5.2.5.2">
	</section>		<name slugifiedName="name-overflow-threshold-percenta">Overflow-Thre
			shold-Percentage Sub-TLV</name>
	<section title="Overflow-Threshold-Percentage sub-TLV" anchor="sect-5.2.5		<t pn="section-5.2.5.2-1">
	.2"><t>
	The Overflow-Threshold-Percentage sub-TLV is used to decide if the		The Overflow-Threshold-Percentage sub-TLV is used to decide if the
	LSP bandwidth should be adjusted immediately.</t>		LSP bandwidth should be adjusted immediately.</t>
			<figure anchor="Overflow-Threshold-Percentage-sub-TLV" align="left"
	<figure><artwork><![CDATA[		suppress-title="false" pn="figure-14">
			<name slugifiedName="name-overflow-threshold-percentag">Overflow-T
			hreshold-Percentage Sub-TLV Format</name>
			<artwork name="" type="" align="left" alt="" pn="section-5.2.5.2-2
			.1">
	0 1 2 3		0 1 2 3
	0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1		0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
	+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+		+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
	| Type=11 | Length=8 |		| Type=11 | Length=8 |
	+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+		+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
	| Percentage | Reserved | Count |		| Percentage | Reserved | Count |
	+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+		+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
	| Minimum-Threshold |		| Minimum-Threshold |
	+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+		+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+</artwork>
			</figure>
	Overflow-Threshold-Percentage sub-TLV format		<t pn="section-5.2.5.2-3">The Type is 11, the Length is 8 octets, an
	]]></artwork>		d the value comprises the following:</t>
	</figure>		<dl newline="false" spacing="normal" indent="3" pn="section-5.2.5.2-
			4">
	<t>The Type is 11, Length is 8 octets, and the value comprises of -</t>		<dt pn="section-5.2.5.2-4.1">Percentage:</dt>
			<dd pn="section-5.2.5.2-4.2">The Overflow-Threshold value (7 bits)
	<t><list style="hanging" hangIndent="3">		, encoded
			in a percentage (an integer from 1 to 100). The value 0 is considered to
	<t hangText="Percentage:"> The Overflow-Threshold value (7 bits), encoded
	in percentage (an integer from 1 to 100). The value 0 is considered to
	be invalid. If the percentage increase of the current MaxAvgBw from the		be invalid. If the percentage increase of the current MaxAvgBw from the
	current bandwidth reservation is greater than or equal to the threshold		current bandwidth reservation is greater than or equal to the threshold
	percentage, the overflow condition is met.</t>		percentage, the overflow condition is met.</dd>
			<dt pn="section-5.2.5.2-4.3">Reserved:</dt>
	<t hangText="Reserved:"> MUST be set to zero on transmission and MUST be		<dd pn="section-5.2.5.2-4.4">
	ignored on receipt.</t>		<bcp14>MUST</bcp14> be set to zero on transmission and <bcp14>MU
			ST</bcp14> be
	<t hangText="Count:"> The Overflow-Count value (5 bits), encoded in		ignored on receipt.</dd>
	integer. The value 0 is considered to be invalid. The number of		<dt pn="section-5.2.5.2-4.5">Count:</dt>
	consecutive samples for which the overflow condition MUST be met for the		<dd pn="section-5.2.5.2-4.6">The Overflow-Count value (5 bits), en
	LSP bandwidth to be immediately adjusted to the current bandwidth demand,		coded in
	bypassing the (up) adjustment-interval.</t>		an integer. The value 0 is considered to be invalid. The number of
			consecutive samples for which the overflow condition <bcp14>MUST</bcp14> be
	<t hangText="Minimum-Threshold:"> The absolute Minimum-Threshold		met for the
	bandwidth value, encoded in IEEE floating point format (see [<xref		LSP bandwidth is to be immediately adjusted to the current bandwidth demand
	target="IEEE.754.1985"/>]), expressed in bytes per second. The increase		,
	of the LSP bandwidth MUST be at least or above the minimum-threshold		bypassing the (up) Adjustment-Interval.</dd>
	before the bandwidth adjustment is made.</t>		<dt pn="section-5.2.5.2-4.7">Minimum-Threshold:</dt>
			<dd pn="section-5.2.5.2-4.8">The absolute Minimum-Threshold
	</list>		bandwidth value, encoded in IEEE floating point format (see <xref target="I
	</t>		EEE.754.1985" format="default" sectionFormat="of" derivedContent="IEEE.754.1985"
			/>) and expressed in bytes per second. The increase
	<t>		of the LSP bandwidth <bcp14>MUST</bcp14> be at or above the Minimum-Thresho
	In case of an invalid value, the Sub-TLV MUST be ignored and the		ld
	previous value is maintained.</t>		before the bandwidth adjustment is made.</dd>
			</dl>
	</section>		<t pn="section-5.2.5.2-5">
			In the case in which an invalid value is present, the sub-TLV <bcp14>MUST</bc
	<section title="Underflow-Threshold sub-TLV" anchor="sect-5.2.5.3"><t>		p14> be ignored and the
			previous value will be maintained.</t>
			</section>
			<section anchor="sect-5.2.5.3" numbered="true" toc="include" removeInR
			FC="false" pn="section-5.2.5.3">
			<name slugifiedName="name-underflow-threshold-sub-tlv">Underflow-Thr
			eshold Sub-TLV</name>
			<t pn="section-5.2.5.3-1">
	The Underflow-Threshold sub-TLV is used to decide if the LSP		The Underflow-Threshold sub-TLV is used to decide if the LSP
	bandwidth should be adjusted immediately.</t>		bandwidth should be adjusted immediately.</t>
			<figure anchor="Underflow-Threshold-sub-TLV" align="left" suppress-t
	<figure><artwork><![CDATA[		itle="false" pn="figure-15">
			<name slugifiedName="name-underflow-threshold-sub-tlv-">Underflow-
			Threshold Sub-TLV Format</name>
			<artwork name="" type="" align="left" alt="" pn="section-5.2.5.3-2
			.1">
	0 1 2 3		0 1 2 3
	0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1		0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
	+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+		+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
	| Type=12 | Length=8 |		| Type=12 | Length=8 |
	+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+		+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
	| Reserved | Count |		| Reserved | Count |
	+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+		+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
	| Underflow-Threshold |		| Underflow-Threshold |
	+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+		+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+</artwork>
			</figure>
	Underflow-Threshold sub-TLV format		<t pn="section-5.2.5.3-3">The Type is 12, the Length is 8 octets, an
			d the value comprises the following: </t>
	]]></artwork>		<dl newline="false" spacing="normal" indent="3" pn="section-5.2.5.3-
	</figure>		4">
			<dt pn="section-5.2.5.3-4.1">Reserved:</dt>
	<t>The Type is 12, Length is 8 octets, and the value comprises of - </t>		<dd pn="section-5.2.5.3-4.2">
			<bcp14>MUST</bcp14> be set to zero on transmission and <bcp14>MU
	<t><list style="hanging" hangIndent="3">		ST</bcp14> be
			ignored on receipt.</dd>
	<t hangText="Reserved:"> MUST be set to zero on transmission and MUST be		<dt pn="section-5.2.5.3-4.3">Count:</dt>
	ignored on receipt.</t>		<dd pn="section-5.2.5.3-4.4"> The Underflow-Count value (5 bits),
			encoded in an integer.
	<t hangText="Count:"> The Underflow-Count value (5 bits), encoded in integ
	er.
	The value 0 is considered to be invalid. The number of		The value 0 is considered to be invalid. The number of
	consecutive samples for which the underflow condition MUST be met		consecutive samples for which the underflow condition <bcp14>MUST</bcp14>
	for the LSP bandwidth to be immediately adjusted to the current		be met
	bandwidth demand, bypassing the down-adjustment-interval.</t>		for the LSP bandwidth is to be immediately adjusted to the current
			bandwidth demand, bypassing the Down-Adjustment-Interval.</dd>
	<t hangText="Underflow-Threshold:"> The absolute Underflow-Threshold		<dt pn="section-5.2.5.3-4.5">Underflow-Threshold:</dt>
	bandwidth value, encoded in IEEE floating point format (see [<xref		<dd pn="section-5.2.5.3-4.6"> The absolute Underflow-Threshold
	target="IEEE.754.1985"/>]), expressed in bytes per second. Refer to		bandwidth value, encoded in IEEE floating point format (see <xref target="
	Section 3.1.2 of <xref target="RFC3471"/> for a table of commonly used		IEEE.754.1985" format="default" sectionFormat="of" derivedContent="IEEE.754.1985
	values. If the difference of the current MaxAvgBw from the current		"/>) and expressed in bytes per second. Refer to
			<xref target="RFC3471" sectionFormat="of" section="3.1.2" format="default"
			derivedLink="https://rfc-editor.org/rfc/rfc3471#section-3.1.2" derivedContent="
			RFC3471"/> for a table of commonly used
			values. If the difference between the current MaxAvgBw and the current
	bandwidth reservation is greater than or equal to the threshold value,		bandwidth reservation is greater than or equal to the threshold value,
	the underflow condition is met.</t>		the underflow condition is met.</dd>
			</dl>
	</list>		<t pn="section-5.2.5.3-5">
	</t>		In the case in which an invalid value is present, the sub-TLV <bcp14>MUST</bc
			p14> be ignored and the
	<t>		previous value will be maintained.</t>
	In case of an invalid value, the Sub-TLV MUST be ignored and the		</section>
	previous value is maintained.</t>		<section anchor="sect-5.2.5.4" numbered="true" toc="include" removeInR
			FC="false" pn="section-5.2.5.4">
	</section>		<name slugifiedName="name-underflow-threshold-percent">Underflow-Thr
			eshold-Percentage Sub-TLV</name>
	<section title="Underflow-Threshold-Percentage sub-TLV" anchor="sect-5.2.		<t pn="section-5.2.5.4-1">
	5.4"><t>
	The Underflow-Threshold-Percentage sub-TLV is used to decide if the		The Underflow-Threshold-Percentage sub-TLV is used to decide if the
	LSP bandwidth should be adjusted immediately.</t>		LSP bandwidth should be adjusted immediately.</t>
			<figure anchor="Underflow-Threshold-Percentage-sub-TLV" align="left"
	<figure><artwork><![CDATA[		suppress-title="false" pn="figure-16">
			<name slugifiedName="name-underflow-threshold-percenta">Underflow-
			Threshold-Percentage Sub-TLV Format</name>
			<artwork name="" type="" align="left" alt="" pn="section-5.2.5.4-2
			.1">
	0 1 2 3		0 1 2 3
	0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1		0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
	+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+		+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
	| Type=13 | Length=8 |		| Type=13 | Length=8 |
	+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+		+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
	| Percentage | Reserved | Count |		| Percentage | Reserved | Count |
	+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+		+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
	| Minimum-Threshold |		| Minimum-Threshold |
	+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+		+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+</artwork>
			</figure>
	Underflow-Threshold-Percentage sub-TLV format		<t pn="section-5.2.5.4-3">The Type is 13, the Length is 8 octets, an
	]]></artwork>		d the value comprises the following:</t>
	</figure>		<dl newline="false" spacing="normal" indent="3" pn="section-5.2.5.4-
			4">
	<t>The Type is 13, Length is 8 octets, and the value comprises of -</t>		<dt pn="section-5.2.5.4-4.1">Percentage:</dt>
			<dd pn="section-5.2.5.4-4.2"> The Underflow-Threshold value (7 bit
	<t><list style="hanging" hangIndent="3">		s),
	<t hangText="Percentage:"> The Underflow-Threshold value (7 bits),
	encoded in percentage (an integer from 1 to 100). The value 0 is		encoded in percentage (an integer from 1 to 100). The value 0 is
	considered to be invalid. If the percentage decrease of the current		considered to be invalid. If the percentage decrease of the current
	MaxAvgBw from the current bandwidth reservation is greater than or equal		MaxAvgBw from the current bandwidth reservation is greater than or equal
	to the threshold percentage, the underflow condition is met.</t>		to the threshold percentage, the underflow condition is met.</dd>
			<dt pn="section-5.2.5.4-4.3">Reserved:</dt>
	<t hangText="Reserved:"> MUST be set to zero on transmission and MUST be		<dd pn="section-5.2.5.4-4.4">
	ignored on receipt.</t>		<bcp14>MUST</bcp14> be set to zero on transmission and <bcp14>MU
			ST</bcp14> be
	<t hangText="Count:"> The Underflow-Count value (5 bits), encoded in		ignored on receipt.</dd>
	integer. The value 0 is considered to be invalid. The number of		<dt pn="section-5.2.5.4-4.5">Count:</dt>
	consecutive samples for which the underflow condition MUST be met for		<dd pn="section-5.2.5.4-4.6"> The Underflow-Count value (5 bits),
	the LSP bandwidth to be immediately adjusted to the current bandwidth		encoded in an integer. The value 0 is considered to be invalid. The number of
	demand, bypassing the down-adjustment-interval.</t>		consecutive samples for which the underflow condition <bcp14>MUST</bcp14>
			be met for
	<t hangText="Minimum-Threshold:"> The absolute Minimum-Threshold		the LSP bandwidth is to be immediately adjusted to the current bandwidth
	bandwidth value, encoded in IEEE floating point format (see [<xref		demand, bypassing the Down-Adjustment-Interval.</dd>
	target="IEEE.754.1985"/>]), expressed in bytes per second. The decrease		<dt pn="section-5.2.5.4-4.7">Minimum-Threshold:</dt>
	of the LSP bandwidth MUST be at least or above the minimum-threshold		<dd pn="section-5.2.5.4-4.8"> The absolute Minimum-Threshold
	before the bandwidth adjustment is made.</t>		bandwidth value, encoded in IEEE floating point format (see <xref target="
			IEEE.754.1985" format="default" sectionFormat="of" derivedContent="IEEE.754.1985
	</list>		"/>) and expressed in bytes per second. The decrease
	</t>		of the LSP bandwidth <bcp14>MUST</bcp14> be at or above the Minimum-Thresh
			old
	<t>		before the bandwidth adjustment is made.</dd>
	In case of an invalid value, the Sub-TLV MUST be ignored and the		</dl>
	previous value is maintained.</t>		<t pn="section-5.2.5.4-5">
			In the case in which an invalid value is present, the sub-TLV <bcp14>MUST</bc
	</section>		p14> be ignored and the
			previous value will be maintained.</t>
	</section>		</section>
			</section>
	</section>		</section>
			<section anchor="sect-5.3" numbered="true" toc="include" removeInRFC="fals
	<section title="BANDWIDTH Object" anchor="sect-5.3"><t>		e" pn="section-5.3">
	As per <xref target="RFC5440"/>, the BANDWIDTH object (Object-Class value 5)		<name slugifiedName="name-bandwidth-object">BANDWIDTH Object</name>
	is		<t pn="section-5.3-1">
	defined with two Object-Type values as following:</t>		As per <xref target="RFC5440" format="default" sectionFormat="of" derivedCont
			ent="RFC5440"/>, the BANDWIDTH object (Object-Class value 5) is
	<t><list style="hanging" hangIndent="3">		defined with two Object-Type values as follows:</t>
			<dl newline="false" spacing="normal" indent="3" pn="section-5.3-2">
	<t hangText="Requested Bandwidth:"> BANDWIDTH Object-Type value is		<dt pn="section-5.3-2.1">Requested Bandwidth:</dt>
	1.</t>		<dd pn="section-5.3-2.2">The BANDWIDTH Object-Type value is
			1.</dd>
	<t hangText="Re-optimization Bandwidth:"> Bandwidth of an existing TE		<dt pn="section-5.3-2.3">Reoptimization Bandwidth:</dt>
	LSP for which a re-optimization is requested. BANDWIDTH Object-Type		<dd pn="section-5.3-2.4">The bandwidth of an existing TE
	value is 2.</t>		LSP for which a reoptimization is requested. The BANDWIDTH Object-Type
			value is 2.</dd>
	</list>		</dl>
	</t>		<t pn="section-5.3-3">
	<t>
	The PCC reports the calculated bandwidth to be adjusted (MaxAvgBw) to		The PCC reports the calculated bandwidth to be adjusted (MaxAvgBw) to
	the Stateful PCE using the existing 'Requested Bandwidth' with		the stateful PCE using the existing 'Requested Bandwidth' with the BANDWIDTH
	BANDWIDTH Object-Type as 1. The reporting of the 're-optimization		Object-Type as 1. The reporting of the 'reoptimization
	bandwidth' with BANDWIDTH Object-Type as 2 is not required as the		bandwidth' with BANDWIDTH Object-Type as 2 is not required as the
	Stateful PCE is aware of the existing LSP bandwidth.</t>		stateful PCE is aware of the existing LSP bandwidth.</t>
			</section>
	</section>		<section anchor="sect-5.4" numbered="true" toc="include" removeInRFC="fals
			e" pn="section-5.4">
	<section title="The PCInitiate Message" anchor="sect-5.4"><t>		<name slugifiedName="name-the-pcinitiate-message">The PCInitiate Message
			</name>
			<t pn="section-5.4-1">
	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 <xref target="RFC8281"/>.</t>		trigger LSP instantiation or deletion <xref target="RFC8281" format="default"
			sectionFormat="of" derivedContent="RFC8281"/>.</t>
	<t>		<t pn="section-5.4-2">
	For the PCE-Initiated LSP with Auto-Bandwidth feature enabled,		For the PCE-initiated LSP with the auto-bandwidth feature enabled,
	AUTO-BANDWIDTH-ATTRIBUTES TLV MUST be included in the LSPA object with the		AUTO-BANDWIDTH-ATTRIBUTES TLV <bcp14>MUST</bcp14> be included in the LSPA obj
			ect with the
	PCInitiate message.</t>		PCInitiate message.</t>
			<t pn="section-5.4-3">
	<t>		The Routing Backus-Naur Form (RBNF) definition of the PCInitiate
	The Routing Backus-Naur Format (RBNF) definition of the PCInitiate		message <xref target="RFC8281" format="default" sectionFormat="of" derivedCon
	message <xref target="RFC8281"/> is unchanged by this document.</t>		tent="RFC8281"/> is unchanged by this document.</t>
			</section>
	</section>		<section anchor="sect-5.5" numbered="true" toc="include" removeInRFC="fals
			e" pn="section-5.5">
	<section title="The PCUpd Message" anchor="sect-5.5"><t>		<name slugifiedName="name-the-pcupd-message">The PCUpd Message</name>
			<t pn="section-5.5-1">
	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 <xref target="RFC8231"/>.</t>		the LSP parameters <xref target="RFC8231" format="default" sectionFormat="of"
			derivedContent="RFC8231"/>.</t>
	<t>		<t pn="section-5.5-2">
	For PCE-Initiated LSPs with Auto-Bandwidth feature enabled,		For PCE-initiated LSPs with the auto-bandwidth feature enabled,
	AUTO-BANDWIDTH-ATTRIBUTES TLV MUST be included in the LSPA object with the		the AUTO-BANDWIDTH-ATTRIBUTES TLV <bcp14>MUST</bcp14> be included in the LSPA
			object with the
	PCUpd message. The PCE can send this TLV to direct the PCC to change the		PCUpd message. The PCE can send this TLV to direct the PCC to change the
	auto-bandwidth parameters.</t>		auto-bandwidth parameters.</t>
			<t pn="section-5.5-3">
	<t>		The RBNF definition of the PCUpd message <xref target="RFC8231" format="defau
	The RBNF definition of the PCUpd message <xref target="RFC8231"/> is unchange		lt" sectionFormat="of" derivedContent="RFC8231"/> is unchanged by
	d by
	this document.</t>		this document.</t>
			</section>
	</section>		<section anchor="sect-5.6" numbered="true" toc="include" removeInRFC="fals
			e" pn="section-5.6">
	<section title="The PCRpt Message" anchor="sect-5.6"><t>		<name slugifiedName="name-the-pcrpt-message">The PCRpt Message</name>
	The PCRpt message <xref target="RFC8231"/> is a PCEP message sent by a PCC to		<t pn="section-5.6-1">
	a PCE		The PCRpt message <xref target="RFC8231" format="default" sectionFormat="of"
			derivedContent="RFC8231"/> is a PCEP message sent by a PCC to a PCE
	to report the status of one or more LSPs.</t>		to report the status of one or more LSPs.</t>
			<t pn="section-5.6-2">
	<t>		For PCE-initiated LSPs <xref target="RFC8281" format="default" sectionFormat=
	For PCE-Initiated LSPs <xref target="RFC8281"/>, the PCC creates the LSP usin		"of" derivedContent="RFC8281"/>, the PCC creates the LSP using the
	g the		attributes communicated by the PCE and 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
	the LSP, PCC automatically delegates the LSP to the PCE and generates		the LSP, the PCC automatically delegates the LSP to the PCE and generates
	a PCRpt message to provide the status report for the LSP.</t>		a PCRpt message to provide the status report for the LSP.</t>
			<t pn="section-5.6-3">
	<t>		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.</t>		specify the requested bandwidth in the PCRpt message.</t>
			<t pn="section-5.6-4">
	<t>		The RBNF definition of the PCRpt message <xref target="RFC8231" format="defau
	The RBNF definition of the PCRpt message <xref target="RFC8231"/> is unchange		lt" sectionFormat="of" derivedContent="RFC8231"/> is unchanged by
	d by
	this document.</t>		this document.</t>
			</section>
	</section>		<section anchor="sect-5.7" numbered="true" toc="include" removeInRFC="fals
			e" pn="section-5.7">
	<section title="The PCNtf Message" anchor="sect-5.7"><t>		<name slugifiedName="name-the-pcntf-message">The PCNtf Message</name>
	As per <xref target="RFC5440"/>, the PCEP Notification message (PCNtf) can be		<t pn="section-5.7-1">
	sent		As per <xref target="RFC5440" format="default" sectionFormat="of" derivedCont
			ent="RFC5440"/>, the PCEP Notification message (PCNtf) can be sent
	by a PCEP speaker to notify its peer of a specific event.</t>		by a PCEP speaker to notify its peer of a specific event.</t>
			<t pn="section-5.7-2">
	<t>		A PCEP speaker (PCE or PCC) <bcp14>SHOULD</bcp14> notify its PCEP peer (PCC o
	A PCEP speaker (PCE or PCC) SHOULD notify its PCEP peer (PCC or PCE)		r PCE)
	when it is in overwhelmed state due to the auto-bandwidth feature.		when it is in an overwhelmed state due to the auto-bandwidth feature.
	An implementation needs to make an attempt to send this notification		An implementation needs to make an attempt to send this notification
	(when overwhelmed by auto-bandwidth adjustments) unless sending this		(when overwhelmed by auto-bandwidth adjustments) unless sending this
	notification would only serve to increase the load further. Note that		notification would only serve to increase the load further. Note that
	when the notification is not received the PCEP speaker would continue		when the notification is not received, the PCEP speaker would continue
	to request bandwidth adjustments even when they could not be handled		to request bandwidth adjustments even when they cannot be handled
	in a timely fashion.</t>		in a timely fashion.</t>
			<t pn="section-5.7-3">
	<t>		Upon receipt of an auto-bandwidth overwhelm notification, the peer
	Upon receipt of auto-bandwidth overwhelm notification, the peer		<bcp14>SHOULD NOT</bcp14> send any PCEP messages related to auto-bandwidth
	SHOULD NOT send any PCEP messages related to auto-bandwidth
	adjustment. If a PCEP message related to auto-bandwidth adjustment		adjustment. If a PCEP message related to auto-bandwidth adjustment
	is received during in overwhelmed state, it MUST be ignored.</t>		is received while in an overwhelmed state, it <bcp14>MUST</bcp14> be ignored.
			</t>
	<t><list style="symbols"><t>When a PCEP speaker is overwhelmed, it		<ul spacing="normal" bare="false" empty="false" pn="section-5.7-4">
	SHOULD notify its peer by sending a PCNtf message with		<li pn="section-5.7-4.1">When a PCEP speaker is overwhelmed, it
	Notification-Type = TBD3 (Auto-bandwidth Overwhelm State) and		<bcp14>SHOULD</bcp14> notify its peer by sending a PCNtf message with
	Notification-Value = 1 (Entering auto-bandwidth overwhelm state).		Notification-type = 5 (Auto-Bandwidth Overwhelm State) and
	Optionally, OVERLOADED-DURATION TLV <xref target="RFC5440"/> MAY be		Notification-value = 1 (Entering Auto-Bandwidth Overwhelm State).
	included that specifies the time period during which no further PCEP		Optionally, an OVERLOADED-DURATION TLV <xref target="RFC5440" format="def
	messages related to auto-bandwidth adjustment should be sent.</t>		ault" sectionFormat="of" derivedContent="RFC5440"/> <bcp14>MAY</bcp14> be
			included to specify the time period during which no further PCEP
	<t>When the PCEP speaker is no longer in the overwhelm state and is		messages related to auto-bandwidth adjustment should be sent.</li>
	available to process the auto-bandwidth adjustments, it SHOULD		<li pn="section-5.7-4.2">When the PCEP speaker is no longer in the ove
	notify its peers by sending a PCNtf message with Notification Type		rwhelm state and is
	= TBD3 (Auto-bandwidth Overwhelm State) and Notification Value = 2		available to process the auto-bandwidth adjustments, it <bcp14>SHOULD</bcp
	(Clearing auto-bandwidth overwhelm state). A PCEP speaker SHOULD		14>
	send such notification to all peers to with a Notification message		notify its peers by sending a PCNtf message with Notification-type
	(Notification-Type=TBD3, Notification-Value=1) was sent earlier		= 5 (Auto-Bandwidth Overwhelm State) and Notification-value = 2
	unless an OVERLOADED-DURATION TLV was included and the PCEP		(Clearing Auto-Bandwidth Overwhelm State). A PCEP speaker <bcp14>SHOULD</b
			cp14>
			send such notification to all peers if a Notification message
			(Notification-type = 5, Notification-value = 1) was sent earlier.
			This message is not sent if an OVERLOADED-DURATION TLV was included and th
			e PCEP
	speakers wishes for the peer to wait for the expiration of that		speakers wishes for the peer to wait for the expiration of that
	period of time before receiving further PCEP messages related to		period of time before receiving further PCEP messages related to
	auto-bandwidth adjustment.</t>		auto-bandwidth adjustment.</li>
			</ul>
	</list>		<t pn="section-5.7-5">
	</t>		When the auto-bandwidth feature is deployed, a PCE can send this
			notification to a PCC when it reports frequent auto-bandwidth
	<t>		adjustments. If a PCC is overwhelmed with resignaling, it can also
	When Auto-Bandwidth feature is deployed, a PCE can send this		notify the PCE to not adjust the LSP bandwidth while in the overwhelm
	notification to PCC when a PCC is reporting frequent auto-bandwidth
	adjustments. If a PCC is overwhelmed with re-signaling, it can also
	notify the PCE to not adjust the LSP bandwidth while in overwhelm
	state.</t>		state.</t>
			<t pn="section-5.7-6">
	<t>		Some dampening notification procedure (as per <xref target="RFC5440" format="
	Some dampening notification procedure (as per <xref target="RFC5440"/>) to av		default" sectionFormat="of" derivedContent="RFC5440"/>) to avoid
	oid		oscillations of the overwhelm state is <bcp14>RECOMMENDED</bcp14>. On receipt
	oscillations of the overwhelm state is RECOMMENDED. On receipt of an		of an
	auto-bandwidth overwhelm notification from the PCE, a PCC should		auto-bandwidth overwhelm notification from the PCE, a PCC should
	consider the impact on the entire network. Moving the delegations of		consider the impact on the entire network. Moving the delegations of
	auto-bandwidth enabled LSP to another PCE could cause further		auto-bandwidth-enabled LSPs to another PCE could cause further
	overloading.</t>		overloading.</t>
			</section>
	</section>		</section>
			<section anchor="sect-6" numbered="true" toc="include" removeInRFC="false" p
	</section>		n="section-6">
			<name slugifiedName="name-manageability-consideration">Manageability Consi
	<section title="Manageability Considerations" anchor="sect-6"><section ti		derations</name>
	tle="Control of Function and Policy" anchor="sect-6.1"><t>		<section anchor="sect-6.1" numbered="true" toc="include" removeInRFC="fals
	The Auto-Bandwidth feature SHOULD be controlled per LSP (at PCC		e" pn="section-6.1">
	(head-end of the LSP) or PCE) and the values for auto-bandwidth		<name slugifiedName="name-control-of-function-and-pol">Control of Functi
	parameters e.g. sample-interval, adjustment-interval (up/down),		on and Policy</name>
	minimum-bandwidth, maximum-bandwidth, adjustment-threshold (up/down)		<t pn="section-6.1-1">
	SHOULD be configurable by an operator.</t>		The auto-bandwidth feature <bcp14>SHOULD</bcp14> be controlled on a per-LSP
			basis (at
	<t>		the PCC
	The Maximum-Bandwidth (and Minimum-Bandwidth) should be set to		(head-end of the LSP) or PCE), and the values for auto-bandwidth
	acceptable limit to avoid impact on the rest of the MPLS-TE domain.</t>		parameters, e.g., Sample-Interval, Adjustment-Interval (up/down),
			Minimum-Bandwidth, Maximum-Bandwidth, and Adjustment-Threshold (up/down),
	<t>		<bcp14>SHOULD</bcp14> be configurable by an operator.</t>
			<t pn="section-6.1-2">
			The Maximum-Bandwidth (and Minimum-Bandwidth) should be set to an
			acceptable limit to avoid having an impact on the rest of the MPLS-TE dom
			ain.</t>
			<t pn="section-6.1-3">
	The operator should make sure that the Overflow-Threshold is greater		The operator should make sure that the Overflow-Threshold is greater
	than or at least equal to the Up-Adjustment-Threshold. And similarly,		than or at least equal to the Up-Adjustment-Threshold. And similarly,
	make sure that the Underflow-Threshold is greater than or at least		it is important to ensure that the Underflow-Threshold is greater than or at least
	equal to the Down-Adjustment-Threshold.</t>		equal to the Down-Adjustment-Threshold.</t>
			</section>
	</section>		<section anchor="sect-6.2" numbered="true" toc="include" removeInRFC="fals
			e" pn="section-6.2">
	<section title="Information and Data Models" anchor="sect-6.2"><t>		<name slugifiedName="name-information-and-data-models">Information and D
	A MIB module for gathering operational information about PCEP is		ata Models</name>
	defined in <xref target="RFC7420"/>. Additionally, the YANG module defined i		<t pn="section-6.2-1">
	n		A MIB module for gathering operational information about the PCEP is
	<xref target="I-D.ietf-pce-pcep-yang"/> provides for both configuration of PC		defined in <xref target="RFC7420" format="default" sectionFormat="of" derived
	EP as		Content="RFC7420"/>. Additionally, the YANG module defined in
			<xref target="I-D.ietf-pce-pcep-yang" format="default" sectionFormat="of" der
			ivedContent="PCE-PCEP-YANG"/> provides both configuration of PCEP as
	well as operational management. These could be enhanced to provide		well as operational management. These could be enhanced to provide
	controls and indicators for support of auto-bandwidth feature.		controls and indicators for support of the auto-bandwidth feature.
	Support for various configuration knobs as well as counters of		Support for various configuration knobs as well as counters of
	messages sent/received containing the TLVs defined in this document		messages sent/received containing the TLVs defined in this document
	could be added.</t>		could be added.</t>
			</section>
	</section>		<section anchor="sect-6.3" numbered="true" toc="include" removeInRFC="fals
			e" pn="section-6.3">
	<section title="Liveness Detection and Monitoring" anchor="sect-6.3"><t>		<name slugifiedName="name-liveness-detection-and-moni">Liveness Detectio
			n and Monitoring</name>
			<t pn="section-6.3-1">
	The mechanisms defined in this document do not imply any new liveness		The mechanisms defined in this document do not imply any new liveness
	detection and monitoring requirements in addition to those already		detection and monitoring requirements in addition to those already
	listed in <xref target="RFC5440"/>.</t>		listed in <xref target="RFC5440" format="default" sectionFormat="of" derivedC
			ontent="RFC5440"/>.</t>
	</section>		</section>
			<section anchor="sect-6.4" numbered="true" toc="include" removeInRFC="fals
	<section title="Verify Correct Operations" anchor="sect-6.4"><t>		e" pn="section-6.4">
			<name slugifiedName="name-verifying-correct-operation">Verifying Correct
			Operations</name>
			<t pn="section-6.4-1">
	The mechanisms defined in this document do not imply any new		The mechanisms defined in this document do not imply any new
	operation verification requirements in addition to those already		operation verification requirements in addition to those already
	listed in <xref target="RFC5440"/>.</t>		listed in <xref target="RFC5440" format="default" sectionFormat="of" derivedC
			ontent="RFC5440"/>.</t>
	<t>		<t pn="section-6.4-2">
	In case of an invalid value, the Sub-TLV would get ignored and the		In the case in which an invalid value is present, the sub-TLV would get ignor
	previous value would be maintained. In such case the implementation		ed and the
	SHOULD log the event.</t>		previous value will be maintained. In such a case, the implementation
			<bcp14>SHOULD</bcp14> log the event.</t>
	</section>		</section>
			<section anchor="sect-6.5" numbered="true" toc="include" removeInRFC="fals
	<section title="Requirements On Other Protocols" anchor="sect-6.5"><t>		e" pn="section-6.5">
			<name slugifiedName="name-requirements-for-other-prot">Requirements for
			Other Protocols</name>
			<t pn="section-6.5-1">
	The mechanisms defined in this document do not add any new		The mechanisms defined in this document do not add any new
	requirements on other protocols.</t>		requirements for other protocols.</t>
			</section>
	</section>		<section anchor="sect-6.6" numbered="true" toc="include" removeInRFC="fals
			e" pn="section-6.6">
	<section title="Impact On Network Operations" anchor="sect-6.6"><t>		<name slugifiedName="name-impact-on-network-operation">Impact on Network
			Operations</name>
			<t pn="section-6.6-1">
	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 <bcp14>SHOULD</bcp14> allow a limit to be placed on the number
	LSPs that can be enabled with auto-bandwidth feature. For each LSP		of
	enabled with auto-bandwidth feature there is an extra load on PCC, as		LSPs that can be enabled with the auto-bandwidth feature. For each LSP
			enabled with the auto-bandwidth feature, there is an extra load on the PCC, a
			s
	it needs to monitor the traffic and report the calculated bandwidth		it needs to monitor the traffic and report the calculated bandwidth
	to be adjusted to the PCE. The PCE further re-compute paths based on		to be adjusted to the PCE. The PCE further recomputes paths based on
	the requested bandwidth and update the path to the PCC, which in		the requested bandwidth and updates the path to the PCC, which, in
	turns triggers the re-signaling of the path. All these steps adds		turn, triggers the resignaling of the path. All these steps add
	extra load and churn in the network and thus operator needs to take		extra load and churn in the network; thus, the operator needs to take
	due care while enabling this features on a number of LSPs.</t>		due care while enabling these features on a number of LSPs.</t>
			<t pn="section-6.6-2">
	<t>		An implementation <bcp14>MAY</bcp14> allow a limit to be placed on the rate o
	An implementation MAY allow a limit to be placed on the rate of		f
	auto-bandwidth related messages sent by a PCEP speaker and received by a		auto-bandwidth-related messages sent by a PCEP speaker and received by a
	peer. An implementation SHOULD also allow sending a notification when a		peer. An implementation <bcp14>SHOULD</bcp14> also allow notifications to
	PCEP speaker is overwhelmed or the rate of messages reach a threshold.</t>		be sent when a PCEP speaker is overwhelmed or when the rate of messages
			reaches a threshold.</t>
	<t>		<t pn="section-6.6-3">
	Due care is required by the operator if a Sample-Interval value		Due care is required by the operator if a Sample-Interval value
	significantly smaller than the default (5 minute) is used, as a small		significantly smaller than the default (5 minutes) is used, as small
	Sample-Interval values, e.g., 1 minute or less, could cause		Sample-Interval values, e.g., 1 minute or less, could cause
	undesirable interactions with transport protocols. These undesirable		undesirable interactions with transport protocols. These undesirable
	interactions result from providing insufficient time for transport		interactions result from providing insufficient time for transport
	protocol reactions to a prior bandwidth adjustment to settle out		protocol reactions to a prior bandwidth adjustment to settle down
	before bandwidth samples are taken for the next bandwidth adjustment.</t>		before Bandwidth-Samples are taken for the next bandwidth adjustment.</t>
			</section>
	</section>		</section>
			<section anchor="sect-7" numbered="true" toc="include" removeInRFC="false" p
	</section>		n="section-7">
			<name slugifiedName="name-security-considerations">Security Considerations
	<section title="Security Considerations" anchor="sect-7"><t> This		</name>
			<t pn="section-7-1"> This
	document defines AUTO-BANDWIDTH-CAPABILITY TLV and		document defines AUTO-BANDWIDTH-CAPABILITY TLV and
	AUTO-BANDWIDTH-ATTRIBUTES sub-TLVs which do not add any substantial		AUTO-BANDWIDTH-ATTRIBUTES sub-TLVs, which do not add any substantial
	new security concerns beyond those already discussed in <xref		new security concerns beyond those already discussed in <xref target="RFC
	target="RFC8231"/> and <xref target="RFC8281"/> for stateful PCE		8231" format="default" sectionFormat="of" derivedContent="RFC8231"/> and <xref t
	operations. As per <xref target="RFC8231"/>, it is RECOMMENDED that		arget="RFC8281" format="default" sectionFormat="of" derivedContent="RFC8281"/> f
			or stateful PCE
			operations. As per <xref target="RFC8231" format="default" sectionFormat
			="of" derivedContent="RFC8231"/>, it is <bcp14>RECOMMENDED</bcp14> that
	these PCEP extensions only be activated on authenticated and encrypted		these PCEP extensions only be activated on authenticated and encrypted
	sessions across PCEs and PCCs belonging to the same administrative		sessions across PCEs and PCCs belonging to the same administrative
	authority, using Transport Layer Security (TLS) <xref		authority, using Transport Layer Security (TLS) <xref target="RFC8253" fo
	target="RFC8253"/>, as per the recommendations and best current		rmat="default" sectionFormat="of" derivedContent="RFC8253"/>, as per the recomme
	practices in BCP 195 <xref target="RFC7525"/> (unless explicitly set		ndations and best current
	aside in <xref target="RFC8253"/>).</t>		practices in BCP 195 <xref target="RFC7525" format="default" sectionForma
			t="of" derivedContent="RFC7525"/> (unless explicitly set
	<t>		aside in <xref target="RFC8253" format="default" sectionFormat="of" deriv
			edContent="RFC8253"/>).</t>
			<t pn="section-7-2">
	Incorrect auto-bandwidth parameters in the AUTO-BANDWIDTH-ATTRIBUTES		Incorrect auto-bandwidth parameters in the AUTO-BANDWIDTH-ATTRIBUTES
	sub-TLVs could have an adverse effect on the LSP as well as on the		sub-TLVs could have an adverse effect on the LSP as well as on the
	network.</t>		network.</t>
			</section>
	</section>		<section anchor="sect-8" numbered="true" toc="include" removeInRFC="false" p
			n="section-8">
	<section title="IANA Considerations" anchor="sect-8"><section title="PCEP		<name slugifiedName="name-iana-considerations">IANA Considerations</name>
	TLV Type Indicators" anchor="sect-8.1"><t>		<section anchor="sect-8.1" numbered="true" toc="include" removeInRFC="fals
	This document defines the following new PCEP TLVs; IANA is requested		e" pn="section-8.1">
	to make the following allocations from the "PCEP TLV Type Indicators"		<name slugifiedName="name-pcep-tlv-type-indicators">PCEP TLV Type Indica
	sub-registry of the PCEP Numbers registry, as follows:</t>		tors</name>
			<t pn="section-8.1-1">
	<figure><artwork><![CDATA[		This document defines the following new PCEP TLVs; IANA has made
	Value Name Reference		the following allocations from the "PCEP TLV Type Indicators"
	TBD2 AUTO-BANDWIDTH-CAPABILITY [This document]		subregistry of the "Path Computation Element Protocol (PCEP) Numbers" registr
	TBD1 AUTO-BANDWIDTH-ATTRIBUTES [This document]		y as follows:</t>
	]]></artwork>		<table anchor="pcep-tlv" align="left" pn="table-3">
	</figure>		<name slugifiedName="name-pcep-tlv-type-indicators-2">PCEP TLV Type In
	</section>		dicators</name>
			<thead>
	<section title="AUTO-BANDWIDTH-CAPABILITY TLV Flag Field" anchor="sect-8.		<tr>
	2"><t>		<th align="left" colspan="1" rowspan="1">Value</th>
	IANA is requested to create a sub-registry to manage the Flag field		<th align="left" colspan="1" rowspan="1">Description</th>
			<th align="left" colspan="1" rowspan="1">Reference</th>
			</tr>
			</thead>
			<tbody>
			<tr>
			<td align="left" colspan="1" rowspan="1">36</td>
			<td align="left" colspan="1" rowspan="1">AUTO-BANDWIDTH-CAPABILITY
			</td>
			<td align="left" colspan="1" rowspan="1">[RFC8733]</td>
			</tr>
			<tr>
			<td align="left" colspan="1" rowspan="1">37</td>
			<td align="left" colspan="1" rowspan="1">AUTO-BANDWIDTH-ATTRIBUTES
			</td>
			<td align="left" colspan="1" rowspan="1">[RFC8733]</td>
			</tr>
			</tbody>
			</table>
			</section>
			<section anchor="sect-8.2" numbered="true" toc="include" removeInRFC="fals
			e" pn="section-8.2">
			<name slugifiedName="name-auto-bandwidth-capability-tlv">AUTO-BANDWIDTH-
			CAPABILITY TLV Flag Field</name>
			<t pn="section-8.2-1">
			IANA has created a subregistry to manage the Flag field
	of the AUTO-BANDWIDTH-CAPABILITY TLV within the "Path Computation Element Pro tocol (PCEP) Numbers" registry.</t>		of the AUTO-BANDWIDTH-CAPABILITY TLV within the "Path Computation Element Pro tocol (PCEP) Numbers" registry.</t>
			<t pn="section-8.2-2">
	<t>		New bit numbers are to be assigned by Standards Action <xref target="RFC8126"
	New bit numbers are to be assigned by Standards Action <xref target="RFC8126"		format="default" sectionFormat="of" derivedContent="RFC8126"/>.
	/>.
	Each bit should be tracked with the following qualities:</t>		Each bit should be tracked with the following qualities:</t>
			<ul spacing="normal" bare="false" empty="false" pn="section-8.2-3">
	<t><list style="symbols"><t>Bit number (counting from bit 0 as the most s		<li pn="section-8.2-3.1">Bit number (counting from bit 0 as the most s
	ignificant bit)</t>		ignificant bit)</li>
			<li pn="section-8.2-3.2">Capability description</li>
	<t>Capability description</t>		<li pn="section-8.2-3.3">Defining RFC</li>
			</ul>
	<t>Defining RFC</t>		<t pn="section-8.2-4">
			The initial contents of the subregistry are empty, with all bits
	</list>		marked unassigned.</t>
	</t>		</section>
			<section anchor="sect-8.3" numbered="true" toc="include" removeInRFC="fals
	<t>		e" pn="section-8.3">
	The initial contents of the sub-registry are empty, with all bits		<name slugifiedName="name-auto-bandwidth-attributes-s">AUTO-BANDWIDTH-AT
	marked unassigned</t>		TRIBUTES Sub-TLV</name>
			<t pn="section-8.3-1">
	</section>		This document specifies the AUTO-BANDWIDTH-ATTRIBUTES sub-TLVs. IANA
			has created an "AUTO-BANDWIDTH-ATTRIBUTES Sub-TLV Types"
	<section title="AUTO-BANDWIDTH-ATTRIBUTES Sub-TLV" anchor="sect-8.3"><t>		subregistry within the "Path Computation Element Protocol (PCEP) Numbers" reg
	This document specifies the AUTO-BANDWIDTH-ATTRIBUTES Sub-TLVs. IANA		istry to manage the type indicator space for sub-TLVs of
	is requested to create an "AUTO-BANDWIDTH-ATTRIBUTES Sub-TLV Types"
	sub-registry within the "Path Computation Element Protocol (PCEP) Numbers" re
	gistry to manage the type indicator space for sub-TLVs of
	the AUTO-BANDWIDTH-ATTRIBUTES TLV. The valid range of values in the		the AUTO-BANDWIDTH-ATTRIBUTES TLV. The valid range of values in the
	registry is 0-65535. IANA is requested to initialize the registry		registry is 0-65535. IANA has initialized the registry
	with the following values. All other values in the registry should		with the following values. All other values in the registry should
	be marked as "Unassigned".</t>		be marked as "Unassigned".</t>
			<t pn="section-8.3-2">
	<t>		IANA has set the Registration Procedure for this registry
	IANA is requested to set the registration procedure for this registry
	to read as follows:</t>		to read as follows:</t>
			<table anchor="registration" align="left" pn="table-4">
	<figure><artwork><![CDATA[		<name slugifiedName="name-registration-procedure-for-">Registration Pr
			ocedure for the "AUTO-BANDWIDTH-ATTRIBUTES Sub-TLV" Registry</name>
	0-65503 IETF Review		<thead>
			<tr>
	65504-65535 Experimental Use		<th align="left" colspan="1" rowspan="1">Range</th>
			<th align="left" colspan="1" rowspan="1">Registration Procedure</t
			h>
			</tr>
			</thead>
			<tbody>
			<tr>
			<td align="left" colspan="1" rowspan="1">0-65503</td>
			<td align="left" colspan="1" rowspan="1">IETF Review</td>
			</tr>
			<tr>
			<td align="left" colspan="1" rowspan="1">65504-65535</td>
			<td align="left" colspan="1" rowspan="1">Experimental Use</td>
			</tr>
			</tbody>
			</table>
			<t pn="section-8.3-4">
	This document defines the following types:		This document defines the following types:
			</t>
	Type Name Reference		<table anchor="registry" align="left" pn="table-5">
	0 Reserved [This document]		<name slugifiedName="name-initial-contents-of-the-aut">Initial Content
	1 Sample-Interval sub-TLV [This document]		s of the "AUTO-BANDWIDTH-ATTRIBUTES Sub-TLV" Registry</name>
	2 Adjustment-Interval sub-TLV [This document]		<thead>
	3 Down-Adjustment-Interval sub-TLV [This document]		<tr>
	4 Adjustment-Threshold sub-TLV [This document]		<th align="left" colspan="1" rowspan="1">Type</th>
	5 Adjustment-Threshold-Percentage sub-TLV [This document]		<th align="left" colspan="1" rowspan="1">Name</th>
	6 Down-Adjustment-Threshold sub-TLV [This document]		<th align="left" colspan="1" rowspan="1">Reference</th>
	7 Down-Adjustment-Threshold-Percentage sub-TLV [This document]		</tr>
	8 Minimum-Bandwidth sub-TLV [This document]		</thead>
	9 Maximum-Bandwidth sub-TLV [This document]		<tbody>
	10 Overflow-Threshold sub-TLV [This document]		<tr>
	11 Overflow-Threshold-Percentage sub-TLV [This document]		<td align="left" colspan="1" rowspan="1">0</td>
	12 Underflow-Threshold sub-TLV [This document]		<td align="left" colspan="1" rowspan="1">Reserved</td>
	13 Underflow-Threshold-Percentage sub-TLV [This document]		<td align="left" colspan="1" rowspan="1">[RFC8733]</td>
	14- Unassigned [This document]		</tr>
	65503		<tr>
	]]></artwork>		<td align="left" colspan="1" rowspan="1">1</td>
	</figure>		<td align="left" colspan="1" rowspan="1">Sample-Interval </td>
	</section>		<td align="left" colspan="1" rowspan="1">[RFC8733]</td>
			</tr>
	<section title="Error Object" anchor="sect-8.4"><t> This document		<tr>
	defines a new Error-Value for PCErr message of Error-Type 19 (Invalid		<td align="left" colspan="1" rowspan="1">2</td>
	Operation) <xref target="RFC8231"/>. IANA is requested to allocate		<td align="left" colspan="1" rowspan="1">Adjustment-Interval </td>
	new error-value within the "PCEP-ERROR Object Error Types and Values"		<td align="left" colspan="1" rowspan="1">[RFC8733]</td>
	subregistry of the PCEP Numbers registry, as follows:</t>		</tr>
			<tr>
	<figure><artwork><![CDATA[		<td align="left" colspan="1" rowspan="1">3</td>
	Error-Type Meaning & error values Reference		<td align="left" colspan="1" rowspan="1">Down-Adjustment-Interval<
	19 Invalid Operations		/td>
			<td align="left" colspan="1" rowspan="1">[RFC8733]</td>
	Error-Value = TBD4: [This document]		</tr>
	Auto-Bandwidth Capability		<tr>
	was not Advertised		<td align="left" colspan="1" rowspan="1">4</td>
	]]></artwork>		<td align="left" colspan="1" rowspan="1">Adjustment-Threshold </td
	</figure>		>
	</section>		<td align="left" colspan="1" rowspan="1">[RFC8733]</td>
			</tr>
	<section title="Notification Object" anchor="sect-8.5"><t>		<tr>
	IANA is requested to allocate new Notification Type and Notification		<td align="left" colspan="1" rowspan="1">5</td>
	Values within the "Notification Object" sub-registry of the PCEP		<td align="left" colspan="1" rowspan="1">Adjustment-Threshold-Perc
	Numbers registry, as follows:</t>		entage </td>
			<td align="left" colspan="1" rowspan="1">[RFC8733]</td>
	<figure><artwork><![CDATA[		</tr>
	Type Meaning Reference		<tr>
	TBD3 Auto-Bandwidth Overwhelm State [This document]		<td align="left" colspan="1" rowspan="1">6</td>
			<td align="left" colspan="1" rowspan="1">Down-Adjustment-Threshold
	Notification-value=1: Entering Auto-Bandwidth		</td>
	overwhelm state		<td align="left" colspan="1" rowspan="1">[RFC8733]</td>
	Notification-value=2: Clearing Auto-Bandwidth		</tr>
	overwhelm state		<tr>
	]]></artwork>		<td align="left" colspan="1" rowspan="1">7</td>
	</figure>		<td align="left" colspan="1" rowspan="1">Down-Adjustment-Threshold
	</section>		-Percentage </td>
			<td align="left" colspan="1" rowspan="1">[RFC8733]</td>
	</section>		</tr>
			<tr>
	</middle>		<td align="left" colspan="1" rowspan="1">8</td>
			<td align="left" colspan="1" rowspan="1">Minimum-Bandwidth </td>
	<back>		<td align="left" colspan="1" rowspan="1">[RFC8733]</td>
	<references title="Normative References">		</tr>
	&RFC2119;		<tr>
	&RFC5440;		<td align="left" colspan="1" rowspan="1">9</td>
	&RFC7525;		<td align="left" colspan="1" rowspan="1">Maximum-Bandwidth </td>
	&RFC8126;		<td align="left" colspan="1" rowspan="1">[RFC8733]</td>
	&RFC8174;		</tr>
	&RFC8231;		<tr>
	&RFC8253;		<td align="left" colspan="1" rowspan="1">10</td>
	&RFC8281;		<td align="left" colspan="1" rowspan="1">Overflow-Threshold </td>
	<reference anchor="IEEE.754.1985"><front>		<td align="left" colspan="1" rowspan="1">[RFC8733]</td>
	<title>Standard for Binary Floating-Point Arithmetic</title>		</tr>
	<author>		<tr>
	<organization>Institute of Electrical and Electronics Engineers</organiza		<td align="left" colspan="1" rowspan="1">11</td>
	tion>		<td align="left" colspan="1" rowspan="1">Overflow-Threshold-Percen
	</author>		tage </td>
			<td align="left" colspan="1" rowspan="1">[RFC8733]</td>
	<date month="August" year="1985"/>		</tr>
	</front>		<tr>
			<td align="left" colspan="1" rowspan="1">12</td>
	<seriesInfo name="IEEE" value="Standard 754"/>		<td align="left" colspan="1" rowspan="1">Underflow-Threshold </td>
	</reference>		<td align="left" colspan="1" rowspan="1">[RFC8733]</td>
	</references>		</tr>
	<references title="Informative References">		<tr>
	&RFC3209;		<td align="left" colspan="1" rowspan="1">13</td>
	&RFC3471;		<td align="left" colspan="1" rowspan="1">Underflow-Threshold-Perce
	&RFC7420;		ntage</td>
	&RFC8051;		<td align="left" colspan="1" rowspan="1">[RFC8733]</td>
	&I-D.ietf-pce-pcep-yang;		</tr>
	</references>		<tr>
	<section title="Acknowledgments" numbered="no" anchor="acknowledgments"><		<td align="left" colspan="1" rowspan="1">14-65503</td>
	t>		<td align="left" colspan="1" rowspan="1">Unassigned</td>
	Authors would like to thank Robert Varga, Venugopal Reddy, Reeja		<td align="left" colspan="1" rowspan="1">[RFC8733]</td>
	Paul, Sandeep Boina, Avantika, JP Vasseur, Himanshu Shah, Jonathan		</tr>
	Hardwick and Adrian Farrel for their useful comments and suggestions.</t>		</tbody>
			</table>
	<t>		</section>
	Thanks to Daniel Franke, Joe Clarke, David Black, and Erik Kline for		<section anchor="sect-8.4" numbered="true" toc="include" removeInRFC="fals
			e" pn="section-8.4">
			<name slugifiedName="name-error-object">Error Object</name>
			<t pn="section-8.4-1"> This document
			defines a new Error-value for PCErr message of Error-Type 19 (Invalid
			Operation) <xref target="RFC8231" format="default" sectionFormat="of" der
			ivedContent="RFC8231"/>. IANA has allocated
			a new Error-value within the "PCEP-ERROR Object Error Types and Values"
			subregistry of the "Path Computation Element Protocol (PCEP) Numbers" reg
			istry as follows:</t>
			<table anchor="PCEP-registry" align="left" pn="table-6">
			<name slugifiedName="name-addition-to-the-pcep-error-">Addition to the
			"PCEP-ERROR Object Error Types and
			Values" Registry</name>
			<thead>
			<tr>
			<th align="left" colspan="1" rowspan="1">Error-Type</th>
			<th align="left" colspan="1" rowspan="1">Meaning</th>
			<th align="left" colspan="1" rowspan="1">Error-value</th>
			<th align="left" colspan="1" rowspan="1">Reference</th>
			</tr>
			</thead>
			<tbody>
			<tr>
			<td align="left" colspan="1" rowspan="1">19</td>
			<td align="left" colspan="1" rowspan="1">Invalid Operation</td>
			<td align="left" colspan="1" rowspan="1">14: Auto-Bandwidth capabi
			lity was not
			advertised</td>
			<td align="left" colspan="1" rowspan="1">[RFC8733]</td>
			</tr>
			</tbody>
			</table>
			</section>
			<section anchor="sect-8.5" numbered="true" toc="include" removeInRFC="fals
			e" pn="section-8.5">
			<name slugifiedName="name-notification-object">Notification Object</name
			>
			<t pn="section-8.5-1">
			IANA has allocated a new Notification-type and Notification-values within the
			"Notification Object" subregistry of the "Path
			Computation Element Protocol (PCEP)
			Numbers" registry as follows:</t>
			<table anchor="notification-object" align="left" pn="table-7">
			<name slugifiedName="name-additions-to-the-notificati">Additions to th
			e "Notification Object" Registry</name>
			<thead>
			<tr>
			<th align="left" colspan="1" rowspan="1">Notification-type</th>
			<th align="left" colspan="1" rowspan="1">Name</th>
			<th align="left" colspan="1" rowspan="1">Notification-value</th>
			<th align="left" colspan="1" rowspan="1">Reference</th>
			</tr>
			</thead>
			<tbody>
			<tr>
			<td align="left" colspan="1" rowspan="1">5</td>
			<td align="left" colspan="1" rowspan="1">Auto-Bandwidth Overwhelm
			State</td>
			<td align="left" colspan="1" rowspan="1">0: Unassigned</td>
			<td align="left" colspan="1" rowspan="1">[RFC8733]</td>
			</tr>
			<tr>
			<td align="left" colspan="1" rowspan="1"/>
			<td align="left" colspan="1" rowspan="1"/>
			<td align="left" colspan="1" rowspan="1">1: Entering Auto-Bandwidt
			h Overwhelm State</td>
			<td align="left" colspan="1" rowspan="1">[RFC8733]</td>
			</tr>
			<tr>
			<td align="left" colspan="1" rowspan="1"/>
			<td align="left" colspan="1" rowspan="1"/>
			<td align="left" colspan="1" rowspan="1">2: Clearing Auto-Bandwidt
			h Overwhelm State</td>
			<td align="left" colspan="1" rowspan="1">[RFC8733]</td>
			</tr>
			</tbody>
			</table>
			</section>
			</section>
			</middle>
			<back>
			<displayreference target="I-D.ietf-pce-pcep-yang" to="PCE-PCEP-YANG"/>
			<references pn="section-9">
			<name slugifiedName="name-references">References</name>
			<references pn="section-9.1">
			<name slugifiedName="name-normative-references">Normative References</na
			me>
			<reference anchor="IEEE.754.1985" quoteTitle="true" target="https://doi.
			org/10.1109/IEEESTD.1985.82928" derivedAnchor="IEEE.754.1985">
			<front>
			<title>Standard for Binary Floating-Point Arithmetic</title>
			<seriesInfo name="DOI" value="10.1109/IEEESTD.1985.82928"/>
			<seriesInfo name="IEEE" value="Standard 754"/>
			<author>
			<organization showOnFrontPage="true">IEEE</organization>
			</author>
			<date month="October" year="1985"/>
			</front>
			</reference>
			<reference anchor="RFC2119" target="https://www.rfc-editor.org/info/rfc2
			119" quoteTitle="true" derivedAnchor="RFC2119">
			<front>
			<title>Key words for use in RFCs to Indicate Requirement Levels</tit
			le>
			<author initials="S." surname="Bradner" fullname="S. Bradner">
			<organization showOnFrontPage="true"/>
			</author>
			<date year="1997" month="March"/>
			<abstract>
			<t>In many standards track documents several words are used to sig
			nify the requirements in the specification. These words are often capitalized.
			This document defines these words as they should be interpreted in IETF document
			s. This document specifies an Internet Best Current Practices for the Internet
			Community, and requests discussion and suggestions for improvements.</t>
			</abstract>
			</front>
			<seriesInfo name="BCP" value="14"/>
			<seriesInfo name="RFC" value="2119"/>
			<seriesInfo name="DOI" value="10.17487/RFC2119"/>
			</reference>
			<reference anchor="RFC5440" target="https://www.rfc-editor.org/info/rfc5
			440" quoteTitle="true" derivedAnchor="RFC5440">
			<front>
			<title>Path Computation Element (PCE) Communication Protocol (PCEP)<
			/title>
			<author initials="JP." surname="Vasseur" fullname="JP. Vasseur" role
			="editor">
			<organization showOnFrontPage="true"/>
			</author>
			<author initials="JL." surname="Le Roux" fullname="JL. Le Roux" role
			="editor">
			<organization showOnFrontPage="true"/>
			</author>
			<date year="2009" month="March"/>
			<abstract>
			<t>This document specifies the Path Computation Element (PCE) Comm
			unication Protocol (PCEP) for communications between a Path Computation Client (
			PCC) and a PCE, or between two PCEs. Such interactions include path computation
			requests and path computation replies as well as notifications of specific stat
			es related to the use of a PCE in the context of Multiprotocol Label Switching (
			MPLS) and Generalized MPLS (GMPLS) Traffic Engineering. PCEP is designed to be
			flexible and extensible so as to easily allow for the addition of further messag
			es and objects, should further requirements be expressed in the future. [STANDA
			RDS-TRACK]</t>
			</abstract>
			</front>
			<seriesInfo name="RFC" value="5440"/>
			<seriesInfo name="DOI" value="10.17487/RFC5440"/>
			</reference>
			<reference anchor="RFC7525" target="https://www.rfc-editor.org/info/rfc7
			525" quoteTitle="true" derivedAnchor="RFC7525">
			<front>
			<title>Recommendations for Secure Use of Transport Layer Security (T
			LS) and Datagram Transport Layer Security (DTLS)</title>
			<author initials="Y." surname="Sheffer" fullname="Y. Sheffer">
			<organization showOnFrontPage="true"/>
			</author>
			<author initials="R." surname="Holz" fullname="R. Holz">
			<organization showOnFrontPage="true"/>
			</author>
			<author initials="P." surname="Saint-Andre" fullname="P. Saint-Andre
			">
			<organization showOnFrontPage="true"/>
			</author>
			<date year="2015" month="May"/>
			<abstract>
			<t>Transport Layer Security (TLS) and Datagram Transport Layer Sec
			urity (DTLS) are widely used to protect data exchanged over application protocol
			s such as HTTP, SMTP, IMAP, POP, SIP, and XMPP. Over the last few years, severa
			l serious attacks on TLS have emerged, including attacks on its most commonly us
			ed cipher suites and their modes of operation. This document provides recommend
			ations for improving the security of deployed services that use TLS and DTLS. Th
			e recommendations are applicable to the majority of use cases.</t>
			</abstract>
			</front>
			<seriesInfo name="BCP" value="195"/>
			<seriesInfo name="RFC" value="7525"/>
			<seriesInfo name="DOI" value="10.17487/RFC7525"/>
			</reference>
			<reference anchor="RFC8126" target="https://www.rfc-editor.org/info/rfc8
			126" quoteTitle="true" derivedAnchor="RFC8126">
			<front>
			<title>Guidelines for Writing an IANA Considerations Section in RFCs
			</title>
			<author initials="M." surname="Cotton" fullname="M. Cotton">
			<organization showOnFrontPage="true"/>
			</author>
			<author initials="B." surname="Leiba" fullname="B. Leiba">
			<organization showOnFrontPage="true"/>
			</author>
			<author initials="T." surname="Narten" fullname="T. Narten">
			<organization showOnFrontPage="true"/>
			</author>
			<date year="2017" month="June"/>
			<abstract>
			<t>Many protocols make use of points of extensibility that use con
			stants to identify various protocol parameters. To ensure that the values in th
			ese fields do not have conflicting uses and to promote interoperability, their a
			llocations are often coordinated by a central record keeper. For IETF protocols
			, that role is filled by the Internet Assigned Numbers Authority (IANA).</t>
			<t>To make assignments in a given registry prudently, guidance des
			cribing the conditions under which new values should be assigned, as well as whe
			n and how modifications to existing values can be made, is needed. This documen
			t defines a framework for the documentation of these guidelines by specification
			authors, in order to assure that the provided guidance for the IANA Considerati
			ons is clear and addresses the various issues that are likely in the operation o
			f a registry.</t>
			<t>This is the third edition of this document; it obsoletes RFC 52
			26.</t>
			</abstract>
			</front>
			<seriesInfo name="BCP" value="26"/>
			<seriesInfo name="RFC" value="8126"/>
			<seriesInfo name="DOI" value="10.17487/RFC8126"/>
			</reference>
			<reference anchor="RFC8174" target="https://www.rfc-editor.org/info/rfc8
			174" quoteTitle="true" derivedAnchor="RFC8174">
			<front>
			<title>Ambiguity of Uppercase vs Lowercase in RFC 2119 Key Words</ti
			tle>
			<author initials="B." surname="Leiba" fullname="B. Leiba">
			<organization showOnFrontPage="true"/>
			</author>
			<date year="2017" month="May"/>
			<abstract>
			<t>RFC 2119 specifies common key words that may be used in protoco
			l specifications. This document aims to reduce the ambiguity by clarifying tha
			t only UPPERCASE usage of the key words have the defined special meanings.</t>
			</abstract>
			</front>
			<seriesInfo name="BCP" value="14"/>
			<seriesInfo name="RFC" value="8174"/>
			<seriesInfo name="DOI" value="10.17487/RFC8174"/>
			</reference>
			<reference anchor="RFC8231" target="https://www.rfc-editor.org/info/rfc8
			231" quoteTitle="true" derivedAnchor="RFC8231">
			<front>
			<title>Path Computation Element Communication Protocol (PCEP) Extens
			ions for Stateful PCE</title>
			<author initials="E." surname="Crabbe" fullname="E. Crabbe">
			<organization showOnFrontPage="true"/>
			</author>
			<author initials="I." surname="Minei" fullname="I. Minei">
			<organization showOnFrontPage="true"/>
			</author>
			<author initials="J." surname="Medved" fullname="J. Medved">
			<organization showOnFrontPage="true"/>
			</author>
			<author initials="R." surname="Varga" fullname="R. Varga">
			<organization showOnFrontPage="true"/>
			</author>
			<date year="2017" month="September"/>
			<abstract>
			<t>The Path Computation Element Communication Protocol (PCEP) prov
			ides mechanisms for Path Computation Elements (PCEs) to perform path computation
			s in response to Path Computation Client (PCC) requests.</t>
			<t>Although PCEP explicitly makes no assumptions regarding the inf
			ormation available to the PCE, it also makes no provisions for PCE control of ti
			ming and sequence of path computations within and across PCEP sessions. This do
			cument describes a set of extensions to PCEP to enable stateful control of MPLS-
			TE and GMPLS Label Switched Paths (LSPs) via PCEP.</t>
			</abstract>
			</front>
			<seriesInfo name="RFC" value="8231"/>
			<seriesInfo name="DOI" value="10.17487/RFC8231"/>
			</reference>
			<reference anchor="RFC8253" target="https://www.rfc-editor.org/info/rfc8
			253" quoteTitle="true" derivedAnchor="RFC8253">
			<front>
			<title>PCEPS: Usage of TLS to Provide a Secure Transport for the Pat
			h Computation Element Communication Protocol (PCEP)</title>
			<author initials="D." surname="Lopez" fullname="D. Lopez">
			<organization showOnFrontPage="true"/>
			</author>
			<author initials="O." surname="Gonzalez de Dios" fullname="O. Gonzal
			ez de Dios">
			<organization showOnFrontPage="true"/>
			</author>
			<author initials="Q." surname="Wu" fullname="Q. Wu">
			<organization showOnFrontPage="true"/>
			</author>
			<author initials="D." surname="Dhody" fullname="D. Dhody">
			<organization showOnFrontPage="true"/>
			</author>
			<date year="2017" month="October"/>
			<abstract>
			<t>The Path Computation Element Communication Protocol (PCEP) defi
			nes the mechanisms for the communication between a Path Computation Client (PCC)
			and a Path Computation Element (PCE), or among PCEs. This document describes PC
			EPS -- the usage of Transport Layer Security (TLS) to provide a secure transport
			for PCEP. The additional security mechanisms are provided by the transport pro
			tocol supporting PCEP; therefore, they do not affect the flexibility and extensi
			bility of PCEP.</t>
			<t>This document updates RFC 5440 in regards to the PCEP initializ
			ation phase procedures.</t>
			</abstract>
			</front>
			<seriesInfo name="RFC" value="8253"/>
			<seriesInfo name="DOI" value="10.17487/RFC8253"/>
			</reference>
			<reference anchor="RFC8281" target="https://www.rfc-editor.org/info/rfc8
			281" quoteTitle="true" derivedAnchor="RFC8281">
			<front>
			<title>Path Computation Element Communication Protocol (PCEP) Extens
			ions for PCE-Initiated LSP Setup in a Stateful PCE Model</title>
			<author initials="E." surname="Crabbe" fullname="E. Crabbe">
			<organization showOnFrontPage="true"/>
			</author>
			<author initials="I." surname="Minei" fullname="I. Minei">
			<organization showOnFrontPage="true"/>
			</author>
			<author initials="S." surname="Sivabalan" fullname="S. Sivabalan">
			<organization showOnFrontPage="true"/>
			</author>
			<author initials="R." surname="Varga" fullname="R. Varga">
			<organization showOnFrontPage="true"/>
			</author>
			<date year="2017" month="December"/>
			<abstract>
			<t>The Path Computation Element Communication Protocol (PCEP) prov
			ides mechanisms for Path Computation Elements (PCEs) to perform path computation
			s in response to Path Computation Client (PCC) requests.</t>
			<t>The extensions for stateful PCE provide active control of Multi
			protocol Label Switching (MPLS) Traffic Engineering Label Switched Paths (TE LSP
			s) via PCEP, for a model where the PCC delegates control over one or more locall
			y configured LSPs to the PCE. This document describes the creation and deletion
			of PCE-initiated LSPs under the stateful PCE model.</t>
			</abstract>
			</front>
			<seriesInfo name="RFC" value="8281"/>
			<seriesInfo name="DOI" value="10.17487/RFC8281"/>
			</reference>
			</references>
			<references pn="section-9.2">
			<name slugifiedName="name-informative-references">Informative References
			</name>
			<reference anchor="I-D.ietf-pce-pcep-yang" quoteTitle="true" target="htt
			ps://tools.ietf.org/html/draft-ietf-pce-pcep-yang-13" derivedAnchor="PCE-PCEP-YA
			NG">
			<front>
			<title>A YANG Data Model for Path Computation Element Communications
			Protocol (PCEP)</title>
			<author initials="D" surname="Dhody" fullname="Dhruv Dhody">
			<organization showOnFrontPage="true"/>
			</author>
			<author initials="J" surname="Hardwick" fullname="Jonathan Hardwick"
			>
			<organization showOnFrontPage="true"/>
			</author>
			<author initials="V" surname="Beeram" fullname="Vishnu Beeram">
			<organization showOnFrontPage="true"/>
			</author>
			<author initials="J" surname="Tantsura" fullname="Jeff Tantsura">
			<organization showOnFrontPage="true"/>
			</author>
			<date month="October" day="31" year="2019"/>
			<abstract>
			<t>This document defines a YANG data model for the management of P
			ath Computation Element communications Protocol (PCEP) for communications betwee
			n a Path Computation Client (PCC) and a Path Computation Element (PCE), or betwe
			en two PCEs. The data model includes configuration and state data.</t>
			</abstract>
			</front>
			<seriesInfo name="Internet-Draft" value="draft-ietf-pce-pcep-yang-13"/
			>
			<format type="TXT" target="http://www.ietf.org/internet-drafts/draft-i
			etf-pce-pcep-yang-13.txt"/>
			<refcontent>Work in Progress</refcontent>
			</reference>
			<reference anchor="RFC3209" target="https://www.rfc-editor.org/info/rfc3
			209" quoteTitle="true" derivedAnchor="RFC3209">
			<front>
			<title>RSVP-TE: Extensions to RSVP for LSP Tunnels</title>
			<author initials="D." surname="Awduche" fullname="D. Awduche">
			<organization showOnFrontPage="true"/>
			</author>
			<author initials="L." surname="Berger" fullname="L. Berger">
			<organization showOnFrontPage="true"/>
			</author>
			<author initials="D." surname="Gan" fullname="D. Gan">
			<organization showOnFrontPage="true"/>
			</author>
			<author initials="T." surname="Li" fullname="T. Li">
			<organization showOnFrontPage="true"/>
			</author>
			<author initials="V." surname="Srinivasan" fullname="V. Srinivasan">
			<organization showOnFrontPage="true"/>
			</author>
			<author initials="G." surname="Swallow" fullname="G. Swallow">
			<organization showOnFrontPage="true"/>
			</author>
			<date year="2001" month="December"/>
			<abstract>
			<t>This document describes the use of RSVP (Resource Reservation P
			rotocol), including all the necessary extensions, to establish label-switched pa
			ths (LSPs) in MPLS (Multi-Protocol Label Switching). Since the flow along an LS
			P is completely identified by the label applied at the ingress node of the path,
			these paths may be treated as tunnels. A key application of LSP tunnels is tra
			ffic engineering with MPLS as specified in RFC 2702. [STANDARDS-TRACK]</t>
			</abstract>
			</front>
			<seriesInfo name="RFC" value="3209"/>
			<seriesInfo name="DOI" value="10.17487/RFC3209"/>
			</reference>
			<reference anchor="RFC3471" target="https://www.rfc-editor.org/info/rfc3
			471" quoteTitle="true" derivedAnchor="RFC3471">
			<front>
			<title>Generalized Multi-Protocol Label Switching (GMPLS) Signaling
			Functional Description</title>
			<author initials="L." surname="Berger" fullname="L. Berger" role="ed
			itor">
			<organization showOnFrontPage="true"/>
			</author>
			<date year="2003" month="January"/>
			<abstract>
			<t>This document describes extensions to Multi-Protocol Label Swit
			ching (MPLS) signaling required to support Generalized MPLS. Generalized MPLS e
			xtends the MPLS control plane to encompass time-division (e.g., Synchronous Opti
			cal Network and Synchronous Digital Hierarchy, SONET/SDH), wavelength (optical l
			ambdas) and spatial switching (e.g., incoming port or fiber to outgoing port or
			fiber). This document presents a functional description of the extensions. Pro
			tocol specific formats and mechanisms, and technology specific details are speci
			fied in separate documents. [STANDARDS-TRACK]</t>
			</abstract>
			</front>
			<seriesInfo name="RFC" value="3471"/>
			<seriesInfo name="DOI" value="10.17487/RFC3471"/>
			</reference>
			<reference anchor="RFC7420" target="https://www.rfc-editor.org/info/rfc7
			420" quoteTitle="true" derivedAnchor="RFC7420">
			<front>
			<title>Path Computation Element Communication Protocol (PCEP) Manage
			ment Information Base (MIB) Module</title>
			<author initials="A." surname="Koushik" fullname="A. Koushik">
			<organization showOnFrontPage="true"/>
			</author>
			<author initials="E." surname="Stephan" fullname="E. Stephan">
			<organization showOnFrontPage="true"/>
			</author>
			<author initials="Q." surname="Zhao" fullname="Q. Zhao">
			<organization showOnFrontPage="true"/>
			</author>
			<author initials="D." surname="King" fullname="D. King">
			<organization showOnFrontPage="true"/>
			</author>
			<author initials="J." surname="Hardwick" fullname="J. Hardwick">
			<organization showOnFrontPage="true"/>
			</author>
			<date year="2014" month="December"/>
			<abstract>
			<t>This memo defines a portion of the Management Information Base
			(MIB) for use with network management protocols in the Internet community. In pa
			rticular, it describes managed objects for modeling of the Path Computation Elem
			ent Communication Protocol (PCEP) for communications between a Path Computation
			Client (PCC) and a Path Computation Element (PCE), or between two PCEs.</t>
			</abstract>
			</front>
			<seriesInfo name="RFC" value="7420"/>
			<seriesInfo name="DOI" value="10.17487/RFC7420"/>
			</reference>
			<reference anchor="RFC8051" target="https://www.rfc-editor.org/info/rfc8
			051" quoteTitle="true" derivedAnchor="RFC8051">
			<front>
			<title>Applicability of a Stateful Path Computation Element (PCE)</t
			itle>
			<author initials="X." surname="Zhang" fullname="X. Zhang" role="edit
			or">
			<organization showOnFrontPage="true"/>
			</author>
			<author initials="I." surname="Minei" fullname="I. Minei" role="edit
			or">
			<organization showOnFrontPage="true"/>
			</author>
			<date year="2017" month="January"/>
			<abstract>
			<t>A stateful Path Computation Element (PCE) maintains information
			about Label Switched Path (LSP) characteristics and resource usage within a net
			work in order to provide traffic-engineering calculations for its associated Pat
			h Computation Clients (PCCs). This document describes general considerations fo
			r a stateful PCE deployment and examines its applicability and benefits, as well
			as its challenges and limitations, through a number of use cases. PCE Communic
			ation Protocol (PCEP) extensions required for stateful PCE usage are covered in
			separate documents.</t>
			</abstract>
			</front>
			<seriesInfo name="RFC" value="8051"/>
			<seriesInfo name="DOI" value="10.17487/RFC8051"/>
			</reference>
			</references>
			</references>
			<section numbered="false" anchor="acknowledgments" toc="include" removeInRFC
			="false" pn="section-appendix.a">
			<name slugifiedName="name-acknowledgments">Acknowledgments</name>
			<t pn="section-appendix.a-1">
			The authors would like to thank <contact fullname="Robert Varga"/>, <contact
			fullname="Venugopal Reddy"/>, <contact fullname="Reeja Paul"/>, <contact full
			name="Sandeep Boina"/>, <contact fullname="Avantika"/>, <contact fullname="JP Va
			sseur"/>, <contact fullname="Himanshu Shah"/>, <contact fullname="Jonathan Ha
			rdwick"/>, and <contact fullname="Adrian Farrel"/> for their useful comments and
			suggestions.</t>
			<t pn="section-appendix.a-2">
			Thanks to <contact fullname="Daniel Franke"/>, <contact fullname="Joe Clarke"
			/>, <contact fullname="David Black"/>, and <contact fullname="Erik Kline"/> for
	the directorate reviews.</t>		the directorate reviews.</t>
			<t pn="section-appendix.a-3">
	<t>		Thanks to <contact fullname="Mirja Kühlewind"/>, <contact fullname="Barry Lei
	Thanks to Mirja Kuhlewind, Barry Leiba, Benjamin Kaduk, and Roman		ba"/>, <contact fullname="Benjamin Kaduk"/>, and <contact fullname="Roman Dan
	Danyliw for the IESG review.</t>		yliw"/> for the IESG review.</t>
			</section>
	</section>		<section numbered="false" anchor="contributors" toc="include" removeInRFC="f
			alse" pn="section-appendix.b">
	<section title="Contributors" numbered="no" anchor="contributors"><figure		<name slugifiedName="name-contributors">Contributors</name>
	><artwork><![CDATA[		<contact fullname="He Zekun">
	He Zekun		<organization showOnFrontPage="true">Tencent Holdings Ltd.</organization
	Tencent Holdings Ltd,		>
	Shenzhen P.R.China		<address>
			<postal>
	Email: kinghe@tencent.com		<city>Shenzhen</city>
			<country>China</country>
	Xian Zhang		</postal>
	Huawei Technologies		<email>kinghe@tencent.com</email>
	Research Area F3-1B,		</address>
	Huawei Industrial Base,		</contact>
	Shenzhen, 518129		<contact fullname="Xian Zhang">
	China		<organization showOnFrontPage="true">Huawei Technologies</organization>
			<address>
	Phone: +86-755-28972645		<postal>
	Email: zhang.xian@huawei.com		<street>Research Area F3-1B</street>
			<street>Huawei Industrial Base,</street>
	Young Lee		<city>Shenzhen</city>
	SKKU		<code>518129</code>
			<country>China</country>
	Email: younglee.tx@gmail.com		</postal>
	]]></artwork>		<phone>+86-755-28972645</phone>
	</figure>		<email>zhang.xian@huawei.com</email>
	</section>		</address>
			</contact>
	</back>		<contact fullname="Young Lee">
			<organization showOnFrontPage="true">Samsung</organization>
	</rfc>		<address>
			<postal>
			</postal>
			<email>younglee.tx@gmail.com</email>
			</address>
			</contact>
			</section>
			<section anchor="authors-addresses" numbered="false" removeInRFC="false" toc
			="include" pn="section-appendix.c">
			<name slugifiedName="name-authors-addresses">Authors' Addresses</name>
			<author fullname="Dhruv Dhody" initials="D." role="editor" surname="Dhody"
			>
			<organization showOnFrontPage="true">Huawei Technologies</organization>
			<address>
			<postal>
			<street>Divyashree Techno Park, Whitefield</street>
			<city>Bangalore</city>
			<region>Karnataka</region>
			<code>560066</code>
			<country>India</country>
			</postal>
			<email>dhruv.ietf@gmail.com</email>
			</address>
			</author>
			<author fullname="Rakesh Gandhi" initials="R." role="editor" surname="Gand
			hi">
			<organization showOnFrontPage="true">Cisco Systems, Inc.</organization>
			<address>
			<postal>
			<country>Canada</country>
			</postal>
			<email>rgandhi@cisco.com</email>
			</address>
			</author>
			<author fullname="Udayasree Palle" initials="U." surname="Palle">
			<organization showOnFrontPage="true">Individual Contributor</organizatio
			n>
			<address>
			<email>udayasreereddy@gmail.com</email>
			</address>
			</author>
			<author fullname="Ravi Singh" initials="R." surname="Singh">
			<organization showOnFrontPage="true">Individual Contributor</organizatio
			n>
			<address>
			<email>ravi.singh.ietf@gmail.com</email>
			</address>
			</author>
			<author fullname="Luyuan Fang" initials="L." surname="Fang">
			<organization showOnFrontPage="true">Expedia Group, Inc.</organization>
			<address>
			<postal>
			<country>United States of America</country>
			</postal>
			<email>luyuanf@gmail.com</email>
			</address>
			</author>
			</section>
			</back>
			</rfc>
End of changes. 187 change blocks.
	1336 lines changed or deleted		2466 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/