<?xml version="1.0" encoding="UTF-8"?>
<reference anchor="I-D.ietf-mpls-bundle" target="https://datatracker.ietf.org/doc/html/draft-ietf-mpls-bundle-06">
   <front>
      <title>Link Bundling in MPLS Traffic Engineering (TE)</title>
      <author initials="Y." surname="Rekhter" fullname="Yakov Rekhter">
         <organization>Juniper Networks</organization>
      </author>
      <author initials="L." surname="Berger" fullname="Lou Berger">
         <organization>Movaz Networks</organization>
      </author>
      <author initials="K." surname="Kompella" fullname="Kireeti Kompella">
         <organization>Juniper Networks</organization>
      </author>
      <date month="December" day="27" year="2004" />
      <abstract>
	 <t>For the purpose of Generalized Multi-Protocol Label Switching (GMPLS) signaling, in certain cases a combination of &lt;link identifier, label&gt; is not sufficient to unambiguously identify the appropriate resource used by a Label Switched Path (LSP).  Such cases are handled by using the link bundling construct, which is described in this document.  This document updates the interface identification TLVs, which are defined in the GMPLS Signaling Functional Description. [STANDARDS-TRACK]
	 </t>
      </abstract>
   </front>
   <seriesInfo name="Internet-Draft" value="draft-ietf-mpls-bundle-06" />
   
</reference>
