I would like to voice my opinion in support of community strings. I had 2 incidents a while ago where a member connected to the route server had a saturated link. It was impacting the quality of my customers connectivity. I wish I had the ability to just not announce to the one member, instead of the all or nothing option we currently have with the route servers.
-----Original Message-----
From: MICE Discuss [mailto:[log in to unmask]] On Behalf Of Doug McIntyre
Sent: Friday, October 17, 2014 5:52 PM
To: [log in to unmask]
Subject: Re: [MICE-DISCUSS] Route Server Announcement Control?
On Fri, Oct 17, 2014 at 10:19:16PM +0000, Charles Monson wrote:
> Do the MICE route servers offer any way to control BGP announcement to specific peers? I didn't see anything on the micemn.net website about ways to do that. With some of the larger content providers connecting to the exchange, the folks who have mostly inbound traffic might want a way to stop the route servers announcements to those potentially high traffic peers without entirely withdrawing advertisements to the route servers.
>
> Some of the other exchanges we connect at let you send a community indicating the ASN you don't want your prefixes advertisements to reach (e.g. you send a community of "0:11796" to stop the route servers from advertising your prefixes to Airstream). It would be nice to have something similar at MICE. Is this something already supported that I missed? Or something that may be considered as a future feature?
We do not have any community filters setup currently.
BIRD supports communities and filtering, but nobody has asked about it prior to now.
It looks like a huge example is at
http://download.de-cix.net/bird.conf.gz
Useful for others?
--
Doug McIntyre <[log in to unmask]>
~.~ ipHouse ~.~
Network Engineer/Provisioning/Jack of all Trades
