<?xml version="1.0" encoding="UTF-8"?>
<reference anchor="I-D.atlas-mpls-te-express-path" target="https://datatracker.ietf.org/doc/html/draft-atlas-mpls-te-express-path-01">
   <front>
      <title>Performance-based Path Selection for Explicitly Routed LSPs</title>
      <author initials="A." surname="Atlas" fullname="Alia Atlas">
         </author>
      <author initials="J." surname="Drake" fullname="John Drake">
         </author>
      <author initials="S." surname="Giacalone" fullname="Spencer Giacalone">
         </author>
      <author initials="D." surname="Ward" fullname="David Ward">
         </author>
      <author initials="S." surname="Previdi" fullname="Stefano Previdi">
         </author>
      <author initials="C." surname="Filsfils" fullname="Clarence Filsfils">
         </author>
      <date month="June" day="25" year="2012" />
      <abstract>
	 <t>   In certain networks, it is critical to consider network performance
   criteria when selecting the path for an explicitly routed RSVP-TE
   LSP.  Such performance criteria can include latency, jitter, and loss
   or other indications such as the conformance to link SLAs and non-
   RSVP TE traffic load.  This specification uses IGP extension data
   (which is defined outside the scope of this document) to perform such
   path selections.

	 </t>
      </abstract>
   </front>
   <seriesInfo name="Internet-Draft" value="draft-atlas-mpls-te-express-path-01" />
   
</reference>
