Cite this STD: TXT
STD 58 contains the following RFCs:| Number | Files | Title | Authors | Date | More Info | Status |
|---|---|---|---|---|---|---|
| RFC 2578, STD 58 | Structure of Management Information Version 2 (SMIv2) | K. McCloghrie, Ed., D. Perkins, Ed., J. Schoenwaelder, Ed. | April 1999 | Obsoletes RFC 1902 | Internet Standard | |
| RFC 2579, STD 58 | Textual Conventions for SMIv2 | K. McCloghrie, Ed., D. Perkins, Ed., J. Schoenwaelder, Ed. | April 1999 | Obsoletes RFC 1903, Errata | Internet Standard | |
| RFC 2580, STD 58 | Conformance Statements for SMIv2 | K. McCloghrie, Ed., D. Perkins, Ed., J. Schoenwaelder, Ed. | April 1999 | Obsoletes RFC 1904 | Internet Standard |
Abstract of RFC 2578
It is the purpose of this document, the Structure of Management Information Version 2 (SMIv2), to define that adapted subset, and to assign a set of associated administrative values. [STANDARDS-TRACK]
Abstract of RFC 2579
It is the purpose of this document to define the initial set of textual conventions available to all MIB modules. [STANDARDS-TRACK]
Abstract of RFC 2580
Collections of related objects are defined in MIB modules. 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. [STANDARDS-TRACK]
For the definition of Status, see RFC 2026.
For the definition of Stream, see RFC 8729.