<?xml version="1.0" encoding="UTF-8"?>
<reference anchor="I-D.ietf-mpls-mldp-node-protection" target="https://datatracker.ietf.org/doc/html/draft-ietf-mpls-mldp-node-protection-08">
   <front>
      <title>Multipoint LDP (mLDP) Node Protection</title>
      <author initials="I." surname="Wijnands" fullname="IJsbrand Wijnands">
         <organization>Cisco Systems</organization>
      </author>
      <author initials="S. K." surname="Raza" fullname="Syed Kamran Raza">
         <organization>Cisco Systems</organization>
      </author>
      <author initials="A." surname="Atlas" fullname="Alia Atlas">
         <organization>Juniper Networks</organization>
      </author>
      <author initials="J." surname="Tantsura" fullname="Jeff Tantsura">
         <organization>Ericsson</organization>
      </author>
      <author initials="Q." surname="Zhao" fullname="Quintin Zhao">
         <organization>Huawei Technology</organization>
      </author>
      <date month="September" day="29" year="2015" />
      <abstract>
	 <t>This document describes procedures to support node protection for Point-to-Multipoint and Multipoint-to-Multipoint Label Switched Paths (P2MP and MP2MP LSPs) that have been built by the Multipoint Label Distribution Protocol (mLDP).  In order to protect a node N, the Point of Local Repair (PLR) Label Switching Router (LSR) of N must learn the Merge Point (MPT) LSR(s) of node N such that traffic can be redirected to them in case node N fails.  Redirecting the traffic around the failed node N depends on existing Point-to-Point (P2P) Label Switched Paths (LSPs).  The pre-established LSPs originate from the PLR LSR and terminate on the MPT LSRs while bypassing LSR N.
	 </t>
      </abstract>
   </front>
   <seriesInfo name="Internet-Draft" value="draft-ietf-mpls-mldp-node-protection-08" />
   
</reference>
