WG Review: Bidirectional Forwarding Detection (bfd)

The IESG <iesg-secretary@ietf.org> Wed, 19 May 2004 19:42 UTC

Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA07376 for <ietf-announce-archive@ietf.org>; Wed, 19 May 2004 15:42:24 -0400 (EDT)
Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx) by ietf-mx with esmtp (Exim 4.32) id 1BQWxM-0000xI-Ik for ietf-announce-archive@ietf.org; Wed, 19 May 2004 15:42:24 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12) id 1BQWtV-0000BW-00 for ietf-announce-archive@ietf.org; Wed, 19 May 2004 15:38:26 -0400
Received: from [65.246.255.50] (helo=mx2.foretec.com) by ietf-mx with esmtp (Exim 4.12) id 1BQWqb-0007GC-00 for ietf-announce-archive@ietf.org; Wed, 19 May 2004 15:35:25 -0400
Received: from optimus22.ietf.org ([132.151.6.22] helo=optimus.ietf.org) by mx2.foretec.com with esmtp (Exim 4.24) id 1BQWbJ-00030g-By for ietf-announce-archive@ietf.org; Wed, 19 May 2004 15:19:37 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1BQVqN-00078A-0u; Wed, 19 May 2004 14:31:07 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1BQSDN-0006Ln-1P for ietf-announce@optimus.ietf.org; Wed, 19 May 2004 10:38:37 -0400
Received: from CNRI.Reston.VA.US (localhost [127.0.0.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA15914; Wed, 19 May 2004 10:38:33 -0400 (EDT)
Message-Id: <200405191438.KAA15914@ietf.org>
From: The IESG <iesg-secretary@ietf.org>
To: IETF-Announce: ;
Reply-to: iesg@ietf.org
Cc: rtg-bfd@ietf.org
Subject: WG Review: Bidirectional Forwarding Detection (bfd)
Date: Wed, 19 May 2004 10:38:33 -0400
Sender: ietf-announce-admin@ietf.org
Errors-To: ietf-announce-admin@ietf.org
X-BeenThere: ietf-announce@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ietf-announce>, <mailto:ietf-announce-request@ietf.org?subject=unsubscribe>
List-Id: <ietf-announce.ietf.org>
List-Post: <mailto:ietf-announce@ietf.org>
List-Help: <mailto:ietf-announce-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ietf-announce>, <mailto:ietf-announce-request@ietf.org?subject=subscribe>
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on ietf-mx.ietf.org
X-Spam-Status: No, hits=0.2 required=5.0 tests=AWL autolearn=no version=2.60

A new IETF working group has been proposed in the Routing Area. The IESG has not 
made any determination as yet. The following description was submitted, and is 
provided for informational purposes only. Please send your comments to the IESG 
mailing list (iesg@ietf.org) by May 26th.

Bidirectional Forwarding Detection (bfd)
----------------------------------------

Description of Working Group:

The BFD Working Group is chartered to specify a protocol for bidirectional
forwarding detection (BFD), as well as extensions to be used within the scope of
BFD and IP routing, or protocols such as MPLS that are based on IP routing,
in a way that will encourage multiple, inter-operable vendor implementations.

BFD is a protocol intended to detect faults in the bidirectional path between
two forwarding engines, including physical interfaces, subinterfaces, data
link(s), and to the extent possible the forwarding engines themselves, with
potentially very low latency. It operates independently of media, data protocols,
and routing protocols. An additional goal is to provide a single mechanism that
can be used for liveness detection over any media, at any protocol layer, with
a wide range of detection times and overhead, to avoid a proliferation of
different methods.

Important characteristics of BFD include:

    - Simple, fixed-field encoding to facilitate implementations in hardware

    - Independence of the data protocol being forwarded between two systems.
        BFD packets are carried as the payload of whatever encapsulating protocol
        is appropriate for the medium and network.

    - Path independence: BFD can provide failure detection on any kind of path
        between systems, including direct physical links, virtual circuits, tunnels,
        MPLS LSPs, multihop routed paths, and unidirectional links (so long
        as there is some return path, of course.)

    - Ability to be bootstrapped by any other protocol that automatically forms
        peer, neighbor or adjacency relationships to seed BFD endpoint discovery.

At this time the WG is chartered to complete the following work items
(additional items will require rechartering):

    1. Develop the base BFD protocol specification and submit it to the IESG
          for publication as a Proposed Standard
    2. Document BFD encapsulation and usage profile for single-hop IPv4 and IPv6
          adjacencies (e.g, physical links and IP/GRE tunnels for static routes,
          IS-IS, OSPFv2, OSPFv3, single-hop BGP) and submit the specification to the
          IESG for publication as a Proposed Standard.
    3. Document BFD encapsulation and usage profile for MPLS LSPs and submit
          the specification to the IESG for publication as a Proposed Standard.
    4. Develop the MIB module for BFD and submit it to the IESG for publication
          as a Proposed Standard.
    5. Document BFD encapsulation and usage profile for multi-hop IPv4 and IPv6
          adjacencies (e.g. OSPF virtual links and iBGP sessions) and submit
          the specification to the IESG for publication as a Proposed Standard.

Topics for Possible Future Work:

    1. Document BFD directly over 802.3 in close collaboration and synchronization
          with the IEEE. 


_______________________________________________
IETF-Announce mailing list
IETF-Announce@ietf.org
https://www1.ietf.org/mailman/listinfo/ietf-announce