Re: [mpls] applicability of draft-wijnands-mpls-mldp-in-band-signaling-02
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [mpls] applicability of draft-wijnands-mpls-mldp-in-band-signaling-02



Yakov,

This prevents receiving a (S,G) from the P2MP LSP and send it down the (*,G) PIM tree. This is the behavior we want to support in combination
with out-of-band source discovery via MSDP. The only thing we want to
restrict is transport (*,G) traffic down the P2MP LSP, that is covered
by section 2.3.

Then the draft should explicitly spell out "the behavior we want
to support", *and* the mechanisms/procedures to support such behavior,
including the interaction with the out-of-band source discovery via MSDP.

There are no additional mechanisms/procedures to support this behavior. This is basic PIM Sparse-mode behavior.

Maybe this goes back to my comment on the other email, that PIM messages are not translated into mLDP messages. The multicast routing state is used to drive the creating of the mLDP LSPs.

Thx,

Ice.

Note: Messages sent to this list are the opinions of the senders and do not imply endorsement by the IETF.