<?xml version="1.0" encoding="UTF-8"?>
<reference anchor="I-D.ginsberg-lsr-rfc8919bis" target="https://datatracker.ietf.org/doc/html/draft-ginsberg-lsr-rfc8919bis-02">
   <front>
      <title>IS-IS Application-Specific Link Attributes</title>
      <author initials="L." surname="Ginsberg" fullname="Les Ginsberg">
         <organization>Cisco Systems</organization>
      </author>
      <author initials="P." surname="Psenak" fullname="Peter Psenak">
         <organization>Cisco Systems</organization>
      </author>
      <author initials="S." surname="Previdi" fullname="Stefano Previdi">
         <organization>Huawei Technologies</organization>
      </author>
      <author initials="W." surname="Henderickx" fullname="Wim Henderickx">
         <organization>Nokia</organization>
      </author>
      <author initials="J." surname="Drake" fullname="John Drake">
         <organization>Juniper Networks</organization>
      </author>
      <date month="July" day="24" year="2022" />
      <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
   that address both of these shortcomings.

   This document obsoletes RFC 8919.

	 </t>
      </abstract>
   </front>
   <seriesInfo name="Internet-Draft" value="draft-ginsberg-lsr-rfc8919bis-02" />
   
</reference>
