[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
RE: I-D ACTION:draft-ietf-ops-mib-review-guidelines-00.txt
At 2/6/2003:06:16 PM, Wijnen, Bert (Bert) wrote:
Hi Bert,
>Pls keep the purpose of the document in mind.
Ok...I had this purpose (from the Introduction)
in mind: "...meet certain generally accepted
standards of quality, including (but not limited
to) compliance with all syntactic and semantic
requirements of SMIv2...."
>I sort of feel that adding this would just bloat the
>document and not add value to detect a problem that
>we encounter in practice (if it happens at all,
>then it is very very rare as far as I know).
I believe it is true that forward references
that seem (to me at least) to be inconsistent
with the SMI's naming hierarchy rules occur
rarely (if at all) in IETF standard MIBs.
I believe that the practice is less clean
in a subset of enterprise MIBs and in some
IETF MIBs in the I-D stage.
I did not anticipate that a substantial amount
of text (bloat) would be needed to make a
statement such as:
"Forward references to OBJECT-TYPE values
not yet defined SHOULD be avoided where it
is possible to do so (via IMPORTs or
hierarchical ordering of objects in a MIB)."
However, I can accept an executive decision
that the matter does not require further
clarity in this "Guidelines for MIB Authors
and Reviewers".
Cheers,
BobN
>> -----Original Message-----
>> From: Bob Natale [mailto:Bob.Natale@AppliedSNMP.com]
>> Sent: donderdag 6 februari 2003 23:05
>> To: mibs@ops.ietf.org
>> Subject: Re: I-D ACTION:draft-ietf-ops-mib-review-guidelines-00.txt
>>
>>
>> At 2/6/2003:10:37 AM, Wijnen, Bert (Bert) wrote:
>>
>> Hi,
>>
>> >Let me first say a THANK YOU to Mike Heard.
>> >
>> >The MIB doctor/reviewers team is working on a document
>> >that guides us in reviwing MIB related documents.
>>
>> Yeah...thanks to Mike and everyone else putting this
>> document together...it will be an excellent resource
>> for many of us.
>>
>> I would like to see some explicit guidance concerning
>> "forward references" in MIB documents, with specific
>> citation of pertinent SMI requirements. I suspect
>> that perhaps this topic *could* be addressed in Sec.
>> 4.4 of the present document...perhaps by breaking it
>> into a discussion of external symbols and internal
>> symbols. Or perhaps the editor/contributors will
>> find a better place for it. But the topic should
>> be covered authoritatively in this document, IMHO.
>>
>> Thanks,
>>
>> BobN
>>
>>
>>
>>
>>
>>
>>
>>
>>
>> >-----Original Message-----
>> >From: Internet-Drafts@ietf.org [mailto:Internet-Drafts@ietf.org]
>> >Sent: donderdag 6 februari 2003 15:30
>> >Subject: I-D ACTION:draft-ietf-ops-mib-review-guidelines-00.txt
>> >
>> >
>> >A New Internet-Draft is available from the on-line
>> Internet-Drafts directories.
>> >This draft is a work item of the Operations & Management
>> Open Area Working Group of the IETF.
>> >
>> > Title : Guidelines for MIB Authors and Reviewers
>> > Author(s) : C. Heard
>> > Filename : draft-ietf-ops-mib-review-guidelines-00.txt
>> > Pages : 39
>> > Date : 2003-2-5
>> >
>> >This memo provides guidelines for authors and reviewers of IETF
>> >specifications containing MIB modules.
>> >
>> >A URL for this Internet-Draft is:
>> >http://www.ietf.org/internet-drafts/draft-ietf-ops-mib-review
>> -guidelines-00.txt
>> >
>> >To remove yourself from the IETF Announcement list, send a
>> message to
>> >ietf-announce-request with the word unsubscribe in the body
>> of the message.
>> >
>> >Internet-Drafts are also available by anonymous FTP. Login
>> with the username
>> >"anonymous" and a password of your e-mail address. After logging in,
>> >type "cd internet-drafts" and then
>> > "get draft-ietf-ops-mib-review-guidelines-00.txt".
>> >
>> >A list of Internet-Drafts directories can be found in
>> >http://www.ietf.org/shadow.html
>> >or ftp://ftp.ietf.org/ietf/1shadow-sites.txt
>> >
>> >
>> >Internet-Drafts can also be obtained by e-mail.
>> >
>> >Send a message to:
>> > mailserv@ietf.org.
>> >In the body type:
>> > "FILE
>> /internet-drafts/draft-ietf-ops-mib-review-guidelines-00.txt".
>> >
>> >NOTE: The mail server at ietf.org can return the document in
>> > MIME-encoded form by using the "mpack" utility. To use this
>> > feature, insert the command "ENCODING mime" before the "FILE"
>> > command. To decode the response(s), you will need
>> "munpack" or
>> > a MIME-compliant mail reader. Different
>> MIME-compliant mail readers
>> > exhibit different behavior, especially when dealing with
>> > "multipart" MIME messages (i.e. documents which have
>> been split
>> > up into multiple messages), so check your local
>> documentation on
>> > how to manipulate these messages.
>> >
>> >
>> >Below is the data which will enable a MIME compliant mail reader
>> >implementation to automatically retrieve the ASCII version of the
>> >Internet-Draft.
>> >
>> >To:
>> >Subject:
>> >Date: Thu, 6 Feb 2003 16:05:23 +0100
>> >MIME-Version: 1.0
>> >X-Mailer: Internet Mail Service (5.5.2653.19)
>> >Content-Type: multipart/mixed;
>> > boundary="----_=_NextPart_002_01C2CDF5.96B9632E"
>> >
>> >
>> >
>> >
>> ><ftp://internet-drafts>
>>
>>