[imss] AD review of: draft-ietf-imss-fc-rtm-mib-02.txt
"Wijnen, Bert (Bert)" <bwijnen@lucent.com> Mon, 06 March 2006 18:34 UTC
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1FGKXR-0005zv-7R; Mon, 06 Mar 2006 13:34:33 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1FGKXP-0005zW-Lx for imss@ietf.org; Mon, 06 Mar 2006 13:34:31 -0500
Received: from ihemail2.lucent.com ([192.11.222.163]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1FGKXP-0004y5-Cr for imss@ietf.org; Mon, 06 Mar 2006 13:34:31 -0500
Received: from nl0006exch001h.wins.lucent.com (h135-85-76-62.lucent.com [135.85.76.62]) by ihemail2.lucent.com (8.12.11/8.12.11) with ESMTP id k26IXsW7003700; Mon, 6 Mar 2006 12:33:55 -0600 (CST)
Received: by nl0006exch001h.nl.lucent.com with Internet Mail Service (5.5.2657.72) id <DVB459LN>; Mon, 6 Mar 2006 19:33:54 +0100
Message-ID: <7D5D48D2CAA3D84C813F5B154F43B155097B8DCF@nl0006exch001u.nl.lucent.com>
From: "Wijnen, Bert (Bert)" <bwijnen@lucent.com>
To: Black_David@emc.com, cds@cisco.com, skode@cisco.com, "Keith McCloghrie (E-mail)" <kzm@cisco.com>, sgai@cisco.com
Date: Mon, 06 Mar 2006 19:33:52 +0100
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2657.72)
Content-Type: text/plain
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 4d87d2aa806f79fed918a62e834505ca
Cc: "Imss (E-mail)" <imss@ietf.org>, "Dan Romascanu (E-mail)" <dromasca@avaya.com>
Subject: [imss] AD review of: draft-ietf-imss-fc-rtm-mib-02.txt
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 document is ready for IETF Last Call. One topic that I would prefer to see addressed: - When I see: t11FcRouteDestAddrId OBJECT-TYPE SYNTAX FcAddressIdOrZero MAX-ACCESS not-accessible STATUS current DESCRIPTION "The destination Fibre Channel Address Identifier of this route. A zero-length string for this field is not allowed." ::= { t11FcRouteEntry 1 } I then wonder why the syntax is not: SYNTAX FcAddressIdOrZero (SIZE(3)) So that the restriction that zero-length is not allowed is also machine readable. COuld be addressesd after IETF Last Call, even with an RFC-Editor note. Mainly have some NITs below. You may consider them as initial IETF Last Call comments. Let me know if you rather do a new rev first or if you prefer to do IETF LC now. I will probably let IETF LC extend beyond the IETF week, because people are probably busy reviewing documents for the IETF week itself. - t11FcRouteRowStatus has a pretty meager DESCRIPTION clause For example, from the DESCRIPTION clause of t11FcRouteIfDown it seems that maybe a 'destroy' to the RowStatus object may not take immediate effect? You might want to describe that. It is also unclear if any writeable objects can be written when a row is active? - The 4 OBJECT clauses that you did as comments in the MODULE-COMPLIANCE are normally put as comments inside the DESCRIPTION clause of the MODULE-COMPLIANCE clause itself. That way the text is better kept when MIB module gets extracted from RFC. Not a blocking comment though. - Section 7 seems redundant with the back matter, and might as well be removed. - In the references section, are the details for [FC-SW-4] now known? If so, might want to fill them out. Bert _______________________________________________ imss mailing list imss@ietf.org https://www1.ietf.org/mailman/listinfo/imss
- [imss] AD review of: draft-ietf-imss-fc-rtm-mib-0… Wijnen, Bert (Bert)
- [imss] RE: AD review of: draft-ietf-imss-fc-rtm-m… Wijnen, Bert (Bert)