An IPv6 NG MVPN uses P2MP LSPs to carry multicast traffic. You can configure either RSVP-TE P2MP or mLDP P2MP LSPs.
P2MP LSPs that carry multicast traffic can be either RSVP-TE P2MP or mLDP P2MP LSPs. Table 1 lists the differences between RSVP-TE P2MP LSPs and mLDP P2MP LSPs.
Compared Aspect |
mLDP P2MP LSP |
RSVP-TE P2MP LSP |
---|---|---|
Main features |
mLDP P2MP LSPs do not support bandwidth reservation and cannot ensure service quality during network congestion. mLDP P2MP LSPs are easier to configure than RSVP-TE P2MP LSPs. |
RSVP-TE P2MP LSPs support bandwidth reservation and can ensure service quality during network congestion. |
Application scenario |
Networks that do not require control over destination nodes Use mLDP P2MP LSPs to carry multicast traffic if high service quality is not required. |
Networks that require control over destination nodes Use RSVP-TE P2MP LSPs to carry multicast traffic if high service quality is required. |
Signaling |
Signaling packets do not need to be periodically sent, reducing network load. |
Signaling packets need to be periodically sent to maintain the tunnel. If a large number of leaf nodes exist, network congestion is likely to occur. |
Select the type of tunnel as needed.
If P2MP LSP that carry multicast traffic is RSVP-TE P2MP LSP, you need to configure a tunnel policy to bind a VPN service to specified RSVP-TE P2MP LSP.