RFC - 1583

OSPF Version 2

Original:	ftp://ftp.isi.edu/in-notes/rfc1583.txt
Authors:	J. Moy [Proteon, Inc.]
Date:	March 1994
Category:	Informational
This specification has been !!! obsoleted !!!

---

Obsoleted by:
RFC-2178	OSPF Version 2 (Obsoleted by RFC-2328std54)

Obsoletes:
RFC-1247	OSPF Version 2 (Obsoleted by RFC-1583 -> RFC-2178 -> RFC-2328std54) (Updated by RFC-1349)

Referred by:	32 RFC
Refers to:	7 RFC

---

Status

This document specifies an Internet standards track protocol for the Internet community, and requests discussion and suggestions for improvements. Please refer to the current edition of the "Internet Official Protocol Standards" (STD 1) for the standardization state and status of this protocol. Distribution of this memo is unlimited.

Abstract

This memo documents version 2 of the OSPF protocol. OSPF is a link-state routing protocol. It is designed to be run internal to a single Autonomous System. Each OSPF router maintains an identical database describing the Autonomous System's topology. From this database, a routing table is calculated by constructing a shortest- path tree.

OSPF recalculates routes quickly in the face of topological changes, utilizing a minimum of routing protocol traffic. OSPF provides support for equal-cost multipath. Separate routes can be calculated for each IP Type of Service. An area routing capability is provided, enabling an additional level of routing protection and a reduction in routing protocol traffic. In addition, all OSPF routing protocol exchanges are authenticated.

OSPF Version 2 was originally documented in RFC 1247(-> 1583(-> 2178(-> 2328^std54))). The differences between RFC 1247(-> 1583(-> 2178(-> 2328^std54))) and this memo are explained in Appendix E. The differences consist of bug fixes and clarifications, and are backward-compatible in nature. Implementations of RFC 1247(-> 1583(-> 2178(-> 2328^std54))) and of this memo will interoperate.

Please send comments to ospf@gated.cornell.edu.

---