[Gen-art] Gen-ART review of draft-ietf-imss-fc-rtm-mib-04.txt
"Spencer Dawkins" <spencer@mcsr-labs.org> Fri, 05 May 2006 11:30 UTC
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1FbyVt-00035g-US; Fri, 05 May 2006 07:30:25 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1FbyVt-00035b-3j for gen-art@ietf.org; Fri, 05 May 2006 07:30:25 -0400
Received: from rwcrmhc11.comcast.net ([216.148.227.151]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1FbyVr-0007aw-Ot for gen-art@ietf.org; Fri, 05 May 2006 07:30:25 -0400
Received: from s73602 (c-66-31-44-141.hsd1.ma.comcast.net[66.31.44.141]) by comcast.net (rwcrmhc11) with SMTP id <20060505113022m1100o6e9ue>; Fri, 5 May 2006 11:30:22 +0000
Message-ID: <0ea301c67037$4e126b60$0600a8c0@china.huawei.com>
From: Spencer Dawkins <spencer@mcsr-labs.org>
To: General Area Review Team <gen-art@ietf.org>
References: <098e01c66403$c0fd40e0$0700a8c0@china.huawei.com>
Subject: [Gen-art] Gen-ART review of draft-ietf-imss-fc-rtm-mib-04.txt
Date: Fri, 05 May 2006 07:30:19 -0400
MIME-Version: 1.0
Content-Type: text/plain; format="flowed"; charset="iso-8859-1"; reply-type="response"
Content-Transfer-Encoding: 7bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 6.00.2900.2869
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.2869
X-Spam-Score: 0.0 (/)
X-Scan-Signature: f66b12316365a3fe519e75911daf28a8
Cc: "Romascanu, Dan (Dan)" <dromasca@avaya.com>, sgai@cisco.com, skode@cisco.com, cds@cisco.com, kzm@cisco.com
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/gen-art>, <mailto:gen-art-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www1.ietf.org/pipermail/gen-art>
List-Post: <mailto:gen-art@ietf.org>
List-Help: <mailto:gen-art-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/gen-art>, <mailto:gen-art-request@ietf.org?subject=subscribe>
Errors-To: gen-art-bounces@ietf.org
Version 04 addresses all the comments I had in my review of 03. From my perspective, ready for publication as a Proposed Standard. Thanks, Spencer >I was selected as General Area Review Team reviewer for this specification > (for background on Gen-ART, please see > http://www.alvestrand.no/ietf/gen/art/gen-art-FAQ.html). > > Summary: This document is almost ready for publication as a Proposed > Standard. I do have a question on Section 5.3, listed below. > > I also identified two editorial comments (not part of the Gen-ART review > for Brian). I hope this is useful. > > Thanks, > > 1. Introduction > > This memo defines a portion of the Management Information Base (MIB) > for use with network management protocols in the Internet community. > In particular, it describes managed objects for information related > to the Fibre Channel network's Routing Table for routing within a > Fabric. Managed objects specific to particular routing protocols, > such as FSPF, are not specified in this MIB module. > > Spencer (NIT): FSPF is not exanded until later in the document (and should > have the reference to [FC-SW-4] that doesn't appear until Section 4). > Suggest "... such as Fabric Shortest Path First (FSPF) protocol [FC-SW-4], > ..." as replacement text. > > 5.3. Fabric Index > > The latest standard for an interconnecting Fabric containing multiple > Fabric Switch elements is [FC-SW-4] (which replaces the previous > revision [FC-SW-3]). [FC-SW-4] specifies the operation of both a > single Fabric in a physical infrastructure, as well as the support of > multiple Virtual Fabrics operating within one (or more) physical > infrastructures. Whether operating on a physical Fabric (i.e., > without Virtual Fabrics) or within a Virtual Fabric, the operation of > FSPF within a Fabric is identical. Therefore, this MIB defines all > Fabric-related information in tables which are INDEX-ed by an > arbitrary integer, named a "Fabric Index", the syntax of which is > IMPORTed from the T11-TC-MIB. When a device is connected to a single > physical Fabric, without use of any virtual Fabrics, the value of > this Fabric Index will always be 1. In an environment of multiple > virtual and/or physical Fabrics, this index provides a means to > distinguish one Fabric from another. > > Spencer: I can guess what a Virtual Fabric is, but I'm guessing and the > term hasn't been introduced yet, and there's no reference for it. Not a > critical problem, but since there's a nice overview in Section 3, maybe it > could have a sentence or two that introduces the concept, before it > appears in Section 5.3? > > 5.5. The t11FcRouteTable's INDEX > > Providing the same useful feature in the MIB in this document, > results in having an unusually large number (ten) of objects in the > t11FcRouteTable's INDEX clause. However, all ten are either integers > or strings of length 0 or 3 octets. Thus, the aggregate number of > sub-identifiers to be appended to an OBJECT-TYPE's OID when naming an > instance of an object in this table, is at most 22 sub-identifiers, > i.e., less than the *minimum* number to be appended for the > inetCidrRouteTable table. In other words, while ten is an unusually > large number of objects in an INDEX clause, the resultant OIDs are > not unusually large. > > Spencer (more than a NIT): This paragraph is really tortured, until you > get to the last sentence, which seems all that's needed anyway (suggest > "While this useful feature results in an unusually large number (ten) of > objects in the t11FcRouteTable's INDEX clause, all ten are all ten are > either integers or strings of length 0 or 3 octets, so the resulting OIDs > are not unusually large."). But the reason I flagged this as "more than a > nit" was that "length 0 or 3 octets" was confusing - the point is, > "maximum length of 3 octets", isn't it? FC people are very aware of > FCAddressIdentifier structure, but no one else is, so "0 or 3 octets" is a > distraction, and the wordy paragraph just made it worse. > > > _______________________________________________ > Gen-art mailing list > Gen-art@ietf.org > https://www1.ietf.org/mailman/listinfo/gen-art > _______________________________________________ Gen-art mailing list Gen-art@ietf.org https://www1.ietf.org/mailman/listinfo/gen-art
- [Gen-art] Gen-ART review of draft-ietf-imss-fc-rt… Spencer Dawkins
- Re: [Gen-art] Gen-ART review of draft-ietf-imss-f… Spencer Dawkins
- [Gen-art] Re: Gen-ART review of draft-ietf-imss-f… Keith McCloghrie
- [Gen-art] Re: Gen-ART review of draft-ietf-imss-f… Spencer Dawkins
- [Gen-art] Re: Gen-ART review of draft-ietf-imss-f… Keith McCloghrie
- [Gen-art] RE: Gen-ART review of draft-ietf-imss-f… Romascanu, Dan (Dan)
- [Gen-art] Re: Gen-ART review of draft-ietf-imss-f… Keith McCloghrie
- [Gen-art] Re: Gen-ART review of draft-ietf-imss-f… Spencer Dawkins
- [Gen-art] Re: Gen-ART review of draft-ietf-imss-f… Keith McCloghrie
- [Gen-art] RE: Gen-ART review of draft-ietf-imss-f… Romascanu, Dan (Dan)
- [Gen-art] Gen-ART review of draft-ietf-imss-fc-rt… Spencer Dawkins
- [Gen-art] Re: Gen-ART review of draft-ietf-imss-f… Keith McCloghrie
- [Gen-art] Re: Gen-ART review of draft-ietf-imss-f… Suresh Krishnan
- [Gen-art] Re: Gen-ART review of draft-ietf-imss-f… Henrik Levkowetz
- Re: [Gen-art] (full) review of draft-ietf-imss-fc… Keith McCloghrie
- Re: [Gen-art] (full) review of draft-ietf-imss-fc… Romascanu, Dan (Dan)
- Re: [Gen-art] (full) review of draft-ietf-imss-fc… Keith McCloghrie
- Re: [Gen-art] (full) review of draft-ietf-imss-fc… Romascanu, Dan (Dan)