MPLS Network Actions for No Further Fast Reroute
draft-li-mpls-mna-nffrr-01
| Document | Type |
Expired Internet-Draft
(mpls WG)
Expired & archived
|
|
|---|---|---|---|
| Authors | Tarek Saad , Israel Meilik , Tony Li , John Drake | ||
| Last updated | 2023-05-07 (Latest revision 2022-10-21) | ||
| RFC stream | Internet Engineering Task Force (IETF) | ||
| Intended RFC status | (None) | ||
| Formats | |||
| Additional resources | Mailing list discussion | ||
| Stream | WG state | Dead WG Document | |
| Document shepherd | (None) | ||
| IESG | IESG state | Expired | |
| Consensus boilerplate | Unknown | ||
| 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:
Abstract
Protection switching for MPLS traffic was first introduced in "Fast Reroute Extensions to RSVP-TE for LSP Tunnels". Since then, Fast Reroute (FRR) has been successfully used in many MPLS networks to help ensure high availability in the face of failures. If there are multiple failures in a network, there are circumstances where FRR, if applied multiple times, can result in sub-optimal behavior, such as forwarding loops. Thus, it is useful to indicate in the forwarding plane that the attached traffic should not be subjected to further FRR redirection. This document describes a network action for identifying such traffic to be used in conjunction with "MPLS Network Action (MNA) Header Encodings".
Authors
Tarek Saad
Israel Meilik
Tony Li
John Drake
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)