[168431] in North American Network Operators' Group
Re: Route Server Filters at IXPs and 4-byte ASNs
daemon@ATHENA.MIT.EDU (Bryan Socha)
Sat Jan 25 10:38:44 2014
In-Reply-To: <20140125151859.GD2913@Eleanor.local>
From: Bryan Socha <bryan@serverstack.com>
Date: Sat, 25 Jan 2014 10:38:11 -0500
To: Job Snijders <job.snijders@hibernianetworks.com>
Cc: NANOG Mailing List <nanog@nanog.org>
Errors-To: nanog-bounces+nanog.discuss=bloom-picayune.mit.edu@nanog.org
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 | *bryan@serverstack.com <bryan@serverstack.com>*
*ServerStack* | Scale Big
On Sat, Jan 25, 2014 at 10:18 AM, Job Snijders <
job.snijders@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
>
