Reading this discussion, I propose the following; Move the use of Local-Prefrence to the last bullet of Section 4, "Best Practice," and rewrite as follows
- If possible, the use of local-preference to locally override AS path selection should be avoided. This can lead other networks to excessively prepend their AS Paths to you in a futile attempt to influence your network. Nevertheless, sometimes the use of local-preference is the only way to achieve a desired traffic engineer policy. Does this strike the right balance for folks? On Sat, Aug 2, 2025 at 4:50 AM Nick Hilliard <[email protected]> wrote: > Gert Doering wrote on 02/08/2025 10:29: > > I second this. This is all very well-intended, but usually just gets > > in the way at some point - so if ISP networks start working with LP, it > > inevitably results in sub-optimal paths later on (LP preferring a > > longer AS path through a private interconnect vs. a direct peering > > over an IXP is a classic example) - which needs manual interaction > > to fix. Given the amount of BGP expertise in operational networks is > > going down over time, doing anything that needs more BGP expertise in > > future should not be encouraged. > > Agreed, LP is convenient in tiny leaf networks, but it can easily cause > more trouble than it's worth on larger networks with any sort of > topology complication. I'd be very cautious about recommending it in a BCP. > > Nick > > _______________________________________________ > GROW mailing list -- [email protected] > To unsubscribe send an email to [email protected] > -- =============================================== David Farmer Email:[email protected] Networking & Telecommunication Services Office of Information Technology University of Minnesota 2218 University Ave SE Phone: 612-626-0815 Minneapolis, MN 55414-3029 Cell: 612-812-9952 ===============================================
_______________________________________________ GROW mailing list -- [email protected] To unsubscribe send an email to [email protected]
