<?xml version="1.0" encoding="UTF-8"?>
<reference anchor="I-D.ietf-mpls-ldp-applicability-label-adv" target="https://datatracker.ietf.org/doc/html/draft-ietf-mpls-ldp-applicability-label-adv-03">
   <front>
      <title>Label Advertisement Discipline for LDP Forwarding Equivalence Classes (FECs)</title>
      <author initials="S. K." surname="Raza" fullname="Syed Kamran Raza">
         <organization>Cisco Systems</organization>
      </author>
      <author initials="S." surname="Boutros" fullname="Sami Boutros">
         <organization>Cisco Systems</organization>
      </author>
      <author initials="L." surname="Martini" fullname="Luca Martini">
         <organization>Cisco Systems</organization>
      </author>
      <author initials="N." surname="Leymann" fullname="Nicolai Leymann">
         <organization>Deutsche Telekom</organization>
      </author>
      <date month="April" day="2" year="2014" />
      <abstract>
	 <t>The label advertising behavior of an LDP speaker for a given Forwarding Equivalence Class (FEC) is governed by the FEC type and not necessarily by the LDP session&#x27;s negotiated label advertisement mode.  This document updates RFC 5036 to make that fact clear.  It also updates RFCs 3212, 4447, 5918, 6388, and 7140 by specifying the label advertisement mode for all currently defined LDP FEC types.
	 </t>
      </abstract>
   </front>
   <seriesInfo name="Internet-Draft" value="draft-ietf-mpls-ldp-applicability-label-adv-03" />
   
</reference>
