[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

RE: FW: FW: Updating the MIB boilerplate



Title: RE: FW: FW: Updating the MIB boilerplate

Hi,

the title in the reference needs to be updated.

dbh

> -----Original Message-----
> From: Wijnen, Bert (Bert) [mailto:bwijnen@lucent.com]
> Sent: Wednesday, November 13, 2002 5:55 AM
> To: Randy Bush
> Cc: mibs@ops.ietf.org
> Subject: RE: FW: FW: Updating the MIB boilerplate
>
>
> Ok, so based on
> - the discussions on this mailing list
> - the desire to make the boiler-plate section-title more
>   or less in sync with the title of the rfc2570bis document
> - the principle of "truth in advertising"
>
> the titles will be as follows:
>
> - RFC2570bis title:
>
>       Introduction and Applicability Statements for
>      the Internet-Standard SNMP Management Framework
>
> - title of MIB boiler plate section in MIB documents
>
>    The Internet-Standard SNMP Management Framework
>
> The complete MIB boiler-plate section now becomes:
>
> ------------- new boiler plate for MIB documents -----------
>
> 1.  The Internet-Standard SNMP Management Framework
>
>    For a detailed overview of the documents that describe the
>    current Internet-Standard SNMP Management Framework, please
>    refer to section 7 of RFC2570bis [rfc2570bis].
>
>    Managed objects are accessed via a virtual information store,
>    termed the Management Information Base or MIB.  MIB objects are
>    generally accessed through the Simple Network Management Protocol
>    (SNMP).  Objects in the MIB are defined using the mechanisms
>    defined in the Structure of Management Information (SMI).  This
>    memo specifies a MIB module that is compliant to the SMIv2, which
>    is described in STD 58, RFC 2578 [RFC2578], STD 58, RFC 2579
>    [RFC2579] and STD 58, RFC 2580 [RFC2580].
>
> 2.  Normative References
>
> [RFC2578]   McCloghrie, K., Perkins, D., Schoenwaelder, J., Case, J.,
>             Rose, M., and S. Waldbusser, "Structure of Management
>             Information Version 2 (SMIv2)", STD 58, RFC 2578, April
>             1999.
>
> [RFC2579]   McCloghrie, K., Perkins, D., Schoenwaelder, J., Case, J.,
>             Rose, M., and S. Waldbusser, "Textual Conventions for
>             SMIv2", STD 58, RFC 2579, April 1999.
>
> [RFC2580]   McCloghrie, K., Perkins, D., Schoenwaelder, J., Case, J.,
>             Rose, M., and S. Waldbusser, "Conformance Statements for
>             SMIv2", STD 58, RFC 2580, April 1999.
>
> 3.  Informative References
>
> [RFC2570bis]Case, J., Mundy, R., Partain, D., and B. Stewart,
>             "Introduction to Version 3 of the
> Internet-standard Network
>             Management Framework", RFC 2570bis , November 2002.
>
>  
>
> Thanks,
> Bert
>
> > -----Original Message-----
> > From: Randy Bush [mailto:randy@psg.com]
> > Sent: dinsdag 12 november 2002 19:01
> > To: Wijnen, Bert (Bert)
> > Cc: mibs@ops.ietf.org
> > Subject: Re: FW: FW: Updating the MIB boilerplate
> >
> >
> > i hate to butt in, but from the outside this seems silly.  the goal
> > of ietf documents is to be clear, correct, and as unambiguous.  it
> > is also a bit amusing that folk seem to have become ashamed of the
> > word 'SNMP'.
> >
> >      Introduction and Applicability Statements for
> >     the Internet-Standard SNMP Management Framework
> >
> >      Introduction and Applicability Statements for
> >     the Internet-Standard SNMP Management Framework
> >
> > seems as clear as you're gonna get.  though, as the document is
> > an internet standard, one could remove "Internet-Standard".
> >
> > randy
> >
>