Re: [imss] FW: MIB Doctor review draft-ietf-imss-fc-fam-mib-01.txt
Keith McCloghrie <kzm@cisco.com> Fri, 07 October 2005 18:00 UTC
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1ENwVo-0005NN-FS; Fri, 07 Oct 2005 14:00:04 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1ENwVn-0005Mz-Dc for imss@megatron.ietf.org; Fri, 07 Oct 2005 14:00:03 -0400
Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA02993 for <imss@ietf.org>; Fri, 7 Oct 2005 14:00:01 -0400 (EDT)
Received: from sj-iport-1-in.cisco.com ([171.71.176.70] helo=sj-iport-1.cisco.com) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1ENwf7-0001Ii-Oi for imss@ietf.org; Fri, 07 Oct 2005 14:09:42 -0400
Received: from sj-core-5.cisco.com ([171.71.177.238]) by sj-iport-1.cisco.com with ESMTP; 07 Oct 2005 10:59:53 -0700
X-IronPort-AV: i="3.97,188,1125903600"; d="scan'208"; a="664303822:sNHT26370724"
Received: from cisco.com (cypher.cisco.com [171.69.11.142]) by sj-core-5.cisco.com (8.12.10/8.12.6) with ESMTP id j97Hxo4V029170; Fri, 7 Oct 2005 10:59:51 -0700 (PDT)
Received: (from kzm@localhost) by cisco.com (8.8.8-Cisco List Logging/8.8.8) id KAA07425; Fri, 7 Oct 2005 10:59:50 -0700 (PDT)
From: Keith McCloghrie <kzm@cisco.com>
Message-Id: <200510071759.KAA07425@cisco.com>
Subject: Re: [imss] FW: MIB Doctor review draft-ietf-imss-fc-fam-mib-01.txt
To: bwijnen@lucent.com
Date: Fri, 07 Oct 2005 10:59:50 -0700
In-Reply-To: <no.id> from "Wijnen, Bert (Bert)" at Oct 06, 2005 06:02:18 PM
X-Mailer: ELM [version 2.5 PL5]
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-Spam-Score: 0.0 (/)
X-Scan-Signature: b045c2b078f76b9f842d469de8a32de3
Content-Transfer-Encoding: 7bit
Cc: imss@ietf.org, orly_n@rad.co.il
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>
Sender: imss-bounces@ietf.org
Errors-To: imss-bounces@ietf.org
Bert/Orly, > WG, > here is the MIB doctor review. > > Thanks to Orly for her review! > > Pls copy her if you want her to see comments/questions/answers > because she is not subscribed to your mailing list. > > W.r.t. to the comment on th eexpired draft: it has been (or > will be soon) resurrected by the secretariat! My responses to Orly's comments are below. I have put an updated document at: ftp://ftpeng.cisco.com/ftp/kzm/draft-ietf-imss-fc-fam-mib-02.txt Let me know if/when I should submit it as the new I-D. Thanks, Keith. ===================== My responses: > The draft has expired, and has been deleted from the Internet-Drafts > directory. > ---------------------------------------------------------------------- > Here are 9 issues I found as potential items for fix: > > 1.)Format---line(738) is too long Oops, one character too many. > 2) Conformance with RFC 3978/3979 boilerplate--- > -Seems as if an old copy of those is being used in the "Status > of this Memo". > > Should be as follows: > > Status of this Memo > > By submitting this Internet-Draft, each author represents that any > applicable patent or other IPR claims of which he or she is aware > have been or will be disclosed, and any of which he or she becomes > aware will be disclosed, in accordance with Section 6 of BCP 79. > > Internet-Drafts are working documents of the Internet Engineering > Task Force (IETF), its areas, and its working groups. Note that > other groups may also distribute working documents as Internet- > Drafts. > > Internet-Drafts are draft documents valid for a maximum of six months > and may be updated, replaced, or obsoleted by other documents at any > time. It is inappropriate to use Internet-Drafts as reference > material or to cite them other than as "work in progress." > > The list of current Internet-Drafts can be accessed at > http://www.ietf.org/ietf/1id-abstracts.txt. > > The list of Internet-Draft Shadow Directories can be accessed at > http://www.ietf.org/shadow.html. > > This Internet-Draft will expire on January 13, 2006. > > Copyright Notice > > Copyright (C) The Internet Society (2005). I myself get very frustrated at the number of times that the boilerplate changes, but because of such changes, I think your replacement text is incorrect, in two ways: a) I think the IETF's requirements (aside: how can they be called "Guidelines" when non-compliant submissions are refused!!) prohibit the inclusion of: "This Internet-Draft will expire on January 13, 2006" in this section. b) idnits now complains about having a Copyright Notice near the beginning of the document !! If I had been clairvoyant enough to have submitted the I-D last February containing the version of the boilerplate which is required today, it would have been unacceptable back then. However, since I do now have to submit a revised version, I will have to change the I-D to have today's version of the boilerplate rather than last February's :-(. > 3) IPR related --- > -Disclaimer of validity (15), copyright statements (14) and IPR > (7) are marked with numbers and > listed in mixed order. > - section 7 is redundant to 15 and seems as older version > Should be as follows: > > Intellectual Property Statement > > The IETF takes no position regarding the validity or scope of any > Intellectual Property Rights or other rights that might be claimed to > pertain to the implementation or use of the technology described in > this document or the extent to which any license under such rights > might or might not be available; nor does it represent that it has > made any independent effort to identify any such rights. Information > on the procedures with respect to rights in RFC documents can be > found in BCP 78 and BCP 79. > > Copies of IPR disclosures made to the IETF Secretariat and any > assurances of licenses to be made available, or the result of an > attempt made to obtain a general license or permission for the use of > such proprietary rights by implementers or users of this > specification can be obtained from the IETF on-line IPR repository at > http://www.ietf.org/ipr. > > The IETF invites any interested party to bring to its attention any > copyrights, patents or patent applications, or other proprietary > rights that may cover technology that may be required to implement > this standard. Please address the information to the IETF at > ietf-ipr@ietf.org. > > > Disclaimer of Validity > > This document and the information contained herein are provided on an > "AS IS" basis and THE CONTRIBUTOR, THE ORGANIZATION HE/SHE REPRESENTS > OR IS SPONSORED BY (IF ANY), THE INTERNET SOCIETY AND THE INTERNET > ENGINEERING TASK FORCE DISCLAIM ALL WARRANTIES, EXPRESS OR IMPLIED, > INCLUDING BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE > INFORMATION HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED > WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE. > > > Copyright Statement > > Copyright (C) The Internet Society (2005). This document is subject > to the rights, licenses and restrictions contained in BCP 78, and > except as set forth therein, the authors retain all their rights. > > > Acknowledgment > > Funding for the RFC Editor function is currently provided by the > Internet Society. I don't know whether the above is correct without comparing it against what the "guidelines" say. To maximize the odds that my new text will be acceptable, I will replace the above with a cut-and-paste from the I-D that I submitted a couple of weeks ago which was acceptable then (and hope that the "guidelines" haven't changed since). > 4.) Abstract -- ok > > 5.) MIB Boilerplate -- ok Above you said "9 issues" -- if #4 and #5 are "-- ok", why are they issues ?? > 6.) References -- > [FC-MGMT] draft-ietf-ips-fcmgmt-mib is RFC4044 by now "Fibre Channel > Management MIB" > RFC2837, was obsoleted by RFC4044, do we really need it? Yes, RFC2837 is referenced in the text because it's part of the history, where it explains why RFC 2837 is obsolete. > 7.) Security Considerations--ok Again, why is this an issue ?? > 8.) Introduction--some redundancy exit with the abstract, maybe > combination with section 3. "Short Overview of Fibre Channel" > could have helped. I agree it is redundant to have both an Abstract and an Intoduction, but the IETF requires both, and even suggests they contain redundant information (specifically, "a satisfactory abstract can be constructed in part from material from the Introduction section"). > 9.) MIB objects-- > --there are few TCs in T11-FC-FABRIC-ADDR-MGR-MIB, why T11FabricIndex > was placed in a separate MODULE and all others not with it ? Because it was known in advance that there would be several follow-on T11-XXX-MIB modules, which would need to IMPORT T11FabricIndex. However, they would not need to IMPORT all of the TC's defined in T11-FC-FABRIC-ADDR-MGR-MIB, and they would need to define their own TC's. So, the only 100%-consistent way to have spread the TC's over the set of MIB modules would have been to delay the approval of draft-ietf-imss-fc-fam-mib until all the other T11-XXX-MIB modules were also ready to be approved, so that the T11-TC-MIB could contain all the common TC's. I did not (and still don't) believe such a delay was/is warranted by such a small increase in consistency. > Also, based on its description it seems as the range should be > (1..4095) , maybe there should be a word stating the consistency with > [FC-SW-4] > regarding the value 0. > Maybe there are good reasons for the above that I simply not aware of. Yes, I should and will add text to the DESCRIPTION, so that the explanation which is presently in the Change Log doesn't get lost when the Change Log is deleted. I'll also take this opportunity to make the DESCRIPTION more definitive (i.e., change it to "the forthcoming standard, FC-SW-4, defines how ...") which is now true, rather than using the speculative text which needed to be written previously. I'll also take this opportunity to delete the Change Log. > --T11FamState description could be easier to follow if the order of the > values-explanation was as the order in the enumeration OK. > --line:260: element #18 `t11FamPrincipalSwitchSelections' does not > match order of > columnar objects under `t11FamEntry', > 't11FamLocalPrincipalSwitchSlctns' is listed as #18 and affect the rest > that follow it. > Better have the right order as the `t11FamEntry' listed and the > corresponding OBJECT -GROUP I had already discovered this and fixed it in my source, but had not re-submitted a new version (so as to try to avoid being disruptive to the process). > --MIB layout is not as usually recommended: > +-- xxxNotifications(0) > +-- xxxObjects(1) > +-- xxxConformance(2) > > It is recommended to change > t11FamNotifications OBJECT IDENTIFIER ::= { t11FamMIBObjects 0 } > > TO: > t11FamNotifications OBJECT IDENTIFIER ::= { t11FabricAddrMgrMIB 0 } Sigh, ... OK. _______________________________________________ imss mailing list imss@ietf.org https://www1.ietf.org/mailman/listinfo/imss
- [imss] Changes to draft-ietf-imss-fc-fam-mib-00.t… Keith McCloghrie
- [imss] Re: Changes to draft-ietf-imss-fc-fam-mib-… Keith McCloghrie
- Re: [imss] Re: Changes to draft-ietf-imss-fc-fam-… Keith McCloghrie
- [imss] Re: Agenda for next week's T11.5 Managemen… Keith McCloghrie
- Re: [imss] FW: MIB Doctor review draft-ietf-imss-… Keith McCloghrie
- Re: [imss] FW: MIB Doctor review draft-ietf-imss-… Keith McCloghrie
- Re: [imss] FW: MIB Doctor review draft-ietf-imss-… Keith McCloghrie
- Re: [imss] Last Call: 'Fibre-Channel Name Server … Keith McCloghrie
- Re: [imss] Last Call: 'Fibre-Channel Name Server … Keith McCloghrie
- [imss] Re: DISCUSS on Keith McCloghrie
- [imss] Re: AD review of: draft-ietf-imss-fc-fspf-… Keith McCloghrie
- [imss] Re: AD review of: draft-ietf-imss-fc-fspf-… Keith McCloghrie
- [imss] Re: AD review of: draft-ietf-imss-fc-rtm-m… Keith McCloghrie
- [imss] Re: AD review of: draft-ietf-imss-fc-fspf-… Keith McCloghrie
- [imss] Re: AD review of: draft-ietf-imss-fc-fspf-… Claudio DeSanti
- Re: [imss] RE: AD review of: draft-ietf-imss-fc-r… Keith McCloghrie
- Re: [imss] RE: AD review of: draft-ietf-imss-fc-r… Keith McCloghrie
- Re: [imss] imss WG Last Call: Fibre Channel RSCN,… Keith McCloghrie
- Re: [imss] imss WG Last Call: Fibre Channel RSCN,… Keith McCloghrie
- Re: [imss] imss WG Last Call: Fibre Channel RSCN,… Keith McCloghrie
- Re: [imss] WG last call: draft-ietf-imss-fc-rscn-… Keith McCloghrie
- Re: [imss] imss WG Last Call: Fibre Channel RSCN,… Keith McCloghrie
- Re: [imss] WG Last Call: draft-ietf-imss-fc-fcs-m… Keith McCloghrie
- [imss] A couple of loose ends Keith McCloghrie
- Re: [imss] WG last call review: T11-FC-FABRIC-LOC… Keith McCloghrie
- Re: [imss] WG last call review: T11-FC-FABRIC-LOC… Keith McCloghrie
- Re: [imss] WG last call review: T11-FC-FABRIC-LOC… Claudio DeSanti
- Re: [imss] WG last call review: T11-FC-ZONE-SERVE… Keith McCloghrie
- Re: [imss] Last Call comments on draft-ietf-imss-… Keith McCloghrie
- RE: [imss] Last Call comments on draft-ietf-imss-… Black_David
- Re: [imss] Keith McCloghrie
- Re: [imss] Keith McCloghrie
- Re: [imss] T11 MIB issue resolutions Keith McCloghrie
- Re: [imss] T11 MIB issue resolutions Keith McCloghrie
- [imss] Rereview for draft-ietf-imss-fc-rscn-mib-0… Wijnen, Bert (Bert)
- Re: [imss] Rereview of: draft-ietf-imss-fc-fcs-mi… Keith McCloghrie
- RE: [imss] Rereview of: draft-ietf-imss-fc-fcs-mi… Black_David
- Re: [imss] re-view: T11-FC-FABRIC-LOCK-MIB in Keith McCloghrie
- RE: [imss] re-view: T11-FC-FABRIC-LOCK-MIB in Wijnen, Bert (Bert)
- Re: [imss] re-review: T11-FC-ZONE-SERVER-MIB in Keith McCloghrie
- RE: [imss] re-review: T11-FC-ZONE-SERVER-MIB in Wijnen, Bert (Bert)
- Re: [imss] Acceptance of draft-kzm-imss-fc-fcsp-m… Keith McCloghrie
- RE: [imss] Acceptance of draft-kzm-imss-fc-fcsp-m… Romascanu, Dan (Dan)
- Re: [imss] imss WG Last Call: FC-SP MIB Keith McCloghrie
- RE: [imss] imss WG Last Call: FC-SP MIB Black_David
- Re: [imss] imss WG Last Call: FC-SP MIB Keith McCloghrie
- Re: [imss] imss WG Last Call: FC-SP MIB Keith McCloghrie
- RE: [imss] imss WG Last Call: FC-SP MIB WIJNEN, Bert (Bert)
- Re: [imss] imss WG Last Call: FC-SP MIB Keith McCloghrie
- RE: [imss] imss WG Last Call: FC-SP MIB Black_David
- Re: [imss] imss WG Last Call: FC-SP MIB Keith McCloghrie
- RE: [imss] imss WG Last Call: FC-SP MIB WIJNEN, Bert (Bert)
- RE: [imss] imss WG Last Call: FC-SP MIB WIJNEN, Bert (Bert)
- Re: [imss] imss WG Last Call: FC-SP MIB Keith McCloghrie
- Re: [imss] MIB doctor review part 1 (SYNTAX Check… Keith McCloghrie
- Re: [imss] MIB doctor review part 2 (T11-FC-SP-TC… Keith McCloghrie
- RE: [imss] MIB doctor review part 2 (T11-FC-SP-TC… WIJNEN, Bert (Bert)
- RE: [imss] imss WG Last Call: FC-SP MIB WIJNEN, Bert (Bert)
- Re: [imss] AD Review for draft-ietf-imss-fc-fcsp-… Keith McCloghrie
- Re: [imss] AD Review for draft-ietf-imss-fc-fcsp-… Black_David
- Re: [imss] AD Review for draft-ietf-imss-fc-fcsp-… Romascanu, Dan (Dan)