From entmib-admin@ietf.org Mon Jan 5 16:46:30 2004 Received: from optimus.ietf.org ([132.151.1.19]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA06276 for ; Mon, 5 Jan 2004 16:46:30 -0500 (EST) Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AdcXy-0005yf-Ba; Mon, 05 Jan 2004 16:46:02 -0500 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AdcXW-0005wl-S7 for entmib@optimus.ietf.org; Mon, 05 Jan 2004 16:45:35 -0500 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA06230 for ; Mon, 5 Jan 2004 16:45:31 -0500 (EST) From: Margaret.Wasserman@nokia.com Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 1AdcXU-0000Vx-00 for entmib@ietf.org; Mon, 05 Jan 2004 16:45:32 -0500 Received: from exim by ietf-mx with spam-scanned (Exim 4.12) id 1AdcVx-0000OM-00 for entmib@ietf.org; Mon, 05 Jan 2004 16:43:57 -0500 Received: from mgw-x1.nokia.com ([131.228.20.21]) by ietf-mx with esmtp (Exim 4.12) id 1AdcTw-0000CX-00; Mon, 05 Jan 2004 16:41:52 -0500 Received: from esvir01nok.ntc.nokia.com (esvir01nokt.ntc.nokia.com [172.21.143.33]) by mgw-x1.nokia.com (Switch-2.2.8/Switch-2.2.8) with ESMTP id i05Lfp404529; Mon, 5 Jan 2004 23:41:51 +0200 (EET) Received: from daebh001.NOE.Nokia.com (unverified) by esvir01nok.ntc.nokia.com (Content Technologies SMTPRS 4.2.5) with ESMTP id ; Mon, 5 Jan 2004 23:41:51 +0200 Received: from bsebe001.NOE.Nokia.com ([172.19.160.13]) by daebh001.NOE.Nokia.com with Microsoft SMTPSVC(5.0.2195.6747); Mon, 5 Jan 2004 13:41:45 -0800 x-mimeole: Produced By Microsoft Exchange V6.0.6487.1 content-class: urn:content-classes:message MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Date: Mon, 5 Jan 2004 16:41:44 -0500 Message-ID: Thread-Topic: Change of Contact Information Thread-Index: AcPT1LY2BUVx6nTcQKeMNgg/MIiu8Q== To: , , X-OriginalArrivalTime: 05 Jan 2004 21:41:45.0410 (UTC) FILETIME=[B70CC220:01C3D3D4] X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on ietf-mx.ietf.org X-Spam-Status: No, hits=0.3 required=5.0 tests=AWL,NO_REAL_NAME autolearn=no version=2.60 Content-Transfer-Encoding: quoted-printable Subject: [Entmib] Change of Contact Information Sender: entmib-admin@ietf.org Errors-To: entmib-admin@ietf.org X-BeenThere: entmib@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: IETF Entity MIB WG List-Post: List-Help: List-Subscribe: , Content-Transfer-Encoding: quoted-printable [This note is cc:ed to many lists. Please be careful with replies. Thanks.] Hi All, I have decided to leave Nokia to join a small company called ThingMagic. My new contact information will be: Margaret Wasserman VP of Development ThingMagic One Broadway Cambridge, MA 02142 USA Work: +1 (617)758-4136 Cell: +1 (781)405-7464 margaret@thingmagic.com http:\\www.thingmagic.com In a vain attempt to control the IETF rumor mill: I have=20 enjoyed working at Nokia very much, and I believe that=20 Nokia is a great company that does excellent work within the IETF and elsewhere. An unexpected opportunity arose=20 to take a leadership role in a small, growing company,=20 and it was just too good to refuse. I plan to continue my=20 IETF activities, with the full support of my new company. My new e-mail address and cell phone number are already operational, so please change your pointers ASAP. My last=20 day at Nokia will be tomorrow (Tuesday, January 6th) and my Nokia e-mail address and cell phone number will probably=20 stop working around the end of the day tomorrow. Regards, Margaret _______________________________________________ Entmib mailing list Entmib@ietf.org https://www1.ietf.org/mailman/listinfo/entmib From exim@www1.ietf.org Mon Jan 5 16:46:31 2004 Received: from optimus.ietf.org ([132.151.1.19]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA06279 for ; Mon, 5 Jan 2004 16:46:31 -0500 (EST) Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AdcXz-0005zB-BK for entmib-archive@odin.ietf.org; Mon, 05 Jan 2004 16:46:03 -0500 Received: (from exim@localhost) by www1.ietf.org (8.12.8/8.12.8/Submit) id i05Lk3bs023005 for entmib-archive@odin.ietf.org; Mon, 5 Jan 2004 16:46:03 -0500 Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AdcXy-0005yf-Ba; Mon, 05 Jan 2004 16:46:02 -0500 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AdcXW-0005wl-S7 for entmib@optimus.ietf.org; Mon, 05 Jan 2004 16:45:35 -0500 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA06230 for ; Mon, 5 Jan 2004 16:45:31 -0500 (EST) From: Margaret.Wasserman@nokia.com Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 1AdcXU-0000Vx-00 for entmib@ietf.org; Mon, 05 Jan 2004 16:45:32 -0500 Received: from exim by ietf-mx with spam-scanned (Exim 4.12) id 1AdcVx-0000OM-00 for entmib@ietf.org; Mon, 05 Jan 2004 16:43:57 -0500 Received: from mgw-x1.nokia.com ([131.228.20.21]) by ietf-mx with esmtp (Exim 4.12) id 1AdcTw-0000CX-00; Mon, 05 Jan 2004 16:41:52 -0500 Received: from esvir01nok.ntc.nokia.com (esvir01nokt.ntc.nokia.com [172.21.143.33]) by mgw-x1.nokia.com (Switch-2.2.8/Switch-2.2.8) with ESMTP id i05Lfp404529; Mon, 5 Jan 2004 23:41:51 +0200 (EET) Received: from daebh001.NOE.Nokia.com (unverified) by esvir01nok.ntc.nokia.com (Content Technologies SMTPRS 4.2.5) with ESMTP id ; Mon, 5 Jan 2004 23:41:51 +0200 Received: from bsebe001.NOE.Nokia.com ([172.19.160.13]) by daebh001.NOE.Nokia.com with Microsoft SMTPSVC(5.0.2195.6747); Mon, 5 Jan 2004 13:41:45 -0800 x-mimeole: Produced By Microsoft Exchange V6.0.6487.1 content-class: urn:content-classes:message MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Date: Mon, 5 Jan 2004 16:41:44 -0500 Message-ID: Thread-Topic: Change of Contact Information Thread-Index: AcPT1LY2BUVx6nTcQKeMNgg/MIiu8Q== To: , , X-OriginalArrivalTime: 05 Jan 2004 21:41:45.0410 (UTC) FILETIME=[B70CC220:01C3D3D4] X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on ietf-mx.ietf.org X-Spam-Status: No, hits=0.3 required=5.0 tests=AWL,NO_REAL_NAME autolearn=no version=2.60 Content-Transfer-Encoding: quoted-printable Subject: [Entmib] Change of Contact Information Sender: entmib-admin@ietf.org Errors-To: entmib-admin@ietf.org X-BeenThere: entmib@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: IETF Entity MIB WG List-Post: List-Help: List-Subscribe: , Content-Transfer-Encoding: quoted-printable [This note is cc:ed to many lists. Please be careful with replies. Thanks.] Hi All, I have decided to leave Nokia to join a small company called ThingMagic. My new contact information will be: Margaret Wasserman VP of Development ThingMagic One Broadway Cambridge, MA 02142 USA Work: +1 (617)758-4136 Cell: +1 (781)405-7464 margaret@thingmagic.com http:\\www.thingmagic.com In a vain attempt to control the IETF rumor mill: I have=20 enjoyed working at Nokia very much, and I believe that=20 Nokia is a great company that does excellent work within the IETF and elsewhere. An unexpected opportunity arose=20 to take a leadership role in a small, growing company,=20 and it was just too good to refuse. I plan to continue my=20 IETF activities, with the full support of my new company. My new e-mail address and cell phone number are already operational, so please change your pointers ASAP. My last=20 day at Nokia will be tomorrow (Tuesday, January 6th) and my Nokia e-mail address and cell phone number will probably=20 stop working around the end of the day tomorrow. Regards, Margaret _______________________________________________ Entmib mailing list Entmib@ietf.org https://www1.ietf.org/mailman/listinfo/entmib From entmib-admin@ietf.org Tue Jan 6 08:40:35 2004 Received: from optimus.ietf.org ([132.151.1.19]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA17990 for ; Tue, 6 Jan 2004 08:40:34 -0500 (EST) Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AdrRF-0001NJ-CZ; Tue, 06 Jan 2004 08:40:05 -0500 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AdrQs-0001Lt-Ob for entmib@optimus.ietf.org; Tue, 06 Jan 2004 08:39:42 -0500 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA17967 for ; Tue, 6 Jan 2004 08:39:40 -0500 (EST) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 1AdrQr-000544-00 for entmib@ietf.org; Tue, 06 Jan 2004 08:39:41 -0500 Received: from exim by ietf-mx with spam-scanned (Exim 4.12) id 1AdrP1-00050Y-00 for entmib@ietf.org; Tue, 06 Jan 2004 08:37:48 -0500 Received: from zcars04f.nortelnetworks.com ([47.129.242.57]) by ietf-mx with esmtp (Exim 4.12) id 1AdrNQ-0004uL-00 for entmib@ietf.org; Tue, 06 Jan 2004 08:36:08 -0500 Received: from zcard309.ca.nortel.com (zcard309.ca.nortel.com [47.129.242.69]) by zcars04f.nortelnetworks.com (Switch-2.2.6/Switch-2.2.0) with ESMTP id i06DZa014230 for ; Tue, 6 Jan 2004 08:35:36 -0500 (EST) Received: by zcard309.ca.nortel.com with Internet Mail Service (5.5.2653.19) id ; Tue, 6 Jan 2004 08:35:36 -0500 Message-ID: <3549C09B853DD5119B540002A52CDD3409B94A34@zcard0ka.ca.nortel.com> From: "Sharon Chisholm" To: entmib@ietf.org Subject: RE: [Entmib] Entity State MIB Issue Status Date: Tue, 6 Jan 2004 08:35:28 -0500 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.2653.19) Content-Type: text/plain X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on ietf-mx.ietf.org X-Spam-Status: No, hits=0.0 required=5.0 tests=AWL autolearn=no version=2.60 Sender: entmib-admin@ietf.org Errors-To: entmib-admin@ietf.org X-BeenThere: entmib@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: IETF Entity MIB WG List-Post: List-Help: List-Subscribe: , Hi I submitted the update to this draft a couple of weeks ago, but my submission was corrupted somehow. I resubmitted shortly after but have not seen it yet. If it doesn't show up in the next couple days, I'll email it to the list. Having received no objections to the proposed resolutions, I have 'resolved' all the issues in http://rt.psg.com (ietf, ietf). So far I think I'm finding this tool useful, although it was annoying until I learned the trick that if a 'submit' was taking too long stop it and try again. Otherwise you end up with timeouts and you lose your form data and have to start again. Sharon -----Original Message----- From: Chisholm, Sharon [CAR:0S00:EXCH] Sent: Wednesday, December 17, 2003 9:10 AM To: entmib@ietf.org Subject: [Entmib] Entity State MIB Issue Status Hi The goal is to get the updated Entity State MIB out by the end of the week. As the proposed resolutions to the following entstate issues have received no objections, I will close them in rt.psg.com. 71, 72,73,74, 75, 76 and 78. Proposed resolutions for the following issues were only recently posted so these will remain open until Friday to allow more time to comment: 79, 80 and 244 The following issues are awaiting either proposed resolutions or updated proposed resolutions: 77 and 243 Sharon Chisholm Portfolio Integration Nortel Networks Ottawa, Canada _______________________________________________ Entmib mailing list Entmib@ietf.org https://www1.ietf.org/mailman/listinfo/entmib _______________________________________________ Entmib mailing list Entmib@ietf.org https://www1.ietf.org/mailman/listinfo/entmib From exim@www1.ietf.org Tue Jan 6 08:40:35 2004 Received: from optimus.ietf.org ([132.151.1.19]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA17998 for ; Tue, 6 Jan 2004 08:40:35 -0500 (EST) Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AdrRH-0001Nz-08 for entmib-archive@odin.ietf.org; Tue, 06 Jan 2004 08:40:07 -0500 Received: (from exim@localhost) by www1.ietf.org (8.12.8/8.12.8/Submit) id i06De6Li005314 for entmib-archive@odin.ietf.org; Tue, 6 Jan 2004 08:40:06 -0500 Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AdrRF-0001NJ-CZ; Tue, 06 Jan 2004 08:40:05 -0500 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AdrQs-0001Lt-Ob for entmib@optimus.ietf.org; Tue, 06 Jan 2004 08:39:42 -0500 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA17967 for ; Tue, 6 Jan 2004 08:39:40 -0500 (EST) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 1AdrQr-000544-00 for entmib@ietf.org; Tue, 06 Jan 2004 08:39:41 -0500 Received: from exim by ietf-mx with spam-scanned (Exim 4.12) id 1AdrP1-00050Y-00 for entmib@ietf.org; Tue, 06 Jan 2004 08:37:48 -0500 Received: from zcars04f.nortelnetworks.com ([47.129.242.57]) by ietf-mx with esmtp (Exim 4.12) id 1AdrNQ-0004uL-00 for entmib@ietf.org; Tue, 06 Jan 2004 08:36:08 -0500 Received: from zcard309.ca.nortel.com (zcard309.ca.nortel.com [47.129.242.69]) by zcars04f.nortelnetworks.com (Switch-2.2.6/Switch-2.2.0) with ESMTP id i06DZa014230 for ; Tue, 6 Jan 2004 08:35:36 -0500 (EST) Received: by zcard309.ca.nortel.com with Internet Mail Service (5.5.2653.19) id ; Tue, 6 Jan 2004 08:35:36 -0500 Message-ID: <3549C09B853DD5119B540002A52CDD3409B94A34@zcard0ka.ca.nortel.com> From: "Sharon Chisholm" To: entmib@ietf.org Subject: RE: [Entmib] Entity State MIB Issue Status Date: Tue, 6 Jan 2004 08:35:28 -0500 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.2653.19) Content-Type: text/plain X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on ietf-mx.ietf.org X-Spam-Status: No, hits=0.0 required=5.0 tests=AWL autolearn=no version=2.60 Sender: entmib-admin@ietf.org Errors-To: entmib-admin@ietf.org X-BeenThere: entmib@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: IETF Entity MIB WG List-Post: List-Help: List-Subscribe: , Hi I submitted the update to this draft a couple of weeks ago, but my submission was corrupted somehow. I resubmitted shortly after but have not seen it yet. If it doesn't show up in the next couple days, I'll email it to the list. Having received no objections to the proposed resolutions, I have 'resolved' all the issues in http://rt.psg.com (ietf, ietf). So far I think I'm finding this tool useful, although it was annoying until I learned the trick that if a 'submit' was taking too long stop it and try again. Otherwise you end up with timeouts and you lose your form data and have to start again. Sharon -----Original Message----- From: Chisholm, Sharon [CAR:0S00:EXCH] Sent: Wednesday, December 17, 2003 9:10 AM To: entmib@ietf.org Subject: [Entmib] Entity State MIB Issue Status Hi The goal is to get the updated Entity State MIB out by the end of the week. As the proposed resolutions to the following entstate issues have received no objections, I will close them in rt.psg.com. 71, 72,73,74, 75, 76 and 78. Proposed resolutions for the following issues were only recently posted so these will remain open until Friday to allow more time to comment: 79, 80 and 244 The following issues are awaiting either proposed resolutions or updated proposed resolutions: 77 and 243 Sharon Chisholm Portfolio Integration Nortel Networks Ottawa, Canada _______________________________________________ Entmib mailing list Entmib@ietf.org https://www1.ietf.org/mailman/listinfo/entmib _______________________________________________ Entmib mailing list Entmib@ietf.org https://www1.ietf.org/mailman/listinfo/entmib From entmib-admin@ietf.org Thu Jan 8 10:34:28 2004 Received: from optimus.ietf.org ([132.151.1.19]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA28078 for ; Thu, 8 Jan 2004 10:34:28 -0500 (EST) Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AecAa-0005U7-FD; Thu, 08 Jan 2004 10:34:00 -0500 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1Aec9o-0005TK-TV for entmib@optimus.ietf.org; Thu, 08 Jan 2004 10:33:12 -0500 Received: from CNRI.Reston.VA.US (localhost [127.0.0.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA27936; Thu, 8 Jan 2004 10:33:07 -0500 (EST) Message-Id: <200401081533.KAA27936@ietf.org> Mime-Version: 1.0 Content-Type: Multipart/Mixed; Boundary="NextPart" To: IETF-Announce: ; Cc: entmib@ietf.org From: Internet-Drafts@ietf.org Reply-to: Internet-Drafts@ietf.org Date: Thu, 08 Jan 2004 10:33:07 -0500 Subject: [Entmib] I-D ACTION:draft-ietf-entmib-state-02.txt Sender: entmib-admin@ietf.org Errors-To: entmib-admin@ietf.org X-BeenThere: entmib@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: IETF Entity MIB WG List-Post: List-Help: List-Subscribe: , --NextPart A New Internet-Draft is available from the on-line Internet-Drafts directories. This draft is a work item of the Entity MIB Working Group of the IETF. Title : Entity State MIB Author(s) : S. Chisholm, D. Perkins Filename : draft-ietf-entmib-state-02.txt Pages : 17 Date : 2004-1-7 This memo defines a portion of the Management Information Base (MIB) for use with network management protocols in the Internet community. In particular, it describes extensions to the entity MIB to provide information about the state of the entity. A URL for this Internet-Draft is: http://www.ietf.org/internet-drafts/draft-ietf-entmib-state-02.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-entmib-state-02.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-entmib-state-02.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: <2004-1-7161112.I-D@ietf.org> ENCODING mime FILE /internet-drafts/draft-ietf-entmib-state-02.txt --OtherAccess Content-Type: Message/External-body; name="draft-ietf-entmib-state-02.txt"; site="ftp.ietf.org"; access-type="anon-ftp"; directory="internet-drafts" Content-Type: text/plain Content-ID: <2004-1-7161112.I-D@ietf.org> --OtherAccess-- --NextPart-- _______________________________________________ Entmib mailing list Entmib@ietf.org https://www1.ietf.org/mailman/listinfo/entmib From exim@www1.ietf.org Thu Jan 8 11:20:44 2004 Received: from optimus.ietf.org ([132.151.1.19]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA28080 for ; Thu, 8 Jan 2004 10:34:28 -0500 (EST) Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AecAb-0005Ue-Jr for entmib-archive@odin.ietf.org; Thu, 08 Jan 2004 10:34:01 -0500 Received: (from exim@localhost) by www1.ietf.org (8.12.8/8.12.8/Submit) id i08FY1K1021097 for entmib-archive@odin.ietf.org; Thu, 8 Jan 2004 10:34:01 -0500 Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AecAa-0005U7-FD; Thu, 08 Jan 2004 10:34:00 -0500 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1Aec9o-0005TK-TV for entmib@optimus.ietf.org; Thu, 08 Jan 2004 10:33:12 -0500 Received: from CNRI.Reston.VA.US (localhost [127.0.0.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA27936; Thu, 8 Jan 2004 10:33:07 -0500 (EST) Message-Id: <200401081533.KAA27936@ietf.org> Mime-Version: 1.0 Content-Type: Multipart/Mixed; Boundary="NextPart" To: IETF-Announce: ; Cc: entmib@ietf.org From: Internet-Drafts@ietf.org Reply-to: Internet-Drafts@ietf.org Date: Thu, 08 Jan 2004 10:33:07 -0500 Subject: [Entmib] I-D ACTION:draft-ietf-entmib-state-02.txt Sender: entmib-admin@ietf.org Errors-To: entmib-admin@ietf.org X-BeenThere: entmib@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: IETF Entity MIB WG List-Post: List-Help: List-Subscribe: , --NextPart A New Internet-Draft is available from the on-line Internet-Drafts directories. This draft is a work item of the Entity MIB Working Group of the IETF. Title : Entity State MIB Author(s) : S. Chisholm, D. Perkins Filename : draft-ietf-entmib-state-02.txt Pages : 17 Date : 2004-1-7 This memo defines a portion of the Management Information Base (MIB) for use with network management protocols in the Internet community. In particular, it describes extensions to the entity MIB to provide information about the state of the entity. A URL for this Internet-Draft is: http://www.ietf.org/internet-drafts/draft-ietf-entmib-state-02.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-entmib-state-02.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-entmib-state-02.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: <2004-1-7161112.I-D@ietf.org> ENCODING mime FILE /internet-drafts/draft-ietf-entmib-state-02.txt --OtherAccess Content-Type: Message/External-body; name="draft-ietf-entmib-state-02.txt"; site="ftp.ietf.org"; access-type="anon-ftp"; directory="internet-drafts" Content-Type: text/plain Content-ID: <2004-1-7161112.I-D@ietf.org> --OtherAccess-- --NextPart-- _______________________________________________ Entmib mailing list Entmib@ietf.org https://www1.ietf.org/mailman/listinfo/entmib From entmib-admin@ietf.org Fri Jan 9 08:32:31 2004 Received: from optimus.ietf.org ([132.151.1.19]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA29258 for ; Fri, 9 Jan 2004 08:32:31 -0500 (EST) Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1Aewk6-000626-QX; Fri, 09 Jan 2004 08:32:02 -0500 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AewjV-0005yd-Gm for entmib@optimus.ietf.org; Fri, 09 Jan 2004 08:31:25 -0500 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA29246 for ; Fri, 9 Jan 2004 08:31:23 -0500 (EST) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 1AewjU-0000Ve-00 for entmib@ietf.org; Fri, 09 Jan 2004 08:31:24 -0500 Received: from exim by ietf-mx with spam-scanned (Exim 4.12) id 1AewiG-0000L9-00 for entmib@ietf.org; Fri, 09 Jan 2004 08:30:08 -0500 Received: from smtp.exodus.net ([66.35.230.236]) by ietf-mx with esmtp (Exim 4.12) id 1AewgP-0007gb-00 for entmib@ietf.org; Fri, 09 Jan 2004 08:28:13 -0500 Received: from ms101.mail1.com (ms101.mail1.com [209.1.5.174]) by smtp.exodus.net (8.12.8/8.12.8) with ESMTP id i09F7aw3032089 for ; Fri, 9 Jan 2004 07:07:36 -0800 Received: from ala-mrwtemp.thingmagic.com (unverified [24.61.30.237]) by accounting.espmail.com (Rockliffe SMTPRA 5.2.5) with ESMTP id for ; Fri, 9 Jan 2004 05:27:42 -0800 Message-Id: <5.1.0.14.2.20040109082204.04499668@ms101.mail1.com> X-Sender: margaret@thingmagic.com@ms101.mail1.com X-Mailer: QUALCOMM Windows Eudora Version 5.1 Date: Fri, 09 Jan 2004 08:25:57 -0500 To: entmib@ietf.org From: Margaret Wasserman In-Reply-To: <200401081533.KAA27936@ietf.org> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii"; format=flowed X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on ietf-mx.ietf.org X-Spam-Status: No, hits=0.0 required=5.0 tests=AWL autolearn=no version=2.60 Subject: [Entmib] Entity State MIB Next Steps Sender: entmib-admin@ietf.org Errors-To: entmib-admin@ietf.org X-BeenThere: entmib@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: IETF Entity MIB WG List-Post: List-Help: List-Subscribe: , Now that the newest version of the Entity State MIB is available, the WG has a decision to make. In my opinion, we have two choices: (1) We decide that the structure and objects defined in the current draft are acceptable, and we send the current draft to WG Last Call in order to identify and resolve final issues. (2) We decide that we want to change the structure or objects defined in this MIB to make it simpler or more functional. I would appreciate it if people would respond to this message with their opinions, so that I can attempt to judge the consensus of the WG on this issue. Thanks, Margaret _______________________________________________ Entmib mailing list Entmib@ietf.org https://www1.ietf.org/mailman/listinfo/entmib From exim@www1.ietf.org Fri Jan 9 08:32:32 2004 Received: from optimus.ietf.org ([132.151.1.19]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA29259 for ; Fri, 9 Jan 2004 08:32:31 -0500 (EST) Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1Aewk7-00062Z-5S for entmib-archive@odin.ietf.org; Fri, 09 Jan 2004 08:32:03 -0500 Received: (from exim@localhost) by www1.ietf.org (8.12.8/8.12.8/Submit) id i09DW3RO023202 for entmib-archive@odin.ietf.org; Fri, 9 Jan 2004 08:32:03 -0500 Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1Aewk6-000626-QX; Fri, 09 Jan 2004 08:32:02 -0500 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AewjV-0005yd-Gm for entmib@optimus.ietf.org; Fri, 09 Jan 2004 08:31:25 -0500 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA29246 for ; Fri, 9 Jan 2004 08:31:23 -0500 (EST) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 1AewjU-0000Ve-00 for entmib@ietf.org; Fri, 09 Jan 2004 08:31:24 -0500 Received: from exim by ietf-mx with spam-scanned (Exim 4.12) id 1AewiG-0000L9-00 for entmib@ietf.org; Fri, 09 Jan 2004 08:30:08 -0500 Received: from smtp.exodus.net ([66.35.230.236]) by ietf-mx with esmtp (Exim 4.12) id 1AewgP-0007gb-00 for entmib@ietf.org; Fri, 09 Jan 2004 08:28:13 -0500 Received: from ms101.mail1.com (ms101.mail1.com [209.1.5.174]) by smtp.exodus.net (8.12.8/8.12.8) with ESMTP id i09F7aw3032089 for ; Fri, 9 Jan 2004 07:07:36 -0800 Received: from ala-mrwtemp.thingmagic.com (unverified [24.61.30.237]) by accounting.espmail.com (Rockliffe SMTPRA 5.2.5) with ESMTP id for ; Fri, 9 Jan 2004 05:27:42 -0800 Message-Id: <5.1.0.14.2.20040109082204.04499668@ms101.mail1.com> X-Sender: margaret@thingmagic.com@ms101.mail1.com X-Mailer: QUALCOMM Windows Eudora Version 5.1 Date: Fri, 09 Jan 2004 08:25:57 -0500 To: entmib@ietf.org From: Margaret Wasserman In-Reply-To: <200401081533.KAA27936@ietf.org> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii"; format=flowed X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on ietf-mx.ietf.org X-Spam-Status: No, hits=0.0 required=5.0 tests=AWL autolearn=no version=2.60 Subject: [Entmib] Entity State MIB Next Steps Sender: entmib-admin@ietf.org Errors-To: entmib-admin@ietf.org X-BeenThere: entmib@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: IETF Entity MIB WG List-Post: List-Help: List-Subscribe: , Now that the newest version of the Entity State MIB is available, the WG has a decision to make. In my opinion, we have two choices: (1) We decide that the structure and objects defined in the current draft are acceptable, and we send the current draft to WG Last Call in order to identify and resolve final issues. (2) We decide that we want to change the structure or objects defined in this MIB to make it simpler or more functional. I would appreciate it if people would respond to this message with their opinions, so that I can attempt to judge the consensus of the WG on this issue. Thanks, Margaret _______________________________________________ Entmib mailing list Entmib@ietf.org https://www1.ietf.org/mailman/listinfo/entmib From entmib-admin@ietf.org Fri Jan 9 08:54:29 2004 Received: from optimus.ietf.org ([132.151.1.19]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA00771 for ; Fri, 9 Jan 2004 08:54:29 -0500 (EST) Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1Aex5N-00078H-7P; Fri, 09 Jan 2004 08:54:01 -0500 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1Aex4S-0006z6-RR for entmib@optimus.ietf.org; Fri, 09 Jan 2004 08:53:04 -0500 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA00745 for ; Fri, 9 Jan 2004 08:53:02 -0500 (EST) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 1Aex4Q-0002Od-00 for entmib@ietf.org; Fri, 09 Jan 2004 08:53:03 -0500 Received: from exim by ietf-mx with spam-scanned (Exim 4.12) id 1Aex3A-0002GN-00 for entmib@ietf.org; Fri, 09 Jan 2004 08:51:44 -0500 Received: from zcars04f.nortelnetworks.com ([47.129.242.57]) by ietf-mx with esmtp (Exim 4.12) id 1Aex0x-0001a8-00 for entmib@ietf.org; Fri, 09 Jan 2004 08:49:27 -0500 Received: from zcard309.ca.nortel.com (zcard309.ca.nortel.com [47.129.242.69]) by zcars04f.nortelnetworks.com (Switch-2.2.6/Switch-2.2.0) with ESMTP id i09Dmst06849 for ; Fri, 9 Jan 2004 08:48:54 -0500 (EST) Received: by zcard309.ca.nortel.com with Internet Mail Service (5.5.2653.19) id ; Fri, 9 Jan 2004 08:48:54 -0500 Message-ID: <3549C09B853DD5119B540002A52CDD3409BFEC5B@zcard0ka.ca.nortel.com> From: "Sharon Chisholm" To: entmib@ietf.org Subject: RE: [Entmib] Entity State MIB Next Steps Date: Fri, 9 Jan 2004 08:48:51 -0500 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.2653.19) Content-Type: text/plain X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on ietf-mx.ietf.org X-Spam-Status: No, hits=0.1 required=5.0 tests=AWL autolearn=no version=2.60 Sender: entmib-admin@ietf.org Errors-To: entmib-admin@ietf.org X-BeenThere: entmib@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: IETF Entity MIB WG List-Post: List-Help: List-Subscribe: , Hi My vote is for 1), except if the current update resolves issues from the previous working group last call do we need a second? There was substantial rewrite, but no objects were changed. I could go either way. I'm hoping that the more concise text in the latest version appeases the concern that what the working group has come up with is too complicated. Sharon -----Original Message----- From: Margaret Wasserman [mailto:margaret@thingmagic.com] Sent: Friday, January 09, 2004 8:26 AM To: entmib@ietf.org Subject: [Entmib] Entity State MIB Next Steps Now that the newest version of the Entity State MIB is available, the WG has a decision to make. In my opinion, we have two choices: (1) We decide that the structure and objects defined in the current draft are acceptable, and we send the current draft to WG Last Call in order to identify and resolve final issues. (2) We decide that we want to change the structure or objects defined in this MIB to make it simpler or more functional. I would appreciate it if people would respond to this message with their opinions, so that I can attempt to judge the consensus of the WG on this issue. Thanks, Margaret _______________________________________________ Entmib mailing list Entmib@ietf.org https://www1.ietf.org/mailman/listinfo/entmib _______________________________________________ Entmib mailing list Entmib@ietf.org https://www1.ietf.org/mailman/listinfo/entmib From exim@www1.ietf.org Fri Jan 9 08:54:30 2004 Received: from optimus.ietf.org ([132.151.1.19]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA00775 for ; Fri, 9 Jan 2004 08:54:30 -0500 (EST) Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1Aex5N-00078o-IF for entmib-archive@odin.ietf.org; Fri, 09 Jan 2004 08:54:01 -0500 Received: (from exim@localhost) by www1.ietf.org (8.12.8/8.12.8/Submit) id i09Ds1lD027433 for entmib-archive@odin.ietf.org; Fri, 9 Jan 2004 08:54:01 -0500 Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1Aex5N-00078H-7P; Fri, 09 Jan 2004 08:54:01 -0500 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1Aex4S-0006z6-RR for entmib@optimus.ietf.org; Fri, 09 Jan 2004 08:53:04 -0500 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA00745 for ; Fri, 9 Jan 2004 08:53:02 -0500 (EST) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 1Aex4Q-0002Od-00 for entmib@ietf.org; Fri, 09 Jan 2004 08:53:03 -0500 Received: from exim by ietf-mx with spam-scanned (Exim 4.12) id 1Aex3A-0002GN-00 for entmib@ietf.org; Fri, 09 Jan 2004 08:51:44 -0500 Received: from zcars04f.nortelnetworks.com ([47.129.242.57]) by ietf-mx with esmtp (Exim 4.12) id 1Aex0x-0001a8-00 for entmib@ietf.org; Fri, 09 Jan 2004 08:49:27 -0500 Received: from zcard309.ca.nortel.com (zcard309.ca.nortel.com [47.129.242.69]) by zcars04f.nortelnetworks.com (Switch-2.2.6/Switch-2.2.0) with ESMTP id i09Dmst06849 for ; Fri, 9 Jan 2004 08:48:54 -0500 (EST) Received: by zcard309.ca.nortel.com with Internet Mail Service (5.5.2653.19) id ; Fri, 9 Jan 2004 08:48:54 -0500 Message-ID: <3549C09B853DD5119B540002A52CDD3409BFEC5B@zcard0ka.ca.nortel.com> From: "Sharon Chisholm" To: entmib@ietf.org Subject: RE: [Entmib] Entity State MIB Next Steps Date: Fri, 9 Jan 2004 08:48:51 -0500 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.2653.19) Content-Type: text/plain X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on ietf-mx.ietf.org X-Spam-Status: No, hits=0.1 required=5.0 tests=AWL autolearn=no version=2.60 Sender: entmib-admin@ietf.org Errors-To: entmib-admin@ietf.org X-BeenThere: entmib@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: IETF Entity MIB WG List-Post: List-Help: List-Subscribe: , Hi My vote is for 1), except if the current update resolves issues from the previous working group last call do we need a second? There was substantial rewrite, but no objects were changed. I could go either way. I'm hoping that the more concise text in the latest version appeases the concern that what the working group has come up with is too complicated. Sharon -----Original Message----- From: Margaret Wasserman [mailto:margaret@thingmagic.com] Sent: Friday, January 09, 2004 8:26 AM To: entmib@ietf.org Subject: [Entmib] Entity State MIB Next Steps Now that the newest version of the Entity State MIB is available, the WG has a decision to make. In my opinion, we have two choices: (1) We decide that the structure and objects defined in the current draft are acceptable, and we send the current draft to WG Last Call in order to identify and resolve final issues. (2) We decide that we want to change the structure or objects defined in this MIB to make it simpler or more functional. I would appreciate it if people would respond to this message with their opinions, so that I can attempt to judge the consensus of the WG on this issue. Thanks, Margaret _______________________________________________ Entmib mailing list Entmib@ietf.org https://www1.ietf.org/mailman/listinfo/entmib _______________________________________________ Entmib mailing list Entmib@ietf.org https://www1.ietf.org/mailman/listinfo/entmib From mailman-admin@ietf.org Fri Jan 9 13:02:03 2004 Received: from optimus.ietf.org ([132.151.1.19]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA18986 for ; Fri, 9 Jan 2004 13:02:03 -0500 (EST) Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1Af0wy-0003eN-7X for entmib-archive@lists.ietf.org; Fri, 09 Jan 2004 13:01:36 -0500 Date: Fri, 09 Jan 2004 13:01:36 -0500 Message-ID: <20040109180136.9164.36492.Mailman@www1.ietf.org> Subject: ietf.org mailing list memberships reminder From: mailman-owner@www1.ietf.org To: entmib-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 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, entmib-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 entmib-archive@lists.ietf.org: List Password // URL ---- -------- entmib@ietf.org CNIo https://www1.ietf.org/mailman/options/entmib/entmib-archive%40lists.ietf.org From entmib-admin@ietf.org Sun Jan 11 09:52:29 2004 Received: from optimus.ietf.org ([132.151.1.19]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA29817 for ; Sun, 11 Jan 2004 09:52:29 -0500 (EST) Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1Afgwb-0003bl-0l; Sun, 11 Jan 2004 09:52:01 -0500 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1Afgw3-0003bY-TX for entmib@optimus.ietf.org; Sun, 11 Jan 2004 09:51:27 -0500 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA29699 for ; Sun, 11 Jan 2004 09:51:20 -0500 (EST) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 1Afgvr-0007NS-00 for entmib@ietf.org; Sun, 11 Jan 2004 09:51:16 -0500 Received: from exim by ietf-mx with spam-scanned (Exim 4.12) id 1Afgre-0007Be-00 for entmib@ietf.org; Sun, 11 Jan 2004 09:46:54 -0500 Received: from smtp.exodus.net ([66.35.230.236]) by ietf-mx with esmtp (Exim 4.12) id 1Afglw-0006za-00 for entmib@ietf.org; Sun, 11 Jan 2004 09:41:00 -0500 Received: from ms101.mail1.com (ms101.mail1.com [209.1.5.174]) by smtp.exodus.net (8.12.8/8.12.8) with ESMTP id i0BGJqw3014115 for ; Sun, 11 Jan 2004 08:19:54 -0800 Received: from ala-mrwtemp.thingmagic.com (unverified [24.61.30.237]) by accounting.espmail.com (Rockliffe SMTPRA 5.2.5) with ESMTP id for ; Sun, 11 Jan 2004 06:40:02 -0800 Message-Id: <5.1.0.14.2.20040111093606.036ece18@ms101.mail1.com> X-Sender: margaret@thingmagic.com@ms101.mail1.com X-Mailer: QUALCOMM Windows Eudora Version 5.1 Date: Sun, 11 Jan 2004 09:38:17 -0500 To: entmib@ietf.org From: Margaret Wasserman Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii"; format=flowed X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on ietf-mx.ietf.org X-Spam-Status: No, hits=0.0 required=5.0 tests=AWL autolearn=no version=2.60 Subject: [Entmib] Proposed Milestone Update Sender: entmib-admin@ietf.org Errors-To: entmib-admin@ietf.org X-BeenThere: entmib@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: IETF Entity MIB WG List-Post: List-Help: List-Subscribe: , Hi All, The Entity MIB (entmib) WG currently has a long list of milestones, some of which are duplicates of each other... I am not quite sure what happened, but I think that one of my earlier updates resulted in duplication, rather than replacement. What I would like to do is prune the entire list so that it only lists these milestones: Done Publish Entity State MIB as a WG I-D Feb 04 Submit the Entity MIB to the IESG for Draft Standard Mar 04 Submit Entity State MIB to the IESG for Proposed Standard Jun 04 Re-charter or shut-down the WG Does that make sense to everyone? Any questions about this? Any concerns that we may not be able to meet these dates? Thanks, Margaret _______________________________________________ Entmib mailing list Entmib@ietf.org https://www1.ietf.org/mailman/listinfo/entmib From exim@www1.ietf.org Sun Jan 11 09:56:29 2004 Received: from optimus.ietf.org ([132.151.1.19]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA00099 for ; Sun, 11 Jan 2004 09:56:29 -0500 (EST) Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1Afh0T-00043B-IF for entmib-archive@odin.ietf.org; Sun, 11 Jan 2004 09:56:01 -0500 Received: (from exim@localhost) by www1.ietf.org (8.12.8/8.12.8/Submit) id i0BEu1Rk015562 for entmib-archive@odin.ietf.org; Sun, 11 Jan 2004 09:56:01 -0500 Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1Afh0S-00042a-OI; Sun, 11 Jan 2004 09:56:00 -0500 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1Afgzl-0003zG-NK for entmib@optimus.ietf.org; Sun, 11 Jan 2004 09:55:17 -0500 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA00022 for ; Sun, 11 Jan 2004 09:55:14 -0500 (EST) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 1Afgzj-0007iC-00 for entmib@ietf.org; Sun, 11 Jan 2004 09:55:15 -0500 Received: from exim by ietf-mx with spam-scanned (Exim 4.12) id 1AfgxU-0007ZK-00 for entmib@ietf.org; Sun, 11 Jan 2004 09:52:57 -0500 Received: from smtp.exodus.net ([66.35.230.236]) by ietf-mx with esmtp (Exim 4.12) id 1Afgua-0007LE-00 for entmib@ietf.org; Sun, 11 Jan 2004 09:49:56 -0500 Received: from ms101.mail1.com (ms101.mail1.com [209.1.5.174]) by smtp.exodus.net (8.12.8/8.12.8) with ESMTP id i0BGT5w3014277 for ; Sun, 11 Jan 2004 08:29:05 -0800 Received: from ala-mrwtemp.thingmagic.com (unverified [24.61.30.237]) by accounting.espmail.com (Rockliffe SMTPRA 5.2.5) with ESMTP id ; Sun, 11 Jan 2004 06:49:16 -0800 Message-Id: <5.1.0.14.2.20040111094056.036b8710@ms101.mail1.com> X-Sender: margaret@thingmagic.com@ms101.mail1.com X-Mailer: QUALCOMM Windows Eudora Version 5.1 Date: Sun, 11 Jan 2004 09:46:35 -0500 To: "Sharon Chisholm" From: Margaret Wasserman Subject: RE: [Entmib] Entity State MIB Next Steps Cc: entmib@ietf.org In-Reply-To: <3549C09B853DD5119B540002A52CDD3409BFEC5B@zcard0ka.ca.norte l.com> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii"; format=flowed X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on ietf-mx.ietf.org X-Spam-Status: No, hits=0.0 required=5.0 tests=AWL autolearn=no version=2.60 Sender: entmib-admin@ietf.org Errors-To: entmib-admin@ietf.org X-BeenThere: entmib@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: IETF Entity MIB WG List-Post: List-Help: List-Subscribe: , Hi Sharon, >My vote is for 1), except if the current update resolves issues from the >previous working group last call do we need a second? There was substantial >rewrite, but no objects were changed. I could go either way. I realize that the objects haven't change, but enough of the text has changed that I would like to have another WG Last Call before sending it to the IESG, just to make sure that the new text has been well-reviewed. >I'm hoping that the more concise text in the latest version appeases the >concern that what the working group has come up with is too complicated. I just finished reading the new version, and I think that it is much simpler and clearer. Thanks! I would be happy to see us publish the Entity State MIB in its current form. What do others think? Margaret _______________________________________________ Entmib mailing list Entmib@ietf.org https://www1.ietf.org/mailman/listinfo/entmib From exim@www1.ietf.org Sun Jan 11 10:39:17 2004 Received: from optimus.ietf.org ([132.151.1.19]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA29819 for ; Sun, 11 Jan 2004 09:52:29 -0500 (EST) Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1Afgwb-0003cD-TI for entmib-archive@odin.ietf.org; Sun, 11 Jan 2004 09:52:01 -0500 Received: (from exim@localhost) by www1.ietf.org (8.12.8/8.12.8/Submit) id i0BEq19v013884 for entmib-archive@odin.ietf.org; Sun, 11 Jan 2004 09:52:01 -0500 Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1Afgwb-0003bl-0l; Sun, 11 Jan 2004 09:52:01 -0500 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1Afgw3-0003bY-TX for entmib@optimus.ietf.org; Sun, 11 Jan 2004 09:51:27 -0500 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA29699 for ; Sun, 11 Jan 2004 09:51:20 -0500 (EST) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 1Afgvr-0007NS-00 for entmib@ietf.org; Sun, 11 Jan 2004 09:51:16 -0500 Received: from exim by ietf-mx with spam-scanned (Exim 4.12) id 1Afgre-0007Be-00 for entmib@ietf.org; Sun, 11 Jan 2004 09:46:54 -0500 Received: from smtp.exodus.net ([66.35.230.236]) by ietf-mx with esmtp (Exim 4.12) id 1Afglw-0006za-00 for entmib@ietf.org; Sun, 11 Jan 2004 09:41:00 -0500 Received: from ms101.mail1.com (ms101.mail1.com [209.1.5.174]) by smtp.exodus.net (8.12.8/8.12.8) with ESMTP id i0BGJqw3014115 for ; Sun, 11 Jan 2004 08:19:54 -0800 Received: from ala-mrwtemp.thingmagic.com (unverified [24.61.30.237]) by accounting.espmail.com (Rockliffe SMTPRA 5.2.5) with ESMTP id for ; Sun, 11 Jan 2004 06:40:02 -0800 Message-Id: <5.1.0.14.2.20040111093606.036ece18@ms101.mail1.com> X-Sender: margaret@thingmagic.com@ms101.mail1.com X-Mailer: QUALCOMM Windows Eudora Version 5.1 Date: Sun, 11 Jan 2004 09:38:17 -0500 To: entmib@ietf.org From: Margaret Wasserman Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii"; format=flowed X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on ietf-mx.ietf.org X-Spam-Status: No, hits=0.0 required=5.0 tests=AWL autolearn=no version=2.60 Subject: [Entmib] Proposed Milestone Update Sender: entmib-admin@ietf.org Errors-To: entmib-admin@ietf.org X-BeenThere: entmib@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: IETF Entity MIB WG List-Post: List-Help: List-Subscribe: , Hi All, The Entity MIB (entmib) WG currently has a long list of milestones, some of which are duplicates of each other... I am not quite sure what happened, but I think that one of my earlier updates resulted in duplication, rather than replacement. What I would like to do is prune the entire list so that it only lists these milestones: Done Publish Entity State MIB as a WG I-D Feb 04 Submit the Entity MIB to the IESG for Draft Standard Mar 04 Submit Entity State MIB to the IESG for Proposed Standard Jun 04 Re-charter or shut-down the WG Does that make sense to everyone? Any questions about this? Any concerns that we may not be able to meet these dates? Thanks, Margaret _______________________________________________ Entmib mailing list Entmib@ietf.org https://www1.ietf.org/mailman/listinfo/entmib From entmib-admin@ietf.org Sun Jan 11 10:43:07 2004 Received: from optimus.ietf.org ([132.151.1.19]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA00097 for ; Sun, 11 Jan 2004 09:56:29 -0500 (EST) Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1Afh0S-00042a-OI; Sun, 11 Jan 2004 09:56:00 -0500 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1Afgzl-0003zG-NK for entmib@optimus.ietf.org; Sun, 11 Jan 2004 09:55:17 -0500 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA00022 for ; Sun, 11 Jan 2004 09:55:14 -0500 (EST) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 1Afgzj-0007iC-00 for entmib@ietf.org; Sun, 11 Jan 2004 09:55:15 -0500 Received: from exim by ietf-mx with spam-scanned (Exim 4.12) id 1AfgxU-0007ZK-00 for entmib@ietf.org; Sun, 11 Jan 2004 09:52:57 -0500 Received: from smtp.exodus.net ([66.35.230.236]) by ietf-mx with esmtp (Exim 4.12) id 1Afgua-0007LE-00 for entmib@ietf.org; Sun, 11 Jan 2004 09:49:56 -0500 Received: from ms101.mail1.com (ms101.mail1.com [209.1.5.174]) by smtp.exodus.net (8.12.8/8.12.8) with ESMTP id i0BGT5w3014277 for ; Sun, 11 Jan 2004 08:29:05 -0800 Received: from ala-mrwtemp.thingmagic.com (unverified [24.61.30.237]) by accounting.espmail.com (Rockliffe SMTPRA 5.2.5) with ESMTP id ; Sun, 11 Jan 2004 06:49:16 -0800 Message-Id: <5.1.0.14.2.20040111094056.036b8710@ms101.mail1.com> X-Sender: margaret@thingmagic.com@ms101.mail1.com X-Mailer: QUALCOMM Windows Eudora Version 5.1 Date: Sun, 11 Jan 2004 09:46:35 -0500 To: "Sharon Chisholm" From: Margaret Wasserman Subject: RE: [Entmib] Entity State MIB Next Steps Cc: entmib@ietf.org In-Reply-To: <3549C09B853DD5119B540002A52CDD3409BFEC5B@zcard0ka.ca.norte l.com> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii"; format=flowed X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on ietf-mx.ietf.org X-Spam-Status: No, hits=0.0 required=5.0 tests=AWL autolearn=no version=2.60 Sender: entmib-admin@ietf.org Errors-To: entmib-admin@ietf.org X-BeenThere: entmib@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: IETF Entity MIB WG List-Post: List-Help: List-Subscribe: , Hi Sharon, >My vote is for 1), except if the current update resolves issues from the >previous working group last call do we need a second? There was substantial >rewrite, but no objects were changed. I could go either way. I realize that the objects haven't change, but enough of the text has changed that I would like to have another WG Last Call before sending it to the IESG, just to make sure that the new text has been well-reviewed. >I'm hoping that the more concise text in the latest version appeases the >concern that what the working group has come up with is too complicated. I just finished reading the new version, and I think that it is much simpler and clearer. Thanks! I would be happy to see us publish the Entity State MIB in its current form. What do others think? Margaret _______________________________________________ Entmib mailing list Entmib@ietf.org https://www1.ietf.org/mailman/listinfo/entmib From exim@www1.ietf.org Sun Jan 11 10:53:28 2004 Received: from optimus.ietf.org ([132.151.1.19]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA02908 for ; Sun, 11 Jan 2004 10:53:28 -0500 (EST) Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1Afhtd-0006SK-V0 for entmib-archive@odin.ietf.org; Sun, 11 Jan 2004 10:53:02 -0500 Received: (from exim@localhost) by www1.ietf.org (8.12.8/8.12.8/Submit) id i0BFr1go024813 for entmib-archive@odin.ietf.org; Sun, 11 Jan 2004 10:53:01 -0500 Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1Afhtd-0006S6-Dg; Sun, 11 Jan 2004 10:53:01 -0500 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AfhtX-0006Rf-M9 for entmib@optimus.ietf.org; Sun, 11 Jan 2004 10:52:55 -0500 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA02900 for ; Sun, 11 Jan 2004 10:52:52 -0500 (EST) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 1AfhtV-0002K1-00 for entmib@ietf.org; Sun, 11 Jan 2004 10:52:53 -0500 Received: from exim by ietf-mx with spam-scanned (Exim 4.12) id 1Afht6-0002GW-00 for entmib@ietf.org; Sun, 11 Jan 2004 10:52:29 -0500 Received: from sj-iport-1-in.cisco.com ([171.71.176.70] helo=sj-iport-1.cisco.com) by ietf-mx with esmtp (Exim 4.12) id 1Afhq8-00026L-00 for entmib@ietf.org; Sun, 11 Jan 2004 10:49:24 -0500 Received: from mira-sjc5-c.cisco.com (IDENT:mirapoint@mira-sjc5-c.cisco.com [171.71.163.17]) by sj-core-1.cisco.com (8.12.9/8.12.6) with ESMTP id i0BFmQGN028512; Sun, 11 Jan 2004 07:48:26 -0800 (PST) Received: from cisco.com (sjc-vpn3-848.cisco.com [10.21.67.80]) by mira-sjc5-c.cisco.com (Mirapoint Messaging Server MOS 3.3.6-GR) with ESMTP id APU04048; Sun, 11 Jan 2004 07:48:25 -0800 (PST) Message-ID: <40017049.7010305@cisco.com> Date: Sun, 11 Jan 2004 07:48:25 -0800 From: Subrahmanya Hegde Organization: Cisco Systems, Inc User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.4) Gecko/20030624 Netscape/7.1 (ax) X-Accept-Language: en-us, en MIME-Version: 1.0 To: Margaret Wasserman CC: entmib@ietf.org Subject: Re: [Entmib] Entity State MIB Next Steps References: <5.1.0.14.2.20040109082204.04499668@ms101.mail1.com> In-Reply-To: <5.1.0.14.2.20040109082204.04499668@ms101.mail1.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on ietf-mx.ietf.org X-Spam-Status: No, hits=0.0 required=5.0 tests=none autolearn=no version=2.60 Content-Transfer-Encoding: 7bit Sender: entmib-admin@ietf.org Errors-To: entmib-admin@ietf.org X-BeenThere: entmib@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: IETF Entity MIB WG List-Post: List-Help: List-Subscribe: , Content-Transfer-Encoding: 7bit Hi a Minor Suggestion: Instead of having these OID definitions: -- Notifications entStateTraps OBJECT IDENTIFIER ::= { entityStateMIB 2 } entStateTrapPrefix OBJECT IDENTIFIER ::= { entStateTraps 0 } We can have entStateNotifs OBJECT IDENTIFIER ::= { entityStateMIB 0 } and use 'entStateNotifs' in the corresponding NOTIFICATION-TYPE Reason we would like to avoid name 'Traps' is: Latest RFCs refer them as Notifications Subra Margaret Wasserman wrote: > > Now that the newest version of the Entity State MIB is available, > the WG has a decision to make. In my opinion, we have two > choices: > > (1) We decide that the structure and objects defined in the > current draft are acceptable, and we send the current draft > to WG Last Call in order to identify and resolve final > issues. > > (2) We decide that we want to change the structure or objects > defined in this MIB to make it simpler or more functional. > > I would appreciate it if people would respond to this message > with their opinions, so that I can attempt to judge the consensus > of the WG on this issue. > > Thanks, > Margaret > > > _______________________________________________ > Entmib mailing list > Entmib@ietf.org > https://www1.ietf.org/mailman/listinfo/entmib > _______________________________________________ Entmib mailing list Entmib@ietf.org https://www1.ietf.org/mailman/listinfo/entmib From entmib-admin@ietf.org Sun Jan 11 11:39:50 2004 Received: from optimus.ietf.org ([132.151.1.19]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA02907 for ; Sun, 11 Jan 2004 10:53:28 -0500 (EST) Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1Afhtd-0006S6-Dg; Sun, 11 Jan 2004 10:53:01 -0500 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AfhtX-0006Rf-M9 for entmib@optimus.ietf.org; Sun, 11 Jan 2004 10:52:55 -0500 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA02900 for ; Sun, 11 Jan 2004 10:52:52 -0500 (EST) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 1AfhtV-0002K1-00 for entmib@ietf.org; Sun, 11 Jan 2004 10:52:53 -0500 Received: from exim by ietf-mx with spam-scanned (Exim 4.12) id 1Afht6-0002GW-00 for entmib@ietf.org; Sun, 11 Jan 2004 10:52:29 -0500 Received: from sj-iport-1-in.cisco.com ([171.71.176.70] helo=sj-iport-1.cisco.com) by ietf-mx with esmtp (Exim 4.12) id 1Afhq8-00026L-00 for entmib@ietf.org; Sun, 11 Jan 2004 10:49:24 -0500 Received: from mira-sjc5-c.cisco.com (IDENT:mirapoint@mira-sjc5-c.cisco.com [171.71.163.17]) by sj-core-1.cisco.com (8.12.9/8.12.6) with ESMTP id i0BFmQGN028512; Sun, 11 Jan 2004 07:48:26 -0800 (PST) Received: from cisco.com (sjc-vpn3-848.cisco.com [10.21.67.80]) by mira-sjc5-c.cisco.com (Mirapoint Messaging Server MOS 3.3.6-GR) with ESMTP id APU04048; Sun, 11 Jan 2004 07:48:25 -0800 (PST) Message-ID: <40017049.7010305@cisco.com> Date: Sun, 11 Jan 2004 07:48:25 -0800 From: Subrahmanya Hegde Organization: Cisco Systems, Inc User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.4) Gecko/20030624 Netscape/7.1 (ax) X-Accept-Language: en-us, en MIME-Version: 1.0 To: Margaret Wasserman CC: entmib@ietf.org Subject: Re: [Entmib] Entity State MIB Next Steps References: <5.1.0.14.2.20040109082204.04499668@ms101.mail1.com> In-Reply-To: <5.1.0.14.2.20040109082204.04499668@ms101.mail1.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on ietf-mx.ietf.org X-Spam-Status: No, hits=0.0 required=5.0 tests=none autolearn=no version=2.60 Content-Transfer-Encoding: 7bit Sender: entmib-admin@ietf.org Errors-To: entmib-admin@ietf.org X-BeenThere: entmib@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: IETF Entity MIB WG List-Post: List-Help: List-Subscribe: , Content-Transfer-Encoding: 7bit Hi a Minor Suggestion: Instead of having these OID definitions: -- Notifications entStateTraps OBJECT IDENTIFIER ::= { entityStateMIB 2 } entStateTrapPrefix OBJECT IDENTIFIER ::= { entStateTraps 0 } We can have entStateNotifs OBJECT IDENTIFIER ::= { entityStateMIB 0 } and use 'entStateNotifs' in the corresponding NOTIFICATION-TYPE Reason we would like to avoid name 'Traps' is: Latest RFCs refer them as Notifications Subra Margaret Wasserman wrote: > > Now that the newest version of the Entity State MIB is available, > the WG has a decision to make. In my opinion, we have two > choices: > > (1) We decide that the structure and objects defined in the > current draft are acceptable, and we send the current draft > to WG Last Call in order to identify and resolve final > issues. > > (2) We decide that we want to change the structure or objects > defined in this MIB to make it simpler or more functional. > > I would appreciate it if people would respond to this message > with their opinions, so that I can attempt to judge the consensus > of the WG on this issue. > > Thanks, > Margaret > > > _______________________________________________ > Entmib mailing list > Entmib@ietf.org > https://www1.ietf.org/mailman/listinfo/entmib > _______________________________________________ Entmib mailing list Entmib@ietf.org https://www1.ietf.org/mailman/listinfo/entmib From entmib-admin@ietf.org Sun Jan 11 22:16:29 2004 Received: from optimus.ietf.org ([132.151.1.19]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id WAA27747 for ; Sun, 11 Jan 2004 22:16:29 -0500 (EST) Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AfsYb-0005dg-Bw; Sun, 11 Jan 2004 22:16:01 -0500 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AfsXf-0005d1-0E for entmib@optimus.ietf.org; Sun, 11 Jan 2004 22:15:03 -0500 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id WAA27728 for ; Sun, 11 Jan 2004 22:14:59 -0500 (EST) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 1AfsXb-00035j-00 for entmib@ietf.org; Sun, 11 Jan 2004 22:14:59 -0500 Received: from exim by ietf-mx with spam-scanned (Exim 4.12) id 1AfsVj-00032Q-00 for entmib@ietf.org; Sun, 11 Jan 2004 22:13:04 -0500 Received: from grebe.mail.pas.earthlink.net ([207.217.120.46]) by ietf-mx with esmtp (Exim 4.12) id 1AfsUz-0002yW-00 for entmib@ietf.org; Sun, 11 Jan 2004 22:12:17 -0500 Received: from h-68-164-80-24.snvacaid.dynamic.covad.net ([68.164.80.24] helo=oemcomputer) by grebe.mail.pas.earthlink.net with smtp (Exim 3.33 #1) id 1AfsUs-0005Hx-00 for entmib@ietf.org; Sun, 11 Jan 2004 19:12:10 -0800 Message-ID: <00cd01c3d8b9$e0c71a40$7f1afea9@oemcomputer> From: "Randy Presuhn" To: References: <5.1.0.14.2.20040109082204.04499668@ms101.mail1.com> <40017049.7010305@cisco.com> Subject: Re: [Entmib] Entity State MIB Next Steps Date: Sun, 11 Jan 2004 19:12:14 -0800 X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 6.00.2800.1158 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1165 X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on ietf-mx.ietf.org X-Spam-Status: No, hits=0.0 required=5.0 tests=none autolearn=no version=2.60 Sender: entmib-admin@ietf.org Errors-To: entmib-admin@ietf.org X-BeenThere: entmib@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: IETF Entity MIB WG List-Post: List-Help: List-Subscribe: , Hi - > From: "Subrahmanya Hegde" > To: "Margaret Wasserman" > Cc: > Sent: Sunday, January 11, 2004 7:48 AM > Subject: Re: [Entmib] Entity State MIB Next Steps ... > Instead of having these OID definitions: > > -- Notifications > > entStateTraps OBJECT IDENTIFIER ::= { entityStateMIB 2 } > entStateTrapPrefix OBJECT IDENTIFIER ::= { entStateTraps 0 } > > > We can have > entStateNotifs OBJECT IDENTIFIER ::= { entityStateMIB 0 } > > and use 'entStateNotifs' in the corresponding NOTIFICATION-TYPE > > Reason we would like to avoid name 'Traps' is: Latest RFCs refer them > as Notifications ... This would also bring it into better alignment with the MIB review guidelines. Randy _______________________________________________ Entmib mailing list Entmib@ietf.org https://www1.ietf.org/mailman/listinfo/entmib From exim@www1.ietf.org Sun Jan 11 22:16:29 2004 Received: from optimus.ietf.org ([132.151.1.19]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id WAA27749 for ; Sun, 11 Jan 2004 22:16:29 -0500 (EST) Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AfsYc-0005eK-5E for entmib-archive@odin.ietf.org; Sun, 11 Jan 2004 22:16:02 -0500 Received: (from exim@localhost) by www1.ietf.org (8.12.8/8.12.8/Submit) id i0C3G1O8021699 for entmib-archive@odin.ietf.org; Sun, 11 Jan 2004 22:16:01 -0500 Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AfsYb-0005dg-Bw; Sun, 11 Jan 2004 22:16:01 -0500 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AfsXf-0005d1-0E for entmib@optimus.ietf.org; Sun, 11 Jan 2004 22:15:03 -0500 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id WAA27728 for ; Sun, 11 Jan 2004 22:14:59 -0500 (EST) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 1AfsXb-00035j-00 for entmib@ietf.org; Sun, 11 Jan 2004 22:14:59 -0500 Received: from exim by ietf-mx with spam-scanned (Exim 4.12) id 1AfsVj-00032Q-00 for entmib@ietf.org; Sun, 11 Jan 2004 22:13:04 -0500 Received: from grebe.mail.pas.earthlink.net ([207.217.120.46]) by ietf-mx with esmtp (Exim 4.12) id 1AfsUz-0002yW-00 for entmib@ietf.org; Sun, 11 Jan 2004 22:12:17 -0500 Received: from h-68-164-80-24.snvacaid.dynamic.covad.net ([68.164.80.24] helo=oemcomputer) by grebe.mail.pas.earthlink.net with smtp (Exim 3.33 #1) id 1AfsUs-0005Hx-00 for entmib@ietf.org; Sun, 11 Jan 2004 19:12:10 -0800 Message-ID: <00cd01c3d8b9$e0c71a40$7f1afea9@oemcomputer> From: "Randy Presuhn" To: References: <5.1.0.14.2.20040109082204.04499668@ms101.mail1.com> <40017049.7010305@cisco.com> Subject: Re: [Entmib] Entity State MIB Next Steps Date: Sun, 11 Jan 2004 19:12:14 -0800 X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 6.00.2800.1158 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1165 X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on ietf-mx.ietf.org X-Spam-Status: No, hits=0.0 required=5.0 tests=none autolearn=no version=2.60 Sender: entmib-admin@ietf.org Errors-To: entmib-admin@ietf.org X-BeenThere: entmib@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: IETF Entity MIB WG List-Post: List-Help: List-Subscribe: , Hi - > From: "Subrahmanya Hegde" > To: "Margaret Wasserman" > Cc: > Sent: Sunday, January 11, 2004 7:48 AM > Subject: Re: [Entmib] Entity State MIB Next Steps ... > Instead of having these OID definitions: > > -- Notifications > > entStateTraps OBJECT IDENTIFIER ::= { entityStateMIB 2 } > entStateTrapPrefix OBJECT IDENTIFIER ::= { entStateTraps 0 } > > > We can have > entStateNotifs OBJECT IDENTIFIER ::= { entityStateMIB 0 } > > and use 'entStateNotifs' in the corresponding NOTIFICATION-TYPE > > Reason we would like to avoid name 'Traps' is: Latest RFCs refer them > as Notifications ... This would also bring it into better alignment with the MIB review guidelines. Randy _______________________________________________ Entmib mailing list Entmib@ietf.org https://www1.ietf.org/mailman/listinfo/entmib From entmib-admin@ietf.org Mon Jan 12 01:09:30 2004 Received: from optimus.ietf.org ([132.151.1.19]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id BAA02020 for ; Mon, 12 Jan 2004 01:09:30 -0500 (EST) Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AfvG1-0002fc-1S; Mon, 12 Jan 2004 01:09:01 -0500 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AfvFt-0002ex-Be for entmib@optimus.ietf.org; Mon, 12 Jan 2004 01:08:53 -0500 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id BAA02015 for ; Mon, 12 Jan 2004 01:08:52 -0500 (EST) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 1AfvFq-0001G2-00 for entmib@ietf.org; Mon, 12 Jan 2004 01:08:50 -0500 Received: from exim by ietf-mx with spam-scanned (Exim 4.12) id 1AfvE3-0001E3-00 for entmib@ietf.org; Mon, 12 Jan 2004 01:07:00 -0500 Received: from tierw.net.avaya.com ([198.152.13.100]) by ietf-mx with esmtp (Exim 4.12) id 1AfvDj-0001Bm-00 for entmib@ietf.org; Mon, 12 Jan 2004 01:06:39 -0500 Received: from tierw.net.avaya.com (localhost [127.0.0.1]) by tierw.net.avaya.com (Switch-3.1.2/Switch-3.1.0) with ESMTP id i0C63Hiv015070 for ; Mon, 12 Jan 2004 01:03:17 -0500 (EST) Received: from IS0004AVEXU1.global.avaya.com (h135-64-105-51.avaya.com [135.64.105.51]) by tierw.net.avaya.com (Switch-3.1.2/Switch-3.1.0) with ESMTP id i0C63Biv015020 for ; Mon, 12 Jan 2004 01:03:12 -0500 (EST) X-MimeOLE: Produced By Microsoft Exchange V6.0.6487.1 content-class: urn:content-classes:message MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Subject: RE: [Entmib] Entity State MIB Next Steps Date: Mon, 12 Jan 2004 08:06:27 +0200 Message-ID: Thread-Topic: [Entmib] Entity State MIB Next Steps Thread-Index: AcPWuA2BsLiEET7xRs+543TEu915jwBz63VQ From: "Romascanu, Dan (Dan)" To: "Sharon Chisholm" , X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on ietf-mx.ietf.org X-Spam-Status: No, hits=0.1 required=5.0 tests=AWL autolearn=no version=2.60 Content-Transfer-Encoding: quoted-printable Sender: entmib-admin@ietf.org Errors-To: entmib-admin@ietf.org X-BeenThere: entmib@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: IETF Entity MIB WG List-Post: List-Help: List-Subscribe: , Content-Transfer-Encoding: quoted-printable I agree with 1) and including the proposal that we should go through a = Last Call again. I do not feel that we had consensus that this is the = right balance between lack of complexity and useful functionality, and = the WG participants should have the formal opportunity to provide again = their inputs. Regards, Dan > -----Original Message----- > From: entmib-admin@ietf.org [mailto:entmib-admin@ietf.org]On=20 > Behalf Of Sharon Chisholm > Sent: 09 January, 2004 3:49 PM > To: entmib@ietf.org > Subject: RE: [Entmib] Entity State MIB Next Steps >=20 >=20 > Hi >=20 > My vote is for 1), except if the current update resolves=20 > issues from the > previous working group last call do we need a second? There=20 > was substantial > rewrite, but no objects were changed. I could go either way. >=20 > I'm hoping that the more concise text in the latest version=20 > appeases the > concern that what the working group has come up with is too=20 > complicated. >=20 > Sharon >=20 > -----Original Message----- > From: Margaret Wasserman [mailto:margaret@thingmagic.com]=20 > Sent: Friday, January 09, 2004 8:26 AM > To: entmib@ietf.org > Subject: [Entmib] Entity State MIB Next Steps >=20 >=20 >=20 > Now that the newest version of the Entity State MIB is=20 > available, the WG has > a decision to make. In my opinion, we have two > choices: >=20 > (1) We decide that the structure and objects defined in the=20 > current draft > are acceptable, and we send the current draft to WG Last Call=20 > in order to > identify and resolve final issues. >=20 > (2) We decide that we want to change the structure or objects=20 > defined in > this MIB to make it simpler or more functional. >=20 > I would appreciate it if people would respond to this message=20 > with their > opinions, so that I can attempt to judge the consensus of the=20 > WG on this > issue. >=20 > Thanks, > Margaret >=20 >=20 > _______________________________________________ > Entmib mailing list > Entmib@ietf.org > https://www1.ietf.org/mailman/listinfo/entmib >=20 > _______________________________________________ > Entmib mailing list > Entmib@ietf.org > https://www1.ietf.org/mailman/listinfo/entmib >=20 _______________________________________________ Entmib mailing list Entmib@ietf.org https://www1.ietf.org/mailman/listinfo/entmib From exim@www1.ietf.org Mon Jan 12 01:09:31 2004 Received: from optimus.ietf.org ([132.151.1.19]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id BAA02037 for ; Mon, 12 Jan 2004 01:09:31 -0500 (EST) Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AfvG1-0002fo-MX for entmib-archive@odin.ietf.org; Mon, 12 Jan 2004 01:09:02 -0500 Received: (from exim@localhost) by www1.ietf.org (8.12.8/8.12.8/Submit) id i0C691HM010275 for entmib-archive@odin.ietf.org; Mon, 12 Jan 2004 01:09:01 -0500 Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AfvG1-0002fc-1S; Mon, 12 Jan 2004 01:09:01 -0500 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AfvFt-0002ex-Be for entmib@optimus.ietf.org; Mon, 12 Jan 2004 01:08:53 -0500 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id BAA02015 for ; Mon, 12 Jan 2004 01:08:52 -0500 (EST) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 1AfvFq-0001G2-00 for entmib@ietf.org; Mon, 12 Jan 2004 01:08:50 -0500 Received: from exim by ietf-mx with spam-scanned (Exim 4.12) id 1AfvE3-0001E3-00 for entmib@ietf.org; Mon, 12 Jan 2004 01:07:00 -0500 Received: from tierw.net.avaya.com ([198.152.13.100]) by ietf-mx with esmtp (Exim 4.12) id 1AfvDj-0001Bm-00 for entmib@ietf.org; Mon, 12 Jan 2004 01:06:39 -0500 Received: from tierw.net.avaya.com (localhost [127.0.0.1]) by tierw.net.avaya.com (Switch-3.1.2/Switch-3.1.0) with ESMTP id i0C63Hiv015070 for ; Mon, 12 Jan 2004 01:03:17 -0500 (EST) Received: from IS0004AVEXU1.global.avaya.com (h135-64-105-51.avaya.com [135.64.105.51]) by tierw.net.avaya.com (Switch-3.1.2/Switch-3.1.0) with ESMTP id i0C63Biv015020 for ; Mon, 12 Jan 2004 01:03:12 -0500 (EST) X-MimeOLE: Produced By Microsoft Exchange V6.0.6487.1 content-class: urn:content-classes:message MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Subject: RE: [Entmib] Entity State MIB Next Steps Date: Mon, 12 Jan 2004 08:06:27 +0200 Message-ID: Thread-Topic: [Entmib] Entity State MIB Next Steps Thread-Index: AcPWuA2BsLiEET7xRs+543TEu915jwBz63VQ From: "Romascanu, Dan (Dan)" To: "Sharon Chisholm" , X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on ietf-mx.ietf.org X-Spam-Status: No, hits=0.1 required=5.0 tests=AWL autolearn=no version=2.60 Content-Transfer-Encoding: quoted-printable Sender: entmib-admin@ietf.org Errors-To: entmib-admin@ietf.org X-BeenThere: entmib@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: IETF Entity MIB WG List-Post: List-Help: List-Subscribe: , Content-Transfer-Encoding: quoted-printable I agree with 1) and including the proposal that we should go through a = Last Call again. I do not feel that we had consensus that this is the = right balance between lack of complexity and useful functionality, and = the WG participants should have the formal opportunity to provide again = their inputs. Regards, Dan > -----Original Message----- > From: entmib-admin@ietf.org [mailto:entmib-admin@ietf.org]On=20 > Behalf Of Sharon Chisholm > Sent: 09 January, 2004 3:49 PM > To: entmib@ietf.org > Subject: RE: [Entmib] Entity State MIB Next Steps >=20 >=20 > Hi >=20 > My vote is for 1), except if the current update resolves=20 > issues from the > previous working group last call do we need a second? There=20 > was substantial > rewrite, but no objects were changed. I could go either way. >=20 > I'm hoping that the more concise text in the latest version=20 > appeases the > concern that what the working group has come up with is too=20 > complicated. >=20 > Sharon >=20 > -----Original Message----- > From: Margaret Wasserman [mailto:margaret@thingmagic.com]=20 > Sent: Friday, January 09, 2004 8:26 AM > To: entmib@ietf.org > Subject: [Entmib] Entity State MIB Next Steps >=20 >=20 >=20 > Now that the newest version of the Entity State MIB is=20 > available, the WG has > a decision to make. In my opinion, we have two > choices: >=20 > (1) We decide that the structure and objects defined in the=20 > current draft > are acceptable, and we send the current draft to WG Last Call=20 > in order to > identify and resolve final issues. >=20 > (2) We decide that we want to change the structure or objects=20 > defined in > this MIB to make it simpler or more functional. >=20 > I would appreciate it if people would respond to this message=20 > with their > opinions, so that I can attempt to judge the consensus of the=20 > WG on this > issue. >=20 > Thanks, > Margaret >=20 >=20 > _______________________________________________ > Entmib mailing list > Entmib@ietf.org > https://www1.ietf.org/mailman/listinfo/entmib >=20 > _______________________________________________ > Entmib mailing list > Entmib@ietf.org > https://www1.ietf.org/mailman/listinfo/entmib >=20 _______________________________________________ Entmib mailing list Entmib@ietf.org https://www1.ietf.org/mailman/listinfo/entmib From exim@www1.ietf.org Mon Jan 12 06:50:30 2004 Received: from optimus.ietf.org ([132.151.1.19]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id GAA22781 for ; Mon, 12 Jan 2004 06:50:29 -0500 (EST) Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1Ag0a3-00082p-HK for entmib-archive@odin.ietf.org; Mon, 12 Jan 2004 06:50:03 -0500 Received: (from exim@localhost) by www1.ietf.org (8.12.8/8.12.8/Submit) id i0CBo3Mj030913 for entmib-archive@odin.ietf.org; Mon, 12 Jan 2004 06:50:03 -0500 Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1Ag0a3-00082S-4S; Mon, 12 Jan 2004 06:50:03 -0500 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1Ag0ZW-000812-7n for entmib@optimus.ietf.org; Mon, 12 Jan 2004 06:49:30 -0500 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id GAA22752 for ; Mon, 12 Jan 2004 06:49:16 -0500 (EST) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 1Ag0ZD-0004mV-00 for entmib@ietf.org; Mon, 12 Jan 2004 06:49:11 -0500 Received: from exim by ietf-mx with spam-scanned (Exim 4.12) id 1Ag0VE-0004cp-00 for entmib@ietf.org; Mon, 12 Jan 2004 06:45:05 -0500 Received: from zcars04f.nortelnetworks.com ([47.129.242.57]) by ietf-mx with esmtp (Exim 4.12) id 1Ag0RJ-0004Sl-00 for entmib@ietf.org; Mon, 12 Jan 2004 06:41:01 -0500 Received: from zcard309.ca.nortel.com (zcard309.ca.nortel.com [47.129.242.69]) by zcars04f.nortelnetworks.com (Switch-2.2.6/Switch-2.2.0) with ESMTP id i0CBe6c25739 for ; Mon, 12 Jan 2004 06:40:06 -0500 (EST) Received: by zcard309.ca.nortel.com with Internet Mail Service (5.5.2653.19) id ; Mon, 12 Jan 2004 06:40:06 -0500 Message-ID: <3549C09B853DD5119B540002A52CDD3409C66956@zcard0ka.ca.nortel.com> From: "Sharon Chisholm" To: entmib@ietf.org Subject: RE: [Entmib] Entity State MIB Next Steps Date: Mon, 12 Jan 2004 06:40:05 -0500 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.2653.19) Content-Type: text/plain X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on ietf-mx.ietf.org X-Spam-Status: No, hits=0.1 required=5.0 tests=AWL autolearn=no version=2.60 Sender: entmib-admin@ietf.org Errors-To: entmib-admin@ietf.org X-BeenThere: entmib@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: IETF Entity MIB WG List-Post: List-Help: List-Subscribe: , Hi I've captured the trap name/oid issue as #306 and will resolve it with any other issues that arrive from the working group last call, which seems to be the consensus path forward. Margaret, I'll leave it to you to call that. Sharon -----Original Message----- From: Romascanu, Dan (Dan) [mailto:dromasca@avaya.com] Sent: Monday, January 12, 2004 1:06 AM To: Chisholm, Sharon [CAR:0S00:EXCH]; entmib@ietf.org Subject: RE: [Entmib] Entity State MIB Next Steps I agree with 1) and including the proposal that we should go through a Last Call again. I do not feel that we had consensus that this is the right balance between lack of complexity and useful functionality, and the WG participants should have the formal opportunity to provide again their inputs. Regards, Dan > -----Original Message----- > From: entmib-admin@ietf.org [mailto:entmib-admin@ietf.org]On > Behalf Of Sharon Chisholm > Sent: 09 January, 2004 3:49 PM > To: entmib@ietf.org > Subject: RE: [Entmib] Entity State MIB Next Steps > > > Hi > > My vote is for 1), except if the current update resolves > issues from the > previous working group last call do we need a second? There > was substantial > rewrite, but no objects were changed. I could go either way. > > I'm hoping that the more concise text in the latest version > appeases the > concern that what the working group has come up with is too > complicated. > > Sharon > > -----Original Message----- > From: Margaret Wasserman [mailto:margaret@thingmagic.com] > Sent: Friday, January 09, 2004 8:26 AM > To: entmib@ietf.org > Subject: [Entmib] Entity State MIB Next Steps > > > > Now that the newest version of the Entity State MIB is > available, the WG has > a decision to make. In my opinion, we have two > choices: > > (1) We decide that the structure and objects defined in the > current draft > are acceptable, and we send the current draft to WG Last Call > in order to > identify and resolve final issues. > > (2) We decide that we want to change the structure or objects > defined in > this MIB to make it simpler or more functional. > > I would appreciate it if people would respond to this message > with their > opinions, so that I can attempt to judge the consensus of the > WG on this > issue. > > Thanks, > Margaret > > > _______________________________________________ > Entmib mailing list > Entmib@ietf.org > https://www1.ietf.org/mailman/listinfo/entmib > > _______________________________________________ > Entmib mailing list > Entmib@ietf.org > https://www1.ietf.org/mailman/listinfo/entmib > _______________________________________________ Entmib mailing list Entmib@ietf.org https://www1.ietf.org/mailman/listinfo/entmib From entmib-admin@ietf.org Mon Jan 12 07:40:00 2004 Received: from optimus.ietf.org ([132.151.1.19]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id GAA22780 for ; Mon, 12 Jan 2004 06:50:29 -0500 (EST) Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1Ag0a3-00082S-4S; Mon, 12 Jan 2004 06:50:03 -0500 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1Ag0ZW-000812-7n for entmib@optimus.ietf.org; Mon, 12 Jan 2004 06:49:30 -0500 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id GAA22752 for ; Mon, 12 Jan 2004 06:49:16 -0500 (EST) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 1Ag0ZD-0004mV-00 for entmib@ietf.org; Mon, 12 Jan 2004 06:49:11 -0500 Received: from exim by ietf-mx with spam-scanned (Exim 4.12) id 1Ag0VE-0004cp-00 for entmib@ietf.org; Mon, 12 Jan 2004 06:45:05 -0500 Received: from zcars04f.nortelnetworks.com ([47.129.242.57]) by ietf-mx with esmtp (Exim 4.12) id 1Ag0RJ-0004Sl-00 for entmib@ietf.org; Mon, 12 Jan 2004 06:41:01 -0500 Received: from zcard309.ca.nortel.com (zcard309.ca.nortel.com [47.129.242.69]) by zcars04f.nortelnetworks.com (Switch-2.2.6/Switch-2.2.0) with ESMTP id i0CBe6c25739 for ; Mon, 12 Jan 2004 06:40:06 -0500 (EST) Received: by zcard309.ca.nortel.com with Internet Mail Service (5.5.2653.19) id ; Mon, 12 Jan 2004 06:40:06 -0500 Message-ID: <3549C09B853DD5119B540002A52CDD3409C66956@zcard0ka.ca.nortel.com> From: "Sharon Chisholm" To: entmib@ietf.org Subject: RE: [Entmib] Entity State MIB Next Steps Date: Mon, 12 Jan 2004 06:40:05 -0500 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.2653.19) Content-Type: text/plain X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on ietf-mx.ietf.org X-Spam-Status: No, hits=0.1 required=5.0 tests=AWL autolearn=no version=2.60 Sender: entmib-admin@ietf.org Errors-To: entmib-admin@ietf.org X-BeenThere: entmib@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: IETF Entity MIB WG List-Post: List-Help: List-Subscribe: , Hi I've captured the trap name/oid issue as #306 and will resolve it with any other issues that arrive from the working group last call, which seems to be the consensus path forward. Margaret, I'll leave it to you to call that. Sharon -----Original Message----- From: Romascanu, Dan (Dan) [mailto:dromasca@avaya.com] Sent: Monday, January 12, 2004 1:06 AM To: Chisholm, Sharon [CAR:0S00:EXCH]; entmib@ietf.org Subject: RE: [Entmib] Entity State MIB Next Steps I agree with 1) and including the proposal that we should go through a Last Call again. I do not feel that we had consensus that this is the right balance between lack of complexity and useful functionality, and the WG participants should have the formal opportunity to provide again their inputs. Regards, Dan > -----Original Message----- > From: entmib-admin@ietf.org [mailto:entmib-admin@ietf.org]On > Behalf Of Sharon Chisholm > Sent: 09 January, 2004 3:49 PM > To: entmib@ietf.org > Subject: RE: [Entmib] Entity State MIB Next Steps > > > Hi > > My vote is for 1), except if the current update resolves > issues from the > previous working group last call do we need a second? There > was substantial > rewrite, but no objects were changed. I could go either way. > > I'm hoping that the more concise text in the latest version > appeases the > concern that what the working group has come up with is too > complicated. > > Sharon > > -----Original Message----- > From: Margaret Wasserman [mailto:margaret@thingmagic.com] > Sent: Friday, January 09, 2004 8:26 AM > To: entmib@ietf.org > Subject: [Entmib] Entity State MIB Next Steps > > > > Now that the newest version of the Entity State MIB is > available, the WG has > a decision to make. In my opinion, we have two > choices: > > (1) We decide that the structure and objects defined in the > current draft > are acceptable, and we send the current draft to WG Last Call > in order to > identify and resolve final issues. > > (2) We decide that we want to change the structure or objects > defined in > this MIB to make it simpler or more functional. > > I would appreciate it if people would respond to this message > with their > opinions, so that I can attempt to judge the consensus of the > WG on this > issue. > > Thanks, > Margaret > > > _______________________________________________ > Entmib mailing list > Entmib@ietf.org > https://www1.ietf.org/mailman/listinfo/entmib > > _______________________________________________ > Entmib mailing list > Entmib@ietf.org > https://www1.ietf.org/mailman/listinfo/entmib > _______________________________________________ Entmib mailing list Entmib@ietf.org https://www1.ietf.org/mailman/listinfo/entmib From entmib-admin@ietf.org Mon Jan 12 09:14:32 2004 Received: from optimus.ietf.org ([132.151.1.19]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA27316 for ; Mon, 12 Jan 2004 09:14:32 -0500 (EST) Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1Ag2pN-0004iD-Fp; Mon, 12 Jan 2004 09:14:01 -0500 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1Ag2oj-0004hG-93 for entmib@optimus.ietf.org; Mon, 12 Jan 2004 09:13:21 -0500 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA27304 for ; Mon, 12 Jan 2004 09:13:19 -0500 (EST) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 1Ag2oh-0003DK-00 for entmib@ietf.org; Mon, 12 Jan 2004 09:13:19 -0500 Received: from exim by ietf-mx with spam-scanned (Exim 4.12) id 1Ag2mt-00038U-00 for entmib@ietf.org; Mon, 12 Jan 2004 09:11:28 -0500 Received: from tierw.net.avaya.com ([198.152.13.100]) by ietf-mx with esmtp (Exim 4.12) id 1Ag2le-00032v-00 for entmib@ietf.org; Mon, 12 Jan 2004 09:10:10 -0500 Received: from tierw.net.avaya.com (localhost [127.0.0.1]) by tierw.net.avaya.com (Switch-3.1.2/Switch-3.1.0) with ESMTP id i0CE6piv013597 for ; Mon, 12 Jan 2004 09:06:51 -0500 (EST) Received: from IS0004AVEXU1.global.avaya.com (h135-64-105-51.avaya.com [135.64.105.51]) by tierw.net.avaya.com (Switch-3.1.2/Switch-3.1.0) with ESMTP id i0CE6miv013553 for ; Mon, 12 Jan 2004 09:06:49 -0500 (EST) X-MimeOLE: Produced By Microsoft Exchange V6.0.6487.1 content-class: urn:content-classes:message MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Subject: RE: [Entmib] Entity State MIB Next Steps Date: Mon, 12 Jan 2004 16:10:05 +0200 Message-ID: Thread-Topic: [Entmib] Entity State MIB Next Steps Thread-Index: AcPYUwwo1AoQbr57SOGvJyPOS5uI8QAwhXJQ From: "Romascanu, Dan (Dan)" To: "Margaret Wasserman" , "Sharon Chisholm" Cc: X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on ietf-mx.ietf.org X-Spam-Status: No, hits=0.1 required=5.0 tests=AWL autolearn=no version=2.60 Content-Transfer-Encoding: quoted-printable Sender: entmib-admin@ietf.org Errors-To: entmib-admin@ietf.org X-BeenThere: entmib@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: IETF Entity MIB WG List-Post: List-Help: List-Subscribe: , Content-Transfer-Encoding: quoted-printable See in line. Regards, Dan >=20 > >My vote is for 1), except if the current update resolves=20 > issues from the > >previous working group last call do we need a second? There=20 > was substantial > >rewrite, but no objects were changed. I could go either way. >=20 > I realize that the objects haven't change, but enough of the text has > changed that I would like to have another WG Last Call before sending > it to the IESG, just to make sure that the new text has been=20 > well-reviewed. I agree with Margaret. Some of the text changes may amount to changes in = semantics, even if the OIDs stay the same. >=20 > >I'm hoping that the more concise text in the latest version=20 > appeases the > >concern that what the working group has come up with is too=20 > complicated. >=20 > I just finished reading the new version, and I think that it is > much simpler and clearer. Thanks! I would be happy to see us publish > the Entity State MIB in its current form. What do others think? Yes - with the comments during and after the last call appropriately = dealt with.=20 >=20 > Margaret >=20 >=20 >=20 > _______________________________________________ > Entmib mailing list > Entmib@ietf.org > https://www1.ietf.org/mailman/listinfo/entmib >=20 _______________________________________________ Entmib mailing list Entmib@ietf.org https://www1.ietf.org/mailman/listinfo/entmib From exim@www1.ietf.org Mon Jan 12 09:14:33 2004 Received: from optimus.ietf.org ([132.151.1.19]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA27332 for ; Mon, 12 Jan 2004 09:14:32 -0500 (EST) Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1Ag2pQ-0004iY-44 for entmib-archive@odin.ietf.org; Mon, 12 Jan 2004 09:14:04 -0500 Received: (from exim@localhost) by www1.ietf.org (8.12.8/8.12.8/Submit) id i0CEE4nI018128 for entmib-archive@odin.ietf.org; Mon, 12 Jan 2004 09:14:04 -0500 Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1Ag2pN-0004iD-Fp; Mon, 12 Jan 2004 09:14:01 -0500 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1Ag2oj-0004hG-93 for entmib@optimus.ietf.org; Mon, 12 Jan 2004 09:13:21 -0500 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA27304 for ; Mon, 12 Jan 2004 09:13:19 -0500 (EST) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 1Ag2oh-0003DK-00 for entmib@ietf.org; Mon, 12 Jan 2004 09:13:19 -0500 Received: from exim by ietf-mx with spam-scanned (Exim 4.12) id 1Ag2mt-00038U-00 for entmib@ietf.org; Mon, 12 Jan 2004 09:11:28 -0500 Received: from tierw.net.avaya.com ([198.152.13.100]) by ietf-mx with esmtp (Exim 4.12) id 1Ag2le-00032v-00 for entmib@ietf.org; Mon, 12 Jan 2004 09:10:10 -0500 Received: from tierw.net.avaya.com (localhost [127.0.0.1]) by tierw.net.avaya.com (Switch-3.1.2/Switch-3.1.0) with ESMTP id i0CE6piv013597 for ; Mon, 12 Jan 2004 09:06:51 -0500 (EST) Received: from IS0004AVEXU1.global.avaya.com (h135-64-105-51.avaya.com [135.64.105.51]) by tierw.net.avaya.com (Switch-3.1.2/Switch-3.1.0) with ESMTP id i0CE6miv013553 for ; Mon, 12 Jan 2004 09:06:49 -0500 (EST) X-MimeOLE: Produced By Microsoft Exchange V6.0.6487.1 content-class: urn:content-classes:message MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Subject: RE: [Entmib] Entity State MIB Next Steps Date: Mon, 12 Jan 2004 16:10:05 +0200 Message-ID: Thread-Topic: [Entmib] Entity State MIB Next Steps Thread-Index: AcPYUwwo1AoQbr57SOGvJyPOS5uI8QAwhXJQ From: "Romascanu, Dan (Dan)" To: "Margaret Wasserman" , "Sharon Chisholm" Cc: X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on ietf-mx.ietf.org X-Spam-Status: No, hits=0.1 required=5.0 tests=AWL autolearn=no version=2.60 Content-Transfer-Encoding: quoted-printable Sender: entmib-admin@ietf.org Errors-To: entmib-admin@ietf.org X-BeenThere: entmib@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: IETF Entity MIB WG List-Post: List-Help: List-Subscribe: , Content-Transfer-Encoding: quoted-printable See in line. Regards, Dan >=20 > >My vote is for 1), except if the current update resolves=20 > issues from the > >previous working group last call do we need a second? There=20 > was substantial > >rewrite, but no objects were changed. I could go either way. >=20 > I realize that the objects haven't change, but enough of the text has > changed that I would like to have another WG Last Call before sending > it to the IESG, just to make sure that the new text has been=20 > well-reviewed. I agree with Margaret. Some of the text changes may amount to changes in = semantics, even if the OIDs stay the same. >=20 > >I'm hoping that the more concise text in the latest version=20 > appeases the > >concern that what the working group has come up with is too=20 > complicated. >=20 > I just finished reading the new version, and I think that it is > much simpler and clearer. Thanks! I would be happy to see us publish > the Entity State MIB in its current form. What do others think? Yes - with the comments during and after the last call appropriately = dealt with.=20 >=20 > Margaret >=20 >=20 >=20 > _______________________________________________ > Entmib mailing list > Entmib@ietf.org > https://www1.ietf.org/mailman/listinfo/entmib >=20 _______________________________________________ Entmib mailing list Entmib@ietf.org https://www1.ietf.org/mailman/listinfo/entmib From entmib-admin@ietf.org Mon Jan 12 16:45:30 2004 Received: from optimus.ietf.org ([132.151.1.19]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA23441 for ; Mon, 12 Jan 2004 16:45:30 -0500 (EST) Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1Ag9rp-0006sl-DQ; Mon, 12 Jan 2004 16:45:01 -0500 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1Ag9rk-0006sR-9C for entmib@optimus.ietf.org; Mon, 12 Jan 2004 16:44:56 -0500 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA23418 for ; Mon, 12 Jan 2004 16:44:53 -0500 (EST) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 1Ag9ri-0003mO-00 for entmib@ietf.org; Mon, 12 Jan 2004 16:44:54 -0500 Received: from exim by ietf-mx with spam-scanned (Exim 4.12) id 1Ag9qC-0003cm-00 for entmib@ietf.org; Mon, 12 Jan 2004 16:43:21 -0500 Received: from sj-iport-5.cisco.com ([171.68.10.87]) by ietf-mx with esmtp (Exim 4.12) id 1Ag9ol-0003Uh-00 for entmib@ietf.org; Mon, 12 Jan 2004 16:41:51 -0500 Received: from sj-core-1.cisco.com (171.71.177.237) by sj-iport-5.cisco.com with ESMTP; 12 Jan 2004 13:41:38 -0800 Received: from cisco.com (cypher.cisco.com [171.69.11.143]) by sj-core-1.cisco.com (8.12.9/8.12.6) with ESMTP id i0CLfIGN022817 for ; Mon, 12 Jan 2004 13:41:19 -0800 (PST) Received: (from kzm@localhost) by cisco.com (8.8.8/2.6/Cisco List Logging/8.8.8) id NAA08000 for entmib@ietf.org; Mon, 12 Jan 2004 13:41:18 -0800 (PST) From: Keith McCloghrie Message-Id: <200401122141.NAA08000@cisco.com> To: entmib@ietf.org Date: Mon, 12 Jan 2004 13:41:18 -0800 (PST) X-Mailer: ELM [version 2.5 PL1] MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on ietf-mx.ietf.org X-Spam-Status: No, hits=0.0 required=5.0 tests=none autolearn=no version=2.60 Content-Transfer-Encoding: 7bit Subject: [Entmib] Comments on draft-ietf-entmib-state-02.txt Sender: entmib-admin@ietf.org Errors-To: entmib-admin@ietf.org X-BeenThere: entmib@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: IETF Entity MIB WG List-Post: List-Help: List-Subscribe: , Content-Transfer-Encoding: 7bit I was asked to post these comments: Keith. > the MIB still needs work: > > the term 'shuttingDown' suggests that the action of shutting down is > in progress, which of course is an operational condition, not an admin > state. A term more reflective of what the AdminState DESCRIPTION appears > to define would be 'noNewUsage'. In any case, this concept of 'usage' > is almost always a higher-level usage (e.g., a new ATM connection on an > ATM interface, a new Unix login on a cpu module, etc.) and thus don't > belong at the physical layer (i.e., don't apply to entPhysicalIndex). > > 'notSupported' is semantically wrong, because a compliant implementation > obviously supports the MIB, but it can return 'notSupported' for > every object in the MIB. Presumably, the intended semantics is that > the agent would return the right value if only it knew the right value; > i.e., 'unknown' is the desired semantics. Also, why is each definition > of 'notSupported' defined in an object's DESCRIPTION, not in the TC's > DESCRIPTION ? > > 'enabled' and 'disabled' to me imply that an admin state, i.e., if > I saw an operState of 'disabled', or a entStateOperDisabled notification, > I'd look for the knob by which I could issue the enable command to enable > it again. > > the entities to which this MIB applies are physical entities, and thus > it seems natural to apply the term 'locked' in a physcial sense, rather > than a logical sense, i.e., 'locked' is not the right term to use for > administratively disabling a device, because if a device had a physical > lock, then its adminState should not be 'locked' if/when its physical lock > could be unlocked, and vice versa. > > 'underRepair' is an operState, not an AlarmState. > > from what perspective are the alarms classified as critical/major/minor/etc. > e.g., does a particular fault have the same alarm status in 'coldStandby' > as it does in 'hotStandby' or in 'providingService' ?? (hint: the answer > is no!!). > > should the MIB define DateAndTimeOrZero ? What does zero mean ? > > for most things, I believe you have to turn them on to see if they work; > if they don't work, you can turn them off again, and label them "inoperable", > but what that means is that they were inoperable the last time they were > turned on, and it doesn't necessarily mean they are still inoperable, e.g., > if something was inoperable the last time it was turned on and has just > been repaired, but not yet turned on again, is it still inoperable ?? > That is, neither 'disabled' nor 'inoperable' is the right term for operState. > _______________________________________________ Entmib mailing list Entmib@ietf.org https://www1.ietf.org/mailman/listinfo/entmib From exim@www1.ietf.org Mon Jan 12 16:45:35 2004 Received: from optimus.ietf.org ([132.151.1.19]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA23442 for ; Mon, 12 Jan 2004 16:45:30 -0500 (EST) Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1Ag9rq-0006tJ-SU for entmib-archive@odin.ietf.org; Mon, 12 Jan 2004 16:45:02 -0500 Received: (from exim@localhost) by www1.ietf.org (8.12.8/8.12.8/Submit) id i0CLj2gP026477 for entmib-archive@odin.ietf.org; Mon, 12 Jan 2004 16:45:02 -0500 Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1Ag9rp-0006sl-DQ; Mon, 12 Jan 2004 16:45:01 -0500 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1Ag9rk-0006sR-9C for entmib@optimus.ietf.org; Mon, 12 Jan 2004 16:44:56 -0500 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA23418 for ; Mon, 12 Jan 2004 16:44:53 -0500 (EST) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 1Ag9ri-0003mO-00 for entmib@ietf.org; Mon, 12 Jan 2004 16:44:54 -0500 Received: from exim by ietf-mx with spam-scanned (Exim 4.12) id 1Ag9qC-0003cm-00 for entmib@ietf.org; Mon, 12 Jan 2004 16:43:21 -0500 Received: from sj-iport-5.cisco.com ([171.68.10.87]) by ietf-mx with esmtp (Exim 4.12) id 1Ag9ol-0003Uh-00 for entmib@ietf.org; Mon, 12 Jan 2004 16:41:51 -0500 Received: from sj-core-1.cisco.com (171.71.177.237) by sj-iport-5.cisco.com with ESMTP; 12 Jan 2004 13:41:38 -0800 Received: from cisco.com (cypher.cisco.com [171.69.11.143]) by sj-core-1.cisco.com (8.12.9/8.12.6) with ESMTP id i0CLfIGN022817 for ; Mon, 12 Jan 2004 13:41:19 -0800 (PST) Received: (from kzm@localhost) by cisco.com (8.8.8/2.6/Cisco List Logging/8.8.8) id NAA08000 for entmib@ietf.org; Mon, 12 Jan 2004 13:41:18 -0800 (PST) From: Keith McCloghrie Message-Id: <200401122141.NAA08000@cisco.com> To: entmib@ietf.org Date: Mon, 12 Jan 2004 13:41:18 -0800 (PST) X-Mailer: ELM [version 2.5 PL1] MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on ietf-mx.ietf.org X-Spam-Status: No, hits=0.0 required=5.0 tests=none autolearn=no version=2.60 Content-Transfer-Encoding: 7bit Subject: [Entmib] Comments on draft-ietf-entmib-state-02.txt Sender: entmib-admin@ietf.org Errors-To: entmib-admin@ietf.org X-BeenThere: entmib@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: IETF Entity MIB WG List-Post: List-Help: List-Subscribe: , Content-Transfer-Encoding: 7bit I was asked to post these comments: Keith. > the MIB still needs work: > > the term 'shuttingDown' suggests that the action of shutting down is > in progress, which of course is an operational condition, not an admin > state. A term more reflective of what the AdminState DESCRIPTION appears > to define would be 'noNewUsage'. In any case, this concept of 'usage' > is almost always a higher-level usage (e.g., a new ATM connection on an > ATM interface, a new Unix login on a cpu module, etc.) and thus don't > belong at the physical layer (i.e., don't apply to entPhysicalIndex). > > 'notSupported' is semantically wrong, because a compliant implementation > obviously supports the MIB, but it can return 'notSupported' for > every object in the MIB. Presumably, the intended semantics is that > the agent would return the right value if only it knew the right value; > i.e., 'unknown' is the desired semantics. Also, why is each definition > of 'notSupported' defined in an object's DESCRIPTION, not in the TC's > DESCRIPTION ? > > 'enabled' and 'disabled' to me imply that an admin state, i.e., if > I saw an operState of 'disabled', or a entStateOperDisabled notification, > I'd look for the knob by which I could issue the enable command to enable > it again. > > the entities to which this MIB applies are physical entities, and thus > it seems natural to apply the term 'locked' in a physcial sense, rather > than a logical sense, i.e., 'locked' is not the right term to use for > administratively disabling a device, because if a device had a physical > lock, then its adminState should not be 'locked' if/when its physical lock > could be unlocked, and vice versa. > > 'underRepair' is an operState, not an AlarmState. > > from what perspective are the alarms classified as critical/major/minor/etc. > e.g., does a particular fault have the same alarm status in 'coldStandby' > as it does in 'hotStandby' or in 'providingService' ?? (hint: the answer > is no!!). > > should the MIB define DateAndTimeOrZero ? What does zero mean ? > > for most things, I believe you have to turn them on to see if they work; > if they don't work, you can turn them off again, and label them "inoperable", > but what that means is that they were inoperable the last time they were > turned on, and it doesn't necessarily mean they are still inoperable, e.g., > if something was inoperable the last time it was turned on and has just > been repaired, but not yet turned on again, is it still inoperable ?? > That is, neither 'disabled' nor 'inoperable' is the right term for operState. > _______________________________________________ Entmib mailing list Entmib@ietf.org https://www1.ietf.org/mailman/listinfo/entmib From entmib-admin@ietf.org Tue Jan 13 03:27:34 2004 Received: from optimus.ietf.org ([132.151.1.19]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id DAA01223 for ; Tue, 13 Jan 2004 03:27:34 -0500 (EST) Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AgJt6-0003Ms-RU; Tue, 13 Jan 2004 03:27:00 -0500 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AgJsG-0003LQ-9t for entmib@optimus.ietf.org; Tue, 13 Jan 2004 03:26:08 -0500 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id DAA01196 for ; Tue, 13 Jan 2004 03:26:06 -0500 (EST) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 1AgJsE-0000kA-00 for entmib@ietf.org; Tue, 13 Jan 2004 03:26:06 -0500 Received: from exim by ietf-mx with spam-scanned (Exim 4.12) id 1AgJqU-0000i6-00 for entmib@ietf.org; Tue, 13 Jan 2004 03:24:19 -0500 Received: from zcars04f.nortelnetworks.com ([47.129.242.57]) by ietf-mx with esmtp (Exim 4.12) id 1AgJox-0000cp-00 for entmib@ietf.org; Tue, 13 Jan 2004 03:22:43 -0500 Received: from zcard309.ca.nortel.com (zcard309.ca.nortel.com [47.129.242.69]) by zcars04f.nortelnetworks.com (Switch-2.2.6/Switch-2.2.0) with ESMTP id i0D8MCe00626 for ; Tue, 13 Jan 2004 03:22:12 -0500 (EST) Received: by zcard309.ca.nortel.com with Internet Mail Service (5.5.2653.19) id ; Tue, 13 Jan 2004 03:22:12 -0500 Message-ID: <3549C09B853DD5119B540002A52CDD3409C67284@zcard0ka.ca.nortel.com> From: "Sharon Chisholm" To: entmib@ietf.org Subject: RE: [Entmib] Comments on draft-ietf-entmib-state-02.txt Date: Tue, 13 Jan 2004 03:22:12 -0500 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.2653.19) Content-Type: text/plain X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on ietf-mx.ietf.org X-Spam-Status: No, hits=0.1 required=5.0 tests=AWL autolearn=no version=2.60 Sender: entmib-admin@ietf.org Errors-To: entmib-admin@ietf.org X-BeenThere: entmib@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: IETF Entity MIB WG List-Post: List-Help: List-Subscribe: , Hi Thanks Keith for the detailed review. I have created issues 307-312 to capture the individual issues you have raised. Here's my initial thoughts on one of the items. ----------------- 307: 'notSupported' is semantically wrong There are three issues here 1. The name 'notSupported' A term like 'notReportable' might be more accurate. Depending on point 307-3, I could go either way. 2. Compliance of implementations that list all values as 'notSupported' Interesting question. It was felt we needed this enumeration to cover the case when certain status could not be reported. Otherwise you end up with holes. I suppose we either allow the case where people just list 'notSupported' for all states for all entities, or we put something in the compliance statement indicating that at least one state should have a value other than 'notSupported'. Again, I could go either way. 3. Description in TC versus Object. The intention is that these TCs could be used in other MIBs so we were trying to not pollute them with any Entity specific concept. As a result, there is quite a bit of description in objects themselves. That having been said, moving text to each TC to the effect of "A value of 'notApplicable' means that this resource is unable to report [this] state." This doesn't really affect this MIB, but would make for better consistency across other MIBs using these TCs. -------------- Sharon -----Original Message----- From: Keith McCloghrie [mailto:kzm@cisco.com] Sent: Monday, January 12, 2004 4:41 PM To: entmib@ietf.org Subject: [Entmib] Comments on draft-ietf-entmib-state-02.txt I was asked to post these comments: Keith. > the MIB still needs work: > > the term 'shuttingDown' suggests that the action of shutting down is > in progress, which of course is an operational condition, not an admin > state. A term more reflective of what the AdminState DESCRIPTION appears > to define would be 'noNewUsage'. In any case, this concept of 'usage' > is almost always a higher-level usage (e.g., a new ATM connection on an > ATM interface, a new Unix login on a cpu module, etc.) and thus don't > belong at the physical layer (i.e., don't apply to > entPhysicalIndex). > > 'notSupported' is semantically wrong, because a compliant implementation > obviously supports the MIB, but it can return 'notSupported' for > every object in the MIB. Presumably, the intended semantics is that > the agent would return the right value if only it knew the right value; > i.e., 'unknown' is the desired semantics. Also, why is each definition > of 'notSupported' defined in an object's DESCRIPTION, not in the TC's > DESCRIPTION ? > > 'enabled' and 'disabled' to me imply that an admin state, i.e., if > I saw an operState of 'disabled', or a entStateOperDisabled notification, > I'd look for the knob by which I could issue the enable command to enable > it again. > > the entities to which this MIB applies are physical entities, and thus > it seems natural to apply the term 'locked' in a physcial sense, rather > than a logical sense, i.e., 'locked' is not the right term to use for > administratively disabling a device, because if a device had a physical > lock, then its adminState should not be 'locked' if/when its physical lock > could be unlocked, and vice versa. > > 'underRepair' is an operState, not an AlarmState. > > from what perspective are the alarms classified as critical/major/minor/etc. > e.g., does a particular fault have the same alarm status in 'coldStandby' > as it does in 'hotStandby' or in 'providingService' ?? (hint: the answer > is no!!). > > should the MIB define DateAndTimeOrZero ? What does zero mean ? > > for most things, I believe you have to turn them on to see if they work; > if they don't work, you can turn them off again, and label them "inoperable", > but what that means is that they were inoperable the last time they were > turned on, and it doesn't necessarily mean they are still inoperable, e.g., > if something was inoperable the last time it was turned on and has just > been repaired, but not yet turned on again, is it still inoperable ?? > That is, neither 'disabled' nor 'inoperable' is the right term for > operState. > _______________________________________________ Entmib mailing list Entmib@ietf.org https://www1.ietf.org/mailman/listinfo/entmib _______________________________________________ Entmib mailing list Entmib@ietf.org https://www1.ietf.org/mailman/listinfo/entmib From exim@www1.ietf.org Tue Jan 13 03:27:35 2004 Received: from optimus.ietf.org ([132.151.1.19]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id DAA01239 for ; Tue, 13 Jan 2004 03:27:34 -0500 (EST) Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AgJtB-0003NQ-FY for entmib-archive@odin.ietf.org; Tue, 13 Jan 2004 03:27:05 -0500 Received: (from exim@localhost) by www1.ietf.org (8.12.8/8.12.8/Submit) id i0D8R53K012971 for entmib-archive@odin.ietf.org; Tue, 13 Jan 2004 03:27:05 -0500 Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AgJt6-0003Ms-RU; Tue, 13 Jan 2004 03:27:00 -0500 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AgJsG-0003LQ-9t for entmib@optimus.ietf.org; Tue, 13 Jan 2004 03:26:08 -0500 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id DAA01196 for ; Tue, 13 Jan 2004 03:26:06 -0500 (EST) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 1AgJsE-0000kA-00 for entmib@ietf.org; Tue, 13 Jan 2004 03:26:06 -0500 Received: from exim by ietf-mx with spam-scanned (Exim 4.12) id 1AgJqU-0000i6-00 for entmib@ietf.org; Tue, 13 Jan 2004 03:24:19 -0500 Received: from zcars04f.nortelnetworks.com ([47.129.242.57]) by ietf-mx with esmtp (Exim 4.12) id 1AgJox-0000cp-00 for entmib@ietf.org; Tue, 13 Jan 2004 03:22:43 -0500 Received: from zcard309.ca.nortel.com (zcard309.ca.nortel.com [47.129.242.69]) by zcars04f.nortelnetworks.com (Switch-2.2.6/Switch-2.2.0) with ESMTP id i0D8MCe00626 for ; Tue, 13 Jan 2004 03:22:12 -0500 (EST) Received: by zcard309.ca.nortel.com with Internet Mail Service (5.5.2653.19) id ; Tue, 13 Jan 2004 03:22:12 -0500 Message-ID: <3549C09B853DD5119B540002A52CDD3409C67284@zcard0ka.ca.nortel.com> From: "Sharon Chisholm" To: entmib@ietf.org Subject: RE: [Entmib] Comments on draft-ietf-entmib-state-02.txt Date: Tue, 13 Jan 2004 03:22:12 -0500 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.2653.19) Content-Type: text/plain X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on ietf-mx.ietf.org X-Spam-Status: No, hits=0.1 required=5.0 tests=AWL autolearn=no version=2.60 Sender: entmib-admin@ietf.org Errors-To: entmib-admin@ietf.org X-BeenThere: entmib@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: IETF Entity MIB WG List-Post: List-Help: List-Subscribe: , Hi Thanks Keith for the detailed review. I have created issues 307-312 to capture the individual issues you have raised. Here's my initial thoughts on one of the items. ----------------- 307: 'notSupported' is semantically wrong There are three issues here 1. The name 'notSupported' A term like 'notReportable' might be more accurate. Depending on point 307-3, I could go either way. 2. Compliance of implementations that list all values as 'notSupported' Interesting question. It was felt we needed this enumeration to cover the case when certain status could not be reported. Otherwise you end up with holes. I suppose we either allow the case where people just list 'notSupported' for all states for all entities, or we put something in the compliance statement indicating that at least one state should have a value other than 'notSupported'. Again, I could go either way. 3. Description in TC versus Object. The intention is that these TCs could be used in other MIBs so we were trying to not pollute them with any Entity specific concept. As a result, there is quite a bit of description in objects themselves. That having been said, moving text to each TC to the effect of "A value of 'notApplicable' means that this resource is unable to report [this] state." This doesn't really affect this MIB, but would make for better consistency across other MIBs using these TCs. -------------- Sharon -----Original Message----- From: Keith McCloghrie [mailto:kzm@cisco.com] Sent: Monday, January 12, 2004 4:41 PM To: entmib@ietf.org Subject: [Entmib] Comments on draft-ietf-entmib-state-02.txt I was asked to post these comments: Keith. > the MIB still needs work: > > the term 'shuttingDown' suggests that the action of shutting down is > in progress, which of course is an operational condition, not an admin > state. A term more reflective of what the AdminState DESCRIPTION appears > to define would be 'noNewUsage'. In any case, this concept of 'usage' > is almost always a higher-level usage (e.g., a new ATM connection on an > ATM interface, a new Unix login on a cpu module, etc.) and thus don't > belong at the physical layer (i.e., don't apply to > entPhysicalIndex). > > 'notSupported' is semantically wrong, because a compliant implementation > obviously supports the MIB, but it can return 'notSupported' for > every object in the MIB. Presumably, the intended semantics is that > the agent would return the right value if only it knew the right value; > i.e., 'unknown' is the desired semantics. Also, why is each definition > of 'notSupported' defined in an object's DESCRIPTION, not in the TC's > DESCRIPTION ? > > 'enabled' and 'disabled' to me imply that an admin state, i.e., if > I saw an operState of 'disabled', or a entStateOperDisabled notification, > I'd look for the knob by which I could issue the enable command to enable > it again. > > the entities to which this MIB applies are physical entities, and thus > it seems natural to apply the term 'locked' in a physcial sense, rather > than a logical sense, i.e., 'locked' is not the right term to use for > administratively disabling a device, because if a device had a physical > lock, then its adminState should not be 'locked' if/when its physical lock > could be unlocked, and vice versa. > > 'underRepair' is an operState, not an AlarmState. > > from what perspective are the alarms classified as critical/major/minor/etc. > e.g., does a particular fault have the same alarm status in 'coldStandby' > as it does in 'hotStandby' or in 'providingService' ?? (hint: the answer > is no!!). > > should the MIB define DateAndTimeOrZero ? What does zero mean ? > > for most things, I believe you have to turn them on to see if they work; > if they don't work, you can turn them off again, and label them "inoperable", > but what that means is that they were inoperable the last time they were > turned on, and it doesn't necessarily mean they are still inoperable, e.g., > if something was inoperable the last time it was turned on and has just > been repaired, but not yet turned on again, is it still inoperable ?? > That is, neither 'disabled' nor 'inoperable' is the right term for > operState. > _______________________________________________ Entmib mailing list Entmib@ietf.org https://www1.ietf.org/mailman/listinfo/entmib _______________________________________________ Entmib mailing list Entmib@ietf.org https://www1.ietf.org/mailman/listinfo/entmib From entmib-admin@ietf.org Tue Jan 13 03:39:31 2004 Received: from optimus.ietf.org ([132.151.1.19]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id DAA01590 for ; Tue, 13 Jan 2004 03:39:31 -0500 (EST) Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AgK4j-0003uT-Qo; Tue, 13 Jan 2004 03:39:01 -0500 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AgK3v-0003nD-Us for entmib@optimus.ietf.org; Tue, 13 Jan 2004 03:38:11 -0500 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id DAA01566 for ; Tue, 13 Jan 2004 03:38:10 -0500 (EST) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 1AgK3t-0001Dg-00 for entmib@ietf.org; Tue, 13 Jan 2004 03:38:09 -0500 Received: from exim by ietf-mx with spam-scanned (Exim 4.12) id 1AgK22-000190-00 for entmib@ietf.org; Tue, 13 Jan 2004 03:36:14 -0500 Received: from zcars04f.nortelnetworks.com ([47.129.242.57]) by ietf-mx with esmtp (Exim 4.12) id 1AgK07-00010Q-00 for entmib@ietf.org; Tue, 13 Jan 2004 03:34:15 -0500 Received: from zcard309.ca.nortel.com (zcard309.ca.nortel.com [47.129.242.69]) by zcars04f.nortelnetworks.com (Switch-2.2.6/Switch-2.2.0) with ESMTP id i0D8XiE00807 for ; Tue, 13 Jan 2004 03:33:44 -0500 (EST) Received: by zcard309.ca.nortel.com with Internet Mail Service (5.5.2653.19) id ; Tue, 13 Jan 2004 03:33:44 -0500 Message-ID: <3549C09B853DD5119B540002A52CDD3409C67289@zcard0ka.ca.nortel.com> From: "Sharon Chisholm" To: entmib@ietf.org Subject: FW: [Entmib] Proposed Milestone Update Date: Tue, 13 Jan 2004 03:33:44 -0500 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.2653.19) Content-Type: text/plain X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on ietf-mx.ietf.org X-Spam-Status: No, hits=0.1 required=5.0 tests=AWL autolearn=no version=2.60 Sender: entmib-admin@ietf.org Errors-To: entmib-admin@ietf.org X-BeenThere: entmib@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: IETF Entity MIB WG List-Post: List-Help: List-Subscribe: , Hi This seems to have been lost. Sharon -----Original Message----- From: Chisholm, Sharon [CAR:0S00:EXCH] Sent: Monday, January 12, 2004 8:45 AM To: 'entmib@ietf.org' Subject: RE: [Entmib] Proposed Milestone Update Hi March seems doable for IESG last call on the Entity State MIB if all goes well. The biggest variable I'd say would be the comments from the MIB Doctor review. Sharon -----Original Message----- From: Margaret Wasserman [mailto:margaret@thingmagic.com] Sent: Sunday, January 11, 2004 9:38 AM To: entmib@ietf.org Subject: [Entmib] Proposed Milestone Update Hi All, The Entity MIB (entmib) WG currently has a long list of milestones, some of which are duplicates of each other... I am not quite sure what happened, but I think that one of my earlier updates resulted in duplication, rather than replacement. What I would like to do is prune the entire list so that it only lists these milestones: Done Publish Entity State MIB as a WG I-D Feb 04 Submit the Entity MIB to the IESG for Draft Standard Mar 04 Submit Entity State MIB to the IESG for Proposed Standard Jun 04 Re-charter or shut-down the WG Does that make sense to everyone? Any questions about this? Any concerns that we may not be able to meet these dates? Thanks, Margaret _______________________________________________ Entmib mailing list Entmib@ietf.org https://www1.ietf.org/mailman/listinfo/entmib _______________________________________________ Entmib mailing list Entmib@ietf.org https://www1.ietf.org/mailman/listinfo/entmib From exim@www1.ietf.org Tue Jan 13 03:39:33 2004 Received: from optimus.ietf.org ([132.151.1.19]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id DAA01607 for ; Tue, 13 Jan 2004 03:39:32 -0500 (EST) Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AgK4l-0003v1-9q for entmib-archive@odin.ietf.org; Tue, 13 Jan 2004 03:39:03 -0500 Received: (from exim@localhost) by www1.ietf.org (8.12.8/8.12.8/Submit) id i0D8d3Ru015049 for entmib-archive@odin.ietf.org; Tue, 13 Jan 2004 03:39:03 -0500 Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AgK4j-0003uT-Qo; Tue, 13 Jan 2004 03:39:01 -0500 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AgK3v-0003nD-Us for entmib@optimus.ietf.org; Tue, 13 Jan 2004 03:38:11 -0500 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id DAA01566 for ; Tue, 13 Jan 2004 03:38:10 -0500 (EST) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 1AgK3t-0001Dg-00 for entmib@ietf.org; Tue, 13 Jan 2004 03:38:09 -0500 Received: from exim by ietf-mx with spam-scanned (Exim 4.12) id 1AgK22-000190-00 for entmib@ietf.org; Tue, 13 Jan 2004 03:36:14 -0500 Received: from zcars04f.nortelnetworks.com ([47.129.242.57]) by ietf-mx with esmtp (Exim 4.12) id 1AgK07-00010Q-00 for entmib@ietf.org; Tue, 13 Jan 2004 03:34:15 -0500 Received: from zcard309.ca.nortel.com (zcard309.ca.nortel.com [47.129.242.69]) by zcars04f.nortelnetworks.com (Switch-2.2.6/Switch-2.2.0) with ESMTP id i0D8XiE00807 for ; Tue, 13 Jan 2004 03:33:44 -0500 (EST) Received: by zcard309.ca.nortel.com with Internet Mail Service (5.5.2653.19) id ; Tue, 13 Jan 2004 03:33:44 -0500 Message-ID: <3549C09B853DD5119B540002A52CDD3409C67289@zcard0ka.ca.nortel.com> From: "Sharon Chisholm" To: entmib@ietf.org Subject: FW: [Entmib] Proposed Milestone Update Date: Tue, 13 Jan 2004 03:33:44 -0500 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.2653.19) Content-Type: text/plain X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on ietf-mx.ietf.org X-Spam-Status: No, hits=0.1 required=5.0 tests=AWL autolearn=no version=2.60 Sender: entmib-admin@ietf.org Errors-To: entmib-admin@ietf.org X-BeenThere: entmib@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: IETF Entity MIB WG List-Post: List-Help: List-Subscribe: , Hi This seems to have been lost. Sharon -----Original Message----- From: Chisholm, Sharon [CAR:0S00:EXCH] Sent: Monday, January 12, 2004 8:45 AM To: 'entmib@ietf.org' Subject: RE: [Entmib] Proposed Milestone Update Hi March seems doable for IESG last call on the Entity State MIB if all goes well. The biggest variable I'd say would be the comments from the MIB Doctor review. Sharon -----Original Message----- From: Margaret Wasserman [mailto:margaret@thingmagic.com] Sent: Sunday, January 11, 2004 9:38 AM To: entmib@ietf.org Subject: [Entmib] Proposed Milestone Update Hi All, The Entity MIB (entmib) WG currently has a long list of milestones, some of which are duplicates of each other... I am not quite sure what happened, but I think that one of my earlier updates resulted in duplication, rather than replacement. What I would like to do is prune the entire list so that it only lists these milestones: Done Publish Entity State MIB as a WG I-D Feb 04 Submit the Entity MIB to the IESG for Draft Standard Mar 04 Submit Entity State MIB to the IESG for Proposed Standard Jun 04 Re-charter or shut-down the WG Does that make sense to everyone? Any questions about this? Any concerns that we may not be able to meet these dates? Thanks, Margaret _______________________________________________ Entmib mailing list Entmib@ietf.org https://www1.ietf.org/mailman/listinfo/entmib _______________________________________________ Entmib mailing list Entmib@ietf.org https://www1.ietf.org/mailman/listinfo/entmib From entmib-admin@ietf.org Tue Jan 13 05:15:31 2004 Received: from optimus.ietf.org ([132.151.1.19]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id FAA04302 for ; Tue, 13 Jan 2004 05:15:31 -0500 (EST) Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AgLZd-0006mz-S5; Tue, 13 Jan 2004 05:15:01 -0500 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AgLYu-0006lT-A5 for entmib@optimus.ietf.org; Tue, 13 Jan 2004 05:14:16 -0500 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id FAA04246 for ; Tue, 13 Jan 2004 05:14:12 -0500 (EST) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 1AgLYq-0004Cu-00 for entmib@ietf.org; Tue, 13 Jan 2004 05:14:12 -0500 Received: from exim by ietf-mx with spam-scanned (Exim 4.12) id 1AgLX0-00049l-00 for entmib@ietf.org; Tue, 13 Jan 2004 05:12:18 -0500 Received: from zcars0m9.nortelnetworks.com ([47.129.242.157]) by ietf-mx with esmtp (Exim 4.12) id 1AgLWA-00046q-00 for entmib@ietf.org; Tue, 13 Jan 2004 05:11:26 -0500 Received: from zcard309.ca.nortel.com (zcard309.ca.nortel.com [47.129.242.69]) by zcars0m9.nortelnetworks.com (Switch-2.2.6/Switch-2.2.0) with ESMTP id i0DAAuq06870 for ; Tue, 13 Jan 2004 05:10:56 -0500 (EST) Received: by zcard309.ca.nortel.com with Internet Mail Service (5.5.2653.19) id ; Tue, 13 Jan 2004 05:10:56 -0500 Message-ID: <3549C09B853DD5119B540002A52CDD3409C6728E@zcard0ka.ca.nortel.com> From: "Sharon Chisholm" To: entmib@ietf.org Date: Tue, 13 Jan 2004 05:10:53 -0500 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.2653.19) Content-Type: text/plain X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on ietf-mx.ietf.org X-Spam-Status: No, hits=0.1 required=5.0 tests=AWL autolearn=no version=2.60 Subject: [Entmib] Thoughts on Issues 308, 309, 310, 312 Sender: entmib-admin@ietf.org Errors-To: entmib-admin@ietf.org X-BeenThere: entmib@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: IETF Entity MIB WG List-Post: List-Help: List-Subscribe: , 308: Shutting Down Admin State ------------------------------ Two issues 1. Is shutting down really more an operational state? The state refers more to whether your administrative model allows systems to be shut down gracefully or not. The idea being that if it does, you would still have the options to bring it down less gracefully. We have allowed in the description of the object for systems that don't support this value for the state. 2. Would 'noNewUsage' be a better term. Well, except that the idea is that once all the existing 'users' are gone, the system will shut down. The term 'noNewUsage' does not really reflect that. 312: Locked Admin State ----------------------- The question was whether this should be a physical lock instead of a logical one. By physical lock do you mean like something that requires a physical key? I think a logical lock, in that case, is both more reportable as well as more useful. 309: Operational State Names and Concepts ----------------------------------------- Two issues 1. 'enabled' and 'disabled' bad name choice Perhaps, but they don't really bother be enough to warrant the change from the OSI names. 2. Predetermining operability before administrative unlocking If there are know error conditions against an entity, then a lot of implementations can tell that it won't be operational if administratively unlocked. I'm sure there are some implementations that can't do this, and I'm sure that even for implementations that can there would be cases when this can't be accurately predicted due to undetected problems or the impact of known problems being underestimated. I would suggest some text indicating something of this sort would be useful. 310: Alarm State Issues ----------------------- Two issues 1. 'underRepair' is an operState, not an AlarmState Well, in this context the idea being that the value of this object is not reliable. We could remove this object I suppose, but I think I'd rather just see text added to this effect. 2. Severity of Alarms The question was whether the severity of the alarms are influenced by other state attributes. The answer is that it is explicitly states in section 2.1 that all of the state objects in this MIB are raw state, so therefore not affected by other states. What you are referring to is computed state which would be nice to get to but we need to walk first. Sharon Chisholm Portfolio Integration Nortel Networks Ottawa, Canada _______________________________________________ Entmib mailing list Entmib@ietf.org https://www1.ietf.org/mailman/listinfo/entmib From exim@www1.ietf.org Tue Jan 13 05:15:33 2004 Received: from optimus.ietf.org ([132.151.1.19]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id FAA04319 for ; Tue, 13 Jan 2004 05:15:33 -0500 (EST) Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AgLZf-0006nO-UH for entmib-archive@odin.ietf.org; Tue, 13 Jan 2004 05:15:06 -0500 Received: (from exim@localhost) by www1.ietf.org (8.12.8/8.12.8/Submit) id i0DAF35x026117 for entmib-archive@odin.ietf.org; Tue, 13 Jan 2004 05:15:03 -0500 Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AgLZd-0006mz-S5; Tue, 13 Jan 2004 05:15:01 -0500 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AgLYu-0006lT-A5 for entmib@optimus.ietf.org; Tue, 13 Jan 2004 05:14:16 -0500 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id FAA04246 for ; Tue, 13 Jan 2004 05:14:12 -0500 (EST) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 1AgLYq-0004Cu-00 for entmib@ietf.org; Tue, 13 Jan 2004 05:14:12 -0500 Received: from exim by ietf-mx with spam-scanned (Exim 4.12) id 1AgLX0-00049l-00 for entmib@ietf.org; Tue, 13 Jan 2004 05:12:18 -0500 Received: from zcars0m9.nortelnetworks.com ([47.129.242.157]) by ietf-mx with esmtp (Exim 4.12) id 1AgLWA-00046q-00 for entmib@ietf.org; Tue, 13 Jan 2004 05:11:26 -0500 Received: from zcard309.ca.nortel.com (zcard309.ca.nortel.com [47.129.242.69]) by zcars0m9.nortelnetworks.com (Switch-2.2.6/Switch-2.2.0) with ESMTP id i0DAAuq06870 for ; Tue, 13 Jan 2004 05:10:56 -0500 (EST) Received: by zcard309.ca.nortel.com with Internet Mail Service (5.5.2653.19) id ; Tue, 13 Jan 2004 05:10:56 -0500 Message-ID: <3549C09B853DD5119B540002A52CDD3409C6728E@zcard0ka.ca.nortel.com> From: "Sharon Chisholm" To: entmib@ietf.org Date: Tue, 13 Jan 2004 05:10:53 -0500 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.2653.19) Content-Type: text/plain X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on ietf-mx.ietf.org X-Spam-Status: No, hits=0.1 required=5.0 tests=AWL autolearn=no version=2.60 Subject: [Entmib] Thoughts on Issues 308, 309, 310, 312 Sender: entmib-admin@ietf.org Errors-To: entmib-admin@ietf.org X-BeenThere: entmib@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: IETF Entity MIB WG List-Post: List-Help: List-Subscribe: , 308: Shutting Down Admin State ------------------------------ Two issues 1. Is shutting down really more an operational state? The state refers more to whether your administrative model allows systems to be shut down gracefully or not. The idea being that if it does, you would still have the options to bring it down less gracefully. We have allowed in the description of the object for systems that don't support this value for the state. 2. Would 'noNewUsage' be a better term. Well, except that the idea is that once all the existing 'users' are gone, the system will shut down. The term 'noNewUsage' does not really reflect that. 312: Locked Admin State ----------------------- The question was whether this should be a physical lock instead of a logical one. By physical lock do you mean like something that requires a physical key? I think a logical lock, in that case, is both more reportable as well as more useful. 309: Operational State Names and Concepts ----------------------------------------- Two issues 1. 'enabled' and 'disabled' bad name choice Perhaps, but they don't really bother be enough to warrant the change from the OSI names. 2. Predetermining operability before administrative unlocking If there are know error conditions against an entity, then a lot of implementations can tell that it won't be operational if administratively unlocked. I'm sure there are some implementations that can't do this, and I'm sure that even for implementations that can there would be cases when this can't be accurately predicted due to undetected problems or the impact of known problems being underestimated. I would suggest some text indicating something of this sort would be useful. 310: Alarm State Issues ----------------------- Two issues 1. 'underRepair' is an operState, not an AlarmState Well, in this context the idea being that the value of this object is not reliable. We could remove this object I suppose, but I think I'd rather just see text added to this effect. 2. Severity of Alarms The question was whether the severity of the alarms are influenced by other state attributes. The answer is that it is explicitly states in section 2.1 that all of the state objects in this MIB are raw state, so therefore not affected by other states. What you are referring to is computed state which would be nice to get to but we need to walk first. Sharon Chisholm Portfolio Integration Nortel Networks Ottawa, Canada _______________________________________________ Entmib mailing list Entmib@ietf.org https://www1.ietf.org/mailman/listinfo/entmib From entmib-admin@ietf.org Fri Jan 23 16:00:30 2004 Received: from optimus.ietf.org ([132.151.1.19]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA22235 for ; Fri, 23 Jan 2004 16:00:30 -0500 (EST) Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1Ak8PJ-0002Px-KZ; Fri, 23 Jan 2004 16:00:01 -0500 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1Ak8OM-0002NO-SJ for entmib@optimus.ietf.org; Fri, 23 Jan 2004 15:59:02 -0500 Received: from CNRI.Reston.VA.US (localhost [127.0.0.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA21853; Fri, 23 Jan 2004 15:58:59 -0500 (EST) Message-Id: <200401232058.PAA21853@ietf.org> Mime-Version: 1.0 Content-Type: Multipart/Mixed; Boundary="NextPart" To: IETF-Announce: ; Cc: entmib@ietf.org From: Internet-Drafts@ietf.org Reply-to: Internet-Drafts@ietf.org Date: Fri, 23 Jan 2004 15:58:59 -0500 Subject: [Entmib] I-D ACTION:draft-ietf-entmib-v3-04.txt Sender: entmib-admin@ietf.org Errors-To: entmib-admin@ietf.org X-BeenThere: entmib@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: IETF Entity MIB WG List-Post: List-Help: List-Subscribe: , --NextPart A New Internet-Draft is available from the on-line Internet-Drafts directories. This draft is a work item of the Entity MIB Working Group of the IETF. Title : Entity MIB (Version 3) Author(s) : K. McCloghrie, A. Bierman Filename : draft-ietf-entmib-v3-04.txt Pages : 66 Date : 2004-1-23 This memo defines a portion of the Management Information Base (MIB) for use with network management protocols in the Internet community. In particular, it describes managed objects used for managing multiple logical and physical entities managed by a single SNMP agent. This document specifies version 3 of the Entity MIB, which obsoletes version 2 (RFC 2737). A URL for this Internet-Draft is: http://www.ietf.org/internet-drafts/draft-ietf-entmib-v3-04.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-entmib-v3-04.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-entmib-v3-04.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: <2004-1-23161712.I-D@ietf.org> ENCODING mime FILE /internet-drafts/draft-ietf-entmib-v3-04.txt --OtherAccess Content-Type: Message/External-body; name="draft-ietf-entmib-v3-04.txt"; site="ftp.ietf.org"; access-type="anon-ftp"; directory="internet-drafts" Content-Type: text/plain Content-ID: <2004-1-23161712.I-D@ietf.org> --OtherAccess-- --NextPart-- _______________________________________________ Entmib mailing list Entmib@ietf.org https://www1.ietf.org/mailman/listinfo/entmib From exim@www1.ietf.org Fri Jan 23 16:00:31 2004 Received: from optimus.ietf.org ([132.151.1.19]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA22252 for ; Fri, 23 Jan 2004 16:00:31 -0500 (EST) Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1Ak8PK-0002Qu-Kl for entmib-archive@odin.ietf.org; Fri, 23 Jan 2004 16:00:02 -0500 Received: (from exim@localhost) by www1.ietf.org (8.12.8/8.12.8/Submit) id i0NL026t009329 for entmib-archive@odin.ietf.org; Fri, 23 Jan 2004 16:00:02 -0500 Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1Ak8PJ-0002Px-KZ; Fri, 23 Jan 2004 16:00:01 -0500 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1Ak8OM-0002NO-SJ for entmib@optimus.ietf.org; Fri, 23 Jan 2004 15:59:02 -0500 Received: from CNRI.Reston.VA.US (localhost [127.0.0.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA21853; Fri, 23 Jan 2004 15:58:59 -0500 (EST) Message-Id: <200401232058.PAA21853@ietf.org> Mime-Version: 1.0 Content-Type: Multipart/Mixed; Boundary="NextPart" To: IETF-Announce: ; Cc: entmib@ietf.org From: Internet-Drafts@ietf.org Reply-to: Internet-Drafts@ietf.org Date: Fri, 23 Jan 2004 15:58:59 -0500 Subject: [Entmib] I-D ACTION:draft-ietf-entmib-v3-04.txt Sender: entmib-admin@ietf.org Errors-To: entmib-admin@ietf.org X-BeenThere: entmib@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: IETF Entity MIB WG List-Post: List-Help: List-Subscribe: , --NextPart A New Internet-Draft is available from the on-line Internet-Drafts directories. This draft is a work item of the Entity MIB Working Group of the IETF. Title : Entity MIB (Version 3) Author(s) : K. McCloghrie, A. Bierman Filename : draft-ietf-entmib-v3-04.txt Pages : 66 Date : 2004-1-23 This memo defines a portion of the Management Information Base (MIB) for use with network management protocols in the Internet community. In particular, it describes managed objects used for managing multiple logical and physical entities managed by a single SNMP agent. This document specifies version 3 of the Entity MIB, which obsoletes version 2 (RFC 2737). A URL for this Internet-Draft is: http://www.ietf.org/internet-drafts/draft-ietf-entmib-v3-04.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-entmib-v3-04.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-entmib-v3-04.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: <2004-1-23161712.I-D@ietf.org> ENCODING mime FILE /internet-drafts/draft-ietf-entmib-v3-04.txt --OtherAccess Content-Type: Message/External-body; name="draft-ietf-entmib-v3-04.txt"; site="ftp.ietf.org"; access-type="anon-ftp"; directory="internet-drafts" Content-Type: text/plain Content-ID: <2004-1-23161712.I-D@ietf.org> --OtherAccess-- --NextPart-- _______________________________________________ Entmib mailing list Entmib@ietf.org https://www1.ietf.org/mailman/listinfo/entmib From entmib-admin@ietf.org Fri Jan 23 17:00:34 2004 Received: from optimus.ietf.org ([132.151.1.19]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA28577 for ; Fri, 23 Jan 2004 17:00:34 -0500 (EST) Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1Ak9LQ-0005Zw-4D; Fri, 23 Jan 2004 17:00:04 -0500 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1Ak9KR-0005Y1-8U for entmib@optimus.ietf.org; Fri, 23 Jan 2004 16:59:03 -0500 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA28500 for ; Fri, 23 Jan 2004 16:58:59 -0500 (EST) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 1Ak9KL-0001yv-00 for entmib@ietf.org; Fri, 23 Jan 2004 16:58:57 -0500 Received: from exim by ietf-mx with spam-scanned (Exim 4.12) id 1Ak9Jf-0001x1-00 for entmib@ietf.org; Fri, 23 Jan 2004 16:58:15 -0500 Received: from smtp.exodus.net ([66.35.230.236]) by ietf-mx with esmtp (Exim 4.12) id 1Ak9J4-0001oF-00 for entmib@ietf.org; Fri, 23 Jan 2004 16:57:38 -0500 Received: from ms101.mail1.com (ms101.mail1.com [209.1.5.174]) by smtp.exodus.net (8.12.8/8.12.8) with ESMTP id i0NNaYw3029308 for ; Fri, 23 Jan 2004 15:36:34 -0800 Received: from ala-mrwtemp.thingmagic.com (unverified [207.31.248.169]) by accounting.espmail.com (Rockliffe SMTPRA 5.2.5) with ESMTP id for ; Fri, 23 Jan 2004 13:57:06 -0800 Message-Id: <5.1.0.14.2.20040123160612.0447e570@ms101.mail1.com> X-Sender: margaret@thingmagic.com@ms101.mail1.com X-Mailer: QUALCOMM Windows Eudora Version 5.1 Date: Fri, 23 Jan 2004 16:53:18 -0500 To: entmib@ietf.org From: Margaret Wasserman Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii"; format=flowed X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on ietf-mx.ietf.org X-Spam-Status: No, hits=0.0 required=5.0 tests=none autolearn=no version=2.60 Subject: [Entmib] Final Check: EntMIB to Draft Standard Sender: entmib-admin@ietf.org Errors-To: entmib-admin@ietf.org X-BeenThere: entmib@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: IETF Entity MIB WG List-Post: List-Help: List-Subscribe: , Hi All, I believe that we are ready to send the Entity MIB to the IESG for publication as a Draft Standard RFC. The latest Entity MIB document can be found at: http://www.ietf.org/internet-drafts/draft-ietf-entmib-v3-04.txt Our implementation report can be found at: http://www.psg.com/~mrw/EntMIB-Impl-Report-Sep03.html This document has been through several WG last calls, and this final version addresses all of the WG last call issues and brings the MIB into alignment with our implementation report. I will be doing a quick review of the I-D and the implementation report to make sure that they do match, and then I will submit it to Bert for publication. If you have any concerns or issues regarding this plan, please let me know by Tuesday (27-Jan) at 5pm EST. Margaret _______________________________________________ Entmib mailing list Entmib@ietf.org https://www1.ietf.org/mailman/listinfo/entmib From exim@www1.ietf.org Fri Jan 23 17:00:35 2004 Received: from optimus.ietf.org ([132.151.1.19]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA28594 for ; Fri, 23 Jan 2004 17:00:35 -0500 (EST) Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1Ak9LT-0005bA-QD for entmib-archive@odin.ietf.org; Fri, 23 Jan 2004 17:00:08 -0500 Received: (from exim@localhost) by www1.ietf.org (8.12.8/8.12.8/Submit) id i0NM07ep021506 for entmib-archive@odin.ietf.org; Fri, 23 Jan 2004 17:00:07 -0500 Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1Ak9LQ-0005Zw-4D; Fri, 23 Jan 2004 17:00:04 -0500 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1Ak9KR-0005Y1-8U for entmib@optimus.ietf.org; Fri, 23 Jan 2004 16:59:03 -0500 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA28500 for ; Fri, 23 Jan 2004 16:58:59 -0500 (EST) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 1Ak9KL-0001yv-00 for entmib@ietf.org; Fri, 23 Jan 2004 16:58:57 -0500 Received: from exim by ietf-mx with spam-scanned (Exim 4.12) id 1Ak9Jf-0001x1-00 for entmib@ietf.org; Fri, 23 Jan 2004 16:58:15 -0500 Received: from smtp.exodus.net ([66.35.230.236]) by ietf-mx with esmtp (Exim 4.12) id 1Ak9J4-0001oF-00 for entmib@ietf.org; Fri, 23 Jan 2004 16:57:38 -0500 Received: from ms101.mail1.com (ms101.mail1.com [209.1.5.174]) by smtp.exodus.net (8.12.8/8.12.8) with ESMTP id i0NNaYw3029308 for ; Fri, 23 Jan 2004 15:36:34 -0800 Received: from ala-mrwtemp.thingmagic.com (unverified [207.31.248.169]) by accounting.espmail.com (Rockliffe SMTPRA 5.2.5) with ESMTP id for ; Fri, 23 Jan 2004 13:57:06 -0800 Message-Id: <5.1.0.14.2.20040123160612.0447e570@ms101.mail1.com> X-Sender: margaret@thingmagic.com@ms101.mail1.com X-Mailer: QUALCOMM Windows Eudora Version 5.1 Date: Fri, 23 Jan 2004 16:53:18 -0500 To: entmib@ietf.org From: Margaret Wasserman Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii"; format=flowed X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on ietf-mx.ietf.org X-Spam-Status: No, hits=0.0 required=5.0 tests=none autolearn=no version=2.60 Subject: [Entmib] Final Check: EntMIB to Draft Standard Sender: entmib-admin@ietf.org Errors-To: entmib-admin@ietf.org X-BeenThere: entmib@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: IETF Entity MIB WG List-Post: List-Help: List-Subscribe: , Hi All, I believe that we are ready to send the Entity MIB to the IESG for publication as a Draft Standard RFC. The latest Entity MIB document can be found at: http://www.ietf.org/internet-drafts/draft-ietf-entmib-v3-04.txt Our implementation report can be found at: http://www.psg.com/~mrw/EntMIB-Impl-Report-Sep03.html This document has been through several WG last calls, and this final version addresses all of the WG last call issues and brings the MIB into alignment with our implementation report. I will be doing a quick review of the I-D and the implementation report to make sure that they do match, and then I will submit it to Bert for publication. If you have any concerns or issues regarding this plan, please let me know by Tuesday (27-Jan) at 5pm EST. Margaret _______________________________________________ Entmib mailing list Entmib@ietf.org https://www1.ietf.org/mailman/listinfo/entmib From entmib-admin@ietf.org Fri Jan 23 17:05:30 2004 Received: from optimus.ietf.org ([132.151.1.19]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA29081 for ; Fri, 23 Jan 2004 17:05:30 -0500 (EST) Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1Ak9QF-0005y0-LI; Fri, 23 Jan 2004 17:05:03 -0500 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1Ak9Q8-0005wz-M8 for entmib@optimus.ietf.org; Fri, 23 Jan 2004 17:04:56 -0500 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA29066 for ; Fri, 23 Jan 2004 17:04:53 -0500 (EST) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 1Ak9Q6-0002Wp-00 for entmib@ietf.org; Fri, 23 Jan 2004 17:04:54 -0500 Received: from exim by ietf-mx with spam-scanned (Exim 4.12) id 1Ak9P8-0002Uu-00 for entmib@ietf.org; Fri, 23 Jan 2004 17:03:55 -0500 Received: from smtp.exodus.net ([66.35.230.236]) by ietf-mx with esmtp (Exim 4.12) id 1Ak9OX-0002LB-00 for Entmib@ietf.org; Fri, 23 Jan 2004 17:03:17 -0500 Received: from ms101.mail1.com (ms101.mail1.com [209.1.5.174]) by smtp.exodus.net (8.12.8/8.12.8) with ESMTP id i0NNgCw3029470 for ; Fri, 23 Jan 2004 15:42:12 -0800 Received: from ala-mrwtemp.thingmagic.com (unverified [207.31.248.169]) by accounting.espmail.com (Rockliffe SMTPRA 5.2.5) with ESMTP id for ; Fri, 23 Jan 2004 14:02:46 -0800 Message-Id: <5.1.0.14.2.20040123165643.045a9d70@ms101.mail1.com> X-Sender: margaret@thingmagic.com@ms101.mail1.com X-Mailer: QUALCOMM Windows Eudora Version 5.1 Date: Fri, 23 Jan 2004 17:00:59 -0500 To: Entmib@ietf.org From: Margaret Wasserman Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii"; format=flowed X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on ietf-mx.ietf.org X-Spam-Status: No, hits=0.0 required=5.0 tests=none autolearn=no version=2.60 Subject: [Entmib] WG Last Call: Entity State MIB Sender: entmib-admin@ietf.org Errors-To: entmib-admin@ietf.org X-BeenThere: entmib@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: IETF Entity MIB WG List-Post: List-Help: List-Subscribe: , Hi All, This is a two week WG Last Call for submitting the Entity State MIB to the IESG for publication as a Proposed Standard. The latest version of this document can be found at: http://www.ietf.org/internet-drafts/draft-ietf-entmib-state-02.txt This WG Last Call will end on Friday, February 6th at 5pm EST. Please review the document and forward substantive comments to the mailing list. Editorial comments can be sent directly to the authors. Thanks, Margaret _______________________________________________ Entmib mailing list Entmib@ietf.org https://www1.ietf.org/mailman/listinfo/entmib From exim@www1.ietf.org Fri Jan 23 17:05:30 2004 Received: from optimus.ietf.org ([132.151.1.19]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA29083 for ; Fri, 23 Jan 2004 17:05:30 -0500 (EST) Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1Ak9QF-0005yd-T5 for entmib-archive@odin.ietf.org; Fri, 23 Jan 2004 17:05:03 -0500 Received: (from exim@localhost) by www1.ietf.org (8.12.8/8.12.8/Submit) id i0NM53Hf022962 for entmib-archive@odin.ietf.org; Fri, 23 Jan 2004 17:05:03 -0500 Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1Ak9QF-0005y0-LI; Fri, 23 Jan 2004 17:05:03 -0500 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1Ak9Q8-0005wz-M8 for entmib@optimus.ietf.org; Fri, 23 Jan 2004 17:04:56 -0500 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA29066 for ; Fri, 23 Jan 2004 17:04:53 -0500 (EST) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 1Ak9Q6-0002Wp-00 for entmib@ietf.org; Fri, 23 Jan 2004 17:04:54 -0500 Received: from exim by ietf-mx with spam-scanned (Exim 4.12) id 1Ak9P8-0002Uu-00 for entmib@ietf.org; Fri, 23 Jan 2004 17:03:55 -0500 Received: from smtp.exodus.net ([66.35.230.236]) by ietf-mx with esmtp (Exim 4.12) id 1Ak9OX-0002LB-00 for Entmib@ietf.org; Fri, 23 Jan 2004 17:03:17 -0500 Received: from ms101.mail1.com (ms101.mail1.com [209.1.5.174]) by smtp.exodus.net (8.12.8/8.12.8) with ESMTP id i0NNgCw3029470 for ; Fri, 23 Jan 2004 15:42:12 -0800 Received: from ala-mrwtemp.thingmagic.com (unverified [207.31.248.169]) by accounting.espmail.com (Rockliffe SMTPRA 5.2.5) with ESMTP id for ; Fri, 23 Jan 2004 14:02:46 -0800 Message-Id: <5.1.0.14.2.20040123165643.045a9d70@ms101.mail1.com> X-Sender: margaret@thingmagic.com@ms101.mail1.com X-Mailer: QUALCOMM Windows Eudora Version 5.1 Date: Fri, 23 Jan 2004 17:00:59 -0500 To: Entmib@ietf.org From: Margaret Wasserman Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii"; format=flowed X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on ietf-mx.ietf.org X-Spam-Status: No, hits=0.0 required=5.0 tests=none autolearn=no version=2.60 Subject: [Entmib] WG Last Call: Entity State MIB Sender: entmib-admin@ietf.org Errors-To: entmib-admin@ietf.org X-BeenThere: entmib@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: IETF Entity MIB WG List-Post: List-Help: List-Subscribe: , Hi All, This is a two week WG Last Call for submitting the Entity State MIB to the IESG for publication as a Proposed Standard. The latest version of this document can be found at: http://www.ietf.org/internet-drafts/draft-ietf-entmib-state-02.txt This WG Last Call will end on Friday, February 6th at 5pm EST. Please review the document and forward substantive comments to the mailing list. Editorial comments can be sent directly to the authors. Thanks, Margaret _______________________________________________ Entmib mailing list Entmib@ietf.org https://www1.ietf.org/mailman/listinfo/entmib