RFC 1248: OSPF Version 2 Management Information Base
This RFC has been replaced. Do not implement against it for new work — it was formally obsoleted by RFC 1252.
Current document in this lineage: RFC 4750 — OSPF Version 2 Management Information Base
In plain English — editorial summary, not part of the RFC
This memo defines an experimental portion of the Management Information Base (MIB) for use with network management protocols in TCP/IP-based internets. In particular, it defines objects for managing OSPF Version 2. [STANDARDS-TRACK]
Document record
- Document ID
- RFC1248
- Published
- July 1991
- Authors
- F. Baker; R. Coltun
- Status
- PROPOSED STANDARD
- Stream
- Legacy
- Area
- —
- Pages
- 42
- Also known as
- —
Topics
Standards lineage
This document is one revision in a chain of 5 RFCs, each formally replacing the one before it.
Read the full history of OSPF Version 2 Management Information Base →
Referenced by
2 later RFCs formally update or obsolete part of this document.
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 1246Experience with the OSPF ProtocolCurrent
July 1991
- RFC 1850OSPF Version 2 Management Information BaseObsoleted
November 1995
- RFC 1245OSPF Protocol AnalysisCurrent
July 1991
- RFC 4750OSPF Version 2 Management Information BaseCurrent
December 2006
- 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 7367Definition of Managed Objects for the Mobile Ad Hoc Network (MANET) Simplified Multicast Framework Relay Set ProcessCurrent
October 2014
- RFC 7939Definition of Managed Objects for the Neighborhood Discovery ProtocolCurrent
August 2016
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?