<?xml version="1.0" encoding="UTF-8"?>
<reference anchor="I-D.atlas-mpls-ldp-mrt" target="https://datatracker.ietf.org/doc/html/draft-atlas-mpls-ldp-mrt-03">
   <front>
      <title>LDP Extensions to Support Maximally Redundant Trees</title>
      <author initials="A." surname="Atlas" fullname="Alia Atlas">
         <organization>Juniper Networks</organization>
      </author>
      <author initials="K." surname="Tiruveedhula" fullname="Kishore Tiruveedhula">
         <organization>Juniper Networks</organization>
      </author>
      <author initials="C." surname="Bowers" fullname="Chris Bowers">
         <organization>Juniper Networks</organization>
      </author>
      <author initials="J." surname="Tantsura" fullname="Jeff Tantsura">
         <organization>Ericsson</organization>
      </author>
      <author initials="I." surname="Wijnands" fullname="IJsbrand Wijnands">
         <organization>Cisco Systems</organization>
      </author>
      <date month="December" day="15" year="2014" />
      <abstract>
	 <t>   This document specifies extensions to the Label Distribution
   Protocol(LDP) to support the creation of label-switched paths for
   Maximally Redundant Trees (MRT).  A prime use of MRTs is for unicast
   and multicast IP/LDP Fast-Reroute, which we will refer to as MRT-FRR.

   The sole protocol extension to LDP is simply the ability to advertise
   an MRT Capability.  This document describes that extension and the
   associated behavior expected for LSRs and LERs advertising the MRT
   Capability.

   MRT-FRR uses LDP multi-topology extensions and requires three
   different multi-topology IDs to be allocated from the LDP MT-ID
   space.

	 </t>
      </abstract>
   </front>
   <seriesInfo name="Internet-Draft" value="draft-atlas-mpls-ldp-mrt-03" />
   
</reference>
