RFC 2328: OSPF Version 2

This memo documents version 2 of the OSPF protocol. OSPF is a link- state routing protocol. [STANDARDS-TRACK]

Read RFC 2328 on the RFC Editor

Outgoing relationships (14 related RFCs)

Obsoletes, Informative reference — RFC 2178: OSPF Version 2
Informative reference — RFC 1321: The MD5 Message-Digest Algorithm
Informative reference — RFC 1191: Path MTU discovery
Informative reference — RFC 1112: Host extensions for IP multicasting
Informative reference — RFC 1519: Classless Inter-Domain Routing (CIDR): an Address Assignment and Aggregation Strategy
Informative reference — RFC 1771: A Border Gateway Protocol 4 (BGP-4)
Informative reference — RFC 1583: OSPF Version 2
Informative reference — RFC 1584: Multicast Extensions to OSPF
Informative reference — RFC 1349: Type of Service in the Internet Protocol Suite
Informative reference — RFC 1793: Extending OSPF to Support Demand Circuits
Informative reference — RFC 905: ISO Transport Protocol specification ISO DP 8073
Informative reference — RFC 1293: Inverse Address Resolution Protocol
Informative reference — RFC 1587: The OSPF NSSA Option
Informative reference — RFC 1586: Guidelines for Running OSPF Over Frame Relay Networks

Incoming relationships (99 related RFCs)

Showing 50 of 99 related RFCs.

Updated by, Normatively referenced by — RFC 5709: OSPFv2 HMAC-SHA Cryptographic Authentication
Updated by, Normatively referenced by — RFC 7474: Security Extension for OSPFv2 When Using Manual Key Management
Updated by, Normatively referenced by — RFC 6845: OSPF Hybrid Broadcast and Point-to-Multipoint Interface Type
Updated by — RFC 6549: OSPFv2 Multi-Instance Extensions
Updated by — RFC 8042: OSPF Two-Part Metric
Updated by — RFC 6860: Hiding Transit-Only Networks in OSPF
Updated by — RFC 9355: OSPF Bidirectional Forwarding Detection (BFD) Strict-Mode
Updated by, Normatively referenced by — RFC 9454: Update to OSPF Terminology
Normatively referenced by — RFC 7752: North-Bound Distribution of Link-State and Traffic Engineering (TE) Information Using BGP
Normatively referenced by — RFC 3618: Multicast Source Discovery Protocol (MSDP)
Normatively referenced by — RFC 7684: OSPFv2 Prefix/Link Attribute Advertisement
Normatively referenced by — RFC 4915: Multi-Topology (MT) Routing in OSPF
Normatively referenced by — RFC 8665: OSPF Extensions for Segment Routing
Normatively referenced by — RFC 7166: Supporting Authentication Trailer for OSPFv3
Normatively referenced by — RFC 7770: Extensions to OSPF for Advertising Optional Router Capabilities
Normatively referenced by — RFC 6553: The Routing Protocol for Low-Power and Lossy Networks (RPL) Option for Carrying RPL Information in Data-Plane Datagrams
Normatively referenced by — RFC 9552: Distribution of Link-State and Traffic Engineering Information Using BGP
Normatively referenced by — RFC 5073: IGP Routing Protocol Extensions for Discovery of Traffic Engineering Node Capabilities
Normatively referenced by — RFC 6565: OSPFv3 as a Provider Edge to Customer Edge (PE-CE) Routing Protocol
Normatively referenced by — RFC 5443: LDP IGP Synchronization
Normatively referenced by — RFC 5614: Mobile Ad Hoc Network (MANET) Extension of OSPF Using Connected Dominating Set (CDS) Flooding
Normatively referenced by — RFC 6506: Supporting Authentication Trailer for OSPFv3
Normatively referenced by — RFC 6987: OSPF Stub Router Advertisement
Normatively referenced by — RFC 4972: Routing Extensions for Discovery of Multiprotocol (MPLS) Label Switch Router (LSR) Traffic Engineering (TE) Mesh Membership
Normatively referenced by — RFC 9129: YANG Data Model for the OSPF Protocol
Normatively referenced by — RFC 5643: Management Information Base for OSPFv3
Normatively referenced by — RFC 5786: Advertising a Router's Local Addresses in OSPF Traffic Engineering (TE) Extensions
Normatively referenced by — RFC 9843: IGP Flexible Algorithms: Bandwidth, Delay, Metrics, and Constraints
Normatively referenced by — RFC 4990: Use of Addresses in Generalized Multiprotocol Label Switching (GMPLS) Networks
Normatively referenced by — RFC 5787: OSPFv2 Routing Protocols Extensions for Automatically Switched Optical Network (ASON) Routing
Normatively referenced by — RFC 6396: Multi-Threaded Routing Toolkit (MRT) Routing Information Export Format
Normatively referenced by — RFC 6601: Generic Connection Admission Control (GCAC) Algorithm Specification for IP/MPLS Networks
Normatively referenced by — RFC 6827: Automatically Switched Optical Network (ASON) Routing for OSPFv2 Protocols
Normatively referenced by — RFC 8346: A YANG Data Model for Layer 3 Topologies
Normatively referenced by — RFC 9067: A YANG Data Model for Routing Policy
Normatively referenced by — RFC 9492: OSPF Application-Specific Link Attributes
Normatively referenced by — RFC 9667: Dynamic Flooding on Dense Graphs
Normatively referenced by — RFC 9857: Advertisement of Segment Routing Policies Using BGP - Link State
Normatively referenced by — RFC 5330: A Link-Type sub-TLV to Convey the Number of Traffic Engineering Label Switched Paths Signalled with Zero Reserved Bandwidth across a Link
Normatively referenced by — RFC 6825: Traffic Engineering Database Management Information Base in Support of MPLS-TE/GMPLS
Normatively referenced by — RFC 7503: OSPFv3 Autoconfiguration
Normatively referenced by — RFC 7580: OSPF-TE Extensions for General Network Element Constraints
Normatively referenced by — RFC 8099: OSPF Topology-Transparent Zone
Normatively referenced by — RFC 8333: Micro-loop Prevention by Introducing a Local Convergence Delay
Normatively referenced by — RFC 8379: OSPF Graceful Link Shutdown
Normatively referenced by — RFC 8920: OSPF Application-Specific Link Attributes
Normatively referenced by — RFC 9084: OSPF Prefix Originator Extensions
Normatively referenced by — RFC 9502: IGP Flexible Algorithm in IP Networks
Normatively referenced by — RFC 9696: Routing in Fat Trees (RIFT) Applicability and Operational Considerations
Normatively referenced by — RFC 3883: Detecting Inactive Neighbors over OSPF Demand Circuits (DC)