From disman-bounces@ietf.org Mon Apr 4 14:11:11 2005 Received: from megatron.ietf.org (megatron.ietf.org [132.151.6.71]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA07214 for ; Mon, 4 Apr 2005 14:11:11 -0400 (EDT) Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1DIVxF-0000of-Ic; Mon, 04 Apr 2005 14:05:41 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1DIVxE-0000oO-0T; Mon, 04 Apr 2005 14:05:40 -0400 Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA05960; Mon, 4 Apr 2005 14:05:39 -0400 (EDT) Received: from pop-a065c10.pas.sa.earthlink.net ([207.217.121.184]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1DIW5D-0003Eq-Bg; Mon, 04 Apr 2005 14:13:55 -0400 Received: from h-68-166-189-216.snvacaid.dynamic.covad.net ([68.166.189.216] helo=oemcomputer) by pop-a065c10.pas.sa.earthlink.net with smtp (Exim 3.36 #10) id 1DIVxB-0003hP-00; Mon, 04 Apr 2005 11:05:37 -0700 Message-ID: <002e01c53941$1340d2c0$7f1afea9@oemcomputer> From: "Randy Presuhn" To: "LTRU Working Group" , "Disman" Date: Mon, 4 Apr 2005 11:06:50 -0700 X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 6.00.2800.1478 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1478 X-Spam-Score: 0.0 (/) X-Scan-Signature: 21c69d3cfc2dd19218717dbe1d974352 Subject: [Disman] Fw: Enforcement of Updated IPR Boilerplate X-BeenThere: disman@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Distributed Management List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: disman-bounces@ietf.org Errors-To: disman-bounces@ietf.org Hi - Anyone submitting or planning to submit internet drafts, please take note! > From: "IETF Secretariat" > To: "IETF Announcement list" > Cc: ; ; > Sent: Monday, April 04, 2005 10:05 AM > Subject: Enforcement of Updated IPR Boilerplate > > As you may be aware, RFC 3667 (BCP 78), "IETF Rights in Contributions," > has been obsoleted by RFC 3978 (BCP 78), which was published in March > 2005, and which bears the same title. The major difference between the > two RFCs is that the IPR-related notices and disclaimers that the IETF > requires in all Internet-Drafts have been updated to correct anomalies. > > The updated versions of the required notices and disclaimers are specified > in Section 5, "Notices Required in IETF Documents," of RFC 3978, and in > Section 3, "IPR-Related Notices Required in Internet-Drafts," of the > recently revised "Guidelines to Authors of Internet-Drafts" > (http://www.ietf.org/ietf/1id-guidelines.html). The "Guidelines" document > also provides additional guidance regarding the placement of these notices. > > Currently, the IETF Secretariat accepts and posts Internet-Drafts that > include *either* the RFC 3667 or the RFC 3978 version of these notices. > However, as of 17:00 ET on Friday May 6, 2005, the Secretariat will > accept *only* those Internet-Drafts that comply with the requirements > of RFC 3978, and with the most recent version of the "Guidelines" > document. > > Please note that the required notices and disclaimers must be reproduced > verbatim since they have been legally reviewed and formally adopted as part > of the IETF process. The Secretariat will not accept deviations from the > specified text, nor will it correct the text. Any documents that do not > comply with the requirements will be returned to the submitter. > > The IETF Secretariat > > _______________________________________________ > IETF-Announce mailing list > IETF-Announce@ietf.org > https://www1.ietf.org/mailman/listinfo/ietf-announce From disman-bounces@ietf.org Thu Apr 14 15:07:44 2005 Received: from megatron.ietf.org (megatron.ietf.org [132.151.6.71]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA13020 for ; Thu, 14 Apr 2005 15:07:44 -0400 (EDT) Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1DM9ev-0001qW-48; Thu, 14 Apr 2005 15:05:49 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1DM9et-0001h5-0F; Thu, 14 Apr 2005 15:05:47 -0400 Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA12721; Thu, 14 Apr 2005 15:05:41 -0400 (EDT) Received: from pop-a065d10.pas.sa.earthlink.net ([207.217.121.251]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1DM9or-00050Z-Bs; Thu, 14 Apr 2005 15:16:06 -0400 Received: from h-68-165-2-188.snvacaid.dynamic.covad.net ([68.165.2.188] helo=oemcomputer) by pop-a065d10.pas.sa.earthlink.net with smtp (Exim 3.36 #10) id 1DM9ee-0006CZ-00; Thu, 14 Apr 2005 12:05:32 -0700 Message-ID: <000c01c54125$2342c160$7f1afea9@oemcomputer> From: "Randy Presuhn" To: "LTRU Working Group" , , "Disman" Date: Thu, 14 Apr 2005 12:06:57 -0700 X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 6.00.2800.1478 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1478 X-Spam-Score: 0.1 (/) X-Scan-Signature: f4c2cf0bccc868e4cc88dace71fb3f44 Subject: [Disman] Fw: Outages on IETF servers in the near future X-BeenThere: disman@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Distributed Management List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: disman-bounces@ietf.org Errors-To: disman-bounces@ietf.org Hi - Forwarded for your information. Randy > From: > To: > Cc: ; > Sent: Thursday, April 14, 2005 11:35 AM > Subject: Outages on IETF servers in the near future > > > Hi All, > > I want to let you know about some scheduled maintenance activities > that may cause network and mail outages on ietf.org sites. The > activities, which are described below, have been scheduled for the > next four Saturday mornings, from 08:00 or 09:00 until 12:00 ET. > Please check the IETF System Status Page (http://noc.ietf.org/) > periodically for updates on the status of these activities. If you > have any questions, then please feel free to send them my way. > > sb. Scott Blomquist ietf-admin@techsquare.com > ----- > * Sat 4/16 - 08:00 EST - 12:00 EST > Task: reorganizing mailing list archives > Affected: The mailing lists will be down for a good portion of the morning > Comment: I am going to try and get this down in less than 2 hours > but I am giving myself a little extra time just in case > > * Sat 4/23 - 09:00 EST - 12:00 EST > Task: reorganizing CNRI network infrastructure part 1 > Affected: there should be no services affected > Comment: just in case there are some minor network outages this is > what is going on at CNRI > > * Sat 4/30 - 09:00 EST - 12:00 EST > Task: Reorganizing CNRI network infrastructure part 2 > Affected: There maybe some minor (up to 1/2hour) network outages on > ietf systems. > Comment: None > > * Sat 5/7 - 09:00 EST - 12:00 EST > Task: reorganizing CNRI network infrastructure part 3 > Affected: there should be no services affected > Comment: just in case there are some minor network outages this is > what is going on at CNRI > > > _______________________________________________ > Ietf mailing list > Ietf@ietf.org > https://www1.ietf.org/mailman/listinfo/ietf From disman-bounces@ietf.org Tue Apr 19 05:56:37 2005 Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1DNpTA-00036R-Fv; Tue, 19 Apr 2005 05:56:36 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1DNpT7-00036E-VD for disman@megatron.ietf.org; Tue, 19 Apr 2005 05:56:34 -0400 Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id FAA23069 for ; Tue, 19 Apr 2005 05:56:30 -0400 (EDT) Received: from mail.ammion.com ([62.231.40.83] helo=ammionexch.ammion.com) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1DNpe4-0006cG-3j for disman@ietf.org; Tue, 19 Apr 2005 06:07:55 -0400 X-Mimeole: Produced By Microsoft Exchange V6.0.4712.0 content-class: urn:content-classes:message MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----_=_NextPart_001_01C544C6.09017E62" Date: Tue, 19 Apr 2005 10:56:19 +0100 Message-ID: <32C54C3F4BD88347AF45A62B195133C41C1B35@ammionexch.ammion.com> Thread-Topic: Status of the Application MIB (RFC 2564) Thread-Index: AcVExgcvwVIiuDoFT0ilNnP7T+GDcw== From: "Dave Anderson" To: X-Spam-Score: 0.1 (/) X-Scan-Signature: 156eddb66af16eef49a76ae923b15b92 Subject: [Disman] Status of the Application MIB (RFC 2564) X-BeenThere: disman@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Distributed Management List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: disman-bounces@ietf.org Errors-To: disman-bounces@ietf.org This is a multi-part message in MIME format. ------_=_NextPart_001_01C544C6.09017E62 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable All, =20 After reading RFC 2564 some time ago I've been wondering what became of this proposal? I haven't found an implementation, nor have I found an RFC which obsoletes the Application-MIB. =20 I've done some work that may become a base to build an open-source implementation for this RFC (See the thread on net-snmp-users http://sourceforge.net/mailarchive/message.php?msg_id=3D11179049). =20 It seems unlikely that nobody has implemented this already, so perhaps there is a newer, better replacement for monitoring application throughput? =20 Best Regards =20 Dave -- ammeon.com =20 =20 ------_=_NextPart_001_01C544C6.09017E62 Content-Type: text/html; charset="us-ascii" Content-Transfer-Encoding: quoted-printable

All,

 

After reading RFC 2564 some time ago I’ve been wondering what became of this proposal? I haven’t found an = implementation, nor have I found an RFC which obsoletes the = Application-MIB.

 

I’ve done some work that may become a base to = build an open-source implementation for this RFC (See the thread on = net-snmp-users http://sourceforge.net/mailarchive/message.php?msg_id=3D11179049).

 

It seems unlikely that nobody has implemented this = already, so perhaps there is a newer, better replacement for monitoring = application throughput?

 

Best Regards

 

Dave

--

ammeon.com

 

 

------_=_NextPart_001_01C544C6.09017E62-- From disman-bounces@ietf.org Tue Apr 19 16:19:34 2005 Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1DNzC2-0007h9-BK; Tue, 19 Apr 2005 16:19:34 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1DNzC1-0007gg-IO for disman@megatron.ietf.org; Tue, 19 Apr 2005 16:19:33 -0400 Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA23237 for ; Tue, 19 Apr 2005 16:19:30 -0400 (EDT) Received: from rwcrmhc12.comcast.net ([216.148.227.85]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1DNzN6-0006nz-1G for disman@ietf.org; Tue, 19 Apr 2005 16:31:00 -0400 Received: from [192.168.20.102] (c-24-91-217-223.hsd1.ma.comcast.net[24.91.217.223]) by comcast.net (rwcrmhc12) with SMTP id <2005041920192201400np57ue>; Tue, 19 Apr 2005 20:19:22 +0000 In-Reply-To: <32C54C3F4BD88347AF45A62B195133C41C1B35@ammionexch.ammion.com> References: <32C54C3F4BD88347AF45A62B195133C41C1B35@ammionexch.ammion.com> Mime-Version: 1.0 (Apple Message framework v619.2) Content-Type: multipart/alternative; boundary=Apple-Mail-13-343291874 Message-Id: From: Jon Saperia Subject: Re: [Disman] Status of the Application MIB (RFC 2564) Date: Tue, 19 Apr 2005 16:19:21 -0400 To: "Dave Anderson" X-Mailer: Apple Mail (2.619.2) X-Spam-Score: 0.6 (/) X-Scan-Signature: 4b7d60495f1a7f2e853e8cbae7e6dbfc Cc: disman@ietf.org X-BeenThere: disman@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Distributed Management List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: disman-bounces@ietf.org Errors-To: disman-bounces@ietf.org --Apple-Mail-13-343291874 Content-Type: text/plain; charset=WINDOWS-1252; format=flowed Content-Transfer-Encoding: quoted-printable Dave, I have not followed this very closely of late, but last I knew some=20 vendors implemented a few objects here and there that look like they=20 could have come from this module. This is very much like other MIB=20 Modules, the System Application and Host Resources Modules being two=20 good examples - though their implementation is broader. If you have a=20= reference implementation, that would be a good thing. I would think=20 that people might want to use it with some open source servers. /jon On Apr 19, 2005, at 5:56 AM, Dave Anderson wrote: > All, > > =A0 > > After reading RFC 2564 some time ago I=92ve been wondering what became=20= > of this proposal? I haven=92t found an implementation, nor have I = found=20 > an RFC which obsoletes the Application-MIB. > > =A0 > > I=92ve done some work that may become a base to build an open-source=20= > implementation for this RFC (See the thread on net-snmp-users=20 > http://sourceforge.net/mailarchive/message.php?msg_id=3D11179049). > > =A0 > > It seems unlikely that nobody has implemented this already, so perhaps=20= > there is a newer, better replacement for monitoring application=20 > throughput? > > =A0 > > Best Regards > > =A0 > > Dave > > -- > > ammeon.com > > =A0 > > =A0 > ----- Jon Saperia saperia@jdscons.com Phone: 978-461-0249 Fax: 617-249-0874 http://www.jdscons.com/ --Apple-Mail-13-343291874 Content-Type: text/enriched; charset=WINDOWS-1252 Content-Transfer-Encoding: quoted-printable Dave, I have not followed this very closely of late, but last I knew some vendors implemented a few objects here and there that look like they could have come from this module. This is very much like other MIB Modules, the System Application and Host Resources Modules being two good examples - though their implementation is broader. If you have a reference implementation, that would be a good thing. I would think that people might want to use it with some open source servers. /jon On Apr 19, 2005, at 5:56 AM, Dave Anderson wrote: = ArialAll,= = Arial=A0 ArialAfter reading RFC 2564 some time ago I=92ve been wondering what became of this proposal? I haven=92t found an implementation, nor have I found an RFC which obsoletes the Application-MIB. = Arial=A0 ArialI=92ve done some work that may become a base to build an open-source implementation for this RFC (See the thread on net-snmp-users = 0000,0000,FFFFhttp://so= urceforge.net/mailarchive/message.php?msg_id=3D11179049). = Arial=A0 ArialIt seems unlikely that nobody has implemented this already, so perhaps there is a newer, better replacement for monitoring application = throughput? = Arial=A0 ArialBest = Regards = Arial=A0 = ArialDave = Arial-- = Arialammeon.com = Arial=A0 = Arial=A0 ----- Jon Saperia saperia@jdscons.com Phone: 978-461-0249 Fax: 617-249-0874 http://www.jdscons.com/ --Apple-Mail-13-343291874-- From disman-bounces@ietf.org Wed Apr 27 11:21:11 2005 Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1DQoLf-0000i5-Mq; Wed, 27 Apr 2005 11:21:11 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1DQoLe-0000gy-EZ for disman@megatron.ietf.org; Wed, 27 Apr 2005 11:21:10 -0400 Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA24004 for ; Wed, 27 Apr 2005 11:21:08 -0400 (EDT) From: c.kalbfleisch@comcast.net Received: from rwcrmhc14.comcast.net ([216.148.227.89]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1DQoYI-00075n-Ff for disman@ietf.org; Wed, 27 Apr 2005 11:34:16 -0400 Received: from 204.127.197.119 ([204.127.197.119]) by comcast.net (rwcrmhc14) with SMTP id <2005042715205801400fq6tee>; Wed, 27 Apr 2005 15:20:58 +0000 Received: from [65.119.52.228] by 204.127.197.119; Wed, 27 Apr 2005 15:20:58 +0000 To: disman@ietf.org Date: Wed, 27 Apr 2005 15:20:58 +0000 Message-Id: <042720051520.6727.426FADDA00029BA900001A472200761438080C9C070A04000D040E05D20C@comcast.net> X-Mailer: AT&T Message Center Version 1 (Dec 17 2004) X-Authenticated-Sender: Yy5rYWxiZmxlaXNjaEBjb21jYXN0Lm5ldA== MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="NextPart_Webmail_9m3u9jl4l_6727_1114615258_0" X-Spam-Score: 1.2 (+) X-Scan-Signature: 9182cfff02fae4f1b6e9349e01d62f32 Subject: [Disman] Alarm MIB implementations X-BeenThere: disman@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Distributed Management List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: disman-bounces@ietf.org Errors-To: disman-bounces@ietf.org --NextPart_Webmail_9m3u9jl4l_6727_1114615258_0 Content-Type: text/plain Content-Transfer-Encoding: 8bit Hi, I was curious if there are implementations of RFC-3877 out there particularly in management stations and applications. I am working on defining the MIBs for a device and am looking at using this MIB to represent alarm information. So was wondering if people know of NMS's that may be able to manage my device if I implement this. Thanks Carl --NextPart_Webmail_9m3u9jl4l_6727_1114615258_0 Content-Type: text/html Content-Transfer-Encoding: 8bit
Hi,
 
I was curious if there are implementations of RFC-3877 out there particularly in management stations and applications. I am working on defining the MIBs for a device and am looking at using this MIB to represent alarm information. So was wondering if people know of NMS's that may be able to manage my device if I implement this.
 
Thanks
Carl
 
--NextPart_Webmail_9m3u9jl4l_6727_1114615258_0-- From disman-bounces@ietf.org Wed Apr 27 17:06:20 2005 Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1DQtjg-0007k7-4e; Wed, 27 Apr 2005 17:06:20 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1DQtL6-0001PA-A4 for disman@megatron.ietf.org; Wed, 27 Apr 2005 16:40:58 -0400 Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA04394 for ; Wed, 27 Apr 2005 16:40:52 -0400 (EDT) Received: from zcars04f.nortelnetworks.com ([47.129.242.57]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1DQtXm-0001ME-3n for disman@ietf.org; Wed, 27 Apr 2005 16:54:03 -0400 Received: from zcars2ky.ca.nortel.com (zcars2ky.ca.nortel.com [47.129.242.221]) by zcars04f.nortelnetworks.com (Switch-2.2.6/Switch-2.2.0) with ESMTP id j3RKef306556 for ; Wed, 27 Apr 2005 16:40:41 -0400 (EDT) Received: from zcard305.ca.nortel.com (zcard305.ca.nortel.com [47.129.242.61]) by zcars2ky.ca.nortel.com (Switch-2.2.0/Switch-2.2.0) with ESMTP id j3RKere25196 for ; Wed, 27 Apr 2005 16:40:53 -0400 (EDT) Received: by zcard305.ca.nortel.com with Internet Mail Service (5.5.2653.19) id ; Wed, 27 Apr 2005 16:40:40 -0400 Message-ID: <713043CE8B8E1348AF3C546DBE02C1B4032E353A@zcarhxm2.corp.nortel.com> From: "Sharon Chisholm" To: disman@ietf.org Subject: RE: [Disman] Alarm MIB implementations Date: Wed, 27 Apr 2005 16:40:33 -0400 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.2653.19) Content-Type: text/plain X-Spam-Score: 0.0 (/) X-Scan-Signature: 8abaac9e10c826e8252866cbe6766464 X-Mailman-Approved-At: Wed, 27 Apr 2005 17:06:19 -0400 X-BeenThere: disman@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Distributed Management List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: disman-bounces@ietf.org Errors-To: disman-bounces@ietf.org hi I know of two potential third party management applications implementations, but I am not sure of their current status or if the vendors have made this public so I don't want to name them explicitly. Also based on the private email questions I get, a lot of people are considering implementations, but I'm not sure if they are looking device side or management application. Plus, of course the work within my own organization. Sharon -----Original Message----- From: disman-bounces@ietf.org [mailto:disman-bounces@ietf.org] On Behalf Of c.kalbfleisch@comcast.net Sent: Wednesday, April 27, 2005 11:21 AM To: disman@ietf.org Subject: [Disman] Alarm MIB implementations Hi, I was curious if there are implementations of RFC-3877 out there particularly in management stations and applications. I am working on defining the MIBs for a device and am looking at using this MIB to represent alarm information. So was wondering if people know of NMS's that may be able to manage my device if I implement this. Thanks Carl From disman-bounces@ietf.org Thu Apr 28 15:58:51 2005 Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1DRF9v-0000Wn-91; Thu, 28 Apr 2005 15:58:51 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1DRF9t-0000Wh-V9 for disman@megatron.ietf.org; Thu, 28 Apr 2005 15:58:49 -0400 Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA19893 for ; Thu, 28 Apr 2005 15:58:48 -0400 (EDT) Received: from pop-a065c32.pas.sa.earthlink.net ([207.217.121.247]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1DRFMo-0002TW-3j for disman@ietf.org; Thu, 28 Apr 2005 16:12:11 -0400 Received: from h-64-105-35-114.snvacaid.dynamic.covad.net ([64.105.35.114] helo=oemcomputer) by pop-a065c32.pas.sa.earthlink.net with smtp (Exim 3.36 #10) id 1DRF9n-0002lR-00 for disman@ietf.org; Thu, 28 Apr 2005 12:58:43 -0700 Message-ID: <003d01c54c2c$f604aa20$7f1afea9@oemcomputer> From: "Randy Presuhn" To: References: <713043CE8B8E1348AF3C546DBE02C1B4032E353A@zcarhxm2.corp.nortel.com> Subject: Re: [Disman] Alarm MIB implementations Date: Thu, 28 Apr 2005 13:00:04 -0700 X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 6.00.2800.1478 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1478 X-Spam-Score: 0.1 (/) X-Scan-Signature: 7655788c23eb79e336f5f8ba8bce7906 X-BeenThere: disman@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Distributed Management List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: disman-bounces@ietf.org Errors-To: disman-bounces@ietf.org Hi - > From: "Sharon Chisholm" > To: > Sent: Wednesday, April 27, 2005 1:40 PM > Subject: RE: [Disman] Alarm MIB implementations ... > I know of two potential third party management applications implementations, > but I am not sure of their current status or if the vendors have made this > public so I don't want to name them explicitly. Also based on the private > email questions I get, a lot of people are considering implementations, but > I'm not sure if they are looking device side or management application. > > Plus, of course the work within my own organization. ... Have any issues surfaced in the course of implementation where changes or clarifications to the specification would be helpful? Randy From disman-bounces@ietf.org Fri Apr 29 13:25:01 2005 Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1DRZEb-0007gC-LH; Fri, 29 Apr 2005 13:25:01 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1DRZEa-0007g0-AP for disman@megatron.ietf.org; Fri, 29 Apr 2005 13:25:00 -0400 Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA18697 for ; Fri, 29 Apr 2005 13:24:57 -0400 (EDT) Received: from zcars04f.nortelnetworks.com ([47.129.242.57]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1DRZRa-0006W1-75 for disman@ietf.org; Fri, 29 Apr 2005 13:38:26 -0400 Received: from zrtps0m6.us.nortel.com (zrtps0m6.us.nortel.com [47.140.192.58]) by zcars04f.nortelnetworks.com (Switch-2.2.6/Switch-2.2.0) with ESMTP id j3THOR911906 for ; Fri, 29 Apr 2005 13:24:28 -0400 (EDT) Received: from zcard305.ca.nortel.com (zcard305.ca.nortel.com [47.129.242.61]) by zrtps0m6.us.nortel.com (Switch-2.2.6/Switch-2.2.0) with ESMTP id j3THOBA03733 for ; Fri, 29 Apr 2005 13:24:11 -0400 (EDT) Received: by zcard305.ca.nortel.com with Internet Mail Service (5.5.2653.19) id ; Fri, 29 Apr 2005 13:24:11 -0400 Message-ID: <713043CE8B8E1348AF3C546DBE02C1B4033355F8@zcarhxm2.corp.nortel.com> From: "Sharon Chisholm" To: disman@ietf.org Subject: RE: [Disman] Alarm MIB implementations Date: Fri, 29 Apr 2005 13:24:07 -0400 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.2653.19) Content-Type: text/plain X-Spam-Score: 0.0 (/) X-Scan-Signature: a7d6aff76b15f3f56fcb94490e1052e4 X-BeenThere: disman@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Distributed Management List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: disman-bounces@ietf.org Errors-To: disman-bounces@ietf.org hi Not really. We did observe that probable cause may make more sense associated with the active alarm instance, but that was easily solvable via an extension. Sharon -----Original Message----- From: disman-bounces@ietf.org [mailto:disman-bounces@ietf.org] On Behalf Of Randy Presuhn Sent: Thursday, April 28, 2005 4:00 PM To: disman@ietf.org Subject: Re: [Disman] Alarm MIB implementations Hi - > From: "Sharon Chisholm" > To: > Sent: Wednesday, April 27, 2005 1:40 PM > Subject: RE: [Disman] Alarm MIB implementations ... > I know of two potential third party management applications > implementations, but I am not sure of their current status or if the > vendors have made this public so I don't want to name them explicitly. > Also based on the private email questions I get, a lot of people are > considering implementations, but I'm not sure if they are looking > device side or management application. > > Plus, of course the work within my own organization. ... Have any issues surfaced in the course of implementation where changes or clarifications to the specification would be helpful? Randy