A Tier-3 Service Provider is evolving into a Tier-2 Service Provider due to the amount of Enterprise business it is receiving. The network engineers are re-evaluating their IP/MPLS design…

Route Distinguishers are prepended to customer IPv4 prefixes to create unique VPNv4 addresses (formatted as RD:prefix) within the provider's MP-BGP RIB, allowing multiple enterprises with identical IP address spaces to coexist without conflict. Each customer VPN receives a unique RD so that identical prefixes from different customers appear as completely distinct routes in the global BGP table. Without unique RDs, the provider cannot differentiate between the same IP prefix advertised by two separate customers, causing route table instability.

Route Targets control VRF import and export policies to determine which routes are shared between VRFs, but they do not resolve the prefix uniqueness problem in the provider's MP-BGP control plane.

Assigning unique IP space to enterprise NAT or firewalls contradicts the fundamental L3VPN design goal of supporting overlapping customer addressing without requiring customers to renumber their infrastructure.

VRF IDs are locally significant labels on each individual router and do not need to be globally unique across the provider network; the MP-BGP control plane uniqueness is handled by Route Distinguishers, not VRF IDs.