Re: [Idr] Vendor Defaults (was Re: Review of draft-ietf-large-community-06.txt)

["Dickinson, Ian" <[e-mail]>]

Hi Robert,

>My example was very clear and I provided example of AS_PATH prepend.
>The point which you are missing is that if you execute community you should clean up and delete it.
>Blind default on or off is not the way to stop propagation of selected communities.
>And if someone is inserting 5539:* it seems obvious that the intention is that such community should get to 5539.

I would suggest that "clean up and delete" is not representative of all current usage that I know of.
The community is often left in place to show why a change in behaviour was triggered e.g. raising local preference.
This aids troubleshooting within IBGP and for downstream ASNs.

Ian

Information in this email including any attachments may be privileged, confidential and is intended exclusively for the addressee. The views expressed may not be official policy, but the personal views of the originator. If you have received it in error, please notify the sender by return e-mail and delete it from your system. You should not reproduce, distribute, store, retransmit, use or disclose its contents to anyone. Please note we reserve the right to monitor all e-mail communication through our internal and external networks. SKY and the SKY marks are trademarks of Sky plc and Sky International AG and are used under licence.

Sky UK Limited (Registration No. 2906991), Sky-In-Home Service Limited (Registration No. 2067075) and Sky Subscribers Services Limited (Registration No. 2340150) are direct or indirect subsidiaries of Sky plc (Registration No. 2247735). All of the companies mentioned in this paragraph are incorporated in England and Wales and share the same registered office at Grant Way, Isleworth, Middlesex TW7 5QD.