Browse Prior Art Database

Experience with the OSPF Protocol (RFC1246)

IP.com Disclosure Number: IPCOM000002062D
Original Publication Date: 1991-Jul-01
Included in the Prior Art Database: 2001-Oct-24
Document File: 31 page(s) / 70K

Publishing Venue

Internet Society Requests For Comment (RFCs)

Related People

J. Moy: AUTHOR

Abstract

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).

This text was extracted from an ASCII text file.
This is the abbreviated version, containing approximately 5% of the total text.

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.

Abstract

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

report.

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

mechanism.

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

requirements:

[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

   protection.

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

   si...