RFC 2579: Textual Conventions for SMIv2
In plain English — editorial summary, not part of the RFC
It is the purpose of this document to define the initial set of textual conventions available to all MIB modules. [STANDARDS-TRACK]
Document record
- Document ID
- RFC2579
- Published
- April 1999
- Authors
- K. McCloghrie; D. Perkins; J. Schoenwaelder
- Status
- INTERNET STANDARD
- Stream
- Legacy
- Area
- —
- Pages
- 25
- Also known as
- STD58
- Obsoletes:
- RFC 1903
Topics
Standards lineage
This document is one revision in a chain of 3 RFCs, each formally replacing the one before it.
- RFC 1443 (1993)
- RFC 1903 (1996)
- RFC 2579 (1999)
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 2580Conformance Statements for SMIv2Current
April 1999
- RFC 3434Remote Monitoring MIB Extensions for High Capacity AlarmsCurrent
December 2002
- RFC 2578Structure of Management Information Version 2 (SMIv2)Current
April 1999
- RFC 3416Version 2 of the Protocol Operations for the Simple Network Management Protocol (SNMP)Current
December 2002
- RFC 3417Transport Mappings for the Simple Network Management Protocol (SNMP)Updated
December 2002
- RFC 3418Management Information Base (MIB) for the Simple Network Management Protocol (SNMP)Current
December 2002
- RFC 5097MIB for the UDP-Lite protocolCurrent
January 2008
- RFC 5249Templates for Internet-Drafts Containing MIB ModulesCurrent
July 2008
Also filed under
About this page
The document record above — title, authors, date, status, stream, area, relationships, DOI and errata — is imported verbatim from the public RFC Editor index. The “in plain English” section is editorial: written by The metasystema editorial team, not part of the RFC. Where the two differ, the RFC text governs.
Last checked against the RFC Editor index on . RFCs are never revised after publication; changes are issued as new documents.
Data sources · Editorial policy · Report a correction · What is an RFC?