<?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-00">
   <front>
      <title>Implementation Recommendations to Improve the Scalability of RSVP-TE Deployments</title>
      <author initials="V. P." surname="Beeram" fullname="Vishnu Pavan Beeram">
         </author>
      <author initials="I." surname="Minei" fullname="Ina Minei">
         </author>
      <author initials="R." surname="Shakir" fullname="Rob Shakir">
         </author>
      <author initials="E." surname="Aries" fullname="Ebben Aries">
         </author>
      <author initials="D." surname="Pacella" fullname="Dante Pacella">
         </author>
      <author initials="T." surname="Saad" fullname="Tarek Saad">
         </author>
      <author initials="M." surname="Jork" fullname="Markus Jork">
         </author>
      <date month="October" day="5" year="2015" />
      <abstract>
	 <t>    The scale at which RSVP-TE Label Switched Paths (LSPs) get deployed
    is growing continually and the onus is on RSVP-TE implementations
    across the board to keep up with this increasing demand.

    This document makes a set of implementation recommendations to help
    RSVP-TE deployments push the envelope on scaling and advocates the
    use of a couple of techniques - &quot;Refresh Interval Independent RSVP
    (RI-RSVP)&quot; and &quot;Per-Peer flow-control&quot; - for improving scaling.

 
	 </t>
      </abstract>
   </front>
   <seriesInfo name="Internet-Draft" value="draft-ietf-teas-rsvp-te-scaling-rec-00" />
   
</reference>
