[storm] Gen-ART Review of draft-ietf-storm-iscsimib-03.txt

"Romascanu, Dan (Dan)" <dromasca@avaya.com> Sun, 27 January 2013 17:04 UTC

Return-Path: <dromasca@avaya.com>
X-Original-To: storm@ietfa.amsl.com
Delivered-To: storm@ietfa.amsl.com
Received: from localhost (localhost []) by ietfa.amsl.com (Postfix) with ESMTP id 387FC21F84E9; Sun, 27 Jan 2013 09:04:47 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -103.391
X-Spam-Status: No, score=-103.391 tagged_above=-999 required=5 tests=[AWL=0.208, BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([]) by localhost (ietfa.amsl.com []) (amavisd-new, port 10024) with ESMTP id M6zIkIYhl9sa; Sun, 27 Jan 2013 09:04:46 -0800 (PST)
Received: from co300216-co-outbound.net.avaya.com (co300216-co-outbound.net.avaya.com []) by ietfa.amsl.com (Postfix) with ESMTP id 6A7E821F8484; Sun, 27 Jan 2013 09:04:46 -0800 (PST)
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-AV: E=Sophos;i="4.84,541,1355115600"; d="scan'208";a="386218418"
Received: from unknown (HELO p-us1-erheast.us1.avaya.com) ([]) by co300216-co-outbound.net.avaya.com with ESMTP; 27 Jan 2013 12:04:28 -0500
Received: from unknown (HELO AZ-FFEXHC01.global.avaya.com) ([]) by p-us1-erheast-out.us1.avaya.com with ESMTP; 27 Jan 2013 12:04:38 -0500
Received: from AZ-FFEXMB04.global.avaya.com ([fe80::6db7:b0af:8480:c126]) by AZ-FFEXHC01.global.avaya.com ([]) with mapi id 14.02.0328.009; Sun, 27 Jan 2013 12:05:01 -0500
From: "Romascanu, Dan (Dan)" <dromasca@avaya.com>
To: "gen-art@ietf.org" <gen-art@ietf.org>
Thread-Topic: Gen-ART Review of draft-ietf-storm-iscsimib-03.txt
Thread-Index: Ac38ru1wNGisP6GHRvWY2E+60/tmIw==
Date: Sun, 27 Jan 2013 17:05:00 +0000
Message-ID: <9904FB1B0159DA42B0B887B7FA8119CA07867E@AZ-FFEXMB04.global.avaya.com>
Accept-Language: en-US
Content-Language: en-US
x-originating-ip: []
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-Mailman-Approved-At: Sun, 03 Feb 2013 13:08:45 -0800
Cc: "prakashvn@hcl.com" <prakashvn@hcl.com>, "storm@ietf.org" <storm@ietf.org>
Subject: [storm] Gen-ART Review of draft-ietf-storm-iscsimib-03.txt
X-BeenThere: storm@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Storage Maintenance WG <storm.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/storm>, <mailto:storm-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/storm>
List-Post: <mailto:storm@ietf.org>
List-Help: <mailto:storm-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/storm>, <mailto:storm-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sun, 27 Jan 2013 17:04:47 -0000

(I missed one of the authors at the first send)

I am the assigned Gen-ART reviewer for this draft. For background on Gen-ART, please see the FAQ at < http://wiki.tools.ietf.org/area/gen/trac/wiki/GenArtfaq>gt;.

Please wait for direction from your document shepherd or AD before posting a new version of the draft.

Document: draft-ietf-storm-iscsimib-03.txt
Reviewer: Dan Romascanu
Review Date: 1/27/13
IETF LC End Date: 1/28/13
IESG Telechat date: (if known)

Summary: Almost Ready

Major issues:

1) This document will obsolete (when approved) RFC 4544, and add support for iSCSI protocol evolution according to the consolidated version of the iSCSI protocol (as per draft-ietf-storm-iscsi-cons) and for the updates to iSCSI (as per draft-ietf-storm-iscsi-sam) for ProtocolLevel. There is no indication however in for the operators when an upgrade is recommended or becomes mandatory, and which version of the protocol is to be used during the transition, function of the iSCSI versions of the protocol.  

2) A number of changes where agreed by the WG, as reflected in the message http://www.ietf.org/mail-archive/web/storm/current/msg00652.html, according to which: 

> In order to move forward, I suggest that the authors make the functional changes [1] - [6], not make changes [A] - [F] and [I}, and use their best judgment on what (if anything) to do about [G] and [H]

My understanding is that the changes [1]-[6] were implemented, and the authors applying their best judgment did not implement [G] and [H]. However, changes [1]-[6] are npt reflected in Section 5. 

3) I did not perform a MIB Doctor review of the document. I notice however that the text Security Considerations section and the corresponding references do not conform to the latest version of the guidelines for the Security Considerations sections in MIB documents, as per https://svn.tools.ietf.org/area/ops/trac/wiki/mib-security#

Minor issues:

Nits/editorial comments: