STD58, RFC2580 on Conformance Statements for SMIv2

RFC Editor <rfc-ed@ISI.EDU> Fri, 16 April 1999 16:25 UTC

Message-Id: <199904161619.JAA29853@zephyr.isi.edu>
To: IETF-Announce:;
Subject: STD58, RFC2580 on Conformance Statements for SMIv2
Cc: rfc-ed@ISI.EDU
Mime-Version: 1.0
Content-Type: Multipart/Mixed; Boundary="NextPart"
Date: Fri, 16 Apr 1999 09:22:11 -0700
From: RFC Editor <rfc-ed@ISI.EDU>

A new Request for Comments is now available in online RFC libraries.


        STD 58:
	RFC 2580: 

        Title: 	    Conformance Statements for SMIv2
   	Author(s):  K. McCloghrie, D. Perkins, J. Schoenwaelder
        Status:     Standards Track
	Date:       April 1999
        Mailbox:    kzm@cisco.com, dperkins@snmpinfo.com,
                    schoenw@ibr.cs.tu-bs.de 
        Pages:      29
        Characters: 54253
        Obsoletes:  1904
        I-D Tag:    draft-ops-smiv2-conf-01.txt

        URL:        ftp://ftp.isi.edu/in-notes/rfc2580.txt


Management information is viewed as a collection of managed objects,
residing in a virtual information store, termed the Management
Information Base (MIB).  Collections of related objects are defined in
MIB modules.  These modules are written using an adapted subset of
OSI's Abstract Syntax Notation One, ASN.1 (1988), termed the Structure
of Management Information (SMI).  It may be useful to define the
acceptable lower-bounds of implementation, along with the actual level
of implementation achieved.  It is the purpose of this document to
define the notation used for these purposes.

This is now a Standard Protocol.

This document specifies an Internet standards track protocol for the
Internet community, and requests discussion and suggestions for
improvements.  Please refer to the current edition of the "Internet
Official Protocol Standards" (STD 1) for the standardization state
and status of this protocol.  Distribution of this memo is unlimited.

This announcement is sent to the IETF list and the RFC-DIST list.
Requests to be added to or deleted from the IETF distribution list
should be sent to IETF-REQUEST@IETF.ORG.  Requests to be
added to or deleted from the RFC-DIST distribution list should
be sent to RFC-DIST-REQUEST@RFC-EDITOR.ORG.

Details on obtaining RFCs via FTP or EMAIL may be obtained by sending
an EMAIL message to rfc-info@RFC-EDITOR.ORG with the message body 
help: ways_to_get_rfcs.  For example:

        To: rfc-info@RFC-EDITOR.ORG
        Subject: getting rfcs

        help: ways_to_get_rfcs

Requests for special distribution should be addressed to either the
author of the RFC in question, or to RFC-Manager@RFC-EDITOR.ORG.  Unless
specifically noted otherwise on the RFC itself, all RFCs are for
unlimited distribution.echo 
Submissions for Requests for Comments should be sent to
RFC-EDITOR@RFC-EDITOR.ORG.  Please consult RFC 2223, Instructions to RFC
Authors, for further information.


Joyce K. Reynolds and Alegre Ramos
USC/Information Sciences Institute

...

Below is the data which will enable a MIME compliant Mail Reader 
implementation to automatically retrieve the ASCII version
of the RFCs.

ftp://ftp.isi.edu/in-notes/rfc2580.txt"><ftp://ftp.isi.edu/in-notes/rfc2580.txt>

STD58, RFC2580 on Conformance Statements for SMIv2 RFC Editor