From imss-bounces@ietf.org Thu Oct 05 23:03:30 2006 Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1GVfzU-0000rY-Fe; Thu, 05 Oct 2006 23:03:12 -0400 Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1GVfzT-0000rQ-LH for imss@ietf.org; Thu, 05 Oct 2006 23:03:11 -0400 Received: from mexforward.lss.emc.com ([128.222.32.20]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1GVfzR-00060K-75 for imss@ietf.org; Thu, 05 Oct 2006 23:03:11 -0400 Received: from mailhub.lss.emc.com (nagas.lss.emc.com [10.254.144.11]) by mexforward.lss.emc.com (Switch-3.1.7/Switch-3.1.7) with ESMTP id k963322X008203 for ; Thu, 5 Oct 2006 23:03:02 -0400 (EDT) Received: from corpussmtp3.corp.emc.com (corpussmtp3.corp.emc.com [10.254.64.53]) by mailhub.lss.emc.com (Switch-3.1.8/Switch-3.1.7) with ESMTP id k9632Cfc025747 for ; Thu, 5 Oct 2006 23:02:58 -0400 (EDT) From: Black_David@emc.com Received: from CORPUSMX20A.corp.emc.com ([128.221.62.13]) by corpussmtp3.corp.emc.com with Microsoft SMTPSVC(6.0.3790.0); Thu, 5 Oct 2006 23:02:26 -0400 X-MimeOLE: Produced By Microsoft Exchange V6.5 Content-class: urn:content-classes:message MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable Date: Thu, 5 Oct 2006 23:02:25 -0400 Message-ID: X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: MIB Last Call Results and Fabric Config Server MIB Design Issue Thread-Index: Acbhymu1V+8N2FYhTXiYQzr+OQJPcgHKSLHg To: X-OriginalArrivalTime: 06 Oct 2006 03:02:26.0074 (UTC) FILETIME=[DA1E17A0:01C6E8F3] X-PMX-Version: 4.7.1.128075, Antispam-Engine: 2.4.0.264935, Antispam-Data: 2006.10.5.193443 X-PerlMx-Spam: Gauge=, SPAM=0%, Reason='EMC_BODY_1+ -3, EMC_FROM_0+ -2, NO_REAL_NAME 0, __C230066_P5 0, __CT 0, __CTE 0, __CTYPE_CHARSET_QUOTED 0, __CT_TEXT_PLAIN 0, __HAS_MSGID 0, __IMS_MSGID 0, __MIME_TEXT_ONLY 0, __MIME_VERSION 0, __SANE_MSGID 0' X-Spam-Score: 0.2 (/) X-Scan-Signature: c54bc2f42d02429833c0ca4b8725abd7 Cc: Black_David@emc.com Subject: [imss] FW: MIB Last Call Results and Fabric Config Server MIB Design Issue 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 objection to the proposed table restructuring and simplification in the Fabric Config Server MIB, I believe the rough consensus of the imss WG it to simplify the tables as proposed in response to the WG Last Call comment. The editor (Keith) should proceed to do that. Thanks, --David -----Original Message----- From: Black, David=20 Sent: Tuesday, September 26, 2006 8:18 PM To: imss@ietf.org Cc: Black, David Subject: MIB Last Call Results and Fabric Config Server MIB Design Issue The imss WG last call on the Fibre Channel RSCN, Fabric Config Server, and Zone Server MIBs has certainly been interesting, and I want to thank Bert Wijnen and Dan Romascanu for spending time on these MIBs at this juncture - it should help significantly in dealing with these MIBs after they leave the WG. For now, these MIBs are here in the imss WG. While I saw a lot of Last Call issues on MIB syntax, I only saw one significant technical issue on the table structure in the Fabric Config Server MIB (see below). That technical issue appears sufficiently contained (it's about MIB table structure, and does not affect function) that I don't believe a second WG Last Call will be needed once a resolution is determined. So, all three MIBs are through WG Last call, but new versions of all three MIB drafts will be needed to check that the significant number of issues found by Dan and Bert have been addressed. Those will probably show up after the T11 meetings next week because ... We(I) also have some things to address with T11. The good news is that not only is FC-GS-5 now a stable reference, but also based on my discussions with the responsible T11 people, the "Ugly" issue 3) should be resolved by formal T11 action next week that should produce an archive document containing the required FC-SW-5 allocation (which can then be cited in a REFERENCE clause). That issue was: T11 does not have an IANA equivalent, and hence we will need to come up with something to formalize the allocation and record it in some- thing reference-able prior to FC-SW-5 putting in an appearance. The remaining T11 issue is the status/stability of FC-LS, and I will report back to the WG on that after the T11 meetings next week. That leaves one technical issue that needs attention here: ---------------- > Bert Wijnen Keith McCloghrie > - SMICng gave a warning about the indexing of >=20 > t11FcsPortListEntry OBJECT-TYPE > SYNTAX T11FcsPortListEntry > MAX-ACCESS not-accessible > STATUS current > DESCRIPTION > "An entry which identifies that the port which has the > port name, t11FcsPortName, is in a particular list of > ports, which is known to a switch (identified by > fcmInstanceIndex and fcmSwitchIndex)." > INDEX { fcmInstanceIndex, fcmSwitchIndex, > t11FcsPortListIndex, t11FcsPortName } > ::=3D { t11FcsPortListTable 1 } >=20 > I read Keiths explanation, which seemed fine. But now that I am > reviewing the MIB module in details and try to understand things, > now I am no so sure this is goodness. >=20 > So, that t11FcsPortname is a value (embedded in the index) that > should help me find more detailed info, right? > So how do I find that info? I think I need to go to the > t11FcsPortTable, which is indexed by: >=20 > INDEX { fcmInstanceIndex, fcmSwitchIndex, > t11FcsFabricIndex, t11FcsPortName } >=20 > So assuming that the index values for fcmInstanceIndex, fcmSwitchIndex, > are the same in both tables, I can see that I can pick up 3 index > values from the list of t11FcsPortsList in the t11FcsPortsListTable. > But I am missing the 3rd index of the t11FcsPortnameTable, namely > t11FcsFabricIndex. So how am I going to wuickly pick that up? > Or how exactly are the tables connected/linked? >=20 > Maybe I need to study it deeper... but I'd prefer an explanation of > the people who created these tables with the current indexing schemes. =20 To generate an answer to your question, I needed to re-review the structure of the tables, and in doing so, I now think that the current structure is more open-ended/flexible than it needs to be -- having a less open-ended structure would make the MIB simpler. Specifically, the MIB currently has a table whose only purpose is to identify a list of (not necessarily related) ports. However, - each IE is either a virtual IE attached to one virtual Fabric, or (if virtual Fabrics are not in use) it's a physical IE. - each port is either a virtual port attached to one virtual Fabric, or (if virtual Fabrics are not in use) it's a physical port. - GS-5 mentions that an IE has a "port list" and has a dotted line from the "Interconnect Element Object" to the "Port Object" in its "Figure 7 -- Interconnect Element and Port attributes". - However, all ports in an IE's port list will be attached to the same=20 Fabric as that IE is attached to. In other words, the relationship between IEs and ports is hierarchical. - Thus, it would be simpler to: - delete the t11FcsPortListTable, - delete the t11FcsIePortListIndex object, and - insert t11FcsIeName into the INDEX of the t11FcsPortTable, i.e., change the INDEX-ing of the t11FcsPortTable to be: INDEX { fcmInstanceIndex, fcmSwitchIndex, t11FcsFabricIndex, t11FcsIeName, t11FcsPortName } Increasing the INDEX clause from four to five objects makes it a little more cumbersome, but the length is still far short of the maximum length. With these changes, while there will no longer be any explicit mention of a "port list" in the MIB, the list of ports on an IE will be all the rows in t11FcsPortTable which have the same values for the first four index objects, i.e., the value of t11FcsPortName will be the only index value for which they differ. So, a "port list" is (implicitly) a set of adjacent rows in the t11FcsPortTable. ----------------- This looks like a desirable simplification to me (taking out one table), but the purpose of this email is to solicit comments from others on this mailing list. Please comment within the next week. 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 ---------------------------------------------------- _______________________________________________ imss mailing list imss@ietf.org https://www1.ietf.org/mailman/listinfo/imss From imss-bounces@ietf.org Thu Oct 05 23:37:51 2006 Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1GVgWw-0001zD-Un; Thu, 05 Oct 2006 23:37:46 -0400 Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1GVgWv-0001z7-QP for imss@ietf.org; Thu, 05 Oct 2006 23:37:45 -0400 Received: from mexforward.lss.emc.com ([128.222.32.20]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1GVgWr-0005cd-HA for imss@ietf.org; Thu, 05 Oct 2006 23:37:45 -0400 Received: from mailhub.lss.emc.com (sesha.lss.emc.com [10.254.144.12]) by mexforward.lss.emc.com (Switch-3.1.8/Switch-3.1.7) with ESMTP id k963bcVj011262 for ; Thu, 5 Oct 2006 23:37:38 -0400 (EDT) Received: from corpussmtp3.corp.emc.com (corpussmtp3.corp.emc.com [10.254.64.53]) by mailhub.lss.emc.com (Switch-3.1.8/Switch-3.1.7) with ESMTP id k963aYGD025178 for ; Thu, 5 Oct 2006 23:37:32 -0400 (EDT) From: Black_David@emc.com Received: from CORPUSMX20A.corp.emc.com ([128.221.62.13]) by corpussmtp3.corp.emc.com with Microsoft SMTPSVC(6.0.3790.0); Thu, 5 Oct 2006 23:37:31 -0400 X-MimeOLE: Produced By Microsoft Exchange V6.5 Content-class: urn:content-classes:message MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable Date: Thu, 5 Oct 2006 23:37:31 -0400 Message-ID: X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: T11 MIB issue resolutions Thread-Index: Acbo+MCii6DK7RKwRP6LeA/0XXshWQ== To: X-OriginalArrivalTime: 06 Oct 2006 03:37:31.0900 (UTC) FILETIME=[C149A3C0:01C6E8F8] X-PMX-Version: 4.7.1.128075, Antispam-Engine: 2.4.0.264935, Antispam-Data: 2006.10.5.201442 X-PerlMx-Spam: Gauge=, SPAM=0%, Reason='EMC_BODY_1+ -3, EMC_FROM_0+ -2, NO_REAL_NAME 0, __C230066_P5 0, __CP_URI_IN_BODY 0, __CT 0, __CTE 0, __CTYPE_CHARSET_QUOTED 0, __CT_TEXT_PLAIN 0, __HAS_MSGID 0, __IMS_MSGID 0, __MIME_TEXT_ONLY 0, __MIME_VERSION 0, __SANE_MSGID 0' X-Spam-Score: 0.2 (/) X-Scan-Signature: 5a9a1bd6c2d06a21d748b7d0070ddcb8 Cc: Black_David@emc.com Subject: [imss] T11 MIB issue resolutions 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 Technical Committee T11 meeting week is now concluded; this message reports on the actions T11 has taken to respond to issues that surfaced in the recent imss WG Last Call. (1) Both the Fabric Configuration Server MIB and the Zone Server MIB need to reference FC-GS-5. FC-GS-5 is in final ANSI editing before being published as a standard (T11 provided final guidance and approval of ANSI editorial changes this week). The reference should be: Fibre Channel - Generic Services - 5 (FC-GS-5)", ANSI INCITS 427-2006, 2006. (2) The Zone Server MIB needed an FC-SW-* Application ID Value allocated for use in t11FLockFabricIndex. After some initial bobbles, document T11/06-679v0 has been created to perform the allocation at this time (prior to the first draft of FC-SW-5). This document was formally approved by the T11 plenary (a roll call vote was involve, IIRC), and hence it is the reference that should be cited as the authority for the value FF (hex): S. Wilson, "FC-SW-5 Letter to T11.5" Document T11/06-697v0 (http://www.t11.org/ftp/t11/pub/fc/sw-5/06-679v0.pdf) Approved by the T11 and T11.5 plenary meetings on October 5, 2006. The MIB should also state that this value, FF (hex), will appear in FC-SW-5. (3) The RSCN MIB needs to reference a stable version of FC-LS. I have spoken with the T11 FC-LS editor, and the appropriate version of FC-LS to references will be revision 1.6, which should appear prior to the IETF San Diego meetings. That revision should not undergo any technical or organizational changes prior to approval and forwarding to INCITS at the December T11 meetings. In both cases (2) and (3), the references will need to be checked for possible updating at both IETF Last Call and Authors 48 Hours. I will ensure that this need is noted in the PROTO writeup when publication of these drafts is requested. The upshot is that the RSCN MIB will need to be held in the imss WG until sometime in November when an appropriate FC-LS reference will be available. The Fabric Configuration Server MIB and Zone Server MIB should be revised to address the WG Last Call comments and the above comments - it should be possible to request publication of those two MIBs in the next few weeks. Thanks, --David ---------------------------------------------------- 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 ---------------------------------------------------- _______________________________________________ imss mailing list imss@ietf.org https://www1.ietf.org/mailman/listinfo/imss From imss-bounces@ietf.org Wed Oct 11 17:52:57 2006 Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1GXm0M-0000Kt-Kp; Wed, 11 Oct 2006 17:52:46 -0400 Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1GXm0K-0000Jm-V7 for imss@ietf.org; Wed, 11 Oct 2006 17:52:44 -0400 Received: from sj-iport-5.cisco.com ([171.68.10.87]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1GXlwe-0004C8-68 for imss@ietf.org; Wed, 11 Oct 2006 17:48:57 -0400 Received: from sj-dkim-5.cisco.com ([171.68.10.79]) by sj-iport-5.cisco.com with ESMTP; 11 Oct 2006 14:48:56 -0700 X-IronPort-AV: i="4.09,295,1157353200"; d="scan'208"; a="330682053:sNHT48841256" Received: from sj-core-4.cisco.com (sj-core-4.cisco.com [171.68.223.138]) by sj-dkim-5.cisco.com (8.12.11.20060308/8.12.11) with ESMTP id k9BLmtsQ001020; Wed, 11 Oct 2006 14:48:55 -0700 Received: from cisco.com (pita.cisco.com [171.71.177.199]) by sj-core-4.cisco.com (8.12.10/8.12.6) with ESMTP id k9BLmpOV013911; Wed, 11 Oct 2006 14:48:51 -0700 (PDT) Received: (from kzm@localhost) by cisco.com (8.8.8-Cisco List Logging/8.8.8) id OAA24315; Wed, 11 Oct 2006 14:47:35 -0700 (PDT) From: Keith McCloghrie Message-Id: <200610112147.OAA24315@cisco.com> Subject: Re: [imss] T11 MIB issue resolutions To: Black_David@emc.com, bwijnen@lucent.com, dromasca@avaya.com Date: Wed, 11 Oct 2006 14:47:35 -0700 (PDT) In-Reply-To: from "Black_David@emc.com" at Oct 05, 2006 11:37:31 PM X-Mailer: ELM [version 2.5 PL5] MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit DKIM-Signature: a=rsa-sha1; q=dns; l=888; t=1160603335; x=1161467335; c=relaxed/simple; s=sjdkim5002; h=Content-Type:From:Subject:Content-Transfer-Encoding:MIME-Version; d=cisco.com; i=kzm@cisco.com; z=From:Keith=20McCloghrie=20 |Subject:Re=3A=20[imss]=20T11=20MIB=20issue=20resolutions; X=v=3Dcisco.com=3B=20h=3D47u5wGPvUCO4ofTZlfkJ8ZJy1fU=3D; b=ec3OQ24i+WUqxouEFQlqUpQeUW36JaEL2x6lmVqDOoGgr3peHCfj2gF/MzZNXtkJrugclom5 l5lLFkglquq3BOu07j2cf4YduzrLov2nsdfThbMahdidAcgoJOUFDAd+; Authentication-Results: sj-dkim-5.cisco.com; header.From=kzm@cisco.com; dkim=pass ( sig from cisco.com verified; ); X-Spam-Score: 0.0 (/) X-Scan-Signature: 7d33c50f3756db14428398e2bdedd581 Cc: imss@ietf.org 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 upshot is that the RSCN MIB will need to be held in the imss > WG until sometime in November when an appropriate FC-LS reference > will be available. The Fabric Configuration Server MIB and > Zone Server MIB should be revised to address the WG Last Call > comments and the above comments - it should be possible to > request publication of those two MIBs in the next few weeks. The revised version are available at: ftp://ftpeng.cisco.com/ftp/kzm/draft-ietf-imss-fc-zs-mib-01.txt ftp://ftpeng.cisco.com/ftp/kzm/draft-ietf-imss-fc-fcs-mib-01.txt ftp://ftpeng.cisco.com/ftp/kzm/draft-ietf-imss-fc-rscn-mib-01.txt Please could those who submitted comments check that I have accurately captured the agreed resolutions. I plan to submit the new versions (or at least the first two) as updated I-Ds at the beginning of next week. Thanks, Keith. _______________________________________________ imss mailing list imss@ietf.org https://www1.ietf.org/mailman/listinfo/imss From imss-bounces@ietf.org Tue Oct 17 07:21:38 2006 Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1GZn0o-0000Wg-6O; Tue, 17 Oct 2006 07:21:34 -0400 Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1GZn0m-0000Wb-AE for imss@ietf.org; Tue, 17 Oct 2006 07:21:32 -0400 Received: from co300216-ier2.net.avaya.com ([198.152.13.103]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1GZn0j-0007JJ-Vb for imss@ietf.org; Tue, 17 Oct 2006 07:21:32 -0400 Received: from IS0004AVEXU1.global.avaya.com (h135-64-105-51.avaya.com [135.64.105.51]) by co300216-ier2.net.avaya.com (Switch-3.1.8/Switch-3.1.7) with ESMTP id k9HBCHEM012068 for ; Tue, 17 Oct 2006 07:12:18 -0400 X-MimeOLE: Produced By Microsoft Exchange V6.0.6603.0 content-class: urn:content-classes:message MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable Subject: RE: [imss] T11 MIB issue resolutions Date: Tue, 17 Oct 2006 13:21:23 +0200 Message-ID: X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: [imss] T11 MIB issue resolutions Thread-Index: AcbtfxE6mYENOlYTRra7CNYL3rDd7AEXn2fQ From: "Romascanu, Dan \(Dan\)" To: "Keith McCloghrie" , , X-Scanner: InterScan AntiVirus for Sendmail X-Spam-Score: 0.0 (/) X-Scan-Signature: 8b30eb7682a596edff707698f4a80f7d Cc: imss@ietf.org 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 Sorry for the delay in answering. OK with me. Thanks and Regards, Dan =20 =20 > -----Original Message----- > From: Keith McCloghrie [mailto:kzm@cisco.com]=20 > Sent: Wednesday, October 11, 2006 11:48 PM > To: Black_David@emc.com; bwijnen@lucent.com; Romascanu, Dan (Dan) > Cc: imss@ietf.org > Subject: Re: [imss] T11 MIB issue resolutions >=20 > > ... > >=20 > > The upshot is that the RSCN MIB will need to be held in the imss WG=20 > > until sometime in November when an appropriate FC-LS=20 > reference will be=20 > > available. The Fabric Configuration Server MIB and Zone Server MIB=20 > > should be revised to address the WG Last Call comments and=20 > the above=20 > > comments - it should be possible to request publication of=20 > those two=20 > > MIBs in the next few weeks. > =20 > The revised version are available at: >=20 > ftp://ftpeng.cisco.com/ftp/kzm/draft-ietf-imss-fc-zs-mib-01.txt > ftp://ftpeng.cisco.com/ftp/kzm/draft-ietf-imss-fc-fcs-mib-01.txt > ftp://ftpeng.cisco.com/ftp/kzm/draft-ietf-imss-fc-rscn-mib-01.txt >=20 > Please could those who submitted comments check that I have=20 > accurately captured the agreed resolutions. I plan to submit=20 > the new versions (or at least the first two) as updated I-Ds=20 > at the beginning of next week. >=20 > Thanks, > Keith. >=20 _______________________________________________ imss mailing list imss@ietf.org https://www1.ietf.org/mailman/listinfo/imss From imss-bounces@ietf.org Tue Oct 17 14:18:07 2006 Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1GZtVf-0007vN-JS; Tue, 17 Oct 2006 14:17:51 -0400 Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1GZtVe-0007vH-CB for imss@ietf.org; Tue, 17 Oct 2006 14:17:50 -0400 Received: from sj-iport-5.cisco.com ([171.68.10.87]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1GZtVc-0001B7-24 for imss@ietf.org; Tue, 17 Oct 2006 14:17:50 -0400 Received: from sj-dkim-7.cisco.com ([171.68.10.88]) by sj-iport-5.cisco.com with ESMTP; 17 Oct 2006 11:17:47 -0700 Received: from sj-core-3.cisco.com (sj-core-3.cisco.com [171.68.223.137]) by sj-dkim-7.cisco.com (8.12.11.20060308/8.12.11) with ESMTP id k9HIHl9K025535; Tue, 17 Oct 2006 11:17:47 -0700 Received: from cisco.com (pita.cisco.com [171.71.177.199]) by sj-core-3.cisco.com (8.12.10/8.12.6) with ESMTP id k9HIHhbF000733; Tue, 17 Oct 2006 11:17:43 -0700 (PDT) Received: (from kzm@localhost) by cisco.com (8.8.8-Cisco List Logging/8.8.8) id LAA11693; Tue, 17 Oct 2006 11:16:24 -0700 (PDT) From: Keith McCloghrie Message-Id: <200610171816.LAA11693@cisco.com> Subject: Re: [imss] T11 MIB issue resolutions To: dromasca@avaya.com Date: Tue, 17 Oct 2006 11:16:24 -0700 (PDT) In-Reply-To: from "Romascanu, Dan \(Dan\)" at Oct 17, 2006 01:21:23 PM X-Mailer: ELM [version 2.5 PL5] MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit DKIM-Signature: a=rsa-sha1; q=dns; l=1475; t=1161109067; x=1161973067; c=relaxed/simple; s=sjdkim7002; h=Content-Type:From:Subject:Content-Transfer-Encoding:MIME-Version; d=cisco.com; i=kzm@cisco.com; z=From:Keith=20McCloghrie=20 |Subject:Re=3A=20[imss]=20T11=20MIB=20issue=20resolutions; X=v=3Dcisco.com=3B=20h=3D47u5wGPvUCO4ofTZlfkJ8ZJy1fU=3D; b=fmbxtinwZ4Ri6TlJOV/tMkzsRY6Z2q/3W2cxToot4j+1tvUtaL7LFQNjHhPBkEkF8lLo95tx DcaScv14yhfyJRvPZnWiOdMd/PagFWktpRJT83CxCsJA1eNnXV8wAOQ5; Authentication-Results: sj-dkim-7.cisco.com; header.From=kzm@cisco.com; dkim=pass ( sig from cisco.com verified; ); X-Spam-Score: 0.0 (/) X-Scan-Signature: e1e48a527f609d1be2bc8d8a70eb76cb Cc: imss@ietf.org, bwijnen@lucent.com, Keith McCloghrie , Black_David@emc.com 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 Thanks for responding. I have just submitted the revised versions as Internet-Drafts. Keith. > Sorry for the delay in answering. OK with me. Thanks and Regards, Dan > > > -----Original Message----- > > From: Keith McCloghrie [mailto:kzm@cisco.com] > > Sent: Wednesday, October 11, 2006 11:48 PM > > To: Black_David@emc.com; bwijnen@lucent.com; Romascanu, Dan (Dan) > > Cc: imss@ietf.org > > Subject: Re: [imss] T11 MIB issue resolutions > > > > > ... > > > > > > The upshot is that the RSCN MIB will need to be held in the imss WG > > > until sometime in November when an appropriate FC-LS > > reference will be > > > available. The Fabric Configuration Server MIB and Zone Server MIB > > > should be revised to address the WG Last Call comments and > > the above > > > comments - it should be possible to request publication of > > those two > > > MIBs in the next few weeks. > > > > The revised version are available at: > > > > ftp://ftpeng.cisco.com/ftp/kzm/draft-ietf-imss-fc-zs-mib-01.txt > > ftp://ftpeng.cisco.com/ftp/kzm/draft-ietf-imss-fc-fcs-mib-01.txt > > ftp://ftpeng.cisco.com/ftp/kzm/draft-ietf-imss-fc-rscn-mib-01.txt > > > > Please could those who submitted comments check that I have > > accurately captured the agreed resolutions. I plan to submit > > the new versions (or at least the first two) as updated I-Ds > > at the beginning of next week. > > > > Thanks, > > Keith. > > > _______________________________________________ imss mailing list imss@ietf.org https://www1.ietf.org/mailman/listinfo/imss From imss-bounces@ietf.org Fri Oct 20 02:50:21 2006 Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1GaoCy-000716-Qw; Fri, 20 Oct 2006 02:50:20 -0400 Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1GaoCg-0006Iy-R8; Fri, 20 Oct 2006 02:50:03 -0400 Received: from ns1.neustar.com ([2001:503:c779:1a::9c9a:108a]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1GaoCf-0004Q9-Uf; Fri, 20 Oct 2006 02:50:02 -0400 Received: from stiedprstage1.ietf.org (stiedprstage1.va.neustar.com [10.31.47.10]) by ns1.neustar.com (Postfix) with ESMTP id DA31226E64; Fri, 20 Oct 2006 06:50:01 +0000 (GMT) Received: from ietf by stiedprstage1.ietf.org with local (Exim 4.43) id 1GaoCf-0004fo-NA; Fri, 20 Oct 2006 02:50:01 -0400 Content-Type: Multipart/Mixed; Boundary="NextPart" Mime-Version: 1.0 To: i-d-announce@ietf.org From: Internet-Drafts@ietf.org Message-Id: Date: Fri, 20 Oct 2006 02:50:01 -0400 X-Spam-Score: -2.5 (--) X-Scan-Signature: b7b9551d71acde901886cc48bfc088a6 Cc: imss@ietf.org Subject: [imss] I-D ACTION:draft-ietf-imss-fc-fcs-mib-01.txt 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 --NextPart A New Internet-Draft is available from the on-line Internet-Drafts directories. This draft is a work item of the Internet and Management Support for Storage Working Group of the IETF. Title : Fibre-Channel Fabric Configuration Server MIB Author(s) : C. DeSanti, et al. Filename : draft-ietf-imss-fc-fcs-mib-01.txt Pages : 55 Date : 2006-10-19 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 Fabric Configuration Server function of a Fibre Channel network. A URL for this Internet-Draft is: http://www.ietf.org/internet-drafts/draft-ietf-imss-fc-fcs-mib-01.txt To remove yourself from the I-D Announcement list, send a message to i-d-announce-request@ietf.org with the word unsubscribe in the body of the message. You can also visit https://www1.ietf.org/mailman/listinfo/I-D-announce to change your subscription settings. 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-imss-fc-fcs-mib-01.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-imss-fc-fcs-mib-01.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: <2006-10-19204422.I-D@ietf.org> ENCODING mime FILE /internet-drafts/draft-ietf-imss-fc-fcs-mib-01.txt --OtherAccess Content-Type: Message/External-body; name="draft-ietf-imss-fc-fcs-mib-01.txt"; site="ftp.ietf.org"; access-type="anon-ftp"; directory="internet-drafts" Content-Type: text/plain Content-ID: <2006-10-19204422.I-D@ietf.org> --OtherAccess-- --NextPart Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ imss mailing list imss@ietf.org https://www1.ietf.org/mailman/listinfo/imss --NextPart-- From imss-bounces@ietf.org Fri Oct 20 02:50:21 2006 Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1GaoCz-00071c-1K; Fri, 20 Oct 2006 02:50:21 -0400 Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1GaoCg-0006Iw-R5; Fri, 20 Oct 2006 02:50:03 -0400 Received: from ns1.neustar.com ([2001:503:c779:1a::9c9a:108a]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1GaoCf-0004QA-Uu; Fri, 20 Oct 2006 02:50:02 -0400 Received: from stiedprstage1.ietf.org (stiedprstage1.va.neustar.com [10.31.47.10]) by ns1.neustar.com (Postfix) with ESMTP id D9AF726E63; Fri, 20 Oct 2006 06:50:01 +0000 (GMT) Received: from ietf by stiedprstage1.ietf.org with local (Exim 4.43) id 1GaoCf-0004fr-OO; Fri, 20 Oct 2006 02:50:01 -0400 Content-Type: Multipart/Mixed; Boundary="NextPart" Mime-Version: 1.0 To: i-d-announce@ietf.org From: Internet-Drafts@ietf.org Message-Id: Date: Fri, 20 Oct 2006 02:50:01 -0400 X-Spam-Score: -2.5 (--) X-Scan-Signature: 3002fc2e661cd7f114cb6bae92fe88f1 Cc: imss@ietf.org Subject: [imss] I-D ACTION:draft-ietf-imss-fc-rscn-mib-01.txt 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 --NextPart A New Internet-Draft is available from the on-line Internet-Drafts directories. This draft is a work item of the Internet and Management Support for Storage Working Group of the IETF. Title : Fibre Channel Registered State Change Notification (RSCN) MIB Author(s) : C. DeSanti, et al. Filename : draft-ietf-imss-fc-rscn-mib-01.txt Pages : 32 Date : 2006-10-19 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 management of Fibre Channel's Registered State Change Notifications (RSCNs). A URL for this Internet-Draft is: http://www.ietf.org/internet-drafts/draft-ietf-imss-fc-rscn-mib-01.txt To remove yourself from the I-D Announcement list, send a message to i-d-announce-request@ietf.org with the word unsubscribe in the body of the message. You can also visit https://www1.ietf.org/mailman/listinfo/I-D-announce to change your subscription settings. 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-imss-fc-rscn-mib-01.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-imss-fc-rscn-mib-01.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: <2006-10-19204636.I-D@ietf.org> ENCODING mime FILE /internet-drafts/draft-ietf-imss-fc-rscn-mib-01.txt --OtherAccess Content-Type: Message/External-body; name="draft-ietf-imss-fc-rscn-mib-01.txt"; site="ftp.ietf.org"; access-type="anon-ftp"; directory="internet-drafts" Content-Type: text/plain Content-ID: <2006-10-19204636.I-D@ietf.org> --OtherAccess-- --NextPart Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ imss mailing list imss@ietf.org https://www1.ietf.org/mailman/listinfo/imss --NextPart-- From imss-bounces@ietf.org Fri Oct 20 15:51:43 2006 Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1Gb0P4-0008Im-Ll; Fri, 20 Oct 2006 15:51:38 -0400 Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1Gb0O1-0006T9-EL; Fri, 20 Oct 2006 15:50:33 -0400 Received: from stsc1260-eth-s1-s1p1-vip.va.neustar.com ([156.154.16.129] helo=chiedprmail1.ietf.org) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1Gb0O1-0001A2-Bq; Fri, 20 Oct 2006 15:50:33 -0400 Received: from ns3.neustar.com ([156.154.24.138]) by chiedprmail1.ietf.org with esmtp (Exim 4.43) id 1Gb0O1-00060H-23; Fri, 20 Oct 2006 15:50:33 -0400 Received: from stiedprstage1.ietf.org (stiedprstage1.va.neustar.com [10.31.47.10]) by ns3.neustar.com (Postfix) with ESMTP id BD2F8175FA; Fri, 20 Oct 2006 19:50:02 +0000 (GMT) Received: from ietf by stiedprstage1.ietf.org with local (Exim 4.43) id 1Gb0NW-0001ua-Aj; Fri, 20 Oct 2006 15:50:02 -0400 Content-Type: Multipart/Mixed; Boundary="NextPart" Mime-Version: 1.0 To: i-d-announce@ietf.org From: Internet-Drafts@ietf.org Message-Id: Date: Fri, 20 Oct 2006 15:50:02 -0400 X-Spam-Score: -2.5 (--) X-Scan-Signature: 31247fb3be228bb596db9127becad0bc Cc: imss@ietf.org Subject: [imss] I-D ACTION:draft-ietf-imss-fc-zs-mib-01.txt 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 --NextPart A New Internet-Draft is available from the on-line Internet-Drafts directories. This draft is a work item of the Internet and Management Support for Storage Working Group of the IETF. Title : Fibre-Channel Zone Server MIB Author(s) : C. DeSanti, et al. Filename : draft-ietf-imss-fc-zs-mib-01.txt Pages : 91 Date : 2006-10-20 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 a Fibre Channel Zone Server. A URL for this Internet-Draft is: http://www.ietf.org/internet-drafts/draft-ietf-imss-fc-zs-mib-01.txt To remove yourself from the I-D Announcement list, send a message to i-d-announce-request@ietf.org with the word unsubscribe in the body of the message. You can also visit https://www1.ietf.org/mailman/listinfo/I-D-announce to change your subscription settings. 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-imss-fc-zs-mib-01.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-imss-fc-zs-mib-01.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: <2006-10-20141813.I-D@ietf.org> ENCODING mime FILE /internet-drafts/draft-ietf-imss-fc-zs-mib-01.txt --OtherAccess Content-Type: Message/External-body; name="draft-ietf-imss-fc-zs-mib-01.txt"; site="ftp.ietf.org"; access-type="anon-ftp"; directory="internet-drafts" Content-Type: text/plain Content-ID: <2006-10-20141813.I-D@ietf.org> --OtherAccess-- --NextPart Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ imss mailing list imss@ietf.org https://www1.ietf.org/mailman/listinfo/imss --NextPart--