Implementation Recommendations to Improve the Scalability of RSVP-TE Deployments

The information below is for an old version of the document
Document Type None Internet-Draft (teas WG)
Last updated 2017-07-09 (latest revision 2017-07-02)
Replaces draft-beeram-teas-rsvp-te-scaling-rec
Stream IETF
Intended RFC status Proposed Standard
Expired & archived
pdf htmlized bibtex
Additional URLs
- Mailing list discussion
Stream WG state (None)
Document shepherd Lou Berger
Shepherd write-up Show (last changed 2017-07-09)
IESG IESG state Unknown state
Consensus Boilerplate Yes
Telechat date
Responsible AD Deborah Brungard
Send notices to Lou Berger <>

This Internet-Draft is no longer active. A copy of the expired Internet-Draft can be found at


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 introduces a couple of techniques - "Refresh-Interval Independent RSVP (RI-RSVP)" and "Per-Peer Flow-Control" - to help RSVP-TE deployments push the envelope on scaling.


Vishnu Beeram (
Ina Minei (
Rob Shakir (
Dante Pacella (
Tarek Saad (

(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)