From imss-bounces@ietf.org Thu Jul 13 19:03:45 2006 Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1G1ADg-0004pK-IY; Thu, 13 Jul 2006 19:03:44 -0400 Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1G1ADg-0004pF-1S for imss@ietf.org; Thu, 13 Jul 2006 19:03:44 -0400 Received: from mexforward.lss.emc.com ([128.222.32.20]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1G1ADe-00048x-Pp for imss@ietf.org; Thu, 13 Jul 2006 19:03:44 -0400 Received: from mailhub.lss.emc.com (sesha.lss.emc.com [10.254.144.12]) by mexforward.lss.emc.com (Switch-3.1.7/Switch-3.1.7) with ESMTP id k6DN3g4a001973 for ; Thu, 13 Jul 2006 19:03:42 -0400 (EDT) Received: from MAHO3MSX2.corp.emc.com (maho3msx2.corp.emc.com [128.221.11.32]) by mailhub.lss.emc.com (Switch-3.1.8/Switch-3.1.7) with ESMTP id k6DN3dC8020514 for ; Thu, 13 Jul 2006 19:03:40 -0400 (EDT) Received: by maho3msx2.corp.emc.com with Internet Mail Service (5.5.2653.19) id ; Thu, 13 Jul 2006 19:03:39 -0400 Message-ID: From: Black_David@emc.com To: imss@ietf.org Date: Thu, 13 Jul 2006 19:03:36 -0400 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.2653.19) Content-Type: text/plain X-PMX-Version: 4.7.1.128075, Antispam-Engine: 2.4.0.264935, Antispam-Data: 2006.7.13.153432 X-PerlMx-Spam: Gauge=, SPAM=0%, Reason='EMC_BODY_1+ -3, EMC_FROM_0+ -2, NO_REAL_NAME 0, __CT 0, __CT_TEXT_PLAIN 0, __HAS_MSGID 0, __HAS_X_MAILER 0, __IMS_MSGID 0, __IMS_MUA 0, __MIME_TEXT_ONLY 0, __MIME_VERSION 0, __SANE_MSGID 0, __STOCK_CRUFT 0' X-Spam-Score: 0.2 (/) X-Scan-Signature: c1c65599517f9ac32519d043c37c5336 Subject: [imss] Montreal - DRAFT minutes X-BeenThere: imss@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Internet and Management Support for Storage Working Group List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Errors-To: imss-bounces@ietf.org Here are the DRAFT minutes - please send corrections to me (and cc: the list if you want to). Thanks, --David Internet and Management Support for Storage (imss) WG Meeting - Montreal, Quebec, Canada Thursday, July 13, 2006: 1510-1610 DRAFT Minutes ------------------------------------------------------ Administrivia, agenda bashing, draft status review, etc.: 15 min David L. Black, EMC (imss WG chair) Blue sheets Note Well Draft status - All current drafts have been IESG-Approved Milestones - 3 new MIBs in charter, August 2006 T11.5 Status, Fibre Channel MIBs under development: 15 min Roger Cummings (Symantec, T11.5 chair) See slides. Discussion with Dan Romascanu (OPS Area Director responsible for imss) indicates that T11 and imss will need to consider the IEEE MIB development model as part of upcoming imss rechartering in the next few months. The IEEE is now responsible for all of their own MIB development, with the IETF providing MIB Doctor reviews upon request. New FC MIBs forwarded from T11.5: 15 min Keith McCloghrie (Cisco) draft-kzm-imss-fc-rscn-mib-03.txt draft-kzm-imss-fc-zs-mib-03.txt draft-kzm-imss-fc-fcs-mib-02.txt These are the MIB drafts for the following goal on the WG's charter: - Submit Fibre Channel Zone Server, RSCN, and Fabric Configuration Server MIBs to IESG for consideration as Proposed Standard The drafts were adopted as official imss WG drafts (no objection in the room). Keith McCloghrie will submit draft-ietf-imss versions. T11 needs to allocate an Application_ID value for the ZS MIB - that should happen by Calgary T11 meetings in early August. Submission of the draft-ietf-imss version of this MIB will probably wait until that ID is available. _______________________________________________ imss mailing list imss@ietf.org https://www1.ietf.org/mailman/listinfo/imss From imss-bounces@ietf.org Fri Jul 21 15:56:08 2006 Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1G416W-0001gB-0h; Fri, 21 Jul 2006 15:56:08 -0400 Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1G416V-0001fL-2r for imss@ietf.org; Fri, 21 Jul 2006 15:56:07 -0400 Received: from mexforward.lss.emc.com ([128.222.32.20]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1G412D-00025I-IC for imss@ietf.org; Fri, 21 Jul 2006 15:51:42 -0400 Received: from mailhub.lss.emc.com (uraeus.lss.emc.com [10.254.144.14]) by mexforward.lss.emc.com (Switch-3.1.7/Switch-3.1.7) with ESMTP id k6LJpffF007134 for ; Fri, 21 Jul 2006 15:51:41 -0400 (EDT) Received: from mxic2.corp.emc.com (mxic2.corp.emc.com [128.221.12.9]) by mailhub.lss.emc.com (Switch-3.1.8/Switch-3.1.7) with ESMTP id k6LJpcLM016544 for ; Fri, 21 Jul 2006 15:51:40 -0400 (EDT) Received: by mxic2.corp.emc.com with Internet Mail Service (5.5.2653.19) id ; Fri, 21 Jul 2006 15:51:38 -0400 Message-ID: From: Black_David@emc.com To: imss@ietf.org Date: Fri, 21 Jul 2006 15:51:34 -0400 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.2653.19) Content-Type: text/plain X-PMX-Version: 4.7.1.128075, Antispam-Engine: 2.4.0.264935, Antispam-Data: 2006.7.21.121432 X-PerlMx-Spam: Gauge=, SPAM=0%, Reason='EMC_BODY_1+ -3, EMC_FROM_0+ -2, NO_REAL_NAME 0, __C230066_P5 0, __CT 0, __CT_TEXT_PLAIN 0, __HAS_MSGID 0, __HAS_X_MAILER 0, __IMS_MSGID 0, __IMS_MUA 0, __MIME_TEXT_ONLY 0, __MIME_VERSION 0, __SANE_MSGID 0, __STOCK_CRUFT 0' X-Spam-Score: 0.2 (/) X-Scan-Signature: 4b800b1eab964a31702fa68f1ff0e955 Subject: [imss] Montreal - FINAL minutes X-BeenThere: imss@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Internet and Management Support for Storage Working Group List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Errors-To: imss-bounces@ietf.org Having seen no comments or corrections, these are the final Montreal minutes. Thanks, --David (imss WG chair) ---------------------------------------------------- David L. Black, Senior Technologist EMC Corporation, 176 South St., Hopkinton, MA 01748 +1 (508) 293-7953 FAX: +1 (508) 293-7786 black_david@emc.com Mobile: +1 (978) 394-7754 ---------------------------------------------------- -----Original Message----- From: Black_David@emc.com [mailto:Black_David@emc.com] Sent: Thursday, July 13, 2006 7:04 PM To: imss@ietf.org Subject: [imss] Montreal - DRAFT minutes Here are the DRAFT minutes - please send corrections to me (and cc: the list if you want to). Thanks, --David Internet and Management Support for Storage (imss) WG Meeting - Montreal, Quebec, Canada Thursday, July 13, 2006: 1510-1610 DRAFT Minutes ------------------------------------------------------ Administrivia, agenda bashing, draft status review, etc.: 15 min David L. Black, EMC (imss WG chair) Blue sheets Note Well Draft status - All current drafts have been IESG-Approved Milestones - 3 new MIBs in charter, August 2006 T11.5 Status, Fibre Channel MIBs under development: 15 min Roger Cummings (Symantec, T11.5 chair) See slides. Discussion with Dan Romascanu (OPS Area Director responsible for imss) indicates that T11 and imss will need to consider the IEEE MIB development model as part of upcoming imss rechartering in the next few months. The IEEE is now responsible for all of their own MIB development, with the IETF providing MIB Doctor reviews upon request. New FC MIBs forwarded from T11.5: 15 min Keith McCloghrie (Cisco) draft-kzm-imss-fc-rscn-mib-03.txt draft-kzm-imss-fc-zs-mib-03.txt draft-kzm-imss-fc-fcs-mib-02.txt These are the MIB drafts for the following goal on the WG's charter: - Submit Fibre Channel Zone Server, RSCN, and Fabric Configuration Server MIBs to IESG for consideration as Proposed Standard The drafts were adopted as official imss WG drafts (no objection in the room). Keith McCloghrie will submit draft-ietf-imss versions. T11 needs to allocate an Application_ID value for the ZS MIB - that should happen by Calgary T11 meetings in early August. Submission of the draft-ietf-imss version of this MIB will probably wait until that ID is available. _______________________________________________ imss mailing list imss@ietf.org https://www1.ietf.org/mailman/listinfo/imss _______________________________________________ imss mailing list imss@ietf.org https://www1.ietf.org/mailman/listinfo/imss From imss-bounces@ietf.org Tue Jul 25 15:06:17 2006 Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1G5SET-00020M-8r; Tue, 25 Jul 2006 15:06:17 -0400 Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1G5SES-00020B-BC; Tue, 25 Jul 2006 15:06:16 -0400 Received: from oak.neustar.com ([209.173.53.70]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1G5SES-0007z5-2F; Tue, 25 Jul 2006 15:06:16 -0400 Received: from stiedprstage1.ietf.org (stiedprstage1.va.neustar.com [10.31.47.10]) by oak.neustar.com (8.12.8/8.12.8) with ESMTP id k6PJ5hp0003036 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Tue, 25 Jul 2006 19:05:43 GMT Received: from ietf by stiedprstage1.ietf.org with local (Exim 4.43) id 1G5SDv-0006rM-7E; Tue, 25 Jul 2006 15:05:43 -0400 X-test-idtracker: no From: The IESG To: IETF-Announce Message-Id: Date: Tue, 25 Jul 2006 15:05:43 -0400 X-Spam-Score: 0.1 (/) X-Scan-Signature: b2809b6f39decc6de467dcf252f42af1 Cc: imss mailing list , Internet Architecture Board , imss chair , RFC Editor Subject: [imss] Protocol Action: 'The Virtual Fabrics MIB' to Proposed Standard X-BeenThere: imss@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Internet and Management Support for Storage Working Group List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Errors-To: imss-bounces@ietf.org The IESG has approved the following document: - 'The Virtual Fabrics MIB ' as a Proposed Standard This document is the product of the Internet and Management Support for Storage Working Group. The IESG contact persons are Dan Romascanu and David Kessens. A URL of this Internet-Draft is: http://www.ietf.org/internet-drafts/draft-ietf-imss-fc-vf-mib-02.txt Technical Summary 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 for information related to the Fibre Channel network's Virtual Fabric function. Working Group Summary There seems to be wide support in the WG for this document, although the participation in the WG was thin lately. Protocol Quality The document was reviewed by Bert Wijnen on behalf of the IESG. It was reviewed also in Technical Committee T11 (the official Fibre Channel standards body). T11 voted to recommend a prior version of this document to the IETF. Keith McCloghrie is acting as MIB expert for the IMSS WG. Note to RFC Editor 1. In the title of Section 6 OLD: 6. The T11-FC-IRTUAL-FABRIC-MIB Module NEW: 6. The T11-FC-VIRTUAL-FABRIC-MIB Module 2. Add to Section 1 the following: The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this document are to be interpreted as described in RFC 2119. 3. Add a normative reference to RFC 2119 4. In Section 5 OLD: This MIB module provides the means for monitoring the operation of, and configuring some parameters of, one or more instances of Fibre Channel Virtual Fabric functionality. (Note that there are no definitions in this MIB module of "managed actions" which can be invoked via SNMP.) NEW: This MIB module provides the means for monitoring the operation of, and configuring some parameters of, one or more instances of Fibre Channel Virtual Fabric functionality. (Note that there are no definitions in this MIB module of "managed actions" which can be invoked via a remote network management protocol such as SNMP.) 5. In Section 5.1: OLD: The object, fcmInstanceIndex, is IMPORTed from the FC-MGMT- MIB [RFC4044] as the index value to uniquely identify each Fibre Channel management instance within the same SNMP context ([RFC3411] section 3.3.1). NEW: The object, fcmInstanceIndex, is IMPORTed from the FC-MGMT- MIB [RFC4044] as the index value to uniquely identify each Fibre Channel management instance, for example within the same SNMP context ([RFC3411] section 3.3.1). 6. In Section 6: OLD: This table augments the fcmSwitchTable, i.e., every entry in this table has a one-to-one correspondence with an entry in the fcmSwitchTable. At the time when the fcmSwitchTable was defined, it applied to physical switches. With the definition and usage of virtual switches, fcmSwitchTable now applies to virtual switches which (unlike physical fabrics) are create-able via SNMP. So, this entry contains a RowStatus object (to allow the creation of a virtual switch), as well as a StorageType object. Obviously, if a row is created/deleted in this table, the corresponding row in the fcmSwitchTable will be created/deleted." NEW: This table augments the fcmSwitchTable, i.e., every entry in this table has a one-to-one correspondence with an entry in the fcmSwitchTable. At the time when the fcmSwitchTable was defined, it applied to physical switches. With the definition and usage of virtual switches, fcmSwitchTable now applies to virtual switches as well as physical switches, and (in contrast to physical switches) it is appropriate to provide the capability for virtual switches to be created via remote management applications, e.g., via SNMP. So, this entry contains a RowStatus object (to allow the creation of a virtual switch), as well as a StorageType object. Obviously, if a row is created/deleted in this table, the corresponding row in the fcmSwitchTable will be created/deleted." IANA Note Upon approval IANA will be requested to allocate a sub-tree identifier for this MIB module under mib-2. _______________________________________________ imss mailing list imss@ietf.org https://www1.ietf.org/mailman/listinfo/imss From imss-bounces@ietf.org Wed Jul 26 07:09:15 2006 Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1G5hGN-00011r-13; Wed, 26 Jul 2006 07:09:15 -0400 Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1G5hGM-00011e-CV; Wed, 26 Jul 2006 07:09:14 -0400 Received: from us-gw.atrica.com ([63.160.45.2] helo=usmail.atrica.com) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1G5hGK-0005lz-Jf; Wed, 26 Jul 2006 07:09:14 -0400 Received: from mail pickup service by usmail.atrica.com with Microsoft SMTPSVC; Wed, 26 Jul 2006 04:08:59 -0700 Received: from resolution.atrica.com ([63.160.45.67]) by usmail.atrica.com with Microsoft SMTPSVC(6.0.3790.1830); Tue, 25 Jul 2006 12:07:19 -0700 Received: from usmailrelay0.atrica.com (unknown [63.160.45.96]) by resolution.atrica.com (Postfix) with ESMTP id 78F4F2C1AE for ; Tue, 25 Jul 2006 11:41:39 -0700 (PDT) Received: from megatron.ietf.org (www1.ietf.org [156.154.16.145]) by usmailrelay0.atrica.com (Symantec Mail Security) with ESMTP id 31174C0A for ; Tue, 25 Jul 2006 12:07:18 -0700 (PDT) Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1G5SEU-00020Q-7U; Tue, 25 Jul 2006 15:06:18 -0400 Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1G5SES-00020B-BC; Tue, 25 Jul 2006 15:06:16 -0400 Received: from oak.neustar.com ([209.173.53.70]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1G5SES-0007z5-2F; Tue, 25 Jul 2006 15:06:16 -0400 Received: from stiedprstage1.ietf.org (stiedprstage1.va.neustar.com [10.31.47.10]) by oak.neustar.com (8.12.8/8.12.8) with ESMTP id k6PJ5hp0003036 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Tue, 25 Jul 2006 19:05:43 GMT Received: from ietf by stiedprstage1.ietf.org with local (Exim 4.43) id 1G5SDv-0006rM-7E; Tue, 25 Jul 2006 15:05:43 -0400 X-test-idtracker: no From: The IESG To: IETF-Announce Message-Id: Date: Tue, 25 Jul 2006 15:05:43 -0400 X-Spam-Score: 0.1 (/) X-Scan-Signature: b2809b6f39decc6de467dcf252f42af1 X-BeenThere: ietf-announce@ietf.org X-Mailman-Version: 2.1.5 Precedence: list X-Brightmail-Tracker: AAAAAA== X-OriginalArrivalTime: 25 Jul 2006 19:07:19.0711 (UTC) FILETIME=[8D424AF0:01C6B01D] X-Spam-Score: 0.1 (/) X-Scan-Signature: a1852b4f554b02e7e4548cc7928acc1f Cc: imss mailing list , Internet Architecture Board , imss chair , RFC Editor Subject: [imss] Protocol Action: 'The Virtual Fabrics MIB' to Proposed Standard X-BeenThere: imss@ietf.org List-Id: Internet and Management Support for Storage Working Group List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Errors-To: imss-bounces@ietf.org The IESG has approved the following document: - 'The Virtual Fabrics MIB ' as a Proposed Standard This document is the product of the Internet and Management Support for Storage Working Group. The IESG contact persons are Dan Romascanu and David Kessens. A URL of this Internet-Draft is: http://www.ietf.org/internet-drafts/draft-ietf-imss-fc-vf-mib-02.txt Technical Summary 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 for information related to the Fibre Channel network's Virtual Fabric function. Working Group Summary There seems to be wide support in the WG for this document, although the participation in the WG was thin lately. Protocol Quality The document was reviewed by Bert Wijnen on behalf of the IESG. It was reviewed also in Technical Committee T11 (the official Fibre Channel standards body). T11 voted to recommend a prior version of this document to the IETF. Keith McCloghrie is acting as MIB expert for the IMSS WG. Note to RFC Editor 1. In the title of Section 6 OLD: 6. The T11-FC-IRTUAL-FABRIC-MIB Module NEW: 6. The T11-FC-VIRTUAL-FABRIC-MIB Module 2. Add to Section 1 the following: The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this document are to be interpreted as described in RFC 2119. 3. Add a normative reference to RFC 2119 4. In Section 5 OLD: This MIB module provides the means for monitoring the operation of, and configuring some parameters of, one or more instances of Fibre Channel Virtual Fabric functionality. (Note that there are no definitions in this MIB module of "managed actions" which can be invoked via SNMP.) NEW: This MIB module provides the means for monitoring the operation of, and configuring some parameters of, one or more instances of Fibre Channel Virtual Fabric functionality. (Note that there are no definitions in this MIB module of "managed actions" which can be invoked via a remote network management protocol such as SNMP.) 5. In Section 5.1: OLD: The object, fcmInstanceIndex, is IMPORTed from the FC-MGMT- MIB [RFC4044] as the index value to uniquely identify each Fibre Channel management instance within the same SNMP context ([RFC3411] section 3.3.1). NEW: The object, fcmInstanceIndex, is IMPORTed from the FC-MGMT- MIB [RFC4044] as the index value to uniquely identify each Fibre Channel management instance, for example within the same SNMP context ([RFC3411] section 3.3.1). 6. In Section 6: OLD: This table augments the fcmSwitchTable, i.e., every entry in this table has a one-to-one correspondence with an entry in the fcmSwitchTable. At the time when the fcmSwitchTable was defined, it applied to physical switches. With the definition and usage of virtual switches, fcmSwitchTable now applies to virtual switches which (unlike physical fabrics) are create-able via SNMP. So, this entry contains a RowStatus object (to allow the creation of a virtual switch), as well as a StorageType object. Obviously, if a row is created/deleted in this table, the corresponding row in the fcmSwitchTable will be created/deleted." NEW: This table augments the fcmSwitchTable, i.e., every entry in this table has a one-to-one correspondence with an entry in the fcmSwitchTable. At the time when the fcmSwitchTable was defined, it applied to physical switches. With the definition and usage of virtual switches, fcmSwitchTable now applies to virtual switches as well as physical switches, and (in contrast to physical switches) it is appropriate to provide the capability for virtual switches to be created via remote management applications, e.g., via SNMP. So, this entry contains a RowStatus object (to allow the creation of a virtual switch), as well as a StorageType object. Obviously, if a row is created/deleted in this table, the corresponding row in the fcmSwitchTable will be created/deleted." IANA Note Upon approval IANA will be requested to allocate a sub-tree identifier for this MIB module under mib-2. _______________________________________________ IETF-Announce mailing list IETF-Announce@ietf.org https://www1.ietf.org/mailman/listinfo/ietf-announce _______________________________________________ imss mailing list imss@ietf.org https://www1.ietf.org/mailman/listinfo/imss