You are designing a GET VPN solution for an existing branch network. The existing network has the following characteristics: 50 remote sites (with an additional 30 remote sites expected over the next

EIGRP would create a redundant overlay routing plane that serves no purpose because GET VPN's tunnel-less design leaves the original IP headers intact and the existing underlay routing already provides full site-to-site reachability.

A second OSPF process would introduce unnecessary routing complexity since GET VPN does not alter IP headers, and the existing OSPF process already establishes reachability between all group members via the MPLS L3 VPN.

eBGP is not required because GET VPN group members do not form a separate routed overlay network; there are no tunnel endpoints between which new BGP adjacencies would need to be established.

RIPv2 would add slow convergence and unnecessary routing overhead when the existing OSPF and MPLS L3 VPN infrastructure already provides all the reachability that GET VPN group members require.

GET VPN uses the Group Domain of Interpretation (GDOI) protocol and encrypts packets in-place while preserving the original source and destination IP addresses - it does not encapsulate traffic in a new tunnel header as DMVPN or IPsec tunnel mode would. Because the routable IP headers are unchanged, all path selection continues to be handled by the existing OSPF process and MPLS L3 VPN infrastructure, making any additional overlay routing protocol redundant and unnecessary.