<?xml version="1.0" encoding="UTF-8"?>
<reference anchor="I-D.torvi-mpls-rsvp-ingress-protection" target="https://datatracker.ietf.org/doc/html/draft-torvi-mpls-rsvp-ingress-protection-00">
   <front>
      <title>Ingress Protection for RSVP-TE p2p and p2mp LSPs</title>
      <author initials="A." surname="Atlas" fullname="Alia Atlas">
         <organization>Juniper Networks</organization>
      </author>
      <author initials="R." surname="Torvi" fullname="Raveendra Torvi">
         <organization>Juniper Networks</organization>
      </author>
      <author initials="M." surname="Jork" fullname="Markus Jork">
         <organization>Juniper Networks</organization>
      </author>
      <date month="July" day="9" year="2012" />
      <abstract>
	 <t>   Protection against node failure is important for RSVP-TE LSPs,
   whether point-to-point or point-to-multipoint.  While [RFC4090]
   provides a mechanism for node protection, it does not specify how to
   protect against failure of the ingress node.  This document specifies
   the RSVP extensions to support ingress node protection and describes
   the necessary processing behavior.

	 </t>
      </abstract>
   </front>
   <seriesInfo name="Internet-Draft" value="draft-torvi-mpls-rsvp-ingress-protection-00" />
   
</reference>
