Re: MIB question - default BFD enable status?

"Thomas D. Nadeau" <tnadeau@cisco.com> Fri, 12 August 2005 11:46 UTC

Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1E3XzX-0001ca-LF; Fri, 12 Aug 2005 07:46:27 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1E3XzT-0001cT-F0 for rtg-bfd@megatron.ietf.org; Fri, 12 Aug 2005 07:46:25 -0400
Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id HAA17241 for <rtg-bfd@ietf.org>; Fri, 12 Aug 2005 07:46:21 -0400 (EDT)
Received: from rtp-iport-2.cisco.com ([64.102.122.149]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1E3YXx-0006Ty-C3 for rtg-bfd@ietf.org; Fri, 12 Aug 2005 08:22:03 -0400
Received: from rtp-core-2.cisco.com (64.102.124.13) by rtp-iport-2.cisco.com with ESMTP; 12 Aug 2005 07:46:13 -0400
X-IronPort-AV: i="3.96,103,1122868800"; d="scan'208"; a="66270704:sNHT30185778"
Received: from [10.83.15.53] (rtp-tnadeau-vpn4.cisco.com [10.83.15.53]) by rtp-core-2.cisco.com (8.12.10/8.12.6) with SMTP id j7CBkAQm000177; Fri, 12 Aug 2005 07:46:10 -0400 (EDT)
In-Reply-To: <Pine.LNX.4.61.0508120752470.20788@netcore.fi>
References: <20050810201652.GS5530@nexthop.com> <Pine.LNX.4.61.0508110755350.25486@netcore.fi> <31E8370C-8A00-4451-AB12-73B1A696CC58@cisco.com> <Pine.LNX.4.61.0508120752470.20788@netcore.fi>
Mime-Version: 1.0 (Apple Message framework v733)
Content-Type: text/plain; charset="US-ASCII"; delsp="yes"; format="flowed"
Message-Id: <0ACAFB10-AC15-4DD6-824C-594295D486E9@cisco.com>
Content-Transfer-Encoding: 7bit
From: "Thomas D. Nadeau" <tnadeau@cisco.com>
Date: Fri, 12 Aug 2005 07:46:03 -0400
To: Pekka Savola <pekkas@netcore.fi>
X-Mailer: Apple Mail (2.733)
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 69a74e02bbee44ab4f8eafdbcedd94a1
Content-Transfer-Encoding: 7bit
Cc: rtg-bfd@ietf.org, Jeffrey Haas <jhaas@nexthop.com>
Subject: Re: MIB question - default BFD enable status?
X-BeenThere: rtg-bfd@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "RTG Area: Bidirectional Forwarding Detection DT" <rtg-bfd.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/rtg-bfd>, <mailto:rtg-bfd-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:rtg-bfd@ietf.org>
List-Help: <mailto:rtg-bfd-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/rtg-bfd>, <mailto:rtg-bfd-request@ietf.org?subject=subscribe>
Sender: rtg-bfd-bounces@ietf.org
Errors-To: rtg-bfd-bounces@ietf.org

On Aug 12, 2005, at 12:54 AM, Pekka Savola wrote:

> 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 fail to see how that matters in the case of single-hop BFD.

> 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.

     When you are talking about single-hop BFD, it indeed
makes sense to configure per box and/or per interface (and
per session).

     --Tom


>
> -- 
> Pekka Savola                 "You each name yourselves king, yet the
> Netcore Oy                    kingdom bleeds."
> Systems. Networks. Security. -- George R.R. Martin: A Clash of Kings
>