%% You should probably cite draft-beeram-teas-rsvp-te-scaling-rec instead of this I-D. @techreport{beeram-mpls-rsvp-te-scaling-01, number = {draft-beeram-mpls-rsvp-te-scaling-01}, type = {Internet-Draft}, institution = {Internet Engineering Task Force}, publisher = {Internet Engineering Task Force}, note = {Work in Progress}, url = {https://datatracker.ietf.org/doc/draft-beeram-mpls-rsvp-te-scaling/01/}, author = {Vishnu Pavan Beeram and Ina Minei and Yakov Rekhter and Ebben Aries and Dante Pacella}, title = {{RSVP-TE Scalability - Recommendations}}, pagetotal = 9, year = 2015, month = mar, day = 8, abstract = {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.}, }