[imss] RE: imss WG Last Call: FC-SP MIB

"WIJNEN, Bert \(Bert\)" <bwijnen@alcatel-lucent.com> Fri, 02 November 2007 15:08 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 1Iny8e-0007dP-32; Fri, 02 Nov 2007 11:08:48 -0400
Received: from imss by megatron.ietf.org with local (Exim 4.43) id 1Iny8c-0007dB-V6 for imss-confirm+ok@megatron.ietf.org; Fri, 02 Nov 2007 11:08:46 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1Iny8c-0007d3-LZ for imss@ietf.org; Fri, 02 Nov 2007 11:08:46 -0400
Received: from ihemail4.lucent.com ([135.245.0.39]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1Iny8X-0000tT-DJ for imss@ietf.org; Fri, 02 Nov 2007 11:08:46 -0400
Received: from ilexp01.ndc.lucent.com (h135-3-39-1.lucent.com [135.3.39.1]) by ihemail4.lucent.com (8.13.8/IER-o) with ESMTP id lA2F7FSG027782; Fri, 2 Nov 2007 10:08:22 -0500 (CDT)
Received: from DEEXP01.de.lucent.com ([135.248.187.65]) by ilexp01.ndc.lucent.com with Microsoft SMTPSVC(6.0.3790.1830); Fri, 2 Nov 2007 10:07:24 -0500
Received: from DEEXC1U02.de.lucent.com ([135.248.187.29]) by DEEXP01.de.lucent.com with Microsoft SMTPSVC(6.0.3790.1830); Fri, 2 Nov 2007 16:07:22 +0100
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: Fri, 02 Nov 2007 16:07:21 +0100
Message-ID: <D4D321F6118846429CD792F0B5AF471F7E5BF4@DEEXC1U02.de.lucent.com>
In-Reply-To: <FF29F13E2D78C047B4B79F4E062D0363387A95@CORPUSMX20A.corp.emc.com>
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
Thread-Topic: imss WG Last Call: FC-SP MIB
Thread-Index: AcgK0vLbbD32Q+kDSKqF52DDcvyXNQR1sm7QACzkDYA=
References: <FF29F13E2D78C047B4B79F4E062D036338796C@CORPUSMX20A.corp.emc.com> <FF29F13E2D78C047B4B79F4E062D0363387A95@CORPUSMX20A.corp.emc.com>
From: "WIJNEN, Bert (Bert)" <bwijnen@alcatel-lucent.com>
To: Black_David@emc.com, imss@ietf.org
X-OriginalArrivalTime: 02 Nov 2007 15:07:22.0185 (UTC) FILETIME=[11BFEB90:01C81D62]
X-Scanned-By: MIMEDefang 2.57 on 135.245.2.39
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 67c1ea29f88502ef6a32ccec927970f0
Cc:
Subject: [imss] RE: 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

David,

Things are not going as I wanted. 
I was on vacation for a week, just returned this morning.

I have serious workload next week that I must give priority.
The week after I am at IEEE 802.1 meetings (with quite a bit
of MIB related work as well). So It seem it will be at least in
the last week of November that I can seriously get to it (I had
planned (in fact I started) to do so earlier). But it is
also possible that yet other high priority activities get in the 
way at that time. Can't elaborate now on that though.

I will not feel offended if you do not want to wait for that 
and instead look for another MIB Doctor for review.

Bert Wijnen  

> -----Original Message-----
> From: Black_David@emc.com [mailto:Black_David@emc.com] 
> Sent: Thursday, November 01, 2007 6:10 PM
> To: imss@ietf.org; WIJNEN, Bert (Bert)
> Cc: Black_David@emc.com
> Subject: RE: imss WG Last Call: FC-SP MIB
> 
> The WG Last Call on this MIB has ended, but in addition to my 
> comments, I think it would be prudent to wait for Bert to 
> finish wading through this MIB before producing a revised 
> version and submitting it to the ADs/IESG.
> 
> Bert - do you have a timeframe for completing your review.
> 
> Thanks,
> --David (imss WG chair)
> ----------------------------------------------------
> David L. Black, Distinguished Engineer
> 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
> > Sent: Tuesday, October 09, 2007 8:18 PM
> > To: 'imss@ietf.org'
> > Cc: Black, David; 'Romascanu, Dan (Dan)'
> > Subject: imss WG Last Call: FC-SP MIB
> > Importance: High
> > 
> > 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