RFC 5249: Templates for Internet-Drafts Containing MIB Modules
In plain English — editorial summary, not part of the RFC
This memo references three annotated templates for IETF documents that contain the definition of MIB modules. It is intended to reduce the work of the editors of such documents, making these documents more uniform and easier to read and review, thus furthering the quality of such documents and expediting their publication. This document specifies an Internet Best Current Practices for the Internet Community, and requests discussion and suggestions for improvements.
Document record
- Document ID
- RFC5249
- Published
- July 2008
- Authors
- D. Harrington
- Status
- BEST CURRENT PRACTICE
- Stream
- IETF
- Area
- —
- Pages
- 4
- Also known as
- BCP139
Topics
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 6065Using Authentication, Authorization, and Accounting Services to Dynamically Provision View-Based Access Control Model User-to-Group MappingsCurrent
December 2010
- RFC 6779Definition of Managed Objects for the Neighborhood Discovery ProtocolObsoleted
October 2012
- RFC 7184Definition of Managed Objects for the Optimized Link State Routing Protocol Version 2Current
April 2014
- RFC 7330Definitions of Textual Conventions (TCs) for Bidirectional Forwarding Detection (BFD) ManagementCurrent
August 2014
- RFC 7331Bidirectional Forwarding Detection (BFD) Management Information BaseCurrent
August 2014
- RFC 7367Definition of Managed Objects for the Mobile Ad Hoc Network (MANET) Simplified Multicast Framework Relay Set ProcessCurrent
October 2014
- RFC 7388Definition of Managed Objects for IPv6 over Low-Power Wireless Personal Area Networks (6LoWPANs)Current
October 2014
- RFC 7420Path Computation Element Communication Protocol (PCEP) Management Information Base (MIB) ModuleCurrent
December 2014
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?