<?xml version="1.0" encoding="UTF-8"?>
<reference anchor="I-D.hegde-isis-advertising-te-protocols" target="https://datatracker.ietf.org/doc/html/draft-hegde-isis-advertising-te-protocols-03">
   <front>
      <title>Advertising TE protocols in IS-IS</title>
      <author initials="S." surname="Hegde" fullname="Shraddha Hegde">
         <organization>Juniper Networks</organization>
      </author>
      <author initials="C." surname="Bowers" fullname="Chris Bowers">
         <organization>Juniper Networks</organization>
      </author>
      <author initials="P." surname="Mattes" fullname="Paul Mattes">
         <organization>Microsoft</organization>
      </author>
      <author initials="M." surname="Nanduri" fullname="Mohan Nanduri">
         <organization>Microsoft</organization>
      </author>
      <author initials="S." surname="Giacalone" fullname="Spencer Giacalone">
         <organization>Microsoft</organization>
      </author>
      <author initials="I." surname="Mohammad" fullname="Imtiyaz Mohammad">
         <organization>Arista Networks</organization>
      </author>
      <date month="September" day="15" year="2017" />
      <abstract>
	 <t>   This document defines a mechanism to indicate which traffic
   engineering protocols are enabled on a link in IS-IS.  It does so by
   introducing a new traffic-engineering protocol sub-TLV for TLV-22.
   This document also describes mechanisms to address backward
   compatibility issues for implementations that have not yet been
   upgraded to software that understands this new sub-TLV.


	 </t>
      </abstract>
   </front>
   <seriesInfo name="Internet-Draft" value="draft-hegde-isis-advertising-te-protocols-03" />
   
</reference>
