[imss] imss WG Last Call: FC-SP MIB
Black_David@emc.com Wed, 10 October 2007 00:18 UTC
Return-path: <imss-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1IfPHU-0004FN-5j; Tue, 09 Oct 2007 20:18:32 -0400
Received: from imss by megatron.ietf.org with local (Exim 4.43) id 1IfPHT-0004FE-7D for imss-confirm+ok@megatron.ietf.org; Tue, 09 Oct 2007 20:18:31 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1IfPHS-00049I-SS for imss@ietf.org; Tue, 09 Oct 2007 20:18:30 -0400
Received: from mexforward.lss.emc.com ([128.222.32.20]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1IfPHE-0001SU-NM for imss@ietf.org; Tue, 09 Oct 2007 20:18:22 -0400
Received: from mailhub.lss.emc.com (nagas.lss.emc.com [10.254.144.11]) by mexforward.lss.emc.com (Switch-3.2.5/Switch-3.1.7) with ESMTP id l9A0Hsig006779; Tue, 9 Oct 2007 20:17:54 -0400 (EDT)
Received: from corpussmtp3.corp.emc.com (corpussmtp3.corp.emc.com [10.254.64.53]) by mailhub.lss.emc.com (Switch-3.2.5/Switch-3.1.7) with ESMTP id l9A0Hg0b013137; Tue, 9 Oct 2007 20:17:53 -0400 (EDT)
From: Black_David@emc.com
Received: from CORPUSMX20A.corp.emc.com ([128.221.62.11]) by corpussmtp3.corp.emc.com with Microsoft SMTPSVC(6.0.3790.1830); Tue, 9 Oct 2007 20:17:46 -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: Tue, 09 Oct 2007 20:17:33 -0400
Message-ID: <FF29F13E2D78C047B4B79F4E062D036338796C@CORPUSMX20A.corp.emc.com>
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
Thread-Topic: imss WG Last Call: FC-SP MIB
thread-index: AcgK0vLbbD32Q+kDSKqF52DDcvyXNQ==
X-Priority: 1
Priority: Urgent
Importance: high
To: imss@ietf.org
X-OriginalArrivalTime: 10 Oct 2007 00:17:46.0741 (UTC) FILETIME=[FC014250:01C80AD2]
X-PMX-Version: 4.7.1.128075, Antispam-Engine: 2.5.1.298604, Antispam-Data: 2007.8.30.53115
X-PerlMx-Spam: Gauge=, SPAM=0%, Reason='EMC_BODY_1+ -3, EMC_FROM_0+ -3, PRIORITY_NO_NAME 0.716, NO_REAL_NAME 0, __C230066_P5 0, __CP_NOT_1 0, __CT 0, __CTE 0, __CT_TEXT_PLAIN 0, __HAS_MSGID 0, __HAS_X_PRIORITY 0, __IMS_MSGID 0, __MIME_TEXT_ONLY 0, __MIME_VERSION 0, __SANE_MSGID 0'
X-Spam-Score: -4.0 (----)
X-Scan-Signature: 244a2fd369eaf00ce6820a760a3de2e8
Cc: dromasca@avaya.com, Black_David@emc.com
Subject: [imss] imss WG Last Call: FC-SP MIB
X-BeenThere: imss@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Internet and Management Support for Storage Working Group <imss.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/imss>, <mailto:imss-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:imss@ietf.org>
List-Help: <mailto:imss-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/imss>, <mailto:imss-request@ietf.org?subject=subscribe>
Errors-To: imss-bounces@ietf.org
This is to announce an imss WG Last Call on the following MIB draft: MIB for Fibre-Channel Security Protocols (FC-SP) draft-ietf-imss-fc-fcsp-mib-00.txt This WG Last Call will run through 12 midnight Eastern Time on Friday, October 26, 2007 (your WG chair hopes to deal with Last Call results during the week of October 29th and hopes that any revisions can be completed prior to the November 19th Internet Draft submission cutoff for the Vancouver meeting). Technical comments *must* be sent to the imss mailing list. Editorial comments may be sent directly to the draft editor (but please cc: me): Keith McCloghrie [kzm@cisco.com] In order to try to set a good example, I have completed my WG chair review of the MIB prior to announcing this Last Call. I found two technical concerns: (1) The MIB defines precedence values for traffic selectors as opposed to implicitly presenting them in order of precedence. I guess this is ok, but Section 4.7 should explain why this approach was chosen. (2) Section 4.9 defines rate control for Authentication failures on a per-fabric granularity. That strikes me as overly coarse, and I wonder if per-SA would be a more appropriate/useful granularity. I also found a number of editorial concerns: Section 1, 2nd paragraph. Remove the sentence starting with "This latest draft" or insert an instruction to the RFC Editor to remove it before publication as an RFC. Section 3.1 - Delete "The" at the start of the first paragraph. Should Section 3.5 and subsequent subsections of Section 3 all be subsections of Section 3.4 Security? Section 3.10 - "To provide better scaling, the Switch Connectivity Objects are not Fabric-wide information such that they are distributed only to where they are needed." "information such that they are" -> information, but are" Section 3.10 introduces "Active Zone Set" but does not explain what this term means. T11FcSpPolicyNameType - the DESCRIPTION needs to explain the concept of "restricted" - how does a "restricted" entity differ from the corresponding unrestricted entity? 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
- [imss] imss WG Last Call: FC-SP MIB Black_David
- RE: [imss] imss WG Last Call: FC-SP MIB WIJNEN, Bert (Bert)
- [imss] RE: imss WG Last Call: FC-SP MIB Black_David
- [imss] RE: imss WG Last Call: FC-SP MIB WIJNEN, Bert (Bert)
- [imss] RE: imss WG Last Call: FC-SP MIB Black_David
- [imss] RE: imss WG Last Call: FC-SP MIB WIJNEN, Bert (Bert)
- [imss] MIB doctor review part 1 (SYNTAX Checks): … WIJNEN, Bert (Bert)