RFC 2328

RFC 2328
Title	RFC 2328
Author	John Moy
Published	April 1998
Status	Proposed Standard
Relates	OSPF, IP, IETF

RFC 2328

RFC 2328 is the Internet Engineering Task Force (IETF) specification that defines the Open Shortest Path First (OSPF) Version 2 interior gateway routing protocol for IPv4. It standardizes procedures for link-state exchange, route calculation, and interoperability among routers produced by vendors such as Cisco Systems, Juniper Networks, Huawei Technologies, Nokia, and Arista Networks. The document succeeds earlier work from the INTERNET DRAFT process and relates to standards developed within the Internet Society and the Internet Architecture Board.

Introduction

RFC 2328 codifies OSPFv2 as a link-state routing protocol designed for use in IPv4 networks, addressing scalability and convergence concerns faced by operators including AT&T, Verizon Communications, British Telecom, Deutsche Telekom, and NTT Communications. It builds on foundational research from institutions such as Xerox PARC, MIT, Stanford University, University of California, Berkeley, and the Carnegie Mellon University networking groups. The specification is part of the broader IETF routing area alongside documents from working groups like the Routing Area Working Group and relates to technologies deployed by enterprises such as Goldman Sachs, Walmart, Amazon (company), Google, and Facebook.

Background and Purpose

The purpose of RFC 2328 is to provide a robust mechanism for intra-domain routing among autonomous systems operated by organizations such as RIPE NCC, ARIN, APNIC, LACNIC, and AfriNIC. It addresses limitations observed in distance-vector protocols like those used historically by X.25 networks and systems influenced by DECnet and complements exterior gateway protocols such as Border Gateway Protocol used by backbone providers including Level 3 Communications and Cogent Communications. The specification reflects lessons from operational deployments at research networks including CERFnet, SURFnet, CANARIE, and CERNET.

Protocol Overview

RFC 2328 describes OSPFv2 as a link-state protocol where routers build a topology view via Link State Advertisements (LSAs) and compute shortest-path trees using Dijkstra’s algorithm originating from theoretical work by researchers at Bell Labs, ATT Bell Labs, and Bjarne Stroustrup’s contemporaries. Network types defined include point-to-point links commonly used in infrastructures by Lucent Technologies and multi-access networks seen in campus deployments at Harvard University, Yale University, University of Oxford, and University of Cambridge. The protocol defines areas to scale routing in large organizations like Microsoft Corporation, Apple Inc., IBM, and Oracle Corporation and uses the OSPF link-state database to exchange topology information among routers from vendors such as Juniper Networks and Cisco Systems.

Message Types and Packet Format

RFC 2328 specifies OSPF packet types including Hello, Database Description, Link State Request, Link State Update, and Link State Acknowledgment, referencing packet handling used by network equipment makers like Broadcom Inc., Intel Corporation, Marvell Technology Group, and Qualcomm. The packet format encapsulates IPv4 headers standardized by Robert E. Kahn and Vint Cerf and aligns with addressing practices influenced by allocations managed by IANA and registries like ARIN and RIPE NCC. The document details LSA kinds and flooding procedures used in operational networks run by entities such as NASA, NOAA, US Department of Defense, and European Space Agency.

Timers and State Machine

RFC 2328 defines timers and a per-interface and per-neighbor state machine for adjacency establishment and maintenance, referencing engineering practices from Bell Labs, GTE Corporation, Motorola, and Texas Instruments. The neighbor states include Down, Init, Two-Way, ExStart, Exchange, Loading, and Full, modeled in implementations by vendors including Cisco Systems, Juniper Networks, and Huawei Technologies. Timer parameters such as Hello and Dead intervals are tuned in deployments at financial firms like JP Morgan Chase and exchanges such as NASDAQ to meet convergence and stability requirements.

Implementation and Deployment

The RFC influenced implementations in routing software projects and commercial products including Quagga (software), FRRouting, Bird Internet Routing Daemon, GNU Zebra, and embedded platforms from Cisco Systems and Juniper Networks. Large-scale deployments occurred in carrier networks run by Verizon Communications, AT&T, and content delivery networks such as Akamai Technologies and Cloudflare, as well as in campus networks at Stanford University and Massachusetts Institute of Technology. The specification facilitated interoperability testing in events organized by groups like the IETF and demonstrations at conferences such as Interop and RIPE Meetings.

Security Considerations

RFC 2328 discusses security mechanisms including plain-text and cryptographic authentication of OSPF packets, referencing cryptographic primitives and standards from organizations like RSA Security, NIST, IETF, ISO/IEC, and protocols such as IPsec and Secure Shell. Operational security concerns raised by incidents affecting providers like Equinix and research into routing security by institutions including Georgia Tech and University of California, San Diego drove later extensions and BEST CURRENT PRACTICE documents developed by the IETF OPSAWG and working groups addressing routing protocol security. Category:Internet Standards