> WHAT? I'm suggesting that you not treat routes with the ANYCAST
> community learned from R&E peers as if they are R&E routes, but as if
> they are normal internet routes.
> 
> I don't think you want to require or even recommend the removal of the
> ANYCAST community at an EBGP boundary.

well, in this case, with 'you' == robert, he does want it removed :)

fwiw, i don't.  the signal is an attribute of the BGP_PATH not the
peer.

randy

_______________________________________________
GROW mailing list
[email protected]
https://www.ietf.org/mailman/listinfo/grow

Reply via email to