<?xml version="1.0" encoding="UTF-8"?>
<reference anchor="I-D.ietf-mpls-mldp-in-band-signaling" target="https://datatracker.ietf.org/doc/html/draft-ietf-mpls-mldp-in-band-signaling-06">
   <front>
      <title>Multipoint LDP in-band signaling for Point-to-Multipoint and Multipoint- to-Multipoint Label Switched Paths</title>
      <author initials="I." surname="Wijnands" fullname="IJsbrand Wijnands">
         </author>
      <author initials="T. T." surname="Eckert" fullname="Toerless Eckert">
         </author>
      <author initials="N." surname="Leymann" fullname="Nicolai Leymann">
         </author>
      <author initials="M." surname="Napierala" fullname="Maria Napierala">
         </author>
      <date month="June" day="22" year="2012" />
      <abstract>
	 <t>   Consider an IP multicast tree, constructed by Protocol Independent
   Multicast (PIM), needs to pass through an MPLS domain in which
   Multipoint LDP (mLDP) Point-to-Multipoint and/or Multipoint-to-
   Multipoint Labels Switched Paths (LSPs) can be created.  The part of
   the IP multicast tree that traverses the MPLS domain can be
   instantiated as a multipoint LSP.  When a PIM Join message is
   received at the border of the MPLS domain, information from that
   message is encoded into mLDP messages.  When the mLDP messages reach
   the border of the next IP domain, the encoded information is used to
   generate PIM messages that can be sent through the IP domain.  The
   result is an IP multicast tree consisting of a set of IP multicast
   sub-trees that are spliced together with a multipoint LSP.

	 </t>
      </abstract>
   </front>
   <seriesInfo name="Internet-Draft" value="draft-ietf-mpls-mldp-in-band-signaling-06" />
   
</reference>
