Efficient Fast Re-route (FRR) using Facility backup in ring topology
draft-kini-mpls-ring-frr-facility-backup-02
| Document | Type | Expired Internet-Draft (individual) | |
|---|---|---|---|
| Authors | Sriganesh Kini , Autumn Liu | ||
| Last updated | 2011-01-13 | ||
| Stream | (None) | ||
| Intended RFC status | (None) | ||
| Formats |
Expired & archived
plain text
htmlized
pdfized
bibtex
|
||
| Stream | Stream state | (No stream defined) | |
| Consensus boilerplate | Unknown | ||
| RFC Editor Note | (None) | ||
| IESG | IESG state | Expired | |
| Telechat date | (None) | ||
| Responsible AD | (None) | ||
| Send notices to | (None) |
https://www.ietf.org/archive/id/draft-kini-mpls-ring-frr-facility-backup-02.txt
Abstract
Fast Re-route (FRR) using facility backup is a widely deployed MPLS protection mechanism that can protect against link and node failure. It provides a fast protection switch mechanism to minimize traffic loss (typically sub 50msec) if the node that detects the failure locally, does the repair by re-routing the protected traffic to go over the backup tunnel. A direct application of this mechanism to a ring topology results in an inefficient use of link bandwidth that could also result in degraded service. This document describes a mechanism to do it without such problems.
Authors
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)