Re: Small LC Comment on bfd-base-07

Jeffrey Haas <jhaas@pfrc.org> Thu, 14 February 2008 19:48 UTC

Return-Path: <rtg-bfd-bounces@ietf.org>
X-Original-To: ietfarch-rtg-bfd-archive@core3.amsl.com
Delivered-To: ietfarch-rtg-bfd-archive@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 7D58528D0A3; Thu, 14 Feb 2008 11:48:19 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.896
X-Spam-Level:
X-Spam-Status: No, score=-0.896 tagged_above=-999 required=5 tests=[AWL=1.703, BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id ZLhUCuw3euBy; Thu, 14 Feb 2008 11:48:19 -0800 (PST)
Received: from core3.amsl.com (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id C6A483A708C; Thu, 14 Feb 2008 11:48:18 -0800 (PST)
X-Original-To: rtg-bfd@core3.amsl.com
Delivered-To: rtg-bfd@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 122BD28D070 for <rtg-bfd@core3.amsl.com>; Thu, 14 Feb 2008 11:48:18 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id qfHR3QWro4mx for <rtg-bfd@core3.amsl.com>; Thu, 14 Feb 2008 11:48:17 -0800 (PST)
Received: from manos.scc.mi.org (manos.scc.mi.org [204.11.140.250]) by core3.amsl.com (Postfix) with ESMTP id 288E93A68DA for <rtg-bfd@ietf.org>; Thu, 14 Feb 2008 11:48:17 -0800 (PST)
Received: by manos.scc.mi.org (Postfix, from userid 1025) id A2CD14E4A2; Thu, 14 Feb 2008 14:49:38 -0500 (EST)
Date: Thu, 14 Feb 2008 14:49:38 -0500
From: Jeffrey Haas <jhaas@pfrc.org>
To: David Ward <dward@cisco.com>
Subject: Re: Small LC Comment on bfd-base-07
Message-ID: <20080214194938.GA23158@scc.mi.org>
References: <47B366E9.2090300@cisco.com> <3AF13E92-9A08-4A8F-BB7A-3C69492C9D05@juniper.net> <849C71E2-71A6-455E-8F4C-1DA4FBC4FFF2@cisco.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Disposition: inline
In-Reply-To: <849C71E2-71A6-455E-8F4C-1DA4FBC4FFF2@cisco.com>
User-Agent: Mutt/1.5.9i
Cc: BFD WG <rtg-bfd@ietf.org>, Dave Katz <dkatz@juniper.net>
X-BeenThere: rtg-bfd@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: "RTG Area: Bidirectional Forwarding Detection DT" <rtg-bfd.ietf.org>
List-Unsubscribe: <http://www.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: <http://www.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 Thu, Feb 14, 2008 at 12:33:51PM -0600, David Ward wrote:
> Vague language is also good if we need to add new/more diags and not  
> be "trapped."

I think this may be less dire than you're implying.

Consider the case where a session not in one of the down states always
resets the Diagnostic to 0 when not in an error state.  In order for the
session to be reset, you must also reset to the down state.  In the mean
time, you've had the opportunity to pull the current Diagnostic off the
wire.  The BFD protocol itself need not necessarily cache this, but the
management infrastructure probably should as part of the "I'm down!"
callback.

Thus, for example, the MIB could have a bfdSessDiagLastDown object along
with the bfdSessDiag object which would represent the current diag value
in the protocol.  Trap objects become slightly more interesting because
they'd might want to represent a transition out of diagnostic state 0
and potentially back.


-- Jeff