RFC 2438: Advancement of MIB specifications on the IETF Standards Track
In plain English — editorial summary, not part of the RFC
This document specifies the process which the IESG will use to determine if a MIB specification document meets these requirements. It also discusses the rationale for this process. This document specifies an Internet Best Current Practices for the Internet Community, and requests discussion and suggestions for improvements.
Document record
- Document ID
- RFC2438
- Published
- October 1998
- Authors
- M. O'Dell; H. Alvestrand; B. Wijnen; S. Bradner
- Status
- BEST CURRENT PRACTICE
- Stream
- IETF
- Area
- —
- Pages
- 7
- Also known as
- BCP27
Topics
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 2648A URN Namespace for IETF DocumentsUpdated
August 1999
- RFC 2667IP Tunnel MIBObsoleted
August 1999
- RFC 2096IP Forwarding Table MIBObsoleted
January 1997
- RFC 2031IETF-ISOC relationshipObsoleted
October 1996
- RFC 2028The Organizations Involved in the IETF Standards ProcessObsoleted
October 1996
- RFC 3005IETF Discussion List CharterObsoleted
November 2000
- RFC 3160The Tao of IETF - A Novice's Guide to the Internet Engineering Task ForceObsoleted
August 2001
- RFC 3184IETF Guidelines for ConductObsoleted
October 2001
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?