TahoeIX - Tahoe Internet Exchange - AS63212

The Tahoe Internet Exchange is a cooperative effort to foster community and regional routing. TahoeIX is the first exchange in Northern Nevada. Our mission is to make a positive impact on our local internetworking community. We help keep traffic local.

Announcements

Follow us on Twitter @TahoeIX

Why Join TahoeIX?

The Tahoe Internet Exchange connects participants to increase performance, enhance reliability, and keep traffic local to Northern Nevada.

As TahoeIX grows the stronger our Northern Nevada internet community becomes. All types and sizes of peers are welcome to join.

Thank you to our supporters and advisors:

We would like to extend a special thanks to the following participants since you can't start an exchange without anyone to exchange with.

History

Participants are encouraged to use the route server to openly peer with all participants - which is core of joining an exchange. Participants may still choose to peer bilaterally with important peers. The value of the exchange is greatly enhanced with open peering. TahoeIX should not be used for a participant's internal traffic.

Anyone is welcome to join the TahoeIX and participate in peering. There is no minimum prefix size on the exchange, although individual peers may have a minimum prefix length at their discretion. Both IPv4 and IPv6 is supported. TahoeIX does not have a membership fee. The exchange is supported by sponsors and donations.

  1. Peering is bilateral with the exception of route servers. There is no MLPA.
  2. BGP4 (or its successor) is used for peering and peers must set NEXT_HOP_SELF if advertising routes from other TahoeIX participants.
  3. Participants may not point default or statically route.
  4. Participants may not use another participant's resources without permission.
  5. Broadcast traffic may not be delivered to the exchange except as needed for normal operation and troubleshooting.
  6. Participants may not sniff traffic between other participants.
  7. Participants may only utilize a single layer-2 MAC address to place a single layer-3 router per port allocated from the TahoeIX switch fabric unless by prior agreement.
  8. Participants must make valid contact information and relevant documentation available at all times.
  9. No exchange participant may harm the exchange or other participants.

Participants are encouraged to create a PeeringDB entry for their AS if they don't already have one, however it is not mandatory for peering. Some participating peers may require a PeeringDB entry.

Because we are a small regional IX, closed or selective peering policies with minimum requirements are not recommended. We ask that peers with such policies at larger exchanges to make an exception at TahoeIX.

A BGP session to Route Server #1 is required for the looking glass. If you do not wish to use route servers for peering please tag your routes with the appropriate community. A connection to Route Server #2 is optional.

BGP Communities

The following communities are processed by the route server, but are not propagated to peers.

Standard Community Extended Community  
0:peer-as So:0:peer-as Do not advertise to peer-as
63212:peer-as So:63212:peer-as Advertise to peer-as
0:63212 So:0:63212 Do not advertise to any peer

The default behavior is to advertise to all peers.

How to Join TahoeIX

To join TahoeIX please send the following information to info < at > tahoeix < dot > org :

Public Information (for the website)

AS Number:
Organization Name:
Organization URL:
Short Description:

Private Information (for provisioning and contact)

Router MAC Address:
Tech Name:
Tech Email:
Tech Phone:
NOC Phone:
NOC Email:
Peering Email:
IPv6: yes/no

Transport Providers

Several regional and national carriers can provide transport services to the IX fabric with infrastructure present at our locations. Transport may also be available through other TahoeIX participants. This list is for informational purposes only - TahoeIX does not endorse any particular option.

We are using BIRD for our BGP route servers. Looking glass: www.tahoeix.org/lg

Active Peers

Peer or Name AS IP Notes
TahoeIX Route Server #1 63212 206.41.109.2
2001:504:3F::2/64
Required, see "notes" below.
TahoeIX Route Server #2 63212 206.41.109.3
2001:504:3F::3/64
Optional, but recommended.
Roller Network 11170 206.41.109.10
2001:504:3F::2BA2/64
Colocation Datacenter
High Desert Internet Services 32614 206.41.109.11
2001:504:3F::7F66/64
Internet Service Provider
Verisign 26415 206.41.109.13
2001:504:3F::672F/64
Global Registry Services
J-Root Operator, .COM/.NET Resolution
Packet Clearing House 3856 206.41.109.14
2001:504:3F::F10/64
PCH Research
WoodyNet 42 206.41.109.15
2001:504:3F::2A/64
PCH DNS Anycast
Akamai Technologies 20940 206.41.109.16
2001:504:3F::51CC/64
Content Delivery Network
AS112 Project 112 206.41.109.18
2001:504:3F::70/64
as112.rollernet.us
RIPE NCC 25152 206.41.109.19
2001:504:3F::6240/64
K-Root Operator
Internet Systems Consortium 395217 206.41.109.20
2001:504:3F::6:7D1/64
F-Root, Anycast Services
TahoeIX 395651 206.41.109.21
2001:504:3F::6:983/64
TahoeIX Services
GGC @ TahoeIX 11344 Google Global Cache
Route Server 1 Only

Notes

Route server #1 is required because it doubles as the looking glass. If your AS doesn't participate on route servers please tag your announcement to the route server/looking glass on AS63212 appropriately (see BGP communities below) or we can configure a filter on request.

Prefixes for L-Root AS20144 are available to IX participants through AS11170.

In Provisioning

Peer or Name AS IP Notes
Avant Wireless 22415 206.41.109.12 Internet Service Provider
Washoe County 15304 206.41.109.17 Government
Hurricane Electric 6939 206.41.109.22
2001:504:3F::1B1B/64
Internet Service Provider

DNS Geolocation Note

Some peers will use DNS geolocation to determine if their content will be served from peered resources on TahoeIX. Your DNS resolver will need to geolocate to the Reno/Sparks/Carson City and nearby areas for best results.

IPv4 Networks (RS1)
IPv4 Month

IPv6 Networks (RS1)
IPv6 Month

Daily Traffic Summary (every 5 minutes)
Traffic Day

Weekly Traffic Summary (30 Minute Average)
Traffic Week

Monthly Traffic Summary (2 Hour Average)
Traffic Month

Yearly Traffic Summary (1 Day Average)
Traffic Year

Green/Blue: Incoming/Outgoing Traffic
Dark Green/Magenta: Maximal 5 Minute Incoming/Outgoing Traffic

Email

info < at > tahoeix < dot > org

Phone

+1 775 525 2539 (voicemail only)

We will be notified of your message and return your call as soon as possible.

Postal and Shipping

Tahoe Internet Exchange
C/O Roller Network LLC
3545 Airway Dr. Suite 114
Reno, NV 89511

Please contact us first before shipping hardware.

Core

TahoeIX currently consists of two core switches: a Cisco 3750G-12S and a Nexus 3548P-10G connected with a 1Gbps inter-switch link. We are slowly migrating peers off of the 3750G (our first switch) and onto the 3548P donated by PCH. Once complete, the 3750G will be removed from service at the core.

Two route servers are avaiable: Route Server #1 is a virtual machine and Route Server #2 is a physical server.

Extensions

Extensions are managed by TahoeIX, but may run oversubscribed transport links back to the TahoeIX core depending on their physical location and may have a cost to connect. Contact us for more information.

Diagram

TahoeIX Topology