<?xml version='1.0' encoding='utf-8'?><!DOCTYPE rfc SYSTEM "rfc2629.dtd" [ <!ENTITY RFC2119 SYSTEM "https://xml2rfc.ietf.org/public/rfc/bibxml/reference.RFC.2119.xml"> <!ENTITY RFC5440 SYSTEM "https://xml2rfc.ietf.org/public/rfc/bibxml/reference.RFC.5440.xml"> <!ENTITY RFC7525 SYSTEM "https://xml2rfc.ietf.org/public/rfc/bibxml/reference.RFC.7525.xml"> <!ENTITY RFC8126 SYSTEM "https://xml2rfc.ietf.org/public/rfc/bibxml/reference.RFC.8126.xml"> <!ENTITY RFC8174 SYSTEM "https://xml2rfc.ietf.org/public/rfc/bibxml/reference.RFC.8174.xml"> <!ENTITY RFC8231 SYSTEM "https://xml2rfc.ietf.org/public/rfc/bibxml/reference.RFC.8231.xml"> <!ENTITY RFC8253 SYSTEM "https://xml2rfc.ietf.org/public/rfc/bibxml/reference.RFC.8253.xml"> <!ENTITY RFC8281 SYSTEM "https://xml2rfc.ietf.org/public/rfc/bibxml/reference.RFC.8281.xml"> <!ENTITY RFC3209 SYSTEM "https://xml2rfc.ietf.org/public/rfc/bibxml/reference.RFC.3209.xml"> <!ENTITY RFC3471 SYSTEM "https://xml2rfc.ietf.org/public/rfc/bibxml/reference.RFC.3471.xml"> <!ENTITY RFC7420 SYSTEM "https://xml2rfc.ietf.org/public/rfc/bibxml/reference.RFC.7420.xml"> <!ENTITY RFC8051 SYSTEM "https://xml2rfc.ietf.org/public/rfc/bibxml/reference.RFC.8051.xml"> <!ENTITY I-D.ietf-pce-pcep-yang SYSTEM "https://xml2rfc.ietf.org/public/rfc/bibxml3/reference.I-D.ietf-pce-pcep-yang.xml"> ]><rfcsubmissionType="IETF" docName="draft-ietf-pce-stateful-pce-auto-bandwidth-12"xmlns:xi="http://www.w3.org/2001/XInclude" version="3" category="std"ipr="trust200902"> <!-- Generated by id2xml 1.5.0 on 2019-10-29T21:33:17Z --> <?rfc compact="yes"?> <?rfc text-list-symbols="ooo*+-"?> <?rfc subcompact="no"?> <?rfc sortrefs="yes"?> <?rfc symrefs="yes"?> <?rfc strict="yes"?> <?rfc toc="yes"?> <?rfc tocdepth="4"?>consensus="true" docName="draft-ietf-pce-stateful-pce-auto-bandwidth-12" indexInclude="true" ipr="trust200902" number="8733" prepTime="2020-02-25T16:36:04" scripts="Common,Latin" sortRefs="true" submissionType="IETF" symRefs="true" tocDepth="4" tocInclude="true" xml:lang="en"> <link href="https://datatracker.ietf.org/doc/draft-ietf-pce-stateful-pce-auto-bandwidth-12" rel="prev"/> <link href="https://dx.doi.org/10.17487/rfc8733" rel="alternate"/> <link href="urn:issn:2070-1721" rel="alternate"/> <front> <titleabbrev="PCEP Extensions for MPLS-TE LSP Automati">PCEPabbrev="Auto-Bandwidth with Stateful PCE">Path Computation Element Communication Protocol (PCEP) Extensions for MPLS-TELSP Automatic BandwidthLabel Switched Path (LSP) Auto-Bandwidth Adjustment with Stateful PCE</title> <seriesInfo name="RFC" value="8733" stream="IETF"/> <author fullname="Dhruv Dhody" initials="D." role="editor" surname="Dhody"><organization>Huawei<organization showOnFrontPage="true">Huawei Technologies</organization><address><postal><street>Divyashree<address> <postal> <street>Divyashree Techno Park, Whitefield</street><street>Bangalore, Karnataka 560066</street> <street>India</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="Gandhi"><organization>Cisco<organization showOnFrontPage="true">Cisco Systems, Inc.</organization><address><postal><street>Canada</street><address> <postal> <country>Canada</country> </postal> <email>rgandhi@cisco.com</email> </address> </author> <author fullname="Udayasree Palle" initials="U." surname="Palle"><organization>Individual<organization showOnFrontPage="true">Individual Contributor</organization><address><email>udayasreereddy@gmail.com</email><address> <email>udayasreereddy@gmail.com</email> </address> </author> <author fullname="Ravi Singh" initials="R." surname="Singh"><organization>Individual<organization showOnFrontPage="true">Individual Contributor</organization><address><email>ravi.singh.ietf@gmail.com</email><address> <email>ravi.singh.ietf@gmail.com</email> </address> </author> <author fullname="Luyuan Fang" initials="L." surname="Fang"><organization>Expedia,<organization showOnFrontPage="true">Expedia Group, Inc.</organization><address><postal><street>USA</street><address> <postal> <country>United States of America</country> </postal> <email>luyuanf@gmail.com</email> </address> </author> <datemonth="October" year="2019"/>month="02" year="2020"/> <workgroup>PCE Working Group</workgroup><abstract><t><keyword>Bandwidth optimization</keyword> <keyword>PCEP Overwhelm</keyword> <keyword>LSP re-optimization</keyword> <abstract pn="section-abstract"> <t pn="section-abstract-1"> The Path Computation Element Communication Protocol (PCEP) provides mechanisms for Path Computation Elements (PCEs) to perform path computations in response to Path ComputationClients (PCCs)Client (PCC) requests.TheStateful PCE extensions allow stateful control ofMulti-Protocol Label Switching (MPLS) Traffic EngineeringMPLS-TE Label Switched Paths(TE LSPs)(LSPs) using PCEP.</t><t><t pn="section-abstract-2"> Theautomatic bandwidthauto-bandwidth feature allows automatic and dynamic adjustment of the TE LSP bandwidth reservation based on the volume of traffic flowing through the LSP. This document describes PCEP extensions forautomatic bandwidthauto-bandwidth adjustment when employing anActive Statefulactive stateful PCE for bothPCE-InitiatedPCE-initiated andPCC-InitiatedPCC-initiated LSPs.</t> </abstract> <boilerplate> <section anchor="status-of-memo" numbered="false" removeInRFC="false" toc="exclude" pn="section-boilerplate.1"> <name slugifiedName="name-status-of-this-memo">Status of This Memo</name> <t pn="section-boilerplate.1-1"> 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="none"/>. </t> </section> <section anchor="copyright" numbered="false" removeInRFC="false" toc="exclude" 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" pn="section-toc.1"> <name slugifiedName="name-table-of-contents">Table of Contents</name> <ul bare="true" empty="true" indent="2" spacing="compact" pn="section-toc.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 derivedContent="" format="title" sectionFormat="of" target="name-introduction">Introduction</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 derivedContent="" 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="section-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 derivedContent="2.1" format="counter" sectionFormat="of" target="section-2.1"/>. <xref 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 derivedContent="2.2" format="counter" sectionFormat="of" target="section-2.2"/>. <xref 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 derivedContent="2.3" format="counter" sectionFormat="of" target="section-2.3"/>. <xref 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 derivedContent="" format="title" sectionFormat="of" target="name-requirements-for-pcep-exten">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 derivedContent="" format="title" sectionFormat="of" target="name-architectural-overview">Architectural Overview</xref></t> <ul bare="true" empty="true" indent="2" spacing="compact" pn="section-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 derivedContent="4.1" format="counter" sectionFormat="of" target="section-4.1"/>. <xref derivedContent="" format="title" sectionFormat="of" target="name-auto-bandwidth-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 derivedContent="4.2" format="counter" sectionFormat="of" target="section-4.2"/>. <xref derivedContent="" format="title" sectionFormat="of" target="name-auto-bandwidth-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 derivedContent="4.3" format="counter" sectionFormat="of" target="section-4.3"/>. <xref derivedContent="" format="title" sectionFormat="of" target="name-scaling-considerations">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 derivedContent="" format="title" sectionFormat="of" target="name-pcep-extensions">PCEP Extensions</xref></t> <ul bare="true" empty="true" indent="2" spacing="compact" pn="section-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 derivedContent="5.1" format="counter" sectionFormat="of" target="section-5.1"/>. <xref derivedContent="" format="title" sectionFormat="of" target="name-capability-advertisement">Capability Advertisement</xref></t> <ul bare="true" empty="true" indent="2" spacing="compact" pn="section-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"><xref derivedContent="5.1.1" format="counter" sectionFormat="of" target="section-5.1.1"/>. <xref derivedContent="" format="title" sectionFormat="of" target="name-auto-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 derivedContent="5.2" format="counter" sectionFormat="of" target="section-5.2"/>. <xref derivedContent="" format="title" sectionFormat="of" target="name-auto-bandwidth-attributes-t">AUTO-BANDWIDTH-ATTRIBUTES TLV</xref></t> <ul bare="true" empty="true" indent="2" spacing="compact" pn="section-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"><xref derivedContent="5.2.1" format="counter" sectionFormat="of" target="section-5.2.1"/>. <xref derivedContent="" format="title" sectionFormat="of" target="name-sample-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"><xref derivedContent="5.2.2" format="counter" sectionFormat="of" target="section-5.2.2"/>. <xref derivedContent="" format="title" sectionFormat="of" target="name-adjustment-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="section-5.2.2.1"/>. <xref derivedContent="" format="title" sectionFormat="of" target="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="section-5.2.2.2"/>. <xref derivedContent="" format="title" sectionFormat="of" target="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"><xref derivedContent="5.2.3" format="counter" sectionFormat="of" target="section-5.2.3"/>. <xref derivedContent="" format="title" sectionFormat="of" target="name-adjustment-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="section-5.2.3.1"/>. <xref derivedContent="" format="title" sectionFormat="of" target="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="section-5.2.3.2"/>. <xref derivedContent="" format="title" sectionFormat="of" target="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="section-5.2.3.3"/>. <xref derivedContent="" format="title" sectionFormat="of" target="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="section-5.2.3.4"/>. <xref derivedContent="" format="title" sectionFormat="of" target="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"><xref derivedContent="5.2.4" format="counter" sectionFormat="of" target="section-5.2.4"/>. <xref derivedContent="" format="title" sectionFormat="of" target="name-minimum-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="section-5.2.4.1"/>. <xref derivedContent="" format="title" sectionFormat="of" target="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="section-5.2.4.2"/>. <xref derivedContent="" format="title" sectionFormat="of" target="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"><xref derivedContent="5.2.5" format="counter" sectionFormat="of" target="section-5.2.5"/>. <xref derivedContent="" format="title" sectionFormat="of" target="name-overflow-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="section-5.2.5.1"/>. <xref derivedContent="" format="title" sectionFormat="of" target="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="section-5.2.5.2"/>. <xref derivedContent="" format="title" sectionFormat="of" target="name-overflow-threshold-percenta">Overflow-Threshold-Percentage Sub-TLV</xref></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="section-5.2.5.3"/>. <xref derivedContent="" format="title" sectionFormat="of" target="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="section-5.2.5.4"/>. <xref derivedContent="" format="title" sectionFormat="of" target="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 derivedContent="5.3" format="counter" sectionFormat="of" target="section-5.3"/>. <xref derivedContent="" format="title" sectionFormat="of" target="name-bandwidth-object">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 derivedContent="5.4" format="counter" sectionFormat="of" target="section-5.4"/>. <xref derivedContent="" format="title" sectionFormat="of" target="name-the-pcinitiate-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 derivedContent="5.5" format="counter" sectionFormat="of" target="section-5.5"/>. <xref derivedContent="" format="title" sectionFormat="of" target="name-the-pcupd-message">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 derivedContent="5.6" format="counter" sectionFormat="of" target="section-5.6"/>. <xref derivedContent="" format="title" sectionFormat="of" target="name-the-pcrpt-message">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 derivedContent="5.7" format="counter" sectionFormat="of" target="section-5.7"/>. <xref derivedContent="" format="title" sectionFormat="of" target="name-the-pcntf-message">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 derivedContent="" format="title" sectionFormat="of" target="name-manageability-consideration">Manageability Considerations</xref></t> <ul bare="true" empty="true" indent="2" spacing="compact" pn="section-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 derivedContent="6.1" format="counter" sectionFormat="of" target="section-6.1"/>. <xref derivedContent="" format="title" sectionFormat="of" target="name-control-of-function-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 derivedContent="6.2" format="counter" sectionFormat="of" target="section-6.2"/>. <xref derivedContent="" format="title" sectionFormat="of" target="name-information-and-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 derivedContent="6.3" format="counter" sectionFormat="of" target="section-6.3"/>. <xref derivedContent="" format="title" sectionFormat="of" target="name-liveness-detection-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 derivedContent="6.4" format="counter" sectionFormat="of" target="section-6.4"/>. <xref derivedContent="" format="title" sectionFormat="of" target="name-verifying-correct-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 derivedContent="6.5" format="counter" sectionFormat="of" target="section-6.5"/>. <xref 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 derivedContent="6.6" format="counter" sectionFormat="of" target="section-6.6"/>. <xref derivedContent="" format="title" sectionFormat="of" target="name-impact-on-network-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 derivedContent="" 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 derivedContent="" format="title" sectionFormat="of" target="name-iana-considerations">IANA Considerations</xref></t> <ul bare="true" empty="true" indent="2" spacing="compact" pn="section-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 derivedContent="8.1" format="counter" sectionFormat="of" target="section-8.1"/>. <xref 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 derivedContent="8.2" format="counter" sectionFormat="of" target="section-8.2"/>. <xref derivedContent="" format="title" sectionFormat="of" target="name-auto-bandwidth-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 derivedContent="8.3" format="counter" sectionFormat="of" target="section-8.3"/>. <xref derivedContent="" format="title" sectionFormat="of" target="name-auto-bandwidth-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 derivedContent="8.4" format="counter" sectionFormat="of" target="section-8.4"/>. <xref 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 derivedContent="8.5" format="counter" sectionFormat="of" target="section-8.5"/>. <xref 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 derivedContent="" format="title" sectionFormat="of" target="name-references">References</xref></t> <ul bare="true" empty="true" indent="2" spacing="compact" pn="section-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 derivedContent="9.1" format="counter" sectionFormat="of" target="section-9.1"/>. <xref derivedContent="" format="title" sectionFormat="of" target="name-normative-references">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 derivedContent="9.2" format="counter" sectionFormat="of" target="section-9.2"/>. <xref derivedContent="" format="title" sectionFormat="of" target="name-informative-references">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 derivedContent="" format="none" sectionFormat="of" target="section-appendix.a"/><xref derivedContent="" format="title" sectionFormat="of" target="name-acknowledgments">Acknowledgments</xref></t> </li> <li pn="section-toc.1-1.11"> <t keepWithNext="true" pn="section-toc.1-1.11.1"><xref derivedContent="" format="none" sectionFormat="of" target="section-appendix.b"/><xref derivedContent="" format="title" sectionFormat="of" target="name-contributors">Contributors</xref></t> </li> <li pn="section-toc.1-1.12"> <t keepWithNext="true" pn="section-toc.1-1.12.1"><xref derivedContent="" format="none" sectionFormat="of" target="section-appendix.c"/><xref derivedContent="" format="title" sectionFormat="of" target="name-authors-addresses">Authors' Addresses</xref></t> </li> </ul> </section> </toc> </front> <middle> <sectiontitle="Introduction" anchor="sect-1"><t> <xref target="RFC5440"/>anchor="sect-1" numbered="true" toc="include" removeInRFC="false" pn="section-1"> <name slugifiedName="name-introduction">Introduction</name> <t pn="section-1-1"> <xref target="RFC5440" format="default" sectionFormat="of" derivedContent="RFC5440"/> describes the Path Computation Element Protocol (PCEP) as a communication mechanism between a Path Computation Client (PCC) and a Path Computation Element (PCE), or between a PCE and a PCE, that enables computation ofMulti-Protocol Label Switching (MPLS) Traffic EngineeringMPLS-TE Label Switched Paths(TE LSPs).</t> <t>(LSPs).</t> <t pn="section-1-2"> <xreftarget="RFC8231"/>target="RFC8231" format="default" sectionFormat="of" derivedContent="RFC8231"/> specifies extensions to PCEP to enable stateful control ofMPLS TEMPLS-TE LSPs. It describes twomodemodes ofoperations - Passiveoperation: passive stateful PCE andActiveactive stateful PCE. Further, <xreftarget="RFC8281"/>target="RFC8281" format="default" sectionFormat="of" derivedContent="RFC8281"/> describes the setup,maintenancemaintenance, and teardown ofPCE-InitiatedPCE-initiated LSPs for the stateful PCE model. In this document, the focus is onActivethe active statefulPCEPCE, where the LSPs are controlled by the PCE.</t><t><t pn="section-1-3"> Over time, based on the varying traffic pattern, an LSP established with a certain bandwidth may require adjustment of the bandwidth reserved in the network dynamically. The head-end LabelSwitchSwitching Router (LSR) monitors the actual bandwidth demand of the established LSP and periodically computes new bandwidth. The head-end LSR automatically adjusts the bandwidth reservation of the LSP based on the computedbandwidth automatically.bandwidth. This feature, when available in the head-endLabel Switching Router (LSR)LSR implementation, iscommoncommonly referred to asAuto-Bandwidth.auto-bandwidth. TheAuto-Bandwidthauto-bandwidth feature is described in detail inSection 4<xref target="sect-4" format="default" sectionFormat="of" derivedContent="Section 4"/> of this document.</t><t><t pn="section-1-4"> 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 the newadjusted bandwidth.Adjusted Bandwidth. The PCC reports the calculated bandwidth to be adjusted to the PCE. This is similar to thePassivepassive stateful PCE model: while thePassivepassive stateful PCE uses a path request/reply mechanism, theActiveactive stateful PCE uses a report/update mechanism.In case of PCE-InitiatedWith a PCE-initiated LSP, the PCC is requested during the LSP initiation to monitor and calculate the newadjusted bandwidth.Adjusted Bandwidth. <xreftarget="RFC8051"/>target="RFC8051" format="default" sectionFormat="of" derivedContent="RFC8051"/> describes theuse-caseuse case forAuto-Bandwidthauto-bandwidth adjustment forPassivepassive andActiveactive statefulPCE.</t> <t>PCEs.</t> <t pn="section-1-5"> Another approach would be to send the measured valuesitselfthemselves to the PCE, which is considered out of scope for this document.</t><t><t pn="section-1-6"> This document defines the PCEP extensions needed to support anAuto-Bandwidthauto-bandwidth feature in anActiveactive stateful PCE model where the LSP 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 scope of this document.</t> </section> <sectiontitle="Conventionsanchor="sect-2" numbered="true" toc="include" removeInRFC="false" pn="section-2"> <name slugifiedName="name-conventions-used-in-this-do">Conventions Used in ThisDocument" anchor="sect-2"><section title="Requirements Language" anchor="sect-2.1"><t>Document</name> <section anchor="sect-2.1" numbered="true" toc="include" removeInRFC="false" pn="section-2.1"> <name slugifiedName="name-requirements-language">Requirements Language</name> <t pn="section-2.1-1"> The key words"MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", "SHOULD", "SHOULD NOT", "RECOMMENDED", "NOT RECOMMENDED", "MAY","<bcp14>MUST</bcp14>", "<bcp14>MUST NOT</bcp14>", "<bcp14>REQUIRED</bcp14>", "<bcp14>SHALL</bcp14>", "<bcp14>SHALL NOT</bcp14>", "<bcp14>SHOULD</bcp14>", "<bcp14>SHOULD NOT</bcp14>", "<bcp14>RECOMMENDED</bcp14>", "<bcp14>NOT RECOMMENDED</bcp14>", "<bcp14>MAY</bcp14>", and"OPTIONAL""<bcp14>OPTIONAL</bcp14>" in this document are to be interpreted as described inBCP 14BCP 14 <xreftarget="RFC2119"/> <xref target="RFC8174"/>target="RFC2119" format="default" sectionFormat="of" derivedContent="RFC2119"/> <xref target="RFC8174" format="default" sectionFormat="of" derivedContent="RFC8174"/> when, and only when, they appear in all capitals, as shownhere.</t>here. </t> </section> <sectiontitle="Abbreviations" anchor="sect-2.2"> <t><list style="hanging" hangIndent="3"> <t hangText="PCC:">anchor="sect-2.2" numbered="true" toc="include" removeInRFC="false" pn="section-2.2"> <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 ComputationClient.</t> <t hangText="PCE:">Client</dd> <dt pn="section-2.2-1.3">PCE:</dt> <dd pn="section-2.2-1.4"> Path ComputationElement.</t> <t hangText="PCEP:">Element</dd> <dt pn="section-2.2-1.5">PCEP:</dt> <dd pn="section-2.2-1.6"> Path Computation Element CommunicationProtocol.</t> <t hangText="TE LSP:">Protocol</dd> <dt pn="section-2.2-1.7">TE:</dt> <dd pn="section-2.2-1.8"> TrafficEngineering LabelEngineering</dd> <dt pn="section-2.2-1.9">LSP:</dt> <dd pn="section-2.2-1.10">Label SwitchedPath.</t> </list> </t>Path</dd> </dl> </section> <sectiontitle="Terminology" anchor="sect-2.3"><t>anchor="sect-2.3" numbered="true" toc="include" removeInRFC="false" 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 <xreftarget="RFC5440"/>, <xref target="RFC8231"/>, and <xref target="RFC8281"/>.</t> <t>target="RFC5440" format="default" sectionFormat="of" derivedContent="RFC5440"/>, <xref target="RFC8231" format="default" sectionFormat="of" derivedContent="RFC8231"/>, and <xref target="RFC8281" format="default" sectionFormat="of" derivedContent="RFC8281"/>.</t> <t pn="section-2.3-2"> In this document, the PCC is considered to be thehead endhead-end LSR of the LSP. Other types ofPCCPCCs are not in scope.</t><t><t pn="section-2.3-3"> The following auto-bandwidth terminology is defined in this document.</t><t><list style="hanging" hangIndent="3"> <t hangText="Maximum<dl newline="false" spacing="normal" indent="3" pn="section-2.3-4"> <dt pn="section-2.3-4.1">Maximum Average Bandwidth(MaxAvgBw):">The(MaxAvgBw):</dt> <dd pn="section-2.3-4.2">The maximum averagebandwidthrepresentsbandwidth represents the current 'measured' traffic bandwidth demand of the LSP during a time interval. This is the maximum value of the traffic bandwidth rate samples (Bandwidth-Samples) in a given time interval.</t> <t hangText="Adjusted Bandwidth:">This</dd> <dt pn="section-2.3-4.3">Adjusted Bandwidth:</dt> <dd pn="section-2.3-4.4">This is theAuto-Bandwidthauto-bandwidth 'computed' bandwidth that is used to adjust the bandwidth reservation of the LSP.</t> <t hangText="Sample-Interval:">The</dd> <dt pn="section-2.3-4.5">Sample-Interval:</dt> <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.</t> <t hangText="Bandwidth-Sample:">The bandwidth sample</dd> <dt pn="section-2.3-4.7">Bandwidth-Sample:</dt> <dd pn="section-2.3-4.8">The Bandwidth-Sample of the measured traffic rate of the LSP collected at every Sample-Interval.</t> <t hangText="Maximum-Bandwidth:">The maximum bandwidth</dd> <dt pn="section-2.3-4.9">Maximum-Bandwidth:</dt> <dd pn="section-2.3-4.10">The Maximum-Bandwidth that can be reserved for the LSP.</t> <t hangText="Minimum-Bandwidth:">The minimum bandwidth</dd> <dt pn="section-2.3-4.11">Minimum-Bandwidth:</dt> <dd pn="section-2.3-4.12">The Minimum-Bandwidth that can be reserved for the LSP.</t> <t hangText="Up-Adjustment-Interval:">The</dd> <dt pn="section-2.3-4.13">Up-Adjustment-Interval:</dt> <dd pn="section-2.3-4.14">The periodic time interval at which the bandwidth adjustment should be made using theMaxAvgBw,MaxAvgBw when MaxAvgBw is greater than the current bandwidth reservation of the LSP.</t> <t hangText="Down-Adjustment-Interval:">The</dd> <dt pn="section-2.3-4.15">Down-Adjustment-Interval:</dt> <dd pn="section-2.3-4.16">The periodic time interval at which the bandwidth adjustment should be made using theMaxAvgBw,MaxAvgBw when MaxAvgBw is less than the current bandwidth reservation of the LSP.</t> <t hangText="Up-Adjustment-Threshold:">This</dd> <dt pn="section-2.3-4.17">Up-Adjustment-Threshold:</dt> <dd pn="section-2.3-4.18">This parameter is used to decide when the LSP bandwidth should be adjusted. If the percentage or absolute difference between the current MaxAvgBw and the current bandwidth reservation is greater than or equal to the threshold value, the LSP bandwidth is adjusted (upsized) to the current bandwidth demand (Adjusted Bandwidth) at the Up-Adjustment-Interval expiry.</t> <t hangText="Down-Adjustment-Threshold:">This</dd> <dt pn="section-2.3-4.19">Down-Adjustment-Threshold:</dt> <dd pn="section-2.3-4.20">This parameter is used to decide when the LSP bandwidth should be adjusted. If the percentage or absolute difference between the current bandwidth reservation and the current MaxAvgBw is greater than or equal to the threshold value, the LSP bandwidth is adjusted (downsized) to the current bandwidth demand (Adjusted Bandwidth) at the Down-Adjustment-Interval expiry.</t> <t hangText="Overflow-Count:">This</dd> <dt pn="section-2.3-4.21">Overflow-Count:</dt> <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 in traffic demand. This value indicates how many times, consecutively, that the percentage or absolute difference between the current MaxAvgBw and the current bandwidth reservation of the LSP needs to be greater than or equal to the Overflow-Threshold value in order to meet the overflow condition.</t> <t hangText="Overflow-Threshold:">This</dd> <dt pn="section-2.3-4.23">Overflow-Threshold:</dt> <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 increase in traffic demand. If the percentage or absolute difference between the current MaxAvgBw and the current bandwidth reservation of 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 current bandwidthdemanddemand, bypassing the Up-Adjustment-Interval if the overflow condition is met consecutively for the Overflow-Count. The Overflow-Threshold needs to be greater than or equal to the Up-Adjustment-Threshold.</t> <t hangText="Underflow-Count:">This</dd> <dt pn="section-2.3-4.25">Underflow-Count:</dt> <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 in traffic demand. This value indicates how manytimestimes, consecutively, that the percentage or absolute difference between the current MaxAvgBw and the current bandwidth reservation of the LSP needs to be greater than or equal to the Underflow-Threshold value in order to meet the underflow condition.</t> <t hangText="Underflow-Threshold:">This</dd> <dt pn="section-2.3-4.27">Underflow-Threshold:</dt> <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 decrease in traffic demand. If the percentage or absolute difference between the current MaxAvgBw and the current bandwidth reservation of 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 current bandwidthdemanddemand, bypassing the Down-Adjustment-Interval if the underflow condition is met consecutively for the Underflow-Count. The Underflow-Threshold needs to be greater than or equal to the Down-Adjustment-Threshold.</t> <t hangText="Minimum-Threshold:">When</dd> <dt pn="section-2.3-4.29">Minimum-Threshold:</dt> <dd pn="section-2.3-4.30">When percentage-based thresholds are in use, they are accompanied by thisminimum threshold,Minimum-Threshold, which is used toenforceensure that the magnitude of deviation of the calculated LSP bandwidth to be adjusted from the current bandwidth reservations exceeds a specific non-percentage-based criterion (represented as an absolute bandwidth value) before any adjustments are made. This serves to suppress unnecessary auto-bandwidth adjustments andre-signalingresignaling of the LSP at low bandwidth values.</t> </list> </t></dd> </dl> </section> </section> <sectiontitle="Requirementsanchor="sect-3" numbered="true" toc="include" removeInRFC="false" pn="section-3"> <name slugifiedName="name-requirements-for-pcep-exten">Requirements for PCEPExtensions" anchor="sect-3"><t>Extensions</name> <t pn="section-3-1"> The PCEP extensions required for auto-bandwidth are summarized in the following table as well as inFigure 1.</t> <texttable title="Requirements<xref target="ure-overview-of-auto-bandwidth-pcep-extensions" format="default" sectionFormat="of" derivedContent="Figure 1"/>.</t> <table anchor="tab-requirements-for-auto-bandwidth-pcep-extensions" align="center" pn="table-1"> <name slugifiedName="name-requirements-for-auto-bandw">Requirements for Auto-Bandwidth PCEPextensions" anchor="tab-requirements-for-auto-bandwidth-pcep-extensions" style="full"><ttcol> PCC Initiated</ttcol> <ttcol> PCE Initiated</ttcol> <c>PCCExtensions</name> <thead> <tr> <th align="left" colspan="1" rowspan="1">PCC Initiated</th> <th align="left" colspan="1" rowspan="1">PCE Initiated</th> </tr> </thead> <tbody> <tr> <td align="left" colspan="1" rowspan="1">PCC monitors thetraffic</c> <c>Attraffic and reports the calculated bandwidth to be adjusted to the PCE.</td> <td align="left" colspan="1" rowspan="1">At the time ofinitiation,</c> <c>and reportsinitiation, the PCE requests that thecalculated</c> <c>PCE requestPCCto monitor</c> <c>bandwidth to be adjusted</c> <c>themonitor the traffic and reportthe</c> <c>tothePCE.</c> <c>calculatedcalculated bandwidth tobe</c> <c></c> <c>adjustedbe adjusted to thePCE.</c> <c>Extension is needed for PCC</c> <c>ExtensionPCE.</td> </tr> <tr> <td align="left" colspan="1" rowspan="1"> Extension is needed forPCE</c> <c>to pass ontheadjustment</c> <c>toPCC to pass on theadjustment</c> <c>parametersadjustment parameters at the timeof</c> <c>parametersof LSP delegation.</td> <td align="left" colspan="1" rowspan="1"> Extension is needed for the PCE to pass on the adjustment parameters at the timeof</c> <c>LSP Delegation.</c> <c>LSP Initiation.</c> </texttable>of LSP initiation.</td> </tr> </tbody> </table> <figuretitle="Overviewanchor="ure-overview-of-auto-bandwidth-pcep-extensions" align="left" suppress-title="false" pn="figure-1"> <name slugifiedName="name-overview-of-auto-bandwidth-">Overview of Auto-Bandwidth PCEPextensions" anchor="ure-overview-of-auto-bandwidth-pcep-extensions"><artwork><![CDATA[Extensions</name> <artwork name="" type="" align="left" alt="" pn="section-3-3.1"> ---------- | | | PCE | | | ---------- | ^ AUTO-BANDWIDTH CAPABILITY | | AUTO-BANDWIDTH CAPABILITY | | AUTO-BANDWIDTH ATTRIBUTES | | AUTO-BANDWIDTH ATTRIBUTES | | (For Delegated LSPs) | | | | REQUESTED BANDWIDTH v | ---------- | | | PCC | | |---------- ]]></artwork>----------</artwork> </figure><t><t pn="section-3-4"> A PCEP speaker supporting this document must have a mechanism to advertise theautomatic bandwidthauto-bandwidth adjustment capability for bothPCC-InitiatedPCC-initiated andPCE-InitiatedPCE-initiated LSPs.</t><t><t pn="section-3-5"> Auto-bandwidth deployment considerations for PCEP extensions are summarized below:</t><t><list style="symbols"><t>It<ul spacing="normal" bare="false" empty="false" pn="section-3-6"> <li pn="section-3-6.1">It is necessary to identify and inform the PCC which LSPs have enabled theAuto-Bandwidthauto-bandwidth feature. Not all LSPs in some deployments would like their bandwidth to be dependent onthereal-time bandwidth usage; for someLSPsLSPs, leaving the bandwidth constant as set by the operator ispreferred.</t> <t>Inpreferred.</li> <li pn="section-3-6.2">In addition, an operator should be able to specify the auto-bandwidth adjustment parameters(i.e.(i.e., configuration knobs) to control this feature(e.g. minimum/ maximum bandwidth(e.g., Minimum/Maximum-Bandwidth range). The PCC should be informed about these adjustmentparameters.</t> </list> </t>parameters.</li> </ul> </section> <sectiontitle="Architectural Overview" anchor="sect-4"><section title="Auto-Bandwidth Overview" anchor="sect-4.1"><t>anchor="sect-4" numbered="true" toc="include" removeInRFC="false" pn="section-4"> <name slugifiedName="name-architectural-overview">Architectural Overview</name> <section anchor="sect-4.1" numbered="true" toc="include" removeInRFC="false" pn="section-4.1"> <name slugifiedName="name-auto-bandwidth-overview">Auto-Bandwidth Overview</name> <t pn="section-4.1-1"> TheAuto-Bandwidthauto-bandwidth feature allows automatic and dynamic adjustment of the reserved bandwidth of an LSP over time (i.e., without network operator intervention) to accommodate the varying traffic demand of the LSP. If the traffic flowing through the LSP is lower than the configured or current reserved bandwidth of the LSP, the extra bandwidth is being reserved needlessly and is being wasted. Conversely, if the actual traffic flowing through the LSP is higher than the configured or current reserved bandwidth of the LSP, it can potentially cause congestion or packet loss in the network. The initial LSP bandwidth can be set to an arbitrary value (including zero). In practice, it can be set to an expected value based on design and planning. The head-endLabel Switch Router (LSR)LSR monitors the actual traffic flowing through the LSP and uses that information to adjust the bandwidth reservation of the LSP in the network.</t><t><t pn="section-4.1-2"> Bandwidth adjustment must not cause disruption to the traffic flow carried by the LSP. One way to achieve this is to use the make-before-break signaling method <xreftarget="RFC3209"/>.</t>target="RFC3209" format="default" sectionFormat="of" derivedContent="RFC3209"/>.</t> </section> <sectiontitle="Auto-bandwidthanchor="sect-4.2" numbered="true" toc="include" removeInRFC="false" pn="section-4.2"> <name slugifiedName="name-auto-bandwidth-theory-of-op">Auto-Bandwidth Theory ofOperation" anchor="sect-4.2"><t>Operation</name> <t pn="section-4.2-1"> This section describes theAuto-Bandwidthauto-bandwidth feature in a general way. When theAuto-Bandwidthauto-bandwidth feature is enabled, the measured traffic rate is periodically sampled at each Sample-Interval by thePCC,PCC when the PCC is the head-end node of the LSP. Thesample intervalSample-Interval can be configured by an operator, with a default value of 5 minutes. A very low Sample-Interval could have some undesirable interactions with transport protocols (see <xreftarget="sect-6.6"/>).</t> <t>target="sect-6.6" format="default" sectionFormat="of" derivedContent="Section 6.6"/>).</t> <t pn="section-4.2-2"> The traffic rate samples are accumulated over the Adjustment-Interval period (in the Up or Down direction). The period can be configured by an operator, with a default value of 24 hours. The PCCin-chargein charge of calculating the bandwidth to be adjusted can decide to adjust the bandwidth of the LSP to the highest traffic rate sample (MaxAvgBw) amongst the set ofbandwidth samplesBandwidth-Samples collected over the Adjustment-Interval period (in the Up or Down direction) depending on the operator policy.</t><t><t pn="section-4.2-3"> Note that the highest traffic rate sample could be higher or lower than the current LSP bandwidth.OnlyThe LSP is adjusted (upsized) to the current bandwidth demand (MaxAvgBW) only if the difference between the current bandwidth demand (MaxAvgBw) and the current bandwidth reservation is greater than or equal to theAdjustment-Threshold the LSP bandwidth is adjusted (upsized) to the current bandwidth demand (MaxAvgBw).Adjustment-Threshold. The Adjustment-Threshold could be an absolute value or a percentage. The threshold can be configured by an operator, with a default value of 5percentage.percent. Similarly, if the difference between the current bandwidth reservation and the current bandwidth demand (MaxAvgBw) is greater than or equal to the Down-Adjustment-Threshold (percentage or absolute value), the LSP bandwidth is adjusted (downsized) to the current bandwidth demand (MaxAvgBw). Some LSPs are lesseventfuleventful, while other LSPs may encounter a lot of changes in the traffic pattern. The thresholds and intervals for bandwidth adjustment are configured based on the traffic pattern of the LSP.</t><t><t pn="section-4.2-4"> In order to avoid frequentre-signaling,resignaling, an operator may set a longeradjustment-intervalAdjustment-Interval value (Up and/or Down). However, a longer Adjustment-Interval can result inanthe undesirable effect of masking sudden changes in the traffic demands of an LSP. To avoid this, theAuto-Bandwidthauto-bandwidth feature may force the Adjustment-Interval to prematurely expirethe adjustment intervaland adjust the LSP bandwidth to accommodate the sudden bursts of increase in traffic demand as an overflow condition or decrease in traffic demand as an underflow condition. An operator needs to configure appropriate values for the Overflow-Threshold and/or Underflow-Thresholdparametersparameters, and they do not have default values defined in this document.</t><t><t pn="section-4.2-5"> All thresholds in this document could be represented in both absolute value andpercentage,percentage and could be used together. This is provided to accommodatethecases where the LSP bandwidth reservation may become very large or very small over time. For example, an operator may use the percentage threshold to handle small to large bandwidth values and absolute values to handle very large bandwidth values. The auto-bandwidth adjustment is made when either one of the two thresholds, the absolute or percentage, is crossed.</t><t><t pn="section-4.2-6"> When using the (adjustment/overflow/underflow) percentage thresholds, if the LSP bandwidth changes rapidly at very low values, it may trigger frequent auto-bandwidth adjustments due to the crossing of the percentage thresholds. This can lead to unnecessaryre-signalingresignaling of the LSPs in the network. This is suppressed by setting theminimum-thresholdMinimum-Threshold parameters along with the percentage thresholds. The auto-bandwidth adjustment is only made if the LSP bandwidth crosses both the percentage threshold and theminimum-thresholdMinimum-Threshold parameters.</t> </section> <sectiontitle="Scaling Considerations" anchor="sect-4.3"><t>anchor="sect-4.3" numbered="true" toc="include" removeInRFC="false" pn="section-4.3"> <name slugifiedName="name-scaling-considerations">Scaling Considerations</name> <t pn="section-4.3-1"> It should be noted that any bandwidth change requiresre-signalingresignaling of an LSP, which can further trigger preemption oflower prioritylower-priority LSPs in the network. When deployed under scale, this can lead to a signaling churn in the network. TheAuto-bandwidthauto-bandwidth application algorithm is thus advised to take this into consideration before adjusting the LSP bandwidth. Operators are advised to set the values of various auto-bandwidth adjustment parameters appropriate for the deployed LSP scale.</t><t><t pn="section-4.3-2"> If a PCE gets overwhelmed, it can notify the PCC to temporarily suspend the reporting of the new LSP bandwidth to beadjusted (see Section 5.7 of this document).adjusted. Similarly, if a PCC gets overwhelmed due to signaling churn, it can notify the PCE to temporarily suspend new LSP setuprequests (see Section 5.7requests. See <xref target="sect-5.7" format="default" sectionFormat="of" derivedContent="Section 5.7"/> of thisdocument).</t>document.</t> </section> </section> <sectiontitle="PCEP Extensions" anchor="sect-5"><section title="Capability Advertisement" anchor="sect-5.1"><t>anchor="sect-5" numbered="true" toc="include" removeInRFC="false" pn="section-5"> <name slugifiedName="name-pcep-extensions">PCEP Extensions</name> <section anchor="sect-5.1" numbered="true" toc="include" removeInRFC="false" pn="section-5.1"> <name slugifiedName="name-capability-advertisement">Capability Advertisement</name> <t pn="section-5.1-1"> During the PCEPInitialization Phase,initialization phase, PCEP speakers (PCE or PCC) advertise their support ofAutomatic Bandwidththe auto-bandwidth adjustment feature. A PCEP speaker includes the AUTO-BANDWIDTH-CAPABILITYTLV,TLV in the OPENObjectobject to advertise its support for PCEPAuto-Bandwidthauto-bandwidth extensions. The presence of the AUTO-BANDWIDTH-CAPABILITY TLV in the OPENObjectobject indicates that theAutomatic Bandwidthauto-bandwidth feature is supported as described in this document.</t><t><list style="symbols"><t>The<ul spacing="normal" bare="false" empty="false" pn="section-5.1-2"> <li pn="section-5.1-2.1">The PCEP protocol extensions forAuto-Bandwidthauto-bandwidth adjustmentsMUST NOT<bcp14>MUST NOT</bcp14> be used if one or both PCEP speakers have not included the AUTO-BANDWIDTH-CAPABILITY TLV in their respective OPENmessage.</t> <t>Amessage.</li> <li pn="section-5.1-2.2">A PCEP speaker that does not recognize the extensions defined in this document would simply ignore the TLVs as per <xreftarget="RFC5440"/>.</t> <t>Iftarget="RFC5440" format="default" sectionFormat="of" derivedContent="RFC5440"/>.</li> <li pn="section-5.1-2.3">If a PCEP speakerthatsupports the extensions defined in this document but did not advertise this capability, then upon receipt of AUTO-BANDWIDTH-ATTRIBUTES TLV in the LSP Attributes (LSPA) object, itSHOULD<bcp14>SHOULD</bcp14> generate a PCErr witherror-typeError-Type 19 (InvalidOperation), error-value TBD4Operation) and Error-value 14 (Auto-Bandwidth capability was not advertised) and ignore the AUTO-BANDWIDTH-ATTRIBUTESTLV.</t> </list> </t>TLV.</li> </ul> <sectiontitle="AUTO-BANDWIDTH-CAPABILITY TLV" anchor="sect-5.1.1"><t>anchor="sect-5.1.1" numbered="true" toc="include" removeInRFC="false" pn="section-5.1.1"> <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 OPEN Object forAutomatic Bandwidth Adjustmentauto-bandwidth adjustment via PCEP capability advertisement. Its format is shown in the following figure:</t><figure><artwork><![CDATA[<figure anchor="auto-bandwidth-capability-tlv" align="left" suppress-title="false" pn="figure-2"> <name slugifiedName="name-auto-bandwidth-capability-tl">AUTO-BANDWIDTH-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 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=TBD2Type=36 | Length=4 | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ |FlagsFlag |+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ AUTO-BANDWIDTH-CAPABILITY TLV format ]]></artwork>+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+</artwork> </figure><t><t pn="section-5.1.1-3"> TheType of theTLV Type is(TBD2)36, and it has a fixed Length of 4 octets.</t><t><t pn="section-5.1.1-4"> The value comprises a singlefield - Flagsfield: Flag (32 bits). No flags are defined for this TLV in this document.</t><t><t pn="section-5.1.1-5"> Unassigned bits are considered reserved. TheyMUST<bcp14>MUST</bcp14> be set to 0 on transmission andMUST<bcp14>MUST</bcp14> be ignored on receipt.</t><t><t pn="section-5.1.1-6"> Advertisement of the AUTO-BANDWIDTH-CAPABILITY TLV implies support of auto-bandwidth adjustment, as well as the objects,TLVsTLVs, and procedures defined in this document.</t> </section> </section> <sectiontitle="AUTO-BANDWIDTH-ATTRIBUTES TLV" anchor="sect-5.2"><t>anchor="sect-5.2" numbered="true" toc="include" removeInRFC="false" pn="section-5.2"> <name slugifiedName="name-auto-bandwidth-attributes-t">AUTO-BANDWIDTH-ATTRIBUTES TLV</name> <t pn="section-5.2-1"> The AUTO-BANDWIDTH-ATTRIBUTES TLV provides the 'configurable knobs' of thefeaturefeature, and it can be included as an optional TLV in the LSPAObjectobject (as described in <xreftarget="RFC5440"/>).</t> <t>target="RFC5440" format="default" sectionFormat="of" derivedContent="RFC5440"/>).</t> <t pn="section-5.2-2"> ForPCE-Initiateda PCE-initiated LSP <xreftarget="RFC8281"/>,target="RFC8281" format="default" sectionFormat="of" derivedContent="RFC8281"/>, this TLV is included in the LSPAObjectobject with the PCInitiate message. For thePCC-InitiatedPCC-initiated delegated LSPs, this TLV is carried in thePCRptPath Computation State Report (PCRpt) message in the LSPAObject.object. This TLV is also carried in the LSPA object with thePCUpdPath Computation Update Request (PCUpd) message to direct the PCC (LSP head-end) to make updates to auto-bandwidth attributes such as Adjustment-Interval.</t><t><t pn="section-5.2-3"> The TLV is encoded in all PCEP messages for the LSP while the auto-bandwidth adjustment feature isenabled, theenabled. The absence of the TLV indicates the PCEP speaker wishes to disable the feature. This TLV includes multiple AUTO-BANDWIDTH-ATTRIBUTES sub-TLVs. The AUTO-BANDWIDTH-ATTRIBUTES sub-TLVs are included if there is a change since the last information sent in the PCEP message. The default values for missing sub-TLVs apply for the first PCEP message for the LSP.</t><t><t pn="section-5.2-4"> The format of the AUTO-BANDWIDTH-ATTRIBUTES TLV is shown in the following figure:</t><figure><artwork><![CDATA[<figure anchor="AUTO-BANDWIDTH-ATTRIBUTES-TLV" align="left" suppress-title="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 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=TBD1Type=37 | Length | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | | // sub-TLVs // | |+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ AUTO-BANDWIDTH-ATTRIBUTES TLV format ]]></artwork>+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+</artwork> </figure><t><list style="hanging" hangIndent="3"> <t hangText="Type:">TBD1</t> <t hangText="Length:"> The<dl newline="false" spacing="normal" indent="3" pn="section-5.2-6"> <dt pn="section-5.2-6.1">Type:</dt> <dd pn="section-5.2-6.2">37</dd> <dt pn="section-5.2-6.3">Length:</dt> <dd pn="section-5.2-6.4">The Length field defines the length of the value portion inoctetsbytes as per <xreftarget="RFC5440"/>.</t> <t hangText="Value:"> Thistarget="RFC5440" format="default" sectionFormat="of" derivedContent="RFC5440"/>.</dd> <dt pn="section-5.2-6.5">Value:</dt> <dd pn="section-5.2-6.6">This comprises one or moresub-TLVs.</t> </list> </t> <t> Followingsub-TLVs.</dd> </dl> <t pn="section-5.2-7"> The following sub-TLVs are defined in this document:</t><figure><artwork><![CDATA[ Type Len Name ------------------------------------------------------------------- 1 4 Sample-Interval sub-TLV 2 4 Adjustment-Interval sub-TLV 3 4 Down-Adjustment-Interval sub-TLV 4 4 Adjustment-Threshold sub-TLV 5 8 Adjustment-Threshold-Percentage sub-TLV 6 4 Down-Adjustment-Threshold sub-TLV 7 8 Down-Adjustment-Threshold-Percentage sub-TLV 8 4 Minimum-Bandwidth sub-TLV 9 4 Maximum-Bandwidth sub-TLV 10 8 Overflow-Threshold sub-TLV 11 8 Overflow-Threshold-Percentage sub-TLV 12 8 Underflow-Threshold sub-TLV 13 8 Underflow-Threshold-Percentage sub-TLV ]]></artwork> </figure> <t><table anchor="subTLV" align="left" pn="table-2"> <name slugifiedName="name-sub-tlv-types-of-the-auto-b">Sub-TLV Types of the AUTO-BANDWIDTH-ATTRIBUTES TLV</name> <thead> <tr> <th align="left" colspan="1" rowspan="1">Type</th> <th align="left" colspan="1" rowspan="1">Len</th> <th align="left" colspan="1" rowspan="1">Name</th> </tr> </thead> <tbody> <tr> <td align="left" colspan="1" rowspan="1">1</td> <td align="left" colspan="1" rowspan="1">4</td> <td align="left" colspan="1" rowspan="1">Sample-Interval </td> </tr> <tr> <td align="left" colspan="1" rowspan="1">2</td> <td align="left" colspan="1" rowspan="1">4</td> <td align="left" colspan="1" rowspan="1">Adjustment-Interval </td> </tr> <tr> <td align="left" colspan="1" rowspan="1">3</td> <td align="left" colspan="1" rowspan="1">4</td> <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-Percentage </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-Percentage </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-Percentage </td> </tr> </tbody> </table> <t pn="section-5.2-9"> Future specifications can define additional sub-TLVs.</t><t><t pn="section-5.2-10"> The sub-TLVs are encoded to inform the PCEP peer of the various 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 document) or some otheroperator configuredoperator-configured value is used.</t><t><t pn="section-5.2-11"> All sub-TLVs areoptionaloptional, and any unrecognized sub-TLVMUST<bcp14>MUST</bcp14> be ignored. If a sub-TLV of the same type appears more than once, only the first occurrence isprocessedprocessed, and all othersMUST<bcp14>MUST</bcp14> be ignored.</t><t><t pn="section-5.2-12"> The followingsub-sectionssubsections describe the sub-TLVswhichthat are currently definedto beas being carried within the AUTO-BANDWIDTH-ATTRIBUTES TLV.</t> <sectiontitle="Sample-Interval sub-TLV" anchor="sect-5.2.1"><t>anchor="sect-5.2.1" numbered="true" toc="include" removeInRFC="false" pn="section-5.2.1"> <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 secondsatin which traffic samples are collected at the PCC.</t><figure><artwork><![CDATA[<figure anchor="Sample-Interval-sub-TLV" align="left" suppress-title="false" pn="figure-4"> <name slugifiedName="name-sample-interval-sub-tlv-for">Sample-Interval 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 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 | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | Sample-Interval |+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ Sample-Interval sub-TLV format ]]></artwork>+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+</artwork> </figure><t><t pn="section-5.2.1-3"> The Type is 1, the Length is 4 octets, and the value comprisesof - </t> <t><list style="hanging" hangIndent="3"> <t hangText="Sample-Interval:"> Thethe following:</t> <dl newline="false" spacing="normal" indent="3" pn="section-5.2.1-4"> <dt pn="section-5.2.1-4.1">Sample-Interval:</dt> <dd pn="section-5.2.1-4.2">The 4-octet time interval forbandwidth samplethe Bandwidth-Sample collection. The valid range is from 1 to 604800 (7 days), in seconds. The default value is 300 seconds. Due care needs to be taken in a caseofwith a very low Sample-Interval, as it can have some undesirable interactions with transport protocols (see <xreftarget="sect-6.6"/>).target="sect-6.6" format="default" sectionFormat="of" derivedContent="Section 6.6"/>). Thesample-intervalSample-Interval parameterMUST NOT<bcp14>MUST NOT</bcp14> be greater than the (down)adjustment-interval.Adjustment-Interval. In the caseofin which an invalidvalue,value is present, theSub-TLV MUSTsub-TLV <bcp14>MUST</bcp14> be ignored and the previous valueis maintained.</t> </list> </t>will be maintained.</dd> </dl> </section> <sectiontitle="Adjustment Intervals" anchor="sect-5.2.2"><t>anchor="sect-5.2.2" numbered="true" toc="include" removeInRFC="false" pn="section-5.2.2"> <name slugifiedName="name-adjustment-intervals">Adjustment-Intervals</name> <t pn="section-5.2.2-1"> The sub-TLVs in this section are encoded to inform the PCEP peer of theadjustment intervalAdjustment-Interval parameters. The Adjustment-Interval sub-TLV specifies the time interval for both upward (Up-Adjustment-Interval) and downward (Down-Adjustment-Interval) trends. An implementationMAY<bcp14>MAY</bcp14> requireto setthat a differentadjustment interval values forAdjustment-Interval value be set when the bandwidth usage trend is moving downwards from the one used when it is moving upwards. In that case, the operator could use the Down-Adjustment-Intervalsub-TLVsub-TLV, which overrides the Adjustment-Interval value for Down-Adjustment-Interval.</t> <sectiontitle="Adjustment-Interval sub-TLV" anchor="sect-5.2.2.1"><t>anchor="sect-5.2.2.1" numbered="true" toc="include" removeInRFC="false" pn="section-5.2.2.1"> <name slugifiedName="name-adjustment-interval-sub-tlv">Adjustment-Interval Sub-TLV</name> <t pn="section-5.2.2.1-1"> The Adjustment-Interval sub-TLV specifies a time interval in secondsatin which a bandwidth adjustment should be made in an upward or downward direction. This sub-TLVspecifyspecifies the value for Up-Adjustment-Interval and Down-Adjustment-Interval when they are the same and when the Down-Adjustment-Interval sub-TLV is not included.</t><figure><artwork><![CDATA[<figure anchor="Adjustment-Interval-sub-TLV" align="left" suppress-title="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 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 | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | Adjustment-Interval |+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ Adjustment-Interval sub-TLV format ]]></artwork>+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+</artwork> </figure><t>The<t pn="section-5.2.2.1-3">The Type is 2, the Length is 4 octets, and the value comprisesof - </t> <t><list style="hanging" hangIndent="3"> <t hangText="Adjustment-Interval:"> Thethe following:</t> <dl newline="false" spacing="normal" indent="3" pn="section-5.2.2.1-4"> <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 bandwidth adjustments. The valid range is from 1 to 604800 (7 days), in seconds. The default value is 86400 seconds (1 day). Theadjustment-intervalAdjustment-Interval parameterMUST NOT<bcp14>MUST NOT</bcp14> be less than thesample-interval, otherwiseSample-Interval; otherwise, theSub-TLV MUSTsub-TLV <bcp14>MUST</bcp14> beignoredignored, and the previous valueis maintained.</t> </list> </t>will be maintained.</dd> </dl> </section> <sectiontitle="Down-Adjustment-Interval sub-TLV" anchor="sect-5.2.2.2"><t>anchor="sect-5.2.2.2" numbered="true" toc="include" removeInRFC="false" pn="section-5.2.2.2"> <name slugifiedName="name-down-adjustment-interval-su">Down-Adjustment-Interval Sub-TLV</name> <t pn="section-5.2.2.2-1"> The Down-Adjustment-Interval sub-TLV specifies a time interval in secondsatin which a bandwidth adjustment should be made when MaxAvgBw is less than the current bandwidth reservation of the LSP. This parameter overrides the Adjustment-Interval for the downward trend. This sub-TLV is used only when there is a need for differentadjustment intervalsAdjustment-Intervals in the upward and downward directions.</t><figure><artwork><![CDATA[<figure anchor="Down-Adjustment-Interval-sub-TLV" align="left" suppress-title="false" pn="figure-6"> <name slugifiedName="name-down-adjustment-interval-sub">Down-Adjustment-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 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 | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | Down-Adjustment-Interval |+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ Down-Adjustment-Interval sub-TLV format ]]></artwork>+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+</artwork> </figure><t>The<t pn="section-5.2.2.2-3">The Type is 3, the Length is 4 octets, and the value comprisesof -the following: </t><t><list style="hanging" hangIndent="3"> <t hangText="Down-Adjustment-Interval:"> The<dl newline="false" spacing="normal" indent="3" pn="section-5.2.2.2-4"> <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 interval for downward bandwidth adjustments. The valid range is from 1 to 604800 (7 days), in seconds. The default value equals theadjustment-interval.Adjustment-Interval. Thedown-adjustment-intervalDown-Adjustment-Interval parameterMUST NOT<bcp14>MUST NOT</bcp14> be less than thesample-interval, otherwiseSample-Interval; otherwise, theSub-TLV MUSTsub-TLV <bcp14>MUST</bcp14> be ignored and the previous valueis maintained.</t> </list> </t>will be maintained.</dd> </dl> </section> </section> <sectiontitle="Adjustment Thresholds" anchor="sect-5.2.3"><t>anchor="sect-5.2.3" numbered="true" toc="include" removeInRFC="false" pn="section-5.2.3"> <name slugifiedName="name-adjustment-thresholds">Adjustment-Thresholds</name> <t pn="section-5.2.3-1"> The sub-TLVs in this section are encoded to inform the PCEP peer of theadjustment thresholdAdjustment-Threshold parameters. An implementationMAY<bcp14>MAY</bcp14> include both sub-TLVs for the absolute value and the percentage, in which case the bandwidth is adjusted when either of theadjustment thresholdAdjustment-Threshold conditions are met. The Adjustment-Threshold sub-TLV specifies the threshold for both upward (Up-Adjustment-Threshold) and downward (Down-Adjustment-Threshold)trend.trends. If the operator would like to use a differentadjustment thresholdAdjustment-Threshold during the downward trend, the Down-Adjustment-Threshold sub-TLV is included. Similarly, the Adjustment-Threshold-Percentage sub-TLV specifies the threshold percentage for both upward and downwardtrend.trends. If the operator would like to use a differentadjustment thresholdAdjustment-Threshold percentage during the downward trend, the Down-Adjustment-Threshold-Percentage sub-TLV is included. It is worth noting that regardless of how thethresholdthresholds are set, the adjustment will not be made until at least onesample-intervalSample-Interval has passed simply because no sample will be made on which to base a comparison with a threshold.</t> <sectiontitle="Adjustment-Threshold sub-TLV" anchor="sect-5.2.3.1"><t> Theanchor="sect-5.2.3.1" numbered="true" toc="include" removeInRFC="false" pn="section-5.2.3.1"> <name slugifiedName="name-adjustment-threshold-sub-tl">Adjustment-Threshold Sub-TLV</name> <t pn="section-5.2.3.1-1">The Adjustment-Threshold sub-TLV is used to decide when the LSP bandwidth should be adjusted in an upward or downward direction. This sub-TLVspecifyspecifies the absolute value for Up-Adjustment-Threshold and Down-Adjustment-Threshold when they are the same and when the Down-Adjustment-Threshold sub-TLV is not included.</t><figure><artwork><![CDATA[<figure anchor="Adjustment-Threshold-sub-TLV" align="left" suppress-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 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 | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | Adjustment-Threshold |+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ Adjustment-Threshold sub-TLV format ]]></artwork>+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+</artwork> </figure><t><t pn="section-5.2.3.1-3"> The Type is 4, the Length is 4 octets, and the value comprisesof -the following: </t><t><list style="hanging" hangIndent="3"> <t hangText="Adjustment-Threshold:"> The<dl newline="false" spacing="normal" indent="3" pn="section-5.2.3.1-4"> <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 bandwidth difference value, encoded in IEEE floating point format (see[<xref target="IEEE.754.1985"/>]),<xref target="IEEE.754.1985" format="default" sectionFormat="of" derivedContent="IEEE.754.1985"/>) and expressed in bytes per second. The defaultadjustment-thresholdAdjustment-Threshold value is not set. Refer toSection 3.1.2 of<xreftarget="RFC3471"/>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 usedvalues.</t> </list> </t> <t>values.</dd> </dl> <t pn="section-5.2.3.1-5"> If the modulus of difference between the current MaxAvgBw and the current bandwidth reservation is greater than or equal to the threshold value, the LSP bandwidth is adjusted to the current bandwidth demand (MaxAvgBw).</t><t><t pn="section-5.2.3.1-6"> In the caseofin which an invalidvalue,value is present, theSub-TLV MUSTsub-TLV <bcp14>MUST</bcp14> be ignored and the previous valueiswill be maintained.</t> </section> <sectiontitle="Adjustment-Threshold-Percentage sub-TLV" anchor="sect-5.2.3.2"><t> Theanchor="sect-5.2.3.2" numbered="true" toc="include" removeInRFC="false" pn="section-5.2.3.2"> <name slugifiedName="name-adjustment-threshold-percen">Adjustment-Threshold-Percentage Sub-TLV</name> <t pn="section-5.2.3.2-1">The Adjustment-Threshold-Percentage sub-TLV is used to decide when the LSP bandwidth should be adjusted in an upward or downward direction. This sub-TLVspecifyspecifies the percentage value for Up-Adjustment-Threshold and Down-Adjustment-Threshold when they are the same and when the Down-Adjustment-Threshold-Percentage sub-TLV is not included.</t><figure><artwork><![CDATA[<figure anchor="Adjustment-Threshold-Percentage-sub-TLV" align="left" 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 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 | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | Reserved | Percentage | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | Minimum-Threshold |+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ Adjustment-Threshold-Percentage sub-TLV format ]]></artwork>+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+</artwork> </figure><t>The<t pn="section-5.2.3.2-3">The Type is 5, the Length is 8 octets, and the value comprisesof -the following: </t><t><list style="hanging" hangIndent="3"> <t hangText="Reserved:"> MUST<dl newline="false" spacing="normal" indent="3" pn="section-5.2.3.2-4"> <dt pn="section-5.2.3.2-4.1">Reserved:</dt> <dd pn="section-5.2.3.2-4.2"> <bcp14>MUST</bcp14> be set to zero on transmission andMUST<bcp14>MUST</bcp14> be ignored onreceipt.</t> <t hangText="Percentage:"> Thereceipt.</dd> <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 bits), encoded in a percentage (an integer from 1 to 100). The value 0 is considered to be invalid. The default value is 5percent.</t> <t hangText="Minimum-Threshold:"> Thepercent.</dd> <dt pn="section-5.2.3.2-4.5">Minimum-Threshold:</dt> <dd pn="section-5.2.3.2-4.6">The absolute Minimum-Threshold bandwidth value, encoded in IEEE floating point format (see[<xref target="IEEE.754.1985"/>]),<xref target="IEEE.754.1985" format="default" sectionFormat="of" derivedContent="IEEE.754.1985"/>) and expressed in bytes per second. The increase or decrease of the LSP bandwidthMUST<bcp14>MUST</bcp14> be atleastor above theminimum-thresholdMinimum-Threshold before the bandwidth adjustment is made. The default value is0.</t> </list> </t> <t>0.</dd> </dl> <t pn="section-5.2.3.2-5"> If the percentage absolute difference between the current MaxAvgBw and the current bandwidth reservation is greater than or equal to the thresholdpercentage,percentage and the difference in the bandwidth is atleastor above the Minimum-Threshold, the LSP bandwidth is adjusted to the current bandwidth demand (MaxAvgBw).</t><t><t pn="section-5.2.3.2-6"> In the caseofin which an invalidvalue,value is present, theSub-TLV MUSTsub-TLV <bcp14>MUST</bcp14> be ignored and the previous valueiswill be maintained.</t> </section> <sectiontitle="Down-Adjustment-Threshold sub-TLV" anchor="sect-5.2.3.3"><t> Theanchor="sect-5.2.3.3" numbered="true" toc="include" removeInRFC="false" pn="section-5.2.3.3"> <name slugifiedName="name-down-adjustment-threshold-s">Down-Adjustment-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 islesserless than the current bandwidth reservation. This parameter overrides the Adjustment-Threshold for the downward trend. This sub-TLV is used only when there is a need for a different threshold in the upward and downward directions.</t><figure><artwork><![CDATA[<figure anchor="Down-Adjustment-Threshold-sub-TLV" align="left" suppress-title="false" pn="figure-9"> <name slugifiedName="name-down-adjustment-threshold-su">Down-Adjustment-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 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 | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | Down-Adjustment-Threshold |+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ Down-Adjustment-Threshold sub-TLV format ]]></artwork>+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+</artwork> </figure><t>The<t pn="section-5.2.3.3-3">The Type is 6, the Length is 4 octets, and the value comprisesof -the following: </t><t><list style="hanging" hangIndent="3"> <t hangText="Down-Adjustment-Threshold:"> The<dl newline="false" spacing="normal" indent="3" pn="section-5.2.3.3-4"> <dt pn="section-5.2.3.3-4.1">Down-Adjustment-Threshold:</dt> <dd pn="section-5.2.3.3-4.2">The absolute Down-Adjustment-Threshold bandwidth value, encoded in IEEE floating point format (see[<xref target="IEEE.754.1985"/>]),<xref target="IEEE.754.1985" format="default" sectionFormat="of" derivedContent="IEEE.754.1985"/>) and expressed in bytes per second. The default value equals theadjustment-threshold.Adjustment-Threshold. Refer toSection 3.1.2 of<xreftarget="RFC3471"/>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.</t> </list> </t> <t></dd> </dl> <t pn="section-5.2.3.3-5"> If the difference between the current bandwidth reservation and the current MaxAvgBw is greater than or equal to the threshold value, the LSP bandwidth is adjusted to the current bandwidth demand (MaxAvgBw).</t><t><t pn="section-5.2.3.3-6"> In the caseofin which an invalidvalue,value is present, theSub-TLV MUSTsub-TLV <bcp14>MUST</bcp14> be ignored and the previous valueiswill be maintained.</t> </section> <sectiontitle="Down-Adjustment-Threshold-Percentage sub-TLV" anchor="sect-5.2.3.4"><t>anchor="sect-5.2.3.4" numbered="true" toc="include" removeInRFC="false" pn="section-5.2.3.4"> <name slugifiedName="name-down-adjustment-threshold-p">Down-Adjustment-Threshold-Percentage Sub-TLV</name> <t pn="section-5.2.3.4-1"> The Down-Adjustment-Threshold-Percentage sub-TLV is used to decide when the LSP bandwidth should be adjusted when MaxAvgBw islesserless than the current bandwidth reservation. This parameter overrides the Adjustment-Threshold-Percentage for the downward trend. This sub-TLV is used only when there is a need for a different threshold percentage in the upward and downward directions.</t><figure><artwork><![CDATA[<figure anchor="Down-Adjustment-Threshold-Percentage-sub-TLV" align="left" suppress-title="false" pn="figure-10"> <name slugifiedName="name-down-adjustment-threshold-pe">Down-Adjustment-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 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 | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | Reserved | Percentage | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | Minimum-Threshold |+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ Down-Adjustment-Threshold-Percentage sub-TLV format ]]></artwork>+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+</artwork> </figure><t>The<t pn="section-5.2.3.4-3">The Type is 7, the Length is 8 octets, and the value comprisesof -</t> <t><list style="hanging" hangIndent="3"> <t hangText="Reserved:"> MUSTthe following:</t> <dl newline="false" spacing="normal" indent="3" pn="section-5.2.3.4-4"> <dt pn="section-5.2.3.4-4.1">Reserved:</dt> <dd pn="section-5.2.3.4-4.2"> <bcp14>MUST</bcp14> be set to zero on transmission andMUST<bcp14>MUST</bcp14> be ignored onreceipt.</t> <t hangText="Percentage:"> Thereceipt.</dd> <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 (7 bits), encoded in a percentage (an integer from 1 to 100). The value 0 is considered to be invalid. The default value equals theadjustment-threshold-percentage.</t> <t hangText="Minimum-Threshold:"> TheAdjustment-Threshold-Percentage.</dd> <dt pn="section-5.2.3.4-4.5">Minimum-Threshold:</dt> <dd pn="section-5.2.3.4-4.6">The absolute Minimum-Threshold bandwidth value, encoded in IEEE floating point format (see[<xref target="IEEE.754.1985"/>]),<xref target="IEEE.754.1985" format="default" sectionFormat="of" derivedContent="IEEE.754.1985"/>) and expressed in bytes per second. The decrease of the LSP bandwidthMUST<bcp14>MUST</bcp14> be atleastor above theminimum-thresholdMinimum-Threshold before the bandwidth adjustment is made. The default value equals theminimum-thresholdMinimum-Threshold for theadjustment-threshold-percentage.</t> </list> </t> <t>Adjustment-Threshold-Percentage.</dd> </dl> <t pn="section-5.2.3.4-5"> If the percentage difference between the current bandwidth reservation and the current MaxAvgBw is greater than or equal to the thresholdpercentage,percentage and the difference in the bandwidth is atleastor above the Minimum-Threshold, the LSP bandwidth is adjusted to the current bandwidth demand (MaxAvgBw).</t><t><t pn="section-5.2.3.4-6"> In the caseofin which an invalidvalue,value is present, theSub-TLV MUSTsub-TLV <bcp14>MUST</bcp14> be ignored and the previous valueiswill be maintained.</t> </section> </section> <sectiontitle="Minimumanchor="sect-5.2.4" numbered="true" toc="include" removeInRFC="false" pn="section-5.2.4"> <name slugifiedName="name-minimum-and-maximum-bandwid">Minimum andMaximum Bandwidth Values" anchor="sect-5.2.4"><section title="Minimum-Bandwidth sub-TLV" anchor="sect-5.2.4.1"><t>Maximum-Bandwidth Values</name> <section anchor="sect-5.2.4.1" numbered="true" toc="include" removeInRFC="false" pn="section-5.2.4.1"> <name slugifiedName="name-minimum-bandwidth-sub-tlv">Minimum-Bandwidth Sub-TLV</name> <t pn="section-5.2.4.1-1"> The Minimum-Bandwidth sub-TLVspecifyspecifies theminimum bandwidthMinimum-Bandwidth allowed for theLSP,LSP and is expressed in bytes per second. The LSP bandwidth cannot be adjusted below theminimum bandwidthMinimum-Bandwidth value.</t><figure><artwork><![CDATA[<figure anchor="Minimum-Bandwidth-sub-TLV" align="left" suppress-title="false" pn="figure-11"> <name slugifiedName="name-minimum-bandwidth-sub-tlv-f">Minimum-Bandwidth 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 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 | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | Minimum-Bandwidth |+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ Minimum-Bandwidth sub-TLV format ]]></artwork>+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+</artwork> </figure><t>The<t pn="section-5.2.4.1-3">The Type is 8, the Length is 4 octets, and the value comprisesof -the following: </t><t><list style="hanging" hangIndent="3"> <t hangText="Minimum-Bandwidth:"> The<dl newline="false" spacing="normal" indent="3" pn="section-5.2.4.1-4"> <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 in IEEE floating point format (see[<xref target="IEEE.754.1985"/>]),<xref target="IEEE.754.1985" format="default" sectionFormat="of" derivedContent="IEEE.754.1985"/>) and expressed in bytes per second. The defaultminimum-bandwidthMinimum-Bandwidth value is set to 0. Refer toSection 3.1.2 of<xreftarget="RFC3471"/>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 usedvalues.</t> </list> </t> <t>values.</dd> </dl> <t pn="section-5.2.4.1-5"> In the caseofin which an invalidvalue,value is present, theSub-TLV MUSTsub-TLV <bcp14>MUST</bcp14> be ignored and the previous valueiswill be maintained.</t> </section> <sectiontitle="Maximum-Bandwidth sub-TLV" anchor="sect-5.2.4.2"><t>anchor="sect-5.2.4.2" numbered="true" toc="include" removeInRFC="false" pn="section-5.2.4.2"> <name slugifiedName="name-maximum-bandwidth-sub-tlv">Maximum-Bandwidth Sub-TLV</name> <t pn="section-5.2.4.2-1"> The Maximum-Bandwidth sub-TLVspecifyspecifies themaximum bandwidthMaximum-Bandwidth allowed for theLSP,LSP and is expressed in bytes per second. The LSP bandwidth cannot be adjusted above themaximum bandwidthMaximum-Bandwidth value.</t><figure><artwork><![CDATA[<figure anchor="Maximum-Bandwidth-sub-TLV" align="left" suppress-title="false" pn="figure-12"> <name slugifiedName="name-maximum-bandwidth-sub-tlv-f">Maximum-Bandwidth 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 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 | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | Maximum-Bandwidth |+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ Maximum-Bandwidth sub-TLV format ]]></artwork>+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+</artwork> </figure><t>The<t pn="section-5.2.4.2-3">The Type is 9, the Length is 4 octets, and the value comprisesof -the following: </t><t><list style="hanging" hangIndent="3"> <t hangText="Maximum-Bandwidth:"> The<dl newline="false" spacing="normal" indent="3" pn="section-5.2.4.2-4"> <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 in IEEE floating point format (see[<xref target="IEEE.754.1985"/>]),<xref target="IEEE.754.1985" format="default" sectionFormat="of" derivedContent="IEEE.754.1985"/>) and expressed in bytes per second. The defaultmaximum-bandwidthMaximum-Bandwidth value is not set. Refer toSection 3.1.2 of<xreftarget="RFC3471"/>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 usedvalues.</t> </list> </t> <t>values.</dd> </dl> <t pn="section-5.2.4.2-5"> In the caseofin which an invalidvalue,value is present, theSub-TLV MUSTsub-TLV <bcp14>MUST</bcp14> be ignored and the previous valueiswill be maintained.</t> </section> </section> <sectiontitle="Overflowanchor="sect-5.2.5" numbered="true" toc="include" removeInRFC="false" pn="section-5.2.5"> <name slugifiedName="name-overflow-and-underflow-cond">Overflow and UnderflowConditions" anchor="sect-5.2.5"><t>Conditions</name> <t pn="section-5.2.5-1"> The sub-TLVs in this section are encoded to inform the PCEP peer of the overflow and underflow threshold parameters. An implementationMAY<bcp14>MAY</bcp14> include sub-TLVs for an absolute value and/or a percentage for the threshold, in which case the bandwidth is immediately adjusted when either of the threshold conditions is met consecutively for the given count (as long as the difference in the bandwidth is atleastor above the Minimum-Threshold). By default, the threshold values for overflow and underflow conditions are not set.</t> <sectiontitle="Overflow-Threshold sub-TLV" anchor="sect-5.2.5.1"><t>anchor="sect-5.2.5.1" numbered="true" toc="include" removeInRFC="false" pn="section-5.2.5.1"> <name slugifiedName="name-overflow-threshold-sub-tlv">Overflow-Threshold Sub-TLV</name> <t pn="section-5.2.5.1-1"> The Overflow-Threshold sub-TLV is used to decide if the LSP bandwidth should be adjusted immediately.</t><figure><artwork><![CDATA[<figure anchor="Overflow-Threshold-sub-TLV" align="left" suppress-title="false" pn="figure-13"> <name slugifiedName="name-overflow-threshold-sub-tlv-">Overflow-Threshold 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 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 | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | Reserved | Count | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | Overflow-Threshold |+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ Overflow-Threshold sub-TLV format ]]></artwork>+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+</artwork> </figure><t>The<t pn="section-5.2.5.1-3">The Type is 10, the Length is 8 octets, and the value comprisesof -the following: </t><t><list style="hanging" hangIndent="3"> <t hangText="Reserved:"> MUST<dl newline="false" spacing="normal" indent="3" pn="section-5.2.5.1-4"> <dt pn="section-5.2.5.1-4.1">Reserved:</dt> <dd pn="section-5.2.5.1-4.2"> <bcp14>MUST</bcp14> be set to zero on transmission andMUST<bcp14>MUST</bcp14> be ignored onreceipt.</t> <t hangText="Count:"> Thereceipt.</dd> <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), encoded in an integer. The value 0 is considered to be invalid. The number of consecutive samples for which the overflow conditionMUST<bcp14>MUST</bcp14> be met for the LSP bandwidth is to be immediately adjusted to the current bandwidth demand, bypassing the (up)adjustment-interval.</t> <t hangText="Overflow-Threshold:">Adjustment-Interval.</dd> <dt pn="section-5.2.5.1-4.5">Overflow-Threshold:</dt> <dd pn="section-5.2.5.1-4.6"> The absolute Overflow-Threshold bandwidth value, encoded in IEEE floating point format (see[<xref target="IEEE.754.1985"/>]),<xref target="IEEE.754.1985" format="default" sectionFormat="of" derivedContent="IEEE.754.1985"/>) and expressed in bytes per second. Refer toSection 3.1.2 of<xreftarget="RFC3471"/>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 differenceofbetween the current MaxAvgBwfromand the current bandwidth reservation is greater than or equal to the threshold value, the overflow condition ismet.</t> </list> </t> <t>met.</dd> </dl> <t pn="section-5.2.5.1-5"> In the caseofin which an invalidvalue,value is present, theSub-TLV MUSTsub-TLV <bcp14>MUST</bcp14> be ignored and the previous valueiswill be maintained.</t> </section> <sectiontitle="Overflow-Threshold-Percentage sub-TLV" anchor="sect-5.2.5.2"><t>anchor="sect-5.2.5.2" numbered="true" toc="include" removeInRFC="false" pn="section-5.2.5.2"> <name slugifiedName="name-overflow-threshold-percenta">Overflow-Threshold-Percentage Sub-TLV</name> <t pn="section-5.2.5.2-1"> The Overflow-Threshold-Percentage sub-TLV is used to decide if the LSP bandwidth should be adjusted immediately.</t><figure><artwork><![CDATA[<figure anchor="Overflow-Threshold-Percentage-sub-TLV" align="left" suppress-title="false" pn="figure-14"> <name slugifiedName="name-overflow-threshold-percentag">Overflow-Threshold-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 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 | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | Percentage | Reserved | Count | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | Minimum-Threshold |+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ Overflow-Threshold-Percentage sub-TLV format ]]></artwork>+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+</artwork> </figure><t>The<t pn="section-5.2.5.2-3">The Type is 11, the Length is 8 octets, and the value comprisesof -</t> <t><list style="hanging" hangIndent="3"> <t hangText="Percentage:"> Thethe following:</t> <dl newline="false" spacing="normal" indent="3" pn="section-5.2.5.2-4"> <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), encoded in a 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 current bandwidth reservation is greater than or equal to the threshold percentage, the overflow condition ismet.</t> <t hangText="Reserved:"> MUSTmet.</dd> <dt pn="section-5.2.5.2-4.3">Reserved:</dt> <dd pn="section-5.2.5.2-4.4"> <bcp14>MUST</bcp14> be set to zero on transmission andMUST<bcp14>MUST</bcp14> be ignored onreceipt.</t> <t hangText="Count:"> Thereceipt.</dd> <dt pn="section-5.2.5.2-4.5">Count:</dt> <dd pn="section-5.2.5.2-4.6">The Overflow-Count value (5 bits), encoded in an integer. The value 0 is considered to be invalid. The number of consecutive samples for which the overflow conditionMUST<bcp14>MUST</bcp14> be met for the LSP bandwidth is to be immediately adjusted to the current bandwidth demand, bypassing the (up)adjustment-interval.</t> <t hangText="Minimum-Threshold:"> TheAdjustment-Interval.</dd> <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 bandwidth value, encoded in IEEE floating point format (see[<xref target="IEEE.754.1985"/>]),<xref target="IEEE.754.1985" format="default" sectionFormat="of" derivedContent="IEEE.754.1985"/>) and expressed in bytes per second. The increase of the LSP bandwidthMUST<bcp14>MUST</bcp14> be atleastor above theminimum-thresholdMinimum-Threshold before the bandwidth adjustment ismade.</t> </list> </t> <t>made.</dd> </dl> <t pn="section-5.2.5.2-5"> In the caseofin which an invalidvalue,value is present, theSub-TLV MUSTsub-TLV <bcp14>MUST</bcp14> be ignored and the previous valueiswill be maintained.</t> </section> <sectiontitle="Underflow-Threshold sub-TLV" anchor="sect-5.2.5.3"><t>anchor="sect-5.2.5.3" numbered="true" toc="include" removeInRFC="false" pn="section-5.2.5.3"> <name slugifiedName="name-underflow-threshold-sub-tlv">Underflow-Threshold Sub-TLV</name> <t pn="section-5.2.5.3-1"> The Underflow-Threshold sub-TLV is used to decide if the LSP bandwidth should be adjusted immediately.</t><figure><artwork><![CDATA[<figure anchor="Underflow-Threshold-sub-TLV" align="left" suppress-title="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 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 | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | Reserved | Count | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | Underflow-Threshold |+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ Underflow-Threshold sub-TLV format ]]></artwork>+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+</artwork> </figure><t>The<t pn="section-5.2.5.3-3">The Type is 12, the Length is 8 octets, and the value comprisesof -the following: </t><t><list style="hanging" hangIndent="3"> <t hangText="Reserved:"> MUST<dl newline="false" spacing="normal" indent="3" pn="section-5.2.5.3-4"> <dt pn="section-5.2.5.3-4.1">Reserved:</dt> <dd pn="section-5.2.5.3-4.2"> <bcp14>MUST</bcp14> be set to zero on transmission andMUST<bcp14>MUST</bcp14> be ignored onreceipt.</t> <t hangText="Count:">receipt.</dd> <dt pn="section-5.2.5.3-4.3">Count:</dt> <dd pn="section-5.2.5.3-4.4"> The Underflow-Count value (5 bits), encoded in an integer. The value 0 is considered to be invalid. The number of consecutive samples for which the underflow conditionMUST<bcp14>MUST</bcp14> be met for the LSP bandwidth is to be immediately adjusted to the current bandwidth demand, bypassing thedown-adjustment-interval.</t> <t hangText="Underflow-Threshold:">Down-Adjustment-Interval.</dd> <dt pn="section-5.2.5.3-4.5">Underflow-Threshold:</dt> <dd pn="section-5.2.5.3-4.6"> The absolute Underflow-Threshold bandwidth value, encoded in IEEE floating point format (see[<xref target="IEEE.754.1985"/>]),<xref target="IEEE.754.1985" format="default" sectionFormat="of" derivedContent="IEEE.754.1985"/>) and expressed in bytes per second. Refer toSection 3.1.2 of<xreftarget="RFC3471"/>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 differenceofbetween the current MaxAvgBwfromand the current bandwidth reservation is greater than or equal to the threshold value, the underflow condition ismet.</t> </list> </t> <t>met.</dd> </dl> <t pn="section-5.2.5.3-5"> In the caseofin which an invalidvalue,value is present, theSub-TLV MUSTsub-TLV <bcp14>MUST</bcp14> be ignored and the previous valueiswill be maintained.</t> </section> <sectiontitle="Underflow-Threshold-Percentage sub-TLV" anchor="sect-5.2.5.4"><t>anchor="sect-5.2.5.4" numbered="true" toc="include" removeInRFC="false" pn="section-5.2.5.4"> <name slugifiedName="name-underflow-threshold-percent">Underflow-Threshold-Percentage Sub-TLV</name> <t pn="section-5.2.5.4-1"> The Underflow-Threshold-Percentage sub-TLV is used to decide if the LSP bandwidth should be adjusted immediately.</t><figure><artwork><![CDATA[<figure anchor="Underflow-Threshold-Percentage-sub-TLV" align="left" 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 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 | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | Percentage | Reserved | Count | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | Minimum-Threshold |+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ Underflow-Threshold-Percentage sub-TLV format ]]></artwork>+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+</artwork> </figure><t>The<t pn="section-5.2.5.4-3">The Type is 13, the Length is 8 octets, and the value comprisesof -</t> <t><list style="hanging" hangIndent="3"> <t hangText="Percentage:">the following:</t> <dl newline="false" spacing="normal" indent="3" pn="section-5.2.5.4-4"> <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 bits), encoded in percentage (an integer from 1 to 100). The value 0 is considered to be invalid. If the percentage decrease of the current MaxAvgBw from the current bandwidth reservation is greater than or equal to the threshold percentage, the underflow condition ismet.</t> <t hangText="Reserved:"> MUSTmet.</dd> <dt pn="section-5.2.5.4-4.3">Reserved:</dt> <dd pn="section-5.2.5.4-4.4"> <bcp14>MUST</bcp14> be set to zero on transmission andMUST<bcp14>MUST</bcp14> be ignored onreceipt.</t> <t hangText="Count:">receipt.</dd> <dt pn="section-5.2.5.4-4.5">Count:</dt> <dd pn="section-5.2.5.4-4.6"> The Underflow-Count value (5 bits), encoded in an integer. The value 0 is considered to be invalid. The number of consecutive samples for which the underflow conditionMUST<bcp14>MUST</bcp14> be met for the LSP bandwidth is to be immediately adjusted to the current bandwidth demand, bypassing thedown-adjustment-interval.</t> <t hangText="Minimum-Threshold:">Down-Adjustment-Interval.</dd> <dt pn="section-5.2.5.4-4.7">Minimum-Threshold:</dt> <dd pn="section-5.2.5.4-4.8"> The absolute Minimum-Threshold bandwidth value, encoded in IEEE floating point format (see[<xref target="IEEE.754.1985"/>]),<xref target="IEEE.754.1985" format="default" sectionFormat="of" derivedContent="IEEE.754.1985"/>) and expressed in bytes per second. The decrease of the LSP bandwidthMUST<bcp14>MUST</bcp14> be atleastor above theminimum-thresholdMinimum-Threshold before the bandwidth adjustment ismade.</t> </list> </t> <t>made.</dd> </dl> <t pn="section-5.2.5.4-5"> In the caseofin which an invalidvalue,value is present, theSub-TLV MUSTsub-TLV <bcp14>MUST</bcp14> be ignored and the previous valueiswill be maintained.</t> </section> </section> </section> <sectiontitle="BANDWIDTH Object" anchor="sect-5.3"><t>anchor="sect-5.3" numbered="true" toc="include" removeInRFC="false" pn="section-5.3"> <name slugifiedName="name-bandwidth-object">BANDWIDTH Object</name> <t pn="section-5.3-1"> As per <xreftarget="RFC5440"/>,target="RFC5440" format="default" sectionFormat="of" derivedContent="RFC5440"/>, the BANDWIDTH object (Object-Class value 5) is defined with two Object-Type values asfollowing:</t> <t><list style="hanging" hangIndent="3"> <t hangText="Requested Bandwidth:">follows:</t> <dl newline="false" spacing="normal" indent="3" pn="section-5.3-2"> <dt pn="section-5.3-2.1">Requested Bandwidth:</dt> <dd pn="section-5.3-2.2">The BANDWIDTH Object-Type value is1.</t> <t hangText="Re-optimization Bandwidth:"> Bandwidth1.</dd> <dt pn="section-5.3-2.3">Reoptimization Bandwidth:</dt> <dd pn="section-5.3-2.4">The bandwidth of an existing TE LSP for which are-optimizationreoptimization is requested. The BANDWIDTH Object-Type value is2.</t> </list> </t> <t>2.</dd> </dl> <t pn="section-5.3-3"> The PCC reports the calculated bandwidth to be adjusted (MaxAvgBw) to theStatefulstateful PCE using the existing 'Requested Bandwidth' with the BANDWIDTH Object-Type as 1. The reporting of the're-optimization'reoptimization bandwidth' with BANDWIDTH Object-Type as 2 is not required as theStatefulstateful PCE is aware of the existing LSP bandwidth.</t> </section> <sectiontitle="Theanchor="sect-5.4" numbered="true" toc="include" removeInRFC="false" pn="section-5.4"> <name slugifiedName="name-the-pcinitiate-message">The PCInitiateMessage" anchor="sect-5.4"><t>Message</name> <t pn="section-5.4-1"> A PCInitiate message is a PCEP message sent by a PCE to a PCC to trigger LSP instantiation or deletion <xreftarget="RFC8281"/>.</t> <t>target="RFC8281" format="default" sectionFormat="of" derivedContent="RFC8281"/>.</t> <t pn="section-5.4-2"> For thePCE-InitiatedPCE-initiated LSP withAuto-Bandwidththe auto-bandwidth feature enabled, AUTO-BANDWIDTH-ATTRIBUTES TLVMUST<bcp14>MUST</bcp14> be included in the LSPA object with the PCInitiate message.</t><t><t pn="section-5.4-3"> The Routing Backus-NaurFormatForm (RBNF) definition of the PCInitiate message <xreftarget="RFC8281"/>target="RFC8281" format="default" sectionFormat="of" derivedContent="RFC8281"/> is unchanged by this document.</t> </section> <sectiontitle="Theanchor="sect-5.5" numbered="true" toc="include" removeInRFC="false" pn="section-5.5"> <name slugifiedName="name-the-pcupd-message">The PCUpdMessage" anchor="sect-5.5"><t>Message</name> <t pn="section-5.5-1"> A PCUpd message is a PCEP message sent by a PCE to a PCC to update the LSP parameters <xreftarget="RFC8231"/>.</t> <t>target="RFC8231" format="default" sectionFormat="of" derivedContent="RFC8231"/>.</t> <t pn="section-5.5-2"> ForPCE-InitiatedPCE-initiated LSPs withAuto-Bandwidththe auto-bandwidth feature enabled, the AUTO-BANDWIDTH-ATTRIBUTES TLVMUST<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 auto-bandwidth parameters.</t><t><t pn="section-5.5-3"> The RBNF definition of the PCUpd message <xreftarget="RFC8231"/>target="RFC8231" format="default" sectionFormat="of" derivedContent="RFC8231"/> is unchanged by this document.</t> </section> <sectiontitle="Theanchor="sect-5.6" numbered="true" toc="include" removeInRFC="false" pn="section-5.6"> <name slugifiedName="name-the-pcrpt-message">The PCRptMessage" anchor="sect-5.6"><t>Message</name> <t pn="section-5.6-1"> The PCRpt message <xreftarget="RFC8231"/>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><t><t pn="section-5.6-2"> ForPCE-InitiatedPCE-initiated LSPs <xreftarget="RFC8281"/>,target="RFC8281" format="default" sectionFormat="of" derivedContent="RFC8281"/>, the PCC creates the LSP using the attributes communicated by thePCE,PCE andusingthe local values for the unspecified parameters. After the successful instantiation of 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><t><t pn="section-5.6-3"> For bothPCE-InitiatedPCE-initiated andPCC-InitiatedPCC-initiated LSPs, when the LSP is 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 specify the requested bandwidth in the PCRpt message.</t><t><t pn="section-5.6-4"> The RBNF definition of the PCRpt message <xreftarget="RFC8231"/>target="RFC8231" format="default" sectionFormat="of" derivedContent="RFC8231"/> is unchanged by this document.</t> </section> <sectiontitle="Theanchor="sect-5.7" numbered="true" toc="include" removeInRFC="false" pn="section-5.7"> <name slugifiedName="name-the-pcntf-message">The PCNtfMessage" anchor="sect-5.7"><t>Message</name> <t pn="section-5.7-1"> As per <xreftarget="RFC5440"/>,target="RFC5440" format="default" sectionFormat="of" derivedContent="RFC5440"/>, the PCEP Notification message (PCNtf) can be sent by a PCEP speaker to notify its peer of a specific event.</t><t><t pn="section-5.7-2"> A PCEP speaker (PCE or PCC)SHOULD<bcp14>SHOULD</bcp14> notify its PCEP peer (PCC or PCE) when it is in an overwhelmed state due to the auto-bandwidth feature. An implementation needs to make an attempt to send this notification (when overwhelmed by auto-bandwidth adjustments) unless sending this notification would only serve to increase the load further. Note that when the notification is notreceivedreceived, the PCEP speaker would continue to request bandwidth adjustments even when theycould notcannot be handled in a timely fashion.</t><t><t pn="section-5.7-3"> Upon receipt of an auto-bandwidth overwhelm notification, the peerSHOULD NOT<bcp14>SHOULD NOT</bcp14> send any PCEP messages related to auto-bandwidth adjustment. If a PCEP message related to auto-bandwidth adjustment is receivedduringwhile in an overwhelmed state, itMUST<bcp14>MUST</bcp14> be ignored.</t><t><list style="symbols"><t>When<ul spacing="normal" bare="false" empty="false" pn="section-5.7-4"> <li pn="section-5.7-4.1">When a PCEP speaker is overwhelmed, itSHOULD<bcp14>SHOULD</bcp14> notify its peer by sending a PCNtf message withNotification-TypeNotification-type =TBD3 (Auto-bandwidth5 (Auto-Bandwidth Overwhelm State) andNotification-ValueNotification-value = 1 (Enteringauto-bandwidth overwhelm state).Auto-Bandwidth Overwhelm State). Optionally, an OVERLOADED-DURATION TLV <xreftarget="RFC5440"/> MAYtarget="RFC5440" format="default" sectionFormat="of" derivedContent="RFC5440"/> <bcp14>MAY</bcp14> be includedthat specifiesto specify the time period during which no further PCEP messages related to auto-bandwidth adjustment should besent.</t> <t>Whensent.</li> <li pn="section-5.7-4.2">When the PCEP speaker is no longer in the overwhelm state and is available to process the auto-bandwidth adjustments, itSHOULD<bcp14>SHOULD</bcp14> notify its peers by sending a PCNtf message withNotification TypeNotification-type =TBD3 (Auto-bandwidth5 (Auto-Bandwidth Overwhelm State) andNotification ValueNotification-value = 2 (Clearingauto-bandwidth overwhelm state).Auto-Bandwidth Overwhelm State). A PCEP speakerSHOULD<bcp14>SHOULD</bcp14> send such notification to all peersto withif a Notification message(Notification-Type=TBD3, Notification-Value=1) was sent earlier unless(Notification-type = 5, Notification-value = 1) was sent earlier. This message is not sent if an OVERLOADED-DURATION TLV was included and the PCEP speakers wishes for the peer to wait for the expiration of that period of time before receiving further PCEP messages related to auto-bandwidthadjustment.</t> </list> </t> <t>adjustment.</li> </ul> <t pn="section-5.7-5"> WhenAuto-Bandwidththe auto-bandwidth feature is deployed, a PCE can send this notification toPCC whena PCCis reportingwhen it reports frequent auto-bandwidth adjustments. If a PCC is overwhelmed withre-signaling,resignaling, it can also notify the PCE to not adjust the LSP bandwidth while in the overwhelm state.</t><t><t pn="section-5.7-6"> Some dampening notification procedure (as per <xreftarget="RFC5440"/>)target="RFC5440" format="default" sectionFormat="of" derivedContent="RFC5440"/>) to avoid oscillations of the overwhelm state isRECOMMENDED.<bcp14>RECOMMENDED</bcp14>. On receipt of an auto-bandwidth overwhelm notification from the PCE, a PCC should consider the impact on the entire network. Moving the delegations ofauto-bandwidth enabled LSPauto-bandwidth-enabled LSPs to another PCE could cause further overloading.</t> </section> </section> <sectiontitle="Manageability Considerations" anchor="sect-6"><section title="Controlanchor="sect-6" numbered="true" toc="include" removeInRFC="false" pn="section-6"> <name slugifiedName="name-manageability-consideration">Manageability Considerations</name> <section anchor="sect-6.1" numbered="true" toc="include" removeInRFC="false" pn="section-6.1"> <name slugifiedName="name-control-of-function-and-pol">Control of Function andPolicy" anchor="sect-6.1"><t>Policy</name> <t pn="section-6.1-1"> TheAuto-Bandwidthauto-bandwidth featureSHOULD<bcp14>SHOULD</bcp14> be controlledper LSPon a per-LSP basis (at the PCC (head-end of the LSP) orPCE)PCE), and the values for auto-bandwidthparameters e.g. sample-interval, adjustment-intervalparameters, e.g., Sample-Interval, Adjustment-Interval (up/down),minimum-bandwidth, maximum-bandwidth, adjustment-threshold (up/down) SHOULDMinimum-Bandwidth, Maximum-Bandwidth, and Adjustment-Threshold (up/down), <bcp14>SHOULD</bcp14> be configurable by an operator.</t><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 domain.</t><t><t pn="section-6.1-3"> The operator should make sure that the Overflow-Threshold is greater than or at least equal to the Up-Adjustment-Threshold. And similarly,make sureit is important to ensure that the Underflow-Threshold is greater than or at least equal to the Down-Adjustment-Threshold.</t> </section> <sectiontitle="Informationanchor="sect-6.2" numbered="true" toc="include" removeInRFC="false" pn="section-6.2"> <name slugifiedName="name-information-and-data-models">Information and DataModels" anchor="sect-6.2"><t>Models</name> <t pn="section-6.2-1"> A MIB module for gathering operational information about the PCEP is defined in <xreftarget="RFC7420"/>.target="RFC7420" format="default" sectionFormat="of" derivedContent="RFC7420"/>. Additionally, the YANG module defined in <xreftarget="I-D.ietf-pce-pcep-yang"/>target="I-D.ietf-pce-pcep-yang" format="default" sectionFormat="of" derivedContent="PCE-PCEP-YANG"/> providesforboth configuration of PCEP as well as operational management. These could be enhanced to provide controls and indicators for support of the auto-bandwidth feature. Support for various configuration knobs as well as counters of messages sent/received containing the TLVs defined in this document could be added.</t> </section> <sectiontitle="Livenessanchor="sect-6.3" numbered="true" toc="include" removeInRFC="false" pn="section-6.3"> <name slugifiedName="name-liveness-detection-and-moni">Liveness Detection andMonitoring" anchor="sect-6.3"><t>Monitoring</name> <t pn="section-6.3-1"> The mechanisms defined in this document do not imply any new liveness detection and monitoring requirements in addition to those already listed in <xreftarget="RFC5440"/>.</t>target="RFC5440" format="default" sectionFormat="of" derivedContent="RFC5440"/>.</t> </section> <sectiontitle="Verifyanchor="sect-6.4" numbered="true" toc="include" removeInRFC="false" pn="section-6.4"> <name slugifiedName="name-verifying-correct-operation">Verifying CorrectOperations" anchor="sect-6.4"><t>Operations</name> <t pn="section-6.4-1"> The mechanisms defined in this document do not imply any new operation verification requirements in addition to those already listed in <xreftarget="RFC5440"/>.</t> <t>target="RFC5440" format="default" sectionFormat="of" derivedContent="RFC5440"/>.</t> <t pn="section-6.4-2"> In the caseofin which an invalidvalue,value is present, theSub-TLVsub-TLV would get ignored and the previous valuewouldwill be maintained. In suchcasea case, the implementationSHOULD<bcp14>SHOULD</bcp14> log the event.</t> </section> <sectiontitle="Requirements Onanchor="sect-6.5" numbered="true" toc="include" removeInRFC="false" pn="section-6.5"> <name slugifiedName="name-requirements-for-other-prot">Requirements for OtherProtocols" anchor="sect-6.5"><t>Protocols</name> <t pn="section-6.5-1"> The mechanisms defined in this document do not add any new requirementsonfor other protocols.</t> </section> <sectiontitle="Impact Onanchor="sect-6.6" numbered="true" toc="include" removeInRFC="false" pn="section-6.6"> <name slugifiedName="name-impact-on-network-operation">Impact on NetworkOperations" anchor="sect-6.6"><t>Operations</name> <t pn="section-6.6-1"> In order to avoid any unacceptable impact on network operations, an implementationSHOULD<bcp14>SHOULD</bcp14> allow a limit to be placed on the number of LSPs that can be enabled with the auto-bandwidth feature. For each LSP enabled with the auto-bandwidthfeaturefeature, there is an extra load on the PCC, as it needs to monitor the traffic and report the calculated bandwidth to be adjusted to the PCE. The PCE furtherre-computerecomputes paths based on the requested bandwidth andupdateupdates the path to the PCC,whichwhich, inturnsturn, triggers there-signalingresignaling of the path. All these stepsaddsadd extra load and churn in thenetwork and thusnetwork; thus, the operator needs to take due care while enablingthisthese features on a number of LSPs.</t><t><t pn="section-6.6-2"> An implementationMAY<bcp14>MAY</bcp14> allow a limit to be placed on the rate ofauto-bandwidth relatedauto-bandwidth-related messages sent by a PCEP speaker and received by a peer. An implementationSHOULD<bcp14>SHOULD</bcp14> also allowsending a notificationnotifications to be sent when a PCEP speaker is overwhelmed or when the rate of messagesreachreaches a threshold.</t><t><t pn="section-6.6-3"> Due care is required by the operator if a Sample-Interval value significantly smaller than the default (5minute)minutes) is used, asasmall Sample-Interval values, e.g., 1 minute or less, could cause undesirable interactions with transport protocols. These undesirable interactions result from providing insufficient time for transport protocol reactions to a prior bandwidth adjustment to settleoutdown beforebandwidth samplesBandwidth-Samples are taken for the next bandwidth adjustment.</t> </section> </section> <sectiontitle="Security Considerations" anchor="sect-7"><t>anchor="sect-7" numbered="true" toc="include" removeInRFC="false" pn="section-7"> <name slugifiedName="name-security-considerations">Security Considerations</name> <t pn="section-7-1"> This document defines AUTO-BANDWIDTH-CAPABILITY TLV and AUTO-BANDWIDTH-ATTRIBUTESsub-TLVssub-TLVs, which do not add any substantial new security concerns beyond those already discussed in <xreftarget="RFC8231"/>target="RFC8231" format="default" sectionFormat="of" derivedContent="RFC8231"/> and <xreftarget="RFC8281"/>target="RFC8281" format="default" sectionFormat="of" derivedContent="RFC8281"/> for stateful PCE operations. As per <xreftarget="RFC8231"/>,target="RFC8231" format="default" sectionFormat="of" derivedContent="RFC8231"/>, it isRECOMMENDED<bcp14>RECOMMENDED</bcp14> that these PCEP extensions only be activated on authenticated and encrypted sessions across PCEs and PCCs belonging to the same administrative authority, using Transport Layer Security (TLS) <xreftarget="RFC8253"/>,target="RFC8253" format="default" sectionFormat="of" derivedContent="RFC8253"/>, as per the recommendations and best current practices in BCP 195 <xreftarget="RFC7525"/>target="RFC7525" format="default" sectionFormat="of" derivedContent="RFC7525"/> (unless explicitly set aside in <xreftarget="RFC8253"/>).</t> <t>target="RFC8253" format="default" sectionFormat="of" derivedContent="RFC8253"/>).</t> <t pn="section-7-2"> Incorrect auto-bandwidth parameters in the AUTO-BANDWIDTH-ATTRIBUTES sub-TLVs could have an adverse effect on the LSP as well as on the network.</t> </section> <sectiontitle="IANA Considerations" anchor="sect-8"><section title="PCEPanchor="sect-8" numbered="true" toc="include" removeInRFC="false" pn="section-8"> <name slugifiedName="name-iana-considerations">IANA Considerations</name> <section anchor="sect-8.1" numbered="true" toc="include" removeInRFC="false" pn="section-8.1"> <name slugifiedName="name-pcep-tlv-type-indicators">PCEP TLV TypeIndicators" anchor="sect-8.1"><t>Indicators</name> <t pn="section-8.1-1"> This document defines the following new PCEP TLVs; IANAis requested to makehas made the following allocations from the "PCEP TLV Type Indicators"sub-registrysubregistry of thePCEP Numbers registry,"Path Computation Element Protocol (PCEP) Numbers" registry as follows:</t><figure><artwork><![CDATA[ Value Name Reference ----------------------------------------------------------------- TBD2 AUTO-BANDWIDTH-CAPABILITY [This document] TBD1 AUTO-BANDWIDTH-ATTRIBUTES [This document] ]]></artwork> </figure> </section> <section title="AUTO-BANDWIDTH-CAPABILITY<table anchor="pcep-tlv" align="left" pn="table-3"> <name slugifiedName="name-pcep-tlv-type-indicators-2">PCEP TLV Type Indicators</name> <thead> <tr> <th align="left" colspan="1" rowspan="1">Value</th> <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="false" pn="section-8.2"> <name slugifiedName="name-auto-bandwidth-capability-tlv">AUTO-BANDWIDTH-CAPABILITY TLV FlagField" anchor="sect-8.2"><t>Field</name> <t pn="section-8.2-1"> IANAis requested to createhas created asub-registrysubregistry to manage the Flag field of the AUTO-BANDWIDTH-CAPABILITY TLV within the "Path Computation Element Protocol (PCEP) Numbers" registry.</t><t><t pn="section-8.2-2"> New bit numbers are to be assigned by Standards Action <xreftarget="RFC8126"/>.target="RFC8126" format="default" sectionFormat="of" derivedContent="RFC8126"/>. Each bit should be tracked with the following qualities:</t><t><list style="symbols"><t>Bit<ul spacing="normal" bare="false" empty="false" pn="section-8.2-3"> <li pn="section-8.2-3.1">Bit number (counting from bit 0 as the most significantbit)</t> <t>Capability description</t> <t>Defining RFC</t> </list> </t> <t>bit)</li> <li pn="section-8.2-3.2">Capability description</li> <li pn="section-8.2-3.3">Defining RFC</li> </ul> <t pn="section-8.2-4"> The initial contents of thesub-registrysubregistry are empty, with all bits markedunassigned</t>unassigned.</t> </section> <sectiontitle="AUTO-BANDWIDTH-ATTRIBUTES Sub-TLV" anchor="sect-8.3"><t>anchor="sect-8.3" numbered="true" toc="include" removeInRFC="false" pn="section-8.3"> <name slugifiedName="name-auto-bandwidth-attributes-s">AUTO-BANDWIDTH-ATTRIBUTES Sub-TLV</name> <t pn="section-8.3-1"> This document specifies the AUTO-BANDWIDTH-ATTRIBUTESSub-TLVs.sub-TLVs. IANAis requested to createhas created an "AUTO-BANDWIDTH-ATTRIBUTES Sub-TLV Types"sub-registrysubregistry within the "Path Computation Element Protocol (PCEP) Numbers" registry to manage the type indicator space for sub-TLVs of the AUTO-BANDWIDTH-ATTRIBUTES TLV. The valid range of values in the registry is 0-65535. IANAis requested to initializehas initialized the registry with the following values. All other values in the registry should be marked as "Unassigned".</t><t><t pn="section-8.3-2"> IANAis requested tohas set theregistration procedureRegistration Procedure for this registry to read as follows:</t><figure><artwork><![CDATA[ 0-65503 IETF Review 65504-65535 Experimental Use<table anchor="registration" align="left" pn="table-4"> <name slugifiedName="name-registration-procedure-for-">Registration Procedure for the "AUTO-BANDWIDTH-ATTRIBUTES Sub-TLV" Registry</name> <thead> <tr> <th align="left" colspan="1" rowspan="1">Range</th> <th align="left" colspan="1" rowspan="1">Registration Procedure</th> </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:Type Name Reference ----------------------------------------------------------------- 0 Reserved [This document] 1 Sample-Interval sub-TLV [This document] 2 Adjustment-Interval sub-TLV [This document] 3 Down-Adjustment-Interval sub-TLV [This document] 4 Adjustment-Threshold sub-TLV [This document] 5 Adjustment-Threshold-Percentage sub-TLV [This document] 6 Down-Adjustment-Threshold sub-TLV [This document] 7 Down-Adjustment-Threshold-Percentage sub-TLV [This document] 8 Minimum-Bandwidth sub-TLV [This document] 9 Maximum-Bandwidth sub-TLV [This document] 10 Overflow-Threshold sub-TLV [This document] 11 Overflow-Threshold-Percentage sub-TLV [This document] 12 Underflow-Threshold sub-TLV [This document] 13 Underflow-Threshold-Percentage sub-TLV [This document] 14- Unassigned [This document] 65503 ]]></artwork> </figure> </section> <section title="Error Object" anchor="sect-8.4"><t></t> <table anchor="registry" align="left" pn="table-5"> <name slugifiedName="name-initial-contents-of-the-aut">Initial Contents of the "AUTO-BANDWIDTH-ATTRIBUTES Sub-TLV" Registry</name> <thead> <tr> <th align="left" colspan="1" rowspan="1">Type</th> <th align="left" colspan="1" rowspan="1">Name</th> <th align="left" colspan="1" rowspan="1">Reference</th> </tr> </thead> <tbody> <tr> <td align="left" colspan="1" rowspan="1">0</td> <td align="left" colspan="1" rowspan="1">Reserved</td> <td align="left" colspan="1" rowspan="1">[RFC8733]</td> </tr> <tr> <td align="left" colspan="1" rowspan="1">1</td> <td align="left" colspan="1" rowspan="1">Sample-Interval </td> <td align="left" colspan="1" rowspan="1">[RFC8733]</td> </tr> <tr> <td align="left" colspan="1" rowspan="1">2</td> <td align="left" colspan="1" rowspan="1">Adjustment-Interval </td> <td align="left" colspan="1" rowspan="1">[RFC8733]</td> </tr> <tr> <td align="left" colspan="1" rowspan="1">3</td> <td align="left" colspan="1" rowspan="1">Down-Adjustment-Interval</td> <td align="left" colspan="1" rowspan="1">[RFC8733]</td> </tr> <tr> <td align="left" colspan="1" rowspan="1">4</td> <td align="left" colspan="1" rowspan="1">Adjustment-Threshold </td> <td align="left" colspan="1" rowspan="1">[RFC8733]</td> </tr> <tr> <td align="left" colspan="1" rowspan="1">5</td> <td align="left" colspan="1" rowspan="1">Adjustment-Threshold-Percentage </td> <td align="left" colspan="1" rowspan="1">[RFC8733]</td> </tr> <tr> <td align="left" colspan="1" rowspan="1">6</td> <td align="left" colspan="1" rowspan="1">Down-Adjustment-Threshold </td> <td align="left" colspan="1" rowspan="1">[RFC8733]</td> </tr> <tr> <td align="left" colspan="1" rowspan="1">7</td> <td align="left" colspan="1" rowspan="1">Down-Adjustment-Threshold-Percentage </td> <td align="left" colspan="1" rowspan="1">[RFC8733]</td> </tr> <tr> <td align="left" colspan="1" rowspan="1">8</td> <td align="left" colspan="1" rowspan="1">Minimum-Bandwidth </td> <td align="left" colspan="1" rowspan="1">[RFC8733]</td> </tr> <tr> <td align="left" colspan="1" rowspan="1">9</td> <td align="left" colspan="1" rowspan="1">Maximum-Bandwidth </td> <td align="left" colspan="1" rowspan="1">[RFC8733]</td> </tr> <tr> <td align="left" colspan="1" rowspan="1">10</td> <td align="left" colspan="1" rowspan="1">Overflow-Threshold </td> <td align="left" colspan="1" rowspan="1">[RFC8733]</td> </tr> <tr> <td align="left" colspan="1" rowspan="1">11</td> <td align="left" colspan="1" rowspan="1">Overflow-Threshold-Percentage </td> <td align="left" colspan="1" rowspan="1">[RFC8733]</td> </tr> <tr> <td align="left" colspan="1" rowspan="1">12</td> <td align="left" colspan="1" rowspan="1">Underflow-Threshold </td> <td align="left" colspan="1" rowspan="1">[RFC8733]</td> </tr> <tr> <td align="left" colspan="1" rowspan="1">13</td> <td align="left" colspan="1" rowspan="1">Underflow-Threshold-Percentage</td> <td align="left" colspan="1" rowspan="1">[RFC8733]</td> </tr> <tr> <td align="left" colspan="1" rowspan="1">14-65503</td> <td align="left" colspan="1" rowspan="1">Unassigned</td> <td align="left" colspan="1" rowspan="1">[RFC8733]</td> </tr> </tbody> </table> </section> <section anchor="sect-8.4" numbered="true" toc="include" removeInRFC="false" pn="section-8.4"> <name slugifiedName="name-error-object">Error Object</name> <t pn="section-8.4-1"> This document defines a newError-ValueError-value for PCErr message of Error-Type 19 (Invalid Operation) <xreftarget="RFC8231"/>.target="RFC8231" format="default" sectionFormat="of" derivedContent="RFC8231"/>. IANAis requested to allocatehas allocated a newerror-valueError-value within the "PCEP-ERROR Object Error Types and Values" subregistry of thePCEP Numbers registry,"Path Computation Element Protocol (PCEP) Numbers" registry as follows:</t><figure><artwork><![CDATA[ Error-Type Meaning & error values Reference ----------------------------------------------------------------- 19 Invalid Operations Error-Value = TBD4: [This document]<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-BandwidthCapabilitycapability was notAdvertised ]]></artwork> </figure> </section> <section title="Notification Object" anchor="sect-8.5"><t>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="false" pn="section-8.5"> <name slugifiedName="name-notification-object">Notification Object</name> <t pn="section-8.5-1"> IANAis requested to allocatehas allocated a newNotification TypeNotification-type andNotification ValuesNotification-values within the "Notification Object"sub-registrysubregistry of thePCEP Numbers registry,"Path Computation Element Protocol (PCEP) Numbers" registry as follows:</t><figure><artwork><![CDATA[ Type Meaning Reference ----------------------------------------------------------------- TBD3 Auto-Bandwidth<table anchor="notification-object" align="left" pn="table-7"> <name slugifiedName="name-additions-to-the-notificati">Additions to the "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 OverwhelmState [This document] Notification-value=1: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-Bandwidthoverwhelm state Notification-value=2: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-Bandwidthoverwhelm state ]]></artwork> </figure>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> <referencestitle="Normative References"> &RFC2119; &RFC5440; &RFC7525; &RFC8126; &RFC8174; &RFC8231; &RFC8253; &RFC8281;pn="section-9.1"> <name slugifiedName="name-normative-references">Normative References</name> <referenceanchor="IEEE.754.1985"><front>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>Institute of Electrical and Electronics Engineers</organization><organization showOnFrontPage="true">IEEE</organization> </author> <datemonth="August"month="October" year="1985"/> </front><seriesInfo name="IEEE" value="Standard 754"/></reference></references> <references title="Informative References"> &RFC3209; &RFC3471; &RFC7420; &RFC8051; &I-D.ietf-pce-pcep-yang; </references> <section title="Acknowledgments" numbered="no" anchor="acknowledgments"><t> Authors would like<reference anchor="RFC2119" target="https://www.rfc-editor.org/info/rfc2119" quoteTitle="true" derivedAnchor="RFC2119"> <front> <title>Key words for use in RFCs tothank Robert Varga, Venugopal Reddy, Reeja Paul, Sandeep Boina, Avantika, JP Vasseur, Himanshu Shah, Jonathan HardwickIndicate Requirement Levels</title> <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 signify the requirements in the specification. These words are often capitalized. This document defines these words as they should be interpreted in IETF documents. This document specifies an Internet Best Current Practices for the Internet Community, andAdrian Farrelrequests discussion and suggestions fortheir useful commentsimprovements.</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/rfc5440" 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) Communication Protocol (PCEP) for communications between a Path Computation Client (PCC) andsuggestions.</t> <t> Thanksa PCE, or between two PCEs. Such interactions include path computation requests and path computation replies as well as notifications of specific states related to the use of a PCE in the context of Multiprotocol Label Switching (MPLS) and Generalized MPLS (GMPLS) Traffic Engineering. PCEP is designed toDaniel Franke, Joe Clarke, David Black,be flexible andErik Klineextensible so as to easily allow for thedirectorate reviews.</t> <t> Thanksaddition of further messages and objects, should further requirements be expressed in the future. [STANDARDS-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/rfc7525" quoteTitle="true" derivedAnchor="RFC7525"> <front> <title>Recommendations for Secure Use of Transport Layer Security (TLS) 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 Security (DTLS) are widely used toMirja Kuhlewind, Barry Leiba, Benjamin Kaduk,protect data exchanged over application protocols such as HTTP, SMTP, IMAP, POP, SIP, and XMPP. Over the last few years, several serious attacks on TLS have emerged, including attacks on its most commonly used cipher suites andRoman Danyliwtheir modes of operation. This document provides recommendations for improving theIESG review.</t> </section> <section title="Contributors" numbered="no" anchor="contributors"><figure><artwork><![CDATA[ He Zekun Tencent Holdings Ltd, Shenzhen P.R.China Email: kinghe@tencent.com Xian Zhang Huawei Technologies Research Area F3-1B, Huawei Industrial Base, Shenzhen, 518129 China Phone: +86-755-28972645 Email: zhang.xian@huawei.com Young Lee SKKU Email: younglee.tx@gmail.com ]]></artwork> </figure>security of deployed services that use TLS and DTLS. The 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/rfc8126" 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 constants to identify various protocol parameters. To ensure that the values in these fields do not have conflicting uses and to promote interoperability, their allocations 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 describing the conditions under which new values should be assigned, as well as when and how modifications to existing values can be made, is needed. This document defines a framework for the documentation of these guidelines by specification authors, in order to assure that the provided guidance for the IANA Considerations is clear and addresses the various issues that are likely in the operation of a registry.</t> <t>This is the third edition of this document; it obsoletes RFC 5226.</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/rfc8174" quoteTitle="true" derivedAnchor="RFC8174"> <front> <title>Ambiguity of Uppercase vs Lowercase in RFC 2119 Key Words</title> <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 protocol specifications. This document aims to reduce the ambiguity by clarifying that 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/rfc8231" quoteTitle="true" derivedAnchor="RFC8231"> <front> <title>Path Computation Element Communication Protocol (PCEP) Extensions 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) provides mechanisms for Path Computation Elements (PCEs) to perform path computations in response to Path Computation Client (PCC) requests.</t> <t>Although PCEP explicitly makes no assumptions regarding the information available to the PCE, it also makes no provisions for PCE control of timing and sequence of path computations within and across PCEP sessions. This document 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/rfc8253" quoteTitle="true" derivedAnchor="RFC8253"> <front> <title>PCEPS: Usage of TLS to Provide a Secure Transport for the Path 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. Gonzalez 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) defines the mechanisms for the communication between a Path Computation Client (PCC) and a Path Computation Element (PCE), or among PCEs. This document describes PCEPS -- the usage of Transport Layer Security (TLS) to provide a secure transport for PCEP. The additional security mechanisms are provided by the transport protocol supporting PCEP; therefore, they do not affect the flexibility and extensibility of PCEP.</t> <t>This document updates RFC 5440 in regards to the PCEP initialization 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/rfc8281" quoteTitle="true" derivedAnchor="RFC8281"> <front> <title>Path Computation Element Communication Protocol (PCEP) Extensions 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) provides mechanisms for Path Computation Elements (PCEs) to perform path computations in response to Path Computation Client (PCC) requests.</t> <t>The extensions for stateful PCE provide active control of Multiprotocol Label Switching (MPLS) Traffic Engineering Label Switched Paths (TE LSPs) via PCEP, for a model where the PCC delegates control over one or more locally 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="https://tools.ietf.org/html/draft-ietf-pce-pcep-yang-13" derivedAnchor="PCE-PCEP-YANG"> <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 Path Computation Element communications Protocol (PCEP) for communications between a Path Computation Client (PCC) and a Path Computation Element (PCE), or between 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-ietf-pce-pcep-yang-13.txt"/> <refcontent>Work in Progress</refcontent> </reference> <reference anchor="RFC3209" target="https://www.rfc-editor.org/info/rfc3209" 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 Protocol), including all the necessary extensions, to establish label-switched paths (LSPs) in MPLS (Multi-Protocol Label Switching). Since the flow along an LSP 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 traffic 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/rfc3471" 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="editor"> <organization showOnFrontPage="true"/> </author> <date year="2003" month="January"/> <abstract> <t>This document describes extensions to Multi-Protocol Label Switching (MPLS) signaling required to support Generalized MPLS. Generalized MPLS extends the MPLS control plane to encompass time-division (e.g., Synchronous Optical Network and Synchronous Digital Hierarchy, SONET/SDH), wavelength (optical lambdas) and spatial switching (e.g., incoming port or fiber to outgoing port or fiber). This document presents a functional description of the extensions. Protocol specific formats and mechanisms, and technology specific details are specified 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/rfc7420" quoteTitle="true" derivedAnchor="RFC7420"> <front> <title>Path Computation Element Communication Protocol (PCEP) Management 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 particular, it describes managed objects for modeling of the Path Computation Element 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/rfc8051" quoteTitle="true" derivedAnchor="RFC8051"> <front> <title>Applicability of a Stateful Path Computation Element (PCE)</title> <author initials="X." surname="Zhang" fullname="X. Zhang" role="editor"> <organization showOnFrontPage="true"/> </author> <author initials="I." surname="Minei" fullname="I. Minei" role="editor"> <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 network in order to provide traffic-engineering calculations for its associated Path Computation Clients (PCCs). This document describes general considerations for a stateful PCE deployment and examines its applicability and benefits, as well as its challenges and limitations, through a number of use cases. PCE Communication 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 fullname="Sandeep Boina"/>, <contact fullname="Avantika"/>, <contact fullname="JP Vasseur"/>, <contact fullname="Himanshu Shah"/>, <contact fullname="Jonathan Hardwick"/>, 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> <t pn="section-appendix.a-3"> Thanks to <contact fullname="Mirja Kühlewind"/>, <contact fullname="Barry Leiba"/>, <contact fullname="Benjamin Kaduk"/>, and <contact fullname="Roman Danyliw"/> for the IESG review.</t> </section> <section numbered="false" anchor="contributors" toc="include" removeInRFC="false" pn="section-appendix.b"> <name slugifiedName="name-contributors">Contributors</name> <contact fullname="He Zekun"> <organization showOnFrontPage="true">Tencent Holdings Ltd.</organization> <address> <postal> <city>Shenzhen</city> <country>China</country> </postal> <email>kinghe@tencent.com</email> </address> </contact> <contact fullname="Xian Zhang"> <organization showOnFrontPage="true">Huawei Technologies</organization> <address> <postal> <street>Research Area F3-1B</street> <street>Huawei Industrial Base,</street> <city>Shenzhen</city> <code>518129</code> <country>China</country> </postal> <phone>+86-755-28972645</phone> <email>zhang.xian@huawei.com</email> </address> </contact> <contact fullname="Young Lee"> <organization showOnFrontPage="true">Samsung</organization> <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="Gandhi"> <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</organization> <address> <email>udayasreereddy@gmail.com</email> </address> </author> <author fullname="Ravi Singh" initials="R." surname="Singh"> <organization showOnFrontPage="true">Individual Contributor</organization> <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>