Bidirectional Forwarding Detection (BFD) for Interface
draft-chen-bfd-interface-00
| Document | Type |
Expired Internet-Draft
(individual)
Expired & archived
|
|
|---|---|---|---|
| Authors | Liang Guo , Marc Binderberger , Zuliang Wang | ||
| Last updated | 2011-07-04 | ||
| 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 describes how application clients can request IP-based Bidirectional Forwarding Detection (BFD) sessions while either being IP agnostic themselves or while dealing with IP unnumbered interfaces. A dedicated well-known multicast IP address 224.XXX.XXX.XXX is used as the destination IP address of the BFD packets when running BFD for interface. It allows for BFD sessions on interfaces that may have no IP addresses, either because the interface is unnumbered or because the layer 3 protocol status of the interfaces is not up yet. One application of BFD for interface is to run BFD over LAG/Bundle component links. An example will be given in this document.
Authors
Liang Guo
Marc Binderberger
Zuliang Wang
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)