Skip to main content

RSVP-TE Scalability - Recommendations

Document Type Replaced Internet-Draft (individual)
Authors Vishnu Pavan Beeram , Ina Minei , Yakov Rekhter , Ebben Aries , Dante Pacella
Last updated 2015-07-10 (Latest revision 2015-03-08)
Replaced by draft-beeram-teas-rsvp-te-scaling-rec
Stream (None)
Intended RFC status (None)
Expired & archived
Stream Stream state (No stream defined)
Consensus boilerplate Unknown
RFC Editor Note (None)
IESG IESG state Replaced by draft-beeram-teas-rsvp-te-scaling-rec
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:


RSVP-TE [RFC3209] describes the use of standard RSVP [RFC2205] to establish Label Switched Paths (LSPs). As such, RSVP-TE inherited some properties of RSVP that adversely affect its control plane scalability. Specifically these properties are (a) reliance on periodic refreshes for state synchronization between RSVP neighbors and for recovery from lost RSVP messages, (b) reliance on refresh timeout for stale state cleanup, and (c) lack of any mechanisms by which a receiver of RSVP messages can apply back pressure to the sender(s) of these messages. Subsequent to [RFC2205] and [RFC3209] further enhancements to RSVP and RSVP-TE have been developed. In this document we describe how an implementation of RSVP-TE can use these enhancements to address the above mentioned properties to improve RSVP-TE control plane scalability.


Vishnu Pavan Beeram
Ina Minei
Yakov Rekhter
Ebben Aries
Dante Pacella

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