BFD for Multipoint Networks
draft-katz-ward-bfd-multipoint-02
| Document | Type |
Replaced Internet-Draft
(bfd WG)
Expired & archived
|
|
|---|---|---|---|
| Authors | Dave Katz , David Ward | ||
| Last updated | 2009-02-05 | ||
| Replaced by | draft-ietf-bfd-multipoint | ||
| RFC stream | Internet Engineering Task Force (IETF) | ||
| Intended RFC status | (None) | ||
| Formats | |||
| Additional resources | Mailing list discussion | ||
| Stream | WG state | WG Document | |
| Document shepherd | (None) | ||
| IESG | IESG state | Replaced by draft-ietf-bfd-multipoint | |
| Consensus boilerplate | Unknown | ||
| 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 extensions to the Bidirectional Forwarding Detection (BFD) protocol for its use in multipoint and multicast networks. Comments on this draft should be directed to rtg- bfd@ietf.org. Conventions used in this document The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this document are to be interpreted as described in RFC-2119 [KEYWORDS].
Authors
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)