<?xml version="1.0" encoding="UTF-8"?>
<reference anchor="I-D.kumaki-murai-l3vpn-rsvp-te" target="https://datatracker.ietf.org/doc/html/draft-kumaki-murai-l3vpn-rsvp-te-07">
   <front>
      <title>Support for RSVP-TE in L3VPNs</title>
      <author initials="K." surname="Kumaki" fullname="Kenji Kumaki">
         </author>
      <author initials="T." surname="Murai" fullname="Tomoki Murai">
         </author>
      <author initials="D." surname="Cheng" fullname="Dean Cheng">
         </author>
      <author initials="S." surname="Matsushima" fullname="Satoru Matsushima">
         </author>
      <author initials="J." surname="Peng" fullname="PENG JIANG">
         </author>
      <date month="November" day="26" year="2012" />
      <abstract>
	 <t>   IP Virtual Private Networks (VPNs) provide connectivity between sites
   across an IP/MPLS backbone. These VPNs can be operated using BGP/MPLS
   and a single provider edge (PE) node may provide access to multiple
   customer sites belonging to different VPNs.

   The VPNs may support a number of customer services including RSVP and
   RSVP-TE traffic. This document describes how to support RSVP-TE
   between customer sites when a single PE supports multiple VPNs and
   labels are not used to identify VPNs between PEs.


	 </t>
      </abstract>
   </front>
   <seriesInfo name="Internet-Draft" value="draft-kumaki-murai-l3vpn-rsvp-te-07" />
   
</reference>
