<?xml version="1.0" encoding="UTF-8"?>
<reference anchor="I-D.ietf-tewg-te-applicability" target="https://datatracker.ietf.org/doc/html/draft-ietf-tewg-te-applicability-01">
   <front>
      <title>Applicability Statement for Traffic Engineering with MPLS</title>
      <author initials="B." surname="Christian" fullname="Blaine Christian">
         <organization>Worldcom</organization>
      </author>
      <author initials="A." surname="Hannan" fullname="Alan Hannan">
         <organization>RoutingLoop</organization>
      </author>
      <author initials="V." surname="Gill" fullname="Vijay Gill">
         <organization>AOL Time Warner</organization>
      </author>
      <author initials="D. O." surname="Awduche" fullname="Daniel O. Awduche">
         <organization>Movaz Networks</organization>
      </author>
      <author initials="W." surname="Lai" fullname="Wai Lai">
         <organization>AT&amp;T</organization>
      </author>
      <author initials="J." surname="Boyle" fullname="Jim Boyle">
         <organization>PD Nets</organization>
      </author>
      <date month="March" day="5" year="2002" />
      <abstract>
	 <t>This document describes the applicability of Multiprotocol Label
Switching (MPLS) to traffic engineering in IP networks.  Special
considerations for deployment of MPLS for traffic engineering in
operational contexts are discussed and the limitations of the MPLS
approach to traffic engineering are highlighted.
	 </t>
      </abstract>
   </front>
   <seriesInfo name="Internet-Draft" value="draft-ietf-tewg-te-applicability-01" />
   
</reference>
