MRT OAM Requirements and Use cases
draft-agv-rtgwg-mrt-oam-requirements-and-usecases-00
| Document | Type |
Expired Internet-Draft
(individual)
Expired & archived
|
|
|---|---|---|---|
| Authors | Gaurav Agrawal , ANIL KUMAR S N , Vinod KumarS | ||
| Last updated | 2016-03-19 (Latest revision 2015-09-16) | ||
| RFC stream | (None) | ||
| Intended RFC status | (None) | ||
| Formats | |||
| 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) |
This Internet-Draft is no longer active. A copy of the expired Internet-Draft is available in these formats:
Abstract
IP/LDP Fast-Reroute with Maximally Redundant Trees (MRT-FRR) is a technology that gives link-protection and node-protection with 100% coverage in any network topology that is still connected after the failure. MRT-FRR creates two alternate trees separate from the primary next- hop forwarding used during stable operation. These two trees are maximally diverse from each other, providing link and node protection for 100% of paths and failures as long as the failure does not cut the network into multiple pieces. This document spcifies how data plane protocols can be applied to operations and maintenance procedures for MRT. The document is structured to outline how Operations and Management functionality can be used to assist in fault management.
Authors
Gaurav Agrawal
ANIL KUMAR S N
Vinod KumarS
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)