<?xml version="1.0" encoding="UTF-8"?>
<reference anchor="I-D.ietf-mpls-app-aware-tldp" target="https://datatracker.ietf.org/doc/html/draft-ietf-mpls-app-aware-tldp-01">
   <front>
      <title>Application-aware Targeted LDP</title>
      <author initials="S." surname="Esale" fullname="Santosh Esale">
         </author>
      <author initials="R." surname="Torvi" fullname="Raveendra Torvi">
         </author>
      <author initials="C." surname="Bowers" fullname="Chris Bowers">
         </author>
      <author initials="L." surname="Jalil" fullname="Luay Jalil">
         </author>
      <author initials="U." surname="Chunduri" fullname="Uma Chunduri">
         </author>
      <author initials="Z." surname="Li" fullname="Zhenbin Li">
         </author>
      <author initials="S. K." surname="Raza" fullname="Syed Kamran Raza">
         </author>
      <date month="August" day="20" year="2015" />
      <abstract>
	 <t>   Recent targeted LDP applications such as remote loop-free alternate
   (LFA) and BGP auto discovered pseudowire may automatically establish
   a tLDP session to any LSR in a network.  The initiating LSR has
   information about the targeted applications to administratively
   control initiation of the session. However, the responding LSR has no
   such information to control acceptance of this session. This document
   defines a mechanism to advertise and negotiate Targeted Applications
   Capability during LDP session initialization.  As the responding LSR
   becomes aware of targeted applications, it may establish a limited
   number of tLDP sessions for certain applications. In addition, each
   targeted application is mapped to LDP Forwarding Equivalence Class
   (FEC) Elements to advertise only necessary LDP FEC-label bindings
   over the session.


	 </t>
      </abstract>
   </front>
   <seriesInfo name="Internet-Draft" value="draft-ietf-mpls-app-aware-tldp-01" />
   
</reference>
