<?xml version="1.0" encoding="UTF-8"?>
<reference anchor="I-D.villamizar-mpls-multipath-extn" target="https://datatracker.ietf.org/doc/html/draft-villamizar-mpls-multipath-extn-00">
   <front>
      <title>Multipath Extensions for MPLS Traffic Engineering</title>
      <author initials="C." surname="Villamizar" fullname="Curtis Villamizar">
         <organization>Outer Cape Cod Network</organization>
      </author>
      <date month="November" day="13" year="2012" />
      <abstract>
	 <t>   Extensions to OSPF-TE, ISIS-TE, and RSVP-TE are defined in support of
   carrying LSP with strict packet ordering requirements over multipath
   and and carrying LSP with strict packet ordering requirements within
   LSP without violating requirements to maintain packet ordering.  LSP
   with strict packet ordering requirements include MPLS-TP LSP.

   OSPF-TE and ISIS-TE extensions defined here indicate node and link
   capability regarding support for ordered aggregates of traffic,
   multipath traffic distribution, and abilities to support multipath
   load distribution differently per LSP.

   RSVP-TE extensions either identifies an LSP as requiring strict
   packet order, or identifies an LSP as carrying one or more LSP that
   requires strict packet order further down in the label stack, or
   identifies an LSP as having no restrictions on packet ordering except
   the restriction to avoid reordering microflows.  In addition an
   extension indicates whether the first nibble of payload will reliably
   indicate whether payload is IPv4, IPv6, or other type of payload,
   most notably pseudowire using a pseudowire control word.

	 </t>
      </abstract>
   </front>
   <seriesInfo name="Internet-Draft" value="draft-villamizar-mpls-multipath-extn-00" />
   
</reference>
