Design Recommendations for bfd to survive Planned Graceful restart
draft-palanivelan-bfd-gr-rec-03
Document | Type |
Expired Internet-Draft
(individual)
Expired & archived
|
|
---|---|---|---|
Author | Palanivelan Appanasamy | ||
Last updated | 2015-11-02 (Latest revision 2015-05-01) | ||
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
Bidirectional Forwarding Detection (bfd) defined in RFC5880 is comprehensive and has sufficient mechanisms to overcome challenges in surviving Graceful Restart (Planned). However, implementations with architectural limitation were found to influence a BFD failure, in a process intensive environment.This memo outlines design options to overcome the challenges, within the existing bfd framework, in surviving planned GracefulRestart.
Authors
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)