RFC 5243: OSPF Database Exchange Summary List Optimization
In plain English — editorial summary, not part of the RFC
This document describes a backward-compatible optimization for the Database Exchange process in OSPFv2 and OSPFv3. In this optimization, a router does not list a Link State Advertisement (LSA) in Database Description packets sent to a neighbor, if the same or a more recent instance of the LSA was listed in a Database Description packet already received from the neighbor. This optimization reduces Database Description overhead by about 50% in large networks. This optimization does not affect synchronization, since it only omits unnecessary information from Database Description packets. This memo provides information for the Internet community.
Document record
- Document ID
- RFC5243
- Published
- May 2008
- Authors
- R. Ogier
- Status
- INFORMATIONAL
- Stream
- IETF
- Area
- rtg
- Pages
- 5
- Also known as
- —
- Updated by:
- RFC 9454
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.
- RFC 5240Protocol Independent Multicast (PIM) Bootstrap Router MIBCurrent
June 2008
- RFC 5250The OSPF Opaque LSA OptionCurrent
July 2008
- RFC 5251Layer 1 VPN Basic ModeCurrent
July 2008
- RFC 5252OSPF-Based Layer 1 VPN Auto-DiscoveryCurrent
July 2008
- RFC 5253Applicability Statement for Layer 1 Virtual Private Network (L1VPN) Basic ModeCurrent
July 2008
- RFC 5254Requirements for Multi-Segment Pseudowire Emulation Edge-to-Edge (PWE3)Current
October 2008
- RFC 5212Requirements for GMPLS-Based Multi-Region and Multi-Layer Networks (MRN/MLN)Current
July 2008
- RFC 5283LDP Extension for Inter-Area Label Switched Paths (LSPs)Current
July 2008
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?