[Bridge-mib] Advancing RFC 2864 (IF-INVERTED-STACK-MIB)
"C. M. Heard" <heard@pobox.com> Fri, 12 September 2003 08:48 UTC
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id EAA13422 for <bridge-archive@odin.ietf.org>; Fri, 12 Sep 2003 04:48:25 -0400 (EDT)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19xjb1-0004cz-Me for bridge-archive@odin.ietf.org; Fri, 12 Sep 2003 04:48:03 -0400
Received: (from exim@localhost) by www1.ietf.org (8.12.8/8.12.8/Submit) id h8C8m3Rg017789 for bridge-archive@odin.ietf.org; Fri, 12 Sep 2003 04:48:03 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19xjb0-0004ck-KU; Fri, 12 Sep 2003 04:48:02 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19xUZW-0006eR-By for bridge-mib@optimus.ietf.org; Thu, 11 Sep 2003 12:45:30 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA00622; Thu, 11 Sep 2003 12:45:22 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19xUZU-0003Dq-00; Thu, 11 Sep 2003 12:45:28 -0400
Received: from smtpout1.bayarea.net ([209.128.95.10]) by ietf-mx with esmtp (Exim 4.12) id 19xUZT-0003Dn-00; Thu, 11 Sep 2003 12:45:27 -0400
Received: from shell4.bayarea.net (shell4.BAYAREA.NET [209.128.82.1]) by smtpout1.bayarea.net (8.12.8/8.12.8) with ESMTP id h8BGmGhs008304; Thu, 11 Sep 2003 09:48:16 -0700
Received: from localhost (heard@localhost) by shell4.bayarea.net (8.11.6/8.11.6) with ESMTP id h8BGjQG12519; Thu, 11 Sep 2003 09:45:26 -0700
X-Authentication-Warning: shell4.bayarea.net: heard owned process doing -bs
Date: Thu, 11 Sep 2003 09:45:26 -0700
From: "C. M. Heard" <heard@pobox.com>
X-Sender: heard@shell4.bayarea.net
To: mibs@ops.ietf.org
Message-ID: <Pine.LNX.4.10.10309110943150.31919-100000@shell4.bayarea.net>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset="US-ASCII"
Subject: [Bridge-mib] Advancing RFC 2864 (IF-INVERTED-STACK-MIB)
Sender: bridge-mib-admin@ietf.org
Errors-To: bridge-mib-admin@ietf.org
X-BeenThere: bridge-mib@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/bridge-mib>, <mailto:bridge-mib-request@ietf.org?subject=unsubscribe>
List-Id: <bridge-mib.ietf.org>
List-Post: <mailto:bridge-mib@ietf.org>
List-Help: <mailto:bridge-mib-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/bridge-mib>, <mailto:bridge-mib-request@ietf.org?subject=subscribe>
[ NOTE: replies to sender, public comments to mibs@ops.ietf.org ] Colleagues -- As those of you who saw the recent announcement on the IETF-Announce list will know, instead of getting rechartered and reactivated the ifmib WG got closed down. That leaves the IF-MIB (RFC 2863) at Draft Standard and the IF-INVERTED-STACK-MIB (RFC 2864) at Proposed Standard. It occurred to me that a useful interim step would be to collect the implementation reports needed to advance RFC 2864 to Draft Standard, and I have volunteered to do just that. So, if you or your organization has implemented the IF-INVERTED-STACK-MIB, I would appreciate it if you would fill out the following template and return it to me. If you would prefer that your company's name not be made public, please so indicate and its name will be omitted from the public version of the implementation report (although it must be disclosed to the IESG in order for the data to be included). Note that the template below is intended to evaluate conformance to the ifInvCompliance compliance statement, and consequently requests information not only on the ifInvStackTable but also on the ifStackTable and ifStackLastChange, which are defined in IF-MIB. Since ifInvCompliance does not have an OBJECT clause that specifies a MIN-ACCESS of read-only for ifStackStatus, it would be of particular interest to hear of implementations that actually provide read-create access to that object. In the template below please fill in the items in angle brackets and if the information is available please attach the results of a MIB dump of ifStackStatus, ifStackTable, and ifInvStackTable (cf. RFC 2438). I will put together a summary of the information that is received and forward it to the IESG. Regards, Mike Heard ================================================================= Vendor implementation report for RFC 2864 (IF-INVERTED-STACK-MIB) Evaluation of compliance statement ifInvCompliance Legend: yes - implemented, no - not implemented, ro - implemented as read-only Vendor <vendor name> info as of <date> ifInvStackGroup (this module) ifInvStackStatus <yes|no> ifStackGroup2 (IF-MIB) ifStackStatus <yes|no|ro> ifStackLastChange <yes|no> <attach MIB dump of ifStackStatus, ifStackTable, ifInvStackTable> _______________________________________________ Bridge-mib mailing list Bridge-mib@ietf.org https://www1.ietf.org/mailman/listinfo/bridge-mib