<?xml version="1.0" encoding="UTF-8"?>
<reference anchor="I-D.palle-pce-stateful-pce-initiated-p2mp-lsp" target="https://datatracker.ietf.org/doc/html/draft-palle-pce-stateful-pce-initiated-p2mp-lsp-02">
   <front>
      <title>PCEP Extensions for PCE-initiated Point-to-Multipoint LSP Setup in a Stateful PCE Model</title>
      <author initials="U." surname="Palle" fullname="Udayasree Palle">
         </author>
      <author initials="D." surname="Dhody" fullname="Dhruv Dhody">
         </author>
      <author initials="Y." surname="Tanaka" fullname="Yosuke Tanaka">
         </author>
      <author initials="Y." surname="Kamite" fullname="Yuji Kamite">
         </author>
      <author initials="Z." surname="Ali" fullname="Zafar Ali">
         </author>
      <date month="June" day="6" year="2014" />
      <abstract>
	 <t>   The Path Computation Element (PCE) has been identified as an
   appropriate technology for the determination of the paths of point-
   to-multipoint (P2MP) TE LSPs.  The extensions described in
   [I-D.ietf-pce-stateful-pce] provide stateful control of Multiprotocol
   Label Switching (MPLS) Traffic Engineering Label Switched Paths (TE
   LSP) via PCE communication Protocol (PCEP), for a model where the
   Path Computation Client (PCC) delegates control over one or more
   locally configured LSPs to the PCE.  Further
   [I-D.ietf-pce-pce-initiated-lsp] describes the creation and deletion
   of PCE-initiated LSPs under the stateful PCE model.  This document
   provides extensions required for PCEP so as to enable the usage of a
   stateful PCE initiation capability in recommending point-to-
   multipoint (P2MP) TE LSP instantiation.

	 </t>
      </abstract>
   </front>
   <seriesInfo name="Internet-Draft" value="draft-palle-pce-stateful-pce-initiated-p2mp-lsp-02" />
   
</reference>
