Redundant BFD sessions
draft-mbind-bfd-redundancy-01
Document | Type |
Expired Internet-Draft
(individual)
Expired & archived
|
|
---|---|---|---|
Authors | Marc Binderberger , Nobo Akiya | ||
Last updated | 2013-11-08 (Latest revision 2013-05-07) | ||
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
This document defines a second or "shadow" BFD session to an existing "primary" BFD session, providing resiliency against BFD failures that are not legitimate. Scenarios will be discussed on how presence of a shadow BFD session will be beneficial in the context of high availability.
Authors
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)