From exim@www1.ietf.org Tue Jul 1 09:30:47 2003 Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA25825 for ; Tue, 1 Jul 2003 09:30:47 -0400 (EDT) Received: (from exim@localhost) by www1.ietf.org (8.11.6/8.11.6) id h61DUJh21227 for disman-archive@odin.ietf.org; Tue, 1 Jul 2003 09:30:19 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19XLD9-0005WE-Pv for disman-web-archive@optimus.ietf.org; Tue, 01 Jul 2003 09:30:19 -0400 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 JAA25740 for ; Tue, 1 Jul 2003 09:30:16 -0400 (EDT) Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19XLCf-0005En-Bc for disman-web-archive@ietf.org; Tue, 01 Jul 2003 09:29:49 -0400 Date: Tue, 01 Jul 2003 09:29:49 -0400 Message-ID: <20030701132949.18162.66335.Mailman@www1.ietf.org> Subject: ietf.org mailing list memberships reminder From: mailman-owner@www1.ietf.org To: disman-web-archive@ietf.org X-No-Archive: yes X-Ack: no Sender: sip-admin@ietf.org Errors-To: sip-admin@ietf.org X-BeenThere: sip@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk This is a reminder, sent out once a month, about your ietf.org mailing list memberships. It includes your subscription info and how to use it to change it or unsubscribe from a list. You can visit the URLs to change your membership status or configuration, including unsubscribing, setting digest-style delivery or disabling delivery altogether (e.g., for a vacation), and so on. In addition to the URL interfaces, you can also use email to make such changes. For more info, send a message to the '-request' address of the list (for example, disman-request@ietf.org) containing just the word 'help' in the message body, and an email message will be sent to you with instructions. If you have questions, problems, comments, etc, send them to mailman-owner@www1.ietf.org. Thanks! Passwords for disman-web-archive@ietf.org: List Password // URL ---- -------- disman@ietf.org carehu https://www1.ietf.org/mailman/options/disman/disman-web-archive%40ietf.org From sip-admin@ietf.org Tue Jul 1 09:35:50 2003 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 JAA26885 for ; Tue, 1 Jul 2003 09:35:50 -0400 (EDT) Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19XLI2-0007nq-7m for disman-archive@lists.ietf.org; Tue, 01 Jul 2003 09:35:22 -0400 Date: Tue, 01 Jul 2003 09:35:22 -0400 Message-ID: <20030701133522.18162.51034.Mailman@www1.ietf.org> Subject: ietf.org mailing list memberships reminder From: mailman-owner@www1.ietf.org To: disman-archive@ietf.org X-No-Archive: yes X-Ack: no Sender: sip-admin@ietf.org Errors-To: sip-admin@ietf.org X-BeenThere: sip@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk This is a reminder, sent out once a month, about your ietf.org mailing list memberships. It includes your subscription info and how to use it to change it or unsubscribe from a list. You can visit the URLs to change your membership status or configuration, including unsubscribing, setting digest-style delivery or disabling delivery altogether (e.g., for a vacation), and so on. In addition to the URL interfaces, you can also use email to make such changes. For more info, send a message to the '-request' address of the list (for example, disman-request@ietf.org) containing just the word 'help' in the message body, and an email message will be sent to you with instructions. If you have questions, problems, comments, etc, send them to mailman-owner@www1.ietf.org. Thanks! Passwords for disman-archive@lists.ietf.org: List Password // URL ---- -------- disman@ietf.org hixour https://www1.ietf.org/mailman/options/disman/disman-archive%40lists.ietf.org From mailman-admin@ietf.org Thu Jul 3 18:48:49 2003 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 SAA16792 for ; Thu, 3 Jul 2003 18:48:48 -0400 (EDT) Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19YCkU-0007UW-E1 for disman-archive@lists.ietf.org; Thu, 03 Jul 2003 18:40:18 -0400 Date: Thu, 03 Jul 2003 18:40:18 -0400 Message-ID: <20030703224018.4508.3548.Mailman@www1.ietf.org> Subject: ietf.org mailing list memberships reminder From: mailman-owner@www1.ietf.org To: disman-archive@ietf.org X-No-Archive: yes X-Ack: no Sender: mailman-admin@ietf.org Errors-To: mailman-admin@ietf.org X-BeenThere: mailman@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk There was an error in the last monthly reminder, in that the NOTE WELL statement (below) was not included. Therefore, the reminder is being sent out again. This is a reminder, sent out once a month, about your ietf.org mailing list memberships. It includes your subscription info and how to use it to change it or unsubscribe from a list. You can visit the URLs to change your membership status or configuration, including unsubscribing, setting digest-style delivery or disabling delivery altogether (e.g., for a vacation), and so on. In addition to the URL interfaces, you can also use email to make such changes. For more info, send a message to the '-request' address of the list (for example, disman-request@ietf.org) containing just the word 'help' in the message body, and an email message will be sent to you with instructions. *************************************************************************** Note Well All statements related to the activities of the IETF and addressed to the IETF are subject to all provisions of Section 10 of RFC 2026, which grants to the IETF and its participants certain licenses and rights in such statements. Such statements include verbal statements in IETF meetings, as well as written and electronic communications made at any time or place, which are addressed to * the IETF plenary session, * any IETF working group or portion thereof, * the IESG, or any member thereof on behalf of the IESG, * the IAB or any member thereof on behalf of the IAB, * any IETF mailing list, including the IETF list itself, any working group or design team list, or any other list functioning under IETF auspices, * the RFC Editor or the Internet-Drafts function Statements made outside of an IETF meeting, mailing list or other function, that are clearly not intended to be input to an IETF activity, group or function, are not subject to these provisions. *************************************************************************** If you have questions, problems, comments, etc, send them to mailman-owner@www1.ietf.org. Thanks! Passwords for disman-archive@lists.ietf.org: List Password // URL ---- -------- disman@ietf.org hixour https://www1.ietf.org/mailman/options/disman/disman-archive%40lists.ietf.org From exim@www1.ietf.org Thu Jul 3 19:46:51 2003 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 TAA26881 for ; Thu, 3 Jul 2003 19:46:50 -0400 (EDT) Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19YDmP-0002Y0-IF for disman-archive@odin.ietf.org; Thu, 03 Jul 2003 19:46:21 -0400 Received: (from exim@localhost) by www1.ietf.org (8.12.8/8.12.8/Submit) id h63NkLvL009782 for disman-archive@odin.ietf.org; Thu, 3 Jul 2003 19:46:21 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19YDkP-0002Bz-UH for disman-web-archive@optimus.ietf.org; Thu, 03 Jul 2003 19:44:17 -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 TAA23771 for ; Thu, 3 Jul 2003 19:25:27 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19YDEa-0002Uy-00 for disman-web-archive@ietf.org; Thu, 03 Jul 2003 19:11:24 -0400 Received: from ietf.org ([132.151.1.19] helo=optimus.ietf.org) by ietf-mx with esmtp (Exim 4.12) id 19YCrZ-0006xn-00 for disman-web-archive@ietf.org; Thu, 03 Jul 2003 18:47:37 -0400 Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19YCjL-0005eV-D8 for disman-web-archive@ietf.org; Thu, 03 Jul 2003 18:39:07 -0400 Date: Thu, 03 Jul 2003 18:39:07 -0400 Message-ID: <20030703223907.4508.38649.Mailman@www1.ietf.org> Subject: ietf.org mailing list memberships reminder From: mailman-owner@www1.ietf.org To: disman-web-archive@ietf.org X-No-Archive: yes X-Ack: no Sender: mailman-admin@ietf.org Errors-To: mailman-admin@ietf.org X-BeenThere: mailman@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk There was an error in the last monthly reminder, in that the NOTE WELL statement (below) was not included. Therefore, the reminder is being sent out again. This is a reminder, sent out once a month, about your ietf.org mailing list memberships. It includes your subscription info and how to use it to change it or unsubscribe from a list. You can visit the URLs to change your membership status or configuration, including unsubscribing, setting digest-style delivery or disabling delivery altogether (e.g., for a vacation), and so on. In addition to the URL interfaces, you can also use email to make such changes. For more info, send a message to the '-request' address of the list (for example, disman-request@ietf.org) containing just the word 'help' in the message body, and an email message will be sent to you with instructions. *************************************************************************** Note Well All statements related to the activities of the IETF and addressed to the IETF are subject to all provisions of Section 10 of RFC 2026, which grants to the IETF and its participants certain licenses and rights in such statements. Such statements include verbal statements in IETF meetings, as well as written and electronic communications made at any time or place, which are addressed to * the IETF plenary session, * any IETF working group or portion thereof, * the IESG, or any member thereof on behalf of the IESG, * the IAB or any member thereof on behalf of the IAB, * any IETF mailing list, including the IETF list itself, any working group or design team list, or any other list functioning under IETF auspices, * the RFC Editor or the Internet-Drafts function Statements made outside of an IETF meeting, mailing list or other function, that are clearly not intended to be input to an IETF activity, group or function, are not subject to these provisions. *************************************************************************** If you have questions, problems, comments, etc, send them to mailman-owner@www1.ietf.org. Thanks! Passwords for disman-web-archive@ietf.org: List Password // URL ---- -------- disman@ietf.org carehu https://www1.ietf.org/mailman/options/disman/disman-web-archive%40ietf.org From disman-admin@ietf.org Wed Jul 16 13:48:29 2003 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 NAA10096 for ; Wed, 16 Jul 2003 13:48:29 -0400 (EDT) Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19cqNk-0001PQ-TE; Wed, 16 Jul 2003 13:48:00 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19cqN6-0001M4-E1 for disman@optimus.ietf.org; Wed, 16 Jul 2003 13:47:20 -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 NAA10051 for ; Wed, 16 Jul 2003 13:47:16 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19cqN4-0001bh-00 for disman@ietf.org; Wed, 16 Jul 2003 13:47:18 -0400 Received: from auemail1.lucent.com ([192.11.223.161] helo=auemail1.firewall.lucent.com) by ietf-mx with esmtp (Exim 4.12) id 19cqMt-0001bQ-00 for disman@ietf.org; Wed, 16 Jul 2003 13:47:07 -0400 Received: from nj7460exch002h.wins.lucent.com (h135-17-42-35.lucent.com [135.17.42.35]) by auemail1.firewall.lucent.com (Switch-2.2.0/Switch-2.2.0) with ESMTP id h6GHkO513362 for ; Wed, 16 Jul 2003 12:46:24 -0500 (CDT) Received: by nj7460exch002h.ho.lucent.com with Internet Mail Service (5.5.2656.59) id <3CKRZS9P>; Wed, 16 Jul 2003 13:46:23 -0400 Message-ID: From: "Lam, Hing-Kam (Kam)" To: "Wijnen, Bert (Bert)" , "'a_n_huynh@yahoo.com'" , "'David Perkins'" , "Disman (E-mail) (E-mail)" MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.2656.59) Content-Type: text/plain; charset="iso-8859-1" Subject: [Disman] RE: AD review of: draft-ietf-disman-conditionmib-08.txt Sender: disman-admin@ietf.org Errors-To: disman-admin@ietf.org X-BeenThere: disman@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: Distributed Management List-Post: List-Help: List-Subscribe: , List-Archive: Date: Wed, 16 Jul 2003 13:46:20 -0400 Bert and all, Inline below are the proposed changes to the document in response to Bert's reveiw comments. If no objection to the changes, I will produce version -09 and upload it next week after the repository open again. Regards, Kam > -----Original Message----- > From: Wijnen, Bert (Bert) > Sent: Friday, June 06, 2003 9:32 AM > To: Lam, Hing-Kam (Kam); 'a_n_huynh@yahoo.com'; 'David Perkins' > Cc: Disman (E-mail) (E-mail) > Subject: AD review of: draft-ietf-disman-conditionmib-08.txt > > > Here is my review of rev 8. > > If you want, we can issue IETF Last Call, and then you may > consider these comments as IETF Last Call Comments, that you > better address rigth after such an IETF Last Call. > > More or less serious: > > - I see > IANAItuProbableCauseOrZero ::= TEXTUAL-CONVENTION > STATUS current > DESCRIPTION > "This TC can take any value of IANAItuProbableCause or 0. > IANAItuProbableCause is defined in the IANA-ITU-ALARM-TC > module in the Alarm MIB document (see RFC zzzz)." > REFERENCE > "RFC zzzz - Alarm MIB, Chisholm, S. and D. Romascanu, > mmm 2002." > -- RFC Ed.: replace zzzz with the RFC number of the Alarm > MIB document, > -- replace mmm with the actual month, and remove > this notice. > And so I wonder. That IANA mantained MIB module will be > extracted from > the document, and after that, the authoritative version will be at > the iana web site as follows: > http://www.iana.org/assignments/ianaitualarmtc-mib > Now putting a url into the REF clause is not good either, but maybe > something aka: > REFERENCE > "IANA-ITU-ALARM-TC MIB module as maintained at the > IANA web site. > The initial module was also published in RFC zzzz." > However, you do want to add that > http://www.iana.org/assignments/ianaitualarmtc-mib > in the normative references section, cause one must > understand it in > order to udnerstand your TC and how it is used. Replace REFERENCE "RFC zzzz - Alarm MIB, Chisholm, S. and D. Romascanu, mmm 2002." with REFERENCE "IANA-ITU-ALARM-TC MIB module as maintained at the IANA web site. The initial module was also published in RFC zzzz." Add [ITUALARMTC] http://www.iana.org/assignments/ianaitualarmtc-mib to the normative reference. Also add citation to the URL by replacing the last sentence of the 6th paragraph of section 4 by These probable causes (alarm conditions) have been included in the IANAItuProbableCause TC, which is defined in the IANA-ITU-ALARM-TC MIB module [RFCzzzz]. The IANA-ITU-ALARM-TC MIB module is maintained in the IANA web-site [ITUALARMTC]. > > - I believe that the arcEntry should include in its DESCRIPTION clause > some text about the fact that the indexing can cause OIDs of more > than 128 sub-IDs (which are not supported bu SNMPv1, > SNMPv2c or SNMPv3). > This is caused by OIDs for ResourceId syntax of arcIndex and for > arcNotificationId. So some text as to how people can/should avoid > an OID of more than 128 sub-IDs shoiuld be added. Add the following text to the DESCRIPTION clause of arcEntry Implementation need to be aware that if the total size of arcIndex and arcNotificationId exceeds 114 sub-IDs, then OIDs of column instances in this table will have more than 128 sub-IDs and cannot be access using SNMPv1, SNMPv2c, or snmpv3. > > - arcRowStatus OBJECT-TYPE > In the DESCRIPTION clause, pls describe if any objedcts in a row can > or cannot be updated while the row is in active state. Such > is required > as per RFC2579. Add the following text in the DESCRIPTION clause of arcRowStatus OBJECT-TYPE Only the objects arcState and arcNalmTimeRemaining can be updated when a row is active. > > Questions: > - I see > arcTITimeInterval OBJECT-TYPE > SYNTAX Gauge32 > and > arcCDTimeInterval OBJECT-TYPE > SYNTAX Gauge32 > is that a proper syntax for an interval ?? > there are a few more of these. Change the syntax of arcTITimeInterval, arcCDTimeInterval, and arcNalmTimeRemaining from Gauge32 to Unsigned32. In the IMPORTS clause, replace Gauge32 by Unsigned32. > > - I see two informative references (RFC1213 and RFC2863), but I do not > see any citations to it. So are they needed or useful? Remove RFC1213 and RFC2863 from the informative references. > > NITS: > > - Can you do real pagination? Will do. > > - I see " This document defines the SNMP objects..." > I think they are "MIB objects" rather than "SNMP objects" Will change. > > - I see " The ARC MIB defined in" a few times. > I think it is better to write "The ARC MIB module ....." Will change. > > - I see: > DESCRIPTION > "The MIB module describes the objects for > controlling a resource > in reporting alarm conditions that it detects. > > Copyright (C) The Internet Society (2003). This version > of this MIB module is part of RFC yyyy; see the RFC > itself for full legal notices." > -- RFC Ed.: replace yyyy with actual RFC number & remove this note > REVISION "200304160000Z" > DESCRIPTION > "Initial version, published as RFC xxxx." > -- RFC Ed.: replace xxxx with actual RFC number & remove this note > ::={ mib-2 yy } -- to be assigned by IANA > -- RFC Ed.: replace yy with IANA-assigned number & remove this note > It might be easier if you used xxxx instead of yyyy, After all, > these are both going to be the same RFC number, no? Will change. > > bert > From exim@www1.ietf.org Wed Jul 16 13:48:41 2003 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 NAA10118 for ; Wed, 16 Jul 2003 13:48:41 -0400 (EDT) Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19cqNz-0001RX-7I for disman-archive@odin.ietf.org; Wed, 16 Jul 2003 13:48:15 -0400 Received: (from exim@localhost) by www1.ietf.org (8.12.8/8.12.8/Submit) id h6GHmFAJ005543 for disman-archive@odin.ietf.org; Wed, 16 Jul 2003 13:48:15 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19cqNz-0001RK-3c for disman-web-archive@optimus.ietf.org; Wed, 16 Jul 2003 13:48:15 -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 NAA10077 for ; Wed, 16 Jul 2003 13:48:10 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19cqNw-0001cQ-00 for disman-web-archive@ietf.org; Wed, 16 Jul 2003 13:48:12 -0400 Received: from ietf.org ([132.151.1.19] helo=optimus.ietf.org) by ietf-mx with esmtp (Exim 4.12) id 19cqNr-0001cK-00 for disman-web-archive@ietf.org; Wed, 16 Jul 2003 13:48:07 -0400 Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19cqNk-0001PQ-TE; Wed, 16 Jul 2003 13:48:00 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19cqN6-0001M4-E1 for disman@optimus.ietf.org; Wed, 16 Jul 2003 13:47:20 -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 NAA10051 for ; Wed, 16 Jul 2003 13:47:16 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19cqN4-0001bh-00 for disman@ietf.org; Wed, 16 Jul 2003 13:47:18 -0400 Received: from auemail1.lucent.com ([192.11.223.161] helo=auemail1.firewall.lucent.com) by ietf-mx with esmtp (Exim 4.12) id 19cqMt-0001bQ-00 for disman@ietf.org; Wed, 16 Jul 2003 13:47:07 -0400 Received: from nj7460exch002h.wins.lucent.com (h135-17-42-35.lucent.com [135.17.42.35]) by auemail1.firewall.lucent.com (Switch-2.2.0/Switch-2.2.0) with ESMTP id h6GHkO513362 for ; Wed, 16 Jul 2003 12:46:24 -0500 (CDT) Received: by nj7460exch002h.ho.lucent.com with Internet Mail Service (5.5.2656.59) id <3CKRZS9P>; Wed, 16 Jul 2003 13:46:23 -0400 Message-ID: From: "Lam, Hing-Kam (Kam)" To: "Wijnen, Bert (Bert)" , "'a_n_huynh@yahoo.com'" , "'David Perkins'" , "Disman (E-mail) (E-mail)" MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.2656.59) Content-Type: text/plain; charset="iso-8859-1" Subject: [Disman] RE: AD review of: draft-ietf-disman-conditionmib-08.txt Sender: disman-admin@ietf.org Errors-To: disman-admin@ietf.org X-BeenThere: disman@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: Distributed Management List-Post: List-Help: List-Subscribe: , List-Archive: Date: Wed, 16 Jul 2003 13:46:20 -0400 Bert and all, Inline below are the proposed changes to the document in response to Bert's reveiw comments. If no objection to the changes, I will produce version -09 and upload it next week after the repository open again. Regards, Kam > -----Original Message----- > From: Wijnen, Bert (Bert) > Sent: Friday, June 06, 2003 9:32 AM > To: Lam, Hing-Kam (Kam); 'a_n_huynh@yahoo.com'; 'David Perkins' > Cc: Disman (E-mail) (E-mail) > Subject: AD review of: draft-ietf-disman-conditionmib-08.txt > > > Here is my review of rev 8. > > If you want, we can issue IETF Last Call, and then you may > consider these comments as IETF Last Call Comments, that you > better address rigth after such an IETF Last Call. > > More or less serious: > > - I see > IANAItuProbableCauseOrZero ::= TEXTUAL-CONVENTION > STATUS current > DESCRIPTION > "This TC can take any value of IANAItuProbableCause or 0. > IANAItuProbableCause is defined in the IANA-ITU-ALARM-TC > module in the Alarm MIB document (see RFC zzzz)." > REFERENCE > "RFC zzzz - Alarm MIB, Chisholm, S. and D. Romascanu, > mmm 2002." > -- RFC Ed.: replace zzzz with the RFC number of the Alarm > MIB document, > -- replace mmm with the actual month, and remove > this notice. > And so I wonder. That IANA mantained MIB module will be > extracted from > the document, and after that, the authoritative version will be at > the iana web site as follows: > http://www.iana.org/assignments/ianaitualarmtc-mib > Now putting a url into the REF clause is not good either, but maybe > something aka: > REFERENCE > "IANA-ITU-ALARM-TC MIB module as maintained at the > IANA web site. > The initial module was also published in RFC zzzz." > However, you do want to add that > http://www.iana.org/assignments/ianaitualarmtc-mib > in the normative references section, cause one must > understand it in > order to udnerstand your TC and how it is used. Replace REFERENCE "RFC zzzz - Alarm MIB, Chisholm, S. and D. Romascanu, mmm 2002." with REFERENCE "IANA-ITU-ALARM-TC MIB module as maintained at the IANA web site. The initial module was also published in RFC zzzz." Add [ITUALARMTC] http://www.iana.org/assignments/ianaitualarmtc-mib to the normative reference. Also add citation to the URL by replacing the last sentence of the 6th paragraph of section 4 by These probable causes (alarm conditions) have been included in the IANAItuProbableCause TC, which is defined in the IANA-ITU-ALARM-TC MIB module [RFCzzzz]. The IANA-ITU-ALARM-TC MIB module is maintained in the IANA web-site [ITUALARMTC]. > > - I believe that the arcEntry should include in its DESCRIPTION clause > some text about the fact that the indexing can cause OIDs of more > than 128 sub-IDs (which are not supported bu SNMPv1, > SNMPv2c or SNMPv3). > This is caused by OIDs for ResourceId syntax of arcIndex and for > arcNotificationId. So some text as to how people can/should avoid > an OID of more than 128 sub-IDs shoiuld be added. Add the following text to the DESCRIPTION clause of arcEntry Implementation need to be aware that if the total size of arcIndex and arcNotificationId exceeds 114 sub-IDs, then OIDs of column instances in this table will have more than 128 sub-IDs and cannot be access using SNMPv1, SNMPv2c, or snmpv3. > > - arcRowStatus OBJECT-TYPE > In the DESCRIPTION clause, pls describe if any objedcts in a row can > or cannot be updated while the row is in active state. Such > is required > as per RFC2579. Add the following text in the DESCRIPTION clause of arcRowStatus OBJECT-TYPE Only the objects arcState and arcNalmTimeRemaining can be updated when a row is active. > > Questions: > - I see > arcTITimeInterval OBJECT-TYPE > SYNTAX Gauge32 > and > arcCDTimeInterval OBJECT-TYPE > SYNTAX Gauge32 > is that a proper syntax for an interval ?? > there are a few more of these. Change the syntax of arcTITimeInterval, arcCDTimeInterval, and arcNalmTimeRemaining from Gauge32 to Unsigned32. In the IMPORTS clause, replace Gauge32 by Unsigned32. > > - I see two informative references (RFC1213 and RFC2863), but I do not > see any citations to it. So are they needed or useful? Remove RFC1213 and RFC2863 from the informative references. > > NITS: > > - Can you do real pagination? Will do. > > - I see " This document defines the SNMP objects..." > I think they are "MIB objects" rather than "SNMP objects" Will change. > > - I see " The ARC MIB defined in" a few times. > I think it is better to write "The ARC MIB module ....." Will change. > > - I see: > DESCRIPTION > "The MIB module describes the objects for > controlling a resource > in reporting alarm conditions that it detects. > > Copyright (C) The Internet Society (2003). This version > of this MIB module is part of RFC yyyy; see the RFC > itself for full legal notices." > -- RFC Ed.: replace yyyy with actual RFC number & remove this note > REVISION "200304160000Z" > DESCRIPTION > "Initial version, published as RFC xxxx." > -- RFC Ed.: replace xxxx with actual RFC number & remove this note > ::={ mib-2 yy } -- to be assigned by IANA > -- RFC Ed.: replace yy with IANA-assigned number & remove this note > It might be easier if you used xxxx instead of yyyy, After all, > these are both going to be the same RFC number, no? Will change. > > bert > From disman-admin@ietf.org Wed Jul 16 14:43:29 2003 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 OAA12053 for ; Wed, 16 Jul 2003 14:43:29 -0400 (EDT) Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19crEy-0005M8-Ox; Wed, 16 Jul 2003 14:43:00 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19crE2-0005HU-VU for disman@optimus.ietf.org; Wed, 16 Jul 2003 14:42:02 -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 OAA12007 for ; Wed, 16 Jul 2003 14:41:53 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19crDv-00023r-00 for disman@ietf.org; Wed, 16 Jul 2003 14:41:55 -0400 Received: from auemail1.lucent.com ([192.11.223.161] helo=auemail1.firewall.lucent.com) by ietf-mx with esmtp (Exim 4.12) id 19crDk-00023V-00 for disman@ietf.org; Wed, 16 Jul 2003 14:41:44 -0400 Received: from nl0006exch001h.wins.lucent.com (h135-85-76-62.lucent.com [135.85.76.62]) by auemail1.firewall.lucent.com (Switch-2.2.0/Switch-2.2.0) with ESMTP id h6GIeo513834 for ; Wed, 16 Jul 2003 13:40:51 -0500 (CDT) Received: by nl0006exch001h.nl.lucent.com with Internet Mail Service (5.5.2653.19) id ; Wed, 16 Jul 2003 20:40:49 +0200 Message-ID: <7D5D48D2CAA3D84C813F5B154F43B1550201796E@nl0006exch001u.nl.lucent.com> From: "Wijnen, Bert (Bert)" To: "Lam, Hing-Kam (Kam)" , "'a_n_huynh@yahoo.com'" , "'David Perkins'" , "'Disman (E-mail) (E-mail)'" MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.2653.19) Content-Type: text/plain; charset="iso-8859-1" Subject: [Disman] RE: AD review of: draft-ietf-disman-conditionmib-08.txt Sender: disman-admin@ietf.org Errors-To: disman-admin@ietf.org X-BeenThere: disman@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: Distributed Management List-Post: List-Help: List-Subscribe: , List-Archive: Date: Wed, 16 Jul 2003 20:40:47 +0200 Sound good, but w.r.t. > > > > - arcRowStatus OBJECT-TYPE > > In the DESCRIPTION clause, pls describe if any objedcts > in a row can > > or cannot be updated while the row is in active state. Such > > is required > > as per RFC2579. > > Add the following text in the DESCRIPTION clause of > arcRowStatus OBJECT-TYPE > Liteally it is incorect, cause I think that arcRowStatus itself can also be updated/changed, no? Bert From exim@www1.ietf.org Wed Jul 16 14:43:44 2003 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 OAA12072 for ; Wed, 16 Jul 2003 14:43:38 -0400 (EDT) Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19crFB-0005V4-3y for disman-archive@odin.ietf.org; Wed, 16 Jul 2003 14:43:13 -0400 Received: (from exim@localhost) by www1.ietf.org (8.12.8/8.12.8/Submit) id h6GIhDuL021136 for disman-archive@odin.ietf.org; Wed, 16 Jul 2003 14:43:13 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19crFA-0005On-Vw for disman-web-archive@optimus.ietf.org; Wed, 16 Jul 2003 14:43:13 -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 OAA12043 for ; Wed, 16 Jul 2003 14:43:05 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19crF5-00024K-00 for disman-web-archive@ietf.org; Wed, 16 Jul 2003 14:43:07 -0400 Received: from ietf.org ([132.151.1.19] helo=optimus.ietf.org) by ietf-mx with esmtp (Exim 4.12) id 19crEz-00024H-00 for disman-web-archive@ietf.org; Wed, 16 Jul 2003 14:43:01 -0400 Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19crEy-0005M8-Ox; Wed, 16 Jul 2003 14:43:00 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19crE2-0005HU-VU for disman@optimus.ietf.org; Wed, 16 Jul 2003 14:42:02 -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 OAA12007 for ; Wed, 16 Jul 2003 14:41:53 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19crDv-00023r-00 for disman@ietf.org; Wed, 16 Jul 2003 14:41:55 -0400 Received: from auemail1.lucent.com ([192.11.223.161] helo=auemail1.firewall.lucent.com) by ietf-mx with esmtp (Exim 4.12) id 19crDk-00023V-00 for disman@ietf.org; Wed, 16 Jul 2003 14:41:44 -0400 Received: from nl0006exch001h.wins.lucent.com (h135-85-76-62.lucent.com [135.85.76.62]) by auemail1.firewall.lucent.com (Switch-2.2.0/Switch-2.2.0) with ESMTP id h6GIeo513834 for ; Wed, 16 Jul 2003 13:40:51 -0500 (CDT) Received: by nl0006exch001h.nl.lucent.com with Internet Mail Service (5.5.2653.19) id ; Wed, 16 Jul 2003 20:40:49 +0200 Message-ID: <7D5D48D2CAA3D84C813F5B154F43B1550201796E@nl0006exch001u.nl.lucent.com> From: "Wijnen, Bert (Bert)" To: "Lam, Hing-Kam (Kam)" , "'a_n_huynh@yahoo.com'" , "'David Perkins'" , "'Disman (E-mail) (E-mail)'" MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.2653.19) Content-Type: text/plain; charset="iso-8859-1" Subject: [Disman] RE: AD review of: draft-ietf-disman-conditionmib-08.txt Sender: disman-admin@ietf.org Errors-To: disman-admin@ietf.org X-BeenThere: disman@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: Distributed Management List-Post: List-Help: List-Subscribe: , List-Archive: Date: Wed, 16 Jul 2003 20:40:47 +0200 Sound good, but w.r.t. > > > > - arcRowStatus OBJECT-TYPE > > In the DESCRIPTION clause, pls describe if any objedcts > in a row can > > or cannot be updated while the row is in active state. Such > > is required > > as per RFC2579. > > Add the following text in the DESCRIPTION clause of > arcRowStatus OBJECT-TYPE > Liteally it is incorect, cause I think that arcRowStatus itself can also be updated/changed, no? Bert From disman-admin@ietf.org Thu Jul 17 14:56:34 2003 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 OAA17681 for ; Thu, 17 Jul 2003 14:56:34 -0400 (EDT) Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19dDv7-0002gW-Qq; Thu, 17 Jul 2003 14:56:01 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19dDv5-0002fr-Av for disman@optimus.ietf.org; Thu, 17 Jul 2003 14:55:59 -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 OAA17665 for ; Thu, 17 Jul 2003 14:55:54 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19dDv2-0000hY-00 for disman@ietf.org; Thu, 17 Jul 2003 14:55:56 -0400 Received: from hoemail1.lucent.com ([192.11.226.161] helo=hoemail1.firewall.lucent.com) by ietf-mx with esmtp (Exim 4.12) id 19dDur-0000hN-00 for disman@ietf.org; Thu, 17 Jul 2003 14:55:45 -0400 Received: from nj7460exch001h.wins.lucent.com (h135-17-42-36.lucent.com [135.17.42.36]) by hoemail1.firewall.lucent.com (Switch-2.2.0/Switch-2.2.0) with ESMTP id h6HIsqA00438 for ; Thu, 17 Jul 2003 13:54:53 -0500 (CDT) Received: by nj7460exch001h.ho.lucent.com with Internet Mail Service (5.5.2656.59) id <3CJRS371>; Thu, 17 Jul 2003 14:54:51 -0400 Message-ID: From: "Lam, Hing-Kam (Kam)" To: "Wijnen, Bert (Bert)" , "'a_n_huynh@yahoo.com'" , "'David Perkins'" , "'Disman (E-mail) (E-mail)'" MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.2656.59) Content-Type: text/plain; charset="iso-8859-1" Subject: [Disman] RE: AD review of: draft-ietf-disman-conditionmib-08.txt Sender: disman-admin@ietf.org Errors-To: disman-admin@ietf.org X-BeenThere: disman@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: Distributed Management List-Post: List-Help: List-Subscribe: , List-Archive: Date: Thu, 17 Jul 2003 14:54:51 -0400 On Wed, 16 Jul 2003, Wijnen, Bert (Bert) wrote: > Liteally it is incorect, cause I think that arcRowStatus itself can > also be updated/changed, no? Yes, it is an oversight. The sentence will be: Only the objects arcState, arcNalmTimeRemaining, and arcRowStatus can be updated when a row is active. Regards, Kam From exim@www1.ietf.org Thu Jul 17 14:56:46 2003 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 OAA17700 for ; Thu, 17 Jul 2003 14:56:46 -0400 (EDT) Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19dDvQ-0002iD-Pd for disman-archive@odin.ietf.org; Thu, 17 Jul 2003 14:56:20 -0400 Received: (from exim@localhost) by www1.ietf.org (8.12.8/8.12.8/Submit) id h6HIuKFL010419 for disman-archive@odin.ietf.org; Thu, 17 Jul 2003 14:56:20 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19dDvQ-0002hy-Ll for disman-web-archive@optimus.ietf.org; Thu, 17 Jul 2003 14:56:20 -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 OAA17674 for ; Thu, 17 Jul 2003 14:56:15 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19dDvN-0000hg-00 for disman-web-archive@ietf.org; Thu, 17 Jul 2003 14:56:17 -0400 Received: from ietf.org ([132.151.1.19] helo=optimus.ietf.org) by ietf-mx with esmtp (Exim 4.12) id 19dDvI-0000hc-00 for disman-web-archive@ietf.org; Thu, 17 Jul 2003 14:56:12 -0400 Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19dDv7-0002gW-Qq; Thu, 17 Jul 2003 14:56:01 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19dDv5-0002fr-Av for disman@optimus.ietf.org; Thu, 17 Jul 2003 14:55:59 -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 OAA17665 for ; Thu, 17 Jul 2003 14:55:54 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19dDv2-0000hY-00 for disman@ietf.org; Thu, 17 Jul 2003 14:55:56 -0400 Received: from hoemail1.lucent.com ([192.11.226.161] helo=hoemail1.firewall.lucent.com) by ietf-mx with esmtp (Exim 4.12) id 19dDur-0000hN-00 for disman@ietf.org; Thu, 17 Jul 2003 14:55:45 -0400 Received: from nj7460exch001h.wins.lucent.com (h135-17-42-36.lucent.com [135.17.42.36]) by hoemail1.firewall.lucent.com (Switch-2.2.0/Switch-2.2.0) with ESMTP id h6HIsqA00438 for ; Thu, 17 Jul 2003 13:54:53 -0500 (CDT) Received: by nj7460exch001h.ho.lucent.com with Internet Mail Service (5.5.2656.59) id <3CJRS371>; Thu, 17 Jul 2003 14:54:51 -0400 Message-ID: From: "Lam, Hing-Kam (Kam)" To: "Wijnen, Bert (Bert)" , "'a_n_huynh@yahoo.com'" , "'David Perkins'" , "'Disman (E-mail) (E-mail)'" MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.2656.59) Content-Type: text/plain; charset="iso-8859-1" Subject: [Disman] RE: AD review of: draft-ietf-disman-conditionmib-08.txt Sender: disman-admin@ietf.org Errors-To: disman-admin@ietf.org X-BeenThere: disman@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: Distributed Management List-Post: List-Help: List-Subscribe: , List-Archive: Date: Thu, 17 Jul 2003 14:54:51 -0400 On Wed, 16 Jul 2003, Wijnen, Bert (Bert) wrote: > Liteally it is incorect, cause I think that arcRowStatus itself can > also be updated/changed, no? Yes, it is an oversight. The sentence will be: Only the objects arcState, arcNalmTimeRemaining, and arcRowStatus can be updated when a row is active. Regards, Kam From disman-admin@ietf.org Fri Jul 25 15:27:32 2003 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 PAA17636 for ; Fri, 25 Jul 2003 15:27:31 -0400 (EDT) Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19g8DU-0005aW-Ez; Fri, 25 Jul 2003 15:27:00 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19g8DH-0005ZW-8Y for disman@optimus.ietf.org; Fri, 25 Jul 2003 15:26:47 -0400 Received: from CNRI.Reston.VA.US (localhost [127.0.0.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA17437; Fri, 25 Jul 2003 15:26:42 -0400 (EDT) Message-Id: <200307251926.PAA17437@ietf.org> Mime-Version: 1.0 Content-Type: Multipart/Mixed; Boundary="NextPart" To: IETF-Announce: ; Cc: disman@ietf.org From: Internet-Drafts@ietf.org Reply-to: Internet-Drafts@ietf.org Subject: [Disman] I-D ACTION:draft-ietf-disman-conditionmib-09.txt Sender: disman-admin@ietf.org Errors-To: disman-admin@ietf.org X-BeenThere: disman@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: Distributed Management List-Post: List-Help: List-Subscribe: , List-Archive: Date: Fri, 25 Jul 2003 15:26:42 -0400 --NextPart A New Internet-Draft is available from the on-line Internet-Drafts directories. This draft is a work item of the Distributed Management Working Group of the IETF. Title : Alarm Reporting Control MIB Author(s) : K. Lam, A. Huynh, D. Perkins Filename : draft-ietf-disman-conditionmib-09.txt Pages : 16 Date : 2003-7-25 This memo defines a portion of the Management Information Base (MIB) for use with network management protocols in TCP/IP-based internets. In particular, it defines objects for controlling the reporting of alarm conditions. A URL for this Internet-Draft is: http://www.ietf.org/internet-drafts/draft-ietf-disman-conditionmib-09.txt To remove yourself from the IETF Announcement list, send a message to ietf-announce-request with the word unsubscribe in the body of the message. Internet-Drafts are also available by anonymous FTP. Login with the username "anonymous" and a password of your e-mail address. After logging in, type "cd internet-drafts" and then "get draft-ietf-disman-conditionmib-09.txt". A list of Internet-Drafts directories can be found in http://www.ietf.org/shadow.html or ftp://ftp.ietf.org/ietf/1shadow-sites.txt Internet-Drafts can also be obtained by e-mail. Send a message to: mailserv@ietf.org. In the body type: "FILE /internet-drafts/draft-ietf-disman-conditionmib-09.txt". NOTE: The mail server at ietf.org can return the document in MIME-encoded form by using the "mpack" utility. To use this feature, insert the command "ENCODING mime" before the "FILE" command. To decode the response(s), you will need "munpack" or a MIME-compliant mail reader. Different MIME-compliant mail readers exhibit different behavior, especially when dealing with "multipart" MIME messages (i.e. documents which have been split up into multiple messages), so check your local documentation on how to manipulate these messages. Below is the data which will enable a MIME compliant mail reader implementation to automatically retrieve the ASCII version of the Internet-Draft. --NextPart Content-Type: Multipart/Alternative; Boundary="OtherAccess" --OtherAccess Content-Type: Message/External-body; access-type="mail-server"; server="mailserv@ietf.org" Content-Type: text/plain Content-ID: <2003-7-25144541.I-D@ietf.org> ENCODING mime FILE /internet-drafts/draft-ietf-disman-conditionmib-09.txt --OtherAccess Content-Type: Message/External-body; name="draft-ietf-disman-conditionmib-09.txt"; site="ftp.ietf.org"; access-type="anon-ftp"; directory="internet-drafts" Content-Type: text/plain Content-ID: <2003-7-25144541.I-D@ietf.org> --OtherAccess-- --NextPart-- From exim@www1.ietf.org Fri Jul 25 15:27:33 2003 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 PAA17651 for ; Fri, 25 Jul 2003 15:27:33 -0400 (EDT) Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19g8Db-0005bE-9I for disman-archive@odin.ietf.org; Fri, 25 Jul 2003 15:27:07 -0400 Received: (from exim@localhost) by www1.ietf.org (8.12.8/8.12.8/Submit) id h6PJR7NN021520 for disman-archive@odin.ietf.org; Fri, 25 Jul 2003 15:27:07 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19g8Db-0005b1-5n for disman-web-archive@optimus.ietf.org; Fri, 25 Jul 2003 15:27:07 -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 PAA17516 for ; Fri, 25 Jul 2003 15:27:02 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19g8DZ-0002qw-00 for disman-web-archive@ietf.org; Fri, 25 Jul 2003 15:27:05 -0400 Received: from ietf.org ([132.151.1.19] helo=optimus.ietf.org) by ietf-mx with esmtp (Exim 4.12) id 19g8DZ-0002qr-00 for disman-web-archive@ietf.org; Fri, 25 Jul 2003 15:27:05 -0400 Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19g8DU-0005aW-Ez; Fri, 25 Jul 2003 15:27:00 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19g8DH-0005ZW-8Y for disman@optimus.ietf.org; Fri, 25 Jul 2003 15:26:47 -0400 Received: from CNRI.Reston.VA.US (localhost [127.0.0.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA17437; Fri, 25 Jul 2003 15:26:42 -0400 (EDT) Message-Id: <200307251926.PAA17437@ietf.org> Mime-Version: 1.0 Content-Type: Multipart/Mixed; Boundary="NextPart" To: IETF-Announce: ; Cc: disman@ietf.org From: Internet-Drafts@ietf.org Reply-to: Internet-Drafts@ietf.org Subject: [Disman] I-D ACTION:draft-ietf-disman-conditionmib-09.txt Sender: disman-admin@ietf.org Errors-To: disman-admin@ietf.org X-BeenThere: disman@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: Distributed Management List-Post: List-Help: List-Subscribe: , List-Archive: Date: Fri, 25 Jul 2003 15:26:42 -0400 --NextPart A New Internet-Draft is available from the on-line Internet-Drafts directories. This draft is a work item of the Distributed Management Working Group of the IETF. Title : Alarm Reporting Control MIB Author(s) : K. Lam, A. Huynh, D. Perkins Filename : draft-ietf-disman-conditionmib-09.txt Pages : 16 Date : 2003-7-25 This memo defines a portion of the Management Information Base (MIB) for use with network management protocols in TCP/IP-based internets. In particular, it defines objects for controlling the reporting of alarm conditions. A URL for this Internet-Draft is: http://www.ietf.org/internet-drafts/draft-ietf-disman-conditionmib-09.txt To remove yourself from the IETF Announcement list, send a message to ietf-announce-request with the word unsubscribe in the body of the message. Internet-Drafts are also available by anonymous FTP. Login with the username "anonymous" and a password of your e-mail address. After logging in, type "cd internet-drafts" and then "get draft-ietf-disman-conditionmib-09.txt". A list of Internet-Drafts directories can be found in http://www.ietf.org/shadow.html or ftp://ftp.ietf.org/ietf/1shadow-sites.txt Internet-Drafts can also be obtained by e-mail. Send a message to: mailserv@ietf.org. In the body type: "FILE /internet-drafts/draft-ietf-disman-conditionmib-09.txt". NOTE: The mail server at ietf.org can return the document in MIME-encoded form by using the "mpack" utility. To use this feature, insert the command "ENCODING mime" before the "FILE" command. To decode the response(s), you will need "munpack" or a MIME-compliant mail reader. Different MIME-compliant mail readers exhibit different behavior, especially when dealing with "multipart" MIME messages (i.e. documents which have been split up into multiple messages), so check your local documentation on how to manipulate these messages. Below is the data which will enable a MIME compliant mail reader implementation to automatically retrieve the ASCII version of the Internet-Draft. --NextPart Content-Type: Multipart/Alternative; Boundary="OtherAccess" --OtherAccess Content-Type: Message/External-body; access-type="mail-server"; server="mailserv@ietf.org" Content-Type: text/plain Content-ID: <2003-7-25144541.I-D@ietf.org> ENCODING mime FILE /internet-drafts/draft-ietf-disman-conditionmib-09.txt --OtherAccess Content-Type: Message/External-body; name="draft-ietf-disman-conditionmib-09.txt"; site="ftp.ietf.org"; access-type="anon-ftp"; directory="internet-drafts" Content-Type: text/plain Content-ID: <2003-7-25144541.I-D@ietf.org> --OtherAccess-- --NextPart--