RFC 4750: OSPF Version 2 Management Information Base
In plain English — editorial summary, not part of the RFC
This memo defines a 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 version 2 of the Open Shortest Path First Routing Protocol. Version 2 of the OSPF protocol is specific to the IPv4 address family. Version 3 of the OSPF protocol is specific to the IPv6 address family. This memo obsoletes RFC 1850; however, it is designed to be backwards compatible. The functional differences between this memo and RFC 1850 are explained in Appendix B. [STANDARDS-TRACK]
Document record
- Document ID
- RFC4750
- Published
- December 2006
- Authors
- D. Joyal; P. Galecki; S. Giacalone
- Status
- PROPOSED STANDARD
- Stream
- IETF
- Area
- rtg
- Pages
- 121
- Also known as
- —
- Obsoletes:
- RFC 1850
Topics
Standards lineage
This document is one revision in a chain of 5 RFCs, each formally replacing the one before it.
- RFC 1248 (1991)
- RFC 1252 (1991)
- RFC 1253 (1991)
- RFC 1850 (1995)
- RFC 4750 (2006)
Read the full history of OSPF Version 2 Management Information Base →
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 1252OSPF Version 2 Management Information BaseObsoleted
August 1991
- RFC 1246Experience with the OSPF ProtocolCurrent
July 1991
- RFC 5643Management Information Base for OSPFv3Current
August 2009
- RFC 6779Definition of Managed Objects for the Neighborhood Discovery ProtocolObsoleted
October 2012
- RFC 2676QoS Routing Mechanisms and OSPF ExtensionsCurrent
August 1999
- RFC 2328OSPF Version 2Updated
April 1998
- 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
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?