BFD echo mode interoperability Wed, 22 June 2005 13:44 UTC

Received: from localhost.localdomain ([] by with esmtp (Exim 4.32) id 1Dl5XH-0006bI-IL; Wed, 22 Jun 2005 09:44:59 -0400
Received: from ([] by with esmtp (Exim 4.32) id 1Dl5XF-0006YG-Kk for; Wed, 22 Jun 2005 09:44:57 -0400
Received: from (ietf-mx []) by (8.9.1a/8.9.1a) with ESMTP id JAA10594 for <>; Wed, 22 Jun 2005 09:44:54 -0400 (EDT)
Received: from ([]) by with esmtp (Exim 4.33) id 1Dl5vM-00008v-Gl for; Wed, 22 Jun 2005 10:09:53 -0400
Received: from ([]) by with Microsoft SMTPSVC(6.0.3790.211); Wed, 22 Jun 2005 14:43:42 +0100
Received: from ([]) by with Microsoft SMTPSVC(5.0.2195.6713); Wed, 22 Jun 2005 14:43:37 +0100
X-MimeOLE: Produced By Microsoft Exchange V6.0.6603.0
content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
Date: Wed, 22 Jun 2005 14:42:45 +0100
Message-ID: <>
Thread-Topic: BFD echo mode interoperability
Thread-Index: AcV3L9Wb+5UEN0LhTg2AcwFAkbJV3Q==
X-OriginalArrivalTime: 22 Jun 2005 13:43:37.0746 (UTC) FILETIME=[64751F20:01C57730]
X-Spam-Score: 0.3 (/)
X-Scan-Signature: ea4ac80f790299f943f0a53be7e1a21a
Content-Transfer-Encoding: quoted-printable
Subject: BFD echo mode interoperability
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "RTG Area: Bidirectional Forwarding Detection DT" <>
List-Unsubscribe: <>, <>
List-Post: <>
List-Help: <>
List-Subscribe: <>, <>


I've been looking at the BFD base draft and am struggling to understand how interoperable BFD solutions can be developed using echo mode.

The draft states "The means by which the Echo function failures are detected is outside of the scope of this specification. Any means which will detect a communication failure is acceptable." The draft also states "A means of detecting missing Echo packets must be implemented, which most likely involves processing of the Echo packets that are received. The processing of received Echo packets is otherwise outside the scope of this specification."

This is in contrast to the asynchronous mode which uses the detect multiplier to define how many consecutive packets must be missed in order to declare a session down. I have seen an implementation that uses the detect multiplier for echo packets as well as control packets, but this behaviour is not specified in the draft.

If two vendors decide to use different methods/settings for fault detection using echo mode, this will be a real pain to configure/manage, and will also require translation between different methods in order to ensure symmetry in detecting failures in order to avoid black holing traffic.

Unless I've missed something, using echo mode in a multivendor environment does not look like an attractive solution.