<?xml version="1.0" encoding="UTF-8"?>
<reference anchor="I-D.ietf-ospf-prefix-link-attr" target="https://datatracker.ietf.org/doc/html/draft-ietf-ospf-prefix-link-attr-13">
   <front>
      <title>OSPFv2 Prefix/Link Attribute Advertisement</title>
      <author initials="P." surname="Psenak" fullname="Peter Psenak">
         <organization>Cisco Systems</organization>
      </author>
      <author initials="H." surname="Gredler" fullname="Hannes Gredler">
         <organization>Independent</organization>
      </author>
      <author initials="R." surname="Shakir" fullname="Rob Shakir">
         <organization>Jive Communications</organization>
      </author>
      <author initials="W." surname="Henderickx" fullname="Wim Henderickx">
         <organization>Alcatel-Lucent</organization>
      </author>
      <author initials="J." surname="Tantsura" fullname="Jeff Tantsura">
         <organization>Ericsson</organization>
      </author>
      <author initials="A." surname="Lindem" fullname="Acee Lindem">
         <organization>Cisco Systems</organization>
      </author>
      <date month="August" day="20" year="2015" />
      <abstract>
	 <t>OSPFv2 requires functional extension beyond what can readily be done with the fixed-format Link State Advertisements (LSAs) as described in RFC 2328.  This document defines OSPFv2 Opaque LSAs based on Type-Length-Value (TLV) tuples that can be used to associate additional attributes with prefixes or links.  Depending on the application, these prefixes and links may or may not be advertised in the fixed-format LSAs.  The OSPFv2 Opaque LSAs are optional and fully backward compatible.
	 </t>
      </abstract>
   </front>
   <seriesInfo name="Internet-Draft" value="draft-ietf-ospf-prefix-link-attr-13" />
   
</reference>
