Skip to main content

The OSPF Opaque LSA Option

Document Type Replaced Internet-Draft (individual)
Expired & archived
Author Lou Berger
Last updated 2008-04-16 (Latest revision 2006-10-16)
Replaced by RFC 5250
RFC stream (None)
Intended RFC status (None)
Stream Stream state (No stream defined)
Consensus boilerplate Unknown
RFC Editor Note (None)
IESG IESG state Replaced by draft-ietf-ospf-rfc2370bis
Telechat date (None)
Responsible AD (None)
Send notices to (None)

This Internet-Draft is no longer active. A copy of the expired Internet-Draft is available in these formats:


This memo defines enhancements to the OSPF protocol to support a new class of link-state advertisements (LSA) 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 [RFC2370], and adds to it a mechanism to enable an OSPF router to validate AS-scope opaque LSAs originated outside of the router's OSPF area.


Lou Berger

(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)