RE: MIB question - default BFD enable status? Mon, 15 August 2005 10:44 UTC

Received: from localhost.localdomain ([] by with esmtp (Exim 4.32) id 1E4cSB-0003uT-MQ; Mon, 15 Aug 2005 06:44:27 -0400
Received: from ([] by with esmtp (Exim 4.32) id 1E4cS9-0003uJ-V0 for; Mon, 15 Aug 2005 06:44:26 -0400
Received: from (ietf-mx []) by (8.9.1a/8.9.1a) with ESMTP id GAA25317 for <>; Mon, 15 Aug 2005 06:44:23 -0400 (EDT)
Received: from ([]) by with esmtp (Exim 4.43) id 1E4d1F-0003Sc-A7 for; Mon, 15 Aug 2005 07:20:43 -0400
Received: from ([]) by with Microsoft SMTPSVC(6.0.3790.211); Mon, 15 Aug 2005 11:43:57 +0100
Received: from ([]) by with Microsoft SMTPSVC(5.0.2195.6713); Mon, 15 Aug 2005 11:44:04 +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: Mon, 15 Aug 2005 11:44:03 +0100
Message-ID: <>
Thread-Topic: MIB question - default BFD enable status?
Thread-Index: AcWe+k612SMzZ2XNQR2pFHZoijdeewCh1+Kg
X-OriginalArrivalTime: 15 Aug 2005 10:44:04.0300 (UTC) FILETIME=[414A38C0:01C5A186]
X-Spam-Score: 0.3 (/)
X-Scan-Signature: 5a9a1bd6c2d06a21d748b7d0070ddcb8
Content-Transfer-Encoding: quoted-printable
Subject: RE: MIB question - default BFD enable status?
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "RTG Area: Bidirectional Forwarding Detection DT" <>
List-Unsubscribe: <>, <>
List-Post: <>
List-Help: <>
List-Subscribe: <>, <>


BFD needs to be "configured" at the forwarding protocol level (i.e. IPv4, IPv6, MPLS), and in some cases at the control protocol level (e.g. per static route, per EBGP peer). However, ideally an implementation will also support the ability to "enable/disable" configured BFD sessions at the global level, as well as at the per session/interface level. The global enable/disable command is useful for router commissioning scenarios (e.g. to wait until the other nodes in the network have been configured before enabling BFD) and for troubleshooting scenarios (e.g. if BFD is not operating correctly on a particular system).

To use your BGP analogy, BGP sessions are configured on a per peer basis, but all BGP implementation should support the ability to clear/reset sessions at the global level, as well as at the peer level.

Regarding the original question, I agree with Jeff/Tom that the default value for the MIB should be 'disabled', and that r-o should suffice.


> -----Original Message-----
> From: []On
> Behalf Of Pekka Savola
> Sent: 12 August 2005 05:55
> To: Thomas D. Nadeau
> Cc:; Jeffrey Haas
> Subject: Re: MIB question - default BFD enable status?
> On Thu, 11 Aug 2005, Thomas D. Nadeau wrote:
> >> But even if we do, I don't think this global feature is 
> even needed -- 
> >> isn't it enough to have interface, protocol, or other 
> status values which 
> >> the operators can then snmpwalk through ?
> >
> >    I know of at least one implementation that has BFD as a global
> > configuration.
> Let's take an analogue.  Does the same implementation have a global 
> configuration to enable/disable BGP?  BGP and BFD sessions seem like 
> similar beasts, and similar management techniques apply.
> I can only see (real) usefulness for session-based controls (and 
> "enable BGP/BFD" toggle without session-specific config is quite 
> questionable), but others might have different requirements so this 
> isn't really a big issue to get too excited about.
> -- 
> Pekka Savola                 "You each name yourselves king, yet the
> Netcore Oy                    kingdom bleeds."
> Systems. Networks. Security. -- George R.R. Martin: A Clash of Kings