<?xml version="1.0" encoding="UTF-8"?>
<reference anchor="I-D.ietf-ccamp-gmpls-resource-sharing-proc" target="https://datatracker.ietf.org/doc/html/draft-ietf-ccamp-gmpls-resource-sharing-proc-00">
   <front>
      <title>RSVP-TE Signaling Procedure for GMPLS Restoration and Resource Sharing- based LSP Setup and Teardown</title>
      <author initials="X." surname="Zhang" fullname="Xian Zhang">
         <organization>Huawei</organization>
      </author>
      <author initials="H." surname="Zheng" fullname="Haomian Zheng">
         <organization>Huawei</organization>
      </author>
      <author initials="R." surname="Gandhi" fullname="Rakesh Gandhi">
         <organization>Cisco Systems</organization>
      </author>
      <author initials="Z." surname="Ali" fullname="Zafar Ali">
         <organization>Cisco Systems</organization>
      </author>
      <author initials="G." surname="Galimberti" fullname="Gabriele Galimberti">
         <organization>Cisco Systems</organization>
      </author>
      <author initials="P." surname="Brzozowski" fullname="Pawel Brzozowski">
         <organization>ADVA Optical</organization>
      </author>
      <date month="November" day="21" year="2014" />
      <abstract>
	 <t>   In transport networks, there are requirements where Generalized
   Multi-Protocol Label Switching (GMPLS) end-to-end recovery scheme
   needs to employ restoration Label Switched Path (LSP) while keeping
   resources for the working and/or restoration LSPs reserved in the
   network after the failure occurs.  This document reviews how the LSP
   association is to be provided using Resource Reservation Protocol -
   Traffic Engineering (RSVP-TE) signaling in the context of GMPLS end-
   to-end recovery when using restoration LSP where failed LSP is not
   torn down.

   This document compliments existing standards by explaining the
   missing pieces of information during the RSVP-TE signaling procedure
   in support of resource sharing-based LSP setup/teardown in
   GMPLS-controlled circuit networks.  No new procedures or mechanisms
   are defined by this document, and it is strictly informative in
   nature.

	 </t>
      </abstract>
   </front>
   <seriesInfo name="Internet-Draft" value="draft-ietf-ccamp-gmpls-resource-sharing-proc-00" />
   
</reference>
