A service provider engineering team must design a solution that supports end-to-end LSPs for multiple IGP domains within different AS numbers.
According to RFC 3107, which solution achieves this goal?
RFC 3107 defines the usage of BGP to carry Multiprotocol Label Switching (MPLS) labels for Layer 3 Virtual Private Network (VPN) services. This enables the transport of Layer 3 VPN traffic over an MPLS backbone network. Based on this, the answer to the given question is option B, which is BGP and send-label.
Option A, LDP and BGP, is not correct because LDP (Label Distribution Protocol) is not capable of carrying labels for multiple IGP (Interior Gateway Protocol) domains. LDP can only distribute labels within a single IGP domain.
Option C, RSVP and IS-IS or OSPF, is also not correct because RSVP (Resource Reservation Protocol) is used for signaling and setting up MPLS Label Switched Paths (LSPs) for traffic engineering, but it does not support the distribution of labels between IGP domains.
Option D, RSVP and BGP, is incorrect because although RSVP is used for MPLS LSP signaling, BGP is used for MPLS label distribution for Layer 3 VPN services.
Option E, mLDP (Multipoint LDP), is also not correct because mLDP is used for multicast traffic forwarding and does not support the distribution of labels between IGP domains.
Therefore, option B, BGP and send-label, is the correct answer as it allows BGP to distribute labels between different IGP domains, thereby supporting end-to-end LSPs for multiple IGP domains within different AS numbers. The send-label command is used to send MPLS labels along with BGP updates, enabling the distribution of labels for Layer 3 VPN services.