<?xml version="1.0" encoding="UTF-8"?>
<reference anchor="I-D.ietf-ospf-te-link-attr-reuse" target="https://datatracker.ietf.org/doc/html/draft-ietf-ospf-te-link-attr-reuse-16">
   <front>
      <title>OSPF Application-Specific Link Attributes</title>
      <author initials="P." surname="Psenak" fullname="Peter Psenak">
         <organization>Cisco Systems</organization>
      </author>
      <author initials="L." surname="Ginsberg" fullname="Les Ginsberg">
         <organization>Cisco Systems</organization>
      </author>
      <author initials="W." surname="Henderickx" fullname="Wim Henderickx">
         <organization>Nokia</organization>
      </author>
      <author initials="J." surname="Tantsura" fullname="Jeff Tantsura">
         <organization>Apstra</organization>
      </author>
      <author initials="J." surname="Drake" fullname="John Drake">
         <organization>Juniper Networks</organization>
      </author>
      <date month="June" day="30" year="2020" />
      <abstract>
	 <t>Existing traffic-engineering-related link attribute advertisements have been defined and are used in RSVP-TE deployments.  Since the original RSVP-TE use case was defined, additional applications (e.g., Segment Routing Policy and Loop-Free Alternates) that also make use of the link attribute advertisements have been defined.  In cases where multiple applications wish to make use of these link attributes, the current advertisements do not support application-specific values for a given attribute, nor do they support indication of which applications are using the advertised value for a given link.  This document introduces new link attribute advertisements in OSPFv2 and OSPFv3 that address both of these shortcomings.
	 </t>
      </abstract>
   </front>
   <seriesInfo name="Internet-Draft" value="draft-ietf-ospf-te-link-attr-reuse-16" />
   
</reference>
