Skip to main content

Implementation Recommendations to Improve the Scalability of RSVP-TE Deployments
draft-beeram-teas-rsvp-te-scaling-rec-00

Document Type Replaced Internet-Draft (teas WG)
Expired & archived
Authors Vishnu Pavan 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 draft-ietf-teas-rsvp-te-scaling-rec
RFC stream Internet Engineering Task Force (IETF)
Intended RFC status (None)
Formats
Additional resources Mailing list discussion
Stream WG state Candidate for WG Adoption
Document shepherd (None)
IESG IESG state Replaced by draft-ietf-teas-rsvp-te-scaling-rec
Consensus boilerplate Unknown
Telechat date (None)
Responsible AD (None)
Send notices to (None)

This Internet-Draft is no longer active. A copy of the expired Internet-Draft is available in these formats:

Abstract

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.

Authors

Vishnu Pavan 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.)