STDs are stable identifiers for "Internet Standards." An STD may consist of a single RFC or a group of RFCs related to a specific protocol. The collection may become empty as the STD evolves.
RFC 2578: STD 58: Structure of Management Information Version 2 (SMIv2)
Internet Standard
- K. McCloghrie, Ed.
- D. Perkins, Ed.
- J. Schoenwaelder, Ed.
- April 1999
- Legacy publication
Abstract
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
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]
RFC 2579: STD 58: Textual Conventions for SMIv2
Internet Standard
- K. McCloghrie, Ed.
- D. Perkins, Ed.
- J. Schoenwaelder, Ed.
- April 1999
- Legacy publication
Abstract
It is the purpose of this document to define the initial set of textual conventions available to all MIB modules. [STANDARDS-TRACK]
Abstract
It is the purpose of this document to define the initial set of textual conventions available to all MIB modules. [STANDARDS-TRACK]
RFC 2580: STD 58: Conformance Statements for SMIv2
Internet Standard
- K. McCloghrie, Ed.
- D. Perkins, Ed.
- J. Schoenwaelder, Ed.
- April 1999
- Legacy publication
Abstract
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]
Abstract
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]