metasystema.org
ObsoletedDRAFT STANDARDIETF stream

RFC 2178: OSPF Version 2

This RFC has been replaced. Do not implement against it for new work — it was formally obsoleted by RFC 2328.

Current document in this lineage: RFC 2328 — OSPF Version 2

In plain English — editorial summary, not part of the RFC

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. 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. [STANDARDS-TRACK]

Document record

Document ID
RFC2178
Published
July 1997
Authors
J. Moy
Status
DRAFT STANDARD
Stream
IETF
Area
rtg
Pages
211
Also known as
—
Obsoletes:
RFC 1583
Obsoleted by:
RFC 2328

Topics

Standards lineage

This document is one revision in a chain of 5 RFCs, each formally replacing the one before it.

  1. RFC 1131 (1989)
  2. RFC 1247 (1991)
  3. RFC 1583 (1994)
  4. RFC 2178 (1997)
  5. RFC 2328 (1998) ✓

Read the full history of OSPF Version 2 →

Referenced by

One later RFC formally updates or obsoletes part of this document.

Related documents

Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.

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?

canonical URL: /rfc/2178-ospf-version-2