4 Sep 2003 16:49
11 Sep 2003 18:45
Advancing RFC 2864 (IF-INVERTED-STACK-MIB)
C. M. Heard <heard <at> pobox.com>
2003-09-11 16:45:26 GMT
2003-09-11 16:45:26 GMT
[ NOTE: replies to sender, public comments to mibs <at> 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(Continue reading)
11 Sep 2003 18:36
(no subject)
C. M. Heard <heard <at> pobox.com>
2003-09-11 16:36:40 GMT
2003-09-11 16:36:40 GMT
[ NOTE: replies to sender, public comments to mibs <at> 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(Continue reading)
RSS Feed