<?xml version='1.0' encoding='UTF-8'?>

<reference anchor='I-D.atlas-mpls-te-express-path'>
<front>
<title>Performance-based Path Selection for Explicitly Routed LSPs</title>

<author initials='A' surname='Atlas' fullname='Alia Atlas'>
    <organization />
</author>

<author initials='J' surname='Drake' fullname='John Drake'>
    <organization />
</author>

<author initials='D' surname='Ward' fullname='David Ward'>
    <organization />
</author>

<author initials='S' surname='Giacalone' fullname='Spencer Giacalone'>
    <organization />
</author>

<author initials='S' surname='Previdi' fullname='Stefano Previdi'>
    <organization />
</author>

<author initials='C' surname='Filsfils' fullname='Clarence Filsfils'>
    <organization />
</author>

<date month='October' day='24' year='2011' />

<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-00' />
<format type='TXT'
        target='http://www.ietf.org/internet-drafts/draft-atlas-mpls-te-express-path-00.txt' />
</reference>

