Fwd: BFD statistics for BFD-MPLS sessions (fate of MIB)

venkatesan mahalingam <venkatflex@gmail.com> Thu, 04 December 2014 00:34 UTC

Return-Path: <venkatflex@gmail.com>
X-Original-To: rtg-bfd@ietfa.amsl.com
Delivered-To: rtg-bfd@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id D22E71AD03C for <rtg-bfd@ietfa.amsl.com>; Wed, 3 Dec 2014 16:34:33 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.999
X-Spam-Level:
X-Spam-Status: No, score=-1.999 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, SPF_PASS=-0.001] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id bBcI5F1rPaXY for <rtg-bfd@ietfa.amsl.com>; Wed, 3 Dec 2014 16:34:31 -0800 (PST)
Received: from mail-wi0-x232.google.com (mail-wi0-x232.google.com [IPv6:2a00:1450:400c:c05::232]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 24F3D1AD034 for <rtg-bfd@ietf.org>; Wed, 3 Dec 2014 16:34:31 -0800 (PST)
Received: by mail-wi0-f178.google.com with SMTP id em10so6741088wid.5 for <rtg-bfd@ietf.org>; Wed, 03 Dec 2014 16:34:30 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :content-type; bh=AL73h0EXWkHX5vxyBQHzJ/3ma1h/IOIAnewMbJ3wfOM=; b=Xa1Qfb4GxntjfJlYz7lwAt4jknPs0vl6lYoT91Bmw97wSIV1cnLKxyZ7lUokLzQzDL 9Zsh8Hys4FpON7+qZJPaUm09RBUFxvTGj994ksVKE5FgJg+qgePIyHsDKviLGxtNYrig ptItk0JPej25xrjuSWVixKEXYNTWQH/CfWjf1b0VT5kWrJiTTLYMERljgpwfg7mvCEST JKd9GsOqisC2TFeoE6MLKMC+tR4G4RyV088X8YhzuWM4EI54ytccdezFhIzT9A1Jt292 GP3DeG8yEnNE1bNVThHGV8myolG9DzvoNPMxh/NNdw1ACPk05PqHe7VW3WdRP+ILJ3E8 Cx+A==
MIME-Version: 1.0
X-Received: by 10.180.73.175 with SMTP id m15mr17492560wiv.0.1417653269956; Wed, 03 Dec 2014 16:34:29 -0800 (PST)
Received: by 10.194.14.130 with HTTP; Wed, 3 Dec 2014 16:34:29 -0800 (PST)
In-Reply-To: <1693791C-89AF-4023-9FCE-013F2532927E@gmail.com>
References: <20141124194751.GD28464@pfrc> <1693791C-89AF-4023-9FCE-013F2532927E@gmail.com>
Date: Wed, 03 Dec 2014 16:34:29 -0800
Message-ID: <CALXanXLTyYV33q7LpKopD4CV8nC7rcPbe-FitGcCaHsLi3uM-A@mail.gmail.com>
Subject: Fwd: BFD statistics for BFD-MPLS sessions (fate of MIB)
From: venkatesan mahalingam <venkatflex@gmail.com>
To: Jeffrey Haas <jhaas@pfrc.org>, "rtg-bfd@ietf.org" <rtg-bfd@ietf.org>
Content-Type: multipart/alternative; boundary="f46d043c7e52920c0f0509591f03"
Archived-At: http://mailarchive.ietf.org/arch/msg/rtg-bfd/VA5cyJqo1MlKFoC1fQhWN54apwE
X-BeenThere: rtg-bfd@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: "RTG Area: Bidirectional Forwarding Detection DT" <rtg-bfd.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/rtg-bfd>, <mailto:rtg-bfd-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/rtg-bfd/>
List-Post: <mailto:rtg-bfd@ietf.org>
List-Help: <mailto:rtg-bfd-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/rtg-bfd>, <mailto:rtg-bfd-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 04 Dec 2014 00:34:34 -0000

Hi Jeff,

Thanks for questions. Sorry for the delayed response.

Does your implementation provide statistics for connectivity issues in your
UI for BFD over MPLS sessions?

Yes. Our implementation provides statistics for connectivity issues.

>> Let's use these data points to discuss whether the WG will continue to
spend

>> effort on the MIB.

Sure. We are pretty much done the MIB work for BFD over MPLS sessions,
please take this MIB to the next level.

-Venkat.

*From:* Jeffrey Haas <jhaas@pfrc.org>
*Date:* November 24, 2014 at 11:47:51 AM PST
*To:* rtg-bfd@ietf.org
*Subject:* *BFD statistics for BFD-MPLS sessions (fate of MIB)*

Working Group,

One of the topics broached during our status update at IETF-91 was the fate
of the BFD MPLS MIB.  (
https://tools.ietf.org/html/draft-ietf-bfd-mpls-mib-04)

MIBs often don't get a lot of attention within IETF and there is often a
cyclic dependency issue for customer demand based on the publication of an
RFC, but no demand because there's no RFC.

There is also the issue that while BFD for MPLS is obviously a popular
protocol and supported across multiple vendors, MIBs are being generally
supplanted by Yang.  However, existing operational infrastructure still
heavily depends on SNMP polling.

------8<---- cut here ---->8------

I would like to thus turn this into a different question:

Does your implementation provide statistics for connectivity issues in your
UI for BFD over MPLS sessions?

If so, please compare them to the performance counters in the MIB.

------8<---- cut here ---->8------

The MIB obviously covers additional information, but performance counters
are usually the primary motivator for the MIB.

Let's use these data points to discuss whether the WG will continue to spend
effort on the MIB.

-- Jeff