[Ips] RE: Gen-ART review of draft-ietf-ips-scsi-mib-08
Black_David@emc.com Tue, 17 January 2006 16:03 UTC
Received: from localhost.cnri.reston.va.us ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1EytJM-0001PK-DZ; Tue, 17 Jan 2006 11:03:56 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1EytJJ-0001Oy-6N; Tue, 17 Jan 2006 11:03:55 -0500
Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA26711; Tue, 17 Jan 2006 11:02:28 -0500 (EST)
From: Black_David@emc.com
Received: from mexforward.lss.emc.com ([168.159.213.200]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1EytRR-0005d4-JS; Tue, 17 Jan 2006 11:12:19 -0500
Received: from mailhub.lss.emc.com (nirah.lss.emc.com [10.254.144.13]) by mexforward.lss.emc.com (Switch-3.1.0/Switch-3.1.7) with ESMTP id k0HG3ED4014279; Tue, 17 Jan 2006 11:03:14 -0500 (EST)
Received: from MAHO3MSX2.corp.emc.com (maho3msx2.corp.emc.com [128.221.11.32]) by mailhub.lss.emc.com (Switch-3.1.6/Switch-3.1.7) with ESMTP id k0HG2sOo011857; Tue, 17 Jan 2006 11:02:54 -0500 (EST)
Received: by maho3msx2.corp.emc.com with Internet Mail Service (5.5.2653.19) id <CKRHW82J>; Tue, 17 Jan 2006 11:02:50 -0500
Message-ID: <F222151D3323874393F83102D614E055013E906C@CORPUSMX20A.corp.emc.com>
To: harald@alvestrand.no, gen-art@ietf.org
Date: Tue, 17 Jan 2006 11:02:36 -0500
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.1.0.0, Antispam-Data: 2006.01.17.073105
X-PerlMx-Spam: Gauge=, SPAM=0%, Reasons='EMC_BODY_1+ -5, EMC_FROM_00+ -3, IP_HTTP_ADDR 0, 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.3 (/)
X-Scan-Signature: 1449ead51a2ff026dcb23465f5379250
Cc: mbakke@cisco.com, marjorie_krueger@hp.com, mankin@psg.com, yaronled@bezeqint.net, ips@ietf.org, michele@sanrad.com, kzm@cisco.com, Black_David@emc.com
Subject: [Ips] RE: Gen-ART review of draft-ietf-ips-scsi-mib-08
X-BeenThere: ips@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: IP Storage <ips.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ips>, <mailto:ips-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ips@ietf.org>
List-Help: <mailto:ips-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ips>, <mailto:ips-request@ietf.org?subject=subscribe>
Sender: ips-bounces@ietf.org
Errors-To: ips-bounces@ietf.org
Harald, Thanks for the review. We clearly need to respin the document. Let me try to deal with your comments, as I'm the responsible WG chair: > [SAM-2] and [SPC2] are normative references (defines format for ScsiLUN and > other things), but are listed as Working Drafts in the REFERENCE clauses of > multiple MIB objects. (In the references section, the draftness seems > implied by the URL only) > Is this stable enough for an IETF standard reference? > Or are the references in the MIB wrong? The answer to both questions is "yes", and there are two issues here: (1) The REFERENCE clauses are wrong, even though the content of the referenced document is the same as what should have been referenced, and that content is stable. The correct references are those given in the normative references section, namely ANSI INCITS 366-2003 and ANSI INCITS 351-2001, and those need to be used in the REFERENCE clauses. (2) For the normative references, the actual references are to the real standards (ANSI INCITS), which one is expected to pay for. T10 makes the final working drafts available at the URLs given in the references, with the following disclaimer: This page includes the T10 working draft documents. There are no approved (official) standards here. Once a standard is approved, you should buy it from ANSI (+1-212-642-4900). Your payment insures that you receive the actual standard with all the final changes and it supports the standards process. In most cases, the final T10 committee working draft revision for a project is retained here. The drafts are used by T10 Committee members for reference. In case of any conflict, the published ANSI standard prevails. Issue (1) is sufficient to require a respin of the document - IMHO, any change to MIB content requires a respin, lest the RFC Editor do something that prevents the MIB from compiling, and there's an actual change to MIB content needed to deal with something else you found. Issue (2) is more subtle. The URLs are in the draft in order to facilitate development and technical review of the MIB. They should stay there until at least completion of IESG review (and T10 has no problem with this), but probably should be introduced as "final draft available at <URL>". I suggest use of a note to the RFC Editor (in the revised draft) to remove the URLs, so that they remain available for IESG review purposes. A quick check of other IETF documents (published RFCs and drafts in the RFC Editor queue) suggests that we have not included URLs for these sorts of references in the past. This URL issue also affects some of the informative reference. Thanks for catching this. > The term "running at high speed" is a gating criterion for whether or not > the HS counters are mandatory, but I can't see that it's defined in a > testable way. Might have missed it - it would logically seem to belong in > section 7.5. Unfortunately, it's fuzzy and not testable in all cases. Here's what RFC 4181 (Section 4.6.1.2) has to say about this issue: Henceforth "standard" MIB modules MAY use the Counter64 type when it makes sense to do so, and MUST use Counter64 if the information being modelled would wrap in less than one hour if the Counter32 type was used instead. It clearly "makes sense" to use the Counter64 type, as there are SCSI implementations that clearly need it based on the "would wrap in less than one hour" criterion. Would adapting the quoted RFC 4181 text (with a reference to RFC 4181) be sufficient to satisfy your concern? > The scsiDscTgtTable and scsiAuthorizedIntr table seem to form "access > lists". They seem to be read-write via SNMP. Should this be explicitly > mentioned in the intro in section 5? > The security considerations for these objects are very good, and make it > very clear that they're writable! It wouldn't hurt to add statements that they are potentially writable - note that the compliance section contains numerous statements saying that write access is not required. > SAS (Serial Attached SCSI) is not mentioned at all. Is it irrelevant, or > "just another transport"? Or is this what's called "scsiTransportSBP"? None of the above - SBP is SCSI over IEEE 1394 (Firewire). SAS is different, important and definitely should be added - one more reason for a respin. 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 ---------------------------------------------------- > -----Original Message----- > From: Harald Tveit Alvestrand [mailto:harald@alvestrand.no] > Sent: Tuesday, January 17, 2006 10:03 AM > To: gen-art@ietf.org > Cc: mankin@psg.com; Black, David; ips@ietf.org; > michele@sanrad.com; mbakke@cisco.com; yaronled@bezeqint.net; > marjorie_krueger@hp.com; kzm@cisco.com > Subject: Gen-ART review of draft-ietf-ips-scsi-mib-08 > > This is a Gen-ART review. > For Gen-ART info, see this > URL:<http://www.alvestrand.no/ietf/gen/art/gen-art-FAQ.html> > > Document: draft-ietf-ips-scsi-mib-08.txt > Reviewer: Harald Alvestrand > Date: Jan 17, 2006 > Summary: Excellent document, two important comments. > > I enjoyed reading this document! - the intro to SCSI and its history was > fun to read! > ---------------------------------------------------------- > Two important questions, that may warrant a respin of the document if I'm > right that there's a problem here: > > [SAM-2] and [SPC2] are normative references (defines format for ScsiLUN and > other things), but are listed as Working Drafts in the REFERENCE clauses of > multiple MIB objects. (In the references section, the draftness seems > implied by the URL only) > Is this stable enough for an IETF standard reference? > Or are the references in the MIB wrong? > > The term "running at high speed" is a gating criterion for whether or not > the HS counters are mandatory, but I can't see that it's defined in a > testable way. Might have missed it - it would logically seem to belong in > section 7.5. > ------------------------------------------------------------- > Questions, that I'd like to have answered in email, but don't warrant a > respin in my opinion: > > The scsiDscTgtTable and scsiAuthorizedIntr table seem to form "access > lists". They seem to be read-write via SNMP. Should this be explicitly > mentioned in the intro in section 5? > The security considerations for these objects are very good, and make it > very clear that they're writable! > > SAS (Serial Attached SCSI) is not mentioned at all. Is it irrelevant, or > "just another transport"? Or is this what's called "scsiTransportSBP"? > ------------------------------------------------------------- > Nits, which IMHO you can fix or not as you feel like: > > Some byzantine sentences... > > 7.3 "another logical unit changes its status to from available" is missing > something > > 7.4 "at 10GBit/second with 512 read/write operations" seems to be missing a > byte :-) > > RFC 2119 is listed as an informative reference. I think it needs to be > normative. > _______________________________________________ Ips mailing list Ips@ietf.org https://www1.ietf.org/mailman/listinfo/ips
- [Ips] RE: Gen-ART review of draft-ietf-ips-scsi-m… Black_David
- [Ips] RE: [Gen-art] RE: Gen-ART review of draft-i… Black_David
- [Ips] Gen-ART review of draft-ietf-ips-scsi-mib-08 Harald Tveit Alvestrand
- [Ips] RE: Gen-ART review of draft-ietf-ips-scsi-m… Harald Tveit Alvestrand