> That being said, selective more specific prefix announcements are the > bane of my existence when attempting to keep traffic local in the less > mainstream regions of the world. When a given network has some local > transit/peer and some backhauled transit/peer to which it sends a > different set of more specifics, resolving routing hairpins can become > extremely time consuming since we have to convince the team running > that network to adjust their routing policy - as opposed to > unilaterally assigning a higher LocalPref to the announcement which > may have a longer AS-path but doesn't take a scenic route through > $cheap_transit/peering_region.
i am probably misreading, but on the surface this seems to be a routing policy problem in the "local transit/peer." perhaps a diagramatic example would help. randy _______________________________________________ GROW mailing list [email protected] https://www.ietf.org/mailman/listinfo/grow
