<?xml version="1.0" encoding="UTF-8"?>
<reference anchor="I-D.ietf-teas-rsvp-te-scaling-rec" target="https://datatracker.ietf.org/doc/html/draft-ietf-teas-rsvp-te-scaling-rec-09">
   <front>
      <title>Techniques to Improve the Scalability of RSVP-TE Deployments</title>
      <author initials="V. P." surname="Beeram" fullname="Vishnu Pavan Beeram">
         <organization>Juniper Networks</organization>
      </author>
      <author initials="I." surname="Minei" fullname="Ina Minei">
         <organization>Google, Inc</organization>
      </author>
      <author initials="R." surname="Shakir" fullname="Rob Shakir">
         <organization>Google, Inc</organization>
      </author>
      <author initials="D." surname="Pacella" fullname="Dante Pacella">
         <organization>Verizon</organization>
      </author>
      <author initials="T." surname="Saad" fullname="Tarek Saad">
         <organization>Cisco Systems</organization>
      </author>
      <date month="February" day="14" year="2018" />
      <abstract>
	 <t>Networks that utilize RSVP-TE LSPs are encountering implementations that have a limited ability to support the growth in the number of LSPs deployed.

 This document defines two techniques, Refresh-Interval Independent RSVP (RI-RSVP) and Per-Peer Flow Control, that reduce the number of processing cycles required to maintain RSVP-TE LSP state in Label Switching Routers (LSRs) and hence allow implementations to support larger scale deployments.
	 </t>
      </abstract>
   </front>
   <seriesInfo name="Internet-Draft" value="draft-ietf-teas-rsvp-te-scaling-rec-09" />
   
</reference>
