abandoning ike-monitor-mib, isakmp-di-mon-mib, and monitor-mib?
John Shriver <jshriver+ietf@sockeye.com> Fri, 13 June 2003 21:46 UTC
Received: from lists.tislabs.com (portal.gw.tislabs.com [192.94.214.101]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA24274 for <ipsec-archive@lists.ietf.org>; Fri, 13 Jun 2003 17:46:30 -0400 (EDT)
Received: by lists.tislabs.com (8.9.1/8.9.1) id PAA21466 Fri, 13 Jun 2003 15:56:25 -0400 (EDT)
Message-ID: <3EEA2CF9.50106@sockeye.com>
Date: Fri, 13 Jun 2003 15:58:49 -0400
From: John Shriver <jshriver+ietf@sockeye.com>
Organization: Sockeye Networks
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.0.1) Gecko/20020826
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: ipsec@lists.tislabs.com
Subject: abandoning ike-monitor-mib, isakmp-di-mon-mib, and monitor-mib?
Content-Type: text/plain; charset="us-ascii"; format="flowed"
Content-Transfer-Encoding: 7bit
Sender: owner-ipsec@lists.tislabs.com
Precedence: bulk
Content-Transfer-Encoding: 7bit
OK, let's try and sort out the MIB issues one decision at a time. The first thing is to decide if we want to abandon the original set of MIBs: draft-ietf-ipsec-ike-monitor-mib-04.txt, draft-ietf-ipsec-isakmp-di-mon-mib-05.txt, and draft-ietf-ipsec-monitor-mib-06.txt They have never attracted much interest. Neither of the original authors work in the IPsec marketplace anymore, so they can't contribute any implementations to get them through the standards process. I think that there is only one implementation of them, ever. Moreover, both the ISAKMP and IKE MIB modules would require MAJOR rewriting to be compatible with IKE Version 2. Like merging them, since the ISAKMP/IKE layering is extinct in v2. So, given this set of considerable problems, is there anyone who wants these MIBs to track the IPsec standards going forwards, and can find resources to update them and implement them? If nobody wants to do this, will we take the lack of any dissent on their death as "consensus" per the "IETF Process"? I *NEED* to know this, because there are a number of TEXTUAL-CONVENTIONS in the doi-tc-mib that were only used by these three MIBs, and are not used by the IPsec flow MIB, or by the Policy MIB. Since it looks like the doi-tc-mib will NOT be maintained by the IANA (no enumerations), the TC's have to be used in some MIB to progress through the standards process, so we can't stock up on "spare" TCs for possible future needs. So, please consider this a "last call", only for termination instead of promotion along the standards track.