Re: Updating the MIB boilerplate

[Mark Ellison <ellison@ieee.org>]

Another 100% agreement...well said, Bob!

\\Mark

"Natale, Robert C (Bob)" wrote:

> Hi,
>
> I agree that we ought to minimize the number of places
> (ideally to 1) where we have to say the same thing in
> all of our docs.
>
> One caveat, while pointing people to a single reference
> doc for a topic is a good thing, we should be sure that,
> for a given topic, the pointer is to the specific relevant
> part or parts (i.e., section identifiers, not page numbers)
> of that reference doc.
>
> Cheers,
>
> BobN
>
> > -----Original Message-----
> > From: Steve Moulton [mailto:moulton@snmp.com]
> > Sent: Tuesday, October 29, 2002 1:03 PM
> > To: mibs@ops.ietf.org
> > Subject: Re: Updating the MIB boilerplate
> >
> > On Tuesday, October 29 2002, "C. M. Heard" <heard@pobox.com> wrote:
> >
> > > On Tue, 29 Oct 2002, Juergen Schoenwaelder wrote:
> > > > Since SNMPv3 is full standard now, I hope we can actually
> > shorten the
> > > > boilerplate significantly.
> > >
> > > That does not strike me as wise.  SNMPv1 and SNMPv2c do not
> > disappear
> > > right away just because SNMPv3 is made standard.  Indeed I
> > would venture
> > > to say that they will be extensively used for some time to come.  My
> > > suggestion is that when the SNMPv3 documents are published
> > you update
> > > the references (with the already agreed split between normative and
> > > informative) and add a couple of words in the 3rd and 4th bullets of
> > > the boilerplate to say that SNMPv1 now has Historic status.  E.g.:
> > >
> > >     o   Message protocols for transferring management
> > information.  The
> > >         first version of the SNMP message protocol is
> > called SNMPv1 and
> > >         described in STD 15, RFC 1157 [RFC1157], which is
> > now Historic.
> > >         A second version of the SNMP message protocol, which is also
> > >         Historic, is called SNMPv2c and described in RFC 1901
> > >         [RFC1901] and RFC 1906 [RFC1906].  The third version of the
> > >         message protocol is called SNMPv3 and described in
> > RFC 1906bis
> > >         [RFC1906bis], RFC 2572bis [RFC2572bis] and RFC
> > 2574bis [RFC2574bis].
> > >
> > >     o   Protocol operations for accessing management
> > information.  The
> > >         first set of protocol operations and associated PDU
> > formats is
> > >         described in STD 15, RFC 1157 [RFC1157], which is
> > now Historic.
> > >         A second set of protocol operations and associated
> > PDU formats
> > >         is described in RFC 1905bis [RFC1905bis].
> > >
> > > (replace ####bis with actual RFC number).
> > >
> > > Mike
> > >
> > >
> >
> > This is adequately covered in draft-ietf-snmpv3-rfc2570bis-03.txt.
> > Rather than burden MIB documents with references to protocols
> > we no longer
> > recommend, a informative reference to rfc2570bis (whatever it
> > is whenever it is) is sufficient.
> >
> >       - Steve