From mailman-bounces@ietf.org Sun Aug 1 08:08:46 2004 Received: from megatron.ietf.org (megatron.ietf.org [132.151.6.71]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA15959 for ; Sun, 1 Aug 2004 08:08:46 -0400 (EDT) Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1BrCeq-0000Qi-VY for entmib-archive@lists.ietf.org; Sun, 01 Aug 2004 05:29:32 -0400 MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Subject: ietf.org mailing list memberships reminder From: mailman-owner@ietf.org To: entmib-archive@ietf.org X-No-Archive: yes Message-ID: Date: Sun, 01 Aug 2004 05:08:09 -0400 Precedence: bulk X-BeenThere: mailman@lists.ietf.org X-Mailman-Version: 2.1.5 List-Id: Mailman site list X-List-Administrivia: yes Sender: mailman-bounces@ietf.org Errors-To: mailman-bounces@ietf.org Content-Transfer-Encoding: 7bit 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, mailman-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: Any submission to the IETF intended by the Contributor for publication as all or part of an IETF Internet-Draft or RFC and any statement made within the context of an IETF activity is considered an "IETF Contribution". Such statements include oral statements in IETF sessions, as well as written and electronic communications made at any time or place, which are addressed to: o the IETF plenary session, o any IETF working group or portion thereof, o the IESG, or any member thereof on behalf of the IESG, o the IAB or any member thereof on behalf of the IAB, o any IETF mailing list, including the IETF list itself, any working group or design team list, or any other list functioning under IETF auspices, o the RFC Editor or the Internet-Drafts function All IETF Contributions are subject to the rules of RFC 3667 and RFC 3668. Statements made outside of an IETF session, mailing list or other function, that are clearly not intended to be input to an IETF activity, group or function, are not IETF Contributions in the context of this notice. Please consult RFC 3667 for details. ******************************************************************************* If you have questions, problems, comments, etc, send them to mailman-owner@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-bounces@ietf.org Tue Aug 3 17:38:50 2004 Received: from megatron.ietf.org (megatron.ietf.org [132.151.6.71]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA14226 for ; Tue, 3 Aug 2004 17:38:50 -0400 (EDT) Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1Bs6uj-0007Fj-O5; Tue, 03 Aug 2004 17:33:41 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1Bs6uG-0007A7-9G for entmib@megatron.ietf.org; Tue, 03 Aug 2004 17:33:12 -0400 Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA13885 for ; Tue, 3 Aug 2004 17:33:10 -0400 (EDT) Received: from zcars0m9.nortelnetworks.com ([47.129.242.157]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1Bs6xL-0001sO-NN for entmib@ietf.org; Tue, 03 Aug 2004 17:36:28 -0400 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 i73LWUv07974 for ; Tue, 3 Aug 2004 17:32:30 -0400 (EDT) Received: by zcard309.ca.nortel.com with Internet Mail Service (5.5.2653.19) id ; Tue, 3 Aug 2004 17:32:31 -0400 Message-ID: <713043CE8B8E1348AF3C546DBE02C1B4FD7A28@zcarhxm2.corp.nortel.com> From: "Sharon Chisholm" To: entmib@ietf.org Subject: RE: [Entmib] Entity State MIB Status Date: Tue, 3 Aug 2004 17:32:25 -0400 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.2653.19) Content-Type: text/plain X-Spam-Score: 0.0 (/) X-Scan-Signature: d0bdc596f8dd1c226c458f0b4df27a88 X-BeenThere: entmib@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: IETF Entity MIB WG List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: entmib-bounces@ietf.org Errors-To: entmib-bounces@ietf.org hi >From this afternoon's meeting. These issues will be closed once the proposed changes, if applicable, are made to the draft. Please send any objections to these proposed resolution by August 10, 2004. 307 'notSupported' is semantically wrong - This has been changed to 'unavailable'. Some people had wanted 'unknown'. Should I have changed this to unknown? Proposed Resolution: change to 'unknown' 311 DateAndTimeOrZero - Didn't really have proposed resolution or rather we had a couple comments after the proposed resolution Proposed Resolution: Juergen to advance change to data and Time. No further change to draft 322 Textual Convention Names (Prefix) - I just missed the prefix during the edit. It is in a separate module though. - I will update with an 'Entity' prefix Proposed Resolution: Add the 'Entity' Prefix 325 - I thought I made this change, but apparently didn't. I will make it. Proposed Resolution: Change this OID as previously agreed 333 Relationship with Alarm MIB open entity-state - The open bit of this is whether the Alarm MIB should be a normative or informative reference. I think it's a bit of a grey area so propose leaving it where it is for now. Proposed Resolution: Move it to an informative reference 334 Table, Index Descriptions open entity-state - I think the changes reflect what people were looking for, but I wasn't sure. Proposed Resolution: No further changes required 354 More Editorial Changes (2) - I'm not sure what is wrong with the term 'reports' so I can't suggest a replacement - We haven't yet discussed this one, but adding X.731 to the Reference clause was a previous editing instruction based either on consensus or a suggestion from the area director - I forget which. I propose keeping it. Proposed Resolution: Remove 'Reference' clauses in the MIB and move X.731 to be an informative reference. 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-bounces@ietf.org Sat Aug 7 10:44:42 2004 Received: from megatron.ietf.org (megatron.ietf.org [132.151.6.71]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA03775 for ; Sat, 7 Aug 2004 10:44:42 -0400 (EDT) Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1BtSNX-00017V-IA; Sat, 07 Aug 2004 10:40:59 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1BtSM3-0000wj-Bn for entmib@megatron.ietf.org; Sat, 07 Aug 2004 10:39:27 -0400 Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA03527 for ; Sat, 7 Aug 2004 10:39:22 -0400 (EDT) Received: from mail.thingmagic.com ([207.31.248.245] helo=thingmagic.com) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1BtSPv-0004OD-Pi for entmib@ietf.org; Sat, 07 Aug 2004 10:43:29 -0400 Received: from [68.64.253.86] (account margaret HELO [130.129.130.34]) by thingmagic.com (CommuniGate Pro SMTP 4.1.8) with ESMTP-TLS id 123854 for entmib@ietf.org; Sat, 07 Aug 2004 10:36:00 -0400 Mime-Version: 1.0 X-Sender: margaret@mail.thingmagic.com Message-Id: Date: Fri, 6 Aug 2004 23:41:02 -0400 To: entmib@ietf.org From: Margaret Wasserman Content-Type: text/plain; charset="us-ascii" ; format="flowed" X-Spam-Score: 0.8 (/) X-Scan-Signature: 856eb5f76e7a34990d1d457d8e8e5b7f Subject: [Entmib] CONSENSUS CHECK: Undo entAliasMapping deprecation X-BeenThere: entmib@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: IETF Entity MIB WG List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: entmib-bounces@ietf.org Errors-To: entmib-bounces@ietf.org During the Entity MIB meeting at IETF 60 in San Diego, there was consensus in the room for the following course of action: (1) Pull the Entity State MIB document out of IESG processing (currently submitted for publication as a Draft Standard) (2) Update the document to undo the deprecation of the entAliasMapping identifier, and (3) Re-submit the Entity MIB to the IESG for publication as a Proposed Standard. We now need to confirm this consensus on the mailing list. Are there any objections to taking this course of action? Other comments? Thanks, Margaret _______________________________________________ Entmib mailing list Entmib@ietf.org https://www1.ietf.org/mailman/listinfo/entmib From entmib-bounces@ietf.org Sat Aug 7 10:46:49 2004 Received: from megatron.ietf.org (megatron.ietf.org [132.151.6.71]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA03862 for ; Sat, 7 Aug 2004 10:46:49 -0400 (EDT) Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1BtSNX-00017a-Q0; Sat, 07 Aug 2004 10:40:59 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1BtSM3-0000wk-Bp for entmib@megatron.ietf.org; Sat, 07 Aug 2004 10:39:27 -0400 Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA03530 for ; Sat, 7 Aug 2004 10:39:23 -0400 (EDT) Received: from mail.thingmagic.com ([207.31.248.245] helo=thingmagic.com) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1BtSPx-0004OD-6M for entmib@ietf.org; Sat, 07 Aug 2004 10:43:29 -0400 Received: from [68.64.253.86] (account margaret HELO [130.129.130.34]) by thingmagic.com (CommuniGate Pro SMTP 4.1.8) with ESMTP-TLS id 123856 for entmib@ietf.org; Sat, 07 Aug 2004 10:36:01 -0400 Mime-Version: 1.0 X-Sender: margaret@mail.thingmagic.com Message-Id: Date: Sat, 7 Aug 2004 00:00:11 -0400 To: entmib@ietf.org From: Margaret Wasserman Content-Type: text/plain; charset="us-ascii" ; format="flowed" X-Spam-Score: 0.8 (/) X-Scan-Signature: b19722fc8d3865b147c75ae2495625f2 Subject: [Entmib] CONSENSUS CHECK: Entity State MIB Completion X-BeenThere: entmib@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: IETF Entity MIB WG List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: entmib-bounces@ietf.org Errors-To: entmib-bounces@ietf.org During the Entity MIB WG meeting at IETF 60 in San Diego, we reviewed the 7 remaining issues with the Entity State MIB. There was consensus in the room on how to resolve each of these issues. The following list references issue numbers from http://rt.psg.com (userid: ietf, passwd: ietf). Issue 307 - Change the name to "unknown". Issue 311 - Date & time issue. We think that the IETF should make Juergen's proposed changes to the DateAndTime TC. The Entity State MIB will remain unchanged. Issue 322 - Sharon will add the Entity prefix to TCs. Issue 325 - Sharon will make the suggested OID changes. Issue 333 - Relationship to Alarm MIB. The Alarm MIB will be an informative reference. Issue 334 - No further changes required. Issue 354 - The word "report" will remain unchanged. The reference clauses citing X.731 will be removed and the reference to X.731 will be moved to Informative. We agreed that Sharon will make these changes, that we will briefly review the document on the list to ensure that these changes were properly made, and we will submit the document to the IESG for publication as a Proposed Standard. Does anyone disagree with this course of action? Other comments? Thanks, Margaret _______________________________________________ Entmib mailing list Entmib@ietf.org https://www1.ietf.org/mailman/listinfo/entmib From entmib-bounces@ietf.org Sat Aug 7 10:49:42 2004 Received: from megatron.ietf.org (megatron.ietf.org [132.151.6.71]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA04025 for ; Sat, 7 Aug 2004 10:49:42 -0400 (EDT) Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1BtSNX-00017f-Vi; Sat, 07 Aug 2004 10:40:59 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1BtSM3-0000wl-Bq for entmib@megatron.ietf.org; Sat, 07 Aug 2004 10:39:27 -0400 Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA03533 for ; Sat, 7 Aug 2004 10:39:23 -0400 (EDT) Received: from mail.thingmagic.com ([207.31.248.245] helo=thingmagic.com) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1BtSPx-0004OD-Hn for entmib@ietf.org; Sat, 07 Aug 2004 10:43:29 -0400 Received: from [68.64.253.86] (account margaret HELO [130.129.130.34]) by thingmagic.com (CommuniGate Pro SMTP 4.1.8) with ESMTP-TLS id 123858 for entmib@ietf.org; Sat, 07 Aug 2004 10:36:03 -0400 Mime-Version: 1.0 X-Sender: margaret@mail.thingmagic.com Message-Id: Date: Sat, 7 Aug 2004 00:04:18 -0400 To: entmib@ietf.org From: Margaret Wasserman Content-Type: text/plain; charset="us-ascii" ; format="flowed" X-Spam-Score: 0.8 (/) X-Scan-Signature: 08170828343bcf1325e4a0fb4584481c Subject: [Entmib] Status of the MIB formerly know as TCIF :-) X-BeenThere: entmib@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: IETF Entity MIB WG List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: entmib-bounces@ietf.org Errors-To: entmib-bounces@ietf.org During the Entity MIB WG meeting at IETF 60 in Seoul, we discussed the status of the Supplemental Entity MIB. We suggest that the name of this MIB be changed to something more descriptive. Entity MIB Extensions for Manufacturing was suggested. There was support for the idea that this MIB should be published as a sponsored individual submission. Dan Romascanu restated his willingness to review the document. Comments or discussion? Margaret _______________________________________________ Entmib mailing list Entmib@ietf.org https://www1.ietf.org/mailman/listinfo/entmib From entmib-bounces@ietf.org Sat Aug 7 10:50:47 2004 Received: from megatron.ietf.org (megatron.ietf.org [132.151.6.71]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA04099 for ; Sat, 7 Aug 2004 10:50:47 -0400 (EDT) Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1BtSNY-00017k-5G; Sat, 07 Aug 2004 10:41:00 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1BtSM3-0000wm-CM for entmib@megatron.ietf.org; Sat, 07 Aug 2004 10:39:27 -0400 Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA03536 for ; Sat, 7 Aug 2004 10:39:24 -0400 (EDT) Received: from mail.thingmagic.com ([207.31.248.245] helo=thingmagic.com) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1BtSPx-0004OD-Sk for entmib@ietf.org; Sat, 07 Aug 2004 10:43:30 -0400 Received: from [68.64.253.86] (account margaret HELO [130.129.130.34]) by thingmagic.com (CommuniGate Pro SMTP 4.1.8) with ESMTP-TLS id 123860 for entmib@ietf.org; Sat, 07 Aug 2004 10:36:05 -0400 Mime-Version: 1.0 X-Sender: margaret@mail.thingmagic.com Message-Id: Date: Sat, 7 Aug 2004 00:06:54 -0400 To: entmib@ietf.org From: Margaret Wasserman Content-Type: text/plain; charset="us-ascii" ; format="flowed" X-Spam-Score: 0.8 (/) X-Scan-Signature: 200d029292fbb60d25b263122ced50fc Subject: [Entmib] DRAFT Minutes from IETF 60 X-BeenThere: entmib@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: IETF Entity MIB WG List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: entmib-bounces@ietf.org Errors-To: entmib-bounces@ietf.org Here are my draft minutes from IETF 60. Thanks to David Perkins for the notes. Comments? Margaret Entity MIB (entmib) WG Minutes IETF 60, San Diego, CA ============================== CHAIR: Margaret Wasserman AGENDA: - Introduction and Agenda Bashing (5 min) - Status of the Entity MIB (5 min) - Wrapping up the Entity State MIB -- Sharon Chisholm (15 min) http://www.ietf.org/internet-drafts/draft-ietf-entmib-state-04.txt GOALS: Close all open issues and ship it! - Definitions of Supplemental Entity Managed Objects -- Kaj Tesink (20 min) http://www.ietf.org/internet-drafts/draft-tesink-entity-supplmib-00.txt GOALS: Technical review & decision about how/if to move forward - Future of the WG -- Margaret Wasserman (15 min) GOALS: Determine whether a WG recharter is needed - Wrap-up & Action Items (5 min) SUMMARY OF CONSENSUS ITEMS ========================== Consensus was reached in the room on the following items. These need to be confirmed on the mailing list. We will request that the Entity MIB document be removed from the IESG queue. We will undo the deprecation of the entAliasMapping identifer and resubmit the updated Entity MIB to the IESG for publication at PS. Sharon will update the Entity State MIB to correct the few minor issues discussed below, we will do a brief review on the list and submit the Entity State MIB for publication at PS. The WG recommends that the Supplemental Objects MIB module (formerly the TCIF MIB) should be handled as an AD sponsored individual submission. The expectation is that the Entity MIB WG will shut down as soon the Entity State MIB and the updated version of the Entity MIB have been approved by the IESG for publication at PS. STATUS OF THE ENTITY MIB ======================== The MIB is currently in IETF Last Call, ends Friday. Margaret needs to consolidate the implementation report and get it all onto the IETF web site, probably by moving it to a single web page. Sharon Chisholm has raised a Last Call issue regarding deprecation of the entAliasMapping Identifier. Ran Atkinson suggested that we might be on the brink of having a second implementation of this table and that it would be a shame to deprecate this object if that is the case. Most of the people in the room expressed concern that we would not have a way to map these two tables, requiring a product-specific work-around. [Note that the document editor, Andy Bierman, was not in the room.] There was a strong consensus in the room that we should pull back the document from the IESG and undo the deprecation of this object. Needs to be confirmed on the mailing list. There was also unanimous consensus in the room that if we do pull the document back and undo the deprecation, we should immediately re-submit the document for publication at PS. WRAPPING UP THE ENTITY STATE MIB ================================ The WG discussed each of the remaining seven issues with the Entity State MIB. See http://rt.iesg.com (userid: ietf, passwd: ietf) for more details about each issue. Conclusions: Issue 307 - Change the name to "unknown". Issue 311 - Date & time issue. We think that the IETF should make Juergen's proposed changes to the DateAndTime TC. The Entity State MIB will remain unchanged. Issue 322 - Sharon will add the Entity prefix to TCs. Issue 325 - Sharon will make the suggested OID changes. Issue 333 - Relationship to Alarm MIB. The Alarm MIB will be an informative reference. Issue 334 - No further changes required. Issue 354 - The word "report" will remain unchanged. The reference clauses citing X.731 will be removed and the reference to X.731 will be moved to Informative. Sharon will fix the remaining issues ASAP and we will submit the document to the IESG with the changes agreed above. DEFINITIONS OF SUPPLEMENTAL ENTITY MANAGED OBJECTS ================================================== Proposed new name: Entity MIB Extensions for Manufacturing and Alternative Identificaton. Kaj needs to write an I-D for URN for CLEI codes. Originally, David Perkins was going to do this, but they recently agreed that Kaj would do it. Plan is to make the changes proposed (new name and change object to URN), get the document well reviewed by Dan, discuss on the Entity MIB mailing list as necessary and publish as an individual submission. FUTURE OF THE WG ================ Margaret shared her expectation that the WG will shut down after the Entity State MIB has been approved by the IESG. If others believe that there is more work to do in this WG, they should talk to Bert Wijnen, the Area Director, about how to continue this work. _______________________________________________ Entmib mailing list Entmib@ietf.org https://www1.ietf.org/mailman/listinfo/entmib From entmib-bounces@ietf.org Sun Aug 15 18:00:06 2004 Received: from megatron.ietf.org (megatron.ietf.org [132.151.6.71]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA21929 for ; Sun, 15 Aug 2004 18:00:06 -0400 (EDT) Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1BwT0U-0000jt-IZ; Sun, 15 Aug 2004 17:57:38 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1BwSxo-0000WC-1K for entmib@megatron.ietf.org; Sun, 15 Aug 2004 17:54:52 -0400 Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA21686 for ; Sun, 15 Aug 2004 17:54:48 -0400 (EDT) Received: from ihemail2.lucent.com ([192.11.222.163]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1BwT3S-00034C-It for entmib@ietf.org; Sun, 15 Aug 2004 18:00:43 -0400 Received: from nl0006exch001h.wins.lucent.com (h135-85-76-62.lucent.com [135.85.76.62]) by ihemail2.lucent.com (8.12.11/8.12.11) with ESMTP id i7FLsHHS010045 for ; Sun, 15 Aug 2004 16:54:18 -0500 (CDT) Received: by nl0006exch001h.nl.lucent.com with Internet Mail Service (5.5.2657.72) id ; Sun, 15 Aug 2004 23:54:17 +0200 Message-ID: <7D5D48D2CAA3D84C813F5B154F43B15504F2A8A4@nl0006exch001u.nl.lucent.com> From: "Wijnen, Bert (Bert)" To: "Entmib-wg (E-mail)" Date: Sun, 15 Aug 2004 23:54:15 +0200 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.2657.72) Content-Type: text/plain X-Spam-Score: 0.0 (/) X-Scan-Signature: 9182cfff02fae4f1b6e9349e01d62f32 Subject: [Entmib] FW: I-D was expired X-BeenThere: entmib@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: IETF Entity MIB WG List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: entmib-bounces@ietf.org Errors-To: entmib-bounces@ietf.org Since the WG chair asked me to withdraw this document from the IESG table, I put it back to the WG and marked it "AD is watching" in the I-D tracker. As a result it expired. But a new revision was/is needed anyway as a result of the changed target (PS instead of DS, with fewer items deprecated) since IETF60 meeting. Thanks, Bert -----Original Message----- From: I-D Expiring System [mailto:ietf-secretariat-reply@ietf.org] Sent: vrijdag 13 augustus 2004 06:05 To: Bert Wijnen Subject: I-D was expired draft-ietf-entmib-v3-04.txt was just expired. This I-D is in 'AD watching' state in ID Tracker. Thanks, IETF Secretariat. _______________________________________________ Entmib mailing list Entmib@ietf.org https://www1.ietf.org/mailman/listinfo/entmib From entmib-bounces@ietf.org Mon Aug 16 04:29:04 2004 Received: from megatron.ietf.org (megatron.ietf.org [132.151.6.71]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id EAA17427 for ; Mon, 16 Aug 2004 04:29:04 -0400 (EDT) Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1Bwcq5-0005KL-Ni; Mon, 16 Aug 2004 04:27:33 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1BwckB-0004Zi-Vz for entmib@megatron.ietf.org; Mon, 16 Aug 2004 04:21:28 -0400 Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id EAA16550 for ; Mon, 16 Aug 2004 04:21:26 -0400 (EDT) Received: from hermes.iu-bremen.de ([212.201.44.23]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1Bwcpw-0004ON-2A for entmib@ietf.org; Mon, 16 Aug 2004 04:27:25 -0400 Received: from localhost (demetrius.iu-bremen.de [212.201.44.32]) by hermes.iu-bremen.de (Postfix) with ESMTP id AA5346AAA; Mon, 16 Aug 2004 10:20:54 +0200 (CEST) Received: from hermes.iu-bremen.de ([212.201.44.23]) by localhost (demetrius [212.201.44.32]) (amavisd-new, port 10024) with ESMTP id 25706-02; Mon, 16 Aug 2004 10:20:53 +0200 (CEST) Received: from james.eecs.iu-bremen.de (unknown [212.201.47.66]) by hermes.iu-bremen.de (Postfix) with ESMTP id D88BD6A09; Mon, 16 Aug 2004 10:20:53 +0200 (CEST) Received: by james.eecs.iu-bremen.de (Postfix, from userid 1000) id E18ED82EA; Mon, 16 Aug 2004 10:20:53 +0200 (CEST) Date: Mon, 16 Aug 2004 10:20:53 +0200 From: Juergen Schoenwaelder To: Margaret Wasserman Subject: Re: [Entmib] CONSENSUS CHECK: Undo entAliasMapping deprecation Message-ID: <20040816082053.GD1761@iu-bremen.de> Mail-Followup-To: Margaret Wasserman , entmib@ietf.org References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.6+20040722i X-Virus-Scanned: by amavisd-new 20030616p5 at demetrius.iu-bremen.de X-Spam-Score: 0.0 (/) X-Scan-Signature: 9466e0365fc95844abaf7c3f15a05c7d Cc: entmib@ietf.org X-BeenThere: entmib@ietf.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: j.schoenwaelder@iu-bremen.de List-Id: IETF Entity MIB WG List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: entmib-bounces@ietf.org Errors-To: entmib-bounces@ietf.org On Fri, Aug 06, 2004 at 11:41:02PM -0400, Margaret Wasserman wrote: > During the Entity MIB meeting at IETF 60 in San Diego, there was > consensus in the room for the following course of action: > > (1) Pull the Entity State MIB document out of IESG processing > (currently submitted for publication as a Draft Standard) > > (2) Update the document to undo the deprecation of the > entAliasMapping identifier, and > > (3) Re-submit the Entity MIB to the IESG for publication as a > Proposed Standard. > > We now need to confirm this consensus on the mailing list. Are there > any objections to taking this course of action? Other comments? Sounds like a good plan to me. But if we recycle at Proposed, why do we then not simply put the entSupplPhysicalManufacturingDate and the entSupplPhysicalManufacturerInfo objects into the entPhysicalEntry where they actually belong? A new compliance statement would deal with these additions so existing implementations that comply to entity2Compliance would not be affected. /js -- Juergen Schoenwaelder International University Bremen P.O. Box 750 561, 28725 Bremen, Germany _______________________________________________ Entmib mailing list Entmib@ietf.org https://www1.ietf.org/mailman/listinfo/entmib From entmib-bounces@ietf.org Mon Aug 16 10:06:37 2004 Received: from megatron.ietf.org (megatron.ietf.org [132.151.6.71]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA05251 for ; Mon, 16 Aug 2004 10:06:36 -0400 (EDT) Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1Bwi6H-0002jl-2r; Mon, 16 Aug 2004 10:04:37 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1Bwi3v-0001kY-Py for entmib@megatron.ietf.org; Mon, 16 Aug 2004 10:02:12 -0400 Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA04939 for ; Mon, 16 Aug 2004 10:02:09 -0400 (EDT) Received: from thumper.research.telcordia.com ([128.96.41.1]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1Bwi9c-0001qQ-MR for entmib@ietf.org; Mon, 16 Aug 2004 10:08:12 -0400 Received: from shannon.research.telcordia.com (shannon-83.research.telcordia.com [128.96.83.11]) by thumper.research.telcordia.com (8.12.9/8.12.9) with ESMTP id i7GE1R5C008420; Mon, 16 Aug 2004 10:01:27 -0400 (EDT) Received: from kaj-100.research.telcordia.com (kaj-100.cc.telcordia.com [128.96.171.145]) by shannon.research.telcordia.com (8.9.3/8.9.3) with ESMTP id KAA24191; Mon, 16 Aug 2004 10:01:27 -0400 (EDT) Message-Id: <4.3.2.7.2.20040816095956.0270d640@128.96.81.11> X-Sender: kaj@128.96.81.11 X-Mailer: QUALCOMM Windows Eudora Version 4.3.2 Date: Mon, 16 Aug 2004 10:01:41 -0400 To: j.schoenwaelder@iu-bremen.de, Margaret Wasserman From: Kaj Tesink Subject: Re: [Entmib] CONSENSUS CHECK: Undo entAliasMapping deprecation In-Reply-To: <20040816082053.GD1761@iu-bremen.de> References: Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii"; format=flowed X-Spam-Score: 0.0 (/) X-Scan-Signature: f4c2cf0bccc868e4cc88dace71fb3f44 Cc: entmib@ietf.org X-BeenThere: entmib@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: IETF Entity MIB WG List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: entmib-bounces@ietf.org Errors-To: entmib-bounces@ietf.org At 10:20 AM 8/16/2004 +0200, Juergen Schoenwaelder wrote: >On Fri, Aug 06, 2004 at 11:41:02PM -0400, Margaret Wasserman wrote: > > > During the Entity MIB meeting at IETF 60 in San Diego, there was > > consensus in the room for the following course of action: > > > > (1) Pull the Entity State MIB document out of IESG processing > > (currently submitted for publication as a Draft Standard) > > > > (2) Update the document to undo the deprecation of the > > entAliasMapping identifier, and > > > > (3) Re-submit the Entity MIB to the IESG for publication as a > > Proposed Standard. > > > > We now need to confirm this consensus on the mailing list. Are there > > any objections to taking this course of action? Other comments? > >Sounds like a good plan to me. But if we recycle at Proposed, why do >we then not simply put the entSupplPhysicalManufacturingDate and the >entSupplPhysicalManufacturerInfo objects into the entPhysicalEntry >where they actually belong? A new compliance statement would deal >with these additions so existing implementations that comply to >entity2Compliance would not be affected. juergen, thanks for pointing this out. makes a lot of sense & would work for me. kaj >/js > >-- >Juergen Schoenwaelder International University Bremen > P.O. Box 750 561, 28725 Bremen, Germany > >_______________________________________________ >Entmib mailing list >Entmib@ietf.org >https://www1.ietf.org/mailman/listinfo/entmib _/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/ REACH INFO HAS CHANGED; NEW INFO PER 7/19/04: _/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/ Kaj Tesink Telcordia Technologies. Inc. 1 Telcordia Drive Piscataway, NJ 08854-3923 Email: kaj@research.telcordia.com Tel: (732) 699-6068 Fax: (732) 336-2336 _/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/ _______________________________________________ Entmib mailing list Entmib@ietf.org https://www1.ietf.org/mailman/listinfo/entmib From entmib-bounces@ietf.org Mon Aug 16 13:00:32 2004 Received: from megatron.ietf.org (megatron.ietf.org [132.151.6.71]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA15362 for ; Mon, 16 Aug 2004 13:00:32 -0400 (EDT) Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1Bwko3-0000VQ-M9; Mon, 16 Aug 2004 12:57:59 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1Bwkk1-0008WP-8P for entmib@megatron.ietf.org; Mon, 16 Aug 2004 12:53:49 -0400 Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA15102 for ; Mon, 16 Aug 2004 12:53:46 -0400 (EDT) Received: from shell4.bayarea.net ([209.128.82.1]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1Bwkpp-0004ZX-QA for entmib@ietf.org; Mon, 16 Aug 2004 12:59:51 -0400 Received: from NB5.dsperkins.com (shell4.bayarea.net [209.128.82.1]) (authenticated bits=0) by shell4.bayarea.net (8.12.11/8.12.11) with ESMTP id i7GGrbfW009978; Mon, 16 Aug 2004 09:53:38 -0700 Message-Id: <5.2.0.9.2.20040816094625.022f49c0@127.0.0.1> X-Sender: dperkins@127.0.0.1 X-Mailer: QUALCOMM Windows Eudora Version 5.2.0.9 Date: Mon, 16 Aug 2004 09:53:38 -0700 To: j.schoenwaelder@iu-bremen.de, Margaret Wasserman From: "David T. Perkins" Subject: Re: [Entmib] CONSENSUS CHECK: Undo entAliasMapping deprecation In-Reply-To: <20040816082053.GD1761@iu-bremen.de> References: Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" X-Spam-Score: 0.0 (/) X-Scan-Signature: b19722fc8d3865b147c75ae2495625f2 Cc: entmib@ietf.org X-BeenThere: entmib@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: IETF Entity MIB WG List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: entmib-bounces@ietf.org Errors-To: entmib-bounces@ietf.org HI, The below sounds like a good suggestion to me. At 10:20 AM 8/16/2004 +0200, Juergen Schoenwaelder wrote: >On Fri, Aug 06, 2004 at 11:41:02PM -0400, Margaret Wasserman wrote: > >> During the Entity MIB meeting at IETF 60 in San Diego, there was >> consensus in the room for the following course of action: >> >> (1) Pull the Entity State MIB document out of IESG processing >> (currently submitted for publication as a Draft Standard) >> >> (2) Update the document to undo the deprecation of the >> entAliasMapping identifier, and >> >> (3) Re-submit the Entity MIB to the IESG for publication as a >> Proposed Standard. >> >> We now need to confirm this consensus on the mailing list. Are there >> any objections to taking this course of action? Other comments? > >Sounds like a good plan to me. But if we recycle at Proposed, why do >we then not simply put the entSupplPhysicalManufacturingDate and the >entSupplPhysicalManufacturerInfo objects into the entPhysicalEntry >where they actually belong? A new compliance statement would deal >with these additions so existing implementations that comply to >entity2Compliance would not be affected. > >/js Regards, /david t. perkins _______________________________________________ Entmib mailing list Entmib@ietf.org https://www1.ietf.org/mailman/listinfo/entmib From entmib-bounces@ietf.org Tue Aug 17 14:25:17 2004 Received: from megatron.ietf.org (megatron.ietf.org [132.151.6.71]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA04921 for ; Tue, 17 Aug 2004 14:25:17 -0400 (EDT) Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1Bx8Rk-0003ms-Fl; Tue, 17 Aug 2004 14:12:32 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1Bx8Lf-0002hW-HO for entmib@megatron.ietf.org; Tue, 17 Aug 2004 14:06:15 -0400 Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA04082 for ; Tue, 17 Aug 2004 14:06:13 -0400 (EDT) Received: from shell4.bayarea.net ([209.128.82.1]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1Bx8Rh-000145-KU for entmib@ietf.org; Tue, 17 Aug 2004 14:12:31 -0400 Received: from shell4.bayarea.net (localhost [127.0.0.1]) by shell4.bayarea.net (8.12.11/8.12.11) with ESMTP id i7HI6Aj5022193 for ; Tue, 17 Aug 2004 11:06:10 -0700 Received: from localhost (heard@localhost) by shell4.bayarea.net (8.12.11/8.12.11/Submit) with ESMTP id i7HI6AkT022189 for ; Tue, 17 Aug 2004 11:06:10 -0700 X-Authentication-Warning: shell4.bayarea.net: heard owned process doing -bs Date: Tue, 17 Aug 2004 11:06:10 -0700 (PDT) From: "C. M. Heard" X-Sender: heard@shell4.bayarea.net To: entmib@ietf.org Subject: Re: [Entmib] CONSENSUS CHECK: Undo entAliasMapping deprecation In-Reply-To: <20040816082053.GD1761@iu-bremen.de> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Spam-Score: 0.0 (/) X-Scan-Signature: 9466e0365fc95844abaf7c3f15a05c7d X-BeenThere: entmib@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: IETF Entity MIB WG List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: entmib-bounces@ietf.org Errors-To: entmib-bounces@ietf.org On Mon, 16 Aug 2004, Juergen Schoenwaelder wrote: > On Fri, Aug 06, 2004 at 11:41:02PM -0400, Margaret Wasserman wrote: > > > During the Entity MIB meeting at IETF 60 in San Diego, there was > > consensus in the room for the following course of action: > > > > (1) Pull the Entity State MIB document out of IESG processing > > (currently submitted for publication as a Draft Standard) > > > > (2) Update the document to undo the deprecation of the > > entAliasMapping identifier, and > > > > (3) Re-submit the Entity MIB to the IESG for publication as a > > Proposed Standard. > > > > We now need to confirm this consensus on the mailing list. Are there > > any objections to taking this course of action? Other comments? > > Sounds like a good plan to me. But if we recycle at Proposed, why do > we then not simply put the entSupplPhysicalManufacturingDate and the > entSupplPhysicalManufacturerInfo objects into the entPhysicalEntry > where they actually belong? A new compliance statement would deal > with these additions so existing implementations that comply to > entity2Compliance would not be affected. Let me add my voice to those supporting this idea. Mike Heard _______________________________________________ Entmib mailing list Entmib@ietf.org https://www1.ietf.org/mailman/listinfo/entmib From entmib-bounces@ietf.org Tue Aug 17 17:46:06 2004 Received: from megatron.ietf.org (megatron.ietf.org [132.151.6.71]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA16637 for ; Tue, 17 Aug 2004 17:46:06 -0400 (EDT) Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1BxBeE-0000sz-Nt; Tue, 17 Aug 2004 17:37:38 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1BxBYp-0007p0-Hf for entmib@megatron.ietf.org; Tue, 17 Aug 2004 17:32:03 -0400 Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA15556 for ; Tue, 17 Aug 2004 17:32:00 -0400 (EDT) Received: from thumper.research.telcordia.com ([128.96.41.1]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1BxBem-0004iF-41 for entmib@ietf.org; Tue, 17 Aug 2004 17:38:21 -0400 Received: from shannon.research.telcordia.com (shannon-83.research.telcordia.com [128.96.83.11]) by thumper.research.telcordia.com (8.12.9/8.12.9) with ESMTP id i7HLVI5C012356 for ; Tue, 17 Aug 2004 17:31:18 -0400 (EDT) Received: from kaj-100.research.telcordia.com (kaj-100.cc.telcordia.com [128.96.171.145]) by shannon.research.telcordia.com (8.9.3/8.9.3) with ESMTP id RAA25264 for ; Tue, 17 Aug 2004 17:31:17 -0400 (EDT) Message-Id: <4.3.2.7.2.20040817172040.026f8378@128.96.81.11> X-Sender: kaj@128.96.81.11 X-Mailer: QUALCOMM Windows Eudora Version 4.3.2 Date: Tue, 17 Aug 2004 17:31:24 -0400 To: entmib@ietf.org From: Kaj Tesink Subject: Re: [Entmib] CONSENSUS CHECK: Undo entAliasMapping deprecation In-Reply-To: <5.2.0.9.2.20040816094625.022f49c0@127.0.0.1> References: <20040816082053.GD1761@iu-bremen.de> Mime-Version: 1.0 Content-Type: multipart/mixed; boundary="=====================_-1772244533==_" X-Spam-Score: 0.0 (/) X-Scan-Signature: 0a0a359c89658364740632bd00d43825 X-BeenThere: entmib@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: IETF Entity MIB WG List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: entmib-bounces@ietf.org Errors-To: entmib-bounces@ietf.org --=====================_-1772244533==_ Content-Type: text/plain; charset="us-ascii"; format=flowed i've attached an update of the entity supplemental miblet. the updates concern: - change of the title - inclusion of Juergen's suggested URN text & object - reference to a to be published rfc for CLEI URN namespace further actions: - as per the emerging consensus, it is better to insert the two objects in the entPhysicalEntry of the entity mib itself; in that case all that is needed is to cut&paste from the attached - we'll post the draft for the for CLEI URN namespace request soon - any other comments? kaj At 09:53 AM 8/16/2004 -0700, David T. Perkins wrote: >HI, > >The below sounds like a good suggestion to me. > >At 10:20 AM 8/16/2004 +0200, Juergen Schoenwaelder wrote: > >On Fri, Aug 06, 2004 at 11:41:02PM -0400, Margaret Wasserman wrote: > > > >> During the Entity MIB meeting at IETF 60 in San Diego, there was > >> consensus in the room for the following course of action: > >> > >> (1) Pull the Entity State MIB document out of IESG processing > >> (currently submitted for publication as a Draft Standard) > >> > >> (2) Update the document to undo the deprecation of the > >> entAliasMapping identifier, and > >> > >> (3) Re-submit the Entity MIB to the IESG for publication as a > >> Proposed Standard. > >> > >> We now need to confirm this consensus on the mailing list. Are there > >> any objections to taking this course of action? Other comments? > > > >Sounds like a good plan to me. But if we recycle at Proposed, why do > >we then not simply put the entSupplPhysicalManufacturingDate and the > >entSupplPhysicalManufacturerInfo objects into the entPhysicalEntry > >where they actually belong? A new compliance statement would deal > >with these additions so existing implementations that comply to > >entity2Compliance would not be affected. > > > >/js >Regards, >/david t. perkins > > >_______________________________________________ >Entmib mailing list >Entmib@ietf.org >https://www1.ietf.org/mailman/listinfo/entmib --=====================_-1772244533==_ Content-Type: text/plain; charset="us-ascii" Content-Disposition: attachment; filename="entitysuppl.rfc" INTERNET DRAFT Kaj Tesink Telcordia Technologies August 16, 2004 Definitions of Entity Manufacturing and URN Managed Objects Status of this Memo This document is an Internet-Draft and is in full conformance with all provisions of Section 10 of RFC2026. Internet-Drafts are working documents of the Internet Engineering Task Force (IETF), its areas, and its working groups. Note that other groups may also distribute working documents as Internet-Drafts. Internet-Drafts are draft documents valid for a maximum of six months and may be updated, replaced, or obsoleted by other documents at any time. It is inappropriate to use Internet-Drafts as reference material or to cite them other than as "work in progress." The list of current Internet-Drafts can be accessed at http://www.ietf.org/ietf/1id-abstracts.txt The list of Internet-Draft Shadow Directories can be accessed at http://www.ietf.org/shadow.html Copyright Notice Copyright (C) The Internet Society (2004). All Rights Reserved. Abstract This document defines a portion of the Management Information Base (MIB) for use with network management protocols in TCP/IP based internets. In particular, it describes additional objects that supplement those defined in the Definitions of Managed Objects for the Entity MIB document [RFCzzzz]. Expires 02/16/2005Entity Manufacturing and URN Objects [Page 1] Internet Draft 08/16/2004 Table of Contents 1 Conventions ............................................... 3 2 The Internet-Standard Management Framework ................ 3 3 Overview .................................................. 3 3.1 entSupplPhysicalManufacturingDate ....................... 3 3.2 entSupplPhysicalUris .................................... 3 4 Object Definitions ........................................ 5 5 Intellectual Property ..................................... 9 6 Acknowledgments ........................................... 9 7 Security Considerations ................................... 10 8 References ................................................ 11 8.1 Normative References .................................... 11 8.2 Informative References .................................. 11 9 Author's Address .......................................... 11 Full Copyright Statement ................................... 11 Expires 02/16/2005Entity Manufacturing and URN Objects [Page 2] Internet Draft 08/16/2004 1. Conventions The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", "SHOULD", "SHOULD NOT", "RECOMMENDED", "NOT RECOMMENDED", "MAY", and "OPTIONAL", when they appear in this document, are to be interpreted as described in RFC 2119 [RFC2119]. 2. The Internet-Standard Management Framework For a detailed overview of the documents that describe the current Internet-Standard Management Framework, please refer to section 7 of RFC 3410 [RFC3410]. Managed objects are accessed via a virtual information store, termed the Management Information Base or MIB. MIB objects are generally accessed through the Simple Network Management Protocol (SNMP). Objects in the MIB are defined using the mechanisms defined in the Structure of Management Information (SMI). This memo specifies a MIB module that is compliant to the SMIv2, which is described in STD 58, RFC 2578 [RFC2578], STD 58, RFC 2579 [RFC2579] and STD 58, RFC 2580 [RFC2580]. 3. Overview The objects defined in this memo are used in conjunction with objects defined in the Entity MIB [RFCzzzz]. The MIB module defined in this memo is a sparse augmentation of the entPhysicalTable of the ENTITY- MIB -- i.e., it is REQUIRED that an agent implementing objects defined in this memo also implement the relevant ENTITY-MIB objects. The purpose of the augmentation of the entPhysicalTable is to define a managed object for the manufacturing date of a managed entity, and a managed object to support additional information related to the managed entity. 3.1. entSupplPhysicalManufacturingDate This object contains the date of manufacturing of the managed entity. If the manufacturing date is unknown or not supported the object is not instantiated. 3.2. entSupplPhysicalUris This object provides additional identification information about the physical entity. This object may be used to encode for example a URI containing a Common Language Equipment Identifier (CLEI) URI [RFCwwww] for the managed physical entity. If no additional identification information is known or supported about the physical Expires 02/16/2005Entity Manufacturing and URN Objects [Page 3] Internet Draft 08/16/2004 entity the object is not instantiated. Expires 02/16/2005Entity Manufacturing and URN Objects [Page 4] Internet Draft 08/16/2004 4. Object Definitions ENTSUPPL-MIB DEFINITIONS ::= BEGIN IMPORTS MODULE-IDENTITY, OBJECT-TYPE, transmission FROM SNMPv2-SMI DateAndTime FROM SNMPv2-TC MODULE-COMPLIANCE, OBJECT-GROUP FROM SNMPv2-CONF entPhysicalIndex FROM ENTITY-MIB; entitySupplMIB MODULE-IDENTITY LAST-UPDATED "200408160000Z" -- August 16, 2004 ORGANIZATION "IETF Entity MIB Working Group" CONTACT-INFO "WG charter: http://www.ietf.org/html.charters/entmib-charter.html Mailing Lists: General Discussion: entmib@ietf.org To Subscribe: http://www.ietf.org/mailman/listinfo/entmib Chair: Margaret Wasserman Postal: Tel: E-mail: margaret@thingmagic.com Author: Kaj Tesink Postal: One Telcordia Drive Piscataway, NJ 08854 USA Tel: +1 732-699-6068 E-mail: kaj@research.telcordia.com" Expires 02/16/2005Entity Manufacturing and URN Objects [Page 5] Internet Draft 08/16/2004 DESCRIPTION "The objects in this MIB module are used in conjunction with objects in the ENTITY-MIB to manage entities Copyright (C) The Internet Society (2004). This version of this MIB module is part of RFC yyyy; see the RFC itself for full legal notices." -- RFC Ed.: replace yyyy with actual RFC number & remove this notice REVISION "200408160000Z " -- August 16, 2004 DESCRIPTION "Initial version, published as RFC yyyy." -- RFC Ed.: replace yyyy with actual RFC number & remove this notice ::= { transmission XXX } -- RFC Ed.: replace XXX with IANA-assigned number & remove this notice Expires 02/16/2005Entity Manufacturing and URN Objects [Page 6] Internet Draft 08/16/2004 -- The main sections of the module entitySupplObjects OBJECT IDENTIFIER ::= { entitySupplMIB 1 } entitySupplConformance OBJECT IDENTIFIER ::= { entitySupplMIB 2 } -- These objects provide extensions to the entPhysicalTable. entSupplPhysicalTable OBJECT-TYPE SYNTAX SEQUENCE OF EntSupplPhysicalEntry MAX-ACCESS not-accessible STATUS current DESCRIPTION "The table for supplementary objects to the entPhysicalTable." ::= { entitySupplObjects 1 } entSupplPhysicalEntry OBJECT-TYPE SYNTAX EntSupplPhysicalEntry MAX-ACCESS not-accessible STATUS current DESCRIPTION "An entry in the entSupplPhysicalTable. For each instance of this object there MUST be a corresponding instance of entPhysicalEntry." INDEX { entPhysicalIndex } ::= { entSupplPhysicalTable 1 } EntSupplPhysicalEntry ::= SEQUENCE { entSupplPhysicalManufacturingDate DateAndTime, entSupplPhysicalUris OCTET STRING } entSupplPhysicalManufacturingDate OBJECT-TYPE SYNTAX DateAndTime MAX-ACCESS read-only STATUS current DESCRIPTION "The manufacturing date for the physical entity." ::= { entSupplPhysicalEntry 1 } entSupplPhysicalUris OBJECT-TYPE SYNTAX DisplayString MAX-ACCESS read-write STATUS current Expires 02/16/2005Entity Manufacturing and URN Objects [Page 7] Internet Draft 08/16/2004 DESCRIPTION "This object contains additional identification information about the physical entity. The object contains URIs and therefore the syntax of this object must conform to RFC 2396 section 2. Multiple URIs may be separated by white space characters." ::= { entSupplPhysicalEntry 2 } -- -- Conformance Statements -- entitySupplGroups OBJECT IDENTIFIER ::= { entitySupplConformance 1 } entitySupplCompliances OBJECT IDENTIFIER ::= { entitySupplConformance 2 } -- Object Groups entitySupplPhysicalGroup OBJECT-GROUP OBJECTS { entSupplPhysicalManufacturingDate, entSupplPhysicalUris } STATUS current DESCRIPTION "A collection of supplemental objects for to support physical entity features." ::= { entitySupplGroups 1 } -- Compliance Statements entitySupplCompliance MODULE-COMPLIANCE STATUS current DESCRIPTION "The compliance statement for entities that support this module. Compliance with the entity3Compliance statement of the ENTITY-MIB is prerequisite." MODULE -- this module MANDATORY-GROUPS { entitySupplPhysicalGroup } OBJECT entSupplPhysicalUris MIN-ACCESS read-only Expires 02/16/2005Entity Manufacturing and URN Objects [Page 8] Internet Draft 08/16/2004 DESCRIPTION "Write access is not required." ::= { entitySupplCompliances 1 } END 5. Intellectual Property The IETF takes no position regarding the validity or scope of any intellectual property or other rights that might be claimed to pertain to the implementation or use of the technology described in this document or the extent to which any license under such rights might or might not be available; neither does it represent that it has made any effort to identify any such rights. Information on the IETF's procedures with respect to rights in standards-track and standards-related documentation can be found in BCP-11. Copies of claims of rights made available for publication and any assurances of licenses to be made available, or the result of an attempt made to obtain a general license or permission for the use of such proprietary rights by implementors or users of this specification can be obtained from the IETF Secretariat. The IETF invites any interested party to bring to its attention any copyrights, patents or patent applications, or other proprietary rights which may cover technology that may be required to practice this standard. Please address the information to the IETF Executive Director. 6. Acknowledgments The contributions of the Entity MIB Working Group members are gratefully acknowledged. Special thanks go to Mike Heard, Juergen Schoenwaelder, Dave Perkins and Dan Romascanu. Expires 02/16/2005Entity Manufacturing and URN Objects [Page 9] Internet Draft 08/16/2004 7. Security Considerations entSupplPhysicalInfo defined in this MIB module has a MAX-ACCESS clause of read-write; erroreous or unauthorized Writing of this object will result in the provision of misleading information to network management systems. The user of this MIB module must therefore be aware that support for SET operations in a non-secure environment without proper protection can have a negative effect on network operations. The readable objects in this MIB module (i.e., those with MAX-ACCESS other than not-accessible) may be considered sensitive in some environments since, collectively, they provide information about the managed entities and can reveal some aspects of their configuration. In such environments it is important to control even GET and NOTIFY access to these objects and possibly even to encrypt their values when sending them over the network via SNMP. SNMP versions prior to SNMPv3 did not include adequate security. Even if the network itself is secure (for example by using IPSec), even then, there is no control as to who on the secure network is allowed to access and GET/SET (read/change/create/delete) the objects in this MIB module. It is RECOMMENDED that implementers consider the security features as provided by the SNMPv3 framework (see [RFC3410], section 8), including full support for the SNMPv3 cryptographic mechanisms (for authentication and privacy). Further, deployment of SNMP versions prior to SNMPv3 is NOT RECOMMENDED. Instead, it is RECOMMENDED to deploy SNMPv3 and to enable cryptographic security. It is then a customer/operator responsibility to ensure that the SNMP entity giving access to an instance of this MIB module is properly configured to give access to the objects only to those principals (users) that have legitimate rights to indeed GET or SET (change/create/delete) them. Expires 02/16/2005Entity Manufacturing and URN Objects [Page 10] Internet Draft 08/16/2004 8. References 8.1. Normative References [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate Requirements Levels", BCP 14, RFC 2119, March 1997. [RFC2578] McCloghrie, K., Perkins, D., Schoenwaelder, J., Case, J., Rose, M. and S. Waldbusser, "Structure of Management Information Version 2 (SMIv2)", STD 58, RFC 2578, April 1999. [RFC2579] McCloghrie, K., Perkins, D., Schoenwaelder, J., Case, J., Rose, M. and S. Waldbusser, "Textual Conventions for SMIv2", STD 58, RFC 2579, April 1999. [RFC2580] McCloghrie, K., Perkins, D., Schoenwaelder, J., Case, J., Rose, M. and S. Waldbusser, "Conformance Statements for SMIv2", STD 58, RFC 2580, April 1999. [RFCzzzz] Bierman, A., McCloghrie, K., "Entity MIB (Version 3)", RFCzzzz. 8.2. Informative References [RFC3410] Case, J., Mundy, R., Partain, D. and B. Stewart, "Introduction and Applicability Statements for Internet- Standard Management Framework", RFC 3410, December 2002. [RFCwwww] Tesink, K., Robert H. Fox, "A Uniform Resource Name (URN) Namespace for the CLEI Code", RFC wwww, August 2004. 9. Author's Address Kaj Tesink One Telcordia Drive Piscataway, NJ 08854 USA Phone: +1 732 699-6068 EMail: kaj@research.telcordia.com Full Copyright Statement Copyright (C) The Internet Society (2004). All Rights Reserved. This document and translations of it may be copied and furnished to others, and derivative works that comment on or otherwise explain it Expires 02/16/2005Entity Manufacturing and URN Objects [Page 11] Internet Draft 08/16/2004 or assist in its implementation may be prepared, copied, published and distributed, in whole or in part, without restriction of any kind, provided that the above copyright notice and this paragraph are included on all such copies and derivative works. However, this document itself may not be modified in any way, such as by removing the copyright notice or references to the Internet Society or other Internet organizations, except as needed for the purpose of developing Internet standards in which case the procedures for copyrights defined in the Internet Standards process must be followed, or as required to translate it into languages other than English. The limited permissions granted above are perpetual and will not be revoked by the Internet Society or its successors or assigns. This document and the information contained herein is provided on an "AS IS" basis and THE INTERNET SOCIETY AND THE INTERNET ENGINEERING TASK FORCE DISCLAIMS ALL WARRANTIES, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE INFORMATION HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE. Expires 02/16/2005Entity Manufacturing and URN Objects [Page 12] Internet Draft 08/16/2004 ************************************************************ * NOTES TO RFC Editor (to be removed prior to publication) * * * * 1.) The normative references [RFCwwww] and [RFCzzzz] * * must be updated to point to the appropriate * * RFC when the corresponding Internet Draft is published, * * and all occurrences of the reference tags must be * * changed. * * * * 2.) Please replace all occurrences of "yyyy" in the * * DESCRIPTION clause of the MODULE-IDENTITY invocation * * in Section 4 with the RFC number assigned to this * * specification and remove the accompanying notes. * * * * 3.) Please replace "XXX" in the MODULE-IDENTITY value * * with an IANA-assigned value under the 'transmission' * * subtree and remove the accompanying note. * * * ************************************************************ Expires 02/16/2005Entity Manufacturing and URN Objects [Page 13] --=====================_-1772244533==_ Content-Type: text/plain; charset="us-ascii"; format=flowed _/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/ REACH INFO HAS CHANGED; NEW INFO PER 7/19/04: _/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/ Kaj Tesink Telcordia Technologies. Inc. 1 Telcordia Drive Piscataway, NJ 08854-3923 Email: kaj@research.telcordia.com Tel: (732) 699-6068 Fax: (732) 336-2336 _/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/ --=====================_-1772244533==_ Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Disposition: inline Content-Transfer-Encoding: 7bit _______________________________________________ Entmib mailing list Entmib@ietf.org https://www1.ietf.org/mailman/listinfo/entmib --=====================_-1772244533==_-- From entmib-bounces@ietf.org Wed Aug 18 04:37:49 2004 Received: from megatron.ietf.org (megatron.ietf.org [132.151.6.71]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id EAA18244 for ; Wed, 18 Aug 2004 04:37:49 -0400 (EDT) Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1BxLwG-0005Gp-Kf; Wed, 18 Aug 2004 04:36:56 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1BxLsQ-0004t5-WD for entmib@megatron.ietf.org; Wed, 18 Aug 2004 04:32:59 -0400 Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id EAA17994 for ; Wed, 18 Aug 2004 04:32:57 -0400 (EDT) Received: from hermes.iu-bremen.de ([212.201.44.23]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1BxLya-0007jp-SA for entmib@ietf.org; Wed, 18 Aug 2004 04:39:22 -0400 Received: from localhost (demetrius.iu-bremen.de [212.201.44.32]) by hermes.iu-bremen.de (Postfix) with ESMTP id 2CF855E39; Wed, 18 Aug 2004 10:32:25 +0200 (CEST) Received: from hermes.iu-bremen.de ([212.201.44.23]) by localhost (demetrius [212.201.44.32]) (amavisd-new, port 10024) with ESMTP id 22138-05; Wed, 18 Aug 2004 10:32:24 +0200 (CEST) Received: from james.eecs.iu-bremen.de (unknown [212.201.47.66]) by hermes.iu-bremen.de (Postfix) with ESMTP id 56257AC2; Wed, 18 Aug 2004 10:32:24 +0200 (CEST) Received: by james.eecs.iu-bremen.de (Postfix, from userid 1000) id 3935281F3; Wed, 18 Aug 2004 10:32:24 +0200 (CEST) Date: Wed, 18 Aug 2004 10:32:24 +0200 From: Juergen Schoenwaelder To: Kaj Tesink Subject: Re: [Entmib] CONSENSUS CHECK: Undo entAliasMapping deprecation Message-ID: <20040818083224.GA4566@iu-bremen.de> Mail-Followup-To: Kaj Tesink , entmib@ietf.org References: <20040816082053.GD1761@iu-bremen.de> <4.3.2.7.2.20040817172040.026f8378@128.96.81.11> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <4.3.2.7.2.20040817172040.026f8378@128.96.81.11> User-Agent: Mutt/1.5.6+20040722i X-Virus-Scanned: by amavisd-new 20030616p5 at demetrius.iu-bremen.de X-Spam-Score: 0.0 (/) X-Scan-Signature: 7aafa0432175920a4b3e118e16c5cb64 Cc: entmib@ietf.org X-BeenThere: entmib@ietf.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: j.schoenwaelder@iu-bremen.de List-Id: IETF Entity MIB WG List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: entmib-bounces@ietf.org Errors-To: entmib-bounces@ietf.org On Tue, Aug 17, 2004 at 05:31:24PM -0400, Kaj Tesink wrote: > > further actions: > - as per the emerging consensus, it is better to > insert the two objects in the entPhysicalEntry > of the entity mib itself; in that case all that is needed > is to cut&paste from the attached > - we'll post the draft for the for CLEI URN namespace request soon > - any other comments? Cutting and pasting text from your proposal, I came up with this proposal for integration into the ENTITY-MIB itself: entPhysicalMfgDate OBJECT-TYPE SYNTAX DateAndTime MAX-ACCESS read-only STATUS current DESCRIPTION "The manufacturing date for the physical entity. The value '0000000000000000'H should be returned if the manufacturing date for a physical entity is unknown." ::= { entPhysicalEntry 17 } entPhysicalMfgID OBJECT-TYPE SYNTAX DisplayString MAX-ACCESS read-write STATUS current DESCRIPTION "This object contains additional identification information about the physical entity. The object contains URIs and therefore the syntax of this object must conform to RFC 2396 section 2. Multiple URIs may be separated by white space characters. This object contains a zero-length string if no additional identification information is known or supported about the physical entity." ::= { entPhysicalEntry 18 } I think we should say something about when it is appropriate to write entPhysicalMfgId and to what extend it is required to provide write support for this object. In addition, we have to say something about the persistence of any modifications. Note that I called the objects *MfgDate and *MfgId since we already have entPhysicalMfgName and I propose to use null values in case a value is unknown since that avoids holes in tables and seems to be more consistent with the other objects in the entPhysicalTable. /js -- Juergen Schoenwaelder International University Bremen P.O. Box 750 561, 28725 Bremen, Germany _______________________________________________ Entmib mailing list Entmib@ietf.org https://www1.ietf.org/mailman/listinfo/entmib From entmib-bounces@ietf.org Mon Aug 23 13:20:00 2004 Received: from megatron.ietf.org (megatron.ietf.org [132.151.6.71]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA24261 for ; Mon, 23 Aug 2004 13:20:00 -0400 (EDT) Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1BzI6j-0002hM-D6; Mon, 23 Aug 2004 12:55:45 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1BzHi3-0007B5-VA for entmib@megatron.ietf.org; Mon, 23 Aug 2004 12:30:16 -0400 Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA21137 for ; Mon, 23 Aug 2004 12:30:08 -0400 (EDT) Message-Id: <200408231630.MAA21137@ietf.org> Received: from rwcrmhc12.comcast.net ([216.148.227.85]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1BzHiJ-0000Fy-D5 for entmib@ietf.org; Mon, 23 Aug 2004 12:30:32 -0400 Received: from djyxpy41 (h00104b8ce2a3.ne.client2.attbi.com[24.128.104.220]) by comcast.net (rwcrmhc12) with SMTP id <20040823162925014007rm5te>; Mon, 23 Aug 2004 16:29:27 +0000 From: "David B Harrington" To: , "'Margaret Wasserman'" Subject: RE: [Entmib] CONSENSUS CHECK: Undo entAliasMapping deprecation Date: Mon, 23 Aug 2004 12:29:21 -0400 MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit X-Mailer: Microsoft Office Outlook, Build 11.0.5510 Thread-Index: AcSDawYVEF6ol8p7TAu0345+7oS1LAFw0tsg X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1441 In-Reply-To: <20040816082053.GD1761@iu-bremen.de> X-Spam-Score: 0.1 (/) X-Scan-Signature: 4d87d2aa806f79fed918a62e834505ca Content-Transfer-Encoding: 7bit Cc: entmib@ietf.org X-BeenThere: entmib@ietf.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: ietfdbh@comcast.net List-Id: IETF Entity MIB WG List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: entmib-bounces@ietf.org Errors-To: entmib-bounces@ietf.org Content-Transfer-Encoding: 7bit Sounds reasonable to me. dbh -----Original Message----- From: entmib-bounces@ietf.org [mailto:entmib-bounces@ietf.org] On Behalf Of Juergen Schoenwaelder Sent: Monday, August 16, 2004 4:21 AM To: Margaret Wasserman Cc: entmib@ietf.org Subject: Re: [Entmib] CONSENSUS CHECK: Undo entAliasMapping deprecation On Fri, Aug 06, 2004 at 11:41:02PM -0400, Margaret Wasserman wrote: > During the Entity MIB meeting at IETF 60 in San Diego, there was > consensus in the room for the following course of action: > > (1) Pull the Entity State MIB document out of IESG processing > (currently submitted for publication as a Draft Standard) > > (2) Update the document to undo the deprecation of the entAliasMapping > identifier, and > > (3) Re-submit the Entity MIB to the IESG for publication as a Proposed > Standard. > > We now need to confirm this consensus on the mailing list. Are there > any objections to taking this course of action? Other comments? Sounds like a good plan to me. But if we recycle at Proposed, why do we then not simply put the entSupplPhysicalManufacturingDate and the entSupplPhysicalManufacturerInfo objects into the entPhysicalEntry where they actually belong? A new compliance statement would deal with these additions so existing implementations that comply to entity2Compliance would not be affected. /js -- Juergen Schoenwaelder International University Bremen P.O. Box 750 561, 28725 Bremen, Germany _______________________________________________ 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