<?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-06">
   <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">
         <organization>Hewlett-Packard Corp.</organization>
      </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">
         <organization>Thomson Reuters</organization>
      </author>
      <author initials="M." surname="Betts" fullname="Malcolm Betts">
         </author>
      <author initials="Q." surname="Wang" fullname="Qilei Wang">
         <organization>ZTE</organization>
      </author>
      <author initials="J." surname="Drake" fullname="John Drake">
         <organization>Juniper Networks</organization>
      </author>
      <date month="October" day="22" year="2012" />
      <abstract>
	 <t>   Deployment and usage of cloud based applications and services that use
   an underlying MPLS network are expanding and an increasing number of
   applications are extremely sensitive to delay and packet loss.
   Furthermore, in cloud computing an additional decision problem arises of
   simultaneously choosing the data center to host applications along with
   MPLS network connectivity such that the overall performance of the
   application is met. Mechanisms exist to measure and monitor MPLS path
   performance parameters for packet loss and delay, but the mechanisms
   work only after the path has been setup. The cloud-based and performance
   sensitive applications would benefit from measurement of MPLS network
   and potential path information that would be provided for use in the
   computation before LSP setup and then the selection of LSPs.

   This document provides a framework and architecture to solve operator
   problems and requirements using current/proposed approaches, documents
   scalability assessment and recommendations, and identifies any needed
   protocol development.


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