Implementation Recommendations to Improve the Scalability of RSVP-TE Deployments

Document Type Replaced Internet-Draft (teas WG)
Authors Vishnu Beeram  , Ina Minei  , Rob Shakir  , Ebben Aries  , Dante Pacella  , Tarek Saad  , Markus Jork 
Last updated 2015-10-14 (latest revision 2015-07-03)
Replaces draft-beeram-mpls-rsvp-te-scaling
Replaced by RFC 8370
Stream IETF
Intended RFC status (None)
Expired & archived
pdf htmlized (tools) htmlized bibtex
Stream WG state Candidate for WG Adoption
Document shepherd No shepherd assigned
IESG IESG state Replaced by draft-ietf-teas-rsvp-te-scaling-rec
Consensus Boilerplate Unknown
Telechat date
Responsible AD (None)
Send notices to (None)

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 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 - "Refresh Interval Independent RSVP (RI-RSVP)" and "Per-Peer flow-control" - for improving scaling.


Vishnu Beeram (
Ina Minei (
Rob Shakir (
Ebben Aries (
Dante Pacella (
Tarek Saad (
Markus Jork (

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