RFC 5250: The OSPF Opaque LSA Option
In plain English — editorial summary, not part of the RFC
This document defines enhancements to the OSPF protocol to support a new class of link state advertisements (LSAs) called Opaque LSAs. Opaque LSAs provide a generalized mechanism to allow for the future extensibility of OSPF. Opaque LSAs consist of a standard LSA header followed by application-specific information. The information field may be used directly by OSPF or by other applications. Standard OSPF link-state database flooding mechanisms are used to distribute Opaque LSAs to all or some limited portion of the OSPF topology. This document replaces RFC 2370 and adds to it a mechanism to enable an OSPF router to validate Autonomous System (AS)-scope Opaque LSAs originated outside of the router's OSPF area. [STANDARDS-TRACK]
Document record
- Document ID
- RFC5250
- Published
- July 2008
- Authors
- L. Berger; I. Bryskin; A. Zinin; R. Coltun
- Status
- PROPOSED STANDARD
- Stream
- IETF
- Area
- rtg
- Pages
- 17
- Also known as
- —
- Obsoletes:
- RFC 2370
Topics
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 7684OSPFv2 Prefix/Link Attribute AdvertisementCurrent
November 2015
- RFC 4970Extensions to OSPF for Advertising Optional Router CapabilitiesObsoleted
July 2007
- RFC 4222Prioritized Treatment of Specific OSPF Version 2 Packets and Congestion AvoidanceUpdated
October 2005
- RFC 4136OSPF Refresh and Flooding Reduction in Stable TopologiesCurrent
July 2005
- RFC 7770Extensions to OSPF for Advertising Optional Router CapabilitiesCurrent
February 2016
- RFC 5252OSPF-Based Layer 1 VPN Auto-DiscoveryCurrent
July 2008
- RFC 5187OSPFv3 Graceful RestartCurrent
June 2008
- RFC 5185OSPF Multi-Area AdjacencyCurrent
May 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?