FSM health status support in BFD
draft-bfd-fsm-health-status-00
| Document | Type |
Expired Internet-Draft
(individual)
Expired & archived
|
|
|---|---|---|---|
| Author | Palpandi Perumal | ||
| Last updated | 2021-04-16 (Latest revision 2020-10-13) | ||
| 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 operates in different modes. When BFD runs in asynchronous mode requires hello packet needs to be transmitted and received on regular intervals. In software based BFD application, hello packets processing path may be heavy weight which may involve many processing levels to reach BFD application. On a scaled system, processing delay may not be constant at all the time and this processing delay does appear at any point between software path entry point and BFD application. This delay needs to be identified and suppressed otherwise system may end up on false link failure detection. This internet draft deals on this particular case. Since introducing new Diagnostic bit, it requires to update RFC5880.
Authors
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)