Signaling BFD configuration for a backup path in an FRR environment
draft-hanif-rsvp-te-bfd-frr-backup-path-00
| Document | Type |
Expired Internet-Draft
(individual)
Expired & archived
|
|
|---|---|---|---|
| Authors | Mohammad Hanif , Lisa Nguyen | ||
| Last updated | 2009-07-06 | ||
| 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
Today there is no support in the RSVP protocol to dynamically signal the enabling and configuring of the BFD (Bi-directional Forwarding Detection) on a backup path. This document introduces a new RSVP object called "FRR backup BFD object". The procedures described in this document are only applicable to Fast Reroute LSPs [RFC4090].
Authors
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)