>> 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? > > Sort of. I would twist it a bit differently, something with more bias > on "it's the largest hammer in your toolbox, so use with care" - can't > find good wording right now.
local pref may be the largest hammer in one's toolbox, but it deals with a very different nail than path prepending. it influences only inbound routes, i.e. where you send packets. this is the inverse of as path prepending, which influences from where you receive packets. the largest hammer in the inbound packet toolbox is deaggregation. as with all hammers, skill and a bit of wisdom is advised. i am not sure local pref belongs in this document at all, as its title is path prepending, not general traffic engineering. but maybe mission creep and corner cases are the foundation of the game. randy _______________________________________________ GROW mailing list -- [email protected] To unsubscribe send an email to [email protected]
