From the question pile: Route servers (as opposed to route reflectors) don't change anything about a BGP route when re-advertising it to a peer, whether iBGP or eBGP. Why don't route servers cause routing loops (or other problems) in a BGP network?

Route servers are often used by Internet Exchange Points (IXPs) to distribute routes between connected BGP speakers. BGP route servers

• Don't change anything about a received BGP route when advertising the route to its peers (other BGP speakers)
• Don't install routes received through BGP into the local routing table

Shouldn't using route servers in a network—pontentially, at least—cause routing loops or other BGP routing issues?