RE: IPsec Monitoring Mib
Tim Jenkins <TJenkins@Catena.com> Thu, 25 April 2002 15:15 UTC
Received: from lists.tislabs.com (portal.gw.tislabs.com [192.94.214.101]) by above.proper.com (8.11.6/8.11.3) with ESMTP id g3PFFda27731; Thu, 25 Apr 2002 08:15:39 -0700 (PDT)
Received: by lists.tislabs.com (8.9.1/8.9.1) id JAA21765 Thu, 25 Apr 2002 09:28:57 -0400 (EDT)
Message-ID: <231417CB271FD61197020002A593077F2E0905@CAT01S2C>
From: Tim Jenkins <TJenkins@Catena.com>
To: "'Christopher R. Cook'" <ccook@quarrytech.com>, "'ipsec@lists.tislabs.com'" <ipsec@lists.tislabs.com>
Subject: RE: IPsec Monitoring Mib
Date: Thu, 25 Apr 2002 09:13:31 -0400
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
Content-Type: text/plain; charset="iso-8859-1"
Sender: owner-ipsec@lists.tislabs.com
Precedence: bulk
Here's my view. Some time ago, Ted asked if there were any deployments/interest/implementations of the series of MIB document written by John Shriver and me, in an attempt to take them to last call. The only response I recall was from the authors of another MIB. This lead to a debate/discussion where it was suggested that that MIB replace the series first mentioned. Nothing was resolved. The bottom line is that there was little response on the mailing list, even though I have received numerous private emails; none of those people posted on the list to say that they were looking at/implementating/considering or whatever the MIB. I have also sent Ted emails asking him what his opinion of the status is, and I've heard nothing back. As far as changes to the documents themselves go, they are ready for last call. Tim > -----Original Message----- > From: Christopher R. Cook [mailto:ccook@quarrytech.com] > Sent: Wednesday, April 24, 2002 12:35 PM > To: ipsec@lists.tislabs.com > Subject: IPsec Monitoring Mib > > > Any status on Tim Jenkins's IPsec Tunnel monitoring Mib ... > > Initial draft was to expire April 4, 2002 .... > > Are there any current WG's addressing monitoring for IPsec... > > Thanks >
- IPsec Monitoring Mib Christopher R. Cook
- RE: IPsec Monitoring Mib Tim Jenkins
- RE: IPsec Monitoring Mib Casey Carr
- RE: IPsec Monitoring Mib Amit Chitale
- RE: IPsec Monitoring Mib Christopher R. Cook