<?xml version="1.0" encoding="UTF-8"?>
<reference anchor="I-D.ietf-mpls-rsvp-lsp-tunnel" target="https://datatracker.ietf.org/doc/html/draft-ietf-mpls-rsvp-lsp-tunnel-09">
   <front>
      <title>RSVP-TE: Extensions to RSVP for LSP Tunnels</title>
      <author initials="D. O." surname="Awduche" fullname="Daniel O. Awduche">
         <organization>Movaz Networks</organization>
      </author>
      <author initials="L." surname="Berger" fullname="Lou Berger">
         <organization>Juniper Networks</organization>
      </author>
      <author initials="D." surname="Gan" fullname="Der-Hwa Gan">
         <organization>Juniper Networks</organization>
      </author>
      <author initials="T." surname="Li" fullname="Tony Li">
         <organization>Procket Networks</organization>
      </author>
      <author initials="V." surname="Srinivasan" fullname="Dr. Vijay Srinivasan">
         <organization>Cosine Communications</organization>
      </author>
      <author initials="G." surname="Swallow" fullname="George Swallow">
         <organization>Cisco Systems</organization>
      </author>
      <date month="September" day="6" year="2001" />
      <abstract>
	 <t>This document describes the use of RSVP (Resource Reservation Protocol), including all the necessary extensions, to establish label-switched paths (LSPs) in MPLS (Multi-Protocol Label Switching).  Since the flow along an LSP is completely identified by the label applied at the ingress node of the path, these paths may be treated as tunnels.  A key application of LSP tunnels is traffic engineering with MPLS as specified in RFC 2702. [STANDARDS-TRACK]
	 </t>
      </abstract>
   </front>
   <seriesInfo name="Internet-Draft" value="draft-ietf-mpls-rsvp-lsp-tunnel-09" />
   
</reference>
