Re: [mpls] draft-wijnands-mpls-mldp-in-band-signaling - PIM-Bidir

[IJsbrand Wijnands <ice at cisco.com>]

Yakov,

> That still does not answer the question I asked above. Namely, what
> are "the IP multicast control messages used to set up the tree",
> and how do these messages get "translated into mLDP messages" when
> we have mp2mp LSP for (*, G/M)?

PIM messages are not translated into mLDP messages. I think that is  
the key point of the mis-understanding. You translate multicast  
routing state into mLDP messages. So if the MRIB has (*,G) it encodes  
it into a mLDP FEC, if it has (*,G/M) is does the same. That also  
makes the solution independent of PIM, MSDP or IGMP. Any multicast  
protocol that can populate the MRIB can be used to create a mLDP LSP.

> Your answer contradicts your own statement you made above, namely,

Correct, I mis interpreted your question. There will be different  
MP2MP LSPs.

> > This is documented in RFC5015 section 3.1.4. Its not mLDP's
> > functionality to merge the 2 trees together, this is done in PIM.
>
> Does that mean that the merge point has to run PIM ?

Yes, it will by default because this is the Ingress PE/Root of the  
P2MP LSP that borders with the IP PIM network.

> > Let me know if this addresses your concerns.
>
> No this does not address my concerns - see above.

Did we make progress?

Thx,

Ice.