Skip to main content

Refresh-interval Independent FRR Facility Protection

The information below is for an old version of the document.
Document Type
This is an older version of an Internet-Draft whose latest revision state is "Active".
Expired & archived
Authors Chandrasekar R , Tarek Saad , Ina Minei , Dante Pacella
Last updated 2020-09-16 (Latest revision 2019-09-03)
Replaces draft-chandra-mpls-ri-rsvp-frr
RFC stream Internet Engineering Task Force (IETF)
Additional resources Mailing list discussion
Stream WG state WG Document
Revised I-D Needed - Issue raised by IESG
Document shepherd Nicolai Leymann
Shepherd write-up Show Last changed 2019-01-18
IESG IESG state Expired (IESG: Dead)
Consensus boilerplate Yes
Telechat date (None)
Responsible AD Deborah Brungard
Send notices to Nicolai Leymann <>
IANA IANA review state IANA OK - Actions Needed

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


RSVP-TE Fast ReRoute extensions specified in RFC 4090 defines two local repair techniques to reroute Label Switched Path (LSP) traffic over pre-established backup tunnel. Facility backup method allows one or more LSPs traversing a connected link or node to be protected using a bypass tunnel. The many-to-one nature of local repair technique is attractive from scalability point of view. This document enumerates facility backup procedures in RFC 4090 that rely on refresh timeout and hence make facility backup method refresh- interval dependent. The RSVP-TE extensions defined in this document will enhance the facility backup protection mechanism by making the corresponding procedures refresh-interval independent and hence compatible with Refresh-interval Independent RSVP (RI-RSVP) specified in RFC 8370. Hence, this document updates RFC 4090 in order to support RI-RSVP capability specified in RFC 8370.


Chandrasekar R
Tarek Saad
Ina Minei
Dante Pacella

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