Route-Servers-Abstract-Line-Graphic-NYIIX

NYIIX ROUTE SERVERS

About the Thunderbird Route Servers

Telehouse America offers NYIIX Members the opportunity to peer via our New NYIIX Thunderbird Route Servers.

1. Benefits of Using the Thunderbird Route Servers:

Based on BIRD Internet Routing Daemon (http://bird.network.cz/)
Supports all IRR DBs as references to accept member’s routes (http://www.irr.net/docs/list.html)
Supports Export Filter based on BGP community attributes.
A large percentage of Members peer using Thunderbird. Once you connect you can start exchanging traffic immediately.
Setting up peering takes time and effort. When you use Thunderbird, only one peering session is required.
You will receive all routes announced by the members who peer with the Thunderbird. When a new party connects you can automatically exchange new prefixes.

2. Joining or Leaving the Thunderbird Route Servers

Joining the Thunderbird Route Servers is not mandatory for NYIIX Members. It is strictly optional and there is no requirement binding you to use them.

3. How Thunderbird Route Servers work (In a Nutshell)

Peer with the Thunderbird route Servers.
Announce routes you would like to join to the Thunderbird Route Servers members.
You will receive the routes from the members via the Thunderbird Route Server.
Optionally, you can generate your own inbound filter.

NYIIX Route-Servers-Abstract Lines Graphic

4. How do I Join the Thunderbird Route Server Service?

Prerequisites

Either AS-SET or Aut-num must be registered with an IRRdb.
Either Route objects or Route6 objects must be registered with an IRRdb.

Provide the following information:

ASN
IP Address at IIX: IPv4 or IPv6 or both
AS-SET name in Internet Routing Registry (the “IRR”) and the IRRdb in which it is registered. ex: RIPE RADB, ARIN etc..
TCP MD5 Signature: yes or no. If yes, need a password from you.
GTSM: yes or no

Please contact our IIX Engineering team to join the Thunderbird Route Servers @ iixeng@telehouse.com

5. Route Servers

NYIIX-NY Route Servers:

198.32.160.1/23 (primary)
198.32.160.2/23 (secondary)
2001:504:1::a501:3538:1/64 (primary)
2001:504:1::a501:3538:2 /64(secondary)
ASN 13538

*In order to receive all prefixes from the Route Server, “no bgp enforce-first-as” needs to be configured on your side.

NYIIX-LA Route Servers:

198.32.146.1/24 (primary)
198.32.146.2/24 (secondary)
2001:504:a::a501:3538:1 /64 (primary)
2001:504:a::a501:3538:2 /64 (secondary)
ASN 13538

*In order to receive all prefixes from the Route Server, “no bgp enforce-first-as” needs to be configured on your side.

6. Communities Supported

NYIIX Route servers support the following communities:

Eval Order	Community	Action
1	0:peer-as (standard)
	rt:0:peer-as (extended)	Do Not Advertise to peer-as
	ro:0:peer-as (extended)
	13538:0:peer-as (large)

2	13538:peer-as (standard)
	rt:13538:peer-as (extended)	Advertise to peer-as
	ro:13538:peer-as (extended)
	13538:1:peer-as (large)

3	0:13538 (standard)
	rt:0:13538 (extended)	Do Not Advertise to any peer
	ro:0:13538 (extended)
	13538:0:0 (large)

4	13538:13538 (standard)
	rt:13538:13538 (extended)	Advertise to any peer
	ro:13538:13538 (extended)
	13538:1:13538 (large)

Learn More About NYIIX Route Servers and How to Join Today.

Enter your email to get in touch or find out more.