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)
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
Stream IETF
Intended RFC status (None)
Formats
Expired & archived
pdf 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
https://www.ietf.org/archive/id/draft-beeram-teas-rsvp-te-scaling-rec-00.txt

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 Beeram (vbeeram@juniper.net)
Ina Minei (inaminei@google.com)
Rob Shakir (rob.shakir@bt.com)
Ebben Aries (exa@fb.com)
Dante Pacella (dante.j.pacella@verizon.com)
Tarek Saad (tsaad@cisco.com)
Markus Jork (mjork@juniper.net)

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