Re-reading, I was thinking of someone connecting to an IXP, not a new IXP needing a 2Byte. This is an interesting situation and you are correct, my comment was off topic.
*Bryan Socha* Network Engineer 646.450.0472 | *br...@serverstack.com <br...@serverstack.com>* *ServerStack* | Scale Big On Sat, Jan 25, 2014 at 10:18 AM, Job Snijders < job.snijd...@hibernianetworks.com> wrote: > On Sat, Jan 25, 2014 at 10:04:30AM -0500, Bryan Socha wrote: > > I have over 100,000 servers located in routing diverse datacenters > > with 4byte ASN numbers and have not had 1 problem or complaint related > > to the ASN for not able to communicate with the datacenter. The first > > 1 did make me really nervous for all of the reasons already mentioned > > but turned out to be a non-issue. > > This thread is not about reachability of prefixes announced by 4-byte > ASNs. This thread is about prefix filtering on Route Servers at Internet > Exchanges. > > > While it would be nice to see community string support increase to > 4byte, I > > think this is more of an educational challenge for the IXPs on how to > setup > > your community strings to work and not really a technical problem. > > Can you elaborate on how you would setup 'community strings'? > > Kind regards, > > Job >