RFC 4181: Guidelines for Authors and Reviewers of MIB Documents
In plain English — editorial summary, not part of the RFC
This memo provides guidelines for authors and reviewers of IETF standards-track specifications containing MIB modules. Applicable portions may be used as a basis for reviews of other MIB documents. This document specifies an Internet Best Current Practices for the Internet Community, and requests discussion and suggestions for improvements.
Document record
- Document ID
- RFC4181
- Published
- September 2005
- Authors
- C. Heard
- Status
- BEST CURRENT PRACTICE
- Stream
- IETF
- Area
- ops
- Pages
- 42
- Also known as
- BCP111
- Updated by:
- RFC 4841
Topics
Referenced by
One later RFC formally updates or obsoletes part of this document.
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 4188Definitions of Managed Objects for BridgesCurrent
September 2005
- RFC 4150Transport Performance Metrics MIBCurrent
August 2005
- RFC 4149Definition of Managed Objects for Synthetic Sources for Performance Monitoring AlgorithmsCurrent
August 2005
- RFC 4133Entity MIB (Version 3)Obsoleted
August 2005
- RFC 4268Entity State MIBCurrent
December 2005
- RFC 4070Definitions of Managed Object Extensions for Very High Speed Digital Subscriber Lines (VDSL) Using Multiple Carrier Modulation (MCM) Line CodingCurrent
May 2005
- RFC 4069Definitions of Managed Object Extensions for Very High Speed Digital Subscriber Lines (VDSL) Using Single Carrier Modulation (SCM) Line CodingCurrent
May 2005
- RFC 4318Definitions of Managed Objects for Bridges with Rapid Spanning Tree ProtocolCurrent
December 2005
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?