Currently there are two options when deploying a Customer Edge mesh v2 site.

1. Attach the cluster to the "nearest" F5 RE based on Geo proximity (geographic distance)

2. Statically attach the cluster to one F5 RE

It would be beneficial to include a logic based on network performance metric like:

• Latency

• Jitter

• Packet loss

This way a cluster would be able to attach to the "best" performing F5 RE consider network distance rather than geo, which does not consider internet hub locations for specific countries increasing latency significantly.