<?xml version="1.0" encoding="UTF-8"?>
<reference anchor="I-D.fuxh-mpls-delay-loss-te-framework" target="https://datatracker.ietf.org/doc/html/draft-fuxh-mpls-delay-loss-te-framework-05">
   <front>
      <title>Loss and Delay Traffic Engineering Framework for MPLS</title>
      <author initials="X." surname="Fu" fullname="Xihua Fu">
         </author>
      <author initials="V." surname="Manral" fullname="Vishwas Manral">
         </author>
      <author initials="D." surname="McDysan" fullname="Dave McDysan">
         </author>
      <author initials="A. G." surname="Malis" fullname="Andrew G. Malis">
         </author>
      <author initials="S." surname="Giacalone" fullname="Spencer Giacalone">
         </author>
      <author initials="M." surname="Betts" fullname="Malcolm Betts">
         </author>
      <author initials="Q." surname="Wang" fullname="Qilei Wang">
         </author>
      <author initials="J." surname="Drake" fullname="John Drake">
         </author>
      <date month="April" day="11" year="2012" />
      <abstract>
	 <t>   With more and more enterprises using cloud based services, the
   distances between the user and the applications are growing.  A lot
   of the current applications are designed to work across LAN&#x27;s and
   have various inherent assumptions.  For multiple applications such as
   High Performance Computing and Electronic Financial markets, the
   response times are critical as is packet loss, while other
   applications require more throughput.

   [RFC3031] describes the architecture of MPLS based networks.  This
   draft extends the MPLS architecture to allow for latency, loss and
   jitter as properties.  It describes requirements and control plane
   implication for latency and packet loss as a traffic engineering
   performance metric in today&#x27;s network which is consisting of
   potentially multiple layers of packet transport network and optical
   transport network in order to make a accurate end-to-end latency and
   loss prediction before a path is established.

   Note MPLS architecture for Multicast will be taken up in a future
   version of the draft.


	 </t>
      </abstract>
   </front>
   <seriesInfo name="Internet-Draft" value="draft-fuxh-mpls-delay-loss-te-framework-05" />
   
</reference>
