<?xml version="1.0" encoding="UTF-8"?>
<reference anchor="I-D.ietf-ospf-rfc2370bis" target="https://datatracker.ietf.org/doc/html/draft-ietf-ospf-rfc2370bis-05">
   <front>
      <title>The OSPF Opaque LSA Option</title>
      <author initials="R." surname="Coltun" fullname="Rob Coltun">
         <organization>Acoustra Productions</organization>
      </author>
      <author initials="A. D." surname="Zinin" fullname="Alex D. Zinin">
         <organization>Alcatel-Lucent</organization>
      </author>
      <author initials="I." surname="Bryskin" fullname="Igor Bryskin">
         <organization>Adva</organization>
      </author>
      <author initials="L." surname="Berger" fullname="Lou Berger">
         <organization>LabN</organization>
      </author>
      <date month="May" day="8" year="2008" />
      <abstract>
	 <t>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&#x27;s OSPF area. [STANDARDS-TRACK]
	 </t>
      </abstract>
   </front>
   <seriesInfo name="Internet-Draft" value="draft-ietf-ospf-rfc2370bis-05" />
   
</reference>
