Experience with the OSPF Protocol
RFC 1246

Type RFC - Informational (July 1991; No errata)
Last updated 2013-03-02
Stream IETF
Formats plain text pdf ps html
WG state (None)
Document shepherd No shepherd assigned
IESG state RFC 1246 (Informational)
Telechat date
Responsible AD (None)
Send notices to (None)

Email authors IPR References Referenced by Nits Search lists

Network Working Group                                     J. Moy, Editor
Request for Comments: 1246                                     July 1991

                   Experience with the OSPF protocol

Status of this Memo

This memo provides information for the Internet community. It does not
specify any Internet standard. Distribution of this memo is unlimited.


This is the second of two reports on the OSPF protocol. These reports
are required by the IAB/IESG in order for an Internet routing protocol
to advance to Draft Standard Status. OSPF is a TCP/IP routing protocol,
designed to be used internal to an Autonomous System (in other words,
OSPF is an Interior Gateway Protocol).

OSPF is currently designated as a Proposed Standard. Version 1 of the
OSPF protocol was published in RFC 1131. Since then OSPF version 2 has
been developed. Version 2 has been documented in RFC 1247.  The changes
between version 1 and version 2 of the OSPF protocol are explained in
Appendix F of RFC 1247. It is OSPF Version 2 that is the subject of this

This report documents experience with OSPF V2. This includes reports on
interoperability testing, field experience, simulations and the current
state of OSPF implementations. It also presents a summary of the OSPF
Management Information Base (MIB), and a summary of OSPF authentication

Please send comments to ospf@trantor.umd.edu.

1.0  Introduction

This document addresses, for OSPF V2, the requirements set forth by the
IAB/IESG for an Internet routing protocol to advance to Draft Standard
state. This requirements are briefly summarized below. The remaining
sections of this report document how OSPF V2 satisfies these

[Moy]                                                           [Page 1]
RFC 1246                  Experience with OSPF                 July 1991

o  The specification for the routing protocol must be well written such
   that independent, interoperable implementations can be developed
   solely based on the specification. For example, it should be possible
   to develop an interoperable implementation without consulting the
   original developers of the routing protocol.

o  A Management Information Base (MIB) must be written for the protocol.
   The MIB must be in the standardization process, but does not need to
   be at the same level of standardization as the routing protocol.

o  The security architecture of the protocol must be set forth
   explicitly. The security architecture must include mechanisms for
   authenticating routing messages and may include other forms of

o  Two or more interoperable implementations must exist. At least two
   must be written independently.

o  There must be evidence that all features of the protocol have been
   tested, running between at least two implementations. This must
   include that all of the security features have been demonstrated to
   operate, and that the mechanisms defined in the protocol actually
   provide the intended protection.

o  There must be significant operational experience. This must include
   running in a moderate number routers configured in a moderately
   complex topology, and must be part of the operational Internet. All
   significant features of the protocol must be exercised. In the case
   of an Interior Gateway Protocol (IGP), both interior and exterior
   routes must be carried (unless another mechanism is provided for the
   exterior routes). In the case of a Exterior Gateway Protocol (EGP),
   it must carry the full complement of exterior routes.

This report is a compilation of information obtained from many people.
The reader is referred to specific people when more information on a
subject is available. People references are gathered into Section 10.0,
in a format similar to that used in [4].

1.1  Acknowledgments

The OSPF protocol has been developed by the OSPF Working Group of the
Internet Engineering Task Force. Many people have contributed to this
report. They are listed in Section 10.0 of this report.

[Moy]                                                           [Page 2]
RFC 1246                  Experience with OSPF                 July 1991

2.0  Documentation

Version 1 of the OSPF protocol is documented in RFC 1131 [1]. OSPF
Version 2, which supersedes Version 1, has been documented in RFC 1247
[2]. The differences between OSPF Version 1 and Version 2 are relatively
minor, and are listed in Appendix F of RFC 1247 [2]. All information
presented in this report concerns OSPF V2 unless explicitly mentioned

The OSPF protocol was developed by the OSPF Working Group of the
Internet Engineering Task Force. This Working Group has a mailing list,
ospf@trantor.umd.edu, where discussions of protocol features and
Show full document text